Contents
-
Introducing Nomad
-
Implementing Nomad
-
Using Nomad
-
Nomad features
-
Troubleshooting
-
Training
-
Reference
-
Nomad app
-
Nomad tools
-
Nomad OS Deployment task sequence actions
-
Supported Platforms
-
1E Companion Products
-
Communication ports
-
Log files
-
Nomad architecture
-
Nomad command-line switches
-
Nomad installer properties
-
Nomad registry values
-
Nomad return codes
-
FIPS compliant communication encryption
-
Glossary
-
Nomad Product Packs reference
-
Nomad release information
-
Scripts
-
Nomad app
Summary
All the Nomad related tables of information, such as supported platforms, communications ports etc.
In this section...
Nomad app
The Nomad app provides visibility of content distribution activity and cache status for content distributed by both Nomad and Delivery Optimization. This includes Configuration Manager content distributed with Nomad and Software Updates content distributed with either Nomad or Delivery Optimization.
- Overview page
The Nomad app Overview page provides a visual snapshot of download activity.
- Content page
Content titles list the unique contents synced from MEMCM. This includes applications, packages and software updates.
- Task Sequences page
The Task Sequences page lists the configured task sequences.
- Devices page
The Devices page lists every device registered to Nomad.
- Nomad Sites page
The Nomad Sites page is primarily designed to show how the network is being used for content distribution in different locations.
- Client Health page
The Client Health page shows Nomad related device status information from the Guaranteed State app.
Nomad tools
Tools that can help troubleshoot or configure Nomad.- Nomad Download Monitor
The Nomad Download Monitor tool (also known as NomadBranchGUI) is useful for administrators for troubleshooting downloads as they view the status of downloads on local and remote Nomad client devices.
- Nomad Baseline wizard
The Nomad Baseline wizard is used to create a Configuration Manager (CM) Baseline from the Configuration Manager console for settings related to Nomad.
- CacheCleaner
The downloaded content in the Nomad cache consume disk space therefore management of the cache is critical. Because files may be re-used and distributed to other devices on the same subnet or site, the simple solution of deleting the files as soon as they have finished downloading and executing is not sufficient. Instead, Nomad has a sophisticated cache cleaner utility that automatically but intelligently maintains control over the cache's disk usage.
Nomad OS Deployment task sequence actions
Nomad support for Configuration Manager OS Deployment.- 1E Nomad task sequence actions
Set Nomad as Download Program
SetsSMSTSNomad.exe
as the download program during a task sequence. This is accomplished by setting theSMSTSDownloadProgram
task sequence variable toSMSTSNomad.exe
.Create Nomad Application Policy
Creates a Nomad application policy and is used in a task sequence during the provisioning phase prior to any applications being installed. It uses the NomadPackageLocator.exe command-line switches 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 action.Delete Nomad Application Policy
Deletes a Nomad application policy previously created using the Create Nomad Application Policy action. It uses the NomadPackageLocator.exe command-line switches tool to remove the previously created Nomad application policy.Install and Configure Nomad in WinPE
Installs and configures Nomad in WinPE. Typically, to support the use of pre-staged content.Save Nomad Cache
Saves 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
Restores the Nomad cache in the new Operating System during provisioning after the 1E Client has been installed with the Nomad module enabled. This action only needs to be included in the task sequence if Save Nomad Cache is run prior to applying the new Operating System.
Get Migration Settings
Provides support for optional encryption in Nomad PBA, and Provides computer association details in 1E Application Migration. Used in computer Replace and Refresh (Wipe and Load destructive and non-destructive) scenarios, it is configured to run under either the capture phase or the restore phase, depending on the scenario.
It is independent of 1E Nomad PBA task sequence actions but is designed to be used in conjunction with them.
Stage 1E Client Package
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.Install 1E Client
Installs 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. - 1E Nomad PBA task sequence actions
Peer Backup Assistant: Provision Nomad PBA Data Store
Provisions 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
Closes 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
Finds saved user data, prior to restoring user state using the USMT Restore User State action.Peer Backup Assistant: Release Nomad PBA Data Store
Releases saved user data in the Nomad cache, after restoring user state with USMT Restore User State.Peer Backup Assistant: Close Nomad PBA Data Store (deprecated)
This step 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 (deprecated)
This step is deprecated, and you should use the Peer Backup Assistant: Finalize Nomad PBA Data Store instead. Existing deployments will still work, but you cannot modify them. Going forward, we recommend using its replacement. - 1E Nomad Pre 6.0 task sequence actions
Pre-stage Content Using Nomad
Pre-stages 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.Redirect Content Location to the Nomad Cache (deprecated)
This action is deprecated and is currently provided for backwards compatibility only, Use Pre-stage Content Using Nomad instead.
Enable Run from Distribution Point
Used in the following instances:- In conjunction with the pre-stage content using Nomad action to avoid making a local copy of the Nomad share.
- It is used during the provisioning phase, prior to any package being installed, to enable classic packages to run from the DP. This is so that
SMSNomad.exe
can be used as an alternative download provider during OSD.
Disable Run from Distribution Point
Reverts the task sequence variables that were set using the Enable Run from Distribution Point custom task sequence action back to their default values. - 1E OSD task sequence actions
1E WSA Actions
The 1E WSA Actions action is an essential component of the WSA deployment task sequence. Its position and configuration within the task sequence is critical to ensuring the task sequence completes successfully. The action performs one or more of the following functions depending on the selection made when configuring the step:
- Initialize
- Refresh Content Location
- Switch between online and offline content
- Finalize.
- Peer Backup Assistant - PBA
The Peer Backup Assistant (PBA) feature enables files and settings data to be backed-up to a peer device so that they can be maintained when the device 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 devices can be used to provide this storage. The risk of losing user data through the migration process is also greatly reduced in the process.
Supported Platforms
A list of all the platforms supported by Nomad, and the software required to allow Nomad to be installed or to work.
1E Companion Products
A list of the feature dependencies between Nomad and other 1E companion products.
Communication ports
Log files
Names and locations of log files created by Nomad.
Nomad architecture
A description of Nomad and its components and how they connect.
Nomad command-line switches
Nomad accepts configuration changes that can be specified on the command-line. The command-line options for Nomad should be denoted using double dashes (--) or double slashes (//) to distinguish them from the main install command-line.
For Configuration Manager additional Nomad options for controlling the Nomad Provider are denoted using double plusses (++).
- SMSNomad.exe command-line switches
This executable does not normally need to be run on a command-line, but details are provided here for reference purposes.
It is normally installed as part of Nomad and configured using Configuration Manager Admin console extensions. Please refer to Distributing software with Nomad and Configuration Manager: Nomad tab for different types of content.
- NomadBranch.exe command-line switches
This executable does not normally need to be run on a command-line, but details are provided here for reference purposes.
It is normally installed as part of Nomad and configured using Configuration Manager Admin console extensions. Please refer to Nomad tab for different types of content. It is also available in Nomad OSD tools in order to include in WinPE images so that Nomad can be used in OS Deployments. Please refer to Installing Nomad tools for Operating System Deployment OSD.
- NomadPackageLocator.exe command-line switches
NomadPackageLocator.exe is used by the Nomad custom task sequence actions, we recommend that these are used to perform the appropriate functions in preference to the command-line, but details are provided here for reference purposes.
It is installed as part of Nomad. It is also available in Nomad OSD tools in order to include in WinPE images so that Nomad can be used in OS Deployments. Please refer to Installing Nomad tools for Operating System Deployment OSD.
- TSEnv2 command-line switches
TSEnv2 is an executable that can be used primarily to set or change task sequence environment variables, including "readonly" variables, those starting with an underscore, which cannot be changed with ConfigMgr's tsenv.exe tool. It also has other related functions, some of which can be performed by the NomadPackageLocator tool, refer to NomadPackageLocator.exe command-line switches for details.
- CacheCleaner.exe command-line switches
CacheCleaner is an executable that can be used to explicitly purge the Nomad cache. By default, the Nomad cache is not purged unless there is an active download. In most cases, available disk space is not really an issue, but there may be circumstances where you may want to manage the cache to keep the disk usage overhead to a minimum. Please refer to Cache management for further information about managing the cache.
Nomad installer properties
Subject-oriented lists of Nomad installer properties. There are two Nomad installers that have usable installer properties: 1E.Client-x64.msi (and its x86 version) and NomadBranchAdminUIExt.msi.
- Nomad client alphabetic installer properties
The following table shows the supported installer properties for the Nomad client module of the 1E Client.
Each installer property listed below has a link to its corresponding registry value page.
Nomad client settings
Nomad registry values
- Alphabetic NomadBranch registry values
The following table shows the supported NomadBranch registry value and any associated installer properties. Installer properties must be upper-case, and those that use numeric values must be set using decimal integers on the command-line.
Registry value Description Platform\PlatformURL
The URL of the Tachyon Platform, specifically the Tachyon Background Channel, which provides a reverse proxy for the Content Distribution component of Tachyon Platform. Usually of the formhttps://<BackgroundChannelServer>:<BackgroundChannelPort>/Background/
- Nomad client registry values and installer properties
The following table shows supported Nomad client registry values and any associated installer properties. After installation, any enhancements to Nomad functionality must be carried out through its registry values.
Installer properties usually map to similarly named registry values, but not always, and some have no corresponding registry values.
Nomad return codes
The following is a list of the Nomad return codes and their descriptions.
This list is subject to change with each release of Nomad, and provided for reference only.
Return Code | Description |
---|
FIPS compliant communication encryption
Nomad has always provided encryption for most of its communications and uses an advanced FIPS compliant encryption algorithm. The United States Federal Information Processing Standard (FIPS) http://en.wikipedia.org/wiki/FIPS_140-2 is a standard that defines security requirements for software used by the U.S. federal government. It stipulates that applications that encrypt any sensitive data should use only a certain set of approved encryption algorithms.
Glossary
A glossary of Nomad 7.1 terminology.
Nomad Product Packs reference
Reference information for Nomad feature-related Product Packs that are included in the Tachyon Platform zip. These Product Packs are required to support various features of Nomad.- 1E Nomad product pack
Classic product pack used to create the 1E Nomad instruction set in Tachyon, required by the following Nomad 7.1 features:
- Downloads tab on Device views - instructions used to populate details about Content download and other Nomad features
- Nomad Download Pause - instructions used by the CM Admin Console extensions
- Instructions to help with the following Nomad features: Nomad cache, CacheCleaner, Single Site Download, Nomad jobs, NomadBranch service.
- Nomad Client Health Integrated Product Pack
Integrated Product Pack used to create the Nomad Client Health instruction set and Nomad Client Health policy.
For more information please refer to Guaranteed State 1.5 - Nomad Client Health Policy.
Nomad release information
Details of the Nomad 7.1 release history, current release notes and details of third-party licenses.
- Nomad features by release
A list of the Tachyon features organized by the release they were implemented in. Links through to the features have been provided for convenience.
- Licenses
Details of licenses for the 3rd party components used by Nomad 7.1.
You need to add Include Page macros to reference the third-party licenses for all the open licensed third-party components. The source pages can be found here: _Licenses and in its child pages.
Scripts
This page is included from the Tachyon Platform 5.2 documentation.