What's new in ConfigMgr Client Health 0.8.3

Nov 16, 2020
  • Client Health now successfully sets the client max log history.
  • Client Health now successfully sets the client cache size.
  • Fixed an issue with <ClientInstallProperty> using /skipprereq and specifying multiple components while separating with ";" would break the script.
  • Enabled debug logging in the webservice by default to make troubleshooting easier. Debug logs are stored in the "logs" folder.

New in ConfigMgr Client Health 0.8.2 (Oct 1, 2019)

  • ConfigMgr Client Health detects and fixes the following errors:
  • ConfigMgr client is not installed.
  • ConfigMgr client is assigned the correct site code.
  • ConfigMgr client is upgraded to current version if not at specified minimum version.
  • ConfigMgr client not able to forward state messages to management point.
  • ConfigMgr client stuck in provisioning mode.
  • ConfigMgr client cache size. Set fixed size (MB) or percentage of disk.
  • ConfigMgr client maximum log file size and log history files.
  • ConfigMgr client certificate. Checks for a specific error and fixes it.
  • ConfigMgr client hardware inventory not running according to schedule.
  • ConfigMgr client local database files are corrupt or damaged.
  • Corrupt WMI.
  • Downloads stuck at 0% in software center.
  • DNS server record matches local IPs
  • Drivers - Reports faulty or missing drivers on client.
  • Services for ConfigMgr client is not running or disabled.
  • Other services can be specified to start and run and specific state.
  • Pending reboot check
  • Userfriendly reboot of computer 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 fixes known bugs.

New in ConfigMgr Client Health 0.8.1 (Aug 12, 2018)

  • Script will now update database correctly when connecting directly to SQL server.
  • Fixed an issue with BITS test.
  • Fixing ClientCache no longer restarts SCCM agent.
  • Fixed a bug where service uptime test didn't work properly.

New in ConfigMgr Client Health 0.8.0 (Jul 25, 2018)

  • New feature: Webservice for improved communication with database. Fixed bug that could cause Test-Registrypol function to loop. Removed last bit of hardcoded paths in the script. Fixed and enhanced service tests. Script will now validate if Config.xml is valid before executing script.

New in ConfigMgr Client Health 0.7.6 (Apr 29, 2018)

  • Changed test to verify SMSTSMgr is not dependent on CCMExec service, and only WMI service. Script will now abort and not run any health checks if an active task sequence is running on the system.

New in ConfigMgr Client Health 0.7.5 (Apr 11, 2018)

  • Script will now test if service SMSTSMgr is dependent on CCMExec service.
  • Added option to refresh compliance state every XX days.
  • Uptime on services is now configurable in config.xml.
  • Changed DNS test to only lookup DNS servers from active network adapters.
  • Fixed a bug in Remove-CCMOrphanedCache function that potentially could be harmful.
  • Other minor bug fixes.
  • Removed support for PowerShell version 2 and 3.

New in ConfigMgr Client Health 0.7.4 (Mar 22, 2018)

  • Support for PowerShell Core (PowerShell version 6).
  • Improved detection and remediation of corrupt ConfigMgr Client database files.
  • Corrupt WMI check now works on Finnish OS language.
  • Localfiles defaults to C:ClientHealth if not specified in config.xml.
  • DNS errors, driver errors and failed connections to SQL server will no longer write to logfile if LogLevel is set to ClientInstall.
  • Script will use COM object to assign correct sitecode, and no longer reinstall ConfigMgr client if sitecode is wrong.

New in ConfigMgr Client Health 0.7.3.1 (Mar 22, 2018)

  • Fixed a bug in the function cleaning up localfiles on the computer.

New in ConfigMgr Client Health 0.7.3 (Feb 27, 2018)

  • Test on CcmSQLCE.log is now optional and configurable in config.xml.
  • Fixed a bug where script could hang on Windows 7 computers running Powershell version
  • Client Health will now log the reason why it reinstalled the ConfigMgr client.
  • Added option to store time as UTC or client local time.
  • LocalFiles is now configurable in config.xml (default C:ClientHealth).
  • Script will now remove localfiles directory if locallogging is disabled.

New in ConfigMgr Client Health 0.7.2 (Oct 24, 2017)

  • Bugfixes:
  • Local log file will now honor MaxLogHistory, services automatic (delayed start) should now detect and configure correctly.
  • Improved DNS check for Windows 8.1 / Server 2012 R2 and higher.
  • Implemented another check on the CM client health. Improved testing on WUAHandler.log. BITS check, DNS, hardware inventory, software metering and updates check can now run in monitor only mode (fix="false" in config.xml)
  • Script will now triger the built in CM client health check (ccmeval) at the end of the script.

New in ConfigMgr Client Health 0.7.1 (Sep 7, 2017)

  • Fixed a bug where the script would fail to configure services to automatic delayed start

New in ConfigMgr Client Health 0.7.0 (Sep 5, 2017)

  • Added a test and fix for Software Metering.
  • Fixed bug where script would fail to update SQL database.
  • Script will now remove errors from the logfiles where the error is fixed to false positives next time script runs.
  • Added PatchLevel to easily discover which clients are not fully patched.
  • Improved the installation of SCCM agent.
  • Added fix for BITS error that would cause downloads to be stuck at 0%.
  • ClientHealth now use c:clienthealth as directory for temporary files.
  • Local logging logs to c:clienthealthclienthealth.log if enabled.

New in ConfigMgr Client Health 0.6.8 (Aug 10, 2017)

  • Added a test and fix for registry issue that could prevent ccmsetup from installing the sccm client.
  • OSBuild now displays the full build number.
  • Several bug fixes: MaxLogSize now rounds decimals, OSUpdates should no longer mix up day and month, fixed a bug with right click tool showing a parsing error.

New in ConfigMgr Client Health 0.6.7 (Jul 19, 2017)

  • Added a right click tool to the configuration manager console to remotly start client health on devices.
  • Detection and remediation on configmgr client no longer use hardcoded paths, added windows time services in config.xml as service to enforce as automatic.
  • Lenovo models finally reporting correct models name.
  • Fixed a bug where reboot application would not always start on Windows 7 with PowerShell 2.

New in ConfigMgr Client Health 0.6.5 (Jun 6, 2017)

  • Improved check on registry.pol file. Standard PS/2 drivers no longer reports as error. More effective logging code. Fixed bug where hardware inventory