ConfigMgr Client Health detects and fixes known errors in Windows and the Configuration Manager Client, and enforces required services to run and start as Automatic.

ConfigMgr Client Health detects and fixes known errors in Windows and the Configuration Manager Client, and enforces required services to run and start as Automatic.

ConfigMgr Client Health identifies and fixes the following errors:

ConfigMgr client is not installed.
ConfigMgr client is assigned the correct site code.
ConfigMgr client is upgraded to the current version if not at specified minimum version.
ConfigMgr client is not able to forward state messages to the management point.
ConfigMgr client stuck in provisioning mode.
ConfigMgr client cache size. Set fixed size (MB) or percentage of the disk.
ConfigMgr client maximum log file size and log history files.
ConfigMgr client certificate. Checks for a specific error and fixes it.
Corrupt WMI.
DNS server record matches local IPs
Drivers - Reports faulty or missing drivers on the client.
Services for ConfigMgr client is not running or disabled.
Other services can be specified to start and run and a specific state.
Pending reboot check
A user-friendly reboot of computers with 3rd party reboot app when in pending reboot or computer uptime is more than specified in config.
Windows Update Agent not working correctly, causing client not to receive patches.
Windows Update Agent missing patches that fix known bugs.

This tool should be placed on a network share available to all clients where everyone has read access, and only administrators will have write access.

This tool is for advanced users and server admins. Documentation is available here.

ConfigMgr Client Health uses Microsoft PowerShell. Here is a tutorial on using PowerShell if you're new to it:

 Download