Share with you experience gained in the field working with Orchestrator. Session focus on general runbook authoring.

Is Orchestrator the right tool for this task?

Is it technically feasible?

Development cost and effort? Time to recoup investment What ports and permissions will this use?

Closing the loop with ITSM integration

Incident Remediation User Provisioning Recovery Tasks Best candidates for runbook automation

• • • 1 time every month Takes 20 minutes to do 1 week to build runbook

• • • • 1 alert every day 1 st 2 nd line receives and forward (5 mins) line RDP and fix (15 mins) 1 week to build runbook

The runbook will first monitor this system for new objects, then it will… and if it is like that it will… then it will integrate with… and pass data into… …We don’t think it will take more than 14-18 months to build the solution. …By the way, we have never used Orchestrator before

Developers at Contoso often need to test new software versions. This is a time consuming process both for developers and the IT department. Contoso needs to automate this process.

Rename activities and links Re-color links

Success

Warning / Critical

”Could be”

Folder and runbook structure Naming convention Variables and hard coded values brings challenges From left to right

…a process specific log …a technical log …use logfiles …use SEND PLATFORM EVENT …enable activity specific logging

Action Request Collect Validate Record Execute

If you integrate your runbooks in Service Manger, you get the first four for free!

Infrastructure and roles Services Events Job history Queue Real time job dashboard

Sandbox Test Test Sandbox Pre-production

Sandbox Test Test Sandbox Pre-production AD production Exchange production VM production

Start small Plan BEFORE you start Integrate with Service Manager