Summary

A checklist of infrastructure prerequisites and dependencies that most organizations would require in order to install Nomad.

On this page

Installation account permissions

InstallerRights required

Nomad agent: NomadBranch-x64.msi, NomadBranch.msi

Download GUI tool installer: NomadBranchGui.msi

Local Administrator

ConfigMgr console extensions: NomadBranchAdminUIExt.msi

ConfigMgr administrators use console extensions to configure Nomad content download, custom task sequence steps, Nomad dashboard and Nomad Content Pause.

It is recommended the installer is run on all ConfigMgr console installations.

Local Administrator

ConfigMgr OSD Tools: NomadBranchTools.msi

The installer copies the Nomad binaries to the ConfigMgr site installation folder .\OSD\bin\<Architecture> on the SMS Provider server. This enables the files to be injected into the OSD boot image allowing Nomad to be used during the WinPE deployment phase. The installer will also extend the ConfigMgr site WMI namespace to include definitions of the 1E Nomad built in task sequence steps.

The installer must be run on a server hosting the SMS Provider site system role to which the ConfigMgr console is connected.

Local Administrator


Infrastructure prerequisites

CategoryProductNotes

Supported OS

  • Windows Server 2019
  • Windows Server 2016
  • Windows Server 2012 R2
  • Windows 10 CB 1903
  • Windows 10 CB 1809
  • Windows 10 CB 1803
  • Windows 10 CB 1709
  • Windows 10 CB 1703
  • Windows 8.1

Nomad and Nomad Multicast require MSXML6 to communicate with the Configuration Manager client. This is present in all the supported versions of Windows (with the required service packs).

The recommended way to facilitate Nomad peer-to-peer communications is to enable Windows File and Print Sharing. If this is not feasible on your network environment, configure Nomad to use a different means to access network shares.

For Windows Server 2012 R2 Core Server installations:

  • Only 64-bit versions are supported
  • You must enable DirectAccess feature – VPN is a prerequisite for the Nomad agent. The agent fails to install if this feature is not enabled.
  • Distribution Points on this OS do not support PXE or Multicast.

For Windows Server 2016 Core Server installations:
  • Only 64-bit versions are supported
  • Distribution Points on this OS do not support PXE or Multicast.

For Windows 7 SP1, both 32 and 64-bit versions of Enterprise and Professional editions are supported.

Windows Embedded versions are customizable Windows OS, best suited for embedded or kiosk usage and may only have a small subset of the full operating system features. Support for Windows Embedded has to be evaluated on a case-by-case basis.

For Windows embedded OS, you must configure the Universal Write Filters that determine what file and registry entries Nomad is allowed to make changes to.

  • Windows 8.1 embedded

SQL Server

N/A
There is no dependency on database servers.

Configuration Manager

  • SCCM CB 1906
  • SCCM CB 1902
  • SCCM CB 1810
  • SCCM CB 1806
  • SCCM CB 1802
  • SCCM CB 1710

Microsoft, and therefore 1E, no longer support CB1706. If you are running CB1706 and find that NomadAdminUI is not working as expected, we recommend you apply KB4036267 to address the issue.

You must:

  • Have a local installation of the Configuration Manager Admin console to install the Admin Console GUI extensions If you want to install the Admin Console GUI extensions on a remote Configuration Manager console, ensure that the Admin Console GUI extensions have been installed on the site server first.
  • If you are using the BIOS to UEFI feature, ensure you meet the prerequisites for Configuration Manager
  • Enable the Microsoft distributed transaction coordinator (MSDTC) service on the Configuration Manager SQL database server and the ActiveEfficiency SQL database server. 

The Nomad Dashboard and dynamic pre-cache features require ActiveEfficiency to synchronise with the Configuration Manager database. For standalone primary site environments, permissions are assigned to the ActiveEfficiency service account automatically using the ConfigMgr_DViewAccess Windows local group native to Configuration Manager. For a CAS, this group is not created natively and additional steps are required to allow access.

