Many businesses rely on Microsoft Endpoint Manager Configuration Manager (MEMCM) to deploy software, patches and updates across their company networks. It is crucial that Configuration Manager is working effectively.

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 covers the following:

  • Ensure the correct version of the CM client is installed and running and assigned to the correct site
  • Ensure the CM client is not stuck in provisioning mode
  • Ensure that heartbeat discovery, inventory and state messages are being sent regularly
  • Ensures the CM client cache is set to the correct size
  • Ensure the CM client log settings are correct
  • Ensure the BITS service exists, configured to start up automatically  and is running
  • Ensure the Windows Time service exists with correct startup settings
  • Ensure the Windows Management Instrumentation (WMI) service exists, configured to start automatically and is running 
  • Ensure WMI is healthy, the core CIMv2 and ccm namespaces and classes exist and that the WMI repository is consistent 
  • Ensure 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

This policy is intended for deployment to Windows devices only.

Important considerations

Before deploying the MEMCM Client Health Policy you need to be familiar with its contents and comfortable that you want to apply it to the devices in your network.

By default, automated fixes in the Policies provided by 1E are not enabled, this means you will have to specifically enable the ones you want to use before they can take effect.

A new or updated Policy should first be verified by deploying it to a Management Group containing a small number of devices, reviewing the Guaranteed State reports, and confirming the checks and enabled fixes are working as expected.

When you are comfortable with the results you can then deploy to larger Management Groups.

On this page:

MEMCM Client Health Policy Reference

For details on the policy, rules, triggers, preconditions, checks and fixes available in the MEMCM Client Health Policy please refer to MEMCM Client Health Integrated Product Pack.


No instructions.



Fragments (used)

Fragments (spare)

Trigger templates