If you are using the RemoteApp RDWeb Access website feature (RDweb) in Windows Server 2008 R2 and have client/user PCs that have upgraded to Windows 10, read below. This does not apply if you are using full RDP desktop sessions to login and see a desktop which is what many/most people do – i.e. using RDP client to connect to a desktop session.
If users are accessing applications using the RD Web access website (i.e. https://IP or Hostname/rdweb ) to access applications instead of logging into the server via the remote desktop connection client, you will notice that the website doesn’t work from Windows 10 PCs using the new Microsoft Edge browser. RemoteApp RDWEB hosted on a Windows 2008 R2 Server requires the client browser to have ActiveX enabled which basically limits usage to Internet Explorer (doesn’t work on Chrome, Firefox nor for MAC users). (Note: Windows Server 2012R2 RemoteApp RDWEB no longer requires ActiveX).
The end nodes (RD Virtualization Host, RD Session Host, and RD Web Access) are configured with the full list of all the fully qualified domain names (FQDNs) of the RD Connection Broker servers, and they can connect to any of the RD Connection Broker servers in the setup. This Video is show on Configure & Installation Remote Desktop Web Access in Server 2019.Simple way to Install & Configure Remote Desktop Web Access.
Solution
The good news in this situation is Windows 10 still includes Internet Explorer and if you open the website using IE, you should be able to access it – see steps below. In Windows 10, open IE separately and not within Edge (i.e. in Edge, you can click tools, and then say “open in IE” but don’t do it this way). Follow the steps below to open IE, add rdweb URL to trusted sites in IE, then close IE and reopen IE, then it should work.
- CLICK START BUTTON and start typing “Internet Explorer” which should pop-up in search results and select – see screenshot below. Don’t click the browser shortcut in taskbar because that will just open Edge.
2. After IE opens, go to the url you use for RDweb. Click Allow on popup to allow MS RDS web access – see screenshot.
3. Do not login yet – first we need to add to trusted sites in Internet Explorer (only need to do first time), then will need to exit all IE windows and start again.
4. Under the tools icon, click internet options like this, which will open the Option windows, then go to Security Tab, Trusted Sites (the green checkbox), then click on the “Sites” button and then add the url which may be pre-populated – see screenshots.
5. Next, close all Internet Explorer windows and start over except this time login to the RDS site.
Everyone will be familiar with the Remote Desktop client called MSTSC. Since a few years, Microsoft also has a Remote Desktop client for other platforms like iOS, Mac OS X and Android, available for download from the App Store, the Mac App Store, and the Google Play Store.
As a next step, Microsoft now also has a web client based on HTML5 (currently into preview), called the RD Web Client. Best bittorrent client for windows 7. This blog post runs through the setup, based on the early preview that I tested. The Remote Desktop Web Client is installed as an extension of the RD Web Access role.
Requirements
The requirements for the Web Client are as follows;
· RD deployment with Gateway, Broker and WebAccess roles all running Server 2016 Operating System. The endpoints (RDSH or Windows Client SKUs) can be running any Windows Operating System starting from Windows 7 SP1 / Windows Server 2008 R2. The client performance will however be better when connecting to Windows Server 2016 or Windows 10 Anniversary Edition or later.
· The RD deployment should NOT be configured to use per-device license.
· The Server 2016 machine hosting RD Gateway role must have this update installed – https://support.microsoft.com/en-us/help/4025334/windows-10-update-kb4025334
· The Gateway and WebAccess roles should be using public trusted certificates
· The client should work on most HTML5 capable browsers and has official support for Edge, IE11, Google Chrome, Firefox and Safari. Mobile devices are not supported.
Installation
By the time the client releases, new PowerShell CmdLets will be available to deploy, manage and configure the client. Based on the current beta, here’s an example of what these cmdlets might look.
We open an Administrative PowerShell console and run the following commands:
Import-Module ($Env:ProgramFiles + “rd-html5-manageRDWebClientManagement”)
Install-RDWebClientPackage
Next, we copy the certificate used by the RD Web Access role. Optionally export it first, and make sure to include the private key. Then run the following commands in the PowerShell Admin console.
Import-RDWebClientBrokerCert <cer file>
Publish-RDWebClientPackage -Production -Latest
Easy as that! HTML5 support is now added to the RD Web Access role!
Note, in the beta release the Import-RDWebClientBrokerCert currently does not accept password protected pfx files. Make sure you export the certificate using the security principal option as shown below.
Testing
To test the HTML5 web client, open a browser (currently Edge, IE 11, Google Chrome browsers are all officially supported) and browse to https://<publicdomain>/RDWeb/Pages/webclient. For example, in my case I tested an Azure IaaS setup with 2 RD Web Access servers behind an Azure Load balancer. I created a public DNS record for rds.rdsgurus.com and pointed that to the public IP of the Azure Load Balancer. I then browsed to https://rds.rdsgurus.com/RDWeb/Pages/webclient.
At first you will see the regular RD Web Access login screen and you login with a test account as you normally would too.
After logging in you will see the following screen, this is the HTML5 web client containing the 4 sample RemoteApps I published in the RDS deployment.
If you click on one of the RemoteApps an RDP session will be launched. Note that currently you will get an additional prompt for the first RemoteApp as there is no full Single Sign On yet.
Since this was the first RemoteApp, the RDS session will now process the logon.
And shortly after, the RemoteApp is now available within the browser.
From this point, you can navigate to the bar on the left-hand side and switch between applications and launch new application. All RemoteApps are available within the same screen to allow to work with multiple application easily.
The RD Web Client also allows you to copy-paste between your local machine. It is however currently limited to text only.
There is also support for Remote Audio.
For further management, the RDWebClientManagement PowerShell module beta version also comes with a few other Cmdlets to retrieve the package information, certificate and to uninstall the package. Note that these Cmdlets might slightly change once the PowerShell module reaches general availability.
If you want all users to be redirected to the Web Client instead of the traditional RD Web Access page, you can run the following command on the RD Web Access Server
Set-WebConfiguration system.webServer/httpRedirect “IIS:sitesDefault Web Site” -Value @{enabled=”true”;destination=”https://<domainname>/rdweb/pages/webclient”;exactDestination=”false”;httpResponseStatus=”Permanent”;childOnly=”true”};
Or change the same value using IIS Manager:
The RD Web Client also comes with printing support. A virtual printer called “Microsoft Print to PDF” is available in the user’s session. Don’t be confused by the postfix “redirected 3”. This is not a redirected printer, the name will most likely change so that it is clear that it’s a virtual printer. By virtual printer we mean that the printing to this printer will result in a .pdf file that is transported and opened on the local client. From that local client it can then be printed to any locally available printer.
I’m able to print to this redirected printer
Rd Web Access Sign In
Which results in the pdf being locally available
And in this case, I opened it in my local browser to then print to a locally available printer.
How To Access Rd Web Access
This concludes a first walkthrough of the RD Web Client that is coming up, based on the current preview version. I will share more details on this new client as they come in. If you are currently using RDS in a production environment and would like to test drive the RD Web Client functionality. Feel free to reach out to me so that I can help to get onboarded on the preview.
Comments are closed.