Subscribe

# Updating Using the Azure Script

### 📘Important!

If you have invalid cron schedules and you upgrade your Orchestrator instance from v2018.1.x or v2018.2.x to v2018.4.x, they are not going to work anymore. This occurs due to a change in the Quartz.NET validation code. Please make sure your cron expressions are valid before updating your environment.

1. Open the AzurePublishParameters.json and AzureApplicationSettings.json files generated on your previous deployment using a text editor such as Notepad++.
2. Download the latest available UiPathOrchestrator.zip archive.
3. Unblock the UiPathOrchestrator.zip file using the PowerShell command Unblock-File. For example, Unblock-File .\UiPathOrchestrator.zip.
4. Unarchive the UiPathOrchestrator.zip.
5. Run the Publish-Orchestrator.ps1 script in PowerShell using the values found in the AzurePublishParameters.json and AzureApplicationSettings.json files, as follows:
Publish-Orchestrator.ps1 
-action Update
-package "path/to/package" 
-activitiesPackagePath "path/to/UiPathActivities.zip"
-encryptionKey "encryptionKey from AzurePublishParameters.json" 
-packagesApiKey "packagesApiKey from AzureApplicationSettings.json"
-activitiesApiKey "activitiesApiKey from AzureApplicationSettings.json" 
-publishSettingsPath "path/to/publishSettings"
-sessionStateMode "sesionStateMode from AzurePublishParameters.json" 
-sessionStateSqlConnectionString "sessionStateSqlConnectionString from AzurePublishParameters.json"
-machineKeyDecryption "machineKeyDecryption from AzurePublishParameters.json" 
-machineKeyDecryptionKey "machineKeyDecryptionKey from AzurePublishParameters.json"
-machineKeyValidation "machineKeyValidation from AzurePublishParameters.json" 
-machineKeyValidationKey "machineKeyValidationKey from AzurePublishParameters.json"


### 📘Note:

If you are using Redis in your multi-node installation, please include the following parameters:
-redisServer "#{RedisServer}" 
-redisPassword "#{RedisPassword}" 
-redisPort #{RedisPort} 

Where:

• package "path/to/package" - Mandatory. Indicate the full path of the UiPath.Web.zip archive;
• publishSettingsPath "path/to/publishSettings" - Mandatory. Specify the full path of the [appServiceName].PublishSettings file.
• -activitiesPackagePath - Optional. Specify the full path of the UiPathActivities.zip archive, which is included by default, starting with v2018.4.4, in UiPathOrchestrator.zip. This enables you to install the local activity feed in Azure at install-time.

### 📘Important!

If you are using a local path for NuGet packages and/or activities ("~/NuGetPackages", "~/NuGetPackages/Activities") and you decide to change that location using the NuGet.Packages.Path or NuGet.Activities.Path parameters, please make sure to include the following to the publish script:
-foldersToSkip @("\\path\\to\\packages", "\\path\\to\\activities").

It is important to add two backslashes to the paths in this parameter, as it is an array which contains regular expressions and backslashes have to be escaped.

This procedure generates two files:

• AzurePublishParameters.json
• AzureApplicationSettings.json.

### 📘Important!

If your web app is running inside an Azure Stack\Azure Pack\ASE, you have to add Orchestrator's IP to the SQL Server's firewall settings. This is required so that the web app can have access to the database.

1. Store the AzurePublishParameters.json and AzureApplicationSettings.json files to a preferred location, as you need them for future deployments.
2. If you are using Redis for cache management, flush all Redis cache keys, using the FLUSHALL or FLUSHDB`command. More info on them is available here or here.
3. Start the Orchestrator app service. Enjoy using Orchestrator on your Azure Portal.
4. Restart the UiPath Robot service on all Robot machines you have connected to Orchestrator. If you are updating from v2016.2, please note that you also need to add the username and passwords for all your Robots before restarting the service.

### 📘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.

Updated 2 years ago