none
Can't seem to capture windows 8 referance image using MDT 2012 U1.

    Question

  • On a windows 2008 R2 server I have MDT 2012U1 installed. I have created a new deployment share. Added windows 8 OS. I created a basic 'sysprep and capture' task. Updated the deployment share. On my Windows 8 VM I navigated to the lighttouch script. Started it and then answer the couple of questions it askes. When the VM reboots I goes to this screen. After that the VM is... Well crashed. Any ideas what I am doing wrong?


    Just a Simple Admin

    Tuesday, November 20, 2012 10:30 PM

All replies

  • I am getting a similar response from the Task Sequence. I have the same setup as you. Windows 8 Enterprise x64 running in Hyper-V. The same task sequence run fine for Windows 7 Enterprise x64. What gives?

    It doesn't establish the Win PE and Sysprep task doesn't run.

    Excerpt of smsts.log (Errors in BOLD)

    !--------------------------------------------------------------------------------------------! TSManager 11/20/2012 2:58:15 PM 2400 (0x0960)
    Expand a string:           TSManager 11/20/2012 2:58:15 PM 2400 (0x0960)
    Executing command line: cscript.exe "%SCRIPTROOT%\LTIApply.wsf" /PE /STAGE   TSManager 11/20/2012 2:58:15 PM 2400 (0x0960)
    Process completed with exit code 2147749890       TSManager 11/20/2012 2:58:17 PM 2400 (0x0960)
    !--------------------------------------------------------------------------------------------! TSManager 11/20/2012 2:58:17 PM 2400 (0x0960)
    Failed to run the action: Apply Windows PE. Not found (Error: 80041002; Source: WMI)  TSManager 11/20/2012 2:58:17 PM 2400 (0x0960)
    Sending status message . . .         TSManager 11/20/2012 2:58:17 PM 2400 (0x0960)
    Executing in non SMS standalone mode. Ignoring send a task execution status message request TSManager 11/20/2012 2:58:17 PM 2400 (0x0960)
    Set a global environment variable _SMSTSLastActionRetCode=-2147217406    TSManager 11/20/2012 2:58:17 PM 2400 (0x0960)
    Set a global environment variable _SMSTSLastActionSucceeded=false    TSManager 11/20/2012 2:58:17 PM 2400 (0x0960)
    Clear local default environment         TSManager 11/20/2012 2:58:17 PM 2400 (0x0960)
    Let the parent group (Capture Image) decides whether to continue execution   TSManager 11/20/2012 2:58:17 PM 2400 (0x0960)

    The execution of the group (Capture Image) has failed and the execution has been aborted. An action failed.
    Operation aborted (Error: 80004004; Source: Windows)      TSManager 11/20/2012 2:58:17 PM 2400 (0x0960)

    Failed to run the last action: Apply Windows PE. Execution of task sequence failed.
    Not found (Error: 80041002; Source: WMI)       TSManager 11/20/2012 2:58:17 PM 2400 (0x0960)
    Sending status message . . .         TSManager 11/20/2012 2:58:17 PM 2400 (0x0960)
    Executing in non SMS standalone mode. Ignoring send a task execution status message request TSManager 11/20/2012 2:58:17 PM 2400 (0x0960)

    Execution::enExecutionFail != m_eExecutionResult, HRESULT=80004005
    (e:\nts_sms_fre\sms\client\tasksequence\tsmanager\tsmanager.cpp,767)    TSManager 11/20/2012 2:58:17 PM 2400 (0x0960)
    Task Sequence Engine failed! Code: enExecutionFail      TSManager 11/20/2012 2:58:17 PM 2400 (0x0960)
    ****************************************************************************   TSManager 11/20/2012 2:58:17 PM 2400 (0x0960)
    Task sequence execution failed with error code 80004005      TSManager 11/20/2012 2:58:17 PM 2400 (0x0960)
    Cleaning Up. Removing Authenticator        TSManager 11/20/2012 2:58:17 PM 2400 (0x0960)
    Cleaning up task sequence folder        TSManager 11/20/2012 2:58:17 PM 2400 (0x0960)
    DeleteFileW(sVolumeIDFile.c_str()), HRESULT=80070002 (e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,508) TSManager 11/20/2012 2:58:17 PM 2400 (0x0960)
    DeleteFileW(sVolumeIDFile.c_str()), HRESULT=80070002 (e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,508) TSManager 11/20/2012 2:58:17 PM 2400 (0x0960)
    Successfully unregistered Task Sequencing Environment COM Interface.    TSManager 11/20/2012 2:58:17 PM 2400 (0x0960)
    Command line for extension .exe is "%1" %*       TSManager 11/20/2012 2:58:17 PM 2400 (0x0960)
    Set command line: "C:\MININT\Tools\X64\TsProgressUI.exe" /Unregister    TSManager 11/20/2012 2:58:17 PM 2400 (0x0960)
    Executing command line: "C:\MININT\Tools\X64\TsProgressUI.exe" /Unregister   TSManager 11/20/2012 2:58:17 PM 2400 (0x0960)
    ==========[ TsProgressUI started in process 2044 ]==========     TsProgressUI 11/20/2012 2:58:17 PM 1844 (0x0734)
    Command line: "C:\MININT\Tools\X64\TsProgressUI.exe" /Unregister    TsProgressUI 11/20/2012 2:58:17 PM 1844 (0x0734)
    Unregistering COM classes         TsProgressUI 11/20/2012 2:58:17 PM 1844 (0x0734)
    Unregistering class objects         TsProgressUI 11/20/2012 2:58:17 PM 1844 (0x0734)
    Shutdown complete.          TsProgressUI 11/20/2012 2:58:17 PM 1844 (0x0734)
    Process completed with exit code 0        TSManager 11/20/2012 2:58:17 PM 2400 (0x0960)
    Successfully unregistered TS Progress UI.       TSManager 11/20/2012 2:58:17 PM 2400 (0x0960)
    g_TSManager.Run(), HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\tsmanager\tsmanager.cpp,657) TSManager 11/20/2012 2:58:17 PM 2400 (0x0960)
    Error Task Sequence Manager failed to execute task sequence. Code 0x80004005   TSManager 11/20/2012 2:58:17 PM 2400 (0x0960)
    Sending error status message         TSManager 11/20/2012 2:58:17 PM 2400 (0x0960)
    In non SMS staqndalone mode.Ignoring SendStatusMessage request     TSManager 11/20/2012 2:58:17 PM 2400 (0x0960)
    Finalizing logging from process 2404        TSManager 11/20/2012 2:58:17 PM 2400 (0x0960)
    LOGGING: Setting log directory to "C:\Users\ADMINI~1\AppData\Local\Temp\".   TSManager 11/20/2012 2:58:18 PM 2400 (0x0960)
    Process completed with exit code 2147500037       TSMBootstrap 11/20/2012 2:58:18 PM 1252 (0x04E4)
    Exiting with return code 0x80004005        TSMBootstrap 11/20/2012 2:58:18 PM 1252 (0x04E4)
    ==========[ TsProgressUI started in process 1916 ]==========     TsProgressUI 11/20/2012 2:58:18 PM 1776 (0x06F0)
    Command line: "C:\MININT\Tools\X64\TSProgressUI.exe"  /Unregister    TsProgressUI 11/20/2012 2:58:18 PM 1776 (0x06F0)
    Unregistering COM classes         TsProgressUI 11/20/2012 2:58:18 PM 1776 (0x06F0)
    Unregistering class objects         TsProgressUI 11/20/2012 2:58:18 PM 1776 (0x06F0)
    Shutdown complete.          TsProgressUI 11/20/2012 2:58:18 PM 1776 (0x06F0)

    Tuesday, November 20, 2012 11:17 PM
  • Bump!

    Anyone have some helpful ideas?


    Just a Simple Admin

    Friday, November 23, 2012 10:23 PM
  • Yet another bump!

    I too have problems capturing Windows 8 Enterprise.. The default MDT2012u1 Sysprep&Capture TS just reboots the computer.. No errors in bdd.log except for one line about "TScore.dll not found". I have even made a separate capture deploymentshare, but no luck.. 


    Friday, December 21, 2012 10:08 AM
  • I've no problem with capturing an Windows 8 Enterprise image. Here is my setup
    VM: Hyper-V Server 2012
    MDT Server (as Hyper-V 2012 guest).
    OS: Server 2012 Standard (with GUI)
    MDT U1 and Assessment and Deployment Kit.
    Imported full OS, Windows 8 Enterprise x64. All WinPE boot images is x64.
    Two task sequences: One standard deploy client and one standard Sysprep and Capture
    Client (as Hyper-V 2012 guest): Windows 8 Enterprise x64 deployed with MDT.
    Created a snapshot and ran the Sysprep and Capture. MDT run sysprep, apply winpe, reboots, capture the image. And finally the successfully summary screen.
    When i reboot the syspreped and captured windows I get boot error but I don't care about this since I got a snapshot. The image is fine when I deployed it.

     

    Friday, December 21, 2012 3:07 PM
  • I had this issue on a PC not a VM. This issue was only when trying to image with Windows 7. My Windows 8 images were fine. It turns out I had many driver signature issues. May want to look in to this. One way you can verify is to troubleshoot when it brings you to the menu I think F7 was to ignore driver signature issue. "I don't remember the wording sorry" Anyway try that and see if that works.
    Tuesday, April 02, 2013 5:43 PM
  • You needed to install Windows ADK and update the boot.wim

    http://www.microsoft.com/en-gb/download/details.aspx?id=30652



    • Edited by OptimAdam Wednesday, May 15, 2013 3:04 PM
    • Proposed as answer by OptimAdam Wednesday, May 15, 2013 3:04 PM
    Wednesday, April 17, 2013 8:02 AM
  • Found this:

    Sysprep and Capture task sequence in Microsoft Deployment Toolkit (MDT) 2012 Update 1 fails when trying to capture a Windows 8 image that was installed from the media.

    http://support.microsoft.com/kb/2797676

    Confirmed, it fixed my problem
    Tuesday, August 27, 2013 7:01 PM
  • If anyone is still having this issue, do yourself a favor and DO NOT use the Sysprep and Capture task sequence. Change the rules in your deployment share to "SkipCapture=NO" so you're prompted to capture the image. In your task sequence (Standard Client task sequence) to create your reference image add the LTISuspend script.

    http://blogs.technet.com/b/mniehaus/archive/2009/06/27/mdt-2010-new-feature-3-suspend-and-resume-a-lite-touch-task-sequence.aspx

    When your sequence is suspended you can update Windows, add apps you want "baked" into your reference image, etc. Hopefully you did this on a virtual machine so you can capture your image while it's suspended. Why? So you can easily modify your image. Once you continue with the task sequence, it'll save the wim file where you told it to at the beginning of the wizard, thus the skipcapture=no.

    Wednesday, August 28, 2013 9:04 PM