Microsoft’s own Jim Britt just posted a great article over on the Building Clouds blog that describes in detail System Center 2012 Orchestrator and service dependencies. While this is good general information to have, this can also prove to be key if you’re troubleshooting an issue relating to the start of dependent services. Jim does a fantastic job describing how System Center 2012 Orchestrator by default will install with all services set to
Automatic, however dependencies are lacking due to the fact that SQL cannot always be guaranteed to be installed locally on the Management Server. He then goes through some advanced configuration that will need to be done post-installation to ensure that core services for Orchestrator will properly start upon a reboot of a Orchestrator Runbook or Management server. You can check out Jim’s complete post at the link below.