RDP web client setup lets users open remote desktops and apps in a browser tab — no Remote Desktop app to install, which makes it ideal for contractors, locked-down corporate laptops, and Chromebooks. The direct answer: on a Windows Server with the Remote Desktop Services Web Access role, you install the RD Web Client management components, publish it with Install-RDWebClientPackage, point users at https://your-server/RDWeb/webclient/, and they sign in with their domain credentials. This guide walks through the server-side setup, the client experience, and the limitations to know before you promise it to your team.

What the web client is (and isn't)

The RD Web Client is Microsoft's HTML5 client for Remote Desktop Services, and it runs anywhere a modern browser runs. Users get published RemoteApp programs and full desktops through the same RD Web Access portal they'd use to download the .rdp files — except they click and the session opens in the tab. Under the hood it still speaks the RDP protocol to your gateway/broker; only the last hop, browser-to-server, is WebSocket-based.

What it isn't: a replacement for the native client for power users. There's no true multi-monitor support (it's one browser tab), file transfer relies on the browser's upload/download rather than drive redirection, and some Ctrl+Alt+Del-style key chords need the on-screen Ctrl+Alt+Del button the client provides. For occasional access it's excellent; for eight-hour daily driving, install the native app.

Browser any device RD Web Access + Web Client HTTPS /RDWeb/webclient/ Session Host desktops + apps HTTPS RDP
Fig. 1 — The browser talks HTTPS to the web tier; the web tier still speaks native RDP to your session hosts.

Prerequisites

  • A Windows Server (2016 or newer) with the Remote Desktop Services deployment already working — Web Access role installed, session hosts publishing desktops or RemoteApps, and a valid SSL certificate on the Web Access server (the web client refuses to run over plain HTTP or with an untrusted cert in most browsers).
  • Administrator rights on the Web Access server and internet access to download the web client package from Microsoft's feed.
  • Users need accounts authorized for the published resources — the same user provisioning and CAL licensing rules apply; the web client changes the client, not the licensing.

Installing and publishing: step by step

  1. On the RD Web Access server, open an elevated PowerShell and install the web client module:
    Install-Module -Name RDWebClientManagement
  2. Download the latest web client package:
    Install-RDWebClientPackage
    This pulls the signed client files from Microsoft and stages them on the server.
  3. Publish it so browsers can reach it:
    Publish-RDWebClientPackage -Type Production -Latest
    (Use -Type Test first if you want a staging URL to validate against.)
  4. Export the client configuration if you customized settings, or re-import after updates:
    Export-RDWebClientBrokerDescriptor / Import-RDWebClientBrokerDescriptor as needed.
  5. Browse to https://your-server-fqdn/RDWeb/webclient/index.html, accept no certificate warnings (fix the cert instead), and sign in. Published desktops and apps appear as clickable tiles.
  6. When Microsoft ships an update, repeat steps 2–3 to refresh the package — the module checks the feed for the newest build.

Certificate gotcha: the #1 reason a fresh web client shows a blank page is an untrusted or mismatched certificate. The FQDN in the URL must match the certificate's subject name, and the chain must validate in the browser. A free ACME/Let's Encrypt certificate works fine here.

Getting the best experience in the browser

NeedHow in the web client
Full-screen sessionSession bar → full-screen icon, or press the browser's F11 first
Ctrl+Alt+DelUse the on-screen Ctrl+Alt+Del button in the session toolbar
Copy-paste textWorks natively; grant the browser clipboard permission when prompted
Moving filesSession toolbar upload/download — or use our file transfer methods via a parallel native session
Better performanceLower the session resolution in the feed settings; close unused browser tabs
Keyboard shortcutsMany browser-reserved chords (e.g., Ctrl+T) stay with the browser — see the shortcuts guide
RD Web Client — your apps Accounting RemoteApp Desktop Full session CRM RemoteApp
Fig. 2 — What users see: published desktops and apps as tiles in a browser tab. Click, sign in, work.

When the web client isn't the answer

Be realistic about the fit. Heavy multi-screen users should use the native client with true multi-monitor. Anyone moving gigabytes daily is better served by native drive redirection per our file transfer guide. And on high-latency links the browser adds a small but real overhead versus the tuned native client — see latency reduction if sessions feel spongy.

Where the web client shines is access without installation: the contractor's locked-down laptop, the conference-room PC, the Chromebook in a branch office. For those cases, pair it with sensible session timeouts (browser tabs get abandoned more often than native clients) and monitor the hosts with the techniques in our performance monitoring guide. And if you'd rather skip the server roles entirely, a hosted RDP plan (Shared $6/month, Virtual $28/month, Dedicated $165/month, each with dedicated IP, full admin RDP, 24/7 support, 3-day money-back) gives every user a standard RDP login that works in any client — web or native.

Publishing RemoteApps vs full desktops for web users

When you set up the web client, you choose what users see as tiles: individual RemoteApp programs, full session desktops, or both. The choice shapes the whole experience:

  • RemoteApps feel like local software — the app opens in its own window with no desktop around it. They're perfect when users need one or two line-of-business applications and nothing else. Less to learn, less to break, and lighter on server resources per user.
  • Full desktops give the complete Windows environment: taskbar, File Explorer, multiple apps side by side. Choose this when users' work spans several programs or they need the freedom of a real desktop.
  • Both is legitimate: publish the two daily-driver apps as RemoteApps for speed, plus one full desktop tile as the escape hatch for everything else.

Publishing is done in Server Manager → Remote Desktop Services → Collections → Tasks → Publish RemoteApp Programs (or add the desktop via the collection properties). After publishing, users may need to refresh the web client page to see new tiles. One practical note: RemoteApps over the web client inherit the same session timeout behavior as desktops — an abandoned RemoteApp holds its session open until the timers fire, so set disconnected limits thoughtfully when apps are published widely.

Ready for your own RDP server?

Full admin access, dedicated IP, 24/7 support and a 3-day money-back guarantee on every plan. Pay by credit/debit card, bank transfer, Bitcoin or altcoins.

Shared Servers$6/mo
Dedicated Server$165/mo
Get Started

3-day money-back guarantee · Instant setup · 30+ server locations · 99% uptime SLA

RDP Web Client Setup: FAQ

An administrator installs the RD Web Client on the RD Web Access server with Install-RDWebClientPackage and publishes it. Users then open https://server/RDWeb/webclient/ and sign in with their credentials.

No, and that is the point. Any modern browser works, which makes it ideal for locked-down corporate laptops, Chromebooks, and contractors.

Almost always a certificate problem. The hostname in the URL must match the certificate's subject name and the chain must validate in the browser; the client will not run over plain HTTP.

No. The web client runs in a single browser tab with no true multi-monitor support. Use the native Remote Desktop client for multi-screen work.

Use the on-screen Ctrl+Alt+Del button in the session toolbar. The browser reserves the physical key chord, so it never reaches the session.

No. The client does not change licensing at all: users still need the same accounts and CALs as native clients when connecting to session hosts.