Indicates whether the Health service configuration processing is successful and current.
This monitor detects if a health service has failed to process a configuration or its configuration is out-of-date. health service configuration includes the management packs that apply to the health service and the Run As accounts that the health service needs to use.
This aggregate monitor will roll up the state of the child unit monitors. The unit monitors that roll up to this aggregate monitor are disabled by default; review and enable the unit monitors as needed for your monitoring requirements.
View the product knowledge for each unit monitor to identify the criteria for critical and warning states.
This may be caused by a communication outage to the parent management server for this health service.
If this health service is communicating with a gateway server rather than a management server, it may take more time for the health service to get the up-to-date configuration.
The following steps should be followed to diagnose and resolve this issue:
Check that the System Center Management service and System Center Management Configuration service are both started on the root management server. If either service is not started, the new configuration cannot be propagated to the rest of the health services. Start the root management server's System Center Management service and System Center Management Configuration service, if not running.
Check if this health service is reporting up through a gateway server. If it is reporting through a gateway server, verify that the System Center Management service is running on that server and any other management servers between the gateway server and the root management server.
If the services are all running, attempt to restart the health service on this agent. Health service restart 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 its 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 its new configuration.
The state of this monitor is based on the states of its unit monitors. To determine why the state of this monitor has changed, identify the unit monitor that changed its state. To locate this information, open State Change Events in Health Explorer for the monitor. Right-click the alert, point to Open, and then click Health Explorer. In Health Explorer, click the State Change Events tab. The Details pane in the State Change Events tab shows you when the state for the monitor changed, and the details give you information for the context of the state change.
Target | Microsoft.SystemCenter.HealthService | ||
Parent Monitor | System.Health.ConfigurationState | ||
Algorithm | WorstOf | ||
Category | StateCollection | ||
Enabled | False | ||
Alert Generate | True | ||
Alert Severity | Error | ||
Alert Priority | Normal | ||
Alert Auto Resolve | True | ||
Remotable | True | ||
Accessibility | Public | ||
Alert Message |
|
<AggregateMonitor ID="Microsoft.SystemCenter.HealthService.ConfigurationStateHealthRollup" Accessibility="Public" Enabled="false" Target="SCLibrary!Microsoft.SystemCenter.HealthService" ParentMonitorID="Health!System.Health.ConfigurationState" Remotable="true" Priority="Normal">
<Category>StateCollection</Category>
<AlertSettings AlertMessage="Microsoft.SystemCenter.HealthService.ConfigurationStateHealthRollup_AlertMessageResourceID">
<AlertOnState>Error</AlertOnState>
<AutoResolve>true</AutoResolve>
<AlertPriority>Normal</AlertPriority>
<AlertSeverity>Error</AlertSeverity>
</AlertSettings>
<Algorithm>WorstOf</Algorithm>
</AggregateMonitor>