Console window small resolution and/or size


The screen of RDP connection to a remote machine can have either low resolution or be undersized. This can affect the bot's interaction with the interface.


We recommend you to contact your system administrator to adjust the console screen resolution and/or console screen size, as depending on RDS versions and operating systems, the solution may be different.

If you are running a Windows Server, one option is to use a PowerShell script. The following command will set the screen resolution to a value of 1024x768.

Set-DisplayResolution -Width 1024 -Height 768 -Force

RDP/RDS-session timeout


In the RDP/RDS session settings, there is a parameter such as timeout. This parameter can be configured so that the RDP/RDS session will automatically disconnect after some time. The bot may stop working due to a disconnection.


We recommend you to contact your system administrator to configure the timeout settings.

Working with a closed or blocked RDP window

Description of an error

By default, in the closed mode, the target system goes to "screenless" mode, making it impossible to work with application elements in this case.


When the session is locked (RDP session is closed), both the workflow manually launched from Studio Pro right before the locking and the workflow launched through Orchestrator SaaS (except for the interacting with an interface) work successfully.

Method 1. Using an RDP Connection

This is the easiest method since you just need to use an RDP Connection. Let us guide you in this article.

Method 2. Additional virtual machine

For this method to work you need to open an additional (buffer) machine and configure the terminal client there to support minimized mode.

After that, you will need to perform the following steps:


Developer’s machine - M0.

Target machine - M1.

Buffer (additional) machine - M2.

Start the workflow on M1, and connect it to Orchestrator SaaS. Configure the terminal client on M2 as described in this article. After that, connect from the developer's machine (M0) to M2, and from M2 to M1. The next step is to close the connection M0 to M2, without closing the connection M2 to M1. After that, you can run bots through Orchestrator SaaS.

Method 3. Creating a bat file

The idea is to create a BAT file with the following content:

for /f "skip=1 tokens=3" %%s in ('query user %USERNAME%') do (  
%windir%\\System32\\tscon.exe %%s /dest:console  

Next, you need to run it as Administrator instead of closing the session in the terminal. After it has started, you will get a message saying that "another user is logged into the session" and the RDP window will close. You will be able to run robots, including those working with interface elements.

Pay attention that there is only one console on the server and this solution will only work for one user: if you run the same BAT file from a second user, the session of the first user will be the usual "closed" one.

Working with a minimized RDP window

Description of an error

By default, in the minimized mode the target system goes to "screenless" mode - working with application elements, in this case, is unpredictable (for example, the Notepad menu items could be there, but the buttons on the calculator could be not). So, it may affect the result of actions as well.


Configure the terminal client so that the target system does not go into screenless mode. To do this, go to the registry and create a DWORD parameter named RemoteDesktop_SuppressWhenMinimized with the value 2 (it is recommended to set both parameters regardless of the bitness of the system) at the following paths:

  • HKEY_LOCAL_MACHINE\Software\Microsoft\Terminal Server Client
    (32 bit)
  • HKEY_LOCAL_MACHINE/Software\Wow6432Node\Microsoft\Terminal Server Client