Skip to main content

1E 23.11 (SaaS)

Installing Nomad overview

Nomad installation requirements including installers and installation order.

Nomad installers

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

Nomad requires the installation of:

  • Tachyon Platform

  • 1E Client (with the Nomad client module enabled) installed on Windows devices

  • 1E Client (with the Nomad client module enabled) installed on Configuration Manager Distribution Points.

For full details, refer to:

Content Distribution Tools

Content Distribution Tools are provided in a zip file, you can download from https://support.1e.com/.

NomadBranchGui.msi

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

For information about using this tool, please refer to Nomad Download Monitor.

NomadBranchTools.msi

Installer for

  • 1E NomadBranch Tools (for OSD) on Configuration Manager site servers

  • 1E Nomad Branch Admin Extensions on Configuration Manager consoles (previously NomadBranchAdminUIExt.msi)

For information about installing these tools, please refer to Installing Nomad Branch Tools.

Scripts\CDPurgeSettings.ps1

A sample PowerShell script to view or update Purge Configuration in the Content Distribution Service defined in the ContentDistribution PurgeSettings table if it is configured.

For details of how to use this script, please refer to Content Distribution purge configuration script.

Scripts\ExampleSitesAndSubnets.ps1

Sample script that provides two functions to update sites and subnets in the Content Distribution locations table: DeleteAllLocations and AddLocation().

For details of how to use this script, please refer to Example Single Site script.

Scripts\LocationDiscovery.ps1

Sample script to enable and disable the location discovery feature, along with the option to run it and load site, subnet and information in Content Distribution.

For details of how to use this script, please refer to Example Location Discovery script.

Scripts\PostADSitesandSubnets.ps1

Sample script that scans the Active Directory (AD) environment for all sites and subnets and stores the information in the Content Distribution locations table.

For details of how to use this script, please refer to Example Active Directory Single Site script.

Note

The sample PowerShell scripts can be used to populate the Content Distribution database, to support the following Nomad features:

1E Client

You can download the 1E Client zip by clicking on the 1E Client link in the 1E Support Portal at https://support.1e.com/.You can extract these files:

1E.Client-x86.msi

Installer for computers that have a 32-bit platform architecture.

1E.Client-x64.msi

Installer for computers that have a 64-bit platform architecture, including Distribution Points.

Note

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 Introducing 1E Client for installation and configuration details.

Please refer to Introducing Client Deployment Assistant for information about a wizard that assists Configuration Manager with the 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 Platform

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 toPlanning for 1E.Planning for 1E

2

Nomad Tools for Operating System Deployment (OSD) on Configuration site servers

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

Note

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

Tip

If you are also implementing PXE Everywhere, you may wish to install PXE Everywhere Central on your site server at this point. Please refer to Implementing PXE Everywhere.Implementing PXE Everywhere

3

Install Console extensions on Configuration Manager site servers

Install Nomad Branch Toolson any computers that have Configuration Management Console installed, refer to Installing Nomad Branch Tools.

Note

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

4

Deploy 1E Client to selected 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 Nomad post-installation tasks: 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, as described in Nomad post-installation tasks: Antivirus exceptions.

Tip

You can also optionally install PXE Everywhere Responders to selected clients if you have DHCP snooping enabled in your network. Please refer to DHCP Snooping.DHCP Snooping

5

Deploy 1E Client to selected 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.

Tip

You can also optionally enable PXE Everywhere Agent in the 1E Client.

6

Post-installation tasks

Verify selected clients before deploying the 1E Client to remaining Distribution Points and client devices.

Deploy Console extensions to administrator workstations.

Licensing Nomad in 1E Client

The Nomad client module in 1E Client 4.1 and later does not require a license key. Nomad 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.