We are ready to install SCORCH.
To start, before we will actually be able to install SCORCH, we have to install a few prerequisites.
- .NET Framework 3.5 SP1
- .NET Framework 4.0
- IIS (Web Server role)
Here is a video walk through:
Start by either extracting the DVD contents, or mounting the ISO (the TechNet ISO is currently labelled as en_system_center_2012_orchestrator_with_sp1_x86_dvd_1345499). Start by running the SetupOrchestrator.exe.
On the splash screen click the Install link.
On the Product Registration screen, fill in the Name, Organization and Product Key fields, and click Next.
Read and accept the License Terms, and then click Next.
On the Select Features screen, select what you want to install. In this lab example, we are installing all features onto the same server.
Next you need to provide a Service Account for running the Runbooks, and accessing remote systems. Note that the account must have “Log on as a service” rights. Enter the account details, and then click the Test button.
Once the credentials have been tested successfully, you will be able to click Next.
Now you need to configure the database. Provide the server and instance, and click the Test Database Connection button.
Only once the database connection has been successfully tested will you be able to click the Next button.
Now you can also specify the database name. In this lab example we will accept the defaults and click Next.
Now we need to configure the Orchestrator User Group. This group will have Administrative access to Orchestrator. You can locate and use an existing Security Group from Active Directory. Specify a User Group and click Next.
On the Web Services screen, you have the opportunity to change the ports used. For this lab example we will accept the defaults and click Next.
You can also change the installation location. For example, if you have a dedicated drive in the server for the Operating System, and a second drive for the middleware. Make the appropriate modifications if applicable, and then click Next.
New to System Center 2012, you can use Microsoft Update to find updates for the product. In a Production environment, you would probably not want to do this, since there will more than likely be Change Management controls around updating/patching. In this lab example, I am not going to enable Microsoft Updates for the product, so that in the future I will be able to document the update/upgrade process in detail.
Next, you can choose if you want to participate in the CEIP program. In a Production environment, this will probably not be accepted, as there may be some concern over private/personal data. In a lab/non-production environment though, I would personally choose to be a part of the program, because the information collected by Microsoft aids them in improving the product. If no one was willing to participate, then there would be no improvements.
Finally, review the information on the Summary screen, and click Install.
Once the installation is complete, you can select/de-select any of the listed checkboxes, and then click Close.
Here is a video walk through: