- Getting started
- Understanding UiPath Robot
- Installation requirements
- Installing robots for unattended automations
- Configuring robots for unattended automations
- Deploying unattended automations
- Connecting robots for unattended automations to Orchestrator
- Setting up Windows Server for High-Density Robots
- Redirecting robots through a proxy server
- Implementing authentication with credential providers
- Configuring package signature verification
- Setting up package folders and network paths
- Configuring activity feeds
- Using EntraID users with multifactor authentication (MFA) for unattended robots
- Installing robots for attended automations
- Configuring robots for attended automations
- Integrations
- Governance
- Troubleshooting
Robot admin guide
Robot licensing
A licensing process most commonly starts with activating your Orchestrator license. Afterward, you license your Robot by connecting it to Orchestrator or from the Command Line, using the LicenseTool utility.
When your Robot is not connected to Orchestrator, you can activate the license with the help of the Command Prompt.
Attended licenses
To execute attended automations, you need to allocate one or more user licenses to your robots.
For this, you need to have a robot account in Orchestrator. Once the user license is assigned to a specific username, that user can run one or more attended automations on the computer under their username.
The following user licenses are available for attended automations:
- Attended
- Citizen Developer
- Automation Developer
Unattended licenses
To execute unattended automations, you need to allocate one or more robot licenses (or runtimes) to your robots, specifically to the machine that hosts your robots. The number of runtimes assigned to a machine represents the maximum number of concurrent executions. For example, with one runtime, you can execute only one unattended automation at a time. With five runtimes, you can execute up to five unattended automations at the same time, on the same host machine.
Depending on the type of automation, allocate the runtimes as follows:
- For foreground automations - allocate one runtime, as this type of automations are executed one at a time.
- For background automations - Windows machines require one runtime, as they execute one background automation at a time. Windows-Server machines can execute several background automations simultaneously, which represents a concurrent execution.
- For concurrent executions - allocate more than one runtime. The number of allocated runtimes determines how many automations you can execute simultaneously on the same machine.
The following runtimes are available for unattended automations:
- Production (Unattended)
- Testing
