OSD Task Sequence : Formatted the drive, dropped the image on the PC

Issue:  When trying to perform an OSD Task Sequence using SCCM 2007, the deployment fails, usually after it has successfully formatted the drive, dropped the image on the PC, and scanned for drivers. Looking at the SMSTS.log, the following error is logged: Task sequence cannot continue after reboot because TS Manager is not configured to auto-start or GINA is not installed    TSManager
CheckForRebootRequest(&bRebootInitiated), HRESULT=80004005 (e:nts_sms_fresmsclienttasksequenceexecutionengineengine.cxx,274)    TSManager
Fatal error is returned in check for reboot request of the action (Restart Computer).
Unspecified error (Error: 80004005; Source: Windows    TSManager
An error (0x80004005) is encountered in execution of the task sequence    TSManager Cause:  This issue is caused because the “Setup windows and ConfigMgr” task has either been removed, disabled, or has been moved to the wrong place in the Task Sequence. The “Setup windows and ConfigMgr” task performs several tasks that prepares the PC from going from WinPE to the Windows Setup, including modifying boot managers to boot to the correct partition. Once it finishes preparing the PC, this task then reboots the PC at the proper time to start Windows Setup or Mini-Setup. If this task is removed, it will cause the deployment to fail because the PC was not properly prepared. Resolution: For these reasons, the “Setup windows and ConfigMgr” task should never be removed, disabled, or moved to another place other than the default in the Task Sequence. Moving it to another place in the Task Sequence may cause the PC not to be prepared or rebooted at the correct time, causing the deployment to fail. The “Setup windows and ConfigMgr” task should also not be marked as Continue on Error because if this task does error out, the deployment will probably fail anyway.

Leave a Comment