![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(51.2, 85%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDP%3C/text%3E%3C/svg%3E)
System Center Orchestrator
A family of System Center products that provide an automation platform for orchestrating and integrating both Microsoft and non-Microsoft IT tools.
215 questions
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(150.4, 92%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EXM%3C/text%3E%3C/svg%3E)
Hi,
If the Orchestrator services are not visible on the secondary server, it may be due to a variety of reasons such as incorrect installation, configuration, or permissions.
To update the Orchestrator services on the secondary server, you should first troubleshoot the issue and identify the root cause of the problem. You can start by checking the installation logs and event viewer for any errors or warnings related to the Orchestrator services.
Additionally, you can try restarting the Orchestrator-related services and checking the permissions of the user account used to install and configure the Orchestrator services.
If the issue persists, you may need to reinstall or repair the Orchestrator services on the secondary server. To do so, you can follow the same installation steps as before, but select the repair option instead of the install option. This should update the Orchestrator services on the secondary server.
Orchestrator Runbook Server works in failover mode by design. When you deploy a second Orchestrator Runbook Server you have a failover for the active Runbooks automatically.