What’s the deal with the Runbooks?

Yup, there’s a difference between runbooks and runbooks. Thank you Microsoft for making it easy for us! Let me break it down for you.

On the Orchestrator’s TechNet page we can find the following text:

Topics include how to write, test, and deploy a runbook with System Center 2012 – Orchestrator.

And on the Service Management Automation (SMA) page we can find this:

You automate your tasks by using runbooks, which run Windows PowerShell commands.

So, same name on two different products. With a tiny little difference thanks to the keyword “PowerShell”. Where Orchestrator runbooks are based on activities, the SMA runbooks are completly based on Powershell. Or to be more specific Powershell workflows.

But is it really two different products?

SMA is actually located on the Orchestrator media.

SCOsetup

Post-installation it would look something like this on the Orchestrator server:

scoprocesses

And liks this on the SMA server:

smaprocesses

The “Runbook Service” name is used in both products! (With a slightly different naming convention)

What about the runbook execution service in Orchestrator?

scoexecution

And SMA?

smaexecution

What this? Orchestrator.Sandbox.exe!? Ok..

I guess we can conclude that both products are definitely related!

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