Skip to main content
The Windows Remote Desktop connection lets your agents control Windows machines in your own environment over RDP. Unlike Computer Use (which provides a Duvo-managed Windows sandbox), this connection targets your existing Windows servers, cloud VMs, or terminal servers, giving agents access to your internal systems, installed software, and network resources.
Beta — This feature is currently in beta and may change.

Setup

Confirm prerequisites

A Windows machine accessible via RDP (Remote Desktop Protocol).
RDP enabled on the target machine (port 3389 by default).
On the Windows Server host, set the Display Shutdown Event Tracker Group Policy to Disabled. After an unplanned restart, this dialog opens at sign-in and can delay UI automation.
A Windows user account with permissions to log in via RDP.
Network connectivity between Duvo and your Windows machine. For private networks, contact your Duvo account team to set up VPN access.

Grant the required permissions

The Windows user account used for the connection needs:
  • Remote Desktop Users group membership (or equivalent)
  • Permissions for the applications and files the agent will access
  • PowerShell execution policy that permits the automation scripts to run — prefer a least-privilege scope (for example, -Scope Process or -Scope CurrentUser, and signed scripts) rather than relaxing the policy machine-wide
  • Win+R (Run dialog) enabled in Group Policy (required for UI automation). The Duvo launcher task starts automation at sign-in without it, but Duvo still opens the Run dialog to restart automation during a Run.
Scope the connecting account to only what the agent needs. Prefer a least-privilege PowerShell execution policy (for example, -Scope Process or -Scope CurrentUser, with signed scripts) rather than relaxing the policy machine-wide.

Add the connection in Duvo

On the Connections page, open Windows Remote Desktop and fill in these fields. Secrets are encrypted using Google Cloud KMS.
string
required
A custom name for this connection to help you identify it later.
string
required
RDP host address — the IP address or hostname of the Windows machine.
string
required
Windows username used for RDP authentication.
string
required
Windows password used for RDP authentication.
number
RDP port — leave blank to use the default (3389).
string
Windows domain, if the machine is domain-joined.
string
Hostname or IP of a bastion/jump server for two-hop connections.
number
SSH port on the jump host (defaults to 22).
string
User account on the jump host (required when a jump host is set).
string
Password for the jump host (provide either password or private key).
PEM
PEM-encoded private key for the jump host.
string
Passphrase to decrypt the jump host private key.
number
How many Runs and skill recordings can use the machine at once. Leave blank or enter 1 for one at a time. Enter a higher number to allow that many at once, or 0 for no limit. The number belongs to the machine: every Connection your organization has to the same host shares it, so changing it on one Connection changes it on all of them, and only managers and above can change it. Raise this only on a machine that accepts several sign-ins at once, such as a Remote Desktop Services host. Every session from one Connection signs in as the same Windows user, so the machine must also let one user hold several sessions; if it doesn’t, add one Connection per Windows user. Use Test connection to check the machine can serve the number before Runs use it in parallel. Saving never waits for the check.

Start automation without the Run dialog

By default, Duvo starts UI Automation at sign-in by opening the Run dialog (Win+R) and typing a command. Right after the machine restarts, Windows can drop those keystrokes, and Group Policy can turn the Run dialog off. Install the Duvo launcher task once, and Windows starts UI Automation itself whenever Duvo signs in. We recommend it for any machine your agents use regularly. Keep the Run dialog turned on: Duvo still uses it to restart UI Automation during a Run. The script registers one scheduled task for each Windows account you name. At sign-in and on every Remote Desktop reconnect, the task waits for the drive Duvo maps into its session and runs the launcher Duvo puts there. Sessions without that drive, such as a person signing in as the same account, are left alone. The task runs as that account, without elevation, and its script lives in C:\Program Files\Duvo, which only administrators can change. It needs Windows Server 2012 or Windows 8, or later.

Save the script

Save the script below as install-launcher.ps1 on the Windows machine.

Run it as an administrator

In PowerShell run as an administrator, allow scripts in this window, then run the script with the Windows account from your Connection:
Write a local account as COMPUTERNAME\duvo-bot, with the machine’s name. To set up several accounts, list them: -User 'CONTOSO\duvo-bot', 'CONTOSO\duvo-bot-2'. The first line affects only this PowerShell window and ends when you close it.
The launcher task can’t run where Group Policy sets the execution policy to AllSigned. The script it installs and the launcher Duvo maps into the session aren’t signed, and Group Policy overrides the task’s own setting. Duvo’s Run dialog launch is blocked the same way, so UI Automation needs a policy that lets these scripts run.

Set up many machines

Run the same command from a Group Policy startup script or Intune.
To remove the task, run the same command with -Uninstall. If the task isn’t installed, or doesn’t start within a few seconds of sign-in, Duvo opens the Run dialog as before.

How It Works

