There are also a few things to consider when launching and running robots in console mode:

  1. Most often, the command to put the machine into console mode must be executed as an administrator (in rare cases, the required account may already have the necessary level of rights).

  2. The remote machine policies must disable automatic screen locking and hibernation during inactivity. This requirement must be fulfilled if the robot's inactivity time (for example, between its scheduled launches) exceeds the set inactivity limit, after which the account is locked or hibernated. The point is that if the account is locked, the robot will be able to launch, but it will correctly perform only those actions that are performed in the background. The robot will not be able to unlock the account on its own.

  3. It is necessary that in console mode the screen resolution remains the same as it was in the active RDP session when the analyst created the robot source (it does not affect only the screenshot creation action). This rule should always be observed. If the resolution still changes when switching to console mode, you can try modifying the command a bit:

tscon.exe <ID> /dest:console & <Path to QRes.exe> /x:<Value by X> /y:<Value by Y>, where the first command is a jump to the console session, the second command is setting the permission using a specialised utility. The source code of the utility is here: https://sourceforge.net/projects/qres/ 

Note that in some virtual environments, after disconnecting the RDP connection, the permission with which the user was working may not be retained. In console mode, the last time administrators logged on to the virtual environment management console, the permission may be automatically set.

This problem, for example, exists in VMware virtual environments. The proposed solution is described in the link: VM Console Display Resolution Change - vGemba.net: https://www.vgemba.net/vmware/powercli/VMConsole-Resolution-Change/

In order to solve the problem:

а) log on to the required machine via the management console and change the required resolution on the machine:

b) specify the following parameters in the virtual machine settings (via the management console):

guestInfo.svga.wddm.modeset=”FALSE”

guestInfo.svga.wddm.modesetCCD=”FALSE”

guestInfo.svga.wddm.modesetLegacySingle=”FALSE”

guestInfo.svga.wddm.modesetLegacyMulti=”FALSE”

In this mode, manipulating the VMware console size does not affect the resolution that will be on the machine in console mode when the robot is operating.

Correct operation when rdp connection is minimised

  • On the client, make changes to the registry (RemoteDesktop.reg).

  • This parameter prevents the rdp client from blocking the remote computer if the user minimises the rdp client window.

  • After making changes to the registry, you can minimise the window with the remote machine (where the robot is) and the robot will perform correctly.

  • Нет меток