Monitor Agent does not function if no policies pass detection

Article:TECH138265  |  Created: 2010-08-23  |  Updated: 2010-08-28  |  Article URL
NOTE: If you are experiencing this particular known issue, we recommend that you Subscribe to receive email notification each time this article is updated. Subscribers will be the first to learn about any releases, status changes, workarounds or decisions made.
Article Type
Technical Solution


If no Monitor Policies' detection methods are passed, the Monitor Agent's child processes will not execute preventing detection from being executed again until either a service restart or a configuration update.


A single Monitor Policy, "Domain Name Server (DNS)", is applied to a machine. This machine is initially not a DNS server, therefore detection fails and no policies are activated. DNS is then later installed, but the policy does not become activated even after 60 minutes has passed. In order for the policy to become activated, the Monitor Agent must either receive a configuration update, or be restarted.


  • Monitor Solution for Servers SP4 HF1  7.0.7722  (and previous versions)


This behavior is a defect. Monitor Policy detection should run every 60 minutes (default) regardless of if there are currently any activated policies or not.


This issue is resolved in the SP5 release of Monitor Solution for Servers.

Supplemental Materials


Article URL

Terms of use for this information are found in Legal Notices