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 client is now part of the 1E Client. Please refer to 1E Client 5.0 for details of how to deploy the 1E Client with the Nomad client enabled.

The 1E Client should be installed on all Windows clients. You must use the correct installer according to the Windows architecture of the device:

  • 1E.Client-x64.msi is for 64-bit architectures
  • 1E.Client-x86.msi is for 32-bit architectures

Local Administrator

Download GUI tool installer for optional installation on clients: NomadBranchGui.msi.

This is a troubleshooting, testing, and administrative tool only. It should not be installed generally on devices in your network.
Local Administrator

ConfigMgr console extensions: NomadBranchAdminUIExt.msi

ConfigMgr administrators use console extensions to configure Nomad content download, custom task sequence steps, The Nomad Dashboard and Nomad Download Pause features.

The installer should be run on all Windows workstations and servers that have Configuration Manager Console installed, including Site servers.

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 all Site Servers (except Secondary) and all SMS Provider servers. Specifically servers which Configuration Manager Consoles may connect to.

Local Administrator

Infrastructure prerequisites


Supported OS

  • Windows Server 2022
  • Windows Server 2019
  • Windows Server 2016
  • Windows 10 CB 21H2
  • Windows 11 CB 21H2
  • Windows 10 CB 21H1
  • Windows 10 CB 20H2
  • Windows 10 CB 2004
  • Windows 10 CB 1909
  • Windows 10 CB 1903
  • Windows 10 CB 1809
  • Windows 10 CB 1803
  • 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.

Windows 7 SP1 (32 and 64-bit versions of Enterprise and Professional editions) is supported to help customers during their migration to Windows 10, although it is out of mainstream support by Microsoft.

SQL Server

There is no dependency on database servers.

Configuration Manager

  • SCCM CB 2111
  • SCCM CB 2107
  • SCCM CB 2103
  • SCCM CB 2010
  • SCCM CB 2006
  • SCCM CB 2002
  • SCCM CB 1910
  • SCCM CB 1906
  • SCCM CB 1902

1E maintains a testing cycle for our products relative to the Current Branch release cycle.  Please refer to for latest information on future releases of CM Current Branch, and any advisories related to these releases.

When using CB 1910, be sure to apply Hotfix Rollup KB4537079 or later. Prior to this update there is an issue that prevents Alternate Content Providers downloading certain types of content referenced in Task Sequences.

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.

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 on the site server – as is the case in a default Configuration Manager installation. This is a prerequisite for the installing the Nomad Admin Console GUI extensions, which must be installed on the site server before installing on any remote Configuration Manager console
  • Enable the Microsoft distributed transaction coordinator (MSDTC) service on the Configuration Manager SQL database server and the ActiveEfficiency SQL database server.
  • Ensure you meet the prerequisites for Configuration Manager if you are using the BIOS to UEFI feature: BIOS TO UEFI 1.4 - Requirements.
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.

The Nomad Dashboard and dynamic pre-cache features require ActiveEfficiency to synchronize with the Configuration Manager database. For standalone primary site environments, permissions are assigned to the ActiveEfficiency service account automatically using the ConfigMgr_DViewAccess localgroup native to Configuration Manager. For a CAS, this group is not created natively therefore additional steps are required to allow access. Please refer to ActiveEfficiency Server 1.10 - Preparation: Granting access to the Configuration Manager site database.

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), please refer to the procedure in ActiveEfficiency Server 1.10 - Preparation: Service Principal Names and Delegation.

Web servers

  • IIS 10
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.8
  • .NET Framework 4.7.2
  • .NET Framework 4.7
  • .NET Framework 4.6.2

.NET Framework is required for the Admin Console GUI extensions, the Download Monitor, and NomadBranch GUI. It is not a requirement for other features of Nomad.

.NET Framework 4.6 and 4.6.1 have associated Microsoft hotfixes. We recommend you ensure the following are applied before installing or using Admin Console GUI extensions, the Download Monitor, or NomadBranch GUI.
  • 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


  • Google Chrome
  • Microsoft Edge
  • Microsoft Edge (Chromium)
  • Mozilla Firefox
  • Add ActiveEfficiency as a trusted site to avoid warnings on script errors.


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 (


  • Nomad is able to work with Antivirus systems provided they have certain exclusions configured.

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

Tachyon features

  • Working installation of Tachyon 5.0 or later.

  • Working installation of 1E Client 5.0 deployed with Tachyon client enabled.

The Nomad Download Pause feature requires an installation of Tachyon.

The 1E Client Health feature provided in previous versions of Nomad and the Nomad Dashboard is now provided through the Guaranteed State feature of the 1E Tachyon platform. Please refer to Tachyon 5.0 - Nomad Client Health Policy for more details.

Both features require Tachyon 5.0 or later with 1E Client (with Tachyon client enabled) deployed to all devices. A license for Tachyon and Nomad integration is also required.