The Windows Servicing Assistant (WSA) scripts package is used to host files required to support WSA functionality in a task sequence. This guide describes the provisioning of the files and creation of the WSA Scripts package. Creation of a new package is not mandatory; the files listed below can be hosted in any existing OS deployment package such as the MDT Toolkit.

On this page:

Automating VPN connection in a task sequence

Most of the scripts and tools in the WSA Scripts package are for establishing a VPN connection from within a task sequence. VPN solutions vary considerably, and any given VPN solution will support several authentication methods (e.g. username and password, certificates, secure ID tokens etc.). When planning to use WSA for remote users, you must first understand what authentication methods are in use in your organization. Ideally your VPN vendor will provide a command-line tool that allows the VPN connection to be established from the command line without user interaction.

If you are using username and password authentication, the WSA is able to collect these user credentials from the user and store them in the Windows credential store for later use. When the task sequence executes, the WSA Actions Initialize step reads these credentials into task sequence variables. These variables can then be passed to a command line executed in a script to establish the VPN connection.

If you are using other authentication methods, you will need to engineer a method to provision or submit these in the task sequence. Below are some sample scripts for VPN solutions and authentication methods that we have developed for various customers. You can use these as a base for working with other VPN solutions and authentication methods.

Creating the WSA Scripts package

Download or create the appropriate scripts and tools for your particular VPN solution and authentication method as described above. If you decide to use an existing package (e.g. MDT Toolkit), add the files described above into the package source folder and update distribution points. If you are creating a new WSA Scripts package, place these files in a source folder that is accessible to the CM site server and follow the steps below. 

  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:

    Creating a package in Configuration Manager

    1. Name: WSA Scripts.
    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.
  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.