UiPath Installation and Upgrade

The UiPath Installation and Upgrade Guide


Identity Server and Orchestrator are installed together on the same IIS server. Please read here how to proceed with Orchestrator installation.

By default, the installer uses the same database for Orchestrator and Identity Server, but you can specify a different database during installation. The installed Identity Server address is https://OrchestratorURL/identity.



For large deployments, we recommend using a separate database for Identity Server.

Double-check the selected installation path. Moving an installation from one location to another post-install is not supported.

Performing a Clean Installation

The results of performing an Orchestrator installation are the following:

Performing an Update

The results of performing an Orchestrator update are the following:

  • Pre-existent Orchestrator data such as users, tenants, host or default settings are propagated to Identity Server.
  • Orchestrator's UiPath.Orchestrator.dll.config file is updated with Identity Server specific keys.
  • Identity Server's appsettings.json file is updated with Orchestrator specific settings (encryption keys, caching, Redis settings, etc.).



During Orchestrator update, the installer cannot read an encrypted SecureAppSettings section . In order to read the EncryptionKey from Orchestrator's config file and then migrate it into Identity Server's appsettings.Production.json file, the key must be plain text. You need to manually decrypt the section before updating Orchestrator. After the Orchestrator update process was finalized, remember to re-encrypt the SecureAppSettings section in UiPath.Orchestrator.dll.config.

If you have any external providers enabled in UiPath.Orchestrator.dll.config, you are prompted about the manual changes you need to perform in the external providers' location. Read here about the manual changes you need to perform.

For security reasons, for the certificate used to sign the access tokens generated by the Identity Server, make sure to use a public key on 2048 bits. The certificate's location has to be set within appsettings.Production.json's Signing Credential section.

After updating your Orchestrator to v2020.4+, the Profile page won't display login attempts previous to that update, but all the details are still accessible from Orchestrator's database.

Updated about a year ago


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.