This custom task sequence action is used to restore the Nomad cache in the new Operating System during provisioning after Nomad has been installed. It only needs to be run if Save Nomad Cache is run prior to applying the new Operating System.

The Nomad installation can be performed by a standard Configuration Manager package install action which points to the Nomad client installer. This will usually also require a Restart Computer action to update the current environment.

Using the Restore Nomad Cache action with the -ActivateAll option validates all content in the Nomad cache and may therefore take some time to complete. Without the -ActivateAll option selected, Nomad will only validate the required content as it is needed, therefore speeding up the OSD process. Any non-activated content will not be available to other computers. It is possible to run the NomadBranch.exe -ActivateAll as a command-line as a separate thread (so the actual OSD task sequence executes as fast as possible).

When run, this task:
  1. Reads the Nomad cache location from the registry.
  2. Activates all packages in the cache if the Activate All Content checkbox is checked in the custom task sequence action properties. By default this checkbox is unchecked.
This task sequence action:
  • Can only be used after Nomad has been installed onto the new operating system if the Restore Nomad Cache custom task sequence action is configured to preform an activate all command on the packages in the cache.

Configurable parameters

ParameterDefault valueDescription
NameAction to restore Nomad cache post operating system deploymentName for the custom task sequence action.
Description Description for the custom task sequence action.
Operation Link

May be set to one of Copy, Move or Link and either copies, moves or links the %SMSTSMDataPath%\NomadBranchlocation to the existing cache location.

For Link, only a hard link is supported so the Nomad cache and %_SMSTSMDataPath% must be in the same file system.
Activate All Content Disabled by default.Check this to set Nomad to activate all the packages in the cache. This should be done prior to using the contents of the cache. If this option is checked in the custom task sequence action, it must be run after installing Nomad onto the new OS.
The Alternate Cache Path parameter is no longer required as Nomad will read the cache location stored in the Nomad registry (and since we recommend applying this step after Nomad has been installed in the new OS, any alternative path to the default will automatically be picked up and used).