Installation account permissions
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:
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.
ConfigMgr console extensions: NomadBranchAdminUIExt.msi
The installer should be run on all Windows workstations and servers that have Configuration Manager Console installed, including Site servers.
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.
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:
For Windows Server 2016 Core Server installations:
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.
|There is no dependency on database servers.|
1E maintains a testing cycle for our products relative to the Current Branch release cycle. Please refer to https://1eportal.force.com/s/support-for-msft-rapid-release-cycle 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:
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
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:
.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.
The following Nomad features require ActiveEfficiency:
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).
It is likely that Nomad performance will be impaired by antivirus programs. To mitigate this, we have detailed suggested antivirus exclusions you can implement.
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.