SCCM Client error applying policy (Full Version)

All Forums >> [Management Products] >> System Center Products >> System Center Configuration Manager



Message


jmuszynski -> SCCM Client error applying policy (9/29/2008 10:13:56 AM)

Recently we have seen a number of SCCM clients that are installed, but not receiving policies from server. They have all recently been renamed. In the policy agent log we see the following entery repeated:




Download of policy CCM_Policy_Policy4.PolicyID="{be7a1a61-f25d-4aeb-bb9a-b65bb8c670b6}",PolicySource="SMS:NCH",PolicyVersion="2.00" failed (DTS Job ID: {E3E1D9DD-4C97-41A8-9E37-E4DB889E5865}) PolicyAgent_PolicyDownload 09/29/2008 9:28:46 AM 7580 (0x1D9C)
Failed to open to WMI namespace '\\OLDComputerName\ROOT\ccm\policy\machine\requestedconfig' (800706ba) PolicyAgent_PolicyDownload 09/29/2008 9:28:53 AM 7580 (0x1D9C)
Failed to reset policy state. Policy download will not be retried. PolicyAgent_PolicyDownload 09/29/2008 9:28:53 AM 7580 (0x1D9C)





This happened to about 5% of the renamed PCs, the rest worked correctly, and the logs show the correct computer name. All the machines have identical software, and were built with Windows XP recently. There are no records for the client by name or  GUID on the server.

I have connected to the PCs, and verified the permissions, and content of WMI, and it appears to be correct.
We have tried a rebuild of the WMI store just in case with no success.
Repairing the client had no impact. 
Uninstalling the client using ccmsetup.exe /uninstall then reinstalling had no impact.

Everything else on the computer is working correctly, but if we can't find a way to get these working I will have to rebuild them.

Any pointers to what we can try will ge very much appreciated.




dstein -> RE: SCCM Client error applying policy (10/3/2008 6:51:11 AM)

Were they renamed after having been discovered?  Were they installed using an imaging process like Ghost?  Can you identify any common trait among the failures?




ame -> RE: SCCM Client error applying policy (10/9/2008 5:18:55 AM)

We have the same issue using SMS2003.
Yes, they were renamed after having been discovered and were they installed using an imaging process like Ghost (SMSGUID was reset).

In our case CCMClean.exe and client reinstall resolves it, but I guess it can be fixed some other easier way.

Other way: stop SMS agent, delete C:\WINDOWS\system32\CCM\ServiceData\Messaging\EndpointQueues\PolicyAgent_PolicyDownload\00000001.msg (it contains old computername) and que and start SMS agent




Page: [1]

Valid CSS!




Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI
0.28125