Sharing of same robot machine under different different units

Help
1

Hi, I ve read here that we can have multiple robots on the same machine

From the Command Line
1.Provision a Robot to Orchestrator, as explained above. If you have multiple Robots on the same machine, you must provision them all to Orchestrator.

https://orchestrator.uipath.com/v2018.2/docs/connecting-robots-to-orchestrator

However, when I’m trying to add the same robot under another organizational unit, it tells me the user XXX from machine XXX is already used by another robot.

Does that mean:

  1. We cannot use the same user in the same machine as 2 robots
  2. If we want to create 2 robots out of the same machine, we have to create another user account.
  3. If 2 Is true, will the 2 robots be using the same license? (Is it 1 license per machine or 1 license per account)
  4. If 2 is true, what will happen if 2 processes run at the same time in the 2 accounts?

And if there are any documentation regarding this topic, please kindly share.

2

Hi,

to summarize:

  1. True: one user=one robot.
  2. True
  3. One HD robot = one license. So i.e. one server has 3 users(hd robots), this requires 3 licenses.
  4. HD setup can run processes parallel. With correct configuration and development design this is achievable.

more info can be found:

And another good discussion to read:

4

Hi, thanks.
but high density robot can only be run on server OS not desktop OS?

5

AFAIK yes. You can’t really log in several users simultaneously to a Windows desktop OS, so it’s not exactly an UiPath specific limitation.

6

Right, apologies. Too many questions running in my head at the sametime.

But I’m wondering what would happen if I did schedule 2 process on 2 robots on a same machine at the same time. I assume one would fail, but what would be logged on orchestrator?

And re this part of the documentation:

When online and connected to Orchestrator, a machine consumes a number of licenses equal to its runtime capacity. The runtime represents the maximum number of Robots that can simultaneously run on a specific machine and it is manually customizable.

A Windows workstation can run only one process at a time, and therefore it is recommended to assign only one runtime to it.

So the recommendation is that if on Desktop OS, it is not suggested to assign more than 1 robot to a machine/license because that would mean we need to assign more than 1 runtime and having more than 1 runtime on a windows machine would not work as only one process can run at the same time.

7

But I’m wondering what would happen if I did schedule 2 process on 2 robots on a same machine at the same time. I assume one would fail, but what would be logged on orchestrator?

If you have this scenario as a HD setup on a server they would execute just fine in parallel. If however for some reason you insist on having 2 robots(2 separate users) on desktop then one would start and the other would probably(haven’t tested) fail saying something along the lines “cannot login, machine already in use”. If these two processes were scheduled on the same time on one robot, the other process would go to job queue as pending and it would start after the first one has finished.

So the recommendation is that if on Desktop OS, it is not suggested to assign more than 1 robot to a machine/license because that would mean we need to assign more than 1 runtime and having more than 1 runtime on a windows machine would not work as only one process can run at the same time.

This is the correct assumption. You will not really gain any benefits assigning more than one robot since only one can run at a time.

2 Likes
8

Right. thank you so much!