Skip to main content
Version: 0.26.0

RDP Robot

Description Automates a remote machine over Remote Desktop Protocol. This is the recommended type for production: the robot works in its own remote session, so your own desktop stays free.

RDP robot settings in the Open Environment dialog

The screenshot shows the top of the form. Gateway, Connection File and the options described further down sit below the visible area — scroll the dialog to reach them.

Connection settings​

Fields marked with * are required.

FieldDescription
Profile NameName under which this configuration is saved for reuse.
Address *Address of the remote machine.
Username *Login username on the remote machine.
Password *Login password. Store it in the Vault and reference it instead of typing it in plain text.
Domain *Windows domain of the account.
PortRDP service port. Leave Default unless your server listens elsewhere.
Connection FileConnect using an existing .rdp file. The address and port are taken from the file; Username, Password and Domain still come from the profile, so keep them filled in.

Shared folder​

Tick Shared Folder to redirect a local folder into the remote session — that is how files move between the two machines. The folder also shows up as Shared folder (RDP) in the Files panel.

FieldDescription
PathLocal folder to share with the remote session.
NameName the share appears under on the remote machine.

Gateway​

Fill this section in only when the remote machine is reachable through an RD Gateway.

FieldDescription
AddressGateway host.
Username / Password / DomainCredentials for the gateway.
PortGateway port; Default in most deployments.

Other options​

FieldDescription
Enable unicode keyboardTypes text as Unicode characters, independent of the remote machine's keyboard layout. On by default. Turn it off only if the server does not support Unicode input.
Enable autoreconnectReconnects automatically if the RDP session drops mid-run.
Extra optionsAdditional FreeRDP command-line options for edge cases, separated by spaces. Wrap an option that contains spaces in quotes, for example /cert:ignore "/drive:Share,C:\My Files". Backslashes are kept as typed, so Windows paths need no escaping.
Upgrading from 0.25.x
  • Up to 0.25.0 the dialog did not show Gateway, Connection File, Enable unicode keyboard, Enable autoreconnect or Extra options at all. They are all available now.
  • Profiles saved by an older Editor stored Enable unicode keyboard switched off, which with the updated remote-desktop engine drops typed characters. Such profiles are switched on automatically when they are loaded — you do not need to edit them.
  • Type Text with Clear before typing used to click the field a second time right before typing. The remote application took the two clicks as a double-click, which in some applications (for example Helios) lost the first typed characters. The text is now typed straight into the field that the clearing step already focused.
tip

Transfer File To Remote Machine and Get File From Remote Machine (Files → RDP) move files in and out of the session without you touching the shared folder manually.

Connection resilience​

A dropped VPN or remote-desktop link no longer hangs the run. Since 0.24.0 the Editor:

  1. detects the dropped connection within seconds,
  2. dims the live view with a Reconnecting… overlay,
  3. reconnects automatically once the network is back, retrying for up to about 5 minutes,
  4. and if it cannot recover, shows Disconnected and fails the run with a clear error.

Enable autoreconnect in the profile covers the RDP session's own reconnection; this watchdog sits above it and also catches a network that went away entirely.

While the link is down the run controls — Run, Run all, Run to end, Teach robot and Save and Execute — are disabled, since there is nothing to drive. A successful Connect re-enables them immediately; so does Disconnect.

Upgrading from 0.24.x

Up to 0.24.0 one dropped connection could leave those controls greyed out for the rest of the session — the Editor went on treating the robot as unreachable even after it had reconnected, and the only way back was to restart the Editor. Fixed in 0.25.0.

tip

For unattended runs this is the difference between "the job failed at 03:10 because the VPN blipped" and "the job was still "running" when we came in at 8". A scenario that ends with a Send As Email marked Run on Failure will now actually tell you.