CD Client Health

The purpose of Client Health is to ensure the success of your Content Distribution deployments. The CD Client Health of the Nomad app shows rule status and device status from two Endpoint Automation policies.

• Nomad Client Health

• MEMCM Client Health

You can also use Endpoint Automation's Windows Client Health policy.

Nomad Client Health

Nomad is included as part of the 1E Client, and as part of that integration, we offer a Nomad client health compliance policy in Endpoint Automation. This verifies common Nomad requirements such as ACP registration, disk availability, firewall exceptions, crash notifications and cache monitoring.

The Nomad client health policy replaces the client health tile in the Nomad dashboard, plus additional remediation steps:

• Keeps content distribution services up and running on Nomad clients, so that users are secure and productive.

• Ensures Alternative Content Provider (ACP) registration configuration is set.

• Maintains optimal disk availability and monitors cache size for storage capacity planning.

• Enforces Firewall exceptions.

For full details, refer to Nomad Client Health Policy.

MEMCM Client Health

Many businesses rely on Microsoft Endpoint Configuration Manager (MECM) to deploy software, patches and updates across their company networks. It is crucial that Configuration Manager is working effectively. Configuration Manager is part of the Microsoft Endpoint Management suite and is often referred to as MEMCM as well as MECM.

The MEMCM Client Health policy monitors Configuration Manager client health and performance. It checks for cache availability, inventory cycles, service availability and Configuration Manager WMI integrity - common causes of Configuration Manager client problems on devices.

The MEMCM Client Health policy replaces the previous SCCM Client Health policy and ensures:

• The correct version of the CM client is installed and running and assigned to the correct site.

• The CM client is not stuck in provisioning mode.

• That heartbeat discovery, inventory and state messages are being sent regularly.

• The CM client cache is set to the correct size.

• The CM client log settings are correct.

• The BITS service exists, is configured to start up automatically and is running.

• The Windows Time service exists with the correct startup settings.

• The Windows Management Instrumentation (WMI) service exists, is configured to start automatically and is running.

• WMI is healthy, the core CIMv2 and ccm namespaces and classes exist and that the WMI repository is consistent.

• The Windows Update service exists with correct startup settings, is configured to use the correct source (CM, WSUS or Microsoft Update) and that the service can connect to the source.

For full details, refer to MEMCM Client Health Policy.

Windows Client Health

Over time Windows devices can develop performance problems related to device or service availability. This policy verifies the available storage capacity on devices, notifies of application crashes, monitors WMI health and service function, and also checks the behavior of core Windows services.

The Windows client health policy covers all of the following:

• Manages Windows devices and service availability performance problems.

• Safeguards disk space integrity, ensuring sufficient storage capacity.

• Ensures optimum performance of the Configuration Manager client and that WMI is active and integrated.

• Notifies of application crashes and remediation assists. Investigates root cause for specific issues.

For full details, refer to Windows Client Health Policy.