TS Fails at Setup Windows and Configuration Manager after upgrade to 1606

[lord_hydrax]

Hi,

 

Been a while since I had to do anything to my environment but last week I finally updated SCCM 2012 SP1 to 1606.

 

The update itself seemed to go pretty smoothly.

 

We are finding that our Task Sequence stops at the Setup Windows and Configuration Manager step and won't install any of the applications/packages that are list in the steps after.

 

I guessed that maybe the Configuration Manager Client Package had automatically updated to support the latest version so I have redistributed to all my DPs but still the TS stops after the Setup Windows and Configuration Manager step.

 

The client seems to install fine as the agent is running and gets the client policy thats assigned.

 

Here is the last part of the smsts.log

 

Command line: "C:\WINDOWS\CCM\TSMBootstrap.exe" /env:Gina /configpath:C:\_SMSTaskSequence /bootcount:1 TSMBootstrap 8/03/2017 2:49:49 PM 1748 (0x06D4)

Current OS version is 6.1.7601.1 TSMBootstrap 8/03/2017 2:49:49 PM 1748 (0x06D4)

Logging successfully initialized. TSMBootstrap 8/03/2017 2:49:49 PM 1748 (0x06D4)

Resuming Task Sequence in Full OS TSMBootstrap 8/03/2017 2:49:49 PM 1748 (0x06D4)

No logging settings found in TS environement TSMBootstrap 8/03/2017 2:49:49 PM 1748 (0x06D4)

Failed to get the environment key. TSMBootstrap 8/03/2017 2:49:49 PM 1748 (0x06D4)

Failed to resume task sequence (0x800700EA). TSMBootstrap 8/03/2017 2:49:49 PM 1748 (0x06D4)

Exiting with return code 0x800700EA TSMBootstrap 8/03/2017 2:49:49 PM 1748 (0x06D4)

Process completed with exit code 2147942634 OSDSetupHook 8/03/2017 2:49:49 PM 1612 (0x064C)

Task sequence completed 0x800700EA OSDSetupHook 8/03/2017 2:49:49 PM 1612 (0x064C)

Waiting for command shell to complete. OSDSetupHook 8/03/2017 2:49:49 PM 364 (0x016C)

Terminating system message loop. OSDSetupHook 8/03/2017 2:53:31 PM 364 (0x016C)

Wallpaper has changed since initialization so it will not be reverted. OSDSetupHook 8/03/2017 2:53:31 PM 1612 (0x064C)

Exiting SetClientProvisioningMode 0x00000000 OSDSetupHook 8/03/2017 2:53:37 PM 1612 (0x064C)

Uninstalling Setup Hook OSDSetupHook 8/03/2017 2:53:37 PM 1612 (0x064C)

Removing setup hook from registry. OSDSetupHook 8/03/2017 2:53:37 PM 1612 (0x064C)

Successfully removed C:\WINDOWS\system32\OSDGINA.DLL OSDSetupHook 8/03/2017 2:53:37 PM 1612 (0x064C)

Could not delete the file C:\WINDOWS\system32\OSDSETUPHOOK.EXE. Error code 5 OSDSetupHook 8/03/2017 2:53:37 PM 1612 (0x064C)

Marking the file C:\WINDOWS\system32\OSDSETUPHOOK.EXE for deletion on Reboot OSDSetupHook 8/03/2017 2:53:37 PM 1612 (0x064C)

Successfully removed C:\WINDOWS\system32\OSDSETUPHOOK.EXE OSDSetupHook 8/03/2017 2:53:37 PM 1612 (0x064C)

Successfully removed C:\WINDOWS\system32\_SMSOSDSetup OSDSetupHook 8/03/2017 2:53:37 PM 1612 (0x064C)

::RegOpenKeyExW (HKEY_LOCAL_MACHINE, c_szSMSTSKey, 0, KEY_READ, &hSubKey), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\utils.cpp,258) OSDSetupHook 8/03/2017 2:53:37 PM 1612 (0x064C)

RegOpenKeyExW failed for Software\Microsoft\SMS\Task Sequence OSDSetupHook 8/03/2017 2:53:37 PM 1612 (0x064C)

GetTsRegValue() failed. 0x80070002. OSDSetupHook 8/03/2017 2:53:37 PM 1612 (0x064C)

End program: OSDSetupHook 8/03/2017 2:53:37 PM 1612 (0x064C)

Finalizing logging from process 1600 OSDSetupHook 8/03/2017 2:53:37 PM 1612 (0x064C)

Successfully finalized logs to SMS client log directory from C:\WINDOWS\CCM\Logs OSDSetupHook 8/03/2017 2:53:37 PM 1612 (0x064C)

Any ideas?

[lord_hydrax]

I read that I need to update the boot images I use for the TS.

 

I checked and I see I have these new ones version 10.0.14393.0 so i assigned them to the TS but I get the error 8007002 as soon as I start the TS.

 

Can't get logs cause command prompt isn't enabled in the new boot image, will enable and upload asap.... although when pxe booting it still seemed to grab the old boot image so I don't know whats going on yet.

 

Obviously a bit of work I still need to do here....

[lord_hydrax]

So this is fixed now, I added a bunch of the optional components to the new boot image (ver 10.0.14393.0) as well as a couple of network drivers and all seems good now.