Design and Deploy System Center (19%) Continued….Orchestrator The following components make up an Orchestrator deployment:
Orchestrator Web Service
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. A minimum High-availability environment for Orchestrator would consist of the components shown in the image below. 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.
Use the following syntax to get the local computer's UUID/GUID using Windows Powershell: get-wmiobject Win32_ComputerSystemProduct | Select-Object -ExpandProperty UUID Add -computername after the WMI class to find a remote computer's UUID, example: get-wmiobject Win32_ComputerSystemProduct -computername RANTPC | Select-Object -ExpandProperty UUID
gPLink is a property for sites, domains and organisational units that contains a prioritised list of GPOs linked to the node. gPOptions is a property that contains all Block Policy Inheritance settings for the node. To manage GPO links on a node, you must have read and write access to the gPLink and gPOptions properties.
PSLoggedOn is a tool I downloaded to allow me to find out which computers a user is currently logged on to. Getting it up and running wasn’t exactly easy. I’m running a Windows Server 2008 R2 test environment. The first error I encountered was: Error browing network: The list of servers for this workgroup is not currently available. Note: I kept the spelling mistake from the error message to make it easier to find via search engines. To get past this error, you have to enable and start the “Computer Browser” service. Then I started getting the error telling me that the Administrator is not logged on. That’s simply not true because I am logged onto another server (Name: ELARA): I turned the firewall OFF OFF OFF (It is a test network after all). I enabled Network Discovery and to do that I went on a service starting frenzy: DNS Client, Function Discovery Resource Publication, SSDP Discovery, and UPnP Device Host, Computer Browser After all that, I ran the script against the se