Setup WYSE thin client to Autologon to Citrix server

Posted on 2009-05-05
Medium Priority
Last Modified: 2013-11-21
--> Current setup is about 175 WYSE thinclients connecting to a Citrix server farm. DHCP server with scope options are setup. FTP server is setup with WNOS.ini file and Username.ini files to configure user logon prompts and desktop environments. Currently users turn on WYSE unit and get prompted for credentials. All works great as is but the company wants implement auto logons for all thinclients.

--> Goal - Setup one thin client initially to autologon to the Citrix server farm without user input. In other words, turn on the thinclient and have it auto logon all the way without user input (I know this is a really bad idea, but they insist). Next setup all others to auto logon after we see how well it works.

According to WYSE, this should be setup using the global WNOS.ini file to point to a MAC.ini file. I just don't know how to go about this. I need you to provide specific instructions on what to do here and I can test all suggestions but keep in mind that any test must not affect other thin clients. Please let me know if I left out any info, again I'm not familiar with all of this.
Question by:gdctech
  • 4
  • 2

Assisted Solution

NDSSI earned 200 total points
ID: 24311749
Are you going to use one username and credentials or 175 diffrent?
If you are going to use one:
1: Configure username and password in wnos.ini and it will work. But you will have to configure a lot of settings in the TS enviroment so they don't get same sessions.

If you are goning to use 175 diffrent:
1: You will have to assign one thin client to one user, and then set up 175 diffrent Wnos.ini files based on mac reservations in DHCP. This meen 175 FTP folders with 175 wnos ini files and 175 mac adress reservations with 175 diffrent FTP path config. (DHCP option 162) and much work.


Author Comment

ID: 24351261
We are going to use 175 different usernames. So we will be assigning one thin client per user.
So do you actually setup 175 different WNOS.ini files? I thought the WNOS.ini was a global file. Can you actually have 175 of them? And you say you will need to create DHCP reservation for each thin client as well? I will look at this tomorrow to see if this info helps.

Expert Comment

ID: 24353275
Wnos.ini is a sentral file and you can use user.ini files. But to call user.ini files users must log in with their username on the thin client. Ok, you will then not have to type password, but username. Then all wyses will work for all users.

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!


Author Comment

ID: 24404136
Thanks AJ. I will look at this again tomorrow. I think I do have a solution and I will post my results tomorrow after testing this.

Accepted Solution

gdctech earned 0 total points
ID: 24435777
OK here is what I did to make this work:

1) I setup a test folder on the FTP server so I could implement this to a test WYSE thin client without affecting the other 175 thin clients - \\servername\C$\inetpub\ftproot\Test\wnos

2) Next I placed my WNOS.ini file inside of the"wnos" folder and also created a subfolder called "inc " for macaddressfile.

3) Then I configure both my wnos.ini file and my macaddressfile (no extension) as shown in my attachments - NOTE: The wnos needs to have the extension '.ini' and the macaddressfile must have the mac address of the thin client with no spaces or dashes and no extension (I had to remame my wnos file .txt to upload it here).

4) Configure the WYSE station to point to the new test folder: Under Network Setup, Servers tab, put in ip address/test (example Under options, change the File server and Root Path field to an arbitrary number so it doesn't see any DHCP options (Example 200 & 201 instead of 161 & 162). You may need to config a static address under General but I didn't have to.

That's it... Of course you have to cutomize these config files to match your username, password, mac addresses etc but if you made it this far, than you already know that.

So what this does is: Allows you to turn on the WYSE thin client and boot and then automatically logon to the citrix server without having any user input. Yeah I know, it's madness!!

Author Comment

ID: 24435893
Also when you log off, this will log you off of the Citrix server and then shut down the thin client automatically.

Featured Post

Get your Disaster Recovery as a Service basics

Disaster Recovery as a Service is one go-to solution that revolutionizes DR planning. Implementing DRaaS could be an efficient process, easily accessible to non-DR experts. Learn about monitoring, testing, executing failovers and failbacks to ensure a "healthy" DR environment.

Question has a verified solution.

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

After several days of searching and hunting for limited documentation, I wanted to share this guide to hopefully save someone the hassle of trying to figure this out on their own. I have tested this on Xendesktop 7.1 and PS 4.5 running simultaneous…
Citrix XenDesktop 7.6 Citrix Policies Audio
How to install and configure Citrix XenApp 6.5 - Part 1. In this video tutorial we have explained step by step installation of Citrix XenApp 6.5 Server on Windows Server 2008 R2 is explained in this video. We have explained the difference between…
This demo shows you how to set up the containerized NetScaler CPX with NetScaler Management and Analytics System in a non-routable Mesos/Marathon environment for use with Micro-Services applications.
Suggested Courses

840 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