UiPath Orchestrator Guide

Updating Using the Windows Installer

The update process can be different depending on whether you installed the previous version using the Windows installer, or the scripts, or you have installed Orchestrator in a multi-node environment.

Important!

If you have all UiPath products on the same machine, they all need to be updated. Trying to update only one deletes the others.
It is recommended to update Orchestrator in an attended mode, as the database is created or updated at setup. As a result, during the update process, you are prompted if you want to use an existing database or create a new one.

Previous Version Installed With Scripts

To update Orchestrator from a version that was previously installed using the scripts, perform the following actions:

  1. On the machine on which the old version of Orchestrator is installed, open IIS.
  2. Navigate to the Orchestrator website and, in the Actions section, click Stop. The Orchestrator website is stopped.
  1. Back up your automation packages, web.config file, and database.
  2. Open the Web.config file.
  3. Copy the value of the EncryptionKey parameter.
  4. Run the UiPathPlatform.msi Windows installer from the command line by also providing the encryption key from the previous installation, such as UiPathPlatform.msi APP_ENCRYPTION_KEY=encryption_key_from_old_installation. The installation wizard starts.
  5. Fill in the information as explained here, by providing the same SQL database from the previous installation. Orchestrator v2018.2 is installed with the UiPathOrchestrator2018.2 name.
  6. Open the v2018.2 Web.config file, and copy any settings that you have customized in the previous install if any.
  7. Save and close the web.config file.
  8. If your workflows were kept on the disk, copy the NuGet packages and their directory structure from the previous version and copy it to the v2018.2 location.
    • If you are updating from 2016.2 - Move them in the Default tenant (C:\Program Files (x86)\UiPath\Orchestrator\NuGetPackages\Tenants\Default). This step is necessary as the option to segregate data among tenants was not available in that version, and you have to decide how to sort out your packages.

Important!

Restart the UiPath Robot service on all Robot machines you have connected to Orchestrator.

Previous Version Installed With Windows Installer

To update Orchestrator from a version that was previously installed using the Windows installer, perform the following actions:

  1. On the machine on which the old version of Orchestrator is installed, open IIS.
  2. Navigate to the Orchestrator website and, in the Actions section, click Stop. The Orchestrator website is stopped.
  3. Back up your automation packages, web.config file, and database.
  4. Run the v2018.2 UiPathPlatform.msi Windows installer.
  5. Fill in the information as explained here. Orchestrator v2018.2 is installed with the UiPathOrchestrator2018.2 name, the database is updated and all your data is migrated.

Important!

Restart the UiPath Robot service on all Robot machines you have connected to Orchestrator.

Multi-node Environment

If you have a load-balanced environment for Orchestrator, the following steps need to be taken to update all your nodes:

  1. On all nodes, open IIS and stop the Orchestrator website.
  2. Back up your automation packages, web.config file, and database.
  3. On all nodes, run the UiPathPlatform.msi Windows Installer and fill in the information as explained here, using the same SQL Sever and Elasticsearch (if any). Orchestrator v2018.2 is installed with the UiPathOrchestrator2018.2 name.

Note:

If your previous multi-node installation was done with scripts, please also follow the 4-10 steps described above.

  1. Execute the Configure-Platform.ps1 script on the primary node and then all the secondary nodes as explained here.
  2. Restart the UiPath Robot service on all Robot machines you have connected to Orchestrator.

Important!

If you want to use the Concurrent Runtime license type, please note that when updating to v2018.2 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.


Updating Using the Windows Installer