locked
Suspend task sequence in MDT2013 RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    In MDT 2012 I knew how to create a suspend task sequence in the middle of a deploy and capture so I could install software that couldn't easily be deployed.

    I used  <cscript.exe “%SCRIPTROOT%\LTISuspend.wsf”> .

    In MDT 2013 I can see the script still exists but the new layout has confused me.

    I've inserted it after Install applications and before Restore Group.

    Is this correct? If its not, where is the correct place to put it, assuming it still works.

    Friday, November 15, 2013 10:04 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    As you said configuring it in the State Restore Group after Install Applications will work just fine
    Friday, November 15, 2013 11:09 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    If I click on the created icon on the desktop it errors out.

    The target for the shortcut is< D:\Windows\system32\wscript.exe "D:\_SMSTaskSequence\Scripts\LTISuspend.wsf" /resume >

    Error message:

    Windows Script Host

    Can not find script file "D:\_SMSTaskSequence\Scripts\LTISuspend.wsf"

    I've setup SCCM 2012r2 with MDT2013.

    The task is running as a MDT2013 task sequence.

    Explorer tells me that the OSDisk is D.

    Disk mamagement tells me I have a BDE drive and a OSDisk (D:)

    Net share has A D$ referencing D:\, IPC$, and ADMIN$ D:\WINDOWS.

    I'm unsure where I go from here.

    Sunday, November 17, 2013 11:10 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I think my issue is trying to use a deploy and capture task sequence within SCCM.

    I've abandoned using MDT within SCCM and instead gone to use MDT on my SCCM server.

    Partly due to the recommendation from here.

    http://keithga.wordpress.com/2013/09/17/osdpreservedriveletter/

    "Don’t use SCCM to capture images. MDT is the recommended best practice for image creation. SCCM should then be used to deploy the captured images. Then remove the OSDPreserveDriveLetter step from the task sequence, or set it to “True” (same thing)."

    Monday, November 18, 2013 4:56 AM