Docs/Sessions & files/Open in the Remote Desktop app
DartRelay 2.5 documentation
Sessions & files

Open in the Remote Desktop app New in 2.4

The browser is how almost everybody will use DartRelay. But some people need the computer in front of them more than they need a browser — a label printer, a smart card, a scanner. For them, the same card in the portal can hand out a connection file that opens the resource in the Remote Desktop app on their own machine, through your own RD Gateway. DartRelay does not carry that connection, but it still decides who may have the file, records every download, and counts the session as a Relay Seat.

When to use it

Note

The option is off until you switch it on, and it is then chosen per desktop and per application group. An installation that leaves it alone is unaffected.

Switch it on

  1. Open Admin Settings → Remote Desktop app and switch on Offer Open in Remote Desktop app on the portal. This is the installation-wide default.
  2. Enter the RD Gateway address, for example gateway.example.com, adding :port only if it is not 443. Leaving it empty connects straight to the host, which only works inside the network.
  3. Choose which devices the connection file may redirect. By default it offers what an RD Web Access file offers: printers, clipboard, drives, smart cards and WebAuthn, Plug and Play devices and the microphone, with cameras and USB off.
  4. Optionally choose a certificate under Sign the file with. The list shows certificates in the machine's personal store that have a private key and allow server authentication or code signing.
  5. On each desktop or application group, open the Remote Desktop app card and choose as the system setting, on or off.

Only with the person's own Windows account

The option appears only on resources that sign in to the host with the person's own credentials (Pass-Through). A connection file cannot safely carry a saved password that would then work on another computer, so resources using Fixed Credentials, and shared guest sign-ins, never offer it.

Gateways per tenant and per resource

A tenant can carry its own RD Gateway under Tenancy & Branding, and so can an individual desktop or application group. The gateway is chosen in that order: the resource's own, then the tenant's, then the installation-wide setting. The signing certificate works the same way, with a Do not sign choice on the resource.

What people see

A card that offers it shows an RDC App button with a download icon, beside Launch. Clicking it downloads the connection file; a note then tells them to open it and sign in with their Windows password. If the file is refused — because no seat is free, for instance — the reason appears in the usual launch-error banner.

Themes decide whether the button is drawn at all. Show the RDC App button sits in the Apps block, so one tenant's branding can leave it out, and Clicking a card can be set so that clicking the card downloads the file rather than opening the browser session, as RD Web Access does. Cards without the button keep its space, so the Launch buttons still line up.

Relay Seats

Downloading the file costs nothing: a file downloaded on ten computers and never opened takes no seat. The seat is taken by the session itself.

System → Relay Seats shows these sessions live, with Ends with its Windows session in place of Release. They are not in the thirty-day history, because they have no session records of their own.

Watching and ending them

System → Sessions lists browser and Remote Desktop app sessions together, with an All / Relay Sessions / RDC Sessions filter. Each Remote Desktop app row shows the user, the host, the client computer, whether it is connected or disconnected and since when, and when the person signed in. Sign out ends the Windows session and frees the seat at once, and is recorded in the audit log. Every download is audited as RdpDownload, successful or refused, with the tenant named.

Your RD Gateway

The gateway is yours, not DartRelay's. Two things decide whether it works.

An RD Gateway cannot sit behind an HTTP reverse proxy

Its sign-in needs the same connection from the client to the gateway all the way through, which an HTTP proxy does not preserve. The symptom is a gateway event saying the client may not be authenticated yet, with nothing after it, while the client reports that the remote resource cannot be reached. Pass the TLS connection straight through instead — a stream listener in front, or no proxy at all — and give DartRelay the gateway's address with its port if it is not 443.

Your gateway's own connection and resource policies must also allow those people and those hosts, under the names DartRelay holds for them in each host's Address field.

If something goes wrong

What you seeWhat to check
No RDC App button on a cardThe option is off installation-wide or on that resource; the resource signs in with Fixed Credentials; or the theme has the button switched off.
The file downloads but will not connectThe gateway address, including its port; the gateway's own policies; and whether the gateway is behind an HTTP proxy.
The app warns about an unknown publisherNo signing certificate is chosen, or the one chosen is not in the machine's personal store with a usable private key.
A seat is held after somebody has finishedTheir Windows session is disconnected rather than signed out. Set End disconnected sessions after on the host, or use Sign out on the Sessions page.
The download is refusedThe tenant's allocation or the licence is full. Relay Seats shows what is holding one.
Sessions on a host are never countedDartRelay must reach that host with its management account over the same channels it uses for publishing.

Worth knowing

Still stuck? Email support@dartinnovations.com with what you were doing, what you expected and what you saw. A screenshot helps.