- This topic has 16 replies, 3 voices, and was last updated 7 years, 2 months ago by
.
-
Posts
-
Hello Thomas,
Currently we are using D10D Wyse terminals running on ThinOS 8.0_307 version, planning to upgrade to version 8.3_012. Please advise if we can update directly?
As neither the release notes nor the admin guide provided any relevant information. We already have downloaded the firmware labelled WTOS_D10D_8.3_012_EN.zip file and we plan to use it on an RDS environment with Windows Server 2016 in the back end.
Our setup are 2 connected monitors (3840×1080), wired Dell keyboard, wireless Logitech mouse.
We already have our Wyse folder, and wnos.ini file picking up from DHCP server and Wyse setting from FTP server. Could you advise regarding Platform drop down field in General 1 tab in ConfGen tool which one to pickup for D10D (If required)?
Which field in ConfGen tool/wnos.ini we need to update to pickup the hotfix/full firmware update files we have downloaded from Wyse Support website?
Thanks for your assistance.
You can go straight from 8.0 to 8.3 or even 8.4.
Just copy the firmware file ZD10_wnos into the wnos folder on your ftp server and reboot the client.
If the client is configured to use this ftp server it will automatically upgrade.CG
Hi Thomas and thanks for the prompt reply. Please note we’ve conducted all as instructed but Wyse terminal not picking up update for ZD10_wnos file. We attempted to rename the file name to D10D_wnos in case the file name could be the issue when picking up from our root folder. Also we noticed the file state was blocked and was set to unblocked but still no response from Wyse terminal which was also set to reset to factory upon restart.
Any ideas why it would not be picking up? Suggestions most welcome.
Thank you,
Laurent
Are you using ftp or http for transfer?
If http, make sure you set the correct MIME settings.
Check the IIS logs, to see what file ThinOS is looking for. A D10D will always look for ZD10_wnos as the firmware is “shared” between D10D and Z10D.CG
Hi Thomas,
Thanks for the heads up – We use Z10D_wnos firmware for 8.3 version in WNOS folder on server where FTP server is setup. We use FTP for transfer.
Our wnos.ini file has the below settings for firmware upgrade. Is it correct or are we missing an additional parameter?
autoload=202
Rootpath=/wyse/wnos
See the logs sample below in IIS on the FTP server :-
2017-05-18 08:16:16 10.12.1.49 – 10.12.1.215 21 ControlChannelClosed – – 0 0 b4df15cf-098f-42f7-8016-a03b1fe8a9fc –
2017-05-18 08:16:25 10.12.1.49 – 10.12.1.215 21 ControlChannelOpened – – 0 0 de8fb4a3-e211-464e-822f-7249a0064838 –
2017-05-18 08:16:25 10.12.1.49 – 10.12.1.215 21 USER anonymous 331 0 0 de8fb4a3-e211-464e-822f-7249a0064838 –
2017-05-18 08:16:25 10.12.1.49 – 10.12.1.215 21 PASS [email protected] 230 0 0 de8fb4a3-e211-464e-822f-7249a0064838 /
2017-05-18 08:16:25 10.12.1.49 – 10.12.1.215 21 TYPE I 200 0 0 de8fb4a3-e211-464e-822f-7249a0064838 –
2017-05-18 08:16:25 10.12.1.49 – 10.12.1.215 21 SIZE //wyse/wnos/wnos/ZD10_wnos 550 3 3 de8fb4a3-e211-464e-822f-7249a0064838 /wyse/wnos/wnos/ZD10_wnos
2017-05-18 08:16:25 10.12.1.49 – 10.12.1.215 21 CWD //wyse/wnos/wnos/ZD10_wnos 550 3 3 de8fb4a3-e211-464e-822f-7249a0064838 /wyse/wnos/wnos/ZD10_wnos
2017-05-18 08:16:25 10.12.1.49 – 10.12.1.215 21 PASV – 227 0 0 de8fb4a3-e211-464e-822f-7249a0064838 –
2017-05-18 08:16:25 10.12.1.49 – 10.12.1.215 52394 DataChannelOpened – – 0 0 de8fb4a3-e211-464e-822f-7249a0064838 –
2017-05-18 08:16:25 10.12.1.49 – 10.12.1.215 52394 DataChannelClosed – – 3 3 de8fb4a3-e211-464e-822f-7249a0064838 –
2017-05-18 08:16:25 10.12.1.49 – 10.12.1.215 21 RETR //wyse/wnos/wnos/ZD10_wnos 550 3 3 de8fb4a3-e211-464e-822f-7249a0064838 /wyse/wnos/wnos/ZD10_wnosAny advice are most welcome?
Regards,
Laurent
And where did you store the firmware?
C:\inetpub\ftproot\wyse\wnos\wnos\?CG
Hi Thomas,
No it was stored in C:\FTProot\Wyse\wnos folder
Do I need to change something in IIS?
Please advise.
Thank you.
This is how our IIS is configured to pickup the WNOS.ini file, so should be fine isn’t it?
Either you add the missing /wnos folder to your structure or you remove the Rootpath= parameter from your wnos.ini.
I guess you push the fileserver setting to the clients via DHCP, don’t you? Then remove the Rootpath parameter.
As you can see in your ftp log, the client is currently looking here //wyse/wnos/wnos/ZD10_wnos.CG
Hi Thomas,
Indeed we push our settings via DHCP to our Wyse terminals.
I will remove the root path parameter in the wnos.ini, place again the ZD10_wnos file in the C:\FTProot\Wyse\wnos and see if it picks it up now.
Will keep you updated.
Thanks for the heads up. Much appreciated.
Hi Thomas,
Just to give you a bit of background : DHCP and FTP are installed on same server where the Wyse terminals pickup the wnos.ini setting from that server.
In the DHCP scope options on the server, option 161 is checked with the server’s FQDN.
Shall I look into option 162 also or not necesary?
Kindly advise.
Thank you.
I just read that option tag 162 is for the root path, so if I remove the the rootpath parameter in the wnos.ini, I do not need to set it on the FTP/DHCP server’s options and also, do I need to remove same on the network setup of each Wyse terminal or the wnos.ini setting will take precedence if I just do not mention the rootpath parameter?
Hi Thomas,
It was indeed the rootpath parameter which had to be removed from the wnos.ini file – Once removed, the Wyse terminal upon reboot downloaded and applied the firmware update within 45s.
Thanks a lot for the heads up.
Much appreciated.
Hi Thomas,
Note that our Wyse terminals connect to a Windows Server 2008 R2 RDS farm via a connection broker.
One issue we have noticed was when we upgraded the firmware of our D10D’s from 8.0_307 to 8.3_014, when we log on first time on a D10D Wyse on our office desk, it works fine and the Wyse connection manager redirects to our RDS session. Then if we decide to login on our RDS session but on a Wyse terminal (Another D10D with same firmware version 8.3_014) in a boardroom, the RDS session is not redirected and we get a blank screen with a white cursor and it is stuck there. What we need to do is log off the RDS session from RDS session manager console and then the standard user can log on as fresh in the boardroom Wyse.
We did not have these on firmware 8.0_037 version when toggling between 2 same RDS sessions but on 2 separate Wyses. Not sure if the new firmware version is optimized to use on Windows 2008 R2, we will try with a newer OS like Windows Server 2012 R2/2016, but worth confirming.
If anyone has encountered this behaviour before, please let us know.
Regards,
Lsavripen
- You must be logged in to reply to this topic.