Contents
-
Introducing Nomad 6.3
-
Implementing Nomad
-
Working with Nomad
-
Feature Reference
-
Core features
-
Advanced features
-
Client health
-
Cloud Support
-
Deploying Office 365 updates
-
Integrating with WakeUp
-
Managing large package distribution with multicast
-
Nomad Download Pause
-
Nomad FanOut
-
Nomad pre-caching
-
Nomad SECure
-
Peer Backup Assistant (PBA)
-
OS deployment task sequences
-
Set Nomad as download program
-
Create Nomad application policy
-
Delete Nomad application policy
-
Disable Run from distribution point
-
Enable Run from distribution point
-
Install and configure Nomad in WinPE
-
Install Nomad
-
Get migration settings
-
Peer backup assistant Provision Nomad PBA data store
-
Peer backup assistant Finalize Nomad PBA data store
-
Peer backup assistant Locate existing Nomad PBA data store
-
Peer backup assistant Release Nomad PBA data store
-
Peer backup assistant Close Nomad PBA data store
-
Peer backup assistant High-availability
-
Pre-stage content using Nomad
-
Redirect content location to the Nomad cache
-
Save Nomad cache
-
Restore Nomad cache
-
Stage Nomad package
-
1E WSA Actions
-
Set Nomad as download program
-
Single-site download
-
The Download Monitor
-
The Nomad Baseline Wizard
-
Client health
-
Core features
-
Operational best practices
-
Frequently asked questions
-
Feature Reference
-
Technical support for Nomad
-
Training
-
Reference
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).
Actions | Notes |
---|---|
When run, this task:
| This task sequence action:
|
Configurable parameters
Parameter | Default value | Description |
---|---|---|
Name | Action to restore Nomad cache post operating system deployment | Name 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 |
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. |