I was going to run through a step by step install but noticed that Christopher Keyaert, a regular poster on the Operations Manager forums, has already completed an excellent walk through here.
Christopher creates the Orchestrator database and manually assigns the Orchestrator service account db_owner rights part way through the install which gets around the issue mentioned in my post below.
If you create the Orchestrator service account as a local windows administrator with log on as a service rights then you might well see the following error at the end of the install:
“Post-install configuration failed: : Threw Exception.Type: System.ServiceProcess.TimeoutException, Exception Error Code: 0×80131906, Exception.Message: Time out has expired and the operation has not been completed.”
If you check in the SQL Server error log you’ll see “login failed” errors for the Orchestrator service account.
This is because the install doesn’t assign any SQL rights to the Orchestrator service account. The database gets created by the user that is logged in and doing the install who will need SQL SysAdmin rights. But the Orchestrator service account still needs rights on SQL to function.
No definitive list of rights is provided yet but after the install (when the Orchestrator database has been created), I created a login to SQL for the Orchestrator service account and made it a db_owner on the Orchestrator database. Then I rebooted the box. This resolved the error and it all seems to work again.
Move over Opalis – there is new kid on the block. System Center Orchestrator 2012 beta is now available with some great training videos and documentation.
All the details on the Orchestrator 2012 blog.
