UiPath Installation and Upgrade

The UiPath Installation and Upgrade Guide

Azure Marketplace Deployment

Azure marketplace deployments allow you to deploy UiPath solutions directly from the Azure portal.

UiPath Orchestrator

This wizard allows you to deploy single or multi-node environments. The components are:

App Service (Web App)Used for hosting the web services required (eg. Orchestrator, Identity, WebHooks). All components are in the same App Service Plan. If you deploy a multi-node deployment the High Availability Add-on will be accessible using a Virtual Network Integration
SQL Database, single DataBaseThe SQL Database (and server) used by the web services.
Application insightsApplication insights used for logging autoscaling rules.
Storage AccountThe storage account used to store packages/libraries.
User Managed IdentityUsed to configure the deployment using scripts that are run on a Windows Virtual Machine.
Windows Virtual MachineTemporarily deployed Virtual Machine that will run scripts to configure the aforementioned Web Services (Web Apps). This machine uses the Managed Identity to authenticate to Azure. It gets deployed in a separate VNet together with a Network Interface Card and a separate storage account
Deployment ScriptThis is used cleanup Azure Resources (Configuration VM and all dependencies). This resource will automatically be removed at the end if successful.

[Optional] High Availability Add-on (HAA) Components:



Multi-node Orchestrator deployments use the RESP (Redis Serialization Protocol) for communication and thus can be configured using any solution relying on this protocol.
HAA is the only such solution supported by UiPath.
Full support is provided to users of Redis Enterprise with the purchase of an HAA module.

Linux Virtual MachineThere are three Linux VMs that are deployed together to form a High Availability Add-on cluster. The cluster gets deployed in a VNet together with Network Interface Cards for each node. The nodes are not publicly exposed and are connected to the Orchestrator App Service through Virtual Network Integration

Going Through the Wizard



In this step, you need to select the subscription, the Resource Group, and Region where you want the solution to be deployed.



You need to have Owner permissions on the Resource Group or Subscription to deploy since the deployments create a user-managed identity (see components).

Orchestrator Details

Orchestrator NameOrchestrator name will have a random suffix appended.
PasswordDefine the password that will be used for the host administrator and the default tenant administrator account (admin).
Orchestrator VersionSelect the version of the UiPath Orchestrator you want to deploy.
Orchestrator InstancesThe number of P2v2 instances that will be created (scaled to). Can be maximum 30.
Orchestrator SizeThis will deploy different versions of the SQL DataBase.
Small: < 100 robots (4 Core)
Medium: < 250 robots (8 Core)
Large: < 500 or more robots (16 Core)

Please note that if you selected one Orchestrator instance you will have the option to skip High Availability Add-on installation. If you chose to skip it, please not change the number of instances since that will be an unsupported scenario.

HAA Server Configuration

HAA Servers (VM) Admin LoginDefine the admin username for the High Availability Add-on virtual machines.
PasswordDefine the admin password for the High Availability Add-on virtual machines.
HAA Admin EmailDefine the admin email for the High Availability Add-on.
PasswordDefine the admin password for the High Availability Add-on.
High Availability Add-on LicenseHigh Availability Add-on license. If not provided you will have to enter a license in 30 days.
Virtual Machine SizeThe size of the three RHEL (Red Hat Enterprise Linux) virtual machines to provision. We recommend 2-4 CPU and 8-16 GB RAM. See here.
Virtual Network for HAAA virtual network that will be used to deploy the High Availability Add-on virtual machines. They will be deployed in a subnet and another subnet is required for the WebApp virtual network integration (private connectivity).
SubnetsTwo subnets required:
Virtual network subnet that will be used to deploy the High Availability Add-on virtual machines.
Virtual network subnet used for App Service/Web App VNet integration (private connectivity). If you are using an existing VNet, this subnet must be empty, configured (see azure docs) and only used for this purpose.

Orchestrator SQL Settings

Orchestrator SQL Server NameThe SQL server name will have a random suffix appended.
Orchestrator SQL Server Admin LoginDefine the admin username for the Orchestrator SQL server.
PasswordDefine the admin password for the Orchestrator SQL server.

Certificate Configuration

Token Signing Certificate (pfx)The certificate used for token signing.
The requirements for Microsoft App Service Certificates:
The requirements for UiPath Token Signing Certificate are:
The certificate pfx must meet all requirements.
PasswordToken signing certificate password.

The certificate used in this step could be generated using the following commands:

#Generate certificate directly in the LocalMachine personal store
 $cert = New-SelfSignedCertificate -Type Custom -KeySpec Signature `
    -Subject "CN=UiPathSelfSignedRoot" `
    -KeyExportPolicy Exportable `
    -HashAlgorithm sha256 -KeyLength 4096 `
    -CertStoreLocation "cert:\LocalMachine\My" `
    -KeyUsageProperty Sign `
    -KeyUsage CertSign `
    -NotAfter (Get-Date).AddYears(2)

#Create a secure string password for the certificate
$mypwd = ConvertTo-SecureString -String "1234" -Force -AsPlainText

#Export the certificate from the LocalMachine personal store to a file `mypfx.pfx`
Get-ChildItem -Path "cert:\LocalMachine\my\$($cert.Thumbprint)" | Export-PfxCertificate `
    -FilePath mypfx.pfx `
    -Password $mypwd `
    -CryptoAlgorithmOption TripleDES_SHA1

#Remove the certificate from the LocalMachine personal store
Get-ChildItem "Cert:\LocalMachine\My\$($cert.Thumbprint)" | Remove-Item

Tags Configuration

Here you can create tags for the resources created in the deployment.

Updated 3 months ago

Azure Marketplace Deployment

Suggested Edits are limited on API Reference Pages

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