ConfigMgr 2012 OSD Installing Package Hangs

Deploying a captured image hangs at the first install package step when you start the OSD deployment just after you update the Distribution Point with the caputered image. The strange thing is that when you wait for 12hours the deployment will work fine.

In the smsts.log you will find repeatedly;
<![LOG[Waiting for job status notification…]LOG]!>

When searching the web i found a request for help on the Technet Forum. It seems to be a bug and has not been fixed in ConfigMgr 2012 CU1, CU2 or CU3.
Link to the Technet Forum:

Happely there is a fix that came from a support call with Microsoft.
The fix delete a Maintenance Taks which has a “MaxRunTime” of 43200 seconds  what is 12hours. See the below image:

Just put this Visual Basic Script or PowerShell Command Line in your Build and Capture Task Sequence before the step “Capture the Reference Machine”. Or you can add the script in your deploy Task Squence just before your first Install Package step.
In my case i added it in the B&C Task Sequence like the below image.


Visual Basic Script
strComputer = “.” Set objSWbemServices = GetObject(“winmgmts:\\” & strComputer & “\root\ccm”)
Set colSWbemObjectSet = objSWbemServices.InstancesOf(“SMS_MaintenanceTaskRequests”)
For Each objSWbemObject In colSWbemObjectSet
strInstance = “SMS_MaintenanceTaskRequests.TaskID='”&objSWbemObject.TaskID&”‘”
objSWbemServices.delete strInstance

PowerShell Command Line (thanks to Trevor Sullivan)
C:\Windows\System32\WindowsPowerShell\v1.0\PowerShell.exe -noprofile -command “&{Get-WmiObject -Namespace root\ccm -Class SMS_MaintenanceTaskRequests | % { $_.Delete(); };}”

After the new capture i updated the Distribution Point and succesfuly deployed the Task Sequence.

2 Responses to ConfigMgr 2012 OSD Installing Package Hangs


    PowerShell is much shorter than the VBscript code:

    Get-WmiObject -Namespace root\ccm -Class SMS_MaintenanceTaskRequests | % { $_.Delete(); };

  2. Thanks Trevor… I will update the post


leave your comment