The blog post below is discussing how to fix the client that was stuck in provisioning mode. This is only addressing the symptom though and not the root cause which you really should identify. IME, clients get stuck in provisioning mode for one of two reasons (in addition to what James said below):
- The TS fails for some reason even though it looks like it finished. - An application or command-line run during the TS causes an unexpected reboot or "mucks" with the network configuration of the target system causing the TS engine to hiccup. Until you find the root cause, IMO you are just deploying broken systems. J From: [email protected] [mailto:[email protected]] On Behalf Of James Murphy Sent: Wednesday, July 2, 2014 9:48 PM To: [email protected] Subject: RE: [mssms] CM12 clients stuck in Provisioning Mode after OSD Hi Brian, When i encountered this similar situation with our 2007 environment, i came across the same blog post. Make sure you double check all of your 'Restart Computer' steps in the task sequence. I had a couple of restarts in one of mine that I neglected to change the 'Specify what to run after restart' selection to the "currently installed default operating system" Also check that you're allowing enough time for the step just before a restart to complete, before your restart runs. You might need to increase the timeout, especially if the install step is running a batch or .cmd file that may not report back completion in a timely manner. Jim ________________________________ From: [email protected]<mailto:[email protected]> To: [email protected]<mailto:[email protected]> Subject: [mssms] CM12 clients stuck in Provisioning Mode after OSD Date: Wed, 2 Jul 2014 09:15:28 -0500 Hey everyone, Thanks for all who assisted with helping me identify the problem with my Cm12 clients getting stuck in ProvisioningMode. Now that I've narrowed down the issue, I need to determine how to resolve it. I came across the following blog and was curious if anyone knows if this is applicable to Cm12? 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 It will take me heaps amount of time to troubleshoot what is causing the sequence to reboot so I'm looking for a quick fix. Has anyone tried the above method in a CM12 environment? Thanks, Brian
