ConfigMgr Client Health

It’s a well-known fact that programming doesn’t always end with a 100% error-free product, even if it’s an operating system. For instance, patches and updates are constantly pushed on Windows to make it as stable as possible, or introduce new features. However, the update component might get broken, case in which ConfigMgr Client Health can attempt to fix it.

ConfigMgr Client Health isn’t a stand-alone application, being merely a script which needs to be run on Windows iterations such as 7, 8, 8.1, 10, as well as Server 2008 R2, 2012, 2012 R2, and 2016. It works on both x86 and x64 system architectures. PowerShell version 2 or higher is required for the script to properly run.

When deployed, the script attempts to detect and fix known errors in Windows and the Configuration Manager Client to increase patch compliance. It also deploys the necessary updates across a variety of machines, which need to have read access to the root update folder.

Note that it’s recommended for target computers to have the latest updates installed, otherwise there are chances of experiencing issues with the Windows Update Agent. The following updates are known to fix such issues:

Windows 7: KB3065987 KB3102810 KB311664 32-Bit and 64-Bit

Windows 8.1: KB3102812

The script is installed on the main SQL server through one of the methods provided in the documentation. Patches need to be placed in the appropriate folders for operating systems and architectures.