Client Health

Client Health is a Nomad feature which monitors the health of Nomad clients installed on DPs and client machines. It runs 13 checks for different resources and components and if it discovers something that is not running as expected, it attempts to rectify that particular issue. The process for the health checks is:

  1. Run a health check for a particular resource or component – it reports the statuses of its checks with Pass, Error or Warning.
  2. Run a remediation if possible – remediation is not available for all the checks it runs.

The table below details the health checks carried out and where they are run: 

Health checksOnly on DPsOnly on clientsRemediation availabe
Nomad alternative content provider(tick)(error)
Nomad cache in temp (disabled by default)(tick)(error)(error)
Nomad DP LSZ virtual directory(error)(tick)
Nomad DP LSZGen enabled(error)(tick)(error)
Nomad ActiveEfficiency connectivity

(error)
Nomad hashing enabled

(error)
Nomad license state

(error)
Nomad crash dumps

(error)
Nomad disk availability

(error)

The full list of health checks can be found here.

The service that monitors the health of DPs and clients is automatically set to a delayed start and it runs continuously in the background like the Nomad branch service.

The workflow and illustrated log behavior for Client Health reporting is:

  1. Run health checks on clients. The log file is located on the local machine.

    === Running Check: Nomad Service Running ===              
    ClientHealth       10-08-2017 14:55:34              25 (0x0019)  
    Check Complete: Nomad Service Running  Result: Passed           
    ClientHealth       10-08-2017 14:55:34             25 (0x0019)  
    Check 'Nomad Service Running' ran for 0.03s      
    ClientHealth       10-08-2017 14:55:34               25 (0x0019) 
  2. Report statuses to the Configuration Manager server.

    Sending health summary             
    ClientHealth       10-08-2017 14:55:34       25 (0x0019)  
    Health report sent successfully 
    ClientHealth       10-08-2017 14:55:34       25 (0x0019) 
  3. Synchronize between Configuration Manager and ActiveEfficiency.

    2017-07-19 22:16:12 #  27662619ms [   74]  INFO : Started Nomad sync, type: Modified  
    2017-07-19 22:16:12 #  27662666ms [   74]  INFO : Content distribution statistics, JobCount: 207, DeviceCollectionCount: 85, CollectionMemberCount: 61486, LastDevicesMembershipSyncTime: 07/19/2017 20:36:56, NewDeviceCount: 2, ContentGroupCount: 337  
    2017-07-19 22:16:12 #  27662666ms [   74]  INFO : Synchronizing Device collections  
    2017-07-19 22:16:13 #  27663134ms [   74]  INFO : Synchronizing membership of devices created after 07/19/2017 20:36:56  
    2017-07-19 22:16:13 #  27663572ms [   74]  INFO : Synchronizing Contents  
    2017-07-19 22:16:13 #  27663572ms [   74]  INFO : Synchronizing Task sequences  
    2017-07-19 22:16:13 #  27663697ms [   74]  INFO : Synchronizing Applications  
    2017-07-19 22:16:14 #  27664369ms [   74]  INFO : Synchronizing Packages  
    2017-07-19 22:16:14 #  27664447ms [   74]  INFO : Synchronizing Status Messages  
    2017-07-19 22:16:14 #  27664447ms [   74]  INFO : Synchronizing Client Health stat messages  
    2017-07-19 22:16:16 #  27666994ms [   74]  INFO : Synchronizing Final stat messages  
    2017-07-19 22:16:17 #  27667806ms [   74]  INFO : Synchronizing request started messages  
    2017-07-19 22:16:22 #  27673009ms [   74]  INFO : Synchronizing request completed messages  
    2017-07-19 22:16:35 #  27685541ms [   74]  INFO : Deleting old status messages  
    2017-07-19 22:16:36 #  27686869ms [   74]  INFO : Synchronizing version distribution  
    2017-07-20 05:58:50 #  55420535ms [   74]  INFO : Finished Nomad sync 
  4. Update the reporting.ClienthealthStats table.
  5. Nomad dashboard consumes data from the reporting.ClienthealthStats table.
  6. Nomad dashboard Client Health tile consumes data from the reporting.ClienthealthStats table.

Other things to note

  • Is Health Check enabled for all the health checks? For example, for the Nomad Service Running health, ensure the registry value is TRUE for Enabled:

    HKEY_LOCAL_MACHINE\SOFTWARE\1E\ClientHealth\HealthChecks\Nomad Service Running\Enabled=True
  • >Are client health status sent to Configuration Manager? You can verify this with the registry value it TRUE for SendStatusMessage:

    HKEY_LOCAL_MACHINE\SOFTWARE\1E\ClientHealth\SendStatusMessage=True
  • Is the Nomad sync running? Check ActiveEfficiency's Services.log to make sure it is. We expect to see:

    2018-09-24 17:39:45 # 292389914ms [ 28] INFO : Synchronizing Client Health stat messages
  • If successfully received by Activeefficiency, it should be there in the ActiveEfficiency's database table dbo.reporting.ClientHealthStats
  • Also check and verify it in the Nomad Dashboard's Client health tile


Client Health is a Nomad feature which monitors the health of its clients installed on DPs and client machines.  

It Performs 13 Checks for different resources and components and if it finds that something is not running as expected it tries to rectify that(Remediation not available for all checks)  

It’s a two-step process  

  1. Perform a health check for a particular resource or component (it can be reported as Pass, Error, Warning)  

  2. Perform remediation if it is available (remediation is not supported for all the Health Checks)

There are a few checks which apply only to clients and not run on DPs  

  1. Nomad Alternate Content Provider  

  2. Nomad Cache In Temp(its disabled by Default)  

Likewise there and a few checks which are run only on DPS and not clients  

  1. Nomad DP LSZ Virtual Directory  

  2. Nomad DP LSZGen Enabled  

Remediation is not supported for following health checks  

  1. Nomad AE Connectivity  

  2. Nomad Hashing Enabled  

  3. Nomad DP LSZGen Enabled  

  4. Nomad License State  

  5. Nomad Crash Dumps  

  6. Nomad Disk Availability  

  7. Nomad Cache In Temp