Forum Discussion
Dayne_Miller_19
Apr 06, 2010Historic F5 Account
A new Deployment Guide for Windows Server 2008 R2 Remote Desktop Services should be online in the next day or so.
In the meantime, to avoid the error message you're seeing:
1) make sure that the DNS name (FQDN) of the RD Session Host virtual server -- the farm name, in other words -- is correctly resolvable from the RD Web Access server(s) where you're configuring the RemoteApp applications. This can be done via DNS or a local hosts file.
2) Using the same IP address as that which you've used for the RD Session Host servers, create another virtual server that listens on TCP port 135. That virtual should have a pool resource whose members are the RD Session Host farm servers, also on TCP port 135. In most topologies, you'll want to enable SNAT Automap (or use a SNAT pool) for this virtual server.
3) That virtual server IP address must be routable from the RD Web Access servers. (You state that the Connection Broker and Session Host servers are on the same subnet, but not where your Web Access servers are, or if the virtual server addresses are on the local subnet or one that is reached by traversing the LTM).
When you configure RemoteApp applications, the RD Web Access servers try to contact the farm via RPC. If using Microsoft NLB, presumably this part of the configuration is taken care of automatically. With a third-party device like F5 LTM, you have to set up the name resolution and traffic flow manually.
As far as RD Connection Broker goes, it's not much different than TS Session Broker. What problems are you seeing? In all our testing, configuration and behavior of persistence on BIG-IP LTM was identical whether provided by TS Session Broker or RD Connection Broker.