If your set-up is across three distributed servers hosting the ActiveEfficiency service, the database and the Configuration Manager database and you plan to use the Nomad Dashboard or the Nomad pre-cache features (or if you get the Login failed for user NT AUTHORITY\ANONYMOUS LOGON error message in the ActiveEfficiency service log (located in C:\ProgramData\1E\ActveEfficiency), you must follow this procedure.

Configuration Manager clients must be installed on DPs for Client Health to receive status messages. DPs not managed by Configuration Manager will not do this.

For each Configuration Manager site server where you intend to administer task sequence packages to use Nomad as the alternate download provider, you need to ensure that:

  • The Configuration Manager Admin Console must be installed – as is the case in a default Configuration Manager installation. This is a prerequisite for the following:
    • The Nomad Admin Console GUI extensions must be installed

If these conditions are not met, the Nomad settings for task sequences will not be created correctly.

This is the case even if you install a remote Configuration Manager Admin Console with the Nomad Admin Console GUI extension, except for Nomad Branch Tools which are required to be installed on Configuration Manager Site Server only.

Web servers

  • IIS 10
  • IIS 8.5
Nomad depends on the same core requirements as IIS that a Configuration Manager DP role depends on, such as (but not limited to) the following:
  1. Application development
    • ASP.NET
    • ISAPI Extensions
    • ISAPI Filters
  2. Security
    • Windows Authentication
  3. IIS 6 management compatibility
    • IIS 6 Metabase Compatibility
    • IIS 6 WMI Compatibility
  4. Common HTTP features
    • Default document
    • Directory browsing
    • HTTP errors
    • HTTP redirection
    • Static content

Runtime libraries

  • .NET Framework 4.7
  • .NET Framework 4.6.2
  • .NET Framework 4.6.1
  • .NET Framework 4.6

Although .NET is a requirement for Client health, the Admin Console GUI extensions and the Download Monitor and NomadBranch GUI, it is not a general requirement for using all the other features of Nomad.

  • The Client Health services can make use of .NET 4.7, 4.6.2, 4.6.1, 4.6 and 4.5 (which can be installed on Windows 8.1).
  • Admin Console GUI extensions can make use of .NET 4.7, 4.6.2, 4.6.1, 4.6

  • The Download Monitor and NomadBranch GUI uses .NET 4.6 or later
.NET 4.6 and 4.6.1 have associated Microsoft hotfixes. We recommend you ensure that these have been applied before using Nomad.
  • KB3139551 Hotfix Rollup HR-1602 - NPD 4.6/4.6.1 RTM – Win7SP1/Win2K8R2RTM/Win2K8R2SP1/VistaSP2
  • KB3139550 Hotfix Rollup HR-1602 - NPD 4.6/4.6.1 RTM - Win8.1RTM/Win2K12R2RTM
  • KB3139549 Hotfix Rollup HR-1602 - NPD 4.6/4.6.1 RTM - Win2K12RTM

Browsers

  • Google Chrome
  • Internet Explorer 11
  • Microsoft Edge
  • Mozilla Firefox
  • Add ActiveEfficiency as a trusted site to avoid warnings on script errors.

ActiveEfficiency

  • ActiveEfficiency 1.10
  • ActiveEfficiency 1.9.910

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

Antivirus

Nomad is able to work with Antivirus systems provided certain exclusions are implemented.

It is likely that Nomad performance will be impaired by antivirus programs. To mitigate this, we have detailed suggested antivirus exclusions you can implement.

Nomad download pause

This feature requires an installation of Tachyon 3.3 or later with Tachyon agents deployed to all the devices where you want the pause feature enabled.

This feature also requires a license for Tachyon and Nomad integration.

Client health

  • .NET Framework 4.6 or later
The client health feature is enabled by default on any Window system which has the .Net Framework 4.6 (or later) runtime library installed. By default, the ENABLECLIENTHEALTH installer property is enabled (set to 1) during installation but you can disable it by setting it to 0.

For new installations the Configuration Manager status message events required for the Client health status tile on the Nomad dashboard are not included in the StatusMsgEvents registry value. This is to prevent any additional status message burden on Configuration Manager where the dashboard is not being used. To enable client health reporting and activate the sending of these events you will need to add the additional client health status message bits, as described on the StatusMsgEvents page.

For existing installations Nomad will respect the StatusMsgEvents settings currently in place.