UiPath Orchestrator

The UiPath Orchestrator Guide

Connecting Robots to Orchestrator



When deploying multiple Standard Robots from the same machine on Orchestrator, you need to have the same Machine Name and Machine Key for each. To retain the values in the fields, you can click Create Another in the Add Robot window. Alternatively, you can copy the Machine Name and Machine Key from an already deployed Robot by clicking More Actions > Duplicate.

From Orchestrator and the UiPath Robot Settings Window

Connecting the Robot to Orchestrator



Administrator rights are required to perform this procedure for Service Mode Robots.

  1. Create a Robot, as explained here.
  2. In the system tray, click the UiPath Robot icon. The UiPath Robot tray is displayed.
  3. Click the Options button and then select Settings. The UiPath Robot Settings window is displayed.
  1. In the Machine Key field, enter the key received from the user who created the Robot in Orchestrator (as obtained from the Machines page).
  2. In the Orchestrator URL field, enter Orchestrator’s address, such as
  3. Click OK. The Robot is now connected to Orchestrator and has the available status. Each time a Robot is registered to Orchestrator, a Robot user is automatically created and is assigned the Robot role. (You can view it in the Users page.)



The High-Density Robots feature only works if the same machine name and key are used when registering each Robot per user.

From the Command Line

  1. Create a Robot, as explained here. If you have multiple Robots on the same machine, you must provision them all to Orchestrator.
  2. Save the Machine key to the Clipboard or a file, as you need it to connect the Robot to Orchestrator.
  3. Open the Command Prompt.
  4. Go to the directory where your UiPath Robot is installed (by default C:\Program Files (x86)\UiPath\Studio). For example: cd C:\Program Files (x86)\UiPath\Studio.
  5. Use the --connect, -url and -key command line arguments, and the Orchestrator URL and the Machine Key to conenct the Robot to Orchestrator. For example: UiRobot.exe --connect -url -key ba1e4809-2f64-4965-bae2-efda62d20164. The Robot is now connected to Orchestrator and has the available status. If you have a High-Density environment, the Robots corresponding to each user are now connected to Orchestrator.

Automatic Enrollment of Robots

The connection string is a URL that contains the following information:

  • The Orchestrator URL - Identifies the Orchestrator instance the Robot connects to;
  • Tenant ID - Identifies the tenant the Robot connects to;
  • Domain name - Identifies the domain of the machine; this is only necessary if the machine is in a different domain than that specified for the WindowsAuth.Domain parameter in web.config (this is valid for subdomain machines as well). The domain needs to be in a two-way trust relationship with the one set for the WindowsAuth.Domain parameter.

Here are two examples of connection strings according to the machine's domain:

  • Same domain as specified in web.config -
  • Different domain than the one specified in web.config -



In order to deploy Robots to Orchestrator using connection string, the following are required:
the WindowsAuth.Enabled parameter from the web.config file has to be set to true
the WindowsAuth.Domain parameter has to be set to a valid domain
the Robot has to be installed as a Windows Service.

  1. Create a Robot, as explained here.
  2. In the Settings page, on the General tab, look for the Connection String field, and click Copy. The connection string is copied to the clipboard.
  1. Send the connection string to the Robot machine you want to connect to Orchestrator (via e-mail, USB stick etc.)
  2. Use an automatic deployment tool to install the Robots and provide the connection string copied above in the CONNECTIONSTRING parameter used with the UiPathStudio.msi installer. The Robot is connected to Orchestrator and is displayed as Available in the Robots page.

Updated about a year ago

Connecting Robots to Orchestrator

Suggested Edits are limited on API Reference Pages

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