Saturday, February 16, 2013

Permissions for System Center Orchestrator runbooks

Okay, here's a good scenario on  System Center Orchestrator. You create a runbook that connects to a remote server. You tried to start/stop a service but it failed or gives you a warning or error. So how do you resolve this issue?

I've tried so many other ways as being told in other sites but the simplest thing worked out for me. 

Add the Orchestrator run as account as local administrator on remote server that the runbook is working with. And whoala, the runbook can now start/stop a service!

If you want to check other permissions required, check it out here.

No comments:

Post a Comment