Pausing a Task Sequence
On philosophical grounds, a task sequence should only be paused when troubleshooting. Pausing a task sequence to actually affect a deployed system or captured image is like pausing a fully automated widget factory to perform a manual step, and should be avoided at all costs as it limits (and even negates) the value of automating the entire process in the first place. However, pausing a task sequence for troubleshooting purposes is useful, as it allows you to manually simulate actions, test outcomes, and review or even update configuration in short order without having to change the task sequence or rerun it from the beginning. You could even pause the VM you are deploying to after the task sequence is paused, enabling ...
Get System Center 2012 R2 Configuration Manager Unleashed: Supplement to System Center 2012 Configuration Manager (SCCM) Unleashed now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
