In my lab environment there are two services which are failing occasionally and causing Orchestrator not to function. The Orchestrator management pack alerted me of these situations but was not auto-restarting the services when they went offline. The two alerts which are generated are:
Alert: System Center Orchestrator Management Service
Alert: System Center Orchestrator Runbook Service
Management Pack Name: Microsoft System Center Monitoring Pack for System Center 2012 Orchestrator
Management Pack Version: 184.108.40.206
Rule or Monitor: Monitor
Rule or Monitor Name: System Center Orchestrator Management Service
Rule or Monitor Name: System Center Orchestrator Runbook Service
Rule or Monitor Notes: This rule alerts when the service is offline.
Issue: The alert works correctly and is useful but the next step is to manually restart these services when they go offline.
Resolution: Created an override for each monitor to enable the built-in recovery to auto-restart the service.
Both of these alerts have diagnostics which are defined to restart the services but are not enabled by default.
To enable this functionality, create an override for the recovery task setting enabled to True as shown below:
There are three ways to address these particular alerts:
1) Do this override creation for each of the two monitors listed above in your environment discussed in this article.
2) You can manually restart the services by connecting to the computer with the computer management task (available in the Windows Computer Tasks available within the Windows Computers view)
3) Download and install the sample management pack which contains these two overrides and is available at: http://www.systemcentercentral.com/pack-catalog/orchestrator-management-pack-to-autorestart-services/