Duvo connects to your Windows machine using the standard Remote Desktop Protocol (RDP) over port 3389 by default (configurable). The connection is secured with TLS encryption and CredSSP authentication. For machines on private networks, Duvo routes traffic through a site-to-site VPN tunnel to your infrastructure. Test connection runs its checks one after another and shows each result on its own line. You can cancel a check while it runs, and none of them stops you saving.
  • Connection signs in with the details you entered, to check the machine is reachable and accepts the credentials.
  • Sessions at once runs when the Sessions at once field isn’t 1 and the connection check passed. It checks how many sign-ins the machine allows at once: its Windows edition, whether it runs as a Remote Desktop Session Host, and its Remote Desktop connection limit. It signs in again as the Connection’s Windows user and reads these with a short, read-only PowerShell script, which takes a few seconds. If the machine can’t serve the number you set, or the check can’t run on the machine, it shows a warning that says what to check, and Retry runs that check again. It can’t see how many Remote Desktop licenses you have.
If the machine is busy when you test, Test connection shows a neutral busy row instead of a failure: “Not checked, because the computer is busy. Test again when it’s free.” The row shows how many sessions are in use, such as In use · 1 of 1, and lists who holds them:
  • Holders from your own team are named: A Run of the Agent, with a link to that Run, Your recording, A teammate’s recording, or A connection test.
  • Holders from other teams or organizations that share the machine are only counted, as Another team or N sessions from other teams.
Select Test connection again once the machine is free. RDP is a bidirectional protocol — it transmits keyboard and mouse input to the remote machine while streaming the desktop display back. From the Windows perspective, input from Duvo looks identical to input from a local user, which is why desktop applications work seamlessly. The agent can launch programs, click through menus, and type into fields exactly as a person would at that machine.

Capabilities

  • Control Windows applications — Click, type, and navigate Windows applications installed on the target machine, subject to the connected user’s permissions.
  • UI Automation — Interact with UI elements by name and type, not just pixel coordinates, making automation more reliable for thick-client applications.
  • Sign in with stored Logins — Use saved logins from Logins and Secrets to sign in to applications on the remote machine, including one-time 2FA codes, without exposing passwords to the agent.
  • Run PowerShell scripts — Execute PowerShell commands and scripts directly on the remote machine.
  • Clipboard access — Read from and write to the Windows clipboard for data transfer between applications.
  • Access network resources — Reach internal file shares, databases, and services available from the target machine.
  • Live desktop view — Watch the remote desktop in real-time as your agent works.

Key Benefits

  • Your environment, your data — Work directly on your existing Windows infrastructure, with access to installed software and internal resources based on the connected user’s permissions.
  • Thick-client automation — Automate legacy Windows applications, custom business software, and systems that only run on Windows.
  • UI-aware interaction — The UI Automation feature finds and interacts with UI elements by their properties, not just screen positions, making automations more robust.
  • Enterprise integration — Connect to Windows machines behind your firewall, on your VPN, or in any cloud or on-premises environment.
  • Full visibility — Watch the session live and review screenshots of every action for compliance and debugging.

Works Well With

Snowflake

Pull data from your warehouse or ERP, then enter it into a Windows-only application.

Gmail

Process files in desktop applications and send results by email.

Limitations

  • Elevated (administrator) processes cannot be automated if the RDP user runs at a lower privilege level.
  • By default, only one Run or skill recording can use a Windows machine at a time, even when several Connections point at the same host. Set Sessions at once to allow more. Several sessions can sign in as the same Windows user only when the machine allows it, that is when the Group Policy setting Restrict Remote Desktop Services users to a single Remote Desktop Services session is disabled. Otherwise each new sign-in takes over that user’s earlier session. Testing a Connection never signs in over a Run or recording that holds the machine, or once the machine has reached its session limit. If the machine is busy, a new Run waits instead of failing. Duvo checks about every 15 seconds for up to 15 minutes. If the machine is still busy after 15 minutes, the Run stops waiting and reports that the machine is in use. This lets a Queue that sends several Cases to one single-seat machine process them one after another. A Run that is stopped while it waits does not open a session.
  • When you record a skill and have more than one desktop to choose from, the desktop picker marks a busy Windows machine In use · X of Y, or In use · N when Sessions at once has no limit. You can still select it, because it may free up before the recording starts.
  • While a Run waits for a busy machine, its timeline shows a Waiting for the computer note with the time waited so far. The note names one holder, your own team’s first, and counts the rest, for example “Waiting for the computer. It’s in use by your recording and 1 more.” If only other teams hold the machine, it says “It’s in use by another team.” When the Run gets the machine, the note changes to Waited N for the computer, for example Waited 3 min for the computer.
  • A Run that finishes (completed, failed, interrupted, or expired) closes its Windows desktop right away and frees its session on the machine. The next Run or Case on a single-seat machine doesn’t have to wait for it. If you send a follow-up to a finished Run, Duvo opens a new desktop for it.