Introducing Nomad 6.3
Working with Nomad
Deploying Office 365 updates
Integrating with WakeUp
Managing large package distribution with multicast
Nomad Download Pause
Peer Backup Assistant (PBA)
OS deployment task sequences
The Download Monitor
The Nomad Baseline Wizard
- Client health
- Core features
Operational best practices
Frequently asked questions
- Feature Reference
Technical support for Nomad
Client health is a background service that monitors Nomad clients to ensure that they are running as expected and where it encounters issues, it will attempt a self-heal or remediation. It is installed as a 1E Client Health service and like NomadBranch, its Startup Type attribute is Automatic (Delayed Start). It reports its health checks to Configuration Manager in the form of status messages which can be viewed in the Nomad dashboard.
On this page
Health check steps
Each health check when run goes through two steps:
- The status of the service or component is checked and its status reported:
- Pass – health check passed
- Warning – health check passed, but with warnings
- Error – when a health check (and its remediation) fails.
- If an error is found in 1 and a remediation is available, it is run. For example, if the
NomadBranchservice is in a stopped or disabled state, the remediation will try and start it.
Note that some health checks may not apply to certain kind of machines. For example, the Nomad DP LSZGen enabled health check applies only to DPs and not to regular client machines. If a health check is not applicable on a particular machine, it is automatically disabled when the Client Health service starts-up.
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.
Available health checks
There are currently twelve health checks available. Their characteristics are as follows:
|Health Check||Applies to Client||Applies to DP||Has remediation||Notes|
|ActiveEfficiency connectivity||If the ActiveEfficiency URL is present in the Nomad settings, it checks to see if the ActiveEfficiency server is reachable and is serving requests.|
If you are not integrating with ActiveEfficiency, disable Nomad AE Connectivity (Enabled=false).
|Firewall exceptions||Checks exceptions for |
|Nomad service running||Checks if the |
|Nomad share account||Validates the share account and its properties (if custom share is not configured).|
|Nomad share||Validates the share folder and its properties (if custom share is not configured).|
|Nomad hashing enabled||Checks to see if bit 19 is set on a DP and bit 20 on clients (they are enabled by default) on for the CompatibilityFlags registry values.|
|Nomad DP LSZ virtual directory||Checks if the LSZFILES virtual directory is in place on a DP.|
|Nomad DP LSZGen enabled||Check LSZ generation is turned enabled on a DP.|
|Nomad license state||Checks the status of Nomad's license.|
|Nomad crash dumps||Checks for the presence of Nomad crash dumps in the Nomad logs directory.|
|Nomad disk availability||Checks disk space (it expects PercentAvailableDisk+5%) available to Nomad.|
|Nomad alternate content provider||Checks if Nomad is registered as an alternate content provider with Configuration Manager clients.|
|Nomad cache in temp||If Nomad cannot open or share its cache directory, it creates one in the System Temp folder.|
Configuration the behavior of health checks
The behavior health check is determined by its settings in the registry at:
HKEY_LOCAL_MACHINE\SOFTWARE\1E\ClientHealth. If you update the registry values while the
ClientHealth service is running, you must restart it for your changes to take effect. We recommend you back up your registry before making any updates.
To update a registry value:
- Open the Registry Editor.
The Nomad ClientHealth registry values are held under the
HKEY_LOCAL_MACHINE > SOFTWARE > 1E > ClientHealthkey, as shown in the picture opposite.
Each of the registry entries is described in the following table:
Registry value Default value Installer property Description LogFileName
This property sets the path for all the Nomad logs. The ClientHealth log file name is always set to the default ClientHealth.log.
Sets the path and filename of the ClientHealth log file. MaxLogFileSize 1048576Sets the maximum size (in bytes) of the ClientHealth log file. ResendStatusPeriodHrs 336 RESENDHEALTHSTATUSHOURS
Duration (in hours) before sending status messages to Configuration Manager. For example:
- If you set the duration to 12 hours, ClientHealth will not update Configuration Manager until the duration has lapsed or if the status for a particular health check has changed, in which case, a new status message for that particular check is sent.
- If you set the value to 0, ClientHealth updates Configuration Manager each time it runs its checks irrespective of the previous status of a particular check.
This value sets whether Nomad sends the ClientHealth status messages to Configuration Manager or not. To enable this feature, you set this value to
The Nomad Dashboard requires this value to be set to
- Each health check has its own key under the
ClientHealth > HealthCheckskey.
- If you want to enable a particular health check, update
Enabled=true(the default is
Enabled=false) in the health check's key
- The interval (in seconds) between running the health checks can be globally set for all the checks during install time using the HEALTHCHECKPERIODSECS installer property.
- If you want to modify each health check's period individually, update the value for
PeriodInSecs(the default is
PeriodInSecs=3600) under the relevant health check's key.
- If you want to enable a particular health check, update
- When you have finished making changes close the Registry Editor.