Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people, just like you, are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
Solved

WNOS.INI config for Server 2012 R2 Connection Broker

Posted on 2014-09-26
4
1,043 Views
Last Modified: 2014-11-15
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
Comment
Question by:Casey Weaver
  • 3
4 Comments
 
LVL 80

Expert Comment

by:David Johnson, CD, MVP
ID: 40346773
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
 
LVL 7

Author Comment

by:Casey Weaver
ID: 40346823
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
 
LVL 7

Accepted Solution

by:
Casey Weaver earned 0 total points
ID: 40433967
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
 
LVL 7

Author Closing Comment

by:Casey Weaver
ID: 40444253
Couldn't find anyone that has gotten this to work successfully.
0

Featured Post

Back Up Your Microsoft Windows Server®

Back up all your Microsoft Windows Server – on-premises, in remote locations, in private and hybrid clouds. Your entire Windows Server will be backed up in one easy step with patented, block-level disk imaging. We achieve RTOs (recovery time objectives) as low as 15 seconds.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Monitor input from a computer is usually nothing special.  In this instance it prevented anyone from using the computer.  This was a preconfiguration that didn't work.
Exchange server is not supported in any cloud-hosted platform (other than Azure with Azure Premium Storage).
In this Micro Tutorial viewers will learn how they can get their files copied out from their unbootable system without need to use recovery services. As an example non-bootable Windows 2012R2 installation is used which has boot problems.
This tutorial will walk an individual through the process of installing the necessary services and then configuring a Windows Server 2012 system as an iSCSI target. To install the necessary roles, go to Server Manager, and select Add Roles and Featu…

856 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question