OS deployment task sequences

Nomad can integrate with OSD strategies to maximize the efficiency of distributing large OS content across the network. It does this by providing a number of Task Sequence steps that can be integrated directly into your OSD Task Sequences.

• Set Nomad as download program — This custom task sequence action is used to set SMSTSNomad.exe as the download program during a task sequence. This is accomplished by setting the SMSTSDownloadProgram task sequence variable to SMSTSNomad.exe.
• Create Nomad application policy — This custom task sequence creates a Nomad application policy and is used during an OSD task sequence during the provisioning phase prior to any applications being installed. It uses the NomadPackageLocator tool to enable Nomad to be used as an alternative download provider during provisioning. When the application policy is no longer required it can be removed using the Delete Nomad application policy custom task sequence.
• Delete Nomad application policy — This custom task sequence deletes a Nomad application policy previously created using the Create Nomad application policy custom task sequence action. It uses the NomadPackageLocator tool to remove the previously created Nomad application policy.
• Disable Run from distribution point — This custom task sequence is used to revert the task sequence variables set using the Enable Run from distribution point custom task sequence action to their default values.
• Enable Run from distribution point — This custom task sequence can be used in the following instances:
• Install and configure Nomad in WinPE — This custom task sequence action is used specifically to install and configure Nomad in WinPE – typically done in order to support the use of pre-staged content.
• Install 1E Client — This task sequence action is used to install the 1E Client. The Stage 1E Client Package step must be to be included before this step in the Task Sequence. The 1E Client installer and any Transform or Patch that should be applied during installation must be included in the 1E Client Package referenced in the Stage 1E Client Package step.
• Get migration settings — Provides support for optional encryption in Nomad PBA.  Provides computer association details in 1E Application Migration. Used in computer Replace and Refresh (Wipe and Load destructive and non-destructive) scenarios. This task can be configured to run under either the capture phase or the restore phase. Its behavior differs depending on which phase it's run under.
• Peer backup assistant Provision Nomad PBA data store — This custom task sequence action is used to provision a PBA data store prior to saving user state using USMT. It is the first step of the Peer backup assistance sequence (USMT Capture User State follows).
• Peer backup assistant Finalize Nomad PBA data store — This custom task sequence action is used to close the connection to the PBA data store after user state is saved with USMT Capture User State.
• Peer backup assistant Locate existing Nomad PBA data store — This custom task sequence action is used to find saved user data, prior to restoring user state using USMT Restore User State.
• Peer backup assistant Release Nomad PBA data store — This custom task sequence action is used to release saved user data in the Nomad cache, after restoring user state with USMT Restore User State.
• Pre-stage content using Nomad — This custom task sequence action is used to pre-stage content using Nomad either in WinPE or a full Microsoft Windows operating system. It uses the NomadPackageLocator tool to locate any locally available copies of content, as set in the References in the custom task sequence action properties. If no local copies are available ,it will download the content from the DP and store it locally. It then configures the task sequence to use this locally stored content.
• Save Nomad cache — This custom task sequence action is used to save the Nomad cache either in WinPE or a full Microsoft Windows operating system. It copies, links or moves previously downloaded content to the protected task sequence runtime folder so that it is not deleted by the standard Apply Operating System task sequence action.
• Restore Nomad cache — This custom task sequence action is used to restore the Nomad cache in the new Operating System during provisioning after the 1E Client has been installed with the Nomad module enabled. Refer to Stage 1E Client Package and Install 1E Client for details on how to install the 1E Client in the Task Sequence. Restore Nomad Cache only needs to be included in the Task Sequence if Save Nomad Cache is run prior to applying the new Operating System.
• Stage 1E Client Package — This custom task sequence step downloads the 1E Client package ready for installation by the Install 1E Client Task Sequence step. It's typically executed in Windows PE and must be included before the Install 1E Client step in the task sequence.
• 1E WSA Actions — The WSA Actions step is an essential component of the WSA deployment task sequence. Its positioning and configuration within the task sequence is critical to ensuring the task sequence completes successfully. The step performs several different functions depending on the selections made when configuring the step.
• Peer backup assistant Close Nomad PBA data store — This custom task sequence has been replaced by Peer backup assistant Finalize Nomad PBA data store. Existing deployments will still work but you cannot modify them. Going forward, we recommend using its replacement.
• Peer backup assistant High-availability — This custom task sequence is deprecated and you should use the Peer backup assistant Finalize Nomad PBA data store task sequence instead. Existing deployments will still work but you cannot modify them. Going forward, we recommend using using its replacement.
• Redirect content location to the Nomad cache — This action is deprecated and is currently provided for backwards compatibility only, Use Pre-stage Content Using Nomad instead.

Peer Backup Assistant - PBA

The Peer Backup Assistant (PBA) feature enables files and settings data to be backed-up to a peer computer so that they can be maintained when the computer is being migrated to a new Operating System. Using PBA, you can avoid the cost of State Migration Point servers to hold the backup data, as peer computers can be used to provide this storage. The risk of losing user data through the migration process is also greatly reduced in the process.

• NMDS_POLL — The NMDS_POLL argument is available on either the NomadPackageLocator.exe (recommended) or NomadBranch.exe service command-line. When run, it places a request for a network share and size associated with it. It must only be used within a task sequence.
• NMDS_COMPLETE — The NMDS_COMPLETE argument is available on the NomadPackageLocator.exe (recommended) or NomadBranch.exe service argument-line. It indicates that all user data has been copied to the PBA share and the connection can be closed. When run, it disconnects from its associated share and fixes its contents for the duration defined in the Nomad PostCompleteTimeoutHours registry value on the machine where the share is hosted. It is only for use within a task sequence.
• NMDS_HA — The NMDS_HA argument is available on the NomadPackageLocator.exe (recommended) or NomadBranch.exe service argument-line. It creates additional backup copies of the user data that has been copied to the PBA share, so it must be run after the share has been closed using NMDS_COMPLETE. It is only for use within a task sequence.
• NMDS_FIND — The NMDS_FIND argument is available on the NomadPackageLocator.exe (recommended) or NomadBranch.exe service argument-line. When run, it locates and connects to the share associated with it. It is only for use in a task sequence.
• NMDS_DELETE — The NMDS_DELETE argument is available on the NomadPackageLocator.exe (recommended) or NomadBranch.exe service argument-line. When run, it deletes the share, contents and user associated with the shared cache. It is only for use in a task sequence.
• Secondary PBA backup data store — Support for this configuration is deprecated and is currently provided for backwards compatibility only. Use high-availability PBA instead. The PBA task sequence dialogs do not support this option, therefore some scripting would be required to achieve the same functionality.