This chapter will target the goal of having a proper Microsoft System Center Orchestrator 2012 R2 (SCORCH or Orchestrator) architecture in place. We're going to cover the Orchestrator components, their capability to be scalable, and their requirement to better address the question of the design to be chosen. By the end of this chapter, you will be able to identify what requirements you should keep in mind and assess before drawing or implementing Orchestrator.
Microsoft System Center Orchestrator 2012 R2 is a workflow automation product that interconnects with multiple technologies. With Orchestrator, you can target the following points in your datacenter:
Automation of repeated tasks (either system or manually triggered)
Interaction between products
The expected result of the automation of repeated tasks is for the administrative workload to be reduced, thereby improving the quality and performance of the IT staff and also improving on the datacenter dynamics.
In this opening chapter, we will address the following points:
Planning the Orchestrator architecture and deployment
Deploying a single-server solution
Deploying a multiple server solution