How to setup FTP site for WYSE thin client on XENAPP 5

Hello. We have a XENAPP 5 environment already in place and running that was only serving up apps and published desktops to Windows clients. We recently bought a few WYSE Xenith thin clients to try out. I tried setting up without the XEN.ini file, I can log in and see my apps list, but I get a SECURE CONNECTION TIMED OUT when trying to launch an app or desktop. I contact ed WYSE. They had me add my certificate to the Xenith, same problem existed. Then they said I need to use a xen.ini file and specifically use the fixlicense=clean option. I dont have any FTP sites running. WYSE said it can be done on a http (can I do it on an HTTPS)? I cannot find documentation on setting up a site to serve up this ini file. Any help would be appreciated. I am not familiar with setting up new sites in IIS.
Who is Participating?
ctnaConnect With a Mentor Author Commented:
This is ultimately what helped me:

I had to add the CRT to my xen.ini file. Even though I had added the .cer to the WYSE device, it would not work. So I did what the link above said, named my .cer to a .crt and configured the xen.ini file accordingly. I had to put the .crt file in C:\inetpub\ftproot\wyse\wnos\cacerts
Robin CMSenior Security and Infrastructure EngineerCommented:
See attached my xen.ini file, you'll need to put in the correct IP address for your time server (e.g. an AD domain controller)
On an IIS box you'll most likely have the following folder structure:
where inetpub is on the root on a drive (defaults to c:).
Within wwwroot create a wyse folder.
Within that create a wnos folder.
Put the ini file in the wnos folder.

Also get the latest fimware from Wyse, should be a file called C00_xen about 4.5MB and put that in the wnos folder too.

To make the files available via IIS, from IIS Manager (IIS 6), expand web sites, right-click default web site, click properties. Go to the HTTP Headers tab, click the MIME Types button. Add:
. text/plain
.ini text/plain
Think you may need to restart IIS, iisreset from a command prompt will do it.

The Wyse documentation explains some of this, but the folder structure and where to put the files within it was not overly clear. I had excellent support from Wyse over the phone, so call them if you're still stuck.
;*                  Sample INI file (rename to xen.ini)                 *
;*      (Refer to Admin Guide for additional list of supported INIs)    *
;*                                                                      *

;; Wyse Xenith will only replace local engine if an upgrade is available


;; Specify a default domain to show at login page 
;; (remove ';' to enable)


;; Specify timezone on client (in case of timezone passthrough)

'TimeZone="GMT - 08:00" 

;; You can choose to configure the location of XenDesktop server here 
;; instead of using DHCP Option Tag #181 
;; (remove ';' to enable)



Open in new window

ctnaAuthor Commented:
robincm. Thanks. I did create the /wyse/wnos folders already and had my xen.ini file in there. I followed your advice and added the MIME types (thank you!) I will restart IIS this evening. My Xen.ini file is very simple and similar to yours. I will try this in just about an hour and see what happens.
ctnaAuthor Commented:
I restarted IIS. Didn't seem to make any difference. It does appear that my thin client is reading the ini file somewhat because in the (on the Xenith device) "Central Configuration", File Servers/Path shows (unless it is pciking this up from the DHCP options, 161 and 181).
ctnaAuthor Commented:
I had to wing it a little, but the link provided helped me find the answer.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.