For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Jlee_106250's avatar
Jlee_106250
Icon for Nimbostratus rankNimbostratus
Jun 17, 2014

Configuring Remote Desktop Services 2012 R2 according to the F5 deployment guide

We are using Remote Desktop Services on Server 2012 R2, and we intend to deploy all RDS roles (Gateway, Web Access, Connection Broker, and Session Host) in a high-availability configuration. We are a...
application delivery
deployment
LTM
microsoft
Jlee_106250's avatar
Jlee_106250
Icon for Nimbostratus rankNimbostratus
Jun 17, 2014

Thanks for the quick response.

 

I'm not aware of any configuration on the RDGW for the RDCB HA FQDN - can you specify where this is configured?

 

That's correct; there is no longer an option to configure a RemoteApp source in RDWA. There is an option to set the client access FQDN for the RDS deployment using the Set-RDClientAccessName PowerShell cmdlet, but this also changes the RDCB HA FQDN in the deployment's configuration, which is a bit confusing.

 

mikeshimkus_111's avatar
mikeshimkus_111
Historic F5 Account
Jun 18, 2014
Hi Brendan, you are using RD Gateway, correct? When I connect to a published session host collection through RDWA, the client connects to the RD Gateway FQDN on 443. The gateway servers use the RDCB FQDN to locate the user's session on the broker and then they proxy the client through to the RDSH servers. The client sees the RDCB FQDN as the host name in the RD client, even though it's connected to a session host server. When you say that you set the RDSH VIP FQDN in the RDCB HA config, where are you getting that FQDN? I guess I mean that there should only be 2 FQDNs that you need in this case-one for RD Gateway and another for RDCB. Mike