SummaryHow to install, uninstall, licence repair and upgrade Nomad.
On this page
In this section
A step-by-step guide to interactively installing the Nomad client.
A step-by-step guide to installing the Nomad client to all Configuration Manager client machines using Configuration Manager.
A step-by-step guide to installing the Configuration Manager console extensions.
A step-by-step guide to installing the Nomad OSD tools.
A step-by-step guide to interactively installing the Nomad download monitor.
Post-installation tasks that may be necessary to ensure that Nomad will work correctly in your environment.
A step-by-step guide to upgrading 1E Nomad.
Although not a requirement for generally using Nomad, ActiveEfficiency must be installed and available before you can use certain Nomad features. It is therefore highly recommended that the latest version of ActiveEfficiency is installed before installing Nomad. The following Nomad features require ActiveEfficiency:
- Single-site download
- Single-site peer backup assistant
- WakeUp integration (also requires version 7.2.500 of NightWatchman Management Center and WakeUp Servers)
- Nomad Pre-caching
- Nomad Download Pause (also requires Tachyon 3.3 or later)
- Nomad Dashboard
If you plan to use any of these Nomad features you must install or upgrade to the latest version of ActiveEfficiency first, as the Nomad clients need to refer to the location of ActiveEfficiency during deployment.
Before you install Nomad, ensure that you have read and met the Prerequisites. When you download and extract the Nomad zip file, you will find the following:
NomadBranch.msi– installer for 1E NomadBranch for clients on a 32-bit platform architecture
NomadBranch-x64.msi– installer for 1E NomadBranch x64 for clients on a 64-bit platform architecture and on distribution points
NomadBranchAdminUIExt.msi– installer for 1E Nomad Branch Admin Extensions on Configuration Manager consoles
NomadBranchTools.msi– installer for 1E NomadBranch Tools (for OSD) on Configuration Manager site servers
NomadBranchGui.msi– located in the DownloadMonitor folder, installer for a useful tool for troubleshooting Nomad activity. It has no dependency on Configuration Manager.
PostADSitesandSubnets.psl– located in the scripts folder, a collection of sample PowerShell scripts for populating the ActiveEfficiency database with Nomad features (single-site download, high-availability peer backup assistant and WakeUp integration)
We recommend you install Nomad in the following order:
- On the Configuration Manager Consoles install the Configuration Manager Console extensions.
- On the Configuration Manager Distribution Points install the Nomad client.
- On all the Configuration Manager clients install the Nomad client.
- If you are planning to take advantage of Nomad's OSD features, install Nomad Tools for OSD on the Configuration Manager primary sites (and extra SMS Providers, if they exist).
By default, IIS is configured to prevent certain file types from being downloaded. You will need to allow Nomad to download all content as it does not use the Configuration Manager workaround to bypass this Microsoft security feature. We recommend you read IIS request filtering which describes how to update the filtering on all distribution points to enable Nomad to function as expected. You might also want to configure any virus checkers running on your network to make exceptions for the Nomad executables and support files.
Installing Nomad in unattended mode
You can install Nomad (with all its features) in unattended mode by running:
ABCD-1234-5678-8765-4321is your license key. The Nomad executable is installed to
Program Files\1E\NomadBranchand the path is included in the
PATHvariable. The Configuration Manager client is not aware of updates to the
PATHvariable until after a machine reboot.
If you do not want to take advantage of the benefits of the Client Health features, run:
If you had inadvertently installed the Client Health feature, but do not want to benefit from it, you can remove it with:
If you did not install the Client Health feature but want to benefit from it, run:
Here is another example if you want to install Nomad with its FanOut and SSD features enabled:
PLATFORMURLis the hostname/FQDN of your ActiveEfficiency server
The list of command-line arguments you can use to install Nomad in unattended mode is detailed in installer properties.
If you are uninstalling Nomad, we recommend you do it in the following order:
- Close the Configuration Manager Admin Console before you uninstall the Configuration Manager Console extensions and Nomad Tools for OSD.
- If you have installed the Nomad download monitor, uninstall this before Nomad.
- Ensure there are no running jobs before you uninstall the Nomad service.
- Content in the cache may not be automatically deleted when you uninstall Nomad (and some MSI-based installations and files may be required for future application repairs etc). You can delete these files/folders manually or run CacheCleaner.exe -deleteall before you uninstall Nomad.
- Uninstall Nomad from the Add/Remove Programs applet in Control Panel.
Nomad and Nomad multicast are licensed with different keys. If you do not have the respective production license, contact our Sales division for one. You can license Nomad and Nomad multicast by:
|Using installer interactively||Enter a valid license key in the interactive installer setup wizard when prompted.|
If a license key is not provided during installation, Nomad installs with a 30-day evaluation license where you have full functionality, including multicast. If you need an extension to your evaluation, please contact our Sales division.
|Using the installer command-line|
To install a license on the command-line:
|Using the Nomad command-line|
To relicense Nomad from the command-line:
Handling license expiry gracefully
Nomad v6.3 and above can now be configured to pass back responsibility for downloading content to the Configuration Manager Agent when the Nomad license has expired - thereby minimizing the potential impact on downloads. To implement this feature you need to remove the 0x2062 (Nomad return code for unlicensed version of Nomad) entry from SuccessCodes in the NomadBranch registry settings.
In certain circumstances, it may be necessary to repair the Nomad service – this may occur if Nomad program files have been inadvertently deleted,
To repair Nomad:
- Re-run NomadBranch.msi or NomadBranch-x64.msi over an existing installation.
- Choose the Repair option.
When upgrading, we recommend that you follow these general points:
- Upgrades are supported from Nomad 4.1.100
- Update all the site servers and distribution points first before updating Nomad running on the clients to avoid known compatibility issues
- Update all versions of Nomad running on a single subnet at the same time to avoid having hybrid installations where multiple versions are installed on a subnet and making it difficult to troubleshoot issues
- If you are running an earlier version of Nomad and want to upgrade to a later version, please contact 1E support for assistance
If you do not want the benefits of the client health feature when you upgrade, use the command-line:
If you are upgrading Nomad across your entire network, we recommend you follow these steps (if possible the upgrade should be done in a lab or sandbox environment first):
- If you are upgrading to a major release, contact 1E Support for a new license key.
- Install the latest version of Nomad Tools on the site servers.
- Install the latest version of Nomad Console extensions on machines where the Configuration Manager Console is installed.
- Install the latest version of Nomad on Configuration Manager DPs (one at a time and complete the Nomad upgrade on all clients that are managed by that distribution point, subnet by subnet)
- Update the source of the Configuration Manager package/application used to deploy Nomad on clients with the latest version and re-deploy to the clients. Check the Nomad installer logs and Nomad client logs.
- Distribute a test package to a subset of clients to ensure Nomad downloads the package.
- In task sequences, check the Install Package/Application step used to deploy Nomad is using the updated Nomad package/application.
- Re-apply the Nomad steps used in task sequences to ensure the latest updates in the custom task sequence actions are being reflected.
- Update the new license key in Install and configure Nomad in WinPE task sequence step.
- Update distribution points for any relevant boot images.