/ Insights / SCCM Clients Stuck in Provisioning Mode Insights SCCM Clients Stuck in Provisioning Mode September 17, 2013 Concurrency, Inc.I recently had a client with an issue in which all of the SCCM Clients were stuck in Provisioning Mode after the OSD Task Sequence completed. Before I get to the cause and the fix, let’s cover what Provisioning Mode is, why it’s a problem, and how to identify if it’s your issue. First, Provisioning Mode is what SCCM uses to process the steps in a Task Sequence and block other Deployments from running until it finishes. This is important because it allows your Task Sequences to finish everything they need to do before any other actions can start. However, if the SCCM Client stays in Provisioning Mode, no other Deployments or Policies are processed after the Task Sequence is complete. The symptoms of this issue:Nothing is displayed in Software Center.Required Deployments do not run.If it is an OSD Task Sequence, the SCCM Client will not download the client policies and actions will be missing from the client applet.You can also check the following registry keys to determine if this is your issue and fix it at the same. HKEY_LOCAL_MACHINESOFTWAREMicrosoftCCMCcmExecProvisioningMode Provisioning Mode = True Normal Mode = False HKEY_LOCAL_MACHINESOFTWAREMicrosoftCCMCcmExecSystemTaskExcludes This should be empty in when the client is not in Provisioning Mode. Lastly, there is the cause for this issue. In my case, it was the final step in the OSD Task Sequence being a reboot to the Boot Image instead of the Default Operating System. (Incorrect Setting) When the final step reboots to the Boot Image, the system then sees it has nothing do and reboots again without taking the system out of Provisioning Mode. The system then boots into Windows, and everything works, except the SCCM Client. I hope this helps you and let me know if you come across any other causes for this issue.