Who can do this?
Configuration Manager administrators with permissions to create Task Sequences in Configuration Manager.
What is it for?
To capture user data and settings from an old computer that is being replaced.
What you need to do

Create the base task sequence first in Configuration Manager and then customize it with logic to execute the Capture Data and Settings Task Sequence.

What is the Capture Data and Settings Task Sequence?

The Capture Data and Settings Task Sequence is used to capture user data and settings from an old computer that is being replaced. The example documented here is designed to be initiated either through the Windows Servicing Assistant (WSA) or through a standard Configuration Manager task sequence deployment.

The task sequence is able to store the data on itself and one or more local peers for retrieval later when the restore takes place on the replacement computer. If the deployment is initiated through WSA and there are no suitable peers on the network, the user can insert USB media which will be used for user data storage. Subsequently, the Restore User Data and Applications task sequence can be used to restore the captured user data.

Replacing devices without user state migration

The Task Sequence detailed below assumes the Windows Servicing Assistant will be used to capture data and settings from an old PC and migrate these, along with applications, to a new PC. If you only want to migrate applications using the Windows Servicing Assistant, you must still create a Capture task sequence, but add conditions to any steps associated with user state migration (including Peer Backup Assistant steps, steps that modify the OSDMigrateAdditionalCaptureOptions and the Capture User State step) so they only execute if the TS variable 1ESkipUserStateCapture is not true. 1ESkipUserStateCapture is set by the WSA Actions - Initialize step if the option Do not capture user files and settings is enabled in the Data Capture tab of the Replace Capture WSA Application settings.

This feature requires Nomad hotfixes Q20391 (Nomad Branch client) and Q20393 (Nomad Branch Tools), which update the WSA Actions - Initialize step to create the 1ESkipUserStateCapture variable.


 

On this page:

Creating the Capture Data and Settings base task sequence

Nested Task Sequences

The Windows Servicing Assistant (WSA) does not currently support nested Task Sequences (Task Sequences that include the Run Task Sequence step). If your Task Sequence includes Run Task Sequence steps, WSA will fail. You will need to copy the steps from the included Task Sequence and paste them into a group in the WSA Task Sequence.

To create the Capture Data and Settings Task Sequence:

  1. From the Configuration Manager console, select the Software Library workspace.
  2. Expand the Operating Systems tree and choose Task Sequences.

    Creating a new task sequence in Configuration Manager

    1. Right-click Task Sequences.
    2. From its context menu, choose Create Task Sequence.
  3. On the Create New Task Sequence screen:

    Creating a new custom task sequence
    1. Select Create a new custom task sequence.
    2. Click Next.
  4. On the Task Sequence Information screen:

    Population the Task Sequence Information screen
    1. In Task sequence name, enter a logical name for it. For example, Capture Files and Settings.
    2. In Description enter a description for it.
    3. A boot image is not required as this will only run in the full OS.
    4. Click Next.
  5. On the Nomad Settings screen:

    Enabling Nomad on the Nomad Settings screen
    1. Select the the Enable Nomad option.
    2. Click Next.
  6. On the summary screen:

    Reviewing your settings
    Click Next.
  7. On the completion screen:

    The Completion screen

    Click Close.

The process for customizing the base task sequence

  1. On the Configuration Manager console, right-click the Capture Files and Settings Task Sequence from the list of task task sequences.
  2. From its context menu, choose Edit. The process and procedure is described below. As you build the task sequence, define the behavior for groups and add logic to each the steps you create.

Customizing the Capture Files and Settings base task sequence for WSS

