The Windows Servicing Suite uses Configuration Manager OS Deployment Task Sequences to automate the new computer, computer refresh, computer replace and in-place upgrade deployments. After installing the Windows Servicing Suite, a number of custom Task Sequence steps will be available in the Task Sequence editor that enable Windows Servicing Suite functionality to be incorporated into a Task Sequence. This section provides details on how to build Task Sequences for the various deployment scenarios. You can also use these as reference if you prefer to incorporate the Windows Servicing Suite functionality into your existing Task Sequences.

Nested Task Sequences

From version 4.1 the Windows Servicing Assistant (WSA) supports nested Task Sequences (Task Sequences that include the Run Task Sequence step).

Custom Packages required to support the Windows Servicing Assistant

To support the Windows Servicing Assistant, the Task Sequences defined in this section of the documentation include some custom automation that is implemented through PowerShell scripts. It is necessary to create Packages in Configuration Manager as containers for the scripts and associated configuration files. These Packages are then referenced as required in the Task Sequences, depending on the deployment type.

WSA Scripts package

The WSA Scripts package is a container for scripts and configuration files used in a WSA-enabled Task Sequence, primarily to validate WiFi and VPN credentials supplied by the user in the assistant and establish a VPN connection as required during the Task Sequence execution.

Refer to Windows Servicing Assistant Scripts package for details on creating this package.

Setup WinPE Boot package

The Setup WinPE Boot package is a container for a script (SetupWinPEBoot.ps1) that is required to work around an issue with Configuration Manager, where CM may attempt to stage the boot image on an attached USB drive where that drive is larger than the local hard disk but then fail to boot from it leaving the machine in an unusable state. The script creates a temporary file on the attached USB drive that fills the disk, causing CM to stage the boot image on the intended local disk instead of the larger USB disk.

It is important that a separate package is created for SetupWinPEBoot.ps1 – it should not be included in the WSA Scripts package. The corresponding Teardown.ps1, which deletes the temporary file created to fill the USB disk, can be included in the WSA Scripts package.

Download SetupWinPEBoot.ps1 from the link below and save it to a folder that can be used as a Package source in Configuration Manager.

SetupWinPEBoot.ps1

To create the Setup WinPE Boot Package:

  1. In the Configuration Manager console, click Software Library.
  2. In the Software Library workspace, expand Application Management, and choose Packages.
  3. On the Home tab, click Create and choose Create Package.
  4. On the Package screen of the Create Package and Program Wizard, specify the following information:

    1. Name: Setup WinPE Boot.
    2. Description: Files required by a WSA deployment task sequence.
    3. Manufacturer: Optionally specify a manufacturer name to help you identify the package in the Configuration Manager console. This name can be a maximum of 32 characters. 
    4. Language: Optionally specify the language version of the package with a maximum of 32 characters. 
    5. Version: Optionally specify a version number for the package with a maximum of 32 characters. 
    6. Check the This package contains source files option.
    7. Click Browse to open the Set Source Folder dialog box and specify the location of the source files for the package.

      The computer account of the site server must have read access permissions to the source folder that you specify. 
    8. Click Next.

    Creating a package in Configuration Manager

  5. On the Program Type screen, select the Do not create a program option and click Next.
  6. On the Nomad Setting screen, select the Enable Nomad and configure the Command Line Settings as required option and click Next. 
  7. On the Summary screen, click Next and complete the wizard.
  8. Right-click the package and from its context menu, choose Distribute Content.
  9. In the Distribute Content Wizard, click Next.
  10. Click Add and select the DPs or DP groups required and click Next.
  11. On the Summary screen, click Next and complete the wizard.