Well due to a thunder storm and various power cuts over the past few days I have not managed to get any studying done. However at work I had a little triumph in getting our wyse thin clients working correctly at our remote site.
So since the site has been up the wyse clients have required configuring to get them to connect to a citrix session, bit odd as we had also set up an ftp site for the wyse clients to suck their config info from but for whatever reason this was not working. Anyway as we have only had one wyse TC go pop since the remote site went live we just got on with configuring the devices.
Anyway I was over at the site recently and decided to have a real crack at sorting it out and after a bit of fiddling and a bit of googling I discovered the answer.
It basically boiled down to the fact that when the ftp server location is given to the wyse client as a dhcp option the wyse client looks for the configuration in a specific directory from the ftp root (/wyse/wnos/wnos.ini) Our wnos.ini file surfice to say was not at the location. So I created the directory structure in the ftp root and altered the wnos.ini config file rebooted a wyse tc and hey presto it begins working correctly.
This of course now brings us the complete added bonus that if another one goes bang we can tell the users to replace it with another one and it will just work the same as the old one. Brilliant eh!
Its little things like that which please me the most!
Moral of the story if you just want to deploy dhcp option 161 for the FTP site then create a /wyse/wnos folder structure so the clients can see the wnos.ini file, otherwise you will also need the 162 dhcp option to specific an alternative folder structure in an ftp site.
Subscribe to:
Post Comments (Atom)
0 comments:
Post a Comment