Protected: SCOM Commands

There is no excerpt because this is a protected post.

Advertisements

Orchestrator 2012 R2 – Scheduling with Check Schedule

When working with scheduling runbooks you will see that you will need to work with both the Monitor Date/Time and the Check Schedule activity to get the most control out of when you can put a schedule in place. This post will cover the Check Schedule activity. Once a date/time is triggered by Monitor Date/Time,… Continue reading Orchestrator 2012 R2 – Scheduling with Check Schedule

Orchestrator 2012 R2 – Runbook – Scheduled Reboot of servers

This runbook will run on a schedule and incorporate an already created manual reboot runbook, so that you can then have the option of rebooting servers manually or via a schedule. This runbook will cover the following activities: Using the built-in Monitor Date/Time activity, to wait for a certain time to activate Using the built-in Check Schedule activity, to… Continue reading Orchestrator 2012 R2 – Runbook – Scheduled Reboot of servers

Orchestrator 2012 R2 – Runbook – Manual(Non-scheduled) Reboot of servers

This runbook will check a computer to see if it is reachable, put it into maintenance mode, restart it, and update a sharepoint list on success. It can be ran manually (ad-hoc) or invoked from another runbook. This runbook will cover the following activities: Using the built-in Get Computer / IP Status activity, based on a… Continue reading Orchestrator 2012 R2 – Runbook – Manual(Non-scheduled) Reboot of servers

Orchestrator 2012 R2 – Creating a static Computer Group

In my case, I wanted to perform scheduled reboots on the same group of servers on a recurring basis. One of the ways of storing the names of these servers was through the in-built Computer Groups area, so I will go through creating using that method. There are many ways of populating a list of servers for… Continue reading Orchestrator 2012 R2 – Creating a static Computer Group

Orchestrator 2012 R2 – Store Credentials in Orchestrator Variables

When you get into creating runbooks you realize pretty quickly that you can’t keep putting your own credentials into each runbook activity as a password change or account removal will ruin the runbooks. If your runbooks reference a central variable then any update to the variable will carry through to the runbook. This post will… Continue reading Orchestrator 2012 R2 – Store Credentials in Orchestrator Variables