I am trying to build a HP x64 2008 R2 server using SCCM SP2 OSD with
I have customized the task sequence, which deploys the OS
The issue i am having is after the Setup windows and ConfigMgr
step, i install roles and features, then want to do a reboot to apply
the roles etc because subsequent steps require some of the roles to be
installed before they will run, i.e. HP PSP(psp-8.30.w2k8R2.x64.exe
/install) requires SNMP role to be installed. <Info on HP PSP can be found Here. >

But after the reboot
step the task sequence fails and doesn’t resume.
Is there any
pre-requisites needed if we want to put a reboot in an OSD step?

i.e. Gather, Use toolkit steps, before or after reboot? The reboot is
set to  “Currently installed default OS”.

I have tried numerous
If i put a reboot anywhere in my task sequence(after the Setup Windows and Config Mgr step), the steps following the reboot do not run,
no advertisements apply post build and i have the issue specified here
i.e. SCCM is stuck in provisioning mode.

If i take the reboots out the TS completes just fine and everything is
ok(e.g. not stuck in provisioning mode, and all steps get fired)..
However i need reboots for 2 reasons:
1. because subsequent steps needs the roles installed e.g HP PSP and
snmp role.
2. To avoid the broadcom teaming bug with Hyper-V..
e.g. i need to have the hyper-v role installed and thus a reboot before
i do the teaming step.

It seems to me like SCCM is having an issue resuming from the reboot and carrying on the remainder of the TS with the SCCM service installed.

i.e. without the reboot SCCM is running in a different context in that it is running without sccm service being installed, but after the reboot it switches over, as can be seen when viewing the logs, i.e. in winpe mode without SCCM service installed it is logging to smsts.log under x:\windows\temp\smsts\smsts.log, then after reboot it collates all logs and starts logging to c:\windows\syswow64\ccm\logs\ as it would under normal operation in full OS.

See below for
OSD steps.

The Task Sequence..

Full Size


 Full Size

reboot Loads to WINPE and says initializing SMS client… Then just reboots(log files below show that it gets an error and never initializes).


Log Files


Failed to set log directory. Some
execution history may be

The system
 cannot find the file specified. (Error: 80070002; Source:
 Windows)        OSDSetupHook        19/01/2010
 9:24:41 AM        912 (0x0390)
 sequence        OSDSetupHook        19/01/2010
 9:24:41 AM        912 (0x0390)
 (e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,467)        OSDSetupHook        19/01/2010
 AM        912 (0x0390)
 (e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,467)        OSDSetupHook        19/01/2010
 AM        912 (0x0390)
(e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,467)        OSDSetupHook        19/01/2010
 AM        912 (0x0390)
 (e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,1395)        OSDSetupHook        19/01/2010
 AM        912 (0x0390)
 Sequence environment not found.  Task sequence completed in Windows
 PE.        OSDSetupHook        19/01/2010
 9:24:41 AM        912 (0x0390)
 Hook        OSDSetupHook        19/01/2010
 9:24:41 AM        912 (0x0390)
 setup hook from registry.        OSDSetupHook        19/01/2010
 9:24:41 AM        912 (0x0390)
 C:\WINDOWS\system32\OSDGINA.DLL        OSDSetupHook        19/01/2010
 9:24:41 AM        912 (0x0390)
Could not
 delete the file C:\WINDOWS\system32\OSDSETUPHOOK.EXE. Error code
 5        OSDSetupHook        19/01/2010
 9:24:41 AM        912 (0x0390)
Marking the
 file C:\WINDOWS\system32\OSDSETUPHOOK.EXE for deletion on
 Reboot        OSDSetupHook        19/01/2010
 9:24:41 AM        912 (0x0390)
 C:\WINDOWS\system32\OSDSETUPHOOK.EXE        OSDSetupHook        19/01/2010
 AM        912 (0x0390)
 C:\WINDOWS\system32\_SMSOSDSetup        OSDSetupHook        19/01/2010
 9:24:41 AM        912 (0x0390)
 logging from process
 908        OSDSetupHook        19/01/2010
 9:24:41 AM        912 (0x0390)
 finalized logs to SMS client log directory from
 C:\WINDOWS\SysWOW64\CCM\Logs        OSDSetupHook        19/01/2010
 9:24:41 AM        912 (0x0390)
Cleaning up
 task sequencing logging
 configuration.        OSDSetupHook        19/01/2010
 9:24:41 AM        912 (0x0390)


Client Agent Settings for the client are missing from
WMI.        execmgr        19/01/2010
9:26:19 AM        3496 (0x0DA8)

As you can see from my Task sequence steps above i have set it to log progress to a progress.log, showing time and step its upto.

e.g. cmd /c echo %date% %time% Before reboot >> c:\admin\install\logs\Progress.log

As can be seen by viewing the progress log below sccm never executes the next step in the OSD after the reboot step.


19/01/2010  9:17:19.74 Before reboot

Stuck in Provisioning Mode

PS C:\Users\Administrator> Reg query HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\CCM\CcmExec

