Implementing High-Density Robots in Windows 10: Limitations and Recommendations

Can Windows 10 machine be used for High Density Robot setup ?

Introduction: Windows 10, by default, does not support simultaneous logins. This is noteworthy in the context of setting up High-Density Robots, as multi-session capability is a key requirement. This article sheds light on the considerations and limitations of using High-Density Robots with Windows 10, and provides alternatives which allow multiple RDP sessions.


Limitations of Windows 10 with High-Density Robots:

Developing a High-Density Robots environment involves setting up multiple Robots which can simultaneously log on to the host machine using the RDP (Remote Desktop Protocol) protocol. However, Windows 10 inherently doesn't allow simultaneous logins, making it less than ideal for High-Density Robots.

Recommendations and Workarounds:

For High-Density Robot setups to function optimally, it is recommended to use a Windows machine that supports multiple RDP logins simultaneously. An example of such a platform is Windows Virtual Desktop (WVD) , which does support multi-session functionality.

For additional information on enabling multiple RDP sessions, consider reading: How To Allow Multiple RDP Sessions In Windows 11 and Windows 10.

Conclusion:

To summarize, Windows 10 is not typically recommended for High-Density Robot setups due to its limitations on simultaneous logins. However, solutions like Windows Virtual Desktop can facilitate the multi-session functionality required for such use cases.

Hi,
I have a high-density server where I have deployed two SAP-related processes, each using a different SAP login. When executed separately, both processes work fine, but when run concurrently, one of the automations fails. Can you help me identify how to prevent this issue?