Problem, you launch your SCOM console, and your server is in the following state. You browse the server, and check out the health service, and it is clearly running… So now what?
A Windows based machine appears in a “Not monitored” state. While SCOM thinks the machine is un-responsive, we can confirm this is not the case, as we can ping to the machine; in addition we are able to login to the machine.
This is a result of the SCOM health service needing its cache to be cleared.
SCOM has a built in task to do exactly what we want; however, since SCOM believes the machine is in an offline state, it will not be able to trigger the task to the “Not monitored” machine.
SOLUTION – MANUAL PROCESS
- Remote into the machine, and launch the services (services.msc). Locate the Microsoft Monitoring Agent service, and stop the service.
- Once the service has stopped, browse the following folder, “C:\Program Files\Microsoft Monitoring Agent\Agent\”
Delete the entire (Health Service State) folder.
- Go back to the Windows Services (services.msc) and start the Microsoft Monitoring Agent service. This will rebuild the folder we just deleted.
Give SCOM a few seconds, maybe a few minutes, and the Health State of our machine will turn back to healthy!