19. January 2021 at 1:42 #57285
I recently received 3 new 5070 Wyse clients which came with BIOS version 1.5. I’m not able to upgrade existing older Wyse Client BIOS versions, so my only alternative is to downgrade these 3 new devices to version 1.13. I downloaded the X10 1.13 BIOS from this site, and rebooted into the BIOS Update menu and provided the password. I found the updater can read the USB drive and see the x10_bios.bin file, however when it scans the image, I get:
BIOS Update File: FS0:\x10_bios.bin
For consistency / technical reasons, I want to get these new units to 1.13 – is it possible? Am I doing anything wrong?20. January 2021 at 15:50 #58382
I am not sure this is possible.
And I would always go with the latest and greatest BIOS version.
CG1. February 2021 at 3:57 #66228
Thanks for the reply – I decided to go down a different path now and slightly backdate the supplied ThinOS version 8.6.303 to 8.6.113 (instead of downgrading BIOS), and yet I am still getting an issue trying to do this. I know you said in your FAQ:
“1) Units with new Dell Mac Address ranges require 8.1_027 or higher code. In newer 8.4_108 code there is actually blocking to prevent downgrades”
Is it possible me trying to downgrade might be causing the error I am getting (using Merlin USB stick bootable push image of 8.6.113 with USB Imaging Tool):
“Error whilst validating security key (error code: 233)
-Mismatch between the security key of the device and the security key present in the XML file of image package
– Check if you are trying to deploy correct image for the intended platform. Re-register the correct image package.”
Any clue as to what I may be doing wrong?3. February 2021 at 12:33 #67875
The security key mismatch is due to a wrong image.
You may have a 5070 with ThinOS and try to install a ThinOS including PCoIP (or vice versa).
Make sure you are using the correct image.
CG5. February 2021 at 6:32 #69088
Many thanks for the pointer CG. I took a good look but…
I originally got the 8.6.013 ThinOS Wyse 5070 raw image from the Dell website here: https://www.dell.com/support/home/en-au/drivers/driversdetails?driverid=mrv06#
After I downloaded it, I realised I couldn’t use it with a USB stick (I have no central FTP server or WDM software to do it from), so I downloaded the Merlin 8.6.013 image instead: https://www.dell.com/support/home/en-au/drivers/driversdetails?driverid=kgdm2&oscode=thn80&productcode=wyse-5070-thin-client
This second image is the one that I got the error code 233 from. When I go to push this Merlin image, the screen listing the image says:
Architecture: WTOS_Wyse_5070_Thin_Client_16GB_0 – WTOS, X64 (WTOS,OS,5070)
The current System Information tab on my 8.6.303 Wyse Client itself shows:
Operating System: ThinOS Build Version: 8.6.303 Build Name: PX10_wnos Platform Name: 5070 Celeron. I want to downgrade from 8.6.303 to 8.6.013 as I mentioned.
When I lookup the service tag/warranty info of this new device on the Dell website:
It shows I have: 619-ANCI : PCoIP enabled Wyse ThinOS, English
I’m just a bit confused because I could find no other references to an 8.6.013 operating system in any of the OS downloads on the Dell site (even when I looked up older versions). I actually think I have the correct version but there is a weird key mismatch. If only I knew how to extract the eeprom key on my current Wyse, I could compare it to the one within the XML file of the Merlin image and possibly match them to force the update. Some other people seem to had success with this:
“For anyone that is curious –
Old key : 01090737
New key : 01090837
If you change this string in the XML and rsp files on the flash drive to match the client, it will install without issue. I was able to install 2.1 on a system without the patch, simply by changing this string.”
The whole reason I am trying to backdate the OS on this particular Wyse 5070 (8.6.303) is because the Connection Manager is not saving my local RDP sessions between boots. When I reboot, the definition I created previously is gone. My other Wyse clients running 8.6.013 do not have this problem. Unfortunately these client are physically located overseas in New Zealand and I don’t have the ability to upgrade them in any way (and I want to keep all of them the same if possible. I guess worst comes to worst I could try ThinOS 9.1 and see what happens.
Sorry for the long message.
7. February 2021 at 18:13 #70796
- This reply was modified 3 months ago by dfvanden.
7. February 2021 at 23:50 #70954
- This reply was modified 3 months ago by ConfGen.
That worked! Was I filtering wrongly on the Dell site or do you have access to a different repository?8. February 2021 at 10:46 #71286
No other source. I am using the normal Dell Support page.
You just have to filter on top for “ThinOS PCoIP” instead of “ThinOS”-only.
- You must be logged in to reply to this topic.