Introducing Nomad 6.3
Working with Nomad
Technical support for Nomad
Nomad installer properties
Nomad command-line switches
Nomad registry values
Nomad return codes
Status messages for download events
Enabling Nomad on Windows embedded devices
Nomad local multicast
Basic Nomad behavior in a simple environment
- Supported Platforms
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:
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.
|There is no dependency on database servers.|
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.
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
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:
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.
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:
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.
.NET 4.6 and 4.6.1 have associated Microsoft hotfixes. We recommend you ensure that these have been applied before using Nomad.
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:
|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.
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.