I’ve seen this before with SCCM 2007, and then the problem was the client was still in Provisioning Mode.
Provisioning Mode is a mode that the client is in during OSD, which blocks policies from being applied during the installation. Once the task sequence is complete, the client should have been brought out of this mode, and get its policies correctly.
One easy way to check this is opening the Registry Editor and checking this value:
Provisioning Mode is a mode that the client is in during OSD, which blocks policies from being applied during the installation. Once the task sequence is complete, the client should have been brought out of this mode, and get its policies correctly.
One easy way to check this is opening the Registry Editor and checking this value:
Sure enough, the client was still in Provisioning Mode.
So, how should we solve this?
One way is to change the value in the registry and then reinstall the client, but since this happens on almost all new installations, this would be some seriously tedious work.
The easiest solution is to add these two registry changes as seperate command line steps in your Task Sequence after the “Setup Windows and ConfigMgr” step:
Do a new installation now and it should work!
Note: This does not actually solve the underlying issue why the client is still left in Provisioning Mode. It does however get your deployment solution up and running again.
Courtesy Link : http://www.danielclasson.com/how-to-force-an-sccm-2012-client-out-of-provisioing-mode-during-osd/
No comments:
Post a Comment