---
sourceDocument: Yokohama Data and Automation
sourceDocumentLink: https://www.servicenow.com/docs/r/yokohama/integrate-applications

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama Data and Automation

ft:clusterId :

    - crint

bundleId :

    - crint

workflow :

    - Creator


---

# High density robots in RPA Hub

# High density robots in RPA Hub {#ariaid-title1}

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Execute multiple automations (bot processes) simultaneously and independently on a single Windows Server machine using high density robots.

## High density robots overview {#high-density-robots-rpa-hub__section_ttz_wsn_mdc}

High density robots leverage the Remote Desktop Services to execute multiple automations simultaneously on the same Windows Server machine. High density robots can run the same automation or run different automations in separate user sessions on the same machine. The machine must support multiple user sessions at the same time.
This setup maximizes resource utilization by leveraging the machine's capacity to execute several bot processes in parallel.

While configuring unattended robot, you can select the High Density Robot option to create multiple robots with the same machine name. All the high density robots with the same machine name can have different
screen resolutions. But it is ideal for all high density robots associated to the same bot process to have same screen resolution value. For more information about these fields, see [Create an unattended robot in RPA Hub](https://www.servicenow.com/docs/EekFWMReYnVUiRxutOZACw "Create an unattended robot in RPA Hub to run the unattended bot process.").  
Note:  
The machine that is associated with high density robots can't be associated with a non-high density robot. If there are multiple robots with the same machine name marked as high density robots, then none of the robot can be
converted as a non-high density robot.

High density robots can't be added to the robot pool.

## High density robots key features {#high-density-robots-rpa-hub__section_vsy_25n_mdc}

* Runs multiple automations independently on the same machine.
* Reduces the number of machines required, lowering infrastructure costs.
* Enables each robot to operate in its isolated session, which helps preventing overlap or interference.
{#high-density-robots-rpa-hub__ul_fb2_h5n_mdc}

## Configuring high density robots {#high-density-robots-rpa-hub__section_iqz_v3b_d1c}

To configure the high density robots, see [Create an unattended robot in RPA Hub](https://www.servicenow.com/docs/EekFWMReYnVUiRxutOZACw "Create an unattended robot in RPA Hub to run the unattended bot process.").

To convert existing unattended robots to high density robots, see [Convert existing unattended robots to high density robots](https://www.servicenow.com/docs/_oC1bo6WW6tkU4NtsJuX2g "Run multiple unattended automations simultaneously on a single machine by batch converting one or more existing robots to high density robots using the Actions on selected rows option.").
**Related concepts**   

* [High density robots in Unattended Robot](https://www.servicenow.com/docs/bm6ELWrtgpsDkJTuH1E4oQ "Execute multiple automations simultaneously and independently on a single Windows Server machine using high density robots.")  
**Related tasks**   

* [Set up Windows Server machine for high density robots](https://www.servicenow.com/docs/QBhmul9z4F2AlXGicmMfJA "Set up the environment for high density robots on a Windows Server machine by installing a Remote Desktop Session Host. Then, add robot user names who can connect to the machine. It enables them to establish Remote Desktop Protocol (RDP) connection to the Windows Server machine.")
* [Set up Unattended Robot](https://www.servicenow.com/docs/KbOVgbv9bcgjote_b3E0~A "Set up the Unattended Robot application to establish a connection between a robot and the ServiceNow RPA Hub instance.")