70-247 Series: Part 4

 Design and Deploy System Center (19%) Continued…. Orchestrator The following components make up an Orchestrator deployment:
  • Management Server
  • Orchestrator Database
  • Orchestrator Web Service
  • Runbook servers
  • Runbooks
Management Server There can only be one Management Server in an Orchestrator deployment. The Management server does not need to be available for Runbook servers or Runbooks to function. If the management server is not available, the Runbook designer will not be available. Orchestrator Database For high-availability the Orchestrator database can be deployed on a Microsoft SQL Server cluster with at least two nodes. Orchestrator Web Service The Orchestrator Web Service must be installed on a server that is running IIS. The Orchestrator web service does not have to be available for Runbook servers or Runbooks to function. To provide high-availability and improve performance for the web service, deploy the web service to multiple IIS servers configured for load balancing. Runbook Servers For high availability, there should be at least two Runbook servers. If the primary Runbook server is unavailable, the Runbook can run on another server. Runbook servers are not designed to be clustered.  clip_image001  A minimum High-availability environment for Orchestrator would consist of the components shown in the image below.  clip_image002 Runbooks By default, Runbook servers can run 50 Runbooks simultaneously, to change this setting use the commands shown in the image below.
That's it for our introduction to Orchestrator, next up we will have a quick look at Service Manager.

Popular posts from this blog

Get local computer UUID/GUID using Windows Powershell

gPLink and gPOptions

PSLoggedOn Getting Started on Windows Server 2008 R2