How to set and increase a UiPath robot's screen resolution?

[codemonkee (Tim)]

I did some testing on this a while back which can be read here

Robot not working unless logged in to machine

A bit long winded with the different test scenarios and screenshots. If you are experiencing other outcomes from the below, would love to hear about your use case and could test it out within my own environment if you’re interested!. My expectation is if you are running a job that connects to a pre-existing session (Console:false) and disconnecting the local session while the process is still running, this will lock the session, this is a security feature of Windows/RDP. I’m not familiar enough…

Short summary

• RDP in Console mode will connect to the remote host on Session 0 (typically this will be 800x600 or 1024x768)

• RDP in Interactive (Console: False) behaviour will depend on on your remote hosts Policies / Configurations. Which can be configured to only allow one session per credential, so any new session will take over an existing session if it exists, or it could be configured to allow multiple sessions for the same credential/profile. See above link for resolution test scenarios

• RDP by default will suppress the UI essentially virtually locking the screen if you minimize the RDP Window (Look up RemoteDesktop_SuppressWhenMinimized or see Robot - Executing Tasks in a Minimized RDP Window)

• Closing the RDP Window/Session will by default lock the session interfering in a similar way to minimizing the window. In order to work around this you need to either A) Leave the Window open until the Job is complete B) Send the Session to the Console by issuing the command tscon %sessionname% /dest:console. B isn’t ideal from a security perspective as you are leaving the console session unlocked and vulnerable to someone that physically gains access to the host or the console view in the VM Controller.

As noted, there wouldn’t be an issue taking over an existing session if you didn’t logout, but it’s always nice to ensure you start from a fresh session or if nothing else to free up memory. This is something I do frequently during Development, Testing, or I want to observe the job in real-time in production, it’s not recommended, but if you are connecting to the session simultaneously you should definitely perform some tests of your own to become familiar with the nuances and issues you can run into.

Reading over the topic the first thought that came to my mind is your User/Robot configured correctly in Orchestrator? Taking a Screenshot is a foreground activity as such you would need to provide the credentials. If you are only doing Background activities / process, this would not be required.

I would agree with @postwick, with the information as presented I would say resolution is a red herring especially if you’ve reduced your process to only taking a screenshot and saving the screenshot to disk.