Create a [Mostly] Automated Reference Image in MDT – Part 5: Pause/Suspend the Task Sequence

There may be times when you, for one reason or another, have to perform a manual step as part of creating a reference image.  This could be anything from installing a finicky or old piece of software that doesn’t have an unattended installer, making manual changes, or anything else that for whatever reason can’t be automated.  When this happens, you need to temporarily pause or suspend the Task Sequence so that you can perform whatever manual steps are needed.  So, how do you do that?

In the Deployment Workbench, open the Task Sequence you will be using.  Click the Task Sequence tab and then expand the State Restore section.


Click the Add button then choose General > Run Command Line.


Change the Name of this task to something descriptive like “Pause Deployment” and then use the following in the Command line section:

cscript.exe “%SCRIPTROOT%\LTISuspend.wsf”


Highlight the new task and use the Up and Down buttons to position the Pause/Suspend exactly where it should be in your Task Sequence.  Need more than one?  Just create additional Pauses using the steps above.  Once you’re done, click OK and start a deployment with the task.

When your Task Sequence gets to the Pause/Suspend, you’ll see an icon on the Desktop named “Resume Task Sequence.”

04-mdt_suspend_task-task_suspendedRun through any manual configuration that you need including reboots. When you’re done, double-click the “Resume Task Sequence” icon and the Task Sequence will start at the next step.

Series Navigation<< Create a [Mostly] Automated Reference Image in MDT – Part 4: Building the Image
Kyle Beckman

Kyle Beckman

Kyle is a Systems Administrator with 15+ years of experience. He currently works in Higher Education supporting everything from smartphones to desktop PC's to Hyper-V Failover Clusters. (If it has a IP address, he probably supports it!) He has also worked in Small Business IT consulting supporting a wide variety of businesses and non-profit organizations.

Kyle is also the Vice President of the Atlanta Windows Infrastructure and Virtualization User Group (WINVUG).You can find additional articles he's written on
Kyle Beckman


Add a Comment
  1. Handy, thanks!

  2. Great write up! I have a question, is this where you would install Microsoft Office? If not, at what point would you install it?

    1. I usually add an Install Software task inside the task sequence for my reference image. I’ll screenshot that out and post a tutorial.

  3. Found this very helpful. Thanks much!

  4. If I dont have a WSUS server, what should I do?

    1. Stand up a new Windows Server VM and install WSUS on it. You don’t want to create a reference image using the public Windows Update infrastructure.

  5. Great post! Only the LTIsuspend does not work correctly in my deployment, the task sequence will resume after a manual reboot. It’s not what i want :).

    Any thoughts about this? I’m using MDT 2013 update 2.

  6. Doesn’t appear to work in the latest MDT with Windows 10:

    <![LOG[Failed to run the last action: Pause Deployment. Execution of task sequence failed.

  7. Your example uses “smart quotes”! Cutting and pasting it will fail.

    The command still works, but your example has a nasty syntax error that will have most pulling their hair out!

Leave a Reply

Your email address will not be published. Required fields are marked *