SCOrch 2019 - Orchestrator Runbook Service account

Chris.Pierce 101 Reputation points

A few months back, I installed SCOrch 2019 onto a server (both the management server piece and the runbook server piece).

Yesterday, I changed the service account used for the Orchestrator Runbook Service. Now, runbooks will not run when triggered by Service Manager 2019 workflows.

I have verified that the new service account is a local admin on the server, and it has been added to 'Logon as a Service' within local security policy.

Any ideas why runbooks aren't running?

thank you,

System Center Orchestrator
System Center Orchestrator
A family of System Center products that provide an automation platform for orchestrating and integrating both Microsoft and non-Microsoft IT tools.
219 questions
0 comments No comments
{count} votes

Accepted answer
  1. Leon Laude 85,726 Reputation points

    Hi @Chris.Pierce ,

    You update the Orchestrator service account by going to the Services.msc and there search for the Orchestrator services and change the account.


    In addition to that, you must also change the account in the Application Pool "System Center 2012 Orchestrator Web Features" with IIS Admin.

    If you specified Windows Authentication to Orchestrator Database during setup (default and recommended), the new Account must have a login in the Database Orchestrator Database or the SQL Instance, and be a member of the SQL-Roles:

    • Microsoft.SystemCenter.Orchestrator.Admins
    • Microsoft.SystemCenter.Orchestrator.operators
    • Microsoft.SystemCenter.Orchestrator.Users


    If the reply was helpful please don't forget to upvote and/or accept as answer, thank you!

    Best regards,

    1 person found this answer helpful.

0 additional answers

Sort by: Most helpful