Contents
Summary
How to install, uninstall and upgrade Nomad.On this page | In this section |
Installing the 1E Client for Nomad 7.0Guidance for deploying the 1E Client onto Windows computers, including installation and uninstallation. Deploying the Nomad client using Configuration ManagerA 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 extensionsA step-by-step guide to installing the Configuration Manager console extensions. Installing Nomad tools for operating system deploymentA step-by-step guide to installing the Nomad OSD tools, also known as Nomad Branch Tools. Installing the Nomad download monitorA step-by-step guide to interactively installing the Nomad download monitor (also known as NomadBranchGUI). Post-installation tasksPost-installation tasks that may be necessary to ensure that Nomad will work correctly in your environment. Upgrading NomadA step-by-step guide to upgrading Nomad. |
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. |
2 | ActiveEfficiency 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. |
3 | NightWatchman 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. |
4 | Configuration Manager Console extensions | Install Nomad Configuration Manager Console extensions on any computers that have Configuration Management Console installed. |
5 | Deploy 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. |
6 | Deploy 1E Client on all Configuration Manager clients | Install 1E Client (with Nomad client module enabled) on Configuration Manager Distribution Points. Enable Tachyon features and other client modules if required. |
7 | Nomad 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. |
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
- Close the Configuration Manager Admin Console before you uninstall the Configuration Manager Console extensions and Nomad Tools for OSD.
Nomad clients
- If you have installed the Nomad download monitor, uninstall this before Nomad.
- Ensure there are no running jobs before you uninstall 1E Cient or permanently disable the Nomad client module.
- 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.
Location | Artifacts | Recommendation |
---|---|---|
Installation folder | None. | |
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 registry | HKLM\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