“How can System Center 2012 Orchestrator help me with System Center 2012 Operations Manager (SCOM)?” is a question I still get reasonably often. There are definitely many ways Orchestrator can help with SCOM, from maintenance mode, to alert remediation, to creating custom monitoring. Here are four runbooks every SCOM administrator should look into for smoother monitoring operations.
This sample runbook is critical because it eliminates the need for the old “Green Machine” utility or heavy PowerShell scripts that scan every monitor looking for monitors that are red, but have no alert. In fact, it does these legacy solutions one better, as it addresses the problem “as you go”, resulting in a much lighter footprint.
This sample runbook provides a way to go beyond setting up VBScript based recovery tasks in SCOM monitors, providing a way to restart any service that raises an alert in SCOM from a single runbook!
If you are monitoring Linux and UNIX systems in SCOM and using he daemon monitoring template (in the Authoring workspace of the SCOM console), this runbook is one you should check out. It will restart *NIX daemons with the Run SSH Command activity in Orchestrator.
Here’s a computer maintenance mode runbook that will put any computer into maintenance mode, Windows, Linux or UNIX.
These are not runbooks, but articles related to Orchestrator that may give you ideas for solutions of your own.
Hopefully this example motivates you to check out a few other runbook samples that can make a big difference in your environment. If this one was helpful, check out some of these Orchestrator articles.
Orchestrator JumpStart Series