none
MDT 2013 Task Sequence return to command prompt RRS feed

  • Question

  • Hey All,

    I created a fresh MDT 2013 share on a 2008 R2 machine that also holds the WDS for PXE.

    Right after it applies DISM, it restarts back to a command prompt, my logs don't report any errors. When I type exit, the machine reboots and the task sequence continues as normal. Here is the peice in my dynamic log where it stops logging. Last line is where it stops and I type exit.

    ZTIdrivers processing completed successfully. ZTIdrivers 11/3/2014 11:11:59 AM 0 (0x0000)
    Event 41001 sent: ZTIdrivers processing completed successfully. ZTIdrivers 11/3/2014 11:11:59 AM 0 (0x0000)
    Will boot into Windows PE architecture x64 to match OS being deployed. ZTIWinRE 11/3/2014 11:12:00 AM 0 (0x0000)
    OSDTargetDriveCache was determined earlier : C: ZTIWinRE 11/3/2014 11:12:00 AM 0 (0x0000)
    Property OSDTargetDriveCache is now = C: ZTIWinRE 11/3/2014 11:12:00 AM 0 (0x0000)
    Property OSDisk is now = C: ZTIWinRE 11/3/2014 11:12:00 AM 0 (0x0000)
    WinRE is not enabled, Skip. ZTIWinRE 11/3/2014 11:12:00 AM 0 (0x0000)
    ZTIWinRE processing completed successfully. ZTIWinRE 11/3/2014 11:12:00 AM 0 (0x0000)
    Event 41001 sent: ZTIWinRE processing completed successfully. ZTIWinRE 11/3/2014 11:12:00 AM 0 (0x0000)
    Property PHASE is now = STATERESTORE ZTINextPhase 11/3/2014 11:12:00 AM 0 (0x0000)
    ZTINextPhase COMPLETED.  Return Value = 0 ZTINextPhase 11/3/2014 11:12:00 AM 0 (0x0000)
    ZTINextPhase processing completed successfully. ZTINextPhase 11/3/2014 11:12:00 AM 0 (0x0000)
    Event 41001 sent: ZTINextPhase processing completed successfully. ZTINextPhase 11/3/2014 11:12:01 AM 0 (0x0000)

    A little further along I noticed it changed the state to dirty. But I don't think that's related. Could be wrong.


    -G

    Monday, November 3, 2014 5:08 PM

Answers

  • While in Windows PE, the cmd.exe window will appear in one of two scenarios:

    1. The user pressed the F8 key.

       or

    2. Litetouch.wsf returned some kind of failure during processing. This is weird.

    Under what instances would the Litetouch.wsf crash (fail)? Well, the most common scenario is that there are some mixmatched source files in MDT. Updating the deployment share could fix the problem.

    The only other way to know for sure is to run the program in a debugging mode.  When you first boot up to WinPE, instead of starting the deployment wizard, when you are at the welcome wizard, break out into the cmd.exe prompt (not by pressing F8). Then run the command:
    cscript.exe x:\deploy\scripts\litetouch.wsf /debug:true /debugcapture
    At the end of the script we should see an error with a line number.

    If we don't see an error then something else is going on.


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

    Monday, November 3, 2014 7:44 PM
    Moderator

All replies

  • While in Windows PE, the cmd.exe window will appear in one of two scenarios:

    1. The user pressed the F8 key.

       or

    2. Litetouch.wsf returned some kind of failure during processing. This is weird.

    Under what instances would the Litetouch.wsf crash (fail)? Well, the most common scenario is that there are some mixmatched source files in MDT. Updating the deployment share could fix the problem.

    The only other way to know for sure is to run the program in a debugging mode.  When you first boot up to WinPE, instead of starting the deployment wizard, when you are at the welcome wizard, break out into the cmd.exe prompt (not by pressing F8). Then run the command:
    cscript.exe x:\deploy\scripts\litetouch.wsf /debug:true /debugcapture
    At the end of the script we should see an error with a line number.

    If we don't see an error then something else is going on.


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

    Monday, November 3, 2014 7:44 PM
    Moderator
  • Thanks so much Keith,

    You were correct! I checked all my tools versions on the server and regenerated my boot images. FIXED! Definitely a mix match of tools injected into PE that was causing the issue.

    Still getting a Dirty deployment warning, but it sucessfully makes it through deployment without user interaction, so im happy!


    -G


    Wednesday, November 12, 2014 8:26 PM