Monitors the health of the Windows Service: Intersite Messaging Service
If the ISM was stopped due to manual intervention then review your operations procedure because this service is required for the KCC to function.
Target | Microsoft.Windows.Server.2003.AD.EssentialService.ISM | ||
Parent Monitor | System.Health.AvailabilityState | ||
Category | Custom | ||
Enabled | True | ||
Alert Generate | True | ||
Alert Severity | Error | ||
Alert Priority | Normal | ||
Alert Auto Resolve | True | ||
Monitor Type | Microsoft.Windows.CheckNTServiceStateMonitorType | ||
Remotable | False | ||
Accessibility | Public | ||
Alert Message |
| ||
RunAs | Default |
<UnitMonitor ID="Microsoft.Windows.Server.2003.AD.EssentialService.ISM.ServiceCheck" Accessibility="Public" Enabled="onEssentialMonitoring" Target="AD2003Core!Microsoft.Windows.Server.2003.AD.EssentialService.ISM" ParentMonitorID="SystemHealth!System.Health.AvailabilityState" Remotable="false" Priority="Normal" TypeID="Windows!Microsoft.Windows.CheckNTServiceStateMonitorType" ConfirmDelivery="false">
<Category>Custom</Category>
<AlertSettings AlertMessage="Microsoft.Windows.Server.2003.AD.EssentialService.ISM.ServiceCheck.AlertMessage">
<AlertOnState>Error</AlertOnState>
<AutoResolve>true</AutoResolve>
<AlertPriority>Normal</AlertPriority>
<AlertSeverity>Error</AlertSeverity>
<AlertParameters>
<AlertParameter1>$Target/Host/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</AlertParameter1>
</AlertParameters>
</AlertSettings>
<OperationalStates>
<OperationalState ID="Error" MonitorTypeStateID="NotRunning" HealthState="Error"/>
<OperationalState ID="Success" MonitorTypeStateID="Running" HealthState="Success"/>
</OperationalStates>
<Configuration>
<ComputerName>.</ComputerName>
<ServiceName>IsmServ</ServiceName>
</Configuration>
</UnitMonitor>