chthomas

Jerry, I just cleared this issue up in one of my elementary labs and plan on making some changes that should prevent this in the future. Hopefully it's not too late to help you or others. It looks like this could be caused if your OSD TS has a Restart step with a small timer. If the client doesn't have enough time after "Setup Windows and ConfigMgr" step it will get stuck in Provisioning Mode. In addition is looks like some people were saying 2012 (pre-SP1 and def. pre-R2) would sometimes just get clients stuck in Provisioning Mode. My intention is to check each TS and change the Restart step to 60 seconds. I'm pretty sure I lowered it to 5 seconds after our guys were complaining the multiple restarts I had were taking too long. I also intend on putting two Run Command steps after "Setup Windows and ConfigMgr" with the following in each one: REG ADD HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\CCM\CcmExec /v ProvisioningMode /t REG_SZ /d false /f REG ADD HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\CCM\CcmExec /v SystemTaskExcludes /t REG_SZ /d "" /f As a manual workaround, and tested today, I created a bat file for our guys to run. The command window will stay open for the duration of the ccmsetup.exe process and I left it that way as a visual indication of when it was finished so people wouldn't have to check Task Manager. Also be aware that my reading this weekend seems to show that manually doing a Machine Policy Retrieval & Evaluation Cycle action right after installing a client does NOT help at all. All it does is place a request in the queue BEHIND the client installations initial policy request. You just have to sit it out and wait patiently.It DOES work to force a policy retrieval if the initial policy has already come down, just not right after installation. This is the content of the bat for the technicians: I ran that bat file on each desktop, waited 5-10 minutes and was able to shutdown all machines through SCCM. NOTE: If I'm incorrect on the Machine Policy Retrieval thing please let me know. -Chris