I’m happy to announce version 0.7.0 of the PowerShell script that increased our patch compliance to 99%. This version includes a new fix for downloads stuck at 0% in software center, and current patchlevel are now displayed in the database.
The latest version is available here: Microsoft Technet Gallery
Full documentation of the script is always available here: https://www.andersrodland.com/configmgr-client-health/
Changes in ConfigMgr Client Health Version 0.7.0
- Cleans up failed BITS jobs that cause downloads to be stuck at 0% in Software Center. You can enable or disable this check in config.xml.
- Fixes Software Metering error described here: https://support.microsoft.com/en-us/help/3213242/software-metering-agent-fails-with-software-metering-failed-to-start-p. You can enable or disable this check in config.xml.
- PatchLevel is now visible in the database and log files, gathered from this registry key: “HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\UBR”
- Now supports local logfiles on the computer, stored at C:\ClientHealth\ClientHealth.log. You can enable or disable this check in config.xml
- Fixed a bug where some checks would return false and script would fail to update the database.
- The script now remove errors from the logfiles after it remediated, this to prevent a false positive next time the script runs.
- Improved the installation method of the Configuration Manager client by registering required Windows DLL files before the client is installed.
