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:

  1. Using the built-in Get Computer / IP Status activity, based on a pre-filled Orchestrator Computer Group, to determine whether the server is reachable
  2. Using the built-in Send E-mail Message activity upon failure to reach a server
  3. Using the SCOM Integration Pack’s Start Maintenance Mode to begin maintenance mode
  4. Using the built-in Restart System activity to perform the reboot
  5. Using the Sharepoint Integration Pack’s Create List item to update a Sharepoint List on success, it will also show time saved by this runbook.

Reboots_Manual_1

Notes

You do not have to use a Computer Group, you can specify one machine at the Get Computer / IP Status part

There are also many ways to get your list of computers, from reading a text file, getting the contents of an AD group, reading from a Sharepoint list, etc.

Pre-work/learning

Store Credentials in Orchestrator Variables

Creating a Computer Group

Send a Mail Message

Set up SCOM Integration Pack

Set up SharePoint Integration Pack

 

Steps

1. Get Computer/IP Status

Reboots_Manual_2

We are running through our list of servers by referencing our pre-made Computer Group.

The rest of the settings can stay as default.

Reboots_Manual_3

2. Link between steps 1 and 2 (failure)

If the result of Get Computer/IP Status is unsuccessful, then a notification e-mail will be sent in the next activity.

Reboots_Manual_15.png

3. Send Email

Reboots_Manual_16

The Subject field contains published info from the Get Computer/IP Status activity so that the computer name is featured.

The To field contains a variable that holds an my e-mail address.

4. Link between activity 1 and 3

If the result of Get Computer/IP Status is successful, then maintenance mode will be put on the computer.

Reboots_Manual_4

5. Start Maintenance Mode

Reboots_Manual_5

Reboots_Manual_6

  1. Add in your connection to SCOM
  2. Add in the Computer name that will be entered into Maintenance Mode, which will be the computer that was tested, you can reference this Computer name via the published data from that first step. Right-click, Subscribe, Published Data
  3. Enter a Reason, using the selection button to the right of the field helps with choices
  4. Enter the required duration of the maintenance window
  5. Add comments

6. Link between Activity 3 and 4

If Start Maintenance Mode returns successful, then the reboot can occur in the next activity.

Reboots_Manual_7

7. Restart System

Reboots_Manual_8.png

Reboots_Manual_9

Reboots_Manual_10

  1. Use the same reference to the computer that was tested
  2. Enter a message
  3. Enter wait time before the reboot
  4. Choose whether the reboot will be forced
  5. Enter credentials that have the rights to perform the reboot under the security section

8. Link between Activity 4 and 5

If Restart System returns successful, then the list update can occur in the next activity.

Reboots_Manual_11

9. Create List Item

Reboots_Manual_12.png

Reboots_Manual_13.png

  1. Enter the Sharepoint Configuration
  2. Fill in the required properties (What the list requires when adding a new item)
    1. List Name
    2. Job
    3. Result
    4. Time Saved (Minutes)

Resulting list

Reboots_Manual_14.png

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s