Monitor to get a state of the site assignment work item on Management Configuration Service Group
The System Center Management Configuration Service has failed to perform the Site Assignment task in an acceptable amount of time.
The purpose of this monitor is to determine if the Configuration Service has failed to run the “SiteAssignment “ work item over the last 15 minutes (default). The impact of the “SiteAssignment” work item failing is during this time new resource pools cannot be properly enabled in the management group and existing resource pool could experience inconstant behaviors.
Green State: Site Assignment has run successfully once in the last 15 minutes.
Red State: All Instances of Configuration Service failed to consecutively perform this work item for a period of time. An Alert is generated from this monitor when in this state.
This can happen when:
The database or database server is unavailable (networking issue, firewall, disk space, etc.)
The System Center Management Configuration Windows Service account no longer has the required access to the database
The “SiteAssignment” work item has been disabled in the ConfigService.config. The ConfigService.config file is located in “%Program Files%\Microsoft System Center\Operations Manager\Server”.
To further investigate the issue, consider the following:
Review the Operations Manager event log for errors indicating problems with the System Center Management Configuration Service. Filter the event log a source of “OpsMgr Management Configuration” to search for errors.
Confirm you are not seeing connection error to the Operations Manager database from the management server in the Operations Manager event log
Using the Operations Manager Console and SQL Server Management Studio, validate the Default Action Account has the correct access to the database where the Operations Manager database is installed. For more information about configuring the Default Action Account please see the Operations Manager Security Guide.
Open the ConfigService.config file and search for “AgentPoolAssignment” under WorkItems. Make sure Enabled property is set to true. The ConfigService.config file is located in “%Program Files%\Microsoft System Center\Operations Manager\Server”.
Target | Microsoft.SystemCenter.ManagementConfigurationServiceGroup | ||
Parent Monitor | Microsoft.SystemCenter.ManagementConfigurationServiceGroup.WorkItemsHealthMonitor | ||
Category | StateCollection | ||
Enabled | True | ||
Alert Generate | True | ||
Alert Severity | Error | ||
Alert Priority | Normal | ||
Alert Auto Resolve | True | ||
Monitor Type | Microsoft.SystemCenter.ManagementConfigurationService.WorkItemStatsMonitorType | ||
Remotable | True | ||
Accessibility | Internal | ||
Alert Message |
| ||
RunAs | Default |
<UnitMonitor ID="Microsoft.SystemCenter.ManagementConfigurationServiceGroup.SiteAssignmentMonitor" Accessibility="Internal" Enabled="true" Target="Microsoft.SystemCenter.ManagementConfigurationServiceGroup" ParentMonitorID="Microsoft.SystemCenter.ManagementConfigurationServiceGroup.WorkItemsHealthMonitor" TypeID="Microsoft.SystemCenter.ManagementConfigurationService.WorkItemStatsMonitorType" ConfirmDelivery="true">
<Category>StateCollection</Category>
<AlertSettings AlertMessage="Microsoft.SystemCenter.ManagementConfigurationServiceGroup.SiteAssignmentMonitor.AlertMessage">
<AlertOnState>Error</AlertOnState>
<AutoResolve>true</AutoResolve>
<AlertPriority>Normal</AlertPriority>
<AlertSeverity>Error</AlertSeverity>
<AlertParameters>
<AlertParameter1>$Data/Context/DataItem/LastErrorMessage$</AlertParameter1>
</AlertParameters>
</AlertSettings>
<OperationalStates>
<OperationalState ID="Good" MonitorTypeStateID="WorkItemOnSchedule" HealthState="Success"/>
<OperationalState ID="Bad" MonitorTypeStateID="WorkItemDelayed" HealthState="Error"/>
</OperationalStates>
<Configuration>
<FrequencySeconds>60</FrequencySeconds>
<WorkItemName>SiteAssignment</WorkItemName>
<ToleranceSeconds>1800</ToleranceSeconds>
</Configuration>
</UnitMonitor>