XP OSD Failing after R2 CU2 Upgrade

[xstatic411]

We have recently upgraded from SCCM 2012 SP1 to r2 CU2. I am trying to recover the ability to image with XP using the boot.wim from sp1 (not the new ones created with r2). The task sequence successfully boots into PE, formats drive, applies OS and installs CM client. I have been able to validate each step in my smsts.log. The TS reboot after the Client install and never resumes the TS.

 

Here is what I see in the SMSTS.log:

Failed to get the environment key.
Failed to resume task sequence (0x800700EA).
Exiting with return code 0x800700EA
Process completed with exit code 2147942634
Task sequence completed 0x800700EA

 

SMSTS.log with errors:

==============================[ OSDSetupHook.exe ]==============================10/07/2014 14:08:23

Executing task sequence 10/07/2014 14:08:23
Loading the Task Sequencing Environment from "C:\_SMSTaskSequence\TSEnv.dat".10/07/2014 14:08:23
Environment scope successfully created: Global\{51A016B6-F0DE-4752-B97C-54E6F386A912}10/07/2014 14:08:23
Environment scope successfully created: Global\{BA3A3900-CA6D-4ac1-8C28-5073AFC22B03}10/07/2014 14:08:23
Debug shell is enabled 10/07/2014 14:08:33
Successfully enabled debug command shell support. 10/07/2014 14:08:33
Configuring local administrator account 10/07/2014 14:08:33
Enabling local administrator account 10/07/2014 14:08:33
Account was already enabled 10/07/2014 14:08:33
Re-assign all drive letters... 10/07/2014 14:08:33
The drive information which has no drive letter can not be found. No need to re-assign driver letters.10/07/2014 14:08:33
Installing SMS client 10/07/2014 14:08:33
Clearing existing client configuration. 10/07/2014 14:08:33
Cleaning existing client certificates from SMS certificate store10/07/2014 14:08:33
Restoring SMS client identity. 10/07/2014 14:08:33
The client certificates were not found in the environment. New certificates will be generated.10/07/2014 14:08:33
Successfully restored the client identity. 10/07/2014 14:08:33
Using CRL: true 10/07/2014 14:08:33
Unable to read SMS client cert from environment. Not restoring SMS client cert.10/07/2014 14:08:33
Executing command line: "C:\WINDOWS\system32\_SMSOSDSetup\TsProgressUI.exe" /Register:WinPE10/07/2014 14:08:33
==========[ TsProgressUI started in process 1272 ]==========10/07/2014 14:08:34
Registering COM classes 10/07/2014 14:08:34
sbModulePath = C:\WINDOWS\system32\_SMSOSDSetup\TsProgressUI.exe10/07/2014 14:08:34
Shutdown complete. 10/07/2014 14:08:34
Process completed with exit code 0 10/07/2014 14:08:34
Successfully registered TS Progress UI. 10/07/2014 14:08:34
Executing command line: "C:\_SMSTaskSequence\OSD\SWH00326\ccmsetup.exe" /useronly /source:C:\_SMSTaskSequence\OSD\SWH00326 /config:MobileClient.TCF /status:157210/07/2014 14:08:34
Process completed with exit code 0 10/07/2014 14:13:09
Start to cleanup TS policy 10/07/2014 14:13:09
End TS policy cleanup 10/07/2014 14:13:09
Active request handle is empty, registering with new active request handle. This is expected if the TS was started from a media/PXE.10/07/2014 14:13:09
Saving the new active request handle for the task sequence: {9D7AE9CB-A717-4D06-A1E2-DFD623C92A4E}10/07/2014 14:13:09
Succesfully registered the tasksequence with the execution manager10/07/2014 14:15:01
Executing command line: "C:\WINDOWS\system32\_SMSOSDSetup\TsProgressUI.exe" /Unregister10/07/2014 14:15:02
==========[ TsProgressUI started in process 1228 ]==========10/07/2014 14:15:02
Unregistering COM classes 10/07/2014 14:15:02
Shutdown complete. 10/07/2014 14:15:02
Process completed with exit code 0 10/07/2014 14:15:02
Successfully unregistered TS Progress UI. 10/07/2014 14:15:02
Moving logs to SMS client directory 10/07/2014 14:15:02
Successfully moved logs to SMS client log directory: C:\WINDOWS\CCM\Logs\SMSTSLog10/07/2014 14:15:02
Executing task sequence manager bootstrap 10/07/2014 14:15:02
Executing command line: "C:\WINDOWS\CCM\TSMBootstrap.exe" /env:Gina /configpath:C:\_SMSTaskSequence /bootcount:110/07/2014 14:15:02
==============================[ TSMBootStrap.exe ]==============================10/07/2014 14:15:02
Command line: "C:\WINDOWS\CCM\TSMBootstrap.exe" /env:Gina /configpath:C:\_SMSTaskSequence /bootcount:110/07/2014 14:15:02
Current OS version is 5.1.2600.3 10/07/2014 14:15:02
Logging successfully initialized. 10/07/2014 14:15:03
Resuming Task Sequence in Full OS 10/07/2014 14:15:03
Failed to get the environment key. 10/07/2014 14:15:03
Failed to resume task sequence (0x800700EA). 10/07/2014 14:15:03
Exiting with return code 0x800700EA 10/07/2014 14:15:03
Process completed with exit code 2147942634 10/07/2014 14:15:03
Task sequence completed 0x800700EA 10/07/2014 14:15:03
Stopped the service 'ccmexec' successfully 10/07/2014 14:15:08
Uninstalling Setup Hook 10/07/2014 14:15:08
No need to register WFGina for this OS! 10/07/2014 14:15:08
Successfully removed C:\WINDOWS\system32\OSDGINA.DLL10/07/2014 14:15:08
Successfully removed C:\WINDOWS\system32\OSDSETUPHOOK.EXE10/07/2014 14:15:08
Successfully removed C:\WINDOWS\system32\_SMSOSDSetup10/07/2014 14:15:08
RegQueryValueExW failed for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgram10/07/2014 14:15:08
GetTsRegValue() failed. 0x80070002. 10/07/2014 14:15:08
End program: 10/07/2014 14:15:08
Successfully finalized logs to SMS client log directory from C:\WINDOWS\CCM\Logs10/07/2014 14:15:08

[anyweb]

well if it's failing at the client installation, what does the ccmsetup.log tell you ?

[xstatic411]

From what I can tell the client is installed and functioning at the correct CU level. Ive attached both ccmsetup logs.

ccmsetup-20141007-141233.log

ccmsetup.log

[fredbeard]

Have you upgraded AIK to 8.1 and imported the new boot images? If your boot images are > 6.3 you'll experience the TS not finishing.