SCCM 2012 with SP1 R2 OSD deployment system never returns to task sequence after SCCM client install reboots

Server was just upgraded to R2 and in test OSD drops there is no further Task Sequence progress beyond the SCCM client installation reboot. Checking ccmsetup.log and it installs OK on test system. Droping a Windows 7 x86 with SP1 Task sequence that worked previously. The only thing I wondering is if its because of I'm using a Windows PE 4.0 Boot wim? 

February 6th, 2014 1:51pm

What does it mean it drops? Are you seeing abort errors on screen?

Are you testing on a VM or workstation?

Free Windows Admin Tool Kit Click here and download it now
February 6th, 2014 1:55pm

Post your SMSTS.log and that will help with troubleshooting.
February 6th, 2014 1:59pm

Wow, tried to Post but it doesn't like the size. Wish I could attach the file.
Free Windows Admin Tool Kit Click here and download it now
February 6th, 2014 3:22pm

Post it in the body instead.
February 6th, 2014 3:25pm

Or better yet, review it yourself and find the issue (or get close at least) and just post the relevant snippet. Part of being a ConfigMgr admin is reading log files and troubleshooting based on those log files. You may not know the exact issue, but you should at least be able to narrow it down by reviewing the log file. This is a very key ConfigMgr skill.
Free Windows Admin Tool Kit Click here and download it now
February 6th, 2014 3:49pm

We have had this same issue and just changing the TS to a WinPE 5.0 boot image fixed it. I know that R2 has some support for importing WinPE 3.1 and 4.0 boot images but I am not sure if the documented process you have to go through for this fixes something in the image which enables it to work (see the sticky at the top of the forum).

If you change your TS to use WinPE 5.0 then I am sure it will work. If not then as Jason said please review the log and post the part of the log containing the failure.

Mark.

  • Edited by Mark_Thomas Friday, February 07, 2014 7:17 PM
February 7th, 2014 7:16pm

Helpful tip when searching logs - open them up with the cmtrace tool. It's located in your site server share under "Tools"

It'll help you find the relevant warnings and errors much quicker than note/wordpad.

Free Windows Admin Tool Kit Click here and download it now
February 7th, 2014 9:02pm

Any luck with this issue? I'm having the same issue. Upgraded to R2. Windows 7 and 8.0 works ok, Windows 8.1 task sequence loads straight to login page after installing client,
March 4th, 2014 10:05pm

Can I just add - I'm not sure how Jason's comment has been marked as the answer. This doesn't help anyone encountering the same issue, such a
Free Windows Admin Tool Kit Click here and download it now
March 4th, 2014 10:13pm

I am having the same exact issue your talking about.

Here is what someone suggested.  Have you also applied the hotfix KB2905002.

Installation information

This update applies to Central Administration sites, primary sites, administrator consoles, and clients. After you apply this update to a site server, you can create client update packages.

After the update is installed on site servers, any operating system boot images should be updated. To update boot images after the hotfix is applied, follow these steps:

  1. In the Configuration Manager console, click Software Library.
  2. In the Software Library workspace, expand Operating Systems, and then click Boot Images.
  3. Select the boot image that you want to update.
  4. Right-click and then select the Update Distribution Points action.

    Note This action updates all distribution points and may have an adverse effect on an environment that contains many distribution points.
  5. Repeat steps 3 and 4 for all boot images that have previously been distributed.
March 4th, 2014 10:36pm

I am opening up a Severity B case with MS, I can update you on the resolution in about 2 hours.
Free Windows Admin Tool Kit Click here and download it now
March 4th, 2014 10:45pm

I've attached the smsts.log below. As I mentioned in a previous post, Windows 7 and 8.0 works ok. its just Windows 8.1.

I created a new boot image as mentioned previously, but that had no effect.

