Install RD Web Client on Windows Server 2022 – Complete Setup Guide
To access Remote Desktop only via the browser, install the Web Client package --- Step 1: Export the Self-Signed Certificate * Open **Run** → type `certlm.msc` * Navigate to **Personal** → **Certificates** * Select the certificate created for the **RD Connection Broker** * Export the certificate (e.g., to `C:\temp\abcde.cer`) --- Step 2: Install and Publish Web Client Package Open Windows PowerShell 5.1 and run: powershell Install-Module PowerShellGet -Force Install-Module RDWebClientManagement Import-Module RDWebClientManagement # Clean up any stale IIS locks Reset-IISServerManager -Confirm:$false Remove-Module IISAdministration -ErrorAction SilentlyContinue Import-Module RDWebClientManagement # Install the Web Client Install-RDWebClientPackage # Import the exported certificate Import-RDWebClientBrokerCert "C:\temp\abcde.cer" # Publish the Web Client for production Publish-RDWebClientPackage -Type Production -Latest --- Step 3: Access the Web Client Visit: https://<your-serverFQDN>/RDWeb/webclient/index.html If the page does not appear: Restart the **Default Web Site** in **IIS Manager**. Ensure the **webclient** folder is present under the IIS site directory. Check if the correct certificate is applied under **Bindings** in IIS. If want Beginning from Remote access deployment- use this link - Remote Access via HTTPS RDP Web Client on Windows Server 2022 - Installation Issue Solved . | Microsoft Community Hub
Updates KB4534297/KB4534309 Break RDS through Web Application Proxy on Server 2012 R2
We have Remote Desktop https://docs.microsoft.com/en-us/azure/active-directory/manage-apps/application-proxy-integrate-with-remote-desktop-services through Web Application Proxy, both running on Server 2012 R2. The RDS application in WAP is configured for pass-through authentication so users can connect from both Windows and non-Windows ("rich apps" on Android/iOS/Mac) devices. This has been working for the past few years without issue. After installing recent update KB4534309 (or the rollup that contains it, KB4534297), the non-Windows clients are unable to connect. They show error 0x3000008 during the "initiating remote connection" phase: We couldn't connect to the gateway because of an error. If this keeps happening, ask your admin or tech support for help. Has anyone experienced this or figured out a way to fix it?
