Rdwebclient



On February 22nd Microsoft released version 1.0.11 of the RD Web Client (also known as the HTML5 client). Here are the features that were added to this version.

Remote Desktop Web Client is available as a feature of the RD Web Access role on RDS servers running in Windows Server 2016/2019. Prior to RD Web Client implementation, make sure that your infrastructure meets the following requirements. Finally, publish the RDWebClient package to enable it: Publish-RDWebClientPackage -Type Production -Latest. Open a HTML5 compatible browser, and navigate to After signing in: And after clicking the “Full Desktop” icon. I have just moved our RD Gateway and Webaccess server to our DMZ network. Access in and out is working fine however i notice if i connect to the web access URL through the RDWEB/webclient/ HTML5 page the connection will always be sent via the RD Gateway even if the connection is local to the RD Session Hosts. Microsoft Remote Desktop. Can’t access your account?

RD Gateway is no longer required

Previous versions of the RD Web Client required using RD Gateway in the deployment. For internet facing scenarios this makes sense. (We also advise to add RD Gateway to every deployment to add an additional layer of security.) But there are also times when RD Gateway is not needed, for example, if users are local to the deployment. This latest version of the HTML5 Client does not require RD Gateway. Below are a couple of screenshots that show this in action.

Note: This feature is only available for deployments based on a Windows Server 2019 RD Connection Broker and a Windows Server 2019 RD Session Host.

Post box pole

Extra Configuration

If you are working on an all-in-one deployment (all roles are located on the same server) then you do not have to do anything to make this work. However, if you have your roles separated, or you have an highly available deployment you will need to

  1. Bind your SSL certificate to port 3392 on the RD Connection Broker(s) and the RD Session Hosts
  2. Change the listener to listen on port 3392 on Connection Broker(s) and the RD Session Hosts

Rd Web Client Download

Rdwebclient

This article outlines the steps in the section called: “Connecting to RD Broker without RD Gateway in Windows Server 2019”. Some other things to note:

  1. If you are load balancing RD Connection Broker servers to make that role highly available, you need to open port 3392 on the load balancer(s).
  2. Local users will need access to RD Connection Broker and RD Session Hosts over port 3392 so adjust your firewalls accordingly if needed.

Our Testing

Rdweb client downloadRdwebclientRd web client html5

In our testing we got inconsistent results. It worked in one environment and not in another. We are working with the Microsoft RDS Team now and will post as soon as we get resolution!

Feeds now sorted alphabetically

The user feed is now sorted alphabetically (RemoteApps first and full desktops second). This provides a more intuitive user experience.

No need for internet access

This was added in a previous release (version 1.0.7) but its worth a mention here. In previous versions, the installer could only be run directly from the RD Web Access server and it needed internet access during the installation. Now the installer files can be downloaded and copied to various RD Web Access servers; no internet connection required for setup. The RD Web Client can now also be used internally by clients that do not have direct internet access.

Rd Web Client App

More Information

RdwebclientFor more information on how to set up RD Web Client follow this link:

Https Rdweb Wvd Microsoft Webclient Index Html


Rd Client App Windows 10

https://docs.microsoft.com/en-us/windows-server/remote/remote-desktop-services/clients/remote-desktop-web-client-adminFor more information on release information per RD Web Client Version, follow this link:
https://docs.microsoft.com/en-us/windows-server/remote/remote-desktop-services/clients/web-client-whatsnew