locked
Sysprep & Capture does not work anymore RRS feed

  • Question

  • I am using vmware to make a master image for several departments. 6 months back all was working fine. Since then i did not use the sysprep and capture task sequence anymore because the images where updated. Now 6 months later i updated the Vmware install with the newest updates from Microsoft. After this i restart the Vmware client and with CTRL-SHFT-F3 log in. Then start the litetouch.wsf to sysprep and capture the client to MDT2013.

    However very soon after starting that a error appears:

    FAILURE (5206) Litetouch deployment did not complete sucessfully.
    FAILURE (5610) nottrue: Verify file \\server\Captureshare$\boot\litetouchPE_x86.wim
    Litetouch deployment failed: return code = -2147467259 0x80004005
    Failed to run the action: Apply Windows PE

    Unknown error (error 000015EA: Source unknown

    Strange thing about above error when i go manually to : \\server\captureshare$\boot there is no litetouchPE_x86.wim but there is a litetouchPE_x86.XML?

    In the time between 6 months ago and now is that i updated the deployment server from MDT2012 to MDT2013 and i have updated the client image.

    I also have deleted the Task Sequence and recreated it but also without luck.

    Has mdt2013 changed something, or is it due to the updates on the client?


    freddie

    Monday, January 19, 2015 1:33 PM

Answers

  • Sounds like the boot image was accidentally deleted. When you updated for MDT 2013, did you also update the ADK? If you update your deployment share from within the workbench, is a new LitetouchPE_x86.wim created?

    -Nick O.

    • Marked as answer by surfer10 Tuesday, January 20, 2015 11:14 AM
    Monday, January 19, 2015 5:18 PM
  • Chances are that there is some kind of environment problem (missing ADK as Nick mentions above).

    Re-update the deployment share again. The LitetouchPE_x86.wim file should appear.

    If it does not appear, then please look for the pemanager.log *somewhere* under teh %temp% directory.

    if that does not reveal anything of interest, then please launch a debugger like http://live.sysinternals.com/Dbgview.exe and *then* re-update the deployment share again and share the output from dbgview.exe

    -k


    Keith Garner - Principal Consultant [owner] - http://DeploymentLive.com

    • Proposed as answer by Keith GarnerMVP Tuesday, January 20, 2015 5:03 AM
    • Marked as answer by surfer10 Tuesday, January 20, 2015 11:14 AM
    Monday, January 19, 2015 10:38 PM

All replies

  • Sounds like the boot image was accidentally deleted. When you updated for MDT 2013, did you also update the ADK? If you update your deployment share from within the workbench, is a new LitetouchPE_x86.wim created?

    -Nick O.

    • Marked as answer by surfer10 Tuesday, January 20, 2015 11:14 AM
    Monday, January 19, 2015 5:18 PM
  • Chances are that there is some kind of environment problem (missing ADK as Nick mentions above).

    Re-update the deployment share again. The LitetouchPE_x86.wim file should appear.

    If it does not appear, then please look for the pemanager.log *somewhere* under teh %temp% directory.

    if that does not reveal anything of interest, then please launch a debugger like http://live.sysinternals.com/Dbgview.exe and *then* re-update the deployment share again and share the output from dbgview.exe

    -k


    Keith Garner - Principal Consultant [owner] - http://DeploymentLive.com

    • Proposed as answer by Keith GarnerMVP Tuesday, January 20, 2015 5:03 AM
    • Marked as answer by surfer10 Tuesday, January 20, 2015 11:14 AM
    Monday, January 19, 2015 10:38 PM