rvent04

0 I am having trouble with my clients recieving updates. I notice alot of my clients where my primary site is are recieving updates but all of my clients in my secondary sites are not. Below is output from the WUAHandler.log on a client system. Group policy settings were overwritten by a higher authority (Domain Controller) to: Server HTTPS://SERVER.COMPANY.COM:443 and Policy ENABLED WUAHandler 4/12/2013 8:21:28 AM 4220 (0x107C) Failed to Add Update Source for WUAgent of type (2) and id ({AA27FC20-A281-46CC-B04F-D0940B5E072F}). Error = 0x87d00692. WUAHandler 4/12/2013 8:21:28 AM 4220 (0x107C) The server stated above is correct and we have no GPOs applied to our enviornment for an update server. I did just update to SCCM 2012 SP1 and have applied all the hotfixes for WSUS. I am at a roadblock. Perhaps WSUS and SUP reinstall? Any help would be appreciated I am out of ideas. I did a site reset but that didnt help. My enviornment: 1 primary server - roles- sup, dp, mp 3 secondary sites - role - dp and mp - clients under these sites do not get updates

After my upgrade to SP1 I noticed that the compliance level of my update lists had dropped considerably. I am noticing there are 200-230 clients in an “unknown” compliance state. I am worried that something is wrong with the software updates compliance policy or worse something wrong on over 200 of my clients. I have applied all the hotfixes that were suggested before upgrading to SP1. WSUS is up to date with newest hotfixes as well. The majority of my clients health checks are fine. Not all of my clients are updated to the latest SCCM client 7804 but I wouldn’t think this would cause an issue with update compliance. I triple checked my client settings on my primary server. Clients are set to check every hour. Nothing was changed for this before the SP1 upgrade. Am I missing something else? Is there a specific log to check for this? It’s strange to me that before the upgrade I had high compliance rates and now they are very low. Any help would be appreciated.

So to reinstall a client I have had to stop WMI, nuke the repository folder(s), and then restart WMI to rebuild the repository. After that the client will install fine. Otherwise it fails. I am actually going to try a reset on the repository through cmd line because MS says this is better practice. We'll see. To have to hit 250 clients is going to be painful. MS really screwed up on this one.

Its just that simple! I have removed the update on my primary and 3 of my MPs and removed the SCCM client from all 4 servers. Thats the only way I have been able to keep my MP roles stable. I have had some issues with auto client installation on machines as well. If I right click the machine and push the client through the wizard it will install fine. SIMONLJ when you removed WMF on workstations and reinstalled the client did you have to rebuild the repository folder in C:\windows\wbem? I read that this is someth that needs to be done but I have tried on some servers and their clients still fail checks. So I have no evidence in my enviornment this resolves anything. Anyways this is horrible but glad I am not alone in this issue.

Sad to say I am a victim of this evil KB. My management points crashed so I uninstalled the role and reinstalled. Also removed the KB from the servers and removed the CCM client. My management points went green for a while today but look to be failing again. Client check failure is going up in count by the hour. Anyone know if SP1 will truley fix this issue? I know its in beta but I am tempted at this point to apply it. I am also hoping this wont require alot of clean up work on my clients. Right after a migration too from SCCM 2007. Happy Holidays from Microsoft :angry: