none
MDT2010 - Cannot capture image of Win7 reference PC

    Question

  • Hi Everyone,

    I'm having a real problem capturing an image of a Win 7 reference PC with MDT2010, and I've been battling away at it for over a week now with no success. I'm hoping that someone can help me.

    Some background: I'm only new to MDT, first beginning to use it about a month ago. We had a new remote site come online, and we needed to build 20 workstations in quick order down there. To make my job easier I :

    • set up MDT 2010 on my laptop (Win7 enterprise, x86),
    • imported an XP Pro CD, created task sequences, updated deploymentshares, burnt boot CD, etc,
    • built a reference PC from MDT - using the standard client deploy task sequence,
    • installed Office 2007 and all our other customisations,
    • captured that image via a Sysprep and Capture task sequence,
    • deployed that image to the 20 client PCs at the remote site in one afternoon.

    It worked faultlessly, and was lightning quick. Count me in as an MDT evangelist. I subsequently built another 2 SOE images - Windows XP with Office 2003, and a basic domain-joined and updated Windows XP SP3 with no apps. These join the Windows XP SP3 with Office 2007 that was captured previously. All three of these images captured perfectly.

    One of our upcoming projects is to upgrade all the desktops and laptops to Windows 7 / Office 2007. Obviously, having had so much success with MDT and Windows XP images, I was keen to use it. After all, that's why MDT 2010 exists - as a solution accelerator to help people with Win 7 migrations! And this is where I have my problems. I can build the reference PC perfectly fine, but I cannot capture it. Sysprep runs and completes, but then the PC just "stalls" - the script is still running, but nothing happens. I have left it overnight, and still no change.

    Things I have tried:

    • Different hardware (a brand new HP dc8000 PC and a brand new HP 6730b laptop), and it's the same on both.
    • Applying the changes to the ztiutility.vbs file for the "mutliple connections to the same server" error, despite not actually experiencing that error. Figured it couldn't hurt,
    • Running both litetouch.wsf and litetouch.vbs, running them from the Start-Run box, as well as a command prompt. Running them just as themselves, calling them with cscript, and calling them with wscript,
    • Running from an elevated command prompt,
    • Hours googling the error codes that is being thrown, which shows up nothing matching my specific circumstance,
    • Re-importing the OS files, re-creating new task sequences for both deployment of the base OS, as well as capturing the reference image,
    • Building the reference PC from both a MDT deployment sequence, as well as installing "clean" from the original Windows 7 install DVD,
    • Updating the DeploymentShare half a dozen times,
    • Moved the reference PC out of it's normal OU, back into the generic \Computers container, so no GP is being applied at time of capture,
    • Checked permissions on the DepoymentShare$ share,
    • Standing on my head, drinking a cup of water backwards whilst humming God Save The Queen when initiating the capture task,
    • And a dozen other things I've forgotten,

    I have NOT removed the PCs from the domain before running the capture. I've heard people suggest this. I've not yet tried it. It's what I'll be trying next. The WinXP machines were captured whilst still domain-joined, and they worked fine, which leads me to believe these issues are more likely authentication issues than domain-join issues.

    I am using a domain-admin account to log onto the reference PC and initiate the litetouch script. The script is being run from an elevated command prompt, using the UNC for the script. I have tried mapping a drive from the elevated command prompt and executing the script that way - no difference. The domain-admin account that I am logging onto the reference PC with is a different account to what the laptop with the DeploymentShare is logged on with (which is my normal user account). The domain-admin account I'm using on the reference PC has full access to the deploymentshare, and is the same account that is used initially to deploy the base OS install from MDT on the laptop.

    I've rebuilt both machines from scratch 7+ times each now, and am no closer to getting an image captured than I was to start with. So you can see my frustration. It seems to me that the sysprep step completes, and the next step *should* be for the PC to reboot into WinPE, and start the capture. But the PC never reboots. The Sysprep window pops up, does it's thing, and goes away, and then the PC just sits. The script is still running in the command prompt box, and you can see the cscript.exe in Task Manager ticking along at 0% CPU, but nothing happens.

    Onto the Log files!

    These snippets of log files are copied off the Win7 reference PC after the Sysprep component has run, and it's in it's "stuck" stage. These are the "interesting bits" culled from the log files - if there's any value in the entire loge files, I can post them. CNSLAPTOP99 is the MDT console/deployment workbench computer (sanem machine, same config that built and captured the Win XP images).

    C:\MININT\SMSOSD\OSDLogs\BDD.log:

    Up until this point everything seems to be going OK. Where it gets interesting:

     

    <![LOG[About to run command: C:\Windows\system32\sysprep\sysprep.exe /quiet /generalize /oobe /quit]LOG]!><time="15:36:55.000+000" date="05-21-2010" component="LTISysprep" context="" type="1" thread="" file="LTISysprep">
    <![LOG[Return code from command = 0]LOG]!><time="15:40:57.000+000" date="05-21-2010" component="LTISysprep" context="" type="1" thread="" file="LTISysprep">
    <![LOG[Contents of CloneTag(0): Fri May 21 15:37:22 2010]LOG]!><time="15:40:57.000+000" date="05-21-2010" component="LTISysprep" context="" type="1" thread="" file="LTISysprep">
    <![LOG[SystemSetupInProgress is set to 1]LOG]!><time="15:40:57.000+000" date="05-21-2010" component="LTISysprep" context="" type="1" thread="" file="LTISysprep">
    <![LOG[LTISysprep processing completed successfully.]LOG]!><time="15:40:57.000+000" date="05-21-2010" component="LTISysprep" context="" type="1" thread="" file="LTISysprep">
    <![LOG[Litetouch deployment failed, Return Code = -2147467259 0x80004005]LOG ]! ><time="15:40:57.000+000" date="05-21-2010" component="LiteTouch" context="" type="3" thread="" file="LiteTouch">
    <![LOG[For more information, consult the task sequencer log ...\SMSTS.LOG.]LOG]!><time="15:40:57.000+000" date="05-21-2010" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Property RetVal is now = -2147467259]LOG]!><time="15:40:57.000+000" date="05-21-2010" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[CleanStartItems Complete]LOG]!><time="15:40:57.000+000" date="05-21-2010" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[About to run command: MSHTA.exe "\\cnslaptop99\deploymentshare$\scripts\Wizard.hta" /definition:Summary_Definition_ENU.xml]LOG]!><time="15:40:58.000+000" date="05-21-2010" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">

     

    C:\MININT\SMSOSD\OSDLOGS\LiteTouch.log

     

    <![LOG[Successfully established connection using supplied credentials.]LOG]!><time="15:35:18.000+000" date="05-21-2010" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Property DeployDrive is now = Z:]LOG]!><time="15:35:18.000+000" date="05-21-2010" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[DeployDrive = Z:]LOG]!><time="15:35:18.000+000" date="05-21-2010" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Property ResourceRoot is now = \\CNSLAPTOP99\DeploymentShare$]LOG]!><time="15:35:18.000+000" date="05-21-2010" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[DeploymentType = CUSTOM]LOG]!><time="15:35:18.000+000" date="05-21-2010" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[ResourceRoot = \\CNSLAPTOP99\DeploymentShare$]LOG]!><time="15:35:18.000+000" date="05-21-2010" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Property ResourceDrive is now = Z:]LOG]!><time="15:35:18.000+000" date="05-21-2010" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[ResourceDrive = Z:]LOG]!><time="15:35:18.000+000" date="05-21-2010" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Property _SMSTSPackageName is now = Lite Touch Installation]LOG]!><time="15:35:18.000+000" date="05-21-2010" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[SMS Task Sequencer found at \\CNSLAPTOP99\DeploymentShare$\Tools\X86, copying to C:\MININT\Tools\X86]LOG]!><time="15:35:18.000+000" date="05-21-2010" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Copying \\CNSLAPTOP99\DeploymentShare$\Tools\X86\CcmCore.dll to C:\MININT\Tools\X86\CcmCore.dll]LOG]!><time="15:35:18.000+000" date="05-21-2010" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Copying \\CNSLAPTOP99\DeploymentShare$\Tools\X86\CcmUtilLib.dll to C:\MININT\Tools\X86\CcmUtilLib.dll]LOG]!><time="15:35:33.000+000" date="05-21-2010" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Copying \\CNSLAPTOP99\DeploymentShare$\Tools\X86\Smsboot.exe to C:\MININT\Tools\X86\Smsboot.exe]LOG]!><time="15:35:37.000+000" date="05-21-2010" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Copying \\CNSLAPTOP99\DeploymentShare$\Tools\X86\SmsCore.dll to C:\MININT\Tools\X86\SmsCore.dll]LOG]!><time="15:35:38.000+000" date="05-21-2010" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Copying \\CNSLAPTOP99\DeploymentShare$\Tools\X86\TsCore.dll to C:\MININT\Tools\X86\TsCore.dll]LOG]!><time="15:35:41.000+000" date="05-21-2010" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Copying \\CNSLAPTOP99\DeploymentShare$\Tools\X86\TSEnv.exe to C:\MININT\Tools\X86\TSEnv.exe]LOG]!><time="15:35:57.000+000" date="05-21-2010" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Copying \\CNSLAPTOP99\DeploymentShare$\Tools\X86\TsManager.exe to C:\MININT\Tools\X86\TsManager.exe]LOG]!><time="15:35:59.000+000" date="05-21-2010" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Copying \\CNSLAPTOP99\DeploymentShare$\Tools\X86\TsmBootstrap.exe to C:\MININT\Tools\X86\TsmBootstrap.exe]LOG]!><time="15:36:04.000+000" date="05-21-2010" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Copying \\CNSLAPTOP99\DeploymentShare$\Tools\X86\TsMessaging.dll to C:\MININT\Tools\X86\TsMessaging.dll]LOG]!><time="15:36:12.000+000" date="05-21-2010" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Copying \\CNSLAPTOP99\DeploymentShare$\Tools\X86\TsProgressUI.exe to C:\MININT\Tools\X86\TsProgressUI.exe]LOG]!><time="15:36:22.000+000" date="05-21-2010" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Copying \\CNSLAPTOP99\DeploymentShare$\Tools\X86\TSResNlc.dll to C:\MININT\Tools\X86\TSResNlc.dll]LOG]!><time="15:36:36.000+000" date="05-21-2010" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Copying \\CNSLAPTOP99\DeploymentShare$\Tools\X86\xprslib.dll to C:\MININT\Tools\X86\xprslib.dll]LOG]!><time="15:36:39.000+000" date="05-21-2010" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Copying \\CNSLAPTOP99\DeploymentShare$\Tools\X86\00000409\tsres.dll to C:\MININT\Tools\X86\00000409\tsres.dll]LOG]!><time="15:36:40.000+000" date="05-21-2010" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Copying \\CNSLAPTOP99\DeploymentShare$\Control\CAPWIN7\TS.XML to C:\MININT\Tools\X86]LOG]!><time="15:36:44.000+000" date="05-21-2010" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Copying C:\MININT\SMSOSD\OSDLOGS\VARIABLES.DAT to C:\MININT\Tools\X86\VARIABLES.DAT]LOG]!><time="15:36:45.000+000" date="05-21-2010" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[LTI beginning deployment]LOG]!><time="15:36:45.000+000" date="05-21-2010" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[About to run command: "C:\MININT\Tools\X86\TsmBootstrap.exe" /env:SAStart]LOG ]!><time="15:36:45.000+000" date="05-21-2010" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Litetouch deployment failed, Return Code = -2147467259 0x80004005]LOG ]!><time="15:40:57.000+000" date="05-21-2010" component="LiteTouch" context="" type="3" thread="" file="LiteTouch">
    <![LOG[For more information, consult the task sequencer log ...\SMSTS.LOG.]LOG]!><time="15:40:57.000+000" date="05-21-2010" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Property RetVal is now = -2147467259]LOG]!><time="15:40:57.000+000" date="05-21-2010" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[CleanStartItems Complete]LOG]!><time="15:40:57.000+000" date="05-21-2010" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[About to run command: MSHTA.exe "\\cnslaptop99\deploymentshare$\scripts\Wizard.hta" /definition:Summary_Definition_ENU.xml]LOG]!><time="15:40:58.000+000" date="05-21-2010" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">

     

     

    C:\Users\...\Temp\smsts.log

     

    <![LOG[The condition for the action (Apply Windows PE) is evaluated to be true]LOG]!><time="15:40:57.710+000" date="05-21-2010" component="TSManager" context="" type="1" thread="3636" file="instruction.cxx:2912">
    <![LOG[Expand a string: cscript.exe "%SCRIPTROOT%\LTIApply.wsf" /PE]LOG]!><time="15:40:57.710+000" date="05-21-2010" component="TSManager" context="" type="0" thread="3636" file="executionenv.cxx:782">
    <![LOG[Expand a string: ]LOG]!><time="15:40:57.710+000" date="05-21-2010" component="TSManager" context="" type="0" thread="3636" file="executionenv.cxx:782">
    <![LOG[Command line for extension .exe is "%1" %*]LOG]!><time="15:40:57.726+000" date="05-21-2010" component="TSManager" context="" type="0" thread="3636" file="commandline.cpp:229">
    <![LOG[Set command line: cscript.exe "%SCRIPTROOT%\LTIApply.wsf" /PE]LOG]!><time="15:40:57.726+000" date="05-21-2010" component="TSManager" context="" type="0" thread="3636" file="commandline.cpp:707">
    <![LOG[Start executing the command line: cscript.exe "%SCRIPTROOT%\LTIApply.wsf" /PE]LOG]!><time="15:40:57.726+000" date="05-21-2010" component="TSManager" context="" type="1" thread="3636" file="instruction.cxx:2928">
    <![LOG[!--------------------------------------------------------------------------------------------!]LOG]!><time="15:40:57.726+000" date="05-21-2010" component="TSManager" context="" type="1" thread="3636" file="instruction.cxx:2957">
    <![LOG[Expand a string: ]LOG]!><time="15:40:57.726+000" date="05-21-2010" component="TSManager" context="" type="0" thread="3636" file="executionenv.cxx:782">
    <![LOG[Executing command line: cscript.exe "%SCRIPTROOT%\LTIApply.wsf" /PE]LOG]!><time="15:40:57.726+000" date="05-21-2010" component="TSManager" context="" type="1" thread="3636" file="commandline.cpp:805">
    <![LOG[Process completed with exit code 1]LOG]!><time="15:40:57.726+000" date="05-21-2010" component="TSManager" context="" type="1" thread="3636" file="commandline.cpp:1102">
    <![LOG[!--------------------------------------------------------------------------------------------!]LOG]!><time="15:40:57.726+000" date="05-21-2010" component="TSManager" context="" type="1" thread="3636" file="instruction.cxx:3010">
    <![LOG[Failed to run the action: Apply Windows PE.
    Incorrect function. (Error: 00000001;
    Source: Windows
    )]LOG]!><time="15:40:57.741+000" date="05-21-2010" component="TSManager" context="" type="3" thread="3636" file="instruction.cxx:3101">
    <![LOG[Sending status message . . .]LOG]!><time="15:40:57.741+000" date="05-21-2010" component="TSManager" context="" type="1" thread="3636" file="utility.cxx:292">
    <![LOG[Executing in non SMS standalone mode. Ignoring send a task execution status message request]LOG]!><time="15:40:57.741+000" date="05-21-2010" component="TSManager" context="" type="1" thread="3636" file="utility.cxx:302">
    <![LOG[Set a global environment variable _SMSTSLastActionRetCode=1]LOG]!><time="15:40:57.741+000" date="05-21-2010" component="TSManager" context="" type="0" thread="3636" file="executionenv.cxx:668">
    <![LOG[Set a global environment variable _SMSTSLastActionSucceeded=false]LOG]!><time="15:40:57.741+000" date="05-21-2010" component="TSManager" context="" type="0" thread="3636" file="executionenv.cxx:668">
    <![LOG[Clear local default environment]LOG]!><time="15:40:57.741+000" date="05-21-2010" component="TSManager" context="" type="0" thread="3636" file="executionenv.cxx:807">
    <![LOG[Let the parent group (Capture Image) decides whether to continue execution]LOG]!><time="15:40:57.772+000" date="05-21-2010" component="TSManager" context="" type="0" thread="3636" file="instruction.cxx:3210">
    <![LOG[The execution of the group (Capture Image) has failed and the execution has been aborted. An action failed.
    Operation aborted (Error: 80004004; Source: Windows)]LOG]!><time="15:40:57.788+000" date="05-21-2010" component="TSManager" context="" type="3" thread="3636" file="instruction.cxx:2424">
    <![LOG[Failed to run the last action: Apply Windows PE. Execution of task sequence failed.
    Incorrect function. (Error: 00000001; Source: Windows)]LOG]!><time="15:40:57.788+000" date="05-21-2010" component="TSManager" context="" type="3" thread="3636" file="engine.cxx:214">
    <![LOG[Sending status message . . .]LOG]!><time="15:40:57.788+000" date="05-21-2010" component="TSManager" context="" type="1" thread="3636" file="utility.cxx:292">
    <![LOG[Executing in non SMS standalone mode. Ignoring send a task execution status message request]LOG]!><time="15:40:57.788+000" date="05-21-2010" component="TSManager" context="" type="1" thread="3636" file="utility.cxx:302">
    <![LOG[Execution::enExecutionFail != m_eExecutionResult, HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\tsmanager\tsmanager.cpp,762)]LOG]!><time="15:40:57.788+000" date="05-21-2010" component="TSManager" context="" type="0" thread="3636" file="tsmanager.cpp:762">
    <![LOG[Task Sequence Engine failed! Code: enExecutionFail]LOG]!><time="15:40:57.788+000" date="05-21-2010" component="TSManager" context="" type="3" thread="3636" file="tsmanager.cpp:762">
    <![LOG[****************************************************************************]LOG]!><time="15:40:57.788+000" date="05-21-2010" component="TSManager" context="" type="1" thread="3636" file="tsmanager.cpp:784">
    <![LOG[Task sequence execution failed with error code 80004005]LOG]!><time="15:40:57.788+000" date="05-21-2010" component="TSManager" context="" type="3" thread="3636" file="tsmanager.cpp:785">
    <![LOG[Cleaning Up. Removing Authenticator]LOG]!><time="15:40:57.788+000" date="05-21-2010" component="TSManager" context="" type="1" thread="3636" file="tsmanager.cpp:578">

     

     

    C:\Users\...\Temp\SMSTSLog\smsts.log

    <![LOG[The condition for the action (Apply Windows PE) is evaluated to be true]LOG]!><time="15:40:57.710+000" date="05-21-2010" component="TSManager" context="" type="1" thread="3636" file="instruction.cxx:2912">
    <![LOG[Expand a string: cscript.exe "%SCRIPTROOT%\LTIApply.wsf" /PE]LOG]!><time="15:40:57.710+000" date="05-21-2010" component="TSManager" context="" type="0" thread="3636" file="executionenv.cxx:782">
    <![LOG[Expand a string: ]LOG]!><time="15:40:57.710+000" date="05-21-2010" component="TSManager" context="" type="0" thread="3636" file="executionenv.cxx:782">
    <![LOG[Command line for extension .exe is "%1" %*]LOG]!><time="15:40:57.726+000" date="05-21-2010" component="TSManager" context="" type="0" thread="3636" file="commandline.cpp:229">
    <![LOG[Set command line: cscript.exe "%SCRIPTROOT%\LTIApply.wsf" /PE]LOG]!><time="15:40:57.726+000" date="05-21-2010" component="TSManager" context="" type="0" thread="3636" file="commandline.cpp:707">
    <![LOG[Start executing the command line: cscript.exe "%SCRIPTROOT%\LTIApply.wsf" /PE]LOG]!><time="15:40:57.726+000" date="05-21-2010" component="TSManager" context="" type="1" thread="3636" file="instruction.cxx:2928">
    <![LOG[!--------------------------------------------------------------------------------------------!]LOG]!><time="15:40:57.726+000" date="05-21-2010" component="TSManager" context="" type="1" thread="3636" file="instruction.cxx:2957">
    <![LOG[Expand a string: ]LOG]!><time="15:40:57.726+000" date="05-21-2010" component="TSManager" context="" type="0" thread="3636" file="executionenv.cxx:782">
    <![LOG[Executing command line: cscript.exe "%SCRIPTROOT%\LTIApply.wsf" /PE]LOG]!><time="15:40:57.726+000" date="05-21-2010" component="TSManager" context="" type="1" thread="3636" file="commandline.cpp:805">
    <![LOG[Process completed with exit code 1]LOG]!><time="15:40:57.726+000" date="05-21-2010" component="TSManager" context="" type="1" thread="3636" file="commandline.cpp:1102">
    <![LOG[!--------------------------------------------------------------------------------------------!]LOG]!><time="15:40:57.726+000" date="05-21-2010" component="TSManager" context="" type="1" thread="3636" file="instruction.cxx:3010">
    <![LOG[ Failed to run the action: Apply Windows PE.

    Incorrect function. (Error: 00000001; Source: Windows

    )]LOG]!><time="15:40:57.741+000" date="05-21-2010" component="TSManager" context="" type="3" thread="3636" file="instruction.cxx:3101">
    <![LOG[Sending status message . . .]LOG]!><time="15:40:57.741+000" date="05-21-2010" component="TSManager" context="" type="1" thread="3636" file="utility.cxx:292">
    <![LOG[Executing in non SMS standalone mode. Ignoring send a task execution status message request]LOG]!><time="15:40:57.741+000" date="05-21-2010" component="TSManager" context="" type="1" thread="3636" file="utility.cxx:302">
    <![LOG[Set a global environment variable _SMSTSLastActionRetCode=1]LOG]!><time="15:40:57.741+000" date="05-21-2010" component="TSManager" context="" type="0" thread="3636" file="executionenv.cxx:668">
    <![LOG[Set a global environment variable _SMSTSLastActionSucceeded=false]LOG]!><time="15:40:57.741+000" date="05-21-2010" component="TSManager" context="" type="0" thread="3636" file="executionenv.cxx:668">
    <![LOG[Clear local default environment]LOG]!><time="15:40:57.741+000" date="05-21-2010" component="TSManager" context="" type="0" thread="3636" file="executionenv.cxx:807">
    <![LOG[Let the parent group (Capture Image) decides whether to continue execution]LOG]!><time="15:40:57.772+000" date="05-21-2010" component="TSManager" context="" type="0" thread="3636" file="instruction.cxx:3210">
    <![LOG[The execution of the group (Capture Image) has failed and the execution has been aborted. An action failed.
    Operation aborted (Error: 80004004; Source: Windows)]LOG]!><time="15:40:57.788+000" date="05-21-2010" component="TSManager" context="" type="3" thread="3636" file="instruction.cxx:2424">
    <![LOG[Failed to run the last action: Apply Windows PE. Execution of task sequence failed.
    Incorrect function. (Error: 00000001; Source: Windows)]LOG]!><time="15:40:57.788+000" date="05-21-2010" component="TSManager" context="" type="3" thread="3636" file="engine.cxx:214">
    <![LOG[Sending status message . . .]LOG]!><time="15:40:57.788+000" date="05-21-2010" component="TSManager" context="" type="1" thread="3636" file="utility.cxx:292">
    <![LOG[Executing in non SMS standalone mode. Ignoring send a task execution status message request]LOG]!><time="15:40:57.788+000" date="05-21-2010" component="TSManager" context="" type="1" thread="3636" file="utility.cxx:302">
    <![LOG[Execution::enExecutionFail != m_eExecutionResult, HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\tsmanager\tsmanager.cpp,762)]LOG]!><time="15:40:57.788+000" date="05-21-2010" component="TSManager" context="" type="0" thread="3636" file="tsmanager.cpp:762">
    <![LOG[Task Sequence Engine failed! Code: enExecutionFail]LOG]!><time="15:40:57.788+000" date="05-21-2010" component="TSManager" context="" type="3" thread="3636" file="tsmanager.cpp:762">
    <![LOG[****************************************************************************]LOG]!><time="15:40:57.788+000" date="05-21-2010" component="TSManager" context="" type="1" thread="3636" file="tsmanager.cpp:784">
    <![LOG[Task sequence execution failed with error code 80004005]LOG]!><time="15:40:57.788+000" date="05-21-2010" component="TSManager" context="" type="3" thread="3636" file="tsmanager.cpp:785">
    <![LOG[Cleaning Up. Removing Authenticator]LOG]!><time="15:40:57.788+000" date="05-21-2010" component="TSManager" context="" type="1" thread="3636" file="tsmanager.cpp:578">
    <![LOG[Cleaning up task sequence folder]LOG]!><time="15:40:57.804+000" date="05-21-2010" component="TSManager" context="" type="1" thread="3636" file="utils.cpp:1404">
    <![LOG[DeleteFileW(sVolumeIDFile.c_str()), HRESULT=80070002 (e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,513)]LOG]!><time="15:40:57.850+000" date="05-21-2010" component="TSManager" context="" type="0" thread="3636" file="resolvesource.cpp:513">
    <![LOG[Successfully unregistered Task Sequencing Environment COM Interface.]LOG]!><time="15:40:57.866+000" date="05-21-2010" component="TSManager" context="" type="1" thread="3636" file="environmentlib.cpp:855">
    <![LOG[Command line for extension .exe is "%1" %*]LOG]!><time="15:40:57.866+000" date="05-21-2010" component="TSManager" context="" type="0" thread="3636" file="commandline.cpp:229">
    <![LOG[Set command line: "C:\MININT\Tools\X86\TsProgressUI.exe" /Unregister]LOG]!><time="15:40:57.866+000" date="05-21-2010" component="TSManager" context="" type="0" thread="3636" file="commandline.cpp:707">
    <![LOG[Executing command line: "C:\MININT\Tools\X86\TsProgressUI.exe" /Unregister]LOG]!><time="15:40:57.866+000" date="05-21-2010" component="TSManager" context="" type="1" thread="3636" file="commandline.cpp:805">
    <![LOG[==========[ TsProgressUI started in process 3876 ]==========]LOG]!><time="15:40:57.866+000" date="05-21-2010" component="TsProgressUI" context="" type="1" thread="3884" file="winmain.cpp:327">
    <![LOG[Command line: "C:\MININT\Tools\X86\TsProgressUI.exe" /Unregister]LOG]!><time="15:40:57.882+000" date="05-21-2010" component="TsProgressUI" context="" type="0" thread="3884" file="winmain.cpp:330">
    <![LOG[Unregistering COM classes]LOG]!><time="15:40:57.882+000" date="05-21-2010" component="TsProgressUI" context="" type="1" thread="3884" file="winmain.cpp:202">
    <![LOG[Unregistering class objects]LOG]!><time="15:40:57.882+000" date="05-21-2010" component="TsProgressUI" context="" type="1" thread="3884" file="winmain.cpp:503">
    <![LOG[Shutdown complete.]LOG]!><time="15:40:57.882+000" date="05-21-2010" component="TsProgressUI" context="" type="1" thread="3884" file="winmain.cpp:520">
    <![LOG[Process completed with exit code 0]LOG]!><time="15:40:57.882+000" date="05-21-2010" component="TSManager" context="" type="1" thread="3636" file="commandline.cpp:1102">
    <![LOG[Successfully unregistered TS Progress UI.]LOG]!><time="15:40:57.882+000" date="05-21-2010" component="TSManager" context="" type="1" thread="3636" file="utils.cpp:1963">
    <![LOG[g_TSManager.Run(), HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\tsmanager\tsmanager.cpp,654)]LOG]!><time="15:40:57.882+000" date="05-21-2010" component="TSManager" context="" type="0" thread="3636" file="tsmanager.cpp:654">
    <![LOG[Error Task Sequence Manager failed to execute task sequence. Code 0x80004005]LOG]!><time="15:40:57.882+000" date="05-21-2010" component="TSManager" context="" type="3" thread="3636" file="tsmanager.cpp:684">
    <![LOG[Sending error status message]LOG]!><time="15:40:57.882+000" date="05-21-2010" component="TSManager" context="" type="1" thread="3636" file="tsmanager.cpp:685">
    <![LOG[In non SMS staqndalone mode.Ignoring SendStatusMessage request]LOG]!><time="15:40:57.882+000" date="05-21-2010" component="TSManager" context="" type="1" thread="3636" file="tsmanager.cpp:1536">
    <![LOG[Finalizing logging from process 1792]LOG]!><time="15:40:57.882+000" date="05-21-2010" component="TSManager" context="" type="1" thread="3636" file="tslogging.cpp:1736">
    <![LOG[LOGGING: Setting log directory to "C:\Users\AAMRUS~1\AppData\Local\Temp\".]LOG]!><time="15:40:57.882+000" date="05-21-2010" component="TSManager" context="" type="1" thread="3636" file="tslogging.cpp:1803">
    <![LOG[Process completed with exit code 2147500037]LOG]!><time="15:40:57.897+000" date="05-21-2010" component="TSMBootstrap" context="" type="1" thread="3760" file="commandline.cpp:1102">
    <![LOG[Exiting with return code 0x80004005]LOG]!><time="15:40:57.897+000" date="05-21-2010" component="TSMBootstrap" context="" type="1" thread="3760" file="tsmbootstrap.cpp:1117">

     

    As mentioned above, I'm about at my wits end with this. From what I know of the process, the PC has been syspreped and generalise. Certainly if I restart the reference PC at this stage, it boots up and sits on the "installing drivers" startup screen for a long time as it adds in it's drivers. But it certainly doesn't boot into WinPE at that stage - that's the main proper Windows install on the machine which is installing it's drivers.

     

    Additional Info - The SOE image I'm trying to capture is a base install of Win 7 Enterprise x86 with the following customisations:

    • NO BitLocker- we'll do that later as we need to initialise the TPM and escrow the keys into AD
    • Domain-joined, and in a proper OU with standard GP applied
    • All applicable WSUS patches applied to both OS and apps
    • 3 additional Fonts installed
    • Office 2007 Enterprise - Full installation
    • Office 2007 Search Commands ribbon add-in from OfficeLabs.com
    • Office 2007 PDF & XPS add-in from OfficeLabs.com
    • MS FFCS AV
    And that's it. Initially I had installed the Cisco VPN client, but had read reports that it (along with a Symantec product that we do not use) can lead to the "dropped network problem" that seems to be afflicting people. I have since removed that step from our build, as hopefully the laptops will be using DirectAccess for their remote connectivity. Worst case, we can install the VPN client post-image for the select few users who require it.

     

    Has any one come across this issue themselves, and been able to successfully resolve it? Does anyone have any suggestions as to what may be the problem here? I'm willing to try anything at the moment! I feel as if I'm missing something reasonably basic, so don't feel as if any suggestion is too silly to point out - I'll take whatever I can get at this stage.

    Thanks very much for taking the time to read through all this. I hope to hear from the experts soon!

    Kind Regards,

    Matt Russell

    Queensland, Australia

    Friday, May 21, 2010 6:46 AM

Answers

  • Please check out the MDT 2010 Update 1 Beta release available through http://connect.microsoft.com, as it may resolve your problem.

    It appears that the sysprep execution is disrupting the network connectivity, so when the task sequence goes to run the next step after sysprep completes it can't read the script from the network share, so the task sequence then fails.  We've seen this happen with some machines, typically when certain software packages (antivirus, firewall, etc.) insert drivers into the network stack.

    In MDT 2010 Update 1, we've modified the task sequence so that it doesn't need to have network access after sysprep executes - we've already staged what we need locally. 

    -Michael Niehaus
     Senior Software Development Engineer
     mniehaus@microsoft.com
     http://blogs.technet.com/mniehaus

     

    Friday, May 21, 2010 7:30 PM

All replies

  • Hello,

    There's a lot of info in your post (possible a bit too much for me to read in the few minutes I have spare) but when you build your reference image are you installing drivers as part of the process?

    If you are try not installing any drivers (excluding the NIC driver of course) as I have seen issues on Dell systems with sysprep where the build process fails as I had installed the audio drivers.

    Better still use VMWare or Microsoft Virtual PC as your reference PC - if you search this forum there was a recent post that discussed the many benefits of using a virtual platform to build the reference image.

    Friday, May 21, 2010 7:52 AM
  • Please check out the MDT 2010 Update 1 Beta release available through http://connect.microsoft.com, as it may resolve your problem.

    It appears that the sysprep execution is disrupting the network connectivity, so when the task sequence goes to run the next step after sysprep completes it can't read the script from the network share, so the task sequence then fails.  We've seen this happen with some machines, typically when certain software packages (antivirus, firewall, etc.) insert drivers into the network stack.

    In MDT 2010 Update 1, we've modified the task sequence so that it doesn't need to have network access after sysprep executes - we've already staged what we need locally. 

    -Michael Niehaus
     Senior Software Development Engineer
     mniehaus@microsoft.com
     http://blogs.technet.com/mniehaus

     

    Friday, May 21, 2010 7:30 PM
  • Good to hear the new update will fix this issue.

    Also check out this post and see Windows7x64_DeployGuy solution which works for me.

    http://social.technet.microsoft.com/Forums/en-US/itprovistadeployment/thread/38dd443b-428e-4fcd-a037-7f6d11d5d1e4

    Saturday, May 22, 2010 2:35 PM
  • Hi Mosquat - thanks for the help.

    When I deploy the image I am installing the drivers - I have the all loaded into MDT, and it injects them as it needs to. When I built the reference PC from the Windows 7 CD, the default drivers included on the media were sufficient, and I just used them.

    I've installed Virtual PC on my laptop now, so will hopefully spin up an image in it tomorrow to test.

    I'll experiment with the drivers, and try not adding any in. From what I can see in the logs, the sysprep phase is completing successfully, and existing nicely. Certainly all the drivers have been removed by that stage, as I no longer have any network drivers, audio, anything - it's in it's proper "generalised" state, ready for drivers to be detected/injected.

    I'll let you know how I get on with VirtualPC.

    Thanks for the help - much appreciated!

    Matto :)

    Monday, May 24, 2010 6:50 AM
  • Hi Michael,

    Thanks very much for the info. I've downloaded and installed the beta from the link you have provided. I've upgraded and updated my deploymentshare.

    I've run one capture, but it failed again - same as before. However that was using a previously set-up task sequence. I have since re-built the reference PC, and have created a new "sysprep and capture" task sequence, and am currently running that ask against the reference PC now. Hopefully that will give some better results.

    I had been reading up on the dropped network connection threads, but didn't think that my problem was the same as what the others were reporting. It wouldn't surprise me to find out that it is though. The reference PC does have an instance of MS FFCS installed and running on it, so it's possible that that is interfering with the capture.

    I'll let you know how I get on with this current task sequence, and if it's able to complete. Currently, it's looking more promising.

    Again, thanks very much for the assistance.

    Matto :)

    Monday, May 24, 2010 6:56 AM
  • Hi bjohnrini,

    Thanks very much for the help. I've read through that link, but have hit a problem with deployguy's process, in that I can't get into Device Manager at that stage. Same for Network & Sharing centre - it throws an error (which I didn't write down), and won't let me start it. I'm currently attempting an end-around on it, with both N&SC and Device Manager open currently, in case I run into the same problems with this capture.Did you run into similar problems?

    No SEP on my image, and no Cisco VPN, but I would imagine that ForeFront operates in a similar fashion to SEP and has drivers inserted into the stack, as Michael says. If all else fails, I'll make up a special Group Policy to exclude the FFCS install, and hopefully avoid the issue entirely.

    Thanks for the help!

    Matto :)

    Monday, May 24, 2010 7:02 AM
  • Hi everyone,

    I think I may have stumbled upon the issue. As Michael pointed out above, the MDT beta will pre-stage the boot.wim file onto the reference PC before proceeding to run the sysprep stage (and potentially lose the network). When I was running new Capture task, everything was working correctly, up until the stage of "Applying WinPE image". The script had stalled at that point, and would not continue. When I checked the log files, the last entry in the BDD log was :

    Copying \\CNSLAPTOP99\...\LitetouchPE_x86.wim to C:\sources\boot.wim

    Checking the C:\sources\ folder revealed that there was in fact a boot.wim file there, and it was 160Mb in size.

    At this point the reference PC still had network connectivity. I verified this by pinging the CNSLAPTOP99 deployment machine, and it pinged straight back. This is not surprising, since both machine are directly connected to a 100Mb switch here on my desk. What WAS surprising was the ping time - 699ms. Both machines are gigabit ethernet adapters, directly connected to the same switch. Off that switch is a third patch into the main switching here in the branch office.

    So why the massive ping time? A tracert revealed the issue - the pings (as well as all IPv6 traffic) are all going via the isatap router / Nat64 UAG/DA server in our head office. If I ping my laptop's name, it resolves to the ipv6 address of the isatap adapter, which points all traffic via the UAG server. So to copy the 160Mb WIM file 2 feet from the laptop to the workstation, it's going on a merry round trip of around 4000kms, via a restricted WAN link.

    Both the LAN adapter and the isatap adapter have valid IPv6 link-local addresses - for some reason we're just favouring the remote isatap address as our default path. DirectAccess recognises that it's on the corpnet, and has all of it's gear shut down. IE, the Teredo adapter is offline, the DCA knows it's on the internal LAN, the machine can see the inside/outside website, etc. It's jus tthe isatap address is still up, and routing all communications through the isatap router in the head office.

    In other words, the script hadn't stalled at all - it was in the phase of copying the boot.wim down, it's just that it was going to take a further 12hrs (by it's reckoning).

    So now I'm in the process of trying quick-and-dirty ways to "disable" IPv6 on my laptop, thus forcing the machines to communicate over good ol' IPv4 (which is working as you would expect). This is mainly more to do with the fact that, like 98% of the people on the planet at the moment, I'm more comfortable troubleshooting IPv4 connections than I am delving into IPv6 and isatap and all that goodness. But if it gets to that, then it gets to that.

    This also nicely explains why the WinXP image would capture fine on this same MDT workbench - it was using IPv4 and working correctly. What it DOESN'T explains is why I can deploy an image across to this reference PC quickly, without the traffic going via the WAN. WinPE would be IPv6 aware, I would imagine? Do not know.

    What I HAVE done is jump onto my local DNS server and remove the IPv6 address record (AAAA) for my laptop, leaving only the IPv4. On the reference PC, I've cancelled out of the existing script, and have run an "ipconfig /flushdns" and "nbtstat -R". Now, if I ping my laptop from the reference machine, it resolves the IPv4 address, and communication happen instantly.

    As an aside - I love the new ordering in the Task Sequence. Previously this would have required me to rebuild the reference PC, due to the fact that sysprep had run. Because the script never got that far, the reference PC is still in pristine condition. Thanks MDT team - you've just saved me an hour or two!

    The script is running beautifully now - before it was very sluggish moving between screens. This should have tipped me off that something was wrong, but I simply put it down to cscript running on Win7 with a lower priority or something - it registered on my radar but I dismissed it as irrelevant. What's that saying about assuming things, and what that makes of u and me? :)

    Script is running now, I'll post back in a little while to report whether the image capture has completed. But it copied the boot.wim down to the reference PC in around 3 seconds, instead of 12 hours, so I'm quietly confident.

    Thanks to everyone for their help!

    Matto :)

    Monday, May 24, 2010 8:25 AM
  • And I have a captured image!!! :)

     

    Colour me very happy indeed. The process worked fine - the WIM downloaded quickly, the Sysprep phase ran perfectly and generalised the image, and the computer rebooted into WinPE. The WinPE step was able to quickly dump the image across the network onto the laptop, and the process completed without any errors.

    I'm currently in the process of deploying that image back down onto new hardware to confirm that the image is good and that the capture worked properly. But I really don't expect any more problems, now that I've discovered the root cause of the issue. Once the IPv6/isatap was worked around, the process was just as quick and painless as a Windows XP image/deployment!

    Michael - I don't know if you wanted any more information for your team about this, or if you wanted to feed this back to the DA/UAG guys? I'm not sure that it's a problem/fault per-se. But we do have a fairly vanilla UAG DA setup, in a pretty typical usage scenario (IE, we need isatap and UAG DA for the NAT64, and most people who want UAG DA would be in similar circumstances I would imagine), and have all the normal reasons for looking to use MDT (IE, upgrading mcahines to leverage the fancy UAG DA server that just got put in!). I'm happy to provide whatever documentation you would like, if you would like any. If not, we'll chalk it up to a learning experience.

    Thanks to everyone for your help and suggestions. Good result in the end.

    Kind Regards,

    Matt Russell

     

    Monday, May 24, 2010 8:32 AM
  • Sysprep is going to remove the machine from the domain anyway, so why have the reference machine joined to the domain?

    You can set up MDT to join newly deployed systems to the domain after deploying the image anyway. On a reference machine I always try to make it as neutral as possible and typically use a VM for this purpose. Sysprep will generalize as much as possible removing the system from the domain, and removing the unique machine SID from the registry. You can also prepopulate the domain with new computer accounts and setup MDT to automatically name systems based on a pattern followed by a sequence number or you can just have it use the asset tag right out of the system BIOS by using OSDComputerName=%AssetTag% in the CustomSettings.ini file.

    Friday, June 18, 2010 8:47 PM
  • I just saw the update and I will try tomorrow....Hope it works
    Thursday, July 15, 2010 3:04 AM
  • Is it recommended to build a virtual machine (apply updates, service packs, add all company related apps..) then capture the image for mass deployment with MDT or do the same on a physical PC and then capture the image with MDT?

    Thank you kindly~

    Shah

    Wednesday, November 16, 2011 5:10 PM
  • Is it recommended to build a virtual machine (apply updates, service packs, add all company related apps..) then capture the image for mass deployment with MDT or do the same on a physical PC and then capture the image with MDT?

    Thank you kindly~

    Shah


    Horses for courses I suppose. My reference image is a VM with the company standard apps, latest windows updates and service packs applied. I prefer to use a VM as you can snapshot and rollback when making changes, and running sysprep :).
    Thursday, November 17, 2011 1:03 AM