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.


ActionsNotes
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:
  • The 1E Client must be installed with the Nomad module enabled prior to executing the Restore Nomad Cache step when the Activate All option is enabled.

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.

If this option is enabled, Nomad validates all content in the Nomad cache and may take some time to complete. The 1E Client must be installed prior to executing the Restore Nomad Cache step when this option is enabled. Activating the content requires the 1E Nomad Branch service to be running, so when this option is selected the step will check every 10 seconds until the service is available. If it does not start within 10 minutes, the step will fail. 

Without the -ActivateAll option selected, Nomad validates content as it's needed, and so speeds up the OSD process. Any non-activated content will not be available to other computers. It's 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). 

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).