Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1304
  • Last Modified:

WNOS.INI config for Server 2012 R2 Connection Broker

It seems that anyone out there that has gotten this working has not posted any configs. We have a new 2012 R2 RDS farm (2 connection brokers in HA, 1 Gateway, 7 RDS Servers split into 3 different groups). I can't see any way to get our thin clients to go through the connection broker and display available desktops like our Citrix system does. Does anyone know how I should configure my WNOS.ini to do that? Thing Clients are D10D with ThinOS 8 and are 2012R2 certified.

connection broker HA: rdsh.domain.local
Session Hosts: rdsh01-07.domain.local
Session Collections: Group1, Group2, Admins
Gateway (shouldn't be needed internally): rdshgtwy1.domain.local
0
Casey Weaver
Asked:
Casey Weaver
  • 3
1 Solution
 
David Johnson, CD, MVPOwnerCommented:
Host=[name, IP, $SYS VAR] or Application=published application
Host — A list of server hostnames or IP addresses to which the the thin
client will attempt to connect (the next server on the list is attempted if the previous one failed). List items must be separated by semicolons or
commas. NOTE: $UN (see Table 1) specifies that the sign-on user name is used and should be set in a {username}.ini file. If set to Host=$UN in a {username}.ini file, the hostname will display as the sign-on user name. If set to Host=$UN in a wnos.ini file, the hostname will display as the default Start. Application — For ICA Only and defines the published application

http://www.freewysemonkeys.com/downloads/wtos/Wyse%20Thin%20OS%2064%20Parameters.pdf
0
 
Casey WeaverNetwork EngineerAuthor Commented:
But doing that would just remote them into the connection broker would it not? That doesn't seem like it would present the collections to the users so they could determine what they would want to launch.
0
 
Casey WeaverNetwork EngineerAuthor Commented:
Could not find anyone getting these systems to talk to a CB. In the end we just let the intelligence of the system do its job and performed DNS round robin. Systems were always balanced perfectly on all 7 RDS hosts.
0
 
Casey WeaverNetwork EngineerAuthor Commented:
Couldn't find anyone that has gotten this to work successfully.
0

Featured Post

Who's Defending Your Organization from Threats?

Protecting against advanced threats requires an IT dream team – a well-oiled machine of people and solutions working together to defend your organization. Download our resource kit today to learn more about the tools you need to build you IT Dream Team!

  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now