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: mcdonald...@hotmail.com To: mssms@lists.myitforum.com 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
