- Getting started
- Understanding UiPath Robot
- UiPath Assistant
- 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
- Adjusting registry settings for execution in minimized RDP windows
- Using network locations
- Setting up Linux robots
- Configuring package signature verification
- Setting up package folders and network paths
- Configuring activity feeds
- Setting up non-persistent VDIs - follow up with Sai
- Installing robots for attended automations
- Configuring robots for attended automations
- Integrations
- Troubleshooting
Robot admin guide
High-density robots
In a UiPath High-Density (HD) environment, commonly known as HD robots, multiple robots run concurrently under different user accounts on Windows Server machines. The machine allows as many concurrent executions (or user accounts) as the number of runtimes set for the machine template in Orchestrator.
Because each user has its own unique environment and access permissions, you must provide each robot with user-specific paths to navigate the system or to access certain files or folders.
A High-Density environment has the following particularities:
-
Requires Windows Server or Azure Windows 10 Enterprise Multi-session OSs.
-
Requires the
LoginToConsoleparameters to be set tofalsefor all robots. -
You can execute the same automation with all Robots at the same time.
-
You can execute different automations with all Robots at the same time.
-
In Service Mode installations, all robots operating on the machine connect to the same Orchestrator instance.
-
If the Robot Service is already active, you can add a new robot on the machine without restarting the service.
