Multiple users at same time in Server with Unattended Robot (one license), is it possible?


#1

With one unattended robot installed in one machine, is it possible to log and run processes with different users at same time?


#2

Hi,

No, is not working (one licence/user). When you connect the robot to Orchestrator to schedule the process from there, if you remember, it will use a key generated by Orchestrator and the user/password for that machine. This credentials allow the Orchestrator to login on that machine, to do his job and at the end to log out.

Thanks,
Ninett


#3

Thanks Ninett.


#4

@JoaoRodrigues @Ninett_Panfir
It’s possible, we can run robots from multiple user accounts on a machine. The only thing to do is use the same robot key and machine name while provisioning a robot in orchestrator. And don’t forget to use different user account credentials for each robot.


#5

Hi,

@shankm He asked if is working with only one unattended robot(one licence) to run in the same time on multiple users. When you connect a robot to Orchestrator you need to provide an username and a password for that user. If you want to log in and execute on another user, you have to disconnect the previews connection made to add the new user credentials.

Thanks,
Ninett


#6

Hi @Ninett_Panfir
I know, you can connect to the same robot with different user accounts. When we try to add another robot instance with different user credentials, the first robot will disconnect. But after provisioning the second robot, try connecting it. Now both robots will start to send heartbeats. I have already done this in my firm, and I can run 4 robots with same key on same machine.


#7

Hi
I have a similar issue.
I have multiple users running different processes and I would like to put some of them on the same machine.
I have set it up in Orchestrator and if I run the jobs one at the time (waiting for job 1 to finish then starting job 2) it works.
The problem occurs when I run job 1 and while job 1 is still running I run job 2. Then I would expect job 2 to be pending but instead it just fails immediatly.
This is not very sustainable as I would like to schedule the jobs and not run them by hand.

Do you know if it is possible to start job 2 while job 1 is running so that it gets status Pending?

I am using Orchestrator version 2016.2.6302.

Thanks,
Jan


#8

Does this method require separate robot licence?


#9

No. Only one robot licence