orchestrator
2021.10
false
- Getting Started
- Requirements
- Best Practices
- Installation
- Updating
- Identity Server
- Troubleshooting startup errors
OUT OF SUPPORT
Orchestrator Installation Guide
Last updated Oct 31, 2024
Warning: Please keep in mind that this information pertains to
the version that you are upgrading to, NOT to the version that you are upgrading
from. As such, make sure that you read the correct details before
proceeding.
The update process can be different depending on whether:
- the previous version was set up with the Windows installer;
-
your Orchestrator instance is in a multi-node environment.
Important: Before upgrading, please visit the Hardware Reqirements, Software Reqirements and prerequisites pages, for the version you are upgrading to, as they may have changed. You need to ensure you meet all requirements prior
to upgrade.
Important: After upgrading, we recommend that you restart all your robots in order for them to apply the new settings.
Important: If your packages (activities and/or workflows) are stored in a shared folder, please note that the
UiPathOrchestrator.msi installer requires Write access to the aforementioned directory.
Important: Starting with v2020.4, there are more requirements for the SSL certificate of Orchestrator. Make sure you meet all prerequisites. For how to change your existing certificate, see Using a Certificate for the HTTPS Protocol.
Important: Double-check the selected installation path. Moving an installation from one location to another post-install is not supported.
Important: It is recommended to preserve the previous Orchestrator Application Pool identity type for Identity Server and Webhooks as
well. Otherwise, issues may occur while accessing the SQL server.
Important: If you are considering installing Insights, make sure that you select the
db_owner role as this is required when you configure the Insights SQL Server configuration.
Important: If you upgrade from an earlier version that has the Windows Authentication option selected, make sure to run the installer as an AD user.
To update Orchestrator from a version that was previously installed using the Windows installer, perform the following actions:
In a multi-node environment, upgrading is done differently on primary and secondary nodes. The below steps need to be taken to update all your nodes.
Note: Although you provide the admin passwords at host and default tenant level, they are not taken into account. Use your previous
passwords to log in.
Backup Files
Back up your automation packages,
web.config and UiPath.Orchestrator.dll.config files, and database.
Primary Node Installation
For Attended Installation: Run from the Admin Command Prompt the following command:
UiPathOrchestrator.msi OUTPUT_PARAMETERS_FILE=c:\temp\upgradeParams.json /lvx* upgrade.logUiPathOrchestrator.msi OUTPUT_PARAMETERS_FILE=c:\temp\upgradeParams.json /lvx* upgrade.logFor Unattended Installation: Run from the Admin Command Prompt the following command:
UiPathOrchestrator.msi PUBLIC_URL=https://hostname.local APPPOOL_USER_NAME=serviceAccount APPPOOL_PASSWORD=pass OUTPUT_PARAMETERS_FILE=c:\temp\upgradeParams.json /lvx* upgrade.log /QUiPathOrchestrator.msi PUBLIC_URL=https://hostname.local APPPOOL_USER_NAME=serviceAccount APPPOOL_PASSWORD=pass OUTPUT_PARAMETERS_FILE=c:\temp\upgradeParams.json /lvx* upgrade.log /QFollow through with the installation as described here.
Important: Do not forget to back up the
upgradeParams.json configuration file generated by the installation. This is to be used on subsequent, secondary node installations.
Secondary Nodes Installation
It is recommended to run the unattended install, using the
upgradeParams.json configuration file produced on the primary node. Run from the Admin Command Prompt the following command:
UiPathOrchestrator.msi SECONDARY_NODE=1 PARAMETERS_FILE=c:\temp\upgradeParams.json /lvx* upgrade.log /QUiPathOrchestrator.msi SECONDARY_NODE=1 PARAMETERS_FILE=c:\temp\upgradeParams.json /lvx* upgrade.log /QFlush Keys
If you are using HAA for cache management, flush all HAA cache keys from an Active-Active database using the following command:
crdb-cli crdb flush --crdb-guid <guid> [ --no-wait ]crdb-cli crdb flush --crdb-guid <guid> [ --no-wait ]Important: If you want to use the Concurrent Runtime license type, please note that when updating to v2020.4 from an older version, if you have High-Density Robots set up, the
number of runtimes per machine is automatically set to 1, and not the total number of Robots on that machine.
