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.

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. Run the Windows installer for Orchestrator v2018.1 (UiPathPlatform.msi).
  3. Fill in the information as explained here. Orchestrator v2018.1 is installed with the UiPathOrchestrator2018.1 name.
  4. Navigate to the location of the v2018.1 Web.config file. Its default location for the 2018.1 version is the C:\Program Files (x86)\UiPath\Orchestrator directory.
  5. Open the Web.config file.
  6. Change the value of the EncryptionKey parameter to match the one of the EncryptionKey in the older version.
  7. Set the Database.EnableAutomaticMigrations value to true. This enables you to use an existing database, that you set after installation.
  8. Change the value of the connectionString database parameter to point to the database used in the version you want to update.
  9. If you are migrating from a 2016.2 version, also make the following changes:
    • Change the values of the decryptionKey and validationKey attributes in the machinekey node to match the ones in the 2016.2 version.
    • Change the value of the NuGet.Packages.ApiKey parameter to match the one of the apiKey in the 2016.2 version.
    • Change the value of the NuGet.Packages.Path parameter to match the one of the packagesPath in the 2016.2 version.
  10. Copy all other custom values you had in the new web.config file.
  11. Save and close the web.config file.
  12. Start Orchestrator v2018.1 site in IIS. The old database is migrated, and you can use Orchestrator with all the data that existed in the previous version.
  13. Copy the automation packages in the 2018.1 folder, as follows:
    • 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 is available in v2018.1, and you have to decide how to sort out your packages.
    • If you are updating from 2017.1 - If the workflows were kept on the disk, manually copy the directory structure from the old version in the new installation folder.

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.
  1. Back up your automation packages, web.config file, and database.
  2. Run the Windows installer for Orchestrator v2018.1 (UiPathPlatform.msi).
  3. Fill in the information as explained here. Orchestrator v2018.1 is installed with the UiPathOrchestrator2018.1 name, the database is updated and all your data is migrated.

Updating Using the Windows Installer