A new version of ConfigMgr Client Health is finally released, and this version includes several improvements to the script.
I want to thank Apila22, Cody Mathis, Lauri Kurvinen and theaquamarine for contributing to this new version.
Changes in version 0.8.2
- Fixed a bug where logging directly to SQL database would not work.
- Fixed an issue with BITS test.
- Fixed a bug where service uptime test didn’t work properly.
- ClientCacheSize check no longer need to restart CM Agent when changing the cache size.
- ClientCacheSize max limit 99999.
- Fixes errors where configuration baselines fails because script is not signed even when bypass is set as execution policy in client settings.
- Script will now stop services that are in a degraded state.
- Improved code to detect last installed patched.
Updated database to allow null for LastLoggedOnUser. - Check client version is now run at end of script in case client was upgraded by script.
- Script will no longer run if it detects a task sequence already running on the computer.
- Script will not restart services if another installation is running.
- Hostname is now read from environmental variable and not WMI.
- Multiple bugfixes.
- Add Windows Server 2019 support.
- Improved WMI test and fix.
- Will only log to webservice if parameter is specificed.
- Improved the error message when script fails to update SQL.
- Logfiles are now compatible with CMTrace.
Download: Microsoft Technet Galleries
Documentation: ConfigMgr Client Health
What exactly is the new ClientSettingsCheck option?
Hi, thanks for the new version ! I did run across an issue with the webservice updating SQL after updating the web files with the files that had updates since the last version. After troubleshooting, I was able to narrow it down to one file causing the problem, ConfigMgrClientHealthWebservice.dll. With the newer file dated 3/28/19 I kept on receiving this error when the webservice tried to update the SQL database: Error Invoking RestMethod POST on URI http://servername/configmgrclienthealth/clients. Failed to update database using webservice. Exception: The remote server returned an error: (409) conflict. If I stop IIS and copy the dll file from 7/24/18, the update to the SQL database starts to work again though I’m sure I’m losing some type of functionality with the older dll file. IIS is running on a Windows 2012 server. I duplicated the issue with another Windows 2012 server. I’m going to try a Windows 2019 server next.
thanks for the new release and your work
One remark, the update folder for Server 2019 is missing, maybe for the next release.