CheckIdleEndpointSeconds    REG_DWORD    0x12c
CheckMemorySeconds    REG_DWORD    0x3c
FileCleanupSeconds    REG_DWORD    0xa8c0
CoFreeSeconds    REG_DWORD    0x258
LowMemoryThresholdMBytes    REG_DWORD    0x14
SystemTaskExcludes    REG_SZ    SchedulerStartup;SchedulerShutdown;SchedulerLogon;SchedulerLogoff;ClientRegistrationStartup
CheckUserSeconds    REG_DWORD    0x258
ProvisioningMode    REG_SZ    true
ADTimeOutSeconds    REG_DWORD    0x258



Looks like its one of the roles and
features i have selected… if i
disable the roles and features step, my TS completes fine, if its
enabled and a reboot is included afterward it never completes.

Here is an export of the roles and features i have set…

 <step type=”BDD_InstallRoles” name=”Install Roles and
description=”” runIn=”WinPEandFullOS” successCodeList=”0″>
<action>smsswd.exe /run: cscript.exe
<variable name=”OSFeatures”
<variable name=”OSRoleServices”
<variable name=”OSRoles”

Checking the ztiroles log shows…

2010-01-07 15:15:42.039 [Sync] Warning (Id=0) Sync of ‘.NET Framework
skipped because the sync of its antecedent ‘.NET Framework 3.5.1’ needs

2010-01-07 15:15:42.039 [ServerManagerCmd] Error (Id=0) Installation of
[Application Server] .NET Framework 3.5.1 failed. The computer must be
restarted to complete another installation. After restarting the
please re-run the same command to install this role.

2010-01-07 15:15:42.086 [Sync] Warning (Id=0) Sync of ‘HTTP Activation’
because the sync of its antecedent ‘HTTP Activation’ needs reboot

2010-01-07 15:15:42.086 [ServerManagerCmd] Error (Id=0) Installation of
[Application Server] HTTP Activation failed. The computer must be
restarted to
complete another installation. After restarting the computer, please
re-run the
same command to install this role.

2010-01-07 15:15:42.086 [Sync] Warning (Id=0) Sync of ‘Web Server (IIS)
Support’ skipped because the sync of its antecedent ‘Static Content’

2010-01-07 15:15:42.086 [ServerManagerCmd] Error (Id=0) Installation of
[Application Server] Web Server (IIS) Support failed. The computer must
restarted to complete another installation. After restarting the
please re-run the same command to install this role.

2010-01-07 15:15:42.086 [ServerManagerCmd]          [STAT]

Overall Sync Time:
‘33.8820381’ second(s)

2010-01-07 15:15:42.086 [ServerManagerCmd]          Error:

Installation of one or more
roles, role services, or features failed, and a restart is required.
Check the
Server Manager log for additional information and try again.

at the log file above, i un-ticked the Web Server (IIS) and HTTP
Activations(see below).

OSD package now reboots and resumes successfully, and the features that
i unselected are in fact still installed, so another feature must be
installing the features as part of their prerequisites, issue
finally solved!!

So in the end it was due to the Roles and Features Step, it would seem that when a reboot was placed in the TS, and there was a feature(s) that had failed to install because it needed a reboot, when this reboot happened(initiated by the ts)  it would try and install the features, on boot and then reboot underneath SCCM hence leaving SCCM in an unknown or provisioning state.

That probably didn’t make any sense so ill try to explain by means of an example.

In Roles and Features, the Web Server (IIS) Support feature when selected failed to install with a The computer must
restarted to complete another installation. After restarting the
please re-run the same command to install this role.” 

After the Roles and Features step, i have a reboot in my TS.

The TS initiates this reboot fine, when the server comes up from this reboot, SCCM shows initializing the config mgr client….

In the back ground it would seem that the Web Server IIS Support feature is now trying to install.

After a few mins the config mgr client initializes and sccm resumes the ts..

Meanwhile the Web Server IIS Support feature is still installing.

So the SCCM ts could now be part way through its remaining steps and all of a sudden the server reboots again (unexpectedly), i.e. not initiated by sccm or the ts, so my only guess is that the Web Server IIS feature has completed and is forcing the reboot itself.

Then when the server boots up sccm is stuck in provisioning mode, and never completes all its remaining steps.

Any feedback welcome, i can’t see the internal workings of SCCM so the above is just my observations\thoughts.

This entry was posted in Computers and Internet. Bookmark the permalink.

2 Responses to SCCM OSD ISSUES

  1. Lyle says:

    HI MateGreat article!! I am having the exact same issue and your article helped heaps, however I still am getting the same problem which I think is due to the Hyper V role being installed. The TS does not continue after this stepI was wondering if you could let me know how you got your TS working please, if that\’s ok? Or possible just post another screenhot of your working TS in regards to this maybe?Cheers

  2. Shawn says:

    Any chance you could send me the details of the task sequence steps you are using? I’m working on deploy Proliant servers through SCCM and it’s been tricky to get HP software to install and get the Windows Roles and Features to install correctly even when using MDT tasks from within SCCM. Thanks!

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s