SCCM ConfigMgr MP Deinstallation failed Client Registration Issues ConfigMgr. In ConfigMgr/SCCM, Management Point issues are common. It makes a bit interesting when we had a client registration issue after successfully completing the Task Sequence.
The other functionalities of MP like delivering new policies to the existing clients were working fine, so the only issue was with client registration. In our scenario, the client completed the Task Sequence successfully however it was not getting registered to ConfigMgr Management Point.
Table of Contents
SCCM ConfigMgr MP Deinstallation failed Client Registration Issues
I’m not at all expert in the OSD/TS part of SCCM / ConfigMgr, so I was under the assumption during TS the client will get registered with SCCM 2012 MP. However, it seems this is not true?, the SCCM client is registered with MP only after Task Sequence completion.
To prove this, I had checked SmsTs.log, AppEnforce.log, and ClientIDManagerStartup.log. In the ClientIDManagerStartup.log, I could see the following entries.
[RegTask] - Client registration is pending. Sending confirmation request for GUID:6CE6E0PC-4584-4DA1-BE52-D3EBFB29E4C0 ... [RegTask] - Sleeping for 1920 seconds ...
Client Registration Issues ConfigMgr
Then I tried to read around to find about the background process of the client registration and policy retrieval during Task Sequence. During a SCCM OSD Task Sequence, the SCCM client is placed in provisioning mode. So what is provisioning mode?
In provisioning mode, the client does not pick up policy from the MP. This is done so that advertised programs, software updates, and tasks targeted to existing client PCs do not run until the Task Sequence completes. So until the client is provisioning mode, it won’t be able to register with SCCM Management Point.
More details on provisioning mode http://blogs.technet.com/b/configurationmgr/archive/2010/09/13/solution-after-a-configmgr-2007-osd-task-sequence-completes-the-client-may-not-automatically-pull-down-policy.aspx
So back to the original issue, the SCCM ConfigMgr client is not getting registered with MP. I tried checking following logs @ remote MP Site System.
MP_ClientID.log – Nothing much related to the problematic client :
Parse a client ID request Send reply message to the client SMS_UniqueIdentifier0=GUID:441C77F7-3097-4FE9-8BB1-3863D87EB719, LastPXEAdvertisementID=, LastPXEAdvertisementTime=, OfferID=PK020024, OfferIDTime=2/20/2014 11:32:00 AM, PkgID=CAS001SE, PackageVersion=, PackagePath=http://acncmrs.configmgr.com/SMS_DP_SMSPKG$/CAS001PC, BootImageID=CAS001PC, Mandatory=0, Known=1
MP_CliReg.log :- Following entries are there in the log file.
SMS MP Registration Manager stopped. SMS MP Registration Manager started. Could not load logging configuration for component MP_RegistrationManager. Using default values.
MP_RegistrationManager.log :- Following entries are there in the log file.
MP Reg: Did not find client(GUID:5B942C7F-A352-4940-B668-B45BA1515976) public key. This may be because the client has not registered yet. MP Reg: Processing completed. Completion state = 0
None of the new clients are not getting registered. When we checked MPcontrol.log and MP communication with existing clients everything looked fine. While checking MPSetup.log, we found that MP got reinstalled 2 days before. After that this issue started popping up. So what next ?
SCCM ConfigMgr MP Deinstallation failed Client Registration Issues ConfigMgr
One of the options is to remove the MP role and add it back. We removed MP however the remote SCCM MP deinstall was not successful, it got failed. The Sitecomp.log file gave some hints about the issue. SCCM ConfigMgr MP Deinstallation failed and Client Registration Issues ConfigMgr.
Cannot delete registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\SMS_EXECUTIVE\Threads\SMS_COMPONENT_MONITOR on server acncmrs.configmgr.com . The operating system reported error 997: Overlapped I/O operation is in progress. Deinstallation failed and will be retried in the next polling cycle.
On the remote MP, we’ve checked the registry entry and confirmed that Role Install account has full access to the registry entry. So what next? Taken the backup of the registry entry “HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\SMS_EXECUTIVE\Threads\SMS_COMPONENT_MONITOR” and deleted the registry entry given in the above log snippet from remote ConfigMgr SCCM Management Point.
Great that did the trick. Sitecomp.log at primary site indicated that SCCM MP deinstalled or removed successfully. Also, confirmed this with the MPSETUP.log file at remote MP site system server. Added back the MP site system role to remote site system. Performed a test build and Yes, the client is able to register with MP. Issue resolved 😉
Quite easy isn’t it? So what I learned from this issue is provisioning and client registration process post Task Sequence completion !!