Surface automation on Blue Prism installation in RDP with scheduler

[OngunArisev]

Hello, In our project we are using Blue Prism installed on a remote machine that we connect through RDP. Since we are interacting with an old browser application, we have not choice but to use surface automation. We have finished developing the processes and we would like to have the robots run unattended without someone having to log into the remote PC.  As far as I checked and adjusted through the group policy editor the system does not log off the user upon disconnect. When I log in after some time I see that the same programs are running. However, surface automation does not work and it complains about not finding the image of a defined region. Something changes upon disconnect and we want to make (detach of display driver maybe?) it persistent. I think there should be a workaround this issue and would be grateful if you could provide your ideas/suggestions.

[greg.virtudazo]

Make sure you Logoff or Restart the remote machine. You can then login using the Login Agent from the Control Room. Most common reason why the automation cannot see the image is the screen resolution. Now create a process that checks the resolution by calling ""Utility - Environment > Get Screen Resolution"". Run this process on the resource machine after logging in using the Login Agent. Verify that the resolution is the same as you have while you are running it on debug mode. Check the font smoothing as well ""Utility - Environment > Font Smoothing Enabled"". Hope this helps.

[OngunArisev]

Hello Greg, Thanks for the answer, today I tried the login agent but it failed by timing out. The server machine is running Windows Server 2012 R2, is it compatible with this version of Windows? I installed the MSI package, imported the release and set the environmental variable for the particular machine I will log into. I also think that the group policy editor options are correct. What might have gone wrong?

[John__Carter]

RDP is not recommended for a number of reasons, but mainly because the desktop does not persist. You can test this by creating a process that saves a screenshot and running it after you disconnect - the screenshot will be black. Once you have connected via RDP, you will need to log off and then log in via Login Agent before running your process.