Redirect RDWeb in Windows Server 2016 TP4

tp4_rdweb1

The way how to redirect the RDS Webinterface in TP4 of Windows Server 2016 didn’t really change. But from time to time it make sense to put things back on a blogpost.

There are two options to redirect your RDWeb straight to your personal URL.

First you can use the IIS redirection. The feature will be installed when you install the RDWeb Role.

Anyway, make sure the role is installed. Use the easy way of powershell to confirm – run following command:

Get-WindowsFeature -Name *Web-HTTP-Redirect*

tp4_rdweb2

After that start your IIS management console and navigate to the Default Website. Open “HTTP Redirect” and enter the URL you want to redirect to. For examlple https://rds.alschneiter.com/RDweb/Pages. This will redirect the user from http to https and also to the right place of the RDWeb.

Second option: You can use the application.Host.config file from IIS. Open the file with notepad or notepad++ in admin mode and navigate to the code:
<system.webServer> <httpRedirect enabled=“false” />

First enable the httpRedirect by changing “false” to “true” and add the rest of the code like this:

<httpRedirect enabled=”true” destination “https://rds.alschneiter.com/RDweb/Pages&#8221; />

Example:
tp4_rdweb3

For more details of the application.Host.config file visit https://www.iis.net/configreference/system.webserver/httpredirect

Replace RD Web Certificate

Hi,

In some cases (DNS changes, expired certificate, etc.) you have to renew a certificate on your RD Webservers. I hat to do this today on a environment wit two RD Web Servers load balanced by a F5 Loadbalancer. But just replacing the web certificate on the RD Connection broker was not enough.

For some reason the cert was not valid after the replacement.

Solution:

  1. Delete all the old certificates in the personal store of the RD Webservers
  2. Reboot the Webservers
  3. Request a new certificate by using certlm.msc of one of the RD Webservers
  4. Export the .pfx file for the Connection Broker
  5. Redeploy the certificate using the Server Manger / Remote Desktop Services / Deployment Overview / Tasks / Edit Deployment Settings

This should allow you to access the RD Websites without having any certificates warnings.

Cheers,
Al