Analyse l'intégrité du service Windows : service de messagerie intersite
Si le service ISM est arrêté en raison d'une intervention manuelle, revoyez votre procédure opérationnelle car ce service est nécessaire au fonctionnement du vérificateur de cohérence des données.
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 | Microsoft.Windows.Server.2003.AD.EssentialService.ISM.ServiceCheck.AlertMessage |
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>