<![LOG[==============================[ OSDSetupHook.exe ]==============================]LOG]!><time="10:11:09.498-660" date="03-05-2014" component="OSDSetupHook" context="" type="1" thread="2204" file="osdsetuphook.cpp:186">
<![LOG[Executing task sequence]LOG]!><time="10:11:09.577-660" date="03-05-2014" component="OSDSetupHook" context="" type="1" thread="2204" file="osdsetuphook.cpp:279">
<![LOG[Loading the Task Sequencing Environment from "C:\_SMSTaskSequence\TSEnv.dat".]LOG]!><time="10:11:09.702-660" date="03-05-2014" component="OSDSetupHook" context="" type="1" thread="2204" file="basesetuphook.cpp:366">
<![LOG[Environment scope successfully created: Global\{51A016B6-F0DE-4752-B97C-54E6F386A912}]LOG]!><time="10:11:09.780-660" date="03-05-2014" component="OSDSetupHook" context="" type="1" thread="2204" file="environmentscope.cpp:623">
<![LOG[Environment scope successfully created: Global\{BA3A3900-CA6D-4ac1-8C28-5073AFC22B03}]LOG]!><time="10:11:09.780-660" date="03-05-2014" component="OSDSetupHook" context="" type="1" thread="2204" file="environmentscope.cpp:623">
<![LOG[Debug shell is enabled]LOG]!><time="10:11:22.045-660" date="03-05-2014" component="OSDSetupHook" context="" type="1" thread="2204" file="basesetuphook.cpp:1470">
<![LOG[Successfully enabled debug command shell support.]LOG]!><time="10:11:22.045-660" date="03-05-2014" component="OSDSetupHook" context="" type="1" thread="2204" file="debugwindow.cpp:156">
<![LOG[Configuring local administrator account]LOG]!><time="10:11:22.045-660" date="03-05-2014" component="OSDSetupHook" context="" type="1" thread="2204" file="basesetuphook.cpp:1492">
<![LOG[Enabling local administrator account]LOG]!><time="10:11:22.045-660" date="03-05-2014" component="OSDSetupHook" context="" type="1" thread="2204" file="basesetuphook.cpp:1219">
<![LOG[Account was already enabled]LOG]!><time="10:11:22.045-660" date="03-05-2014" component="OSDSetupHook" context="" type="1" thread="2204" file="basesetuphook.cpp:1228">
<![LOG[Re-assign all drive letters...]LOG]!><time="10:11:22.045-660" date="03-05-2014" component="OSDSetupHook" context="" type="1" thread="2204" file="diskutils.cpp:1941">
<![LOG[The drive information which has no drive letter can not be found. No need to re-assign driver letters.]LOG]!><time="10:11:22.062-660" date="03-05-2014" component="OSDSetupHook" context="" type="1" thread="2204" file="diskutils.cpp:1951">
<![LOG[Installing SMS client]LOG]!><time="10:11:22.062-660" date="03-05-2014" component="OSDSetupHook" context="" type="1" thread="2204" file="basesetuphook.cpp:1504">
<![LOG[Clearing existing client configuration.]LOG]!><time="10:11:22.077-660" date="03-05-2014" component="OSDSetupHook" context="" type="1" thread="2204" file="installclient.cpp:291">
<![LOG[Cleaning existing client certificates from SMS certificate store]LOG]!><time="10:11:22.077-660" date="03-05-2014" component="OSDSetupHook" context="" type="0" thread="2204" file="installclient.cpp:138">
<![LOG[Restoring SMS client identity.]LOG]!><time="10:11:22.077-660" date="03-05-2014" component="OSDSetupHook" context="" type="1" thread="2204" file="installclient.cpp:321">
<![LOG[The client certificates were not found in the environment. New certificates will be generated.]LOG]!><time="10:11:22.077-660" date="03-05-2014" component="OSDSetupHook" context="" type="1" thread="2204" file="installclient.cpp:355">
<![LOG[Successfully restored the client identity.]LOG]!><time="10:11:22.077-660" date="03-05-2014" component="OSDSetupHook" context="" type="1" thread="2204" file="installclient.cpp:359">
<![LOG[TS started from an unknown machine... Using submitted GUID GUID:428b74dc-51d0-406e-9c2a-f7070a121149]LOG]!><time="10:11:22.077-660" date="03-05-2014" component="OSDSetupHook" context="" type="1" thread="2204" file="installclient.cpp:376">
<![LOG[Using CRL: ]LOG]!><time="10:11:22.077-660" date="03-05-2014" component="OSDSetupHook" context="" type="1" thread="2204" file="installclient.cpp:952">
<![LOG[Importing certificates to root store]LOG]!><time="10:11:22.077-660" date="03-05-2014" component="OSDSetupHook" context="" type="1" thread="2204" file="utils.cpp:5349">
<![LOG[Executing command line: "C:\WINDOWS\system32\_SMSOSDSetup\TsProgressUI.exe" /Register:WinPE]LOG]!><time="10:11:22.139-660" date="03-05-2014" component="OSDSetupHook" context="" type="1" thread="2204" file="commandline.cpp:827">
<![LOG[==========[ TsProgressUI started in process 2692 ]==========]LOG]!><time="10:11:22.405-660" date="03-05-2014" component="TsProgressUI" context="" type="1" thread="2696" file="winmain.cpp:330">
<![LOG[Registering COM classes]LOG]!><time="10:11:22.405-660" date="03-05-2014" component="TsProgressUI" context="" type="1" thread="2696" file="winmain.cpp:187">
<![LOG[sbModulePath = C:\WINDOWS\system32\_SMSOSDSetup\TsProgressUI.exe]LOG]!><time="10:11:22.405-660" date="03-05-2014" component="TsProgressUI" context="" type="1" thread="2696" file="tsprogressuiclass.cpp:625">
<![LOG[Shutdown complete.]LOG]!><time="10:11:22.436-660" date="03-05-2014" component="TsProgressUI" context="" type="1" thread="2696" file="winmain.cpp:512">
<![LOG[Process completed with exit code 0]LOG]!><time="10:11:22.452-660" date="03-05-2014" component="OSDSetupHook" context="" type="1" thread="2204" file="commandline.cpp:1123">
<![LOG[Successfully registered TS Progress UI.]LOG]!><time="10:11:22.452-660" date="03-05-2014" component="OSDSetupHook" context="" type="1" thread="2204" file="utils.cpp:2862">
<![LOG[Executing command line: "C:\_SMSTaskSequence\OSD\MEL00003\ccmsetup.exe" /useronly /source:C:\_SMSTaskSequence\OSD\MEL00003 /config:MobileClient.TCF /status:732]LOG]!><time="10:11:22.749-660" date="03-05-2014" component="OSDSetupHook" context="" type="1" thread="2204" file="commandline.cpp:827">
<![LOG[Process completed with exit code 1]LOG]!><time="10:17:25.560-660" date="03-05-2014" component="OSDSetupHook" context="" type="1" thread="2204" file="commandline.cpp:1123">
<![LOG[Client installation failed, code 1]LOG]!><time="10:17:25.560-660" date="03-05-2014" component="OSDSetupHook" context="" type="3" thread="2204" file="installclient.cpp:1151">
<![LOG[Set authenticator in transport]LOG]!><time="10:17:25.685-660" date="03-05-2014" component="OSDSetupHook" context="" type="0" thread="2204" file="libsmsmessaging.cpp:7734">
<![LOG[Non fatal error 0x80070057 in sending task sequence execution status message to MP]LOG]!><time="10:17:25.919-660" date="03-05-2014" component="OSDSetupHook" context="" type="2" thread="2204" file="utils.cpp:6390">
<![LOG[Set authenticator in transport]LOG]!><time="10:17:25.919-660" date="03-05-2014" component="OSDSetupHook" context="" type="0" thread="2204" file="libsmsmessaging.cpp:7734">
<![LOG[Non fatal error 0x80070057 in sending task sequence execution status message to MP]LOG]!><time="10:17:25.966-660" date="03-05-2014" component="OSDSetupHook" context="" type="2" thread="2204" file="utils.cpp:6390">
<![LOG[Executing command line: "C:\WINDOWS\system32\_SMSOSDSetup\TsProgressUI.exe" /Unregister]LOG]!><time="10:17:26.982-660" date="03-05-2014" component="OSDSetupHook" context="" type="1" thread="2204" file="commandline.cpp:827">
<![LOG[==========[ TsProgressUI started in process 888 ]==========]LOG]!><time="10:17:27.044-660" date="03-05-2014" component="TsProgressUI" context="" type="1" thread="2872" file="winmain.cpp:330">
<![LOG[Unregistering COM classes]LOG]!><time="10:17:27.044-660" date="03-05-2014" component="TsProgressUI" context="" type="1" thread="2872" file="winmain.cpp:204">
<![LOG[Shutdown complete.]LOG]!><time="10:17:27.044-660" date="03-05-2014" component="TsProgressUI" context="" type="1" thread="2872" file="winmain.cpp:512">
<![LOG[Process completed with exit code 0]LOG]!><time="10:17:27.044-660" date="03-05-2014" component="OSDSetupHook" context="" type="1" thread="2204" file="commandline.cpp:1123">
<![LOG[Successfully unregistered TS Progress UI.]LOG]!><time="10:17:27.044-660" date="03-05-2014" component="OSDSetupHook" context="" type="1" thread="2204" file="utils.cpp:2903">
<![LOG[Failed to install SMS Client (0x80004005)]LOG]!><time="10:17:27.044-660" date="03-05-2014" component="OSDSetupHook" context="" type="3" thread="2204" file="basesetuphook.cpp:1506">
<![LOG[Uninstalling Setup Hook]LOG]!><time="10:17:27.060-660" date="03-05-2014" component="OSDSetupHook" context="" type="1" thread="2204" file="basesetuphook.cpp:1628">
<![LOG[Removing setup hook from registry.]LOG]!><time="10:17:27.060-660" date="03-05-2014" component="OSDSetupHook" context="" type="0" thread="2204" file="vistasetuphook.cpp:143">
<![LOG[Successfully removed C:\WINDOWS\system32\OSDGINA.DLL]LOG]!><time="10:17:27.060-660" date="03-05-2014" component="OSDSetupHook" context="" type="1" thread="2204" file="basesetuphook.cpp:1321">
<![LOG[Successfully removed C:\WINDOWS\system32\OSDSETUPHOOK.EXE]LOG]!><time="10:17:27.091-660" date="03-05-2014" component="OSDSetupHook" context="" type="1" thread="2204" file="basesetuphook.cpp:1321">
<![LOG[Successfully removed C:\WINDOWS\system32\_SMSOSDSetup]LOG]!><time="10:17:27.091-660" date="03-05-2014" component="OSDSetupHook" context="" type="1" thread="2204" file="basesetuphook.cpp:1358">
<![LOG[RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgram]LOG]!><time="10:17:27.091-660" date="03-05-2014" component="OSDSetupHook" context="" type="2" thread="2204" file="utils.cpp:811">
<![LOG[GetTsRegValue() is unsuccessful. 0x80070002.]LOG]!><time="10:17:27.091-660" date="03-05-2014" component="OSDSetupHook" context="" type="2" thread="2204" file="utils.cpp:842">
<![LOG[End program: ]LOG]!><time="10:17:27.091-660" date="03-05-2014" component="OSDSetupHook" context="" type="1" thread="2204" file="basesetuphook.cpp:1642">
<![LOG[Successfully finalized logs to SMS client log directory from C:\WINDOWS\CCM\Logs]LOG]!><time="10:17:27.122-660" date="03-05-2014" component="OSDSetupHook" context="" type="1" thread="2204" file="tslogging.cpp:1542">
<![LOG[Cleaning up task sequence folder]LOG]!><time="10:17:27.122-660" date="03-05-2014" component="OSDSetupHook" context="" type="1" thread="2204" file="utils.cpp:2329">
<![LOG[Deleting volume ID file C:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca ...]LOG]!><time="10:17:27.591-660" date="03-05-2014" component="OSDSetupHook" context="" type="1" thread="2204" file="resolvesource.cpp:506">
<![LOG[Failed to execute task sequence (0x80004005)]LOG]!><time="10:17:27.591-660" date="03-05-2014" component="OSDSetupHook" context="" type="3" thread="2204" file="osdsetuphook.cpp:284">

