Garrett804

The MP can't find your device. Do you have your task sequences deployed to "unknown Computers"? This could also be a network issue as well like IP_helpers or DHCP options PXE::MP_LookupDevice failed; 0x80004005

You really should look into a 10748 Deploying System Center 2012 course or the 10747 course for Administering System Center 2012 as they both will not only answer these questions for you but give you insight on overall design and implementation. I say that because you seem to not have a grasp over the system at all and something like SUP and "best practices" don't really exist because everyone has a preference as to when/how/why depending on the industry and size of the organization. Here are some of my quick answers for you though. 1. Disable the GPO, either decide if you want SCCM controlling overall update compliance and deployment or leave it as automatic updates 2. SCCM SUP integrates with WSUS and has the ability to control 100% of the overall compliance, deployment, and reporting for WSUS 3. I'm not sure what exactly you are pointing out here but the SUP database just like a WSUS database is going to pull updates based on your criteria that you have given it upon setting it up. (example: Windows 7, critical/security updates, service packs) 4. The circles on the right are for overall compliance in the entire environment based on devices in your system with configuration manager clients installed. The meanings are either compliant (they have the update/updates installed), Not Compliant (They don't have them installed), Unknown (There has been no reported compliance back to the MP or FSP so the system does not know one way or the other) Again I'd recommend you get into some good training classes or find a local SCCM Group you can sit down with over coffee and have it not only verbally explained to you but maybe even demonstrated.

So I've done this before a few times in lab and once in production. What I found was that I had to make some final "tweaks" to things like re-installing SUP upon restore and a few other roles including my MP role. Total down time for the system was about 2 days while I worked out the kinks in everything. I have to go through the transition next year though once my server is up from its warranty and lease which I'm not looking forward to again. We are also going UCS so my system will most likely end up with SQL on the cluster and my system as one of many VM's on our UCS setup. Thanks to all the great information on here though I believe I can hopefully get through this ok without to many headaches (SQL being the big one that is going to arise).

Each machine has its own unique ID so it would just realize they already exist in its Database.

The account you are using the console in must have admin rights on the machines in order to execute remote PS commands.

I don't personally uninstall our older java versions as we have lots of vendors that require specific versions in order to work as they check for a specific version. (this annoys me greatly) As far as deploying java I use a program named SuperOrca to edit the .MSI file so that it disables the automatic update feature and doesn't restart. Then I just create an application and use the following to deploy msiexec /i "jre1.8.0_45.msi" /q I've never had any issues with the deployment going out and it installs automatically on any new machines that are discovered as well which makes less manual work for me. I'm working on compliance rules right now for many applications and settings so that I can hopefully automate more.

Ok so lets get the setup down first. You have a Seperate server with SQL hosting your CM DB. Is this server setup to SQL Server best practices (seperate OS on disks, SQL on disk, SQL Tempdb on disk, SQL logs on disk) to allow for the appropriate performance? For instance my SQL logs drive is only 12.8Gb in size of data and is 2x146gb 15k sas drives and I have had my system up for almost 2.5 years. Those logs are for not only SCCM but for the Reporting Server and SUSDB logs as well. If this is a shared SQL Server then how are you isolating it to SCCM logs that are causing the data usage and not one of the other intances?

If these clients have SCCM you could also just setup compliance for the applications and it will check against the compliance rules and either install it if they don't have it or just leave it alone if they do have it.

If you go through the instructions on that site is very easy to get the files imported again. If you can break down which part you are struggling with in those instructions I can try and help you further along.

Well I just looked through my wsyncmgr.log file specifically for one of those updates on your screenshot. Skipped update c1dcfd69-2509-40c4-b00e-171383062c42 - Security Update for Microsoft Excel 2010 (KB2910902) 32-Bit Edition because it was superseded. SMS_WSUS_SYNC_MANAGER 6/24/2015 1:07:28 AM 5560 (0x15B8) Looks like they are superseded but of course the MS documentation for the updates doesn't say what took their place.. go figure.

Not working as in you aren't able to get a new boot image imported? Not working as in the image you did get imported isn't booting?

That would be a maintenance window that you are looking for.

Ok so on the machines with the issue you can't even manually run the file? You can however manually connect to the location via the UNC path from the problem machine?

I like looking at at the update history by going to windows updates then click view update history and sorting by date installed there. By doing it in the programs menu like you are doing it does a group organization so depending on how you have it grouped it sorts them. So your saying that in all the groups that your arranged in nothing later than 5/20/2015 is installed?

Depending on how you are doing the memberships if its direct or Query based and you have the check box for "Use Incremental updates for this collection" that will be why they are updating at random times. Like Peter said you'll need to investigate the colleval.log as well in order to try and pin it down. The limiting collections though won't add anything to another collection unless its running a query and/or incremental update check. If you are going to always do direct membership then I'd leave the check box unchecked for the Incremental updates.

A. You should be more professional with your language that you use. B. Here are some simple instructions to create a new boot image using the ADK 8.1 WinPE image file. http://www.scconfigmgr.com/2014/02/28/default-boot-images-was-not-updated-after-a-configmgr-2012-r2-upgrade/

check the classifications that you are importing for SCCM. I believe those are security updates for the classification. Another issue may be if they are superceeded or expired it won't sync them into its database. Also if they were there once and are not anymore then it can be that the maintenance task cleaned them out of the SCCM Database. http://www.mnscug.org/blogs/brian-mason/145-purging-expired-updates-in-cm12 That site explains it a bit more but basically there is a weekly task that does the cleaning. If you open your wsyncmgr.log you will see a section where it states its deleting expired updates etc.. Updated 78 items in SMS database, new update source content version is 446 SMS_WSUS_SYNC_MANAGER 6/29/2015 1:02:47 AM 26816 (0x68C0) Sync time: 0d00h02m46s SMS_WSUS_SYNC_MANAGER 6/29/2015 1:02:47 AM 26816 (0x68C0) Deleting old expired updates... SMS_WSUS_SYNC_MANAGER 6/29/2015 1:02:47 AM 26816 (0x68C0) Deleted 3 expired updates SMS_WSUS_SYNC_MANAGER 6/29/2015 1:02:47 AM 26816 (0x68C0) Deleted 39 expired updates SMS_WSUS_SYNC_MANAGER 6/29/2015 1:02:48 AM 26816 (0x68C0) Deleted 39 expired updates total SMS_WSUS_SYNC_MANAGER 6/29/2015 1:02:48 AM 26816 (0x68C0)

If its restarting at the preparing network connections part then I'd think you have either the network for the VM set wrong somehow or the drivers aren't present.

Ok if its a task sequence not available issue then its either an approval issue as was stated above or its a deployment issue with the task sequence not being deployed to a collection this machine is a member of.

Yeah I'd try to redo the boot images and go from there.

I don't know what that error number is but if you are using the machinename for the server UNC link and you have a DNS issue at all it could be faulting from some machines not having good DNS going to them. Try navigating to the source location UNC path on one of the failing ones to see if you can get to the files/folders. If that works then try manually running the command on that machine and see if it works manually even.

usually the reboot is due to a driver issue, the drivers you need for the WinPE environment are the sata controller and network. Turn on the Cmd prompt options and when you see it loading up in WinPE press F8 to pop up the command prompt. This will keep it from rebooting and allow you to see if it pulls an IP etc...

Do you have the client and office packages on the DP that you are doing the OSD from?

did you distribute your update group package to the DP that the machine you are using is in a boundry group for?

Uninstall the SUP role, wait for it to complete. Uninstall WSUS. Reboot Install WSUS but don't configure it Install SUP Check all Classifications but don't check any products and run a sync. Once sync completes check the classifications and products you want to sync and sync manually again. Verify the updates are shown in your catalog. Create update group or deploy individual update to test collection with test machine. On the client machine run a software updates scan cycle.