Indicates whether the health service configuration state is up to date or not.
Knowledge Base article:
Summary
This monitor will generate warning and critical state if a Health Service has out of date configuration. Configuration can be:
One or more management packs
Run As Accounts
Out of date configuration may indicate communication issues with the parent Management Server of this Health Service. Here is a summary of the states:
Warning State: This indicates that configuration was updated at the Root Management Server, this Health Service has requested the new configuration, but has not yet received that new configuration for over 45 minutes.
Critical State: If the warning state continues to persist for an additional 45 minutes, then the monitor will go into a critical state. This means that since the Root Management Server indicated there was new configuration for this Health Service, it has not downloaded that new configuration for a total of 90 minutes.
Causes
This may be caused by a communication outage to the parent Management Server for this Health Service.
If this Health Service is communicating with an upstream Gateway Server, it may take some time for the Gateway to get the most up to date configuration before it can propagate it to this Health Service.
Resolutions
The following steps should be followed to diagnoses and resolve this issue:
Check that the Root Management Server’s Health Service is started
If it is not started, the new configuration cannot be propagated to the rest of the Health Services. Start the Root Management Server’s HealthService.
Check that the Root Management Server’s Configuration Service is started.
If it is not started, the HealthServices will not be notified of updated configuration properly. Start the Root Management Server’s Configuration Service.
If you have checked all of the above, check if this Health Service is reporting up through a Gateway Server.
If it is reporting through a Gateway Server, verify that the HealthService is running on that server and any other Management Servers between it up until the Root Management Server.
If they Health Services are all running, attempt to restart the Health Service on this agent.
On Health Service restart it will attempt to get the most recent configuration.
If this does not address the issue, you can follow the below steps to initiate an agent repair which will force the agent to update it management pack and configuration cache as part of the repair process:
Navigate to the Administration space
Click the Agent Managed view under Device Management
In the result pane, select one or more agents
Click Repair… in the Actions pane
You can use the default action account or supply alternate credentials
Click the Repair button
This should repair the agent and force it to request it’s new configuration.
The Health Service has requested new configuration, but either has not received it in the allocated time or has received it but could not load it successfully.
Home
ENU