Setup windows and ConfigMgr task sequence failing.
Hi,
Am trying to create a reference Windows 7 task sequence and the task sequence is failing at the 'Setup Windows and ConfigMgr' task.
There are a lot of threads regarding this step and in particular that as the machine is in a workgroup it cannot install the SCCM client successfully. As recommended on other posts have added SMSLP= and SMSMP= into the Installation properties.
The task sequence is still failing and am unable to make much of the logs.
Will post the errors if anyone can assist?.
<![LOG[Microsoft Deployment Toolkit version: 6.1.2373.0]LOG]!><time="09:48:18.771+00" date="12-02-2013" component="InstallSoftware" context="" type="1" thread="1104" file="runcommandline.cpp:34">
<![LOG[The task sequencer log is located at X:\windows\TEMP\SMSTSLog\SMSTS.LOG. For task sequence failures, please consult this log.]LOG]!><time="09:48:18.771+00" date="12-02-2013" component="InstallSoftware" context="" type="1" thread="1104"
file="runcommandline.cpp:34">
<![LOG[Unable to copy log to the network as no SLShare value was specified.]LOG]!><time="09:48:18.771+00" date="12-02-2013" component="InstallSoftware" context="" type="1" thread="1104" file="runcommandline.cpp:34">
<![LOG[No system restore needed, WMI object not present.]LOG]!><time="09:48:18.771+00" date="12-02-2013" component="InstallSoftware" context="" type="1" thread="1104" file="runcommandline.cpp:34">
<![LOG[Cleaning up default wallpaper registry keys]LOG]!><time="09:48:18.771+00" date="12-02-2013" component="InstallSoftware" context="" type="1" thread="1104" file="runcommandline.cpp:34">
<![LOG[zticopylogs processing completed successfully.]LOG]!><time="09:48:18.771+00" date="12-02-2013" component="InstallSoftware" context="" type="1" thread="1104" file="runcommandline.cpp:34">
<![LOG[Unable to create WebService class]LOG]!><time="09:48:18.771+00" date="12-02-2013" component="InstallSoftware" context="" type="1" thread="1104" file="runcommandline.cpp:34">
<![LOG[Command line returned 0]LOG]!><time="09:48:18.771+00" date="12-02-2013" component="InstallSoftware" context="" type="1" thread="1104" file="runcommandline.cpp:565">
<![LOG[Process completed with exit code 0]LOG]!><time="09:48:18.771+00" date="12-02-2013" component="TSManager" context="" type="1" thread="1048" file="commandline.cpp:1123">
<![LOG[!--------------------------------------------------------------------------------------------!]LOG]!><time="09:48:18.771+00" date="12-02-2013" component="TSManager" context="" type="1" thread="1048" file="instruction.cxx:3012">
<![LOG[Successfully completed the action (Copy Logs) with the exit win32 code 0]LOG]!><time="09:48:18.771+00" date="12-02-2013" component="TSManager" context="" type="1" thread="1048" file="instruction.cxx:3038">
<![LOG[MP server http://UK5SYSDBPR01.s3ms.com. Ports 80,443. CRL=false.]LOG]!><time="09:48:18.771+00" date="12-02-2013" component="TSManager" context="" type="1" thread="1048" file="utils.cpp:5300">
<![LOG[Setting authenticator]LOG]!><time="09:48:18.787+00" date="12-02-2013" component="TSManager" context="" type="1" thread="1048" file="utils.cpp:5322">
<![LOG[Set authenticator in transport]LOG]!><time="09:48:18.787+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048" file="libsmsmessaging.cpp:7751">
<![LOG[Sending StatusMessage]LOG]!><time="09:48:18.787+00" date="12-02-2013" component="TSManager" context="" type="1" thread="1048" file="libsmsmessaging.cpp:4025">
<![LOG[Setting message signatures.]LOG]!><time="09:48:18.803+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048" file="libsmsmessaging.cpp:1297">
<![LOG[Setting the authenticator.]LOG]!><time="09:48:18.803+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048" file="libsmsmessaging.cpp:1327">
<![LOG[CLibSMSMessageWinHttpTransport::Send: URL: UK5SYSDBPR01.s3ms.com:80 CCM_POST /ccm_system/request]LOG]!><time="09:48:18.803+00" date="12-02-2013" component="TSManager" context="" type="1" thread="1048" file="libsmsmessaging.cpp:8621">
<![LOG[Request was succesful.]LOG]!><time="09:48:18.818+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048" file="libsmsmessaging.cpp:8956">
<![LOG[Set a global environment variable _SMSTSLastActionRetCode=0]LOG]!><time="09:48:18.818+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048" file="executionenv.cxx:668">
<![LOG[Set a global environment variable _SMSTSLastActionSucceeded=true]LOG]!><time="09:48:18.818+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048" file="executionenv.cxx:668">
<![LOG[Expand a string: %_SMSTSMDataPath%\Logs]LOG]!><time="09:48:18.818+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048" file="executionenv.cxx:782">
<![LOG[Clear local default environment]LOG]!><time="09:48:18.834+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048" file="executionenv.cxx:807">
<![LOG[Updated security on object C:\_SMSTaskSequence.]LOG]!><time="09:48:18.896+00" date="12-02-2013" component="TSManager" context="" type="1" thread="1048" file="utils.cpp:1121">
<![LOG[Set a global environment variable _SMSTSNextInstructionPointer=140]LOG]!><time="09:48:18.896+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048" file="executionenv.cxx:668">
<![LOG[Set a TS execution environment variable _SMSTSNextInstructionPointer=140]LOG]!><time="09:48:18.896+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048" file="executionenv.cxx:386">
<![LOG[Set a global environment variable _SMSTSInstructionStackString=134]LOG]!><time="09:48:18.896+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048" file="executionenv.cxx:668">
<![LOG[Set a TS execution environment variable _SMSTSInstructionStackString=134]LOG]!><time="09:48:18.896+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048" file="executionenv.cxx:414">
<![LOG[Save the current environment block]LOG]!><time="09:48:18.896+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048" file="executionenv.cxx:833">
<![LOG[Successfully save execution state and environment to local hard disk]LOG]!><time="09:48:18.943+00" date="12-02-2013" component="TSManager" context="" type="1" thread="1048" file="engine.cxx:255">
<![LOG[Start executing an instruction. Instruction name: Error in the task sequence. Instruction pointer: 140]LOG]!><time="09:48:18.959+00" date="12-02-2013" component="TSManager" context="" type="1" thread="1048" file="engine.cxx:117">
<![LOG[Set a global environment variable _SMSTSCurrentActionName=Error in the task sequence]LOG]!><time="09:48:18.959+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048" file="executionenv.cxx:668">
<![LOG[Set a global environment variable _SMSTSNextInstructionPointer=140]LOG]!><time="09:48:18.959+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048" file="executionenv.cxx:668">
<![LOG[Set a local default variable SMSTSDisableWow64Redirection]LOG]!><time="09:48:18.959+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048" file="executionenv.cxx:700">
<![LOG[Set a local default variable _SMSTSRunCommandLineAsUser]LOG]!><time="09:48:18.959+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048" file="executionenv.cxx:700">
<![LOG[Set a global environment variable _SMSTSLogPath=X:\windows\TEMP\SMSTSLog]LOG]!><time="09:48:18.959+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048" file="executionenv.cxx:668">
<![LOG[Expand a string: smsswd.exe /run: cscript "%deployroot%\scripts\ztierrormsg.wsf"]LOG]!><time="09:48:18.959+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048" file="executionenv.cxx:782">
<![LOG[Expand a string: ]LOG]!><time="09:48:18.959+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048" file="executionenv.cxx:782">
<![LOG[Command line for extension .exe is "%1" %*]LOG]!><time="09:48:18.959+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048" file="commandline.cpp:228">
<![LOG[Set command line: smsswd.exe /run: cscript "%deployroot%\scripts\ztierrormsg.wsf"]LOG]!><time="09:48:18.959+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048" file="commandline.cpp:731">
<![LOG[Start executing the command line: smsswd.exe /run: cscript "%deployroot%\scripts\ztierrormsg.wsf"]LOG]!><time="09:48:18.959+00" date="12-02-2013" component="TSManager" context="" type="1" thread="1048" file="instruction.cxx:2930">
<![LOG[!--------------------------------------------------------------------------------------------!]LOG]!><time="09:48:18.959+00" date="12-02-2013" component="TSManager" context="" type="1" thread="1048" file="instruction.cxx:2959">
<![LOG[Expand a string: WinPEandFullOS]LOG]!><time="09:48:18.959+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048" file="executionenv.cxx:782">
<![LOG[Executing command line: smsswd.exe /run: cscript "%deployroot%\scripts\ztierrormsg.wsf"]LOG]!><time="09:48:18.959+00" date="12-02-2013" component="TSManager" context="" type="1" thread="1048" file="commandline.cpp:827">
<![LOG[[ smsswd.exe ]]LOG]!><time="09:48:18.974+00" date="12-02-2013" component="InstallSoftware" context="" type="1" thread="2000" file="main.cpp:289">
<![LOG[PackageID = '']LOG]!><time="09:48:18.974+00" date="12-02-2013" component="InstallSoftware" context="" type="1" thread="2000" file="main.cpp:318">
<![LOG[BaseVar = '', ContinueOnError='']LOG]!><time="09:48:18.974+00" date="12-02-2013" component="InstallSoftware" context="" type="1" thread="2000" file="main.cpp:319">
<![LOG[ProgramName = 'cscript "C:\_SMSTaskSequence\WDPackage\scripts\ztierrormsg.wsf"']LOG]!><time="09:48:18.974+00" date="12-02-2013" component="InstallSoftware" context="" type="1" thread="2000" file="main.cpp:320">
<![LOG[SwdAction = '0001']LOG]!><time="09:48:18.974+00" date="12-02-2013" component="InstallSoftware" context="" type="1" thread="2000" file="main.cpp:321">
<![LOG[Set command line: Run command line]LOG]!><time="09:48:18.974+00" date="12-02-2013" component="InstallSoftware" context="" type="0" thread="2000" file="commandline.cpp:731">
<![LOG[Working dir 'not set']LOG]!><time="09:48:18.974+00" date="12-02-2013" component="InstallSoftware" context="" type="1" thread="2000" file="runcommandline.cpp:542">
<![LOG[Executing command line: Run command line]LOG]!><time="09:48:18.974+00" date="12-02-2013" component="InstallSoftware" context="" type="1" thread="2000" file="commandline.cpp:827">
<![LOG[Process completed with exit code 2147500037]LOG]!><time="09:48:19.037+00" date="12-02-2013" component="InstallSoftware" context="" type="1" thread="2000" file="commandline.cpp:1123">
<![LOG[Microsoft (R) Windows Script Host Version 5.8]LOG]!><time="09:48:19.037+00" date="12-02-2013" component="InstallSoftware" context="" type="1" thread="2000" file="runcommandline.cpp:34">
<![LOG[Copyright (C) Microsoft Corporation. All rights reserved.]LOG]!><time="09:48:19.037+00" date="12-02-2013" component="InstallSoftware" context="" type="1" thread="2000" file="runcommandline.cpp:34">
<![LOG[]LOG]!><time="09:48:19.037+00" date="12-02-2013" component="InstallSoftware" context="" type="1" thread="2000" file="runcommandline.cpp:34">
<![LOG[Microsoft Deployment Toolkit version: 6.1.2373.0]LOG]!><time="09:48:19.037+00" date="12-02-2013" component="InstallSoftware" context="" type="1" thread="2000" file="runcommandline.cpp:34">
<![LOG[The task sequencer log is located at X:\windows\TEMP\SMSTSLog\SMSTS.LOG. For task sequence failures, please consult this log.]LOG]!><time="09:48:19.037+00" date="12-02-2013" component="InstallSoftware" context="" type="1" thread="2000"
file="runcommandline.cpp:34">
<![LOG[ZTI deployment failed, Return Code = -2147467259 0x80004005]LOG]!><time="09:48:19.037+00" date="12-02-2013" component="InstallSoftware" context="" type="1" thread="2000" file="runcommandline.cpp:34">
<![LOG[Unable to create WebService class]LOG]!><time="09:48:19.037+00" date="12-02-2013" component="InstallSoftware" context="" type="1" thread="2000" file="runcommandline.cpp:34">
<![LOG[Command line returned 2147500037]LOG]!><time="09:48:19.037+00" date="12-02-2013" component="InstallSoftware" context="" type="1" thread="2000" file="runcommandline.cpp:565">
<![LOG[Process completed with exit code 2147500037]LOG]!><time="09:48:19.037+00" date="12-02-2013" component="TSManager" context="" type="1" thread="1048" file="commandline.cpp:1123">
<![LOG[!--------------------------------------------------------------------------------------------!]LOG]!><time="09:48:19.037+00" date="12-02-2013" component="TSManager" context="" type="1" thread="1048" file="instruction.cxx:3012">
<![LOG[Failed to run the action: Error in the task sequence.
Unspecified error (Error: 80004005; Source: Windows)]LOG]!><time="09:48:19.037+00" date="12-02-2013" component="TSManager" context="" type="3" thread="1048" file="instruction.cxx:3103">
<![LOG[MP server http://UK5SYSDBPR01.s3ms.com. Ports 80,443. CRL=false.]LOG]!><time="09:48:19.037+00" date="12-02-2013" component="TSManager" context="" type="1" thread="1048" file="utils.cpp:5300">
<![LOG[Setting authenticator]LOG]!><time="09:48:19.052+00" date="12-02-2013" component="TSManager" context="" type="1" thread="1048" file="utils.cpp:5322">
<![LOG[Set authenticator in transport]LOG]!><time="09:48:19.052+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048" file="libsmsmessaging.cpp:7751">
<![LOG[Sending StatusMessage]LOG]!><time="09:48:19.068+00" date="12-02-2013" component="TSManager" context="" type="1" thread="1048" file="libsmsmessaging.cpp:4025">
<![LOG[Setting message signatures.]LOG]!><time="09:48:19.068+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048" file="libsmsmessaging.cpp:1297">
<![LOG[Setting the authenticator.]LOG]!><time="09:48:19.068+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048" file="libsmsmessaging.cpp:1327">
<![LOG[CLibSMSMessageWinHttpTransport::Send: URL: UK5SYSDBPR01.s3ms.com:80 CCM_POST /ccm_system/request]LOG]!><time="09:48:19.068+00" date="12-02-2013" component="TSManager" context="" type="1" thread="1048" file="libsmsmessaging.cpp:8621">
<![LOG[Request was succesful.]LOG]!><time="09:48:19.083+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048" file="libsmsmessaging.cpp:8956">
<![LOG[Set a global environment variable _SMSTSLastActionRetCode=-2147467259]LOG]!><time="09:48:19.083+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048" file="executionenv.cxx:668">
<![LOG[Set a global environment variable _SMSTSLastActionSucceeded=false]LOG]!><time="09:48:19.083+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048" file="executionenv.cxx:668">
<![LOG[Clear local default environment]LOG]!><time="09:48:19.083+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048" file="executionenv.cxx:807">
<![LOG[Let the parent group (Gather Logs and StateStore on Failure) decides whether to continue execution]LOG]!><time="09:48:19.083+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048" file="instruction.cxx:3212">
<![LOG[The execution of the group (Gather Logs and StateStore on Failure) has failed and the execution has been aborted. An action failed.
Operation aborted (Error: 80004004; Source: Windows)]LOG]!><time="09:48:19.083+00" date="12-02-2013" component="TSManager" context="" type="3" thread="1048" file="instruction.cxx:2425">
<![LOG[Failed to run the last action: Error in the task sequence. Execution of task sequence failed.
Unspecified error (Error: 80004005; Source: Windows)]LOG]!><time="09:48:19.083+00" date="12-02-2013" component="TSManager" context="" type="3" thread="1048" file="engine.cxx:214">
<![LOG[MP server http://UK5SYSDBPR01.s3ms.com. Ports 80,443. CRL=false.]LOG]!><time="09:48:19.099+00" date="12-02-2013" component="TSManager" context="" type="1" thread="1048" file="utils.cpp:5300">
<![LOG[Setting authenticator]LOG]!><time="09:48:19.099+00" date="12-02-2013" component="TSManager" context="" type="1" thread="1048" file="utils.cpp:5322">
<![LOG[Set authenticator in transport]LOG]!><time="09:48:19.099+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048" file="libsmsmessaging.cpp:7751">
<![LOG[Sending StatusMessage]LOG]!><time="09:48:19.115+00" date="12-02-2013" component="TSManager" context="" type="1" thread="1048" file="libsmsmessaging.cpp:4025">
<![LOG[Setting message signatures.]LOG]!><time="09:48:19.115+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048" file="libsmsmessaging.cpp:1297">
<![LOG[Setting the authenticator.]LOG]!><time="09:48:19.115+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048" file="libsmsmessaging.cpp:1327">
<![LOG[CLibSMSMessageWinHttpTransport::Send: URL: UK5SYSDBPR01.s3ms.com:80 CCM_POST /ccm_system/request]LOG]!><time="09:48:19.115+00" date="12-02-2013" component="TSManager" context="" type="1" thread="1048" file="libsmsmessaging.cpp:8621">
<![LOG[Request was succesful.]LOG]!><time="09:48:19.146+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048" file="libsmsmessaging.cpp:8956">
<![LOG[Executing command line: X:\windows\system32\cmd.exe /k]LOG]!><time="09:48:26.618+00" date="12-02-2013" component="TSBootShell" context="" type="1" thread="744" file="bootshell.cpp:857">
<![LOG[The command completed successfully.]LOG]!><time="09:48:26.618+00" date="12-02-2013" component="TSBootShell" context="" type="1" thread="744" file="bootshell.cpp:939">
<![LOG[Successfully launched command shell.]LOG]!><time="09:48:26.618+00" date="12-02-2013" component="TSBootShell" context="" type="1" thread="744" file="bootshell.cpp:430">
<![LOG[Execution::enExecutionFail != m_eExecutionResult, HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmanager\tsmanager.cpp,866)]LOG]!><time="10:03:31.818+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048"
file="tsmanager.cpp:866">
<![LOG[Task Sequence Engine failed! Code: enExecutionFail]LOG]!><time="10:03:31.818+00" date="12-02-2013" component="TSManager" context="" type="3" thread="1048" file="tsmanager.cpp:866">
<![LOG[****************************************************************************]LOG]!><time="10:03:31.818+00" date="12-02-2013" component="TSManager" context="" type="1" thread="1048" file="tsmanager.cpp:889">
<![LOG[Task sequence execution failed with error code 80004005]LOG]!><time="10:03:31.818+00" date="12-02-2013" component="TSManager" context="" type="3" thread="1048" file="tsmanager.cpp:890">
<![LOG[Cleaning Up.]LOG]!><time="10:03:31.818+00" date="12-02-2013" component="TSManager" context="" type="1" thread="1048" file="tsmanager.cpp:637">
<![LOG[Removing Authenticator]LOG]!><time="10:03:31.818+00" date="12-02-2013" component="TSManager" context="" type="1" thread="1048" file="tsmanager.cpp:648">
<![LOG[shKey.DeleteValue( c_szRegValue_SecurityToken ), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\ccmutillib\ccmutillib.cpp,1652)]LOG]!><time="10:03:31.818+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048" file="ccmutillib.cpp:1652">
<![LOG[Cleaning up task sequence folder]LOG]!><time="10:03:31.818+00" date="12-02-2013" component="TSManager" context="" type="1" thread="1048" file="utils.cpp:1746">
<![LOG[Unable to delete file C:\_SMSTaskSequence\TSEnv.dat (0x80070005). Continuing.]LOG]!><time="10:03:32.692+00" date="12-02-2013" component="TSManager" context="" type="1" thread="1048" file="ccmfile.cpp:1056">
<![LOG[hr, HRESULT=80070091 (e:\nts_sccm_release\sms\framework\core\ccmcore\ccmfile.cpp,1218)]LOG]!><time="10:03:32.863+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048" file="ccmfile.cpp:1218">
<![LOG[Failed to delete directory 'C:\_SMSTaskSequence']LOG]!><time="10:03:32.863+00" date="12-02-2013" component="TSManager" context="" type="2" thread="1048" file="ccmfile.cpp:1218">
<![LOG[(dwRet = ::SetNamedSecurityInfoW ((WCHAR*) pszObjectName, objectType, OWNER_SECURITY_INFORMATION, pOwnerSID, NULL, NULL, NULL)) == ERROR_SUCCESS, HRESULT=80070005 (e:\nts_sccm_release\sms\framework\tscore\utils.cpp,6090)]LOG]!><time="10:03:32.863+00"
date="12-02-2013" component="TSManager" context="" type="0" thread="1048" file="utils.cpp:6090">
<![LOG[SetNamedSecurityInfo() failed.]LOG]!><time="10:03:32.863+00" date="12-02-2013" component="TSManager" context="" type="3" thread="1048" file="utils.cpp:6090">
<![LOG[SetObjectOwner() failed. 0x80070005.]LOG]!><time="10:03:32.863+00" date="12-02-2013" component="TSManager" context="" type="3" thread="1048" file="utils.cpp:6102">
<![LOG[SetObjectOwner (szFName, SE_FILE_OBJECT, c_szAdministrators), HRESULT=80070005 (e:\nts_sccm_release\sms\framework\tscore\utils.cpp,6187)]LOG]!><time="10:03:32.863+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048"
file="utils.cpp:6187">
<![LOG[RemoveFile() failed for C:\_SMSTaskSequence\TSEnv.dat. 0x80070005.]LOG]!><time="10:03:32.879+00" date="12-02-2013" component="TSManager" context="" type="3" thread="1048" file="utils.cpp:6231">
<![LOG[RemoveDirectoryW failed (0x80070091) for C:\_SMSTaskSequence]LOG]!><time="10:03:32.879+00" date="12-02-2013" component="TSManager" context="" type="2" thread="1048" file="utils.cpp:6315">
<![LOG[Deleting volume ID file C:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca ...]LOG]!><time="10:03:32.879+00" date="12-02-2013" component="TSManager" context="" type="1" thread="1048" file="resolvesource.cpp:519">
<![LOG[DeleteFileW(sVolumeIDFile.c_str()), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\resolvesource.cpp,521)]LOG]!><time="10:03:32.879+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048" file="resolvesource.cpp:521">
<![LOG[Successfully unregistered Task Sequencing Environment COM Interface.]LOG]!><time="10:03:32.879+00" date="12-02-2013" component="TSManager" context="" type="1" thread="1048" file="environmentlib.cpp:886">
<![LOG[Command line for extension .exe is "%1" %*]LOG]!><time="10:03:32.879+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048" file="commandline.cpp:228">
<![LOG[Set command line: "X:\sms\bin\x64\TsProgressUI.exe" /Unregister]LOG]!><time="10:03:32.879+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048" file="commandline.cpp:731">
<![LOG[Executing command line: "X:\sms\bin\x64\TsProgressUI.exe" /Unregister]LOG]!><time="10:03:32.879+00" date="12-02-2013" component="TSManager" context="" type="1" thread="1048" file="commandline.cpp:827">
<![LOG[==========[ TsProgressUI started in process 1728 ]==========]LOG]!><time="10:03:32.879+00" date="12-02-2013" component="TsProgressUI" context="" type="1" thread="948" file="winmain.cpp:330">
<![LOG[Command line: "X:\sms\bin\x64\TsProgressUI.exe" /Unregister]LOG]!><time="10:03:32.879+00" date="12-02-2013" component="TsProgressUI" context="" type="0" thread="948" file="winmain.cpp:332">
<![LOG[Unregistering COM classes]LOG]!><time="10:03:32.879+00" date="12-02-2013" component="TsProgressUI" context="" type="1" thread="948" file="winmain.cpp:204">
<![LOG[Unregistering class objects]LOG]!><time="10:03:32.879+00" date="12-02-2013" component="TsProgressUI" context="" type="1" thread="948" file="winmain.cpp:495">
<![LOG[Shutdown complete.]LOG]!><time="10:03:32.879+00" date="12-02-2013" component="TsProgressUI" context="" type="1" thread="948" file="winmain.cpp:512">
<![LOG[Process completed with exit code 0]LOG]!><time="10:03:32.894+00" date="12-02-2013" component="TSManager" context="" type="1" thread="1048" file="commandline.cpp:1123">
<![LOG[Successfully unregistered TS Progress UI.]LOG]!><time="10:03:32.894+00" date="12-02-2013" component="TSManager" context="" type="1" thread="1048" file="utils.cpp:2320">
<![LOG[g_TSManager.Run(), HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmanager\tsmanager.cpp,725)]LOG]!><time="10:03:32.894+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048" file="tsmanager.cpp:725">
<![LOG[::RegQueryValueExW(hSubKey, szReg, NULL, NULL, NULL, &dwSize), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\utils.cpp,261)]LOG]!><time="10:03:32.894+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048"
file="utils.cpp:261">
<![LOG[RegQueryValueExW failed for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgram]LOG]!><time="10:03:32.894+00" date="12-02-2013" component="TSManager" context="" type="2" thread="1048" file="utils.cpp:261">
<![LOG[GetTsRegValue() failed. 0x80070002.]LOG]!><time="10:03:32.894+00" date="12-02-2013" component="TSManager" context="" type="2" thread="1048" file="utils.cpp:279">
<![LOG[End program: ]LOG]!><time="10:03:32.894+00" date="12-02-2013" component="TSManager" context="" type="1" thread="1048" file="tsmanager.cpp:764">
<![LOG[Error Task Sequence Manager failed to execute task sequence. Code 0x80004005]LOG]!><time="10:03:32.894+00" date="12-02-2013" component="TSManager" context="" type="3" thread="1048" file="tsmanager.cpp:768">
<![LOG[Sending error status message]LOG]!><time="10:03:32.894+00" date="12-02-2013" component="TSManager" context="" type="1" thread="1048" file="tsmanager.cpp:769">
<![LOG[MP server http://UK5SYSDBPR01.s3ms.com. Ports 80,443. CRL=false.]LOG]!><time="10:03:32.894+00" date="12-02-2013" component="TSManager" context="" type="1" thread="1048" file="utils.cpp:5300">
<![LOG[Setting authenticator]LOG]!><time="10:03:32.910+00" date="12-02-2013" component="TSManager" context="" type="1" thread="1048" file="utils.cpp:5322">
<![LOG[Set authenticator in transport]LOG]!><time="10:03:32.910+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048" file="libsmsmessaging.cpp:7751">
<![LOG[Sending StatusMessage]LOG]!><time="10:03:32.941+00" date="12-02-2013" component="TSManager" context="" type="1" thread="1048" file="libsmsmessaging.cpp:4025">
<![LOG[Setting message signatures.]LOG]!><time="10:03:32.941+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048" file="libsmsmessaging.cpp:1297">
<![LOG[Setting the authenticator.]LOG]!><time="10:03:32.941+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048" file="libsmsmessaging.cpp:1327">
<![LOG[CLibSMSMessageWinHttpTransport::Send: URL: UK5SYSDBPR01.s3ms.com:80 CCM_POST /ccm_system/request]LOG]!><time="10:03:32.941+00" date="12-02-2013" component="TSManager" context="" type="1" thread="1048" file="libsmsmessaging.cpp:8621">
<![LOG[Request was succesful.]LOG]!><time="10:03:32.988+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048" file="libsmsmessaging.cpp:8956">
<![LOG[Finalize logging request ignored from process 1044]LOG]!><time="10:03:32.988+00" date="12-02-2013" component="TSManager" context="" type="1" thread="1048" file="tslogging.cpp:1737">
<![LOG[Process completed with exit code 2147500037]LOG]!><time="10:03:32.988+00" date="12-02-2013" component="TSMBootstrap" context="" type="1" thread="824" file="commandline.cpp:1123">
<![LOG[Task Sequence Manager returned code 0x80004005]LOG]!><time="10:03:32.988+00" date="12-02-2013" component="TSMBootstrap" context="" type="1" thread="824" file="tsmediawizardcontrol.cpp:2136">
<![LOG[ThreadToResolveAndExecuteTaskSequence returned code 0x00000000]LOG]!><time="10:03:33.004+00" date="12-02-2013" component="TSMBootstrap" context="" type="1" thread="988" file="tsmediaresolveprogresspage.cpp:221">
<![LOG[ResolveProgressPage::OnWizardNext()]LOG]!><time="10:03:33.004+00" date="12-02-2013" component="TSMBootstrap" context="" type="0" thread="988" file="tsmediaresolveprogresspage.cpp:113">
<![LOG[Activating Finish Page.]LOG]!><time="10:03:33.004+00" date="12-02-2013" component="TSMBootstrap" context="" type="0" thread="988" file="tsmediafinishpage.cpp:107">
<![LOG[Exiting with return code 0x00000000]LOG]!><time="10:03:33.004+00" date="12-02-2013" component="TSMBootstrap" context="" type="1" thread="988" file="tsmbootstrap.cpp:1195">
<![LOG[Execution complete.]LOG]!><time="10:03:33.019+00" date="12-02-2013" component="TSBootShell" context="" type="1" thread="756" file="bootshell.cpp:690">
<![LOG[hMap != 0, HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentscope.cpp,515)]LOG]!><time="10:03:33.019+00" date="12-02-2013" component="TSBootShell" context="" type="0" thread="756" file="environmentscope.cpp:515">
<![LOG[m_pGlobalScope->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,337)]LOG]!><time="10:03:33.019+00" date="12-02-2013" component="TSBootShell" context="" type="0" thread="756" file="environmentlib.cpp:337">
<![LOG[this->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,549)]LOG]!><time="10:03:33.019+00" date="12-02-2013" component="TSBootShell" context="" type="0" thread="756" file="environmentlib.cpp:549">
<![LOG[::RegQueryValueExW(hSubKey, szReg, NULL, NULL, NULL, &dwSize), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\utils.cpp,261)]LOG]!><time="10:03:33.019+00" date="12-02-2013" component="TSBootShell" context="" type="0" thread="756"
file="utils.cpp:261">
<![LOG[RegQueryValueExW failed for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgram]LOG]!><time="10:03:33.019+00" date="12-02-2013" component="TSBootShell" context="" type="2" thread="756" file="utils.cpp:261">
<![LOG[GetTsRegValue() failed. 0x80070002.]LOG]!><time="10:03:33.019+00" date="12-02-2013" component="TSBootShell" context="" type="2" thread="756" file="utils.cpp:279">
<![LOG[End program: ]LOG]!><time="10:03:33.019+00" date="12-02-2013" component="TSBootShell" context="" type="1" thread="756" file="bootshell.cpp:722">
<![LOG[Finalizing logging from process 740]LOG]!><time="10:03:33.019+00" date="12-02-2013" component="TSBootShell" context="" type="1" thread="756" file="tslogging.cpp:1741">
<![LOG[Finalizing logs to root of first available drive]LOG]!><time="10:03:33.019+00" date="12-02-2013" component="TSBootShell" context="" type="1" thread="756" file="tslogging.cpp:1583">
<![LOG[Successfully finalized logs to C:\SMSTSLog]LOG]!><time="10:03:33.035+00" date="12-02-2013" component="TSBootShell" context="" type="1" thread="756" file="tslogging.cpp:1640">
<![LOG[Cleaning up task sequencing logging configuration.]LOG]!><time="10:03:33.035+00" date="12-02-2013" component="TSBootShell" context="" type="0" thread="756" file="tslogging.cpp:584">
Similar Messages
-
Windows 7 becoming corrupt after "Setup Windows and ConfigMgr" step
Hey all,
Redid my reference images and now I got an issue with several machines I tried doing bare metal OSD on.
The TS aborts somehow, it still thinks it's running, after Setup Windows and ConfigMgr. After that step it reboots and I'm greeted with a weird Win 7 logon screen where the font kinda looks like Windings (the font folder on the machine is almost empty, that's
why).
Looked at the ccmsetup log. This error is listed: http://social.technet.microsoft.com/Forums/en-US/ee4e31cd-d456-44f4-a980-6a785d393d84/ccmsetup-failed-with-error-code-0x80040154-in-ccmsetuplog?forum=configmanagerdeployment
The log also complains about BITS, too low version to be able to install ConfigMgr. But obviously Win 7 contains BITS v 4, so I don't get what happens.
None of the apps I install in the reference image build I'm able to start (IE 10, Office apps), Office is not even listed in Add/Remove Programs.
I have redone the reference images two times, once in plain MDT 2013 and once in SCCM.
The error is inconsistent. It happens most frequently on Dell Precision T1700 machines, but not always. Sometimes there's no error when installing the ConfigMgr client and I don't get any font issues, but I still can't start Office apps or IE 10. This is driving
me mad.
ccmsetup.log and smsts.log files are here if anyone wants to take a look: http://1drv.ms/1ETazJx
Please help!You may have a similar issue we had. When we upgraded to R2, and updated our boot images from WinPE 4.0 to WinPE 5.0 we came across a bug with DISM. Our machines would get to the Setup Windows and ConfigMgr step and hang on a black screen/white cursor. After
working with Microsoft for a few weeks we found using a x64 boot image resolved our issue deploying Windows 7 x64.
Can you try recreating your x86 boot image and if that does not work try creating x64?
Daniel Ratliff | http://www.PotentEngineer.com
For me, using a x64 boot image solved the problem. Why I don't know. I created a new x64 MDT boot image and task sequence and tested all newly captured wims on several different models, with different settings, and I couldn't reproduce the problem.
Then I tested the old task sequence (basically only difference is that it uses x86 boot image) and the first deployment went fine. The next one gave me the ccmsetup/windings font error again.
Thanks for your help! I'm also very eager to hear what Microsoft came up with during your support ticket. -
OS WIM file downloads during Setup Windows and ConfigMgr
Let me start by saying, this is not the same issue as this post ;-)
http://social.technet.microsoft.com/Forums/en-US/configmgrosd/thread/58610c01-97b9-476e-9a22-fc0e31033de5
I decided to test the option in 2012 for "Apply Operating System" that allows you to run from DP (Windows 8 image). The overall Task Sequence is set to download and execute so wanted to test how much time it would save to run the Apply OS
phase from the DP. Well it didn't save any time as the step "Setup Windows and ConfigMgr" downloaded the WIM file prior to downloading the SCCM Client install files.
I double checked the source paths for my Client Package and my OS package and they do not contain one others code in them so unlike the post above its not a package source issue.
Has anyone else tried using the check box for run from DP only for apply OS? Curious if this behavior happens even without the check box and it just goes right past it and download the client files since the WIM already exists from the Apply OS phase..
When the build completes I'll start digging through log files to see if there are any clues..
Thoughts?
Thanks,
WilliamSo here's the snippet of the smsts.log showing the "Setup Windows and ConfigMgr" step downloading the Windows 8 WIM. As you can see it triggers a download of the WIM file after preparing the OSDSetupWindows.exe command line?
Doesn't seem to make sense to me since OSDSetupWindows.exe is located in the boot image (X:\sms\bin\i386\OSDSetupWindows.exe) so not sure why it triggers a WIM download..
Thoughts?
Set a global environment variable _SMSTSCurrentActionName=Setup Windows and ConfigMgr TSManager 3/20/2013 9:44:00 AM 1516 (0x05EC)
Set a global environment variable _SMSTSNextInstructionPointer=114 TSManager 3/20/2013 9:44:00 AM 1516 (0x05EC)
Set a local default variable SMSClientInstallProperties TSManager 3/20/2013 9:44:00 AM 1516 (0x05EC)
Set a local default variable _SMSClientPackageID TSManager 3/20/2013 9:44:00 AM 1516 (0x05EC)
Set a global environment variable _SMSTSLogPath=X:\WINDOWS\TEMP\SMSTSLog TSManager 3/20/2013 9:44:00 AM 1516 (0x05EC)
Expand a string: OSDSetupWindows.exe TSManager 3/20/2013 9:44:00 AM 1516 (0x05EC)
Expand a string: TSManager 3/20/2013 9:44:00 AM 1516 (0x05EC)
Command line for extension .exe is "%1" %* TSManager 3/20/2013 9:44:00 AM 1516 (0x05EC)
Set command line: OSDSetupWindows.exe TSManager 3/20/2013 9:44:00 AM 1516 (0x05EC)
Start executing the command line: OSDSetupWindows.exe TSManager 3/20/2013 9:44:00 AM 1516 (0x05EC)
!--------------------------------------------------------------------------------------------! TSManager 3/20/2013 9:44:00 AM 1516 (0x05EC)
Expand a string: WinPEandFullOS TSManager 3/20/2013 9:44:00 AM 1516 (0x05EC)
Executing command line: OSDSetupWindows.exe TSManager 3/20/2013 9:44:00 AM 1516 (0x05EC)
==============================[ OSDSetupWindows.exe ]=========================== OSDSetupWindows 3/20/2013 9:44:00 AM 1412 (0x0584)
Command line: "OSDSetupWindows.exe" OSDSetupWindows 3/20/2013 9:44:00 AM 1412 (0x0584)
ResolveSource flags: 0x00000000 OSDSetupWindows 3/20/2013 9:44:00 AM 1412 (0x0584)
SMSTSPersistContent: . The content for package P10000BB will be persisted OSDSetupWindows 3/20/2013 9:44:00 AM 1412 (0x0584)
DownloadOnDemand flag is true. Attempting to download content locally for Package P10000BB.. OSDSetupWindows 3/20/2013 9:44:00 AM 1412 (0x0584)
Package Flags: 0x1000080 OSDSetupWindows 3/20/2013 9:44:00 AM 1412 (0x0584)
GetDirectoryListing() entered OSDSetupWindows 3/20/2013 9:44:00 AM 1412 (0x0584)
Initializing HTTP transport. OSDSetupWindows 3/20/2013 9:44:00 AM 1412 (0x0584)
Setting URL =
http://MYSCCMSERVER.mydomain.com/SMS_DP_SMSPKG$/P10000BB. OSDSetupWindows 3/20/2013 9:44:00 AM 1412 (0x0584)
Address=http://MYSCCMSERVER.mydomain.com, Scheme=http, Object=/SMS_DP_SMSPKG$/P10000BB, Port=80. OSDSetupWindows 3/20/2013 9:44:00 AM 1412 (0x0584)
Setting Authenticator. OSDSetupWindows 3/20/2013 9:44:00 AM 1412 (0x0584)
Set authenticator in transport OSDSetupWindows 3/20/2013 9:44:00 AM 1412 (0x0584)
WinHttp credentials set OSDSetupWindows 3/20/2013 9:44:00 AM 1412 (0x0584)
CLibSMSMessageWinHttpTransport::Send: URL: MYSCCMSERVER.mydomain.com:80 PROPFIND /SMS_DP_SMSPKG$/P10000BB OSDSetupWindows 3/20/2013 9:44:00 AM 1412 (0x0584)
401 - Authentication failure on request with anonymous access, retrying with context credentials. OSDSetupWindows 3/20/2013 9:44:00 AM 1412 (0x0584)
Using thread token for request OSDSetupWindows 3/20/2013 9:44:00 AM 1412 (0x0584)
401 - Authentication failure on request with context credentials, retrying with supplied credentials. OSDSetupWindows 3/20/2013 9:44:00 AM 1412 (0x0584)
Request was succesful. OSDSetupWindows 3/20/2013 9:44:00 AM 1412 (0x0584)
DAV response string is:
<?xml version="1.0" encoding="utf-8" ?><D:multistatus xmlns:D="DAV:"><D:response><D:href>http://MYSCCMSERVER.mydomain.com/SMS_DP_SMSPKG$/sccm?/P10000BB/</D:href><D:propstat><D:status>HTTP/1.1
200 OK</D:status><D:prop><D:getcontenttype/><D:supportedlock/><D:getetag/><D:creationdate/><D:iscollection>1</D:iscollection><D:resourcetype><D:collection/></D:resourcetype><D:ishidden>0</D:ishidden><D:displayname>http://MYSCCMSERVER.mydomain.com/SMS_DP_SMSPKG$/sccm?/P10000BB/</D:displayname><D:getlastmodified></D:getlastmodified><D:getcontentlanguage/><D:getcontentlength>0</D:getcontentlength></D:prop></D:propstat></D:response><D:response><D:href>http://MYSCCMSERVER.mydomain.com/SMS_DP_SMSPKG$/P10000BB/sccm?/FB_Win8RTM_x64_R03.wim</D:href><D:propstat><D:status>HTTP/1.1
200 OK</D:status><D:prop><D:getcontenttype/><D:lockdiscovery/><D:supportedlock/><D:getetag/><D:getcontentlanguage/><D:iscollection>0</D:iscollection><D:creationdate/><D:resourcetype/><D:ishidden>0</D:ishidden><D:displayname>http://MYSCCMSERVER.mydomain.com/SMS_DP_SMSPKG$/P10000BB/sccm?/FB_Win8RTM_x64_R03.wim</D:displayname><D:getlastmodified>Fri,
08 Mar 2013 16:21:22 GMT</D:getlastmodified><D:getcontentlength>6253977862</D:getcontentlength></D:prop></D:propstat></D:response></D:multistatus> OSDSetupWindows 3/20/2013 9:44:00 AM 1412 (0x0584)
List of files to be downloaded OSDSetupWindows 3/20/2013 9:44:00 AM 1412 (0x0584)
File:
http://MYSCCMSERVER.mydomain.com:80/SMS_DP_SMSPKG$/P10000BB/sccm?/FB_Win8RTM_x64_R03.wim OSDSetupWindows 3/20/2013 9:44:00 AM 1412 (0x0584)
GetDirectoryListing() successfully completed OSDSetupWindows 3/20/2013 9:44:00 AM 1412 (0x0584)
Succeeded loading resource DLL 'X:\sms\bin\i386\1033\TSRES.DLL' OSDSetupWindows 3/20/2013 9:44:00 AM 1412 (0x0584)
401 - Authentication failure on request with anonymous access, retrying with context credentials. OSDSetupWindows 3/20/2013 9:44:00 AM 1412 (0x0584)
401 - Authentication failure on request with context credentials, retrying with supplied credentials. OSDSetupWindows 3/20/2013 9:44:00 AM 1412 (0x0584)
Downloaded file from
http://MYSCCMSERVER.mydomain.com:80/SMS_DP_SMSPKG$/P10000BB/sccm?/FB_Win8RTM_x64_R03.wim to D:\_SMSTaskSequence\Packages\P10000BB\FB_Win8RTM_x64_R03.wim OSDSetupWindows 3/20/2013 9:48:09 AM 1412 (0x0584)
Download done setting progress bar to 100 OSDSetupWindows 3/20/2013 9:48:09 AM 1412 (0x0584) -
Setup Windows and ConfigMgr - OSD Step clarification
Hi,
I am trying to configure the step "Setup Windows and ConfigMgr" and trying to understand the properties in
SCCM 2012 SP1.
If I refer to the following:
About Client Installation Properties in Configuration Manager
http://technet.microsoft.com/en-us/library/gg699356.aspx
It seems there are two types of properties. Those honoured by CCMSetup command line properties and the client.msi properites.
So here are my questions:
1. Which settings does the task sequence follow? For example if I want to set the ManagementPoint do I do:
/mp:<Computer> or SMSMP=?
2. Also I would like to handle being able to deploy the cumlative update.
http://chriscrampton.blogspot.com.au/2013/10/include-cumulative-update-or-patch-in.html
If I look through this article it has the line PATCH=......
However on the page:
About Client Installation Properties in Configuration Manager
http://technet.microsoft.com/en-us/library/gg699356.aspx
it makes no mention of this command line.
So been a long day - and I might of missed something obvious :)
So any advice greatly appreciated.
Thanks,
Ward.A couple of follow-on points here:
- First, a semantic note. Options on the command-line prefixed by a forward slash are parameters (not properties) and are used by ccmsetup.exe to download necessary files and initiate their installation. Options in all caps are Windows Installer properties
passed to client.msi when setting up the ConfigMgr client agent. Thus you can pass any property that is valid for the client.msi like PATCH as that's a universal Windows Installer property.
- As indicated in the documentation you linked to, /mp and SMSMP are two completely different options that do two completely different things. In short /mp does not set the MP: http://blog.configmgrftw.com/ccmsetup-mp-and-smsmp/. Thus choosing which to use
should fit what you are trying to do. From memory, you can't specify parameters in that task though (although I think that may have changed); however, even if you can, /mp is useless because content download and staging is already part of what the TS does.
Jason | http://blog.configmgrftw.com -
SCCM 2012 client in capture but deploy has default step "Setup Windows and ConfigMgr"
Hi,
We have our SCCM 2012 client in the capture but the deploy has a single step "Setup Windows and ConfigMgr" in which there is no option to NOT install the sccm 2012 client.
So what happens then, the client is installed a second time?
Please advise.
J.
Jan HoedtHello !
This is a mandatory step in order to configure Windows for a first use. In your case, the SCCM client will just be serialized, it's not a problem. The SCCM client has generally been prepared during the design capture.
Hope this helps.
Note: This posting is provided 'AS IS' with no warranties or guarantees, and confers no rights. Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable. This helps the community, keeps the forums tidy, and
recognises useful contributions. -
Task sequences won't run after "Setup Windows and ConfigMgr"
In my Task Sequence for SCCM 2012 R2, no task sequences that occur after the "Setup Windows and Configuration Manager" step will run if I add to the Installation properties:
PATCH="\\server.domain.com\D$\SMSPKGSIG\PHX00033.2\configmgr2012ac-r2-kb2905002-x64.msp"
I believe this hotfix is necessary because I had to install on the server to fix the speed of downloading the WIM file. And I believe it says I need to append this PATH= switch to the install.
Is my path used incorrectly or something? Because that is the actual path to the file.
My task sequences will run fine if I remove it and just leave the SMSMP=server.domain.com in the install properties.Your path would then be :
PATCH="C:\_SMSTaskSequence\OSD\JJJ00033.2\configmgr2012ac-r2-kb2905002-x64.msp"
I suggest that you plan for further patches. Create a directory with all your future hotfix in it.
Ex: D:\SCCMHotFixes\KBNumber\x64
Your "Patch" parameter will grow over time, when a new hotfix will be release, you'll need
to add it after this one and so on...
I always use the _SMSTSDataPath without any problem, you could also try this.
PATCH=""%_SMSTSMDataPath%\OSD\JJJ00033.2\configmgr2012ac-r2-kb2905002-x64.msp"
Benoit Lecours | Blog: System Center Dudes -
Build and Capture task sequence fails at 'Prepare ConfigMgr Client for Capture' step
The scenario is as follows:
Task Sequence is a Build and Capture of Windows 7 SP1 x64 Enterprise
There are 17 Applications installed split into 2 'Install Application' steps due to the 9 item limit
129 Software Updates are installed
SCCM 2012 RTM
I have built and captured on this system previously however there were no 'applications', just traditional SCCM 'packages'
All task sequence steps run successfully until it gets to the 'Prepare ConfigMgr Client for Capture' step and it fails here. Here are the relevant parts of the SMSTS.log file:
<![LOG[No certificates to delete]LOG]!><time="15:30:12.531-660" date="11-13-2012" component="PrepareSMSClient" context="" type="1" thread="2880" file="preparesmsclient.cpp:1013">
<![LOG[Deleting Client properties from file C:\Windows\SMSCFG.INI succeeded.]LOG]!><time="15:30:12.531-660" date="11-13-2012" component="PrepareSMSClient" context="" type="1" thread="2880" file="preparesmsclient.cpp:922">
<![LOG[Reseting the Trusted Root Key successful]LOG]!><time="15:30:12.531-660" date="11-13-2012" component="PrepareSMSClient" context="" type="1" thread="2880" file="preparesmsclient.cpp:1088">
<![LOG[Deleting instance of 'CCM_Client' successful]LOG]!><time="15:30:12.531-660" date="11-13-2012" component="PrepareSMSClient" context="" type="1" thread="2880" file="preparesmsclient.cpp:170">
<![LOG[Successfully reset Registration status flag to "not registered"]LOG]!><time="15:30:12.531-660" date="11-13-2012" component="PrepareSMSClient" context="" type="1" thread="2880" file="preparesmsclient.cpp:309">
<![LOG[Successfully disabled provisioning mode.]LOG]!><time="15:30:12.546-660" date="11-13-2012" component="PrepareSMSClient" context="" type="1" thread="2880" file="preparesmsclient.cpp:1273">
<![LOG[Start to cleanup TS policy]LOG]!><time="15:30:12.546-660" date="11-13-2012" component="PrepareSMSClient" context="" type="0" thread="2880" file="utils.cpp:2773">
<![LOG[getPointer()->ExecQuery( BString(L"WQL"), BString(pszQuery), lFlags, pContext, ppEnum ), HRESULT=ffffffff (e:\nts_sccm_release\sms\framework\core\ccmcore\wminamespace.cpp,389)]LOG]!><time="15:35:21.000-660" date="11-13-2012" component="PrepareSMSClient"
context="" type="0" thread="2880" file="wminamespace.cpp:389">
<![LOG[ns.Query(sQuery, &spEnum), HRESULT=ffffffff (e:\nts_sccm_release\sms\framework\tscore\utils.cpp,2800)]LOG]!><time="15:35:21.000-660" date="11-13-2012" component="PrepareSMSClient" context="" type="0" thread="2880" file="utils.cpp:2800">
<![LOG[Wmi query 'select * from CCM_Policy where PolicySource = 'CcmTaskSequence'' failed, hr=0xffffffff]LOG]!><time="15:35:21.000-660" date="11-13-2012" component="PrepareSMSClient" context="" type="3" thread="2880" file="utils.cpp:2800">
<![LOG[End TS policy cleanup]LOG]!><time="15:35:21.000-660" date="11-13-2012" component="PrepareSMSClient" context="" type="0" thread="2880" file="utils.cpp:2821">
<![LOG[TS::Utility::CleanupPolicyEx(false), HRESULT=ffffffff (e:\nts_sccm_release\sms\client\osdeployment\preparesmsclient\preparesmsclient.cpp,457)]LOG]!><time="15:35:21.000-660" date="11-13-2012" component="PrepareSMSClient" context="" type="0" thread="2880"
file="preparesmsclient.cpp:457">
<![LOG[Failed to delete policies compiled by TaskSequence (0xffffffff)]LOG]!><time="15:35:21.000-660" date="11-13-2012" component="PrepareSMSClient" context="" type="3" thread="2880" file="preparesmsclient.cpp:457">
<![LOG[Failed to prepare SMS Client for capture, hr=ffffffff]LOG]!><time="15:35:21.000-660" date="11-13-2012" component="PrepareSMSClient" context="" type="3" thread="2880" file="preparesmsclient.cpp:472">
<![LOG[pCmd->Execute(), HRESULT=ffffffff (e:\nts_sccm_release\sms\client\osdeployment\preparesmsclient\main.cpp,136)]LOG]!><time="15:35:21.000-660" date="11-13-2012" component="PrepareSMSClient" context="" type="0" thread="2880" file="main.cpp:136">
<![LOG[Failed to prepare SMS Client for capture, hr=ffffffff]LOG]!><time="15:35:21.000-660" date="11-13-2012" component="PrepareSMSClient" context="" type="3" thread="2880" file="main.cpp:136">
<![LOG[Process completed with exit code 4294967295]LOG]!><time="15:35:21.015-660" date="11-13-2012" component="TSManager" context="" type="1" thread="2152" file="commandline.cpp:1098">
<![LOG[!--------------------------------------------------------------------------------------------!]LOG]!><time="15:35:21.015-660" date="11-13-2012" component="TSManager" context="" type="1" thread="2152" file="instruction.cxx:3011">
<![LOG[Failed to run the action: Prepare ConfigMgr Client for Capture.
Unknown error (Error: FFFFFFFF; Source: Unknown)]LOG]!><time="15:35:21.046-660" date="11-13-2012" component="TSManager" context="" type="3" thread="2152" file="instruction.cxx:3102">
It looks like there is a similar issue over here (http://www.windows-noob.com/forums/index.php?/topic/5906-task-sequence-error-0xffffffff/) that was resolved by removing the Application Installations one by one until a problematic one was found
and removed - however I would rather avoid this very time consuming process if possible.
I have also testing this using 'capture media' in the full OS and that also fails at the same step with the same errors in the smsts.log
The only workaround I have for now is to let the task sequence fail at the 'Prepare ConfigMgr Client for Capture' step, then I uninstall the SCCM client using 'ccmsetup.exe /uninstall' and use the 'capture media' method - obviously with no SCCM client installed,
it skips the 'Prepare ConfigMgr Client for Capture' step and goes straight to the 'Prepare OS' step and then to the actual capture to the WIM step.
Anybody else seeing this or have any suggestions?
My Microsoft Core Infrastructure & Systems Management blog -
blog.danovich.com.auIt looks like there is a similar issue over here (http://www.windows-noob.com/forums/index.php?/topic/5906-task-sequence-error-0xffffffff/) that was resolved by removing the Application Installations one by one until a problematic one was found
and removed - however I would rather avoid this very time consuming process if possible.
You dont have to test it 18 times....
Just test with 50% of the applications first, if it fails, test with 25% and then on of the time...
You should be able to find the application, within 4-5 tests...
Ronni Pedersen | Microsoft MVP - ConfigMgr | Blogs:
http://www.ronnipedersen.com/ and SCUG.dk/ | Twitter
@ronnipedersen -
Sysprep and Capture Task Sequence Fails "Can not find script file C:\LTIBootstrap.vbs"
I've just installed Windows 8 on a Lenovo ThinkPad T440s using Lenovo's recovery discs. I did not join it to a domain. I logged in as Administrator, navigated to our deployment share, and ran Scripts\LiteTouch.wsf. I selected the new Sysprep and Capture
Task Sequence that I just made, told it to upload to DeploymentShare$\Captures, then started the Task Sequence.
It seemed to run fine until after the first reboot. Windows 8 configured the PC for a while, then displayed an error that it had been shut down unexpectedly. I wasn't sure if this was normal, so I just clicked OK. Then I got an error that said "Can
not find script file C:\LTIBootstrap.vbs". After clicking OK on that, I am brought to the desktop.
The image cannot be found in DeploymentShare$\Captures. Under the Monitoring section of the DeploymentWorkbench, I can see that MDT thinks the Task Sequence is still running on the machine (though it is not), with progress stuck on step 16 of 23: Execute
Sysprep. There are 0 errors and 0 warnings listed.
BDD.log is too long to post all of it, but here's the last few lines in case that's helpful.
<![LOG[BCD> The operation completed successfully.]LOG]!><time="11:20:35.000+000" date="12-26-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[BCDEdit returned ErrorLevel = 0]LOG]!><time="11:20:35.000+000" date="12-26-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Run Command: C:\windows\SYSTEM32\bcdedit.exe /default {d22e7e91-9ee7-46eb-89d7-c5859e4302f0}]LOG]!><time="11:20:35.000+000" date="12-26-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[BCD> The operation completed successfully.]LOG]!><time="11:20:35.000+000" date="12-26-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[BCDEdit returned ErrorLevel = 0]LOG]!><time="11:20:36.000+000" date="12-26-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Property BootPE is now = True]LOG]!><time="11:20:36.000+000" date="12-26-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[LTI Windows PE applied successfully]LOG]!><time="11:20:36.000+000" date="12-26-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Event 41019 sent: LTI Windows PE applied successfully]LOG]!><time="11:20:36.000+000" date="12-26-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[LTIApply processing completed successfully.]LOG]!><time="11:20:36.000+000" date="12-26-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Event 41001 sent: LTIApply processing completed successfully.]LOG]!><time="11:20:36.000+000" date="12-26-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
I would greatly appreciate any assistance determining what went wrong and how to correct it. Thank you.You might get teh c:\LTIBootStrap.vbs error if you are running SysPrep with a unattend.xml template that contains the c:\bootstrap.vbs template, yet you are *NOT* deploying the image with MDT Litetouch, instead just applying the image to the final machine.
Crack open your install.wim file and search for the unattend.xml file in the normal places to see what it is.
I am concerned about the "shut down unexpectedly" error. There should be no shutdown state information left from a captured *.wim file.
If you still need assistance, please feel free to copy the bdd.log file to a public site like OneDrive, and share the link.
Keith Garner - Principal Consultant [owner] -
http://DeploymentLive.com -
Setup Windows and ConfigMgr step doesnt run, shows 'in progress' indefinately
Hi
We have a new SCCM 2012R2 CU3 infrastructure in place and just trying to get OSD working with our existing images, on Dell OptiPlex 980/990 models. I have created a basic task sequence from the wizard and imported our images (windows 7 x64, created
with imagex). The task sequence applies the image and drivers, but then doesn't finish the task sequence. Instead, it reboots, runs the mini setup, reboots twice more and returns to the CTRL ALT DEL prompt. The smsts log shows no errors, and the console
just sits there with the client stuck in 'in progress'. There are no ccmsetup logs in C:\Windows, so the setup didn't start. The files are downloaded successfully however. This is on an image that has never had the ConfigMgr client installed, but I have also
tried capturing the image with a manual client install and deploying that. When that image starts, the task sequence also doesn't finish and the SMS Agent Host service is disabled.
Below is a list of things I have tried:
removing all unattend.xml files from the win7 image
removing all 3rd party drivers from the win7 image
adding all drivers to the boot image
removing all drivers from the boot image
adding all drivers to the 990 driver package
removing all drivers from the 990 driver package
adding just disk and network drivers to the 990 package
adding chipset drivers to the 990 package
deselecting migrate system time in the task sequence
using the RTM client with the PATCH command switch for the CU3 update
Forcing install onto C drive
deleting boot partition from task sequence and creating single boot partition at 100% space
entering the Win7 Pro KMS key into the task sequence
Using the SMSMP= switch in the client installation properties with the %_SMSTSMDataPath% variable
Using the SMSMP= switch in the client installation properties with the C:\_SMSTS folder
removing the scripts directory from c:\windows\setup from the win7 image
replacing apply driver package step in task sequence with auto apply, limited to 980 category, which only contains nic driver
tried manually installing agent, capturing via task sequence and redeploying
Nothing seems to work. Ive even tried deploying Windows 7 SP1 from the media ISO, this also has the same problem. I have used F8 and open a CMD prompt to verify the machine has an IP and can see its storage in WinPE, so I don't think it is a driver issue.
Ive also tried multiple combinations of all drivers versus no drivers in both the boot image and driver package.
I cant upload the log file as we restrict file sharing sites here, but I can paste in certain sections if it helps (the file is over 1MB)
ThanksIm resurrecting this again, the issue seemed to be rectified on the VM capture, but has now resurfaced on a Hybrid image which is based on this image. We have 2 hybrids, the base image which is a vanilla install, customizations such as company background,
.Net 4.5.1, Silverlight, VC++ runtimes, AV, IE10... Then the big hybrid which is based on this, which contains all LOB apps.
So, the flow is like this, with each step being the basis for the next image/task sequence:
Win7 x64 SP1 media install in Task Sequence - WORKS
VM capture, with all outstanding Windows patches - WORKS
Base Hybrid Image, .Net 4.5.1, Silverlight, VC++ runtimes, AV, IE10 - WORKS
Fat Hybrid 1, LOB apps with Office 2003 - DOESNT WORK
Fat Hybrid 2, LOB apps with Office 2013 - DOESNT WORK
Ive gone through and verified all images have the latest binaries for CU3 2012 (version *.1401). Ive also tried to take off all AV (actually, I didn't even install it, is more accurate) before image capture, just in case this is stopping the TS from
completing. This issue is happening on both virtual and physical, which leads me to suspect drivers are not the cause.
So far, Ive come up with the possible causes:
Driver (less likely, images seem to work/not work regardless of hardware)
Software
AV (did not make a difference)
Number of activations (less likely, new fat image built from vmcapture2, rather than base image - still doesn't work)
Customizations/background (less likely, base image has customizations/background and works)
Im disabling the application install steps one by one in the capture TS to see if I can identify an application that is causing this. I have also looked through the list of hotfixes to see if this is a known issue or has a fix:
http://social.technet.microsoft.com/wiki/contents/articles/9539.sccm-2012-list-of-public-microsoft-support-knowledge-base-articles.aspx
I also have the dism and smsts logs from a broken 'fat' hybrid TS and a working base hybrid ts and will
compare them.
Really tricky issue. -
Task sequence fails after upgrading to 2012 R2 and MDT 2013
After upgrading to 2012 R2, my task sequence fails after the Setup Windows and ConfigMGR & Restart Computer. Instead of continuing to run the task sequence and load up the MDT Toolkit Package, it just stops at the Windows 7 login screen.
Do I need to create new toolkit & settings packages with MDT 2013 settings? Or do I just need to create a new task sequence?
I can't figure out what log to look at on the VM that I am imaging. If someone can point it out maybe there's some useful information. Thanks.
My task sequenceIt sounds a lot like that it could be failing at the client installation. Please take a look at the client installation logs.
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude
Here are the log files from c:\windows\ccmsetup\logs .. I took a glance and things run with success 0 which should mean no error right? The system also has the client installed with the CU2 patch.
Client Logs
Searched a bit online and people are saying it's due to the incorrect boot image. I was using a WinPE 5.0 I created on this TS but I'm going to make another and see where it goes.
This was the solution. -
OSD task sequence fails to install application on workgroup computers
Environment:
Windows Server 2008 R2 Standard, SP1
SCCM 2012 R2
Issue:
OSD TS fails to install applications from local DP on Windows 8.1 x86 workgroup computers. Same applications install fine from OSD/TS on domain computers. A standard push installs fine when deployed outside of OSD/TS to workgroup, or domain computer.
- “SMSMP=managementpoint.domain.com” is included in ‘Setup Windows and ConfigMgr’ installation poperties
- “Allow clients to connect anonymously” enable on DP system role, HTTP client communication
- Network Access Account is configured and authentication is confirmed
- Have confirmed no overlapping boundaries
- IIS anonomys and Windows authentication is enabled for SMS_DP_SMSPKG$, anon authentication creds set to "Specific user: IUSR"
After OSD deployment to workgroup computer completes -
AppEnforce.log is missing
smsts.log
App install failed.
Setting TSEnv variable '_TSAppInstallStatus'='Error'
Setting TSEnv variable 'SMSTSInstallApplicationJobID__ScopeId_93E0532F-C5CA-4078-AE13-2BF543602863/Application_486d99ca-817a-4600-889e-50f8e4f91592'=''
Completed installation job.
Step 3 out of 3 complete
Install application action failed: 'Microsoft_Office_Professional_2013_v15.0.4420.1017_CA-copy'. Error Code 0x80004005
CITaskMgr.log
State transition to (Failure), Error(0x87d00222) : CITask(ScopeId_93E0532F-C5CA-4078-AE13-2BF543602863/DeploymentType_f7f47522-3654-43b0-95ef-55198d957bdf.8..Install.ContentDownload)
Initiating task ContentDownload for CI ScopeId_93E0532F-C5CA-4078-AE13-2BF543602863/DeploymentType_5982c24d-07f4-4121-8aa4-4f65a8b7aeb6.15 (Microsoft_Office_Professional_2013_v15.0.4420.1017_CA_x86_P_PW) for target: , consumer: {634F5894-5AB1-4D48-83F7-603E94FE1F3F}
Initiating content download : CITask(ScopeId_93E0532F-C5CA-4078-AE13-2BF543602863/DeploymentType_5982c24d-07f4-4121-8aa4-4f65a8b7aeb6.15..Install.ContentDownload)
State transition to (InProgress), Param(0) : CITask(ScopeId_93E0532F-C5CA-4078-AE13-2BF543602863/DeploymentType_5982c24d-07f4-4121-8aa4-4f65a8b7aeb6.15..Install.ContentDownload)
State transition to (InProgress), Param(0) : CTaskConsumer(ScopeId_93E0532F-C5CA-4078-AE13-2BF543602863/DeploymentType_5982c24d-07f4-4121-8aa4-4f65a8b7aeb6.15.{CC8A099F-8EC4-4484-9191-53FFC1775D18})
Successfully initiated contents download request {5237AC77-651A-4723-AF91-78A1C0497DBD} : CITask(ScopeId_93E0532F-C5CA-4078-AE13-2BF543602863/DeploymentType_5982c24d-07f4-4121-8aa4-4f65a8b7aeb6.15..Install.ContentDownload)
Release task ContentDownload for CI ScopeId_93E0532F-C5CA-4078-AE13-2BF543602863/DeploymentType_5982c24d-07f4-4121-8aa4-4f65a8b7aeb6.15 for target: , consumer {634F5894-5AB1-4D48-83F7-603E94FE1F3F}
Release task ContentDownload for CI ScopeId_93E0532F-C5CA-4078-AE13-2BF543602863/Application_486d99ca-817a-4600-889e-50f8e4f91592.22 for target: , consumer {502180D3-CA3B-4657-AD32-D43F952A6576}
Release task ContentDownload for CI ScopeId_93E0532F-C5CA-4078-AE13-2BF543602863/RequiredApplication_486d99ca-817a-4600-889e-50f8e4f91592.22 for target: , consumer {1A485BC4-DD0C-4659-B034-8D7F9B436B3A}
State transition to (Failure), Error(0x87d00222) : CITask(ScopeId_93E0532F-C5CA-4078-AE13-2BF543602863/DeploymentType_5982c24d-07f4-4121-8aa4-4f65a8b7aeb6.15..Install.ContentDownload)
ContentTransferManager.log
CTM job {1964A4E6-DC01-4A04-983D-AAFD5FB2CA5E} (corresponding DTS job {901A1D57-D363-45FE-A4F4-8509F5556D53}) started download from 'http://HOUMGMT49.APACHECORP.COM/SMS_DP_SMSPKG$/Content_ed232f49-224b-48cc-9c01-0ff31bae851e.1' for full content download.
CTM job {1964A4E6-DC01-4A04-983D-AAFD5FB2CA5E} entered phase CCM_DOWNLOADSTATUS_DOWNLOADING_DATA
CTM job {1964A4E6-DC01-4A04-983D-AAFD5FB2CA5E} entered phase CCM_DOWNLOADSTATUS_DOWNLOADING_DATA
CTM job {1964A4E6-DC01-4A04-983D-AAFD5FB2CA5E} entered phase CCM_DOWNLOADSTATUS_DOWNLOADING_DATA
CTM job {1964A4E6-DC01-4A04-983D-AAFD5FB2CA5E} entered phase CCM_DOWNLOADSTATUS_DOWNLOADING_DATA
CTM encountered error processing reply from DTS. Code 0x87d00215
Cancelled CTM job {1964A4E6-DC01-4A04-983D-AAFD5FB2CA5E}
Two workarounds below (Not acceptable solutions)
*I can add a pause script after Setup Windows and ConfigMgr sequence, wait 5-10 minutes and the applications will install. I assume this is because the CM client has time to fully provision.
* I can add the anon ‘IUSR’ account to the local administrators group on the DP and all applications install (without the pause script mentioned above). I can reproduce the issue repeatedly by removing and adding the anon account.
Any help with this would be greatly appreciated…
Also, I come from a CM 2007 background and somewhat new to CM 2012. Should WebDAV and/or URL Authorization be installed and configured on the DP? According to MS tech support “No”. However, I’ve seen several SCCM 2012 guides on the web that say it should
be installed.
Regards
David K. HarrisonLocationservices.log, CIDownloader.log, CIagent.log, DataTransferService.log also need to be checked. We need to find out what credential the Client trys to use when it downloads content from DP.
Juke Chou
TechNet Community Support -
Build & capture task sequence fails during software update installation
I'm sure this has been discussed a thousand times already, so I hope no one minds talking about it at least one more time. About 6 months ago I created a reference image using a build and capture task sequence within SCCM. After discovering
there were certain updates that would kill a task sequence (because they required multiple restarts), I was able to exclude these updates from deployment so that my task sequence completed successfully. Fast forward to today. I'm working on updating
our reference image to include the last 6 months of updates. Again, I'm having trouble with the task sequence failing to complete. I have excluded all of the updates mentioned in
Microsoft KB article 2894518. I'm able to build the image with all software updates up until 6/30/2014. When I deploy my software group that contains updates from 7/1/2014 to 12/31/2014,
however, the task sequence fails. I'm pulling my hair out trying to figure out which update may be causing the issue, and trust me, I don't have much hair as it is. So, here's my question to all of the experts out there. What is the best
method of debugging this issue and finding which update may be the culprit? The log files really are confusing, so I'm hoping there are some common codes or phrases I can search for within those files. Any and all help is much appreciated. Thanks...> I'm working on updating our reference image to include the last 6 months of updates.
Since this is a Build & Capture task sequence and not joined to the domain, you'll need to treat it
like a workgroup computer. Here are the big three things that usually trip things up:
1. Initial Management Point: The Setup Windows and ConfigMgr step should have the SMSMP=<fqdn>
property specified, as the device won't be able to see the list of MP's in Active Directory
2. Content Location: Make sure the reference machine's IP address falls within an IP Range
or Subnet ID boundary, since it can't use a AD Site boundary as a workgroup machine.
3. Win 7 - NTLM Fallback: Windows 7 devices may need
hotfix KB2522623 installed (as a package/program or with offline servicing) to ensure they fall back to NTLM properly when they fail to authenticate with Kerberos.
If you have those 3 things taken care of, then you should copy all the logs off of the machine while the
error message is still being displayed, zip them, and then share them out through OneDrive or Dropbox.
I hope that helps,
Nashs
Nash Pherson, Senior Systems Consultant
Now Micro -
My Blog Posts
If you found a bug or want the product to work differently,
share your feedback.
<-- If this post was helpful, please click the up arrow or propose as answer. -
Windows 7 64bit Build and Capture Task Sequence keeps failing. Need to Offline Patch
Hi All,
I have been having problems running my SCCM 2007 R3 Build and Capture Task Sequence for Windows 7 64bit since MS released the October 2014 patches. (Having problems described in KB2894518, but can't get workaround to work)
So my next step is to try to apply the patches directly to the install.wim file using dism and "Offline Servicing". I'm hoping this will allow my TS to finish, and also adds the benifit of making my TS much faster to run every month. So I followed
the steps in
this post, and injected 165 updates into the install.wim file (extracted from Win7 ISO). Now, I've copied the updated WIM into my Operating System install package and updated the distribution point. But the Install Software Updates step still installs 160
updates (same as before the Offline patch injection). The only thing that seems faster is that the download of the updates is instantaneous. So it seems like the Offline patch injection just copied the patch installer files to the WIM, but did not actually
install them.
I remember reading a post by Niall C. Brady or Jason Sandys about exactly how they inject patches into a WIM, but have been unable to re-locate the post. Does anybody out there have a tried and true method for offline injection of patches into install.wim
for use with SCCM Build and Capture task sequence? thanks!My recommendation would be to use MDT to build your images instead:
http://technet.microsoft.com/en-us/library/dn744290.aspx
This will make your life much easier with the patching of the image :)
You can use Nickolaj's great MDT Factory tool to set up an MDT Build machine from scratch:
https://gallery.technet.microsoft.com/MDT-Factory-Tool-100-8e68123b
Blog: www.danielclasson.com/blog |
LinkedIn:
Daniel Classon | Twitter: @danielclasson -
OSD Task Sequence fails to install SCCM client
Hello,
Our OSD task sequence fails to install the SCCM client with certain images.
The TS gets to the "Setup Windows and Configuration" step, during which it downloads all the necessary SCCM client files (silverlight, C++ redistributable, client.msi....etc.). At this point computer restarts and in never loads back into the
task sequence, instead it enters the minisetup (setup is starting services, setup is installing devices, setup is applying system settings...preparing computer for first use), after which the computer restarts and you are back at the CTR+ALT+Del screen.
The computer has joined the domain and has run all other steps but it has failed to install SCCM client. I can also see the leftovers of an incomplete TS under c:\_SMSTaskSequence
If we change the image specified under "Apply Operating System" step, everything works ok.
It appears there is something wrong with this particular image. Any ideas?
Logs show no errors. Let me know which logs you'd like me to post (and from which location)
There is no ccm folder under c:\windowsHoping you are using ConfigMgr 2012 R2. If a client machine Join to Domain and doesn't proceed with other steps and not installing the CCM client, then problem seems to be with the Image.Do you have any RunOnce registry setting specified in the Image? You
can mount the Image and check those settings.
RunOnce Key Reference :
https://msdn.microsoft.com/en-us/library/windows/desktop/aa376977(v=vs.85).aspx
If the above key is present in the Image, TS Engine won't resume after the reboot.
You need to use a new variable "SMSTSPostAction" at the end of the Task Sequence, to add your custom actions.
The above variable is applicable in CM 2012 SP1 and R2.
Thanks, Senthil. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. Click on "vote as Helpful" if you feel this post helpful to you. This
can be beneficial to other community members reading the thread. -
I've started getting an intermittent error editing my Windows 7 OSD task sequence. Sometimes I can open the TS to edit, but when I try to apply changes I get the error. Other times I get the error when trying to open the TS. If I try again
right away, I still get the error, but if I wait a few minutes and try again sometimes it will open the TS.
The error reads:
ConfigMgr Error Object:instance of SMS_Extended Status{Description = "Failed to load dynamic properties for class \"SMS_TaskSequence_ApplyWindowsSettingsAction\" from XML into WMI";Error Code = 2147943746;File = "e:\\qfe\\nts\\sms\\siteserver\\sdk_provider\\smsprov\\ssptspackage.cpp";Line = 3454;Operation = "ExecMethod";ParameterInfo = "SMS_TaskSequencePackage";ProviderName = "WinMgmt";StatusCode = 2147749889;}
Coinciding with this error, I show the following entries in the TaskSequenceProvider.log file:
[PID: 7608] Invoking method SMS_TaskSequence.LoadFromXml
TaskSequenceProvider
Failed to protect memory buffer, hr=0x80070542
TaskSequenceProvider
Failed to load dynamic properties for class "SMS_TaskSequence_ApplyWindowsSettingsAction" from XML into WMI 0x80070542 (2147943746)
TaskSequenceProvider
Failed to load node Apply Windows Settings from XML into WMI 0x80070542 (2147943746)
TaskSequenceProvider
Failed to load children steps for node "PostInstall" from XML 0x80070542 (2147943746)
TaskSequenceProvider
Failed to load children steps for node "Execute Task Sequence" from XML 0x80070542 (2147943746)
TaskSequenceProvider
Failed to load children steps for node "" from XML 0x80070542 (2147943746)
TaskSequenceProvider
Failed to load XML for the task sequence into WMI 0x80070542 (2147943746)
TaskSequenceProvider
[PID: 7608] Done with method SMS_TaskSequence.LoadFromXml
TaskSequenceProvider
Setting status complete: status code = 0x80070542; Failed to load dynamic properties for class "SMS_TaskSequence_ApplyWindowsSettingsAction" from XML into WMI
TaskSequenceProvider
I exported the task sequence and checked in "object.xml" for the "ApplyWindowsSettingsAction", to see if there was something odd in the xml, but I don't find anything that jumps out as being wrong. Here's the section of XML for
that step. I've removed identifying info, and replaced it with a generic term in bold.
<step type="SMS_TaskSequence_ApplyWindowsSettingsAction" name="Apply Windows Settings" description="" runIn="WinPE" successCodeList="0" runFromNet="false"><action>osdwinsettings.exe /config</action><defaultVarList><variable name="OSDLocalAdminPassword" property="AdminPassword"></variable><variable name="OSDComputerName" property="ComputerName">%_SMSTSMachineName%</variable><variable name="OSDProductKey" property="ProductKey"></variable><variable name="OSDRandomAdminPassword" property="RandomAdminPassword">false</variable><variable name="OSDRegisteredOrgName" property="RegisteredOrgName">COMPANY NAME</variable><variable name="OSDRegisteredUserName" property="RegisteredUserName">COMPANY NAME</variable><variable name="OSDServerLicenseConnectionLimit" property="ServerLicenseConnectionLimit">5</variable><variable name="OSDTimeZone" property="TimeZone">Central Standard Time</variable></defaultVarList></step><step type="SMS_TaskSequence_ApplyNetworkSettingsAction" name="Apply Network Settings" description="" runIn="WinPEandFullOS" successCodeList="0" runFromNet="false"><action>osdnetsettings.exe configure</action><defaultVarList><variable name="OSDDomainName" property="DomainName">DOMAIN.COM</variable><variable name="OSDJoinPassword" property="DomainPassword"></variable><variable name="OSDJoinAccount" property="DomainUsername">DOMAIN ACCOUNT</variable><variable name="OSDEnableTCPIPFiltering" property="EnableTCPIPFiltering" hidden="true">false</variable><variable name="OSDNetworkJoinType" property="NetworkJoinType">0</variable><variable name="OSDAdapterCount" property="NumAdapters" hidden="true">0</variable></defaultVarList></step>
Is there any other log I should check for a clue on this issue? What could be causing this error?Thanks for sharing that! I tend to save contacting MS support until after I've exhausted other options. I'm always afraid that I'll spend the $500 to open a case and then it turns out to be something simple that I would have found if I had just
kept working on it myself a little longer.
It looks like that link is for an update released in February as KB3023562. I downloaded and installed it. I'll try opening/editing/saving the task sequence a few times today to see if the issue is resolved.
After I had already installed it, I thought to look up that update in configmgr. The update is listed as superseded by 2 other updates. The newest of those is KB3046049, which just installed last night with the other March patches, so it's possible
that I didn't need to install KB3023562 after all.
Maybe you are looking for
-
Can you import music from an itunes from one computer to another?
can you import music from itunes on one computer to another?
-
Macbook backup (LION) on Time Capsule to Macbook Pro
Can I use a macbook backup (LION) on Time Capsule & use that backup to restore a new Macbook Pro also with Lion.
-
Touch: Wont turn off: Need to recover due to "Firmware Probl
Hi all. I have a 40gb Touch that just got the Firmware Problem screen. So, I start looking around here and see about recovery steps, but can't get the player to turn off. Try holding down the power button, nothing. The player turns off while the pape
-
I need APO DP enduser training material
hi gurus, i need APO DP enduser training material, how to give the end user training, what contents should i tell and what is the process of end user training. can u tell me how should i give. Regards, babu
-
Can't Download Adobe Flash Player
I am using WIndows 7 64 bit - IE 9 - Firefox 9.0.1 - Chrome v27 When ever I try to download it sits at either 7%, 8% or 23%..And never progresses. I am not restriced to downloading anything this as it's a personal computer. Firewall is not preventing