- Release Notes
- Getting Started
- UiPath Assistant
- Installation and Upgrade
- Robot Types
- According to License
- Attended Vs Unattended Robots
- High-Density Robots
- Linux Robots
- Robot Components
- Licensing
- Connecting Robots to Orchestrator
- Processes and Activities
- Logging
- Robot JavaScript SDK
- Specific Scenarios
- Restarting Robot Components
- Windows Sessions
- Login Using Thales Luna Credential System
- Login Using NShield Key Storage Provider
- Redirecting Robots Through a Proxy Server
- Executing Tasks in a Minimized RDP Window
- Using Mapped Network Drives
- Stopping a Process
- Disable Stop Button
- Custom Package Folders and Network Paths
- CrowdStrike Integration
- Robot Citrix Apps Virtualization
- Troubleshooting
- Unresponsive Robot Over RDP
- Duplicate Execution Logs
- Frequently Encountered Robot Errors
- Increased Process Execution Duration
- Enforced Package Signature Verification
- Message Too Large to Process
- Errors When Running as Administrator
- NuGet Packages Not Accessible After Migration
- User Access Control Prompt and UI Automation Activities
- .NET required during installation
- Assembly Cannot Be Loaded From Network Or Azure File Share
- Activities cannot find .NET Runtime
High-Density Robots
High-Density Robots is a feature that ensures a full utilization of each machine at your disposal at its maximum potential. As a result, regardless of the Windows version a machine is running on, if you have multiple users on it, you can register a Robot on each of the users.
Any type of Robot, be it an Attended, Unattended, or NonProduction one can be configured in a High-Density environment.
The High-Density environment has the following advantages:
-
On a machine with a Windows Server (2012 R2, 2016, 2019, and 2022), or Azure Windows 10 Enterprise Multi-session operating system:
- you can run the same process with all Robots in the same time;
-
you can run different processes with all Robots in the same time.
Note: When the robot is deployed in service-mode, all users on the machine use the same connection to Orchestrator. Meaning that all robots from one machine will be connected to the same Orchestrator tenant.
If you register a new Robot in Orchestrator on a machine that is running the UiPath Robot service, you do not have to restart the service. It is recommended to wait at most 30 seconds for the heartbeat to be submitted.
To set up High-Density Robots on a Windows Server machine, please see the Setting Up Windows Server for High-Density Robots chapter.
LoginToConsole parameter has to be set on false for all Robots. See the Windows Sessions and UiPath.Settings File Description documents for more information on the functionality that LoginToConsole parameter refers to.
