PART 2, the more reliable solution
Post deployment clients are not talking to the SCCM server and updating it with their information.
The blog post here has some great information on how to solve the issue. What it doesnt cover is how to get the PC's you have rolled out already.
What J.C. Hornbeck does mention is where to correct it, the registry key:
HKLM\SOFTWARE\Microsoft\CCM\CcmExec\ProvisioningMode="true"
I have created a Group Policy Preference to change the "true" to a "false". Follow this up with the script from Microsoft here. If you are deploying this out there, comment all the "Echo" commands out so it gives no prompts and is 100% silent.
This is NOT a fix for the root issue, but gets the clients already deployed to comunicate back to the mothership
I have found that this isnt reliable.
ReplyDeleteSome machines will report back and work but this isnt dependable.
The replacement solution has been posted here:
Deletehttp://faildeploy.blogspot.co.uk/2012/05/sccm-client-not-updating-server-part-2.html