Problem with unattended robot and browser

Help
,
21

Forgot to add that the RDP is on Windows Server 2016 Standard 10.0.1493, UIPath Assistant on the RDP is 20.10.4.

22

On the UIPath forum I’ve seen a post regarding using tscon to disconnect from an RDP session but leave the GUI active. UiRobot run in Remote desktop
I’ve see a similar post here for different use case Disconnecting From Remote Desktop While Running Automated Tests | TestComplete Documentation

What I tried was from cmd as administrator, I ran “query session” to get my Session Name. Then ran " %windir%\System32\tscon.exe RDP-Tcp# NNN /dest:console" substituting my Session Name for “RDP-Tcp#NNN” e.g. %windir%\System32\tscon.exe rdp-tcp#35 /dest:console which kicked me out of my session as expected. Then from orchestrator I kicked of my job and the bot still hangs on browser input for username and password for my web app. I know that both username and password type into’s use simulate type and the click on login uses simulate click. But this doesn’t work, has anyone had any success with tscon.exe? Or anyway to get GUI interation to work while an RDP session is disconnected?

Best regards.

Allow me correct myself, using tscon.exe does work but it took some doing to go through my process and make sure every interactive activity was using either simulate click/type or send windows message. Also, just disconnecting from the RDP session did not work for me, I had to use the tscon.exe method to disconnect. For my robot in settings, the Login to Console had to be set to No. One of the feature that helped meet track down were the process was hanging up and timing out was to set the robot settings for Logging Level to Trace. Then in Automations => Logs, or for the Job, you can click on the more icon (the 3 vertical dots on the right) and click View Logs. Having the bot’s Trace on gave me the detail I needed to figure out where in my process I needed to change the click or type to simulate or windows message.

One other thing. As far as I can tell this only works for RDP. I tried with VMWare VDI and it doesn’t work. When I used query session got get the session name, the rdp-tcp session name has no #number on it and tscon.exe doesn’t like it. I believe if seen there’s some VDI settings that can be tweaked but in my environment I need to get some admins to help me out with that.

Hope this helps anyone who had been struggling with running their bots totally unattended.

1 Like
23

Hello, any solution here? :S

24

Hello, any solution here? :S

25

Hello everybody! I have possible solution for your case:

As far as I understood, when Orchestrator open RDP session to unattended bot machine - it don’t use hardware acceleration. As you can find on some other forums, in this case Chrome could not working properly, as it using gpu by default.

You can try to find gpu settings at chrome://flags/ and also try to run chrome.exe with key --disable-gpu

Hope this will help to you!

26

Hello Valentin,

unfortunately this solution is not working for my process. Any other suggestions?

Thanks,
Eva

27

Hello Everybody,

I have the same problem too. I have solved the problem using IE but our system will not use IE anymore. That is why i have to migrate it to the chrome which is only compatible browser. We never update chrome since august 2019 by the way. Some websites or apps are working properly but many of them are not working properly.

Thanks for helping.

28

Hi All,

I faced the same problem, but just by adding “Minimize Window” and then “Maximize Window” functions helped me to avoid Chrome white screen

1 Like
29

I have the same problem . I used the “Minimize” and “Maximize” of window but it doesn’t work for me . Is there any other suggestion ?

30

Hi All,

Something you can try - go to add or remove programs - tick the box “Register Uipath Robot as Windows Service” and click change to update configuration.

image
image702×516 26.2 KB

31

Click Modify program this will take you to UIpath Change window

32

Thank you so much for that suggestion, @Ruta
Minimize then Maximize worked!!!

33

One more thing to try, when configuring your robot user, if you are setting “log in to console”, you may want to turn this off.

1 Like
34

Thanks @bcorrea . This was the setting that I was missing.

Before turning off “log in console” whenever I started my process from Orchestrator (to test its execution) my RDP session was “stolen” and I couldnt see my automation running.

After I set it to ‘off’ my RDP session is no longer being closed and I can see the automation running and now it is running successful. Thanks for the community!