This monitor checks if the management point responds to HTTP requests, using the MP_CONTROL_MANAGER.
This monitor identifies the Configuration Manager management point’s basic online status, by sending and receiving a basic HTTP request to the management point. The component MP_CONTROL_MANAGER monitors those requests. When a management point is online, it can accept incoming communications from client computers. When the management point is offline, client computers cannot communicate their status, inventory, or state information to the Configuration Manager site. When the management point is offline or in a failed state, client computers cannot make inquiries of the management point to locate content such as software or software updates, and cannot locate key data or system information provided by the management point. When a client computer cannot communicate with any management point, it cannot be actively managed by Microsoft Endpoint Configuration Manager.
This condition could occur because:
The MP_CONTROL_MANAGER component or a management point component is not responding to HTTP requests.
A heartbeat has not been received from the management point control manager component within its expected interval. This can be due to:
High system and Configuration Manager processing loads.
An extended wait on a request.
A deadlock on a shared resource.
A dependent service required by the management point is not operational.
Check the Mpcontrol.log file in the [Configuration Manager Installation folder]\Logs folder.
Determine if the server has sufficient resources such as CPU, memory, or disk space.
Determine that a dependent component has not been stopped or uninstalled.
Check the Site Component Manager log file (sitecomp.log) in the [Configuration Manager Installation folder]\Logs folder for information about other services or components that are failing or not operational on the computer hosting the MP_CONTROL_MANAGER component.
Target | MECM.ManagementPoint | ||
Parent Monitor | MECM.SiteRole.AggregateRollup.Monitor | ||
Category | Custom | ||
Enabled | True | ||
Alert Generate | True | ||
Alert Severity | MatchMonitorHealth | ||
Alert Priority | Normal | ||
Alert Auto Resolve | True | ||
Monitor Type | MECM.StatusMessage3State.MT | ||
Remotable | True | ||
Accessibility | Public | ||
Alert Message |
| ||
RunAs | Default |
<UnitMonitor ID="MECM.ManagementPoint.HttpRequest.StatusMessage.Monitor" Accessibility="Public" Enabled="true" Target="MECM.ManagementPoint" ParentMonitorID="MECM.SiteRole.AggregateRollup.Monitor" Remotable="true" Priority="Normal" TypeID="MECM.StatusMessage3State.MT" ConfirmDelivery="true">
<Category>Custom</Category>
<AlertSettings AlertMessage="MECM.ManagementPoint.HttpRequest.StatusMessage.Monitor.AlertMessage">
<AlertOnState>Warning</AlertOnState>
<AutoResolve>true</AutoResolve>
<AlertPriority>Normal</AlertPriority>
<AlertSeverity>MatchMonitorHealth</AlertSeverity>
<AlertParameters>
<AlertParameter1>$Target/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/PrincipalName$</AlertParameter1>
</AlertParameters>
</AlertSettings>
<OperationalStates>
<OperationalState ID="UIGeneratedOpStateIdae63d1c092c84b83bcbae8d9d34afcc4" MonitorTypeStateID="Good" HealthState="Success"/>
<OperationalState ID="UIGeneratedOpStateIdc031fb0ec1644a8a8dac49a41f22f129" MonitorTypeStateID="Warning" HealthState="Warning"/>
<OperationalState ID="UIGeneratedOpStateId5228350b4f004939b6d6a78f28ed8c40" MonitorTypeStateID="Error" HealthState="Error"/>
</OperationalStates>
<Configuration>
<ComputerName>$Target/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/PrincipalName$</ComputerName>
<ComponentName>SMS_MP_CONTROL_MANAGER</ComponentName>
<RuleId>65AC53A5-8C79-4DF9-AE79-A53F689C2222</RuleId>
<IntervalSeconds>360</IntervalSeconds>
<MatchCount>3</MatchCount>
</Configuration>
</UnitMonitor>