Hello Robert,  Have you created any managed applications in the vWorkspace Console, configured under the resources tab? If not, then create a managed application that is published to all the RDS host servers and assigned to your users.  On your client, select the application radio button on the General tab. The drop-down list above this will then display the managed applications the user has access to, there is no need for you to enter a host IP address or use a DNS round-robin.  With this configuration the user will be connected to one of the RDS host servers for their initial connection, the broker will determine the most suitable host given the current load evaluation on each server.  If the user becomes disconnected from the session they can reconnect by launching the application, the broker will then identify the user has a disconnected session on one of the RDS host servers and reconnect the user.   Regards David
Hello, I have the following question: I'm settinga up a farm of remote desktop servers using a vWorkspace with one connection broker in front. What is your suggestion for load balancing a remote desktop connection. Based on my testing an application load balancig is working fine because it is connecting to vworkspace farm, but with desktop connection, using a quest vWorkspace client, there is no option to specify vWorkspace farm. If I use an dns roundrobin, then I have (sometimes) an issue with roundrobin itself, redirecting me to the wrong remote desktop session host.  Is there any workaround? Thank's in advance.  Regards, Robert
Remote desktop logon settings - load balance