(For more resources related to this topic, see here.)
The installation of SCORCH is simple. You must plan the deployment appropriately according to your needs. This recipe discusses and provides steps on common planning tasks to be performed before inserting the DVD or mounting the ISO for organizations who have successfully deployed SCORCH.
The authors recommend you to review the latest information on SCORCH at http://technet.microsoft.com/en-us/library/hh420383.aspx as the requirements of the product and supported platforms are regularly updated by Microsoft.
There are three planning categories, people, process, and the technology (SCORCH product).
SCORCH deployment type
Deployment type | Description |
Single Server | All SCORCH roles installed on one physical or virtual machine This scenario is typically implemented in test environments but is fully supported in production. This however becomes a single point of failure for highly automated environments. |
Multi-server | The SCORCH roles are separated and installed on one or more machines |
Component | Requirements |
Management Server |
|
Orchestration database |
|
Runbook Server |
|
Orchestrator Console/Web Service |
|
Orchestrator Runbook Designer |
|
SCORCH 2012 SP1
It is required only for the computer running the console in its web browser but not the Web Service server.
Account/Group | Type | Notes |
Orchestrator management service | Service account | Create an Active Directory user account for this service. This is the main management server service account and it is granted log on as a service during the installation. |
Orchestrator Runbook monitor service | Service account | Typically this is the same account as the Orchestrator Management Service. |
Orchestrator Runbook service | Service account | Same user account as the Management and Runbook Server monitor service in a single deployment but can be different for multi-server deployments; Active Directory domain account recommended. |
Runbook authors (SCO_ADMINS) | Group | Create an Active Directory group. This group will have the equivalent access of full administration to the SCORCH deployment. |
Runbook operators (SCO_CON_USERS) | Group | Create an Active Directory group. This group will have the equivalent access of a Runbook operator to the SCORCH deployment. |
Installation user | User | The user with full administrative rights on the SCORCH servers is required to perform the installation and configuration of the SCORCH deployment. |
Source | Targeted computer | Default port | Configurable |
Runbook Designer | Management Server | 135, 1024-65535 | Yes. |
Management Server, Runbook Server, and Web Service | Orchestration database | 1433 | Yes; specified during the installation on the SCORCH supported version of Microsoft SQL Server. This is the case where the SQL Server instance is not using the default port. |
Client browser | Orchestrator Web Service | 81 | Yes; during the SCORCH installation. |
Client browser | Orchestration Console | 82 | Yes; during the SCORCH installation. |
The planning activities discussed are the minimum activities the authors recommend. The tasks performed at this stage will ensure that you ask for and plan for all your requirements before investing time in the actual installation. An additional benefit is identifying any people or budgetary risks before the deployment.
There are two additional planning areas which are typically ignored in technology focused deployments. These areas are communication strategies and stakeholder management.
Communication strategy
One of the inaccurate myths of SCORCH is that it would automate the IT professional. SCORCH when implemented right would improve efficiency but will not replace people. On the contrary you need to communicate with the people who perform the manual tasks as they hold the key to how to best automate their efforts. Early engagement with all IT team members should be one of your key planning tasks.
Stakeholder management
Stakeholders are all users affected by the SCORCH deployment. An important category of stakeholders are the management team responsible for policy creation and enforcement. Automation without organization buy in may lead to conflicts at the political level of your organization. An example of such a scenario is the ability to create Active Directory user accounts with rights to specific organization areas and restricted resources.
I remember deciding to pursue my first IT certification, the CompTIA A+. I had signed…
Key takeaways The transformer architecture has proved to be revolutionary in outperforming the classical RNN…
Once we learn how to deploy an Ubuntu server, how to manage users, and how…
Key-takeaways: Clean code isn’t just a nice thing to have or a luxury in software projects; it's a necessity. If we…
While developing a web application, or setting dynamic pages and meta tags we need to deal with…
Software architecture is one of the most discussed topics in the software industry today, and…