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 able to follow the F5 (LTM only) deployment guide through Scenarios 1 and 2. We can create virtual servers on the F5 for the RD Gateway, RD Connection Broker, and RD Session Host roles. However, there is some confusion about how all of these VIPs interact to form the complete system and how the end user connects to the RDS deployment from the outside.
Specifically, we are confused about how the RD Connection Broker VIP/virtual server is used, particularly when RD Connection Broker load balancing is disabled via Group Policy as suggested by the F5 deployment guide. Once we disable RDCB load balancing, connectivity to the RDS deployment through the RDCB VIP no longer functions. We are still able to connect to the deployment via the RDSH VIP, but we are unsure if that is the proper configuration or which VIP F5 intends us to provide for end-user connectivity.
Further, we are having an issue with Scenario 4 in the F5 deployment guide, which deals with RD Web Access. This section instructs the RDS administrator to configure a RemoteApp source matching the RDSH VIP, which seems to be an important configuration step. However, this option is no longer available in RDS 2012 R2. How should this version be configured to achieve the same result?
Any assistance would be appreciated.