--- title: "Remote Desktop Web Client (RD Web): Install and Publish on Windows Server" canonical: "https://tsplus.net/html5-remote-desktop-web-client/" pubDate: "2024-04-30T16:00:25.000Z" description: "Learn how to install and publish the Remote Desktop Web Client on Windows Server 2025, 2022, 2019 and 2016, with PowerShell steps and security tips." --- The Microsoft Remote Desktop Web Client enables browser-based access to Windows desktops and applications through Remote Desktop Services (RDS). This guide explains how to install, configure and publish the client on Windows Server 2025, 2022, 2019 and 2016, covering system requirements, PowerShell commands, security considerations, performance optimization and troubleshooting for reliable remote access. Microsoft's Remote Desktop Web Client allows users to access Windows desktops and applications directly through a browser, without installing a traditional RDP client. Available for Windows Server Remote Desktop Services (RDS) deployments, it simplifies access to published resources across different desktop operating systems. This article explains how to install and publish the Remote Desktop Web Client on Windows Server 2025, 2022, 2019 and 2016, covering prerequisites, configuration, performance optimization and troubleshooting. ## What Is the Remote Desktop Web Client? The Remote Desktop Web Client is Microsoft's browser-based interface for accessing resources published through Remote Desktop Services. Instead of launching a locally installed RDP client, users connect to a web portal and open their assigned applications or desktops. Built on web technologies, including HTML5, the client supports remote sessions through compatible browsers such as Microsoft Edge, Google Chrome, Mozilla Firefox and Safari. ### How Does the Remote Desktop Web Client Work? The web client operates within an existing Remote Desktop Services deployment. Several server roles work together to provide access: * **RD Web Access:** Provides the web interface through which users discover and launch published resources. * **RD Gateway:** Enables secure external connectivity to internal Remote Desktop Services infrastructure. * **RD Connection Broker:** Manages session routing, load distribution and reconnection to existing sessions. * **RD Session Host:** Runs the Windows desktops and applications accessed by users. The Remote Desktop Web Client does not replace these roles. It adds a browser-based interface to an RDS deployment that must already be operational. ### RD Web Access vs. Remote Desktop Web Client Although closely related, RD Web Access and the Remote Desktop Web Client serve different purposes. RD Web Access is a Windows Server role that presents published applications and desktops. The Remote Desktop Web Client is an additional browser-based client installed and published through that infrastructure. Installing RD Web Access alone does not automatically enable interactive remote sessions inside the browser. Administrators must separately deploy and publish the web client package. ## What Are The Remote Desktop Web Client Requirements on Windows Server? Before installing the web client, verify that the server roles, certificates, licensing and network configuration meet Microsoft's requirements. ### Supported Windows Server Versions Microsoft's current Remote Desktop Web Client documentation lists the following versions among the applicable operating systems: Windows Server 2025 is therefore included in the current [Microsoft documentation](https://learn.microsoft.com/en-us/windows-server/remote/remote-desktop-services/remote-desktop-web-client-admin). However, Microsoft's detailed setup prerequisites still specifically name Windows Server 2016 and 2019 for the RD Gateway, RD Connection Broker and RD Web Access roles. Administrators deploying the web client in a Windows Server 2022 or 2025 environment should verify their server-role configuration against the latest documentation before proceeding. ### Required RDS Roles and Licensing A working RDS deployment must be configured before the web client can be installed. This includes RD Web Access, RD Connection Broker and the relevant session-host infrastructure, together with RD Gateway for the standard documented deployment. Microsoft also requires per-user RDS Client Access Licenses (CALs) for the web client. Per-device licensing is not supported for this scenario. Ensure that the RD Licensing server is configured correctly and that users have the necessary rights to access their assigned resources. ### Certificates and Network Configuration Trusted certificates are essential for secure browser access. Configure appropriate [certificates for Remote Desktop connections](https://tsplus.net/ssl-certificates-for-remote-desktop-connections/) on RD Gateway and RD Web Access, and ensure their hostnames match the addresses used by clients. The RD Connection Broker certificate is also required during web client installation. For network connectivity, HTTPS traffic typically uses TCP port 443. Internal communication between the RDS roles must also be allowed according to the deployment architecture. Avoid exposing RDP port 3389 directly to the public internet. External users should connect through the configured gateway or another supported secure access architecture. ## How to Install the Remote Desktop Web Client on Windows Server Once the RDS infrastructure is ready, the Remote Desktop Web Client can be installed and published using PowerShell. The following procedure follows Microsoft's documented installation sequence. ### Step 1: Export the RD Connection Broker Certificate On the RD Connection Broker server, locate the certificate used for Remote Desktop connections. Export its public certificate as a `.cer` file and copy it to the RD Web Access server. The web client uses this certificate information when establishing connections to the RD Connection Broker. ### Step 2: Prepare PowerShell Sign in to the RD Web Access server and open PowerShell with administrator privileges. On Windows Server 2016, Microsoft instructs administrators to update the PowerShellGet module: ``` Install-Module -Name PowerShellGet -Force ``` Restart the PowerShell session after updating the module. For newer Windows Server versions, verify the installed PowerShell components before making changes. ### Step 3: Install the RD Web Client Management Module Install the management module from the PowerShell Gallery: ``` Install-Module -Name RDWebClientManagement ``` This module provides the commands needed to download, publish and maintain the Remote Desktop Web Client. If installation fails, check access to the PowerShell Gallery and verify that the PowerShell session supports TLS 1.2 or later. ### Step 4: Download the Web Client Package Run the following command: ``` Install-RDWebClientPackage ``` This downloads the latest available Remote Desktop Web Client package. Using the latest supported version is important for security and browser compatibility. Microsoft continues to release updates addressing vulnerabilities, performance issues and client functionality. ### Step 5: Import the RD Connection Broker Certificate Import the certificate exported earlier: ``` Import-RDWebClientBrokerCert "C:\Certificates\RDBroker.cer" ``` Replace the example path with the actual certificate location. The imported certificate must correspond to the RD Connection Broker used by the deployment. ### Step 6: Publish the Remote Desktop Web Client Publish the installed package for production use: ``` Publish-RDWebClientPackage -Type Production -Latest ``` The Remote Desktop Web Client is now available through RD Web Access. Administrators can also publish a test version before making an update available to all users: ``` Publish-RDWebClientPackage -Type Test -Latest ``` Testing is particularly useful when introducing a new browser client version into an established multi-user RDS environment. ## How Can You Access and Publish Remote Desktops Through RD Web? Publishing the web client makes the browser interface available. Administrators must also ensure that the appropriate applications and desktops are published through RDS. ### Open the Remote Desktop Web Client URL The standard web client URL follows this format: ``` https://server.example.com/RDWeb/webclient/index.html ``` Replace `server.example.com` with the fully qualified domain name of the RD Web Access server. The hostname must match the certificate configured for the service. Users can then access the portal with a compatible browser and their organizational credentials. ### Publish RemoteApp Programs and Desktops Applications and desktops are published through Remote Desktop Services, not directly through the web client management module. In Server Manager, navigate to **Remote Desktop Services**, select the appropriate session collection and configure its published RemoteApp programs. Ensure that users have permission to access the relevant collection and resources. Once configured, the applications or desktops appear in the web client interface, where authorized users can launch them. ### Launch a Remote Session Users open the web client URL, authenticate and select an available resource. The remote desktop or application runs inside the browser window, with interaction handled through the RDS infrastructure. Depending on configuration, the browser may request permission to use certain local resources, such as the clipboard. ## How Can You Optimize Your Remote Desktop Web Client Performance? Reliable browser-based remote access depends on more than installing the web client. Network quality, server capacity and session configuration all influence responsiveness. ### Manage Bandwidth and Network Latency Remote desktop traffic varies depending on the applications used, screen resolution and level of graphical activity. Office applications and simple business software generally place different demands on the network than graphics-intensive applications or frequently changing screen content. Before deployment, estimate the number of concurrent users and evaluate available bandwidth during peak periods. Latency is equally important. Even when bandwidth is sufficient, high round-trip times can make typing, scrolling and application interactions feel sluggish. Administrators should monitor network latency, packet loss and bandwidth utilization, particularly when users connect from remote locations. ### Monitor Server Resources and Session Performance RD Session Host servers must have enough CPU, memory and disk capacity to support concurrent users. Monitor resource utilization alongside active session counts to identify capacity limits before users experience performance degradation. Useful metrics include CPU and memory usage, disk activity, network throughput, active and disconnected sessions, and session connection failures. Windows Performance Monitor, Event Viewer and appropriate infrastructure monitoring tools can help identify whether slow sessions are caused by server saturation, network conditions or an individual application. Monitoring should also account for peak workloads rather than relying exclusively on average utilization. ### Keep Browsers and Web Client Packages Updated Browser versions and client-side graphics capabilities can affect remote session performance. [Microsoft's current web client release notes](https://learn.microsoft.com/en-us/windows-server/remote/remote-desktop-services/web-client-whats-new) introduce requirements related to browser age, AVC codec support and WebGL availability. Test supported browsers using representative workloads and keep the web client package updated. Where browser-specific problems appear, compare behavior across supported browsers and, where appropriate, with a native RDP client to help isolate the cause. ## What Is The Process of Managing RD Web Client Deployments Across Multiple Servers? Larger organizations often distribute remote desktop workloads across multiple RD Session Host servers. In these environments, session routing, load distribution and reconnection become essential to maintaining reliable access. ### RD Connection Broker and Load Balancing The RD Connection Broker coordinates connections to published resources and directs users to suitable RD Session Host servers. Within a session collection, it supports load distribution across available hosts, helping administrators spread workloads rather than concentrating every session on one server. This becomes particularly important when several users access the same published applications or desktop environment. Administrators should configure session collections and load-balancing settings according to server capacity and expected workloads. The Remote Desktop Web Client does not introduce a separate load-balancing mechanism. It relies on the existing RDS infrastructure to route connections. ### Session Persistence and Reconnection Users may temporarily lose connectivity because of network interruptions, browser closure or changes in network conditions. RD Connection Broker helps reconnect users to their existing sessions when those sessions remain available. Session persistence depends on the RDS deployment, collection configuration and applicable session policies. Administrators should review disconnected-session limits and automatic reconnection behavior to balance usability, server capacity and security. Testing reconnection is especially important in multi-server environments, where users must be routed back to their original sessions rather than accidentally creating unnecessary additional sessions. ### High Availability Considerations For business-critical deployments, removing single points of failure may require additional RDS infrastructure. This can include highly available RD Connection Broker configurations, redundant gateway and web access services, and multiple RD Session Host servers. RD Web Access and RD Gateway availability must be planned separately from session-host load distribution. Adding more session hosts alone does not make the entire remote access environment highly available. Administrators should also verify certificate consistency, DNS configuration and load-balancer behavior across redundant components. ## What Are The Remote Desktop Web Client Features and Limitations? Browser-based access offers flexibility, but it does not reproduce every capability of a locally installed RDP client. ### Printing and File Transfers Microsoft's web client supports remote printing through a virtual printer that generates downloadable PDF files. File transfers are available through designated virtual locations in the remote session, with a documented download size limit of 255 MB. These workflows differ from direct local drive and printer redirection available in traditional RDP clients. Organizations with specialized printing requirements or frequent large file transfers should test these capabilities before deployment. ### Browser and Mobile Compatibility The web client supports compatible desktop browsers on Windows, macOS, Linux and ChromeOS. However, Microsoft's documentation does not currently list mobile devices as supported for this web client. Organizations requiring access from smartphones or tablets should evaluate dedicated clients or alternative browser-based delivery solutions. ### Security and Access Control The web client benefits from the security controls implemented across the underlying RDS deployment. Administrators should follow [RDP security best practices](https://tsplus.net/advanced-security/blog/how-to-secure-rdp/), including using trusted certificates, restricting unnecessary network exposure and applying least-privilege access policies to published resources Additional security measures, including multifactor authentication through supported access architectures, can help protect externally accessible services. Keep Windows Server, RDS components and the web client updated, and monitor authentication failures and unusual session activity. ## How to Update and Troubleshoot the Remote Desktop Web Client? Regular maintenance reduces connection problems caused by outdated packages, expired certificates and changes to the RDS infrastructure. ### Update the Remote Desktop Web Client To download the latest package, run: ``` Install-RDWebClientPackage ``` Optionally publish it to the test environment first: ``` Publish-RDWebClientPackage -Type Test -Latest ``` After validating the update, publish it to production: ``` Publish-RDWebClientPackage -Type Production -Latest ``` Microsoft's release notes document security updates, compatibility improvements and fixes to known problems. ### Update the RD Connection Broker Certificate When the broker certificate is renewed or replaced, export the updated certificate and import it into the web client configuration: ``` Import-RDWebClientBrokerCert "C:\Certificates\RDBroker-New.cer" ``` Republish the production client: ``` Publish-RDWebClientPackage -Type Production -Latest ``` Failing to update the broker certificate can trigger an unexpected server authentication certificate error. ### Resolve Common Connection Problems **Web client page does not load:** Check RD Web Access availability, DNS resolution, HTTPS connectivity, IIS configuration and whether the package has been published. If connectivity remains the issue, review how to [establish a secure connection to a server](https://tsplus.net/advanced-security/blog/how-to-establish-a-secure-connection-to-a-server/) before changing the web client configuration **Users can sign in but see no applications:** Verify session collection configuration, published resources, user permissions and RD Connection Broker connectivity. **Certificate errors appear:** Check certificate validity, hostname matching and whether the correct broker certificate has been imported. **Remote sessions disconnect frequently:** Investigate network stability, RD Gateway connectivity, session timeout policies and RD Session Host resource utilization. **Sessions are slow or unresponsive:** Compare browser performance, server capacity and network latency. If the issue also occurs through a native RDP client, the cause is more likely to involve the underlying RDS environment. A structured troubleshooting approach helps distinguish browser-client problems from failures elsewhere in the Remote Desktop Services infrastructure. ## TSplus Remote Access: Browser Access Through a Web Application Portal Organizations looking for a simpler approach to browser-based desktop and application delivery can consider [TSplus Remote Access](https://tsplus.net/remote-access/). Its HTML5 web client allows authorized users to access Windows applications and remote desktops directly through a compatible browser, without installing a traditional RDP client. The TSplus web application portal provides a centralized interface for launching published applications and desktops. Unlike Microsoft's Remote Desktop Web Client, which relies on an existing RDS deployment with specific server roles, [our solution](https://docs.tsplus.net/tsplus/quickstart-guide/) provides its own application publishing and browser-access architecture. This makes it an alternative for businesses seeking to deliver Windows resources through a web portal while simplifying deployment and administration. ## Conclusion Microsoft's Remote Desktop Web Client enables browser-based access to Windows desktops and applications through Remote Desktop Services. With Windows Server 2025 included in Microsoft's current documentation, administrators should verify deployment compatibility, licensing, certificates and server roles before installation. For reliable operation, maintaining the web client is only part of the task. Network performance, session management, load balancing and infrastructure monitoring also determine the quality of the remote access experience.