Contents

Installing and upgrading

Summary

How to install, uninstall and upgrade Nomad.

On this page

In this section

Installing the 1E Client for Nomad 7.0

Guidance for deploying the 1E Client onto Windows computers, including installation and uninstallation.

Deploying the Nomad client using Configuration Manager

A step-by-step guide for using Configuration Manager to deploy the Nomad client to computers with the Nomad module enabled.

Installing the Configuration Manager console extensions

A step-by-step guide to installing the Configuration Manager console extensions.

Installing Nomad tools for operating system deployment

A step-by-step guide to installing the Nomad OSD tools, also known as Nomad Branch Tools.

Installing the Nomad download monitor

A step-by-step guide to interactively installing the Nomad download monitor (also known as NomadBranchGUI).

Post-installation tasks

Post-installation tasks that may be necessary to ensure that Nomad will work correctly in your environment.

Upgrading Nomad

A step-by-step guide to upgrading Nomad.

ActiveEfficiency Server

Although not a requirement for generally using Nomad, ActiveEfficiency Server must be installed and available before you can use certain Nomad features.

The following Nomad features require ActiveEfficiency:

Hotfix requirement

If you will be using any of these features with Nomad 7.0 you must install ActiveEfficiency 1.10 with the latest accumulated hotfix available on the 1E Support Portal (https://1eportal.force.com/s/article/LatestHotfixes).

 Ensure you are using the latest version of ActiveEfficiency Server. ActiveEfficiency Server can be installed independently, or by Tachyon Setup as part of a Tachyon installation. Please refer to Tachyon 5.1 for more details about implementing Tachyon.

Nomad installers

Before installing Nomad, make sure your infrastructure meets the Nomad prerequisites.

Download the Nomad zip file from the 1E Support Portal. The following files can be extracted:

NomadBranchAdminUIExt.msiInstaller for 1E Nomad Branch Admin Extensions on Configuration Manager consoles.
NomadBranchGui.msi

Installer for a useful troubleshooting tool to monitor Nomad activity. It has no dependency on Configuration Manager.

Located in the zip's DownloadMonitor folder.

NomadBranchTools.msiInstaller for 1E NomadBranch Tools (for OSD) on Configuration Manager site servers.
PostADSitesandSubnets.ps1

A sample PowerShell script for populating the ActiveEfficiency database to support the following Nomad features:

Located in the zip's scripts folder.

Download the 1E Client zip from the Nomad section of the 1E Support Portal. The following files can be extracted:

1E.Client-x86.msiInstaller for computers that have a 32-bit platform architecture.
1E.Client-x64.msiInstaller for computers that have a 64-bit platform architecture, including Distribution Points.

From version 7.0 the Nomad client is a client module in the 1E Client, which also includes Tachyon and client modules for Shopping/WSA and WakeUp. Please refer to 1E Client 5.1 for installation and configuration details.

Please refer to 1E Client Deployment Assistant 1.5 for information about a wizard that assists Configuration Manager with deployment of 1E Client and PXE Everywhere, guiding you through common settings for clients and deployments.


Installation Order

We recommend you install Nomad in the following order:

1

Tachyon Server

You have a free Tachyon license and can install Tachyon Server provided you only use Tachyon to support the following Nomad features:

If you have purchased a Tachyon license then you can install and use Tachyon for additional features.

To prepare for and install Tachyon, please refer to Tachyon 5.1 - Implementing Tachyon.

2ActiveEfficiency Server

Install an ActiveEfficiency Server if you require any of the features listed under the heading ActiveEfficiency Server.

When installing ActiveEfficiency Server you must enable Nomad Sync to support Nomad Pre-caching or Nomad Dashboard features.

If you are also using Tachyon then you can install ActiveEfficiency 1.10 using Tachyon 5.1 - Tachyon Setup.

If you are not using Tachyon then please refer to ActiveEfficiency Server 1.10 - Implementation.

3NightWatchman Management Center and WakeUp Servers

Install NightWatchman Management Center and WakeUp Servers if you require Nomad integrating with WakeUp.

To prepare for and install NightWatchman Enterprise components please refer to NightWatchman Enterprise 7.3 - Implementation.

4Configuration Manager Console extensions

Install Nomad Configuration Manager Console extensions  on any computers that have Configuration Management Console installed.

Configuration Manager Console should not be running on the computer when NomadBranchAdminUIExt is installed/upgraded.

5Deploy 1E Client on all Configuration Manager Distribution Points

Install 1E Client (with Nomad client module enabled) on Configuration Manager Distribution Points. Enable Tachyon features and other client modules if required. 

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.

6Deploy 1E Client on all Configuration Manager clientsInstall 1E Client (with Nomad client module enabled) on Configuration Manager Distribution Points. Enable Tachyon features and other client modules if required. 
7Nomad Tools for OSD

Install Nomad Tools for OSD on the Configuration Manager primary sites (and extra SMS Providers, if they exist) if Nomad's OSD features are required.

Configuration Manager Console should not be running on the computer when NomadBranchTools is installed/upgraded.

Licensing Nomad in 1E Client

The Nomad client module in 1E Client 4.1 and later does not require a license key. Nomad 7.0 does not require input of a license key, or relicencing when upgrading or updating. Customers are legally bound to use the software within the terms of the 1E software license agreement.

Uninstalling Nomad

If you are uninstalling Nomad, we recommend you do it in the following order:

Configuration Manager Consoles

  1. Close the Configuration Manager Admin Console before you uninstall the Configuration Manager Console extensions and Nomad Tools for OSD.

Nomad clients

  1. If you have installed the Nomad download monitor, uninstall this before Nomad.
  2. Ensure there are no running jobs before you uninstall 1E Cient or permanently disable the Nomad client module.
  3. 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.

Manual uninstallation

1E Client can be uninstalled manually by using Windows Apps and Features (appwiz.cpl). A reboot is not normally required.

Disabling a feature or client module

Please refer to Reconfiguring 1E Client for examples of how to use the -reconfigure command-line to reconfigure the 1E Client.

Uninstallation using the Windows Installer

1E Client can be uninstalled automatically by using a Windows Installer command-line, where the {product code} is dependent on the version of the 1E Client. The example below also includes switches that prevents prompting and restarts, and creates a log file.

msiexec /x {BF6F5FA9-64C8-4B72-A6B6-14A582BF96B8} /qn /norestart /l*vx C:\Windows\temp\1EClient-uninstall.log

Tidy up after uninstallation

After uninstallation of 1E Client, the following is left behind. As with other Windows installers, uninstallation will leave behind any files, folders and registry entries that were created after installation.

LocationArtifactsRecommendation
Installation folderNone.


Logs folder

Log files remain.

Please refer to Log files for log file locations of 1E Client and its client modules.

The log files can be deleted or renamed. If not deleted, then a new installation that uses the same logs folder will continue to use the old log file.

Client\Persist folder remains.

Leave this folder which contains status information about current instructions.

The Persist folder should be deleted only if you do not intend re-installing the 1E Client with Tachyon enabled, or when preparing OS images.

Tachyon client registryHKLM\SOFTWARE\1E\Client\Persist

This registry exists if the Tachyon client feature of the 1E Client is enabled.

It is used to keep a record of hash values for its persistent storage files, which includes status information about current instructions.

This registry key should be deleted only if you do not intend re-installing the 1E Client with Tachyon enabled, or when preparing OS images.

Nomad Cache%ALLUSERSPROFILE%\1E\NomadBranch

The folder should be deleted only if you do not intend re-installing the 1E Client with Nomad enabled.

Downloaded content is retained so that if Nomad client is re-enabled it will be scanned and re-registered, to make available for peer sharing with other Nomad clients.

HKLM\SOFTWARE\1E\Common and HKLM\SOFTWARE\1E\NightWatchman are used by the 1E NightWatchman Agent, previously part of the 1E Agent.

Upgrading Nomad

Refer to Upgrading Nomad for guidance on upgrading to Nomad 7.0