Wyse Client and Windows RDS 2012 Connection Broker High Availability
We are testing our windows 2012 RDS environment and we are looking into RDS CB HA new feature in Windows RDS environment and we would like to know if the current firmware support it.
Our main question is will Wyse client support Win2012 RDS CB High Availability?
We were reading this document: http://microsoftplatform.blogspot.nl...a-and-rdp.html and we found that we need to create a single DNS record for our two connection brokers and that we will need to point to the CB farm instead of RDSH farm. Below, you will see an example of the connection.
" we’re launching an RDP connection using MSTSC with the destination set to the DNS farm name that points to the brokers. Would that not result in launching an RDP session to the RDCB server and not to the RDSH server(s) behind it? Yes it would!
If, after completing the step in blog post no. 2, I would launch MSTSC and enter the DNS farm name as the destination host (as shown below):
That would result in the error below. Why? Because we’re actually launching an RDP session to one of the RDCB servers, and of course that’s denied for our end user.
What we need to do is configure some properties in an .RDP file so that it has knowledge of the fact that we’re trying to connect through a HA Connection Broker.
These are the properties that need to be added:
use redirection server name:i:1
loadbalanceinfo:s:tsv://MS Terminal Services Plugin.1.Wortell_sLab_Ses
alternate full address:s:FARM.LAB.LOCAL
If we try that as our end user, the connection bar would still show the RDCB DNS farm name, but we’re now logged in on the RDSH server"
Our question is if Wyse client has the properties that we need to add in RDP client to make RDS CB HA works?
We havent test it this part, we are looking for information and we would like to know if you have any comments or questions about this.
Thanks for your support on this!
Try following this guide instead of the blogpost:
We have the same question as RLTechserv
We are testing Wyse Thin OS clients but can't understand how to connect client to Connection Broker.
Moreover, we have 2 SB containing 10 servers each. And this groups of 10 servers are separated in same queue into 2 groups for 5 servers.
We have 4 groups at the end for 5 servers.
Now we are using old computers managed by Windows 7 as Clients.
And Client connects to one of 4 groups of servers depending on IP adress (simple startup vbs script).
RLTechserv did you solve the issue?
Was this ever resolved? We are looking to implement some thin clients with Wyse Thin OS into an existing Server 2012 Farm which is HA via a connection broker setup and wondered if its possible.