To customize the newly created task sequence with sequential step to specifically address file capture and settings:

  1.  Initializing the 1E WSA Action step

    In the Task Sequence Editor, click Add and from the menu, choose 1E OSD > 1E WSA Actions.

    On the Properties tabOn the Options tab
    1. Select the Initialize option.
    2. In Shopping URL:, enter the location for the Shopping Web. For example: http://<ShoppingHostHeader>/Shopping/
    1. Click Add Condition > Registry Setting.
    2. Enter the following details:

      Root KeyHKEY_LOCAL_MACHINE
      KeySOFTWARE\1E\NomadBranch
      Conditiongreater than or equals
      Value nameProductVersion
      Value typeREG_SZ
      Value6.3.200
    3. Click OK.
    4. Click Apply.
  2. With the 1E WSA Actions step highlighted, click Add and from the menu, choose New Group.

    On the Properties tabOn the Options tab
    Creating the Main TS group and adding the actions to it
    • Name the group Main TS and ensure that it is positioned as illustrated. Steps 2a-2h are actions for the Main TS group.
    • Select the Continue on error option and click Apply
    1.  Setting Nomad as the download program
      Click Add and from the menu, choose 1E Nomad > Set Nomad as Download Program Ensure the step is positioned as illustrated above and click Apply. No additional settings are required on this step.
    2.  Setting the deployment type

      Click Add and from the menu, choose General > Set Task Sequence Variable.

      On the Properties tabOn the Options tab
      • Enter these values and click Apply

        Step parameterValue
        NameSet DeploymentType=Replace
        Task Sequence VariableDeploymentType
        ValueReplace
      • No action required
    3.  Getting the Migration Settings

      Click Add and from the menu, choose 1E Nomad > Get  Migration Settings .

      On the Properties tabOn the Options tab
      • Ensure that Capture User State option is selected and click Apply.
      • No action required
    4.  Update OSD Migration additional capture options

      This step and the next (e) are optional and provide an example of how to define additional OSD Migration Capture options. If the Task Sequence is initiated through the Windows Servicing Assistant, the OSDMigrateAdditionalCaptureOptions variable may already be defined, so it is necessary to include two steps - one to append your custom options if the variable is already set and another to set the variable with your custom options if it is not already defined. The example shows how to exclude local accounts, which is recommended as these can cause issues on restore if the account does not exist. Click Add and from the menu, choose General > Set Task Sequence Variable.

      On the Properties tabOn the Options tab
      • Enter these values:

        Step parameterValue
        NameUpdate OSDMigrateAdditionalCaptureOptions
        DescriptionAppend options if already exists
        Task Sequence VariableOSDMigrateAdditionalCaptureOptions
        Value%OSDMigrateAdditionalCaptureOptions% /ue:%computername%\*
      1. Click Add Condition and from the menu, choose Task Sequence Variable.

      2. Enter these details:

        VariableOSDMigrateAdditionalCaptureOptions
        Conditionexists
      3. Click OK.
      4. Click Apply.
    5.  Setting the OSD Migrate addition capture options

      Click Add and from the menu, choose General > Set Task Sequence Variable.

      On the Properties tabOn the Options tab
      • Enter these details:

        Step parameterValue
        NameSet OSDMigrateAdditionalCaptureOptions
        DescriptionSets options if not exists
        Task Sequence VariableOSDMigrateAdditionalCaptureOptions
        Value/ue:%computername%\*
      1. Click Add Condition and from the menu, choose Task Sequence Variable.
      2. Enter this condition for the variable:

        VariableOSDMigrateAdditionalCaptureOptions
        Conditionnot exists
      3. Click OK.
      4. Click Apply.
    6.  Adding the PBA: Provision Nomad PBA Data Store

      Click Add and from the menu, choose 1E Nomad PBA > Peer Backup Assistant: Provision Nomad PBA Data Store.

      On the Properties tabOn the Options tab
      • Ensure the Use Nomad's size estimation option is selected. Note that if the Task Sequence is initiated through the Windows Servicing Assistant, the size estimation would have already been completed when the WSA was run and will be used when this step executes instead of re-estimating it.
      1. Click Add Condition and from the menu, choose General >Task Sequence Variable.
      2. Enter these conditions for the variable:

        Step parameterValue
        Variable1EWSA_USBforUSMT
        Conditionnot equals
        ValueTrue
      3. Click OK.
      4. Click Apply.
    7.  Capturing the User State

      Click Add and from the menu, choose User State > Capture User State.

      On the Properties tabOn the Options tab
      • Browse for the Microsoft Corporation User State Migration Tool package. Some of the configuration settings made here will depend upon your capture requirements. 

        For instance, if you require that only those file and folders selected by the user when WSA runs are captured, then select Customize how user profiles are captured and ensure that the Files field remains empty.

        If left set at the default of Capture all user profiles by using standard options, data specified in the standard USMT capture files (MigApp.xml and MigDocs.xml) will be captured along with those folder and file selections made by the user when WSA runs.
      • No action required
    8. Click Add and from the menu, choose 1E Nomad PBA > 

       Adding the PBA: Finalize Nomad PBA Data Store

      Peer Backup Assistant: Finalize Nomad PBA Data Store .

      On the Properties tabOn the Options tab
      • If necessary, set High Availability options to make copies of the data on multiple peers for redundancy. For WSA deployments at remote locations, High Availability is always disabled and overrides any setting made here.
      1. Click Add Condition and from the menu, choose Task Sequence Variable.
      2. Enter the following details:

        Variable1EWSA_USBforUSMT
        Conditionnot equals
        ValueTrue
      3. Click OK.
      4. Click Apply.
  3.  Finalizing the task sequence

    Click Add and from the menu, choose 1E OSD > 1E WSA Actions – ensure that this is positioned in the root of the task sequence outside of the Main TS group.

    On the Properties tabOn the Options tab
    • Select the Finalize option
    1. Click Add Condition and from the menu, choose Task Sequence Variable.
    2. Enter the following details:

      Variable1EWSA
      Conditionequals
      Valuetrue
    3. Click OK.
    4. Click Apply.
  4. Click OK to save the task sequence.