Forum Discussion
Jlee_106250
Nimbostratus
NimbostratusConfiguring 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...
Jlee_106250Nimbostratus
NimbostratusThanks 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.
Brendan_Fusco_1Nimbostratus
NimbostratusHi Mike - I'm a colleague of jlee's jumping into the discussion here. Thanks for your responses - looking forward to the results of your lab testing.
Are you referring to the "DNS round robin name" setting for the Connection Broker high availability in Server Manager? This is the property set by the Set-RDClientAccessName PS cmdlet as well. Whichever FQDN is set here also becomes the farm FQDN provided in the .RDP files generated by RDWA, which is the issue that we face. Setting the RDSH VIP FQDN here makes everything work but raises the question of where the RDCB VIP FQDN is used at all in the configuration. If the RDCB VIP FQDN is set here, clients are unable to connect into the environment as long as we have RDCB load balancing disabled in Group Policy, which is recommended by the F5 deployment guide.
