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.

Note: For installations on Windows Server machines (that enable concurrent execution - HD Robots), you must provide paths that are specific to each user. Using the same shared folder for all users in HD environments is supported with some limitations. Find out more in the custom package folders and network paths documentation.

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.

Note: To use HD Robots, the 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.