- #Windows server 2012 r2 remote desktop services web access install
- #Windows server 2012 r2 remote desktop services web access windows
Recently, I discovered that RD Web Access is susceptible to an anonymous authentication timing attack that can validate usernames within an Active Directory domain. It allows an organizations’ users to access their remote desktop services through a web browser. In part 2, we will go through setting up a second connection broker for high availability deployment.Microsoft’s Remote Desktop Web Access application (RD Web Access) is a popular web-based remote desktop client. Instead of having to go to each individual servers We can now access the RDS web page using: HTTPS:///RDWeb We will use DNS round robin to load balance between the two RD web access servers and this will create a single URL for users to access. Once cert is applied and all status say ok you should no longer get a cert error when access the RD web access URL
#Windows server 2012 r2 remote desktop services web access windows
You can also create a new certificate on this windows aswell. click select existing certificate and select the cert that will be used. Select the roles you want to assign the cert to in my case it was the two RD connection broker and RD web access. I wont go through generating the cert here but once you have the cert you can go to Deployment overview and click on edit deployment properties. Last step I want to do was to use a wild card cert that I have from my internal CA so that I don’t get any cert errors when access the RD web access URL. To finish the current deployment I will add the second RD web access server to do this click on task above deployment servers and add RD Web Access Servers and select second server that will have the role added All servers need to be added to server manager or you be able to mange the deployment Once the deployment has completed there will be the RDS icon on server manager.
The deployment progress screen should then show it can take a while for this to complete Next confirm if all servers have been selected for the correct roles and deploy Select both servers that will be used for sessions hosts. We can add the RD web access to the second server after
#Windows server 2012 r2 remote desktop services web access install
Select Install the RD web access role on RD connection broker. Only one RD connection broker can be select during initial setup HA will be setup after intial setup On the Installation type select Remote Desktops Services installation. Go to mange on the top right of server manager and click add roles and features Once all servers are added to server manager and showing as online we can start to install the RDS roles. To start we need add all servers to server manager on one of the RDS servers.
I have two servers that will be RDS session host, connection brokers and RDS web access and one that will be used later as the licensing and SQL server for RDS broker HA setup. I will be using three servers for this deployment as I want to co-locate some roles as to keep the number of servers to a minimum as this is a small 20 users setup. So I decided to build out the deployment on my test domain to make sure it would work out as expected. I recently had a request to build a new Windows Server 2012 R2 RDS farm as the existing single Windows server 2012 RDS deployment as it was crashing and users where getting a bit angry.