Why Orchestrator Server and SQL server should reside on separate machines 1. What happens on running Orchestrator and Bots on the same server? 2. What if the server does not have Remote Desktop Services with multiple user logins? 3. Why High Density Robot servers do not work well with Multi-Tenant configuration ?
1. What happens on running Orchestrator and Bots on the same server? UiPath recommends running Orchestrator and the SQL database on a different server than your High Density robot server that is running Remote Desktop Services.
Answer: It is recommended having Orchestrator Server and SQL server on separate machines for multiple reasons:
i) Performance - allocate enough resources such as RAM / disk space
ii) Redundancy especially if running SQL as cluster
iii) Maintenance and DB Management
2. What if the server does not have Remote Desktop Services with multiple user logins? On trying to remote desktop into the server to connect the bot, a message that someone else is already logged in is obtained, and it forces user to disconnect them.
Answer: User would need to use a Windows Server machine and follow the documentation Setting up Windows Server For High Density Robots .
3. High Density Robot servers do not work well with Multi-Tenant configuration. The first tenant creates a machine for the High Density Robot, with a unique machine id. When the second tenant needs to create a machine for their use, they need to overwrite the first tenant’s machine id in order to connect the bot. As a result, the first tenant’s bot stops working.
Answer: This is not be possible by design. High Density machine can only connect to one tenant at a time and every tenant has a unique machine key. The only way to achieve that would be to use separate Robot machines.