A wonderful new feature of Server 2022.
This page is a watered-down-quick-and-dirty of this document
Before getting started, keep the following things in mind:
Your users will see better performance connecting to Windows Server 2016 (or later) and Windows 10 (version 1611 or later).
Important
If you used the web client during the preview period and installed a version prior to 1.0.0, you must first uninstall the old client before moving to the new version. If you receive an error that says "The web client was installed using an older version of RDWebClientManagement and must first be removed before deploying the new version," follow these steps:
To install the web client for the first time, follow these steps:
On the RD Connection Broker server, obtain the certificate used for Remote Desktop connections and export it as a .cer file. Copy the .cer file from the RD Connection Broker to the server running the RD Web role.
On the RD Web Access server, open an elevated PowerShell prompt.
On Windows Server 2016, update the PowerShellGet module since the inbox version doesn't support installing the web client management module. To update PowerShellGet, run the following cmdlet:
Install-Module -Name PowerShellGet -Force
Important
You'll need to restart PowerShell before the update can take effect, otherwise the module may not work.
Publish-RDWebClientPackage -Type Production -Latest
Make sure you can access the web client at the web client URL with
your server name, formatted as https://server_FQDN/RDWeb/webclient/index.html
.
It's important to use the server name that matches the RD Web Access
public certificate in the URL (typically the server FQDN).
Note
When running the Publish-RDWebClientPackage cmdlet, you may see a warning that says per-device CALs are not supported, even if your deployment is configured for per-user CALs. If your deployment uses per-user CALs, you can ignore this warning. We display it to make sure you're aware of the configuration limitation.
When you're ready for users to access the web client, just send them the web client URL you created.
Note
To see a list of all supported cmdlets for the RDWebClientManagement module, run the following cmdlet in PowerShell:
Get-Command
-Module RDWebClientManagement
Install the Remote Desktop web client management PowerShell module from the PowerShell gallery with this cmdlet:
Install-Module -Name RDWebClientManagement
After that, run the following cmdlet to download the latest version of the Remote Desktop web client:
Install-RDWebClientPackage
Next, run this cmdlet with the bracketed value replaced with the path of the .cer file that you copied from the RD Broker:
Import-RDWebClientBrokerCert <.cer file path>
Finally, run this cmdlet to publish the Remote Desktop web client:
When a new version of the Remote Desktop web client is available, follow these steps to update the deployment with the new client:
Open an elevated PowerShell prompt on the RD Web Access server and run the following cmdlet to download the latest available version of the web client:
Install-RDWebClientPackage
Publish-RDWebClientPackage -Type Production -Latest
This will replace the client for all users when they relaunch the web page.
To remove all traces of the web client, follow these steps:
On the RD Web Access server, open an elevated PowerShell prompt.
Unpublish the Test and Production clients, uninstall all local packages and remove the web client settings:
Uninstall-Module
-Name RDWebClientManagement
Optionally, you can publish the client for testing before official release by running this cmdlet:
Publish-RDWebClientPackage -Type Test -Latest
The client should appear on the test URL that corresponds to your web client URL (for example, https://server_FQDN/RDWeb/webclient-test/index.html).
Publish the client for users by running the following cmdlet:
Uninstall-RDWebClient
Uninstall the Remote Desktop web client management PowerShell module: