MPAuthor.DiagnosticAndRecovery 1.0.0.1 MPAuthor.DiagnosticAndRecovery Microsoft.SystemCenter.DataWarehouse.Library 6.1.7221.0 31bf3856ad364e35 Microsoft.SystemCenter.Library 6.1.7221.0 31bf3856ad364e35 Microsoft.Windows.Library 6.1.7221.0 31bf3856ad364e35 System.Health.Library 6.1.7221.0 31bf3856ad364e35 System.Library 6.1.7221.0 31bf3856ad364e35 Discovery $Target/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$ AppExists SOFTWARE\MPAuthor\DiagnosticAndRecovery 0 0 120 $MPElement[Name="MPAuthor.DiagnosticAndRecovery.Target"]$ $MPElement[Name="Windows!Microsoft.Windows.Computer"]/PrincipalName$ $Target/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/PrincipalName$ $MPElement[Name="System!System.Entity"]/DisplayName$ $Target/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/PrincipalName$ Values/AppExists Equal True AvailabilityHealth Error true Normal Error $Data/Context/Property[@Name='Name']$ wmiApSrv Custom GetErrorCode.ps1 computerName $Target/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/PrincipalName$ serviceName $Data/StateChange/DataItem/Context/DataItem/Property[@Name='Name']$ 60 Custom GetErrorCode.vbs $Target/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/PrincipalName$ $Data/StateChange/DataItem/Context/DataItem/Property[@Name='Name']$ 60 Custom Diagnostic/DataItem/Property[@Name='ErrorCode'] Equal 3 StartService.ps1 param($computerName,$serviceName) $service = get-service -name $serviceName $service.start() $service.WaitForStatus('Running',(new-timespan -seconds 10)) if ($service.Status -eq 'Running') {write-host "Service $serviceName started successfully."} else {write-host "Service $serviceName could not be started."} serviceName $Data/Diagnostic/DataItem/Property[@Name='ServiceName']$ 300 Custom Diagnostic/DataItem/Property[@Name='ErrorCode'] Equal 3 StartService.vbs $Data/Diagnostic/DataItem/Property[@Name='ComputerName']$ $Data/Diagnostic/DataItem/Property[@Name='ServiceName']$ 300 StateCollection MPAuthor Sample - Property Bag This management pack provides an example of a recovery running after a diagnostic. The recovery only runs if specific criteria is received from the diagnostic output. It also illustrates how to pass property bag data from the monitor to the diagnostic and the recovery. In this example, the diagnostic runs in response to a service monitor. If the specified service is stopped, then the diagnostic runs. The service used is the WMI Performance Adapter (WmiApSrv), but this can be changed in the properties of the monitor. The diagnostic runs a script that collects an error code value from the registry at HKLM\SOFTWARE\MPAuthor\DiagnosticAndRecovery\ErrorCode. If the error code is 3, then the recovery will run. If it is any other value, the recovery will not run. The recovery is a script that restarts the service. A sample diagnostic and recovery are provided for both VBScript and PowerShell. The functionality of each are identical and only one of the diagnostics should be enabled at a time. The monitor is targeted at a class called MPAuthor.DiagnosticAndRecovery.Target. This is discovered by creating a registry key at HKLM\SOFTWARE\MPAuthor\DiagnosticAndRecovery. This registry key must be on the same agent computer with the service being monitored. PowerShell Diagnostic VBScript Diagnostic MPAuthor Discover PropertyBag Target Class MPAuthor Sample Diagnostic and Recovery File size Please see the alert context for details. Script Monitor {0} PowerShell Recovery VBScript Recovery Service Monitor NotRunning Running Service Monitor {0} MPAuthor DiagnosticAndRecovery Target DiagnosticAndRecovery Target