Microsoft just released the beta of System Center Orchestrator 2012 (previously know as Opalis). http://blogs.technet.com/b/systemcenter/archive/2011/06/15/announcing-the-system-center-orchestrator-beta.aspx
This beta is public, could be downloaded and tested by everyone.
First, I invite you to read the Pre-requisites :
But also the Release Notes :
In these TechNet articles you will find useful information, like this one : Even if you are in a lab environment, don’t try to install System Center Orchestrator 2012 Beta on a Domain Controller, It will not pass the requirement check. (thank you to Adam and Ravi to notice that to me).
You will see that Microsoft did an awesome work on the installation process. It’s really easier than installing Opalis 6.3.
Basically, for installing this beta you will need a server with :
- Windows 2008 R2 Server (RTM or SP1, both supported)
- SQL 2008 R2
- .Net Framework 4
1. Download the System Center Orchestrator 2012 Beta file at the Microsoft Download Center : http://www.microsoft.com/download/en/details.aspx?id=26503
2. Extract the content of the file.
3. Run the setupsco.exe file.
4. If you want to install all the features (Runbook Designer, Console/Web Service, Runbook server) on the same server, select Install Orchestrator. The installer also gives the possibility to install each features independently.
5. No product key required for the beta, just accept the license agreement.
6. Select all the features that you want to install. Select everything for this first install.
7. By expanding, you have information about each features and their prerequisites :
8. The installer has a prerequisites checker :
9. Two level in the prerequisites, Critical will block the installation process, warning could be pass.
10. Orchestrator requires a service account to run runbooks and access remote system resources.
11. Go to your Active Directory console, create a new account, and add it in the Local Administrator Group of the server.
12. You also have to authorize this account to "Log on as a service". Enable this right in Administrative Tools -> Local Security Policy -> Local Policies -> User Rights Assignment.
13. Open "Log on as a service" policy and enter the service account that you just created.
14. Back to the Orchestrator 2012 beta installer and click on the Test button.
15. Database connection, Go to your SQL server, open the management studio, and create manually the Orchestrator database.
16. Add your service account as Credentials for the SQL server.
17. Grant this account as db_owner of the Orchestrator DB.
18. Go back to the Orchestrator installer, select Existing database and chose the database that you just created.
19. Orchestrator use a group (local group or Active Group) for authorizing access to the Run Book Designer. Go to your Active Directory console, create a new security group, add your user account and the service account created above as group member.
20. Back to the Orchestrator installer and select the group just created :
21. Check the box Grant remote access for the Runbook Designer.
22. Configure the port for the web service and Orchestrator Console.
23. Select the installation folder.
24. Review the summary, note that you could change any parameter directly from there.
25. Installation in progress…
26. After a few minutes, the installation is finished.
27. You could now enjoy the new Runbook designer.
28. And also the new Web Console based on IIS, .Net and Silverlight.
As you could see, Microsoft really did an awesome work on the installation process. Next post will present all the new features of System Center Orchestrator 2012 in details.