Here is a client healthcheck tool I wrote for Windows –
It writes to the Windows Event Log which you can do analysis on from your log manager or you can look at via BigFix Relevance.
The big challenge of course is how does an unhealthy agent report its unhealthy status? You kinda need an external mechanism – so that was my approach here.
It essentially checks the following on Windows:
- Does the BESClient Service Exist, is it set to Automatic, and is it currently Running
- Do the BigFix Registry Keys exist in HKLM
- Does the EnterpriseClientFolder value and ComputerId value exist in the Registry
- Does the EnterpriseClientFolder value point to a real folder on the disk
- Do the following folders exist: “__BESData”, “__BESData\__Global”, “__BESData\__Global\Logs”, “__BESData\actionsite”
- Do the following files exist: “besclient.exe”, “__BESData\actionsite\ActionSite.afxm”
- Is there a log file in “__BESData\__Global\Logs” from today
If any of the checks fail, the script backups the __BESData dir, runs the BESClient cleaner, and reinstalls the client fresh.
You can of course just remove the cleaner/install step and perform manual remediation.
The actual script is run as a scheduled task and pushed out via Group Policy in most places ive used it.