Introducing Nomad 6.3
Working with Nomad
Technical support for Nomad
Relicensing Nomad client
Resolving common issues
Resolving content integrity (hash checks) issues
Resolving dynamic pre-caching issues
Resolving hard link issues
Resolving Nomad client health issues
Resolving Nomad Dashboard issues
Resolving Nomad peer election issues
Resolving PBA issues
Resolving peer copy over HTTP or HTTPS issues
Resolving remote differential compression issues
Resolving slow content transfer issues
- Known issues
The Nomad client must be licensed during the time of the initial installation or upgrade.
There are three types of Nomad client license:
- Subscription - this type of license expires after the subscription period and must be renewed
- Project Based - this type of license expires after a fixed period (eg Windows Upgrade Project)
- Perpetual (legacy only) - this type of license does not expire but is no longer available for new purchases
- Evaluation - this type of license should only be used in a lab environment and expires after a fixed period
Expiration or corruption of the Nomad license on a machine will cause the Nomad service to stop and content distribution using Nomad will not work, which may also affect Configuration Manager's content distribution.
You will need a new license if:
- Your existing license has expired
- You have increased the number of supported Nomad clients
- You intend to upgrade a major release of Nomad (for example from Nomad 5.x to 6.x)
You will need to re-license Nomad when:
- You have been given a new license
- The existing licensed copy of Nomad has become corrupted
Nomad dashboard - Client health status
The Client health status tile in the Nomad dashboard provides details on unlicensed machines and licenses that are about to expire.
The following are locations where you will need to change the license:
- Configuration Manager Application used to deploy the Nomad client: Relicensing the Nomad Installer Application / Package in Configuration Manager (below).
- Configuration Manager Package used to install Nomad client as part of a Task Sequence in the Install Nomad step.
- Configuration Manager Application/Package used to deploy the Nomad client on Distribution Points: Relicensing the Nomad Installer Application / Package in Configuration Manager (below).
- Configuration Manager Task Sequence step used to configure Nomad client in WinPE: Install and configure Nomad in WinPE.
- Configuration Manager baseline script used in Relicensing the Nomad client with a Configuration Manager Baseline (below).
- Relicensing the Nomad client from the command-line (below).
The Configuration Manager Application and/or Package may have been created using the 1E Endpoint Agent Installer Solution Accelerator, in which the PIDKEY installer property is defined in MSTs.
Relicensing the Nomad Installer Application / Package in Configuration Manager
If your Applications or Packages include the PIDKEY installer property on the command-line, then you will need to edit the command-line.
If your Applications or Packages use MST transform files, or you used 1E's Endpoint Agent Installer Solution Accelerator (EAISA) to ceate Applications and Packages, then you will need to edit the PIDKEY value in each of the MST transform files. Please ensure you make backup copies of the original MST files.
Please ensure you test the updated deployments after modification.
Relicensing Nomad in a Task Sequence
Ensure you change the License Key field here: Install and configure Nomad in WinPE.
Relicensing the Nomad client with a Configuration Manager Baseline
To re-license the Nomad client by creating and applying a Configuration Baseline using Configuration Manager, you will need to run a PowerShell script on the machine that needs to be re-licensed. Use the following resource and example script file to do this:
- Creating and Deploying a Configuration Baseline for Nomad Relicensing.docx
Relicensing the Nomad client from the command-line
You may have created a Configuration Manager package to re-license the Nomad client from the command-line. The manual process is as follows:
- Open an administrator command prompt on the machine that needs to be re-licensed.
- Optional: Navigate to C:\Program Files\1E\NomadBranch or whichever directory you installed Nomad to
- Check NomadBranch.log to see that Nomad is licensed and that the 1E NomadBranch service is running. The log file may be in either C:\ProgramData\1E\NomadBranch\ or C:\WINDOWS\CCM\Logs\.