March 4th, 2014 11:36pm

I've resolved the issue we had. When a hotfix is required for SCCM, normally you patch the servers and deploy the hot fix to clients and in task sequences add the Patch=xx step in the Setup Windows and Configmgr step.

To get around using the Patch=  property in a task sequence you can simply add the updates into the following folder "X:\Program Files\Microsoft Configuration Manager\Client\x64\ClientPatch" (applicable to x86 folder also)

The setup windows and configmgr step always look in this folder, it just isn't document anywhere by Microsoft :). We stumbled across this by looking through logs one day.

Anyway the problem was that we had two R2 hotfixes in this folder. One of the hotfixes was actually superseded by the other, so once it was removed the build rebooted and installed apps and scripts etc.

Glen

Free Windows Admin Tool Kit Click here and download it now
March 5th, 2014 8:08am

<![LOG[Executing command line: "C:\_SMSTaskSequence\OSD\MEL00003\ccmsetup.exe" /useronly /source:C:\_SMSTaskSequence\OSD\MEL00003 /config:MobileClient.TCF /status:732]LOG]!><time="10:11:22.749-660" date="03-05-2014" component="OSDSetupHook" context="" type="1" thread="2204" file="commandline.cpp:827">
<![LOG[Process completed with exit code 1]LOG]!><time="10:17:25.560-660" date="03-05-2014" component="OSDSetupHook" context="" type="1" thread="2204" file="commandline.cpp:1123">
<![LOG[Client installation failed, code 1]LOG]!><time="10:17:25.560-660" date="03-05-2014" component="OSDSetupHook" context="" type="3" thread="2204" file="installclient.cpp:1151">

It seems as if the client installation failed. What does ccmsetup.log tell?
March 5th, 2014 8:09am

this is not supported.
Free Windows Admin Tool Kit Click here and download it now
July 25th, 2015 10:18am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics