Hello

We will stage a Windows 2012 server with SCCM 2012 SP1. The Build and Capture work without Problems.

But when we deploy the WIM with a Task sequence the Task sequence hang when the First Software Package will be installed. When we remove the Software package and redeploy the Task sequence succeed without error. When we start then a Software package via the Software center, that work on an other Server without problems, the Status is always Waiting to install.

We have looked in the smsts.log and execmgr.log and have not found any error. In the Location.log the Client is attached to the Correct Site and have the Correct Boundary.

Any Ideas?

Andreas

• Moved by Kent AgerlundMVP Friday, April 26, 2013 2:40 PM

Check for a duplicate MAC address for the offend

Hi Gerry

We have non duplicate MAC address. But this morning I have seen that also on Win 8 Clients Tasksequence to not run in the full OS

Andreas

Please post SMST

Is the Option ""Allow this application to be installed from the Install Application Task sequence Action without being deployed" on the General Information tab of you application checked?

• Edited by dekac99 Monday, April 29, 2013 1:32 PM

Is the package expecting any input from a user? It may be displaying an 'invisible' dialog?

Neil

Hello

Sorry for my late answer. I was this week not often in the office. I had some success but today it dosent work again.

At one time it worked, i have only rebootet the sccm Server. Today I would go to production and then i had the following error:

"Windows could not configure one or more system components. To install Windows, restart the computer and then restart the installation."

Because I have made some Offline updates I was thinking that there is a Problem. I have recreatet the wim, and now i have again the Problem. All Package work fine in a Tasksequence with W2k8 R2 or when they are attached direct to a OS. The Package to not expecting a input from a user.

I have found in the smsts.log some certificates erros

==============================[ OSDSetupHook.exe ]============================== OSDSetupHook 03.05.2013 21:06:27 1816 (0x0718)
Executing task sequence OSDSetupHook 03.05.2013 21:06:27 1816 (0x0718)
Loading the Task Sequencing Environment from "C:\_SMSTaskSequence\TSEnv.dat". OSDSetupHook 03.05.2013 21:06:27 1816 (0x0718)
Environment scope successfully created: Global\{51A016B6-F0DE-4752-B97C-54E6F386A912} OSDSetupHook 03.05.2013 21:06:27 1816 (0x0718)
Environment scope successfully created: Global\{BA3A3900-CA6D-4ac1-8C28-5073AFC22B03} OSDSetupHook 03.05.2013 21:06:27 1816 (0x0718)
Debug shell is enabled OSDSetupHook 03.05.2013 21:06:28 1816 (0x0718)
Successfully enabled debug command shell support. OSDSetupHook 03.05.2013 21:06:28 1816 (0x0718)
Configuring local administrator account OSDSetupHook 03.05.2013 21:06:28 1816 (0x0718)
Enabling local administrator account OSDSetupHook 03.05.2013 21:06:28 1816 (0x0718)
Re-assign all drive letters... OSDSetupHook 03.05.2013 21:06:28 1816 (0x0718)
The drive information which has no drive letter can not be found. No need to re-assign driver letters. OSDSetupHook 03.05.2013 21:06:28 1816 (0x0718)
Installing SMS client OSDSetupHook 03.05.2013 21:06:28 1816 (0x0718)
Clearing existing client configuration. OSDSetupHook 03.05.2013 21:06:28 1816 (0x0718)
Cleaning existing client certificates from SMS certificate store OSDSetupHook 03.05.2013 21:06:28 1816 (0x0718)
Restoring SMS client identity. OSDSetupHook 03.05.2013 21:06:28 1816 (0x0718)
The client certificates were not found in the environment. New certificates will be generated. OSDSetupHook 03.05.2013 21:06:28 1816 (0x0718)
Successfully restored the client identity. OSDSetupHook 03.05.2013 21:06:28 1816 (0x0718)
Using CRL:  OSDSetupHook 03.05.2013 21:06:28 1816 (0x0718)
Unable to read SMS client cert from environment. Not restoring SMS client cert. OSDSetupHook 03.05.2013 21:06:28 1816 (0x0718)
Executing command line: "C:\Windows\system32\_SMSOSDSetup\TsProgressUI.exe" /Register:WinPE OSDSetupHook 03.05.2013 21:06:28 1816 (0x0718)
==========[ TsProgressUI started in process 1872 ]========== TsProgressUI 03.05.2013 21:06:28 1876 (0x0754)
Registering COM classes TsProgressUI 03.05.2013 21:06:28 1876 (0x0754)
sbModulePath = C:\Windows\system32\_SMSOSDSetup\TsProgressUI.exe TsProgressUI 03.05.2013 21:06:28 1876 (0x0754)
Shutdown complete. TsProgressUI 03.05.2013 21:06:28 1876 (0x0754)
Process completed with exit code 0 OSDSetupHook 03.05.2013 21:06:28 1816 (0x0718)
Successfully registered TS Progress UI. OSDSetupHook 03.05.2013 21:06:28 1816 (0x0718)
Executing command line: "C:\_SMSTaskSequence\OSD\VES00002\ccmsetup.exe" /useronly /source:C:\_SMSTaskSequence\OSD\VES00002 /config:MobileClient.TCF /status:628 OSDSetupHook 03.05.2013 21:06:28 1816 (0x0718)
Process completed with exit code 0 OSDSetupHook 03.05.2013 21:08:30 1816 (0x0718)
Start to cleanup TS policy OSDSetupHook 03.05.2013 21:08:30 1816 (0x0718)
End TS policy cleanup OSDSetupHook 03.05.2013 21:08:30 1816 (0x0718)
Active request handle is empty, registering with new active request handle. This is expected if the TS was started from a media/PXE. OSDSetupHook 03.05.2013 21:08:30 1816 (0x0718)
Saving the new active request handle for the task sequence: {B255AC1D-867D-4AEA-A804-43594334B783} OSDSetupHook 03.05.2013 21:08:30 1816 (0x0718)
Launching command shell. OSDSetupHook 03.05.2013 21:11:33 1864 (0x0748)
executing command: C:\Windows\system32\cmd.exe /k OSDSetupHook 03.05.2013 21:11:33 1864 (0x0748)
executed command: C:\Windows\system32\cmd.exe /k OSDSetupHook 03.05.2013 21:11:33 1864 (0x0748)
TS is not signaled by MTC to start. eState: 0  OSDSetupHook 03.05.2013 21:13:42 1816 (0x0718)
Failed to register task sequence with the newly installed client. (0x00000006). Continuing.. OSDSetupHook 03.05.2013 21:13:42 1816 (0x0718)
Executing command line: "C:\Windows\system32\_SMSOSDSetup\TsProgressUI.exe" /Unregister OSDSetupHook 03.05.2013 21:13:43 1816 (0x0718)
==========[ TsProgressUI started in process 1396 ]========== TsProgressUI 03.05.2013 21:13:43 1920 (0x0780)
Unregistering COM classes TsProgressUI 03.05.2013 21:13:43 1920 (0x0780)
Shutdown complete. TsProgressUI 03.05.2013 21:13:43 1920 (0x0780)
Process completed with exit code 0 OSDSetupHook 03.05.2013 21:13:43 1816 (0x0718)
Successfully unregistered TS Progress UI. OSDSetupHook 03.05.2013 21:13:43 1816 (0x0718)
Moving logs to SMS client directory OSDSetupHook 03.05.2013 21:13:43 1816 (0x0718)

Any luck with this? I am running into the same issue with SCCM 2012 SP1 now. Please share.

Thanks.

Hello

After i have cleared the Cache and resetet the Policy it have worked

Andreas

Hi Andreas,

Thanks for sharing this. Would you mind expanding a little on the resolution? What cache are you clearing? Are you resetting the client policy, and how exactly do you do that?

Thanks,

Terje

this is a bug in SCCM 2012!

check: http://techready.nl/?p=1891

• Proposed as answer by ErikVerwer Monday, April 14, 2014 8:52 AM

That link doesn't show anything - is there another url that describes the fix?