Forum Discussion
Jlee_106250
Jun 17, 2014Nimbostratus
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_111Jun 17, 2014Historic F5 AccountI'll check this in the lab and update the guide if necessary. IIRC, you just need to set the HA FQDN in the Remote Desktop deployment properties in Server Manager and it will pick it up automatically.
- Brendan_Fusco_1Jun 17, 2014NimbostratusHi 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.
- mikeshimkus_111Jun 18, 2014Historic F5 AccountHi 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
- Brendan_Fusco_1Jun 18, 2014NimbostratusHi Mike - what you're saying is the way we expect it to work. However, when we have the hostname as the RDCB FQDN and the gateway set to the RDGW FQDN, then disable RDCB Load Balancing (according to the F5 guide, we should disable it), the deployment no longer functions and clients are unable to connect. We are disabling load balancing by applying the "Use RD Connection Broker load balancing" Group Policy setting on the Session Host servers (set to Disabled) - is that correct? Also, in the situation that you describe, would we need an RDSH F5 virtual server at all, or just the ones for RDCB and RDGW? Thanks again for your help so far.