Leverage Service Manager to allow end users to trigger Orchestrator runbooks




Why do I think that?


Although you can use runbooks to heavily automate processes, in some situations you need to pass information to that runbook for it to be able to do anything. For example: the details of the virtual machine template that you want use to provision a new VM using VMM, or the details of the database that you want to recover using DPM. By hooking System Center Service Manager into Orchestrator, you can create forms in SCSM that allow data to be passed directly to Orchestrator.

For example, you could create a runbook in Orchestrator that allows for the recovery of a SQL Server database by leveraging Data Protection Manager. You can then configure SCSM so that a portal page is available that allows users of that database to perform database recovery themselves. By linking SCSM to Orchestrator, you can query the DPM server to populate a drop down list of available recovery points, allowing the portal user to specify which recovery point they want to recover from rather than having to request a recover operation be performed by a DBA or DPM administrator.

As an administrator, leveraging SCSM, Orchestrator, and DPM, you can get all the back-end stuff working so that from perspective of a database user, recovery of a database becomes as simple as recovering a file from a folder using the Previous Versions of Files functionality.

SCSM can also be configured to automatically execute Orchestrator runbooks in response to jobs submitted through the SCSM Self Service portal. As with all the system center products, the whole is a lot more than the sum of its parts.

Please or Register to post comments.

What's Hyperbole, Embellishment, and Systems Administration Blog?



Orin Thomas

Blog Archive

Sponsored Introduction Continue on to (or wait seconds) ×