Bot running in Background

Help
21

@loginerror
Thanks for your inputs.

Regarding the ToS which you mentioned we have an enterprise orchestrator purchased to run on produtcion.Our company experts are already using it,

The above where in I mentioned me using CE orchestrator with unattended is for Trail purpose as I am in the learning stage. I am trying out all possible combinations.

My understanding is as below, correct me if wrong

Enterprise orchestrator + purchased unattended machine wide robot service installed => can perform Image automation when RDP to VM is disconnected

CE orchestrator + CE unattended robot = cannot perform Image automation when RDP to VM is disconnected.

22

Hi @RajaniG

Orchestrator CE can work fully unattended as well, but only if you install your unattended robot via the MSI installer.

To make it work:

  1. Install Robot on the target machine via the MSI installer
  2. Connect that Robot to your Orchestrator CE using your 1 available unattended license

Thatā€™s it, Orchestrator CE can now communicate and RDP into your machine even if you have all users logged out.

By default, the standard Studio CE EXE installer only allows running an unattended process on a locked user session (and even then it is a bit limited). It cannot receive an RDP request from Orchestrator because the moment you log out your user it kills the Robot service process.

2 Likes
23

Hi,

Where can we download the MSI installer for the CE? I want to try and install the robot in service mode so I could try running processes without the need to for me to RDP to my VM where the robot is installed.

24

The only way to get the MSI that matches the CE version is to go via the Insiderā€™s program for our customers:

Otherwise, you can only get the current stable Enterprise edition from our Resource center:
image

25

Thanks! Tested and it works. Didnā€™t know we could connect Enterprise robot to CE Orchestrator cool!

1 Like
26

Hello All, Iā€™m getting same issue, i tried with both simulate and default input types for click and type into, but my problem is how long screen is not locked everything is running smooth, but once screen is locked, getting below errors ā€œTimeout reached.ā€,ā€œlevelā€:ā€œErrorā€,ā€œlogTypeā€:ā€œDefaultā€, and ā€œCould not find the UI element corresponding to this selectorā€

Any suggestion on it? @loginerror

Any Suggestion is much appreciated :slight_smile:

27

I tried the solution you provided but still facing the same issue.

I tried running robot from Orchestrator as well as from studio when rdp is opened and it worked.

Robot is unable the find Ui element when RDP is disconnected

Thanks,
Jay

28

Hi @aditya.prakash and @jrp,

Did you guys found any solution for this issue?

Thanks and regards.