- This topic has 8 replies, 2 voices, and was last updated 4 years, 3 months ago by
.
-
Posts
-
Hello,
Bought a bare-bones Wyse 5070 from DELL. The plan was to evaluate funcioinality in different O/S installations. However, installation is not possible. After the USB imaging process to initialize a USB stick, and inserting the USB stick to the device, an error 313 pops us complaining about either image is not of correct architecture or USB security key problem. Any ideas? Used both versions 3.1 and 3.3 of the imaging tool…
Thank you
Do you get this message while creating the USB stick or when trying to image the client?
A little background information: You cannot install any Dell Wyse OS (Windows IoT, Thin Linux, or ThinOS) as the client has an implemented security key. This prevents unauthorized imaging or imaging by mistake.
However, if you have a Dell Client with eg. ThinOS, then you can use the USB imaging method, of course. Only conversions from one OS to the other are not possible.CG
I get this error when trying to image the client. So for this, Wyse client is bare-bones (there was no OS installed). We did purchase 2 Wyse devices, one has ThinOs installed. The other was purchased as bare-bones by purpose, to try different OS…
You can only install a Non-Dell OS on the bare bone unit, like Windows 10, Ubuntu, etc.
CG
Thank you for the swift responses. My understanding is that these Wyse Clients have Memory Write Filters that prevent “committed” memory changes so that the internal memory modules are not worn off… I thought a non-dell OS does not “honor” these settings and installing a non-dell O/S like Windows 10 directly will pretty much “fry” the devices eventually. Of course, I may be way wrong here…
Ok, at this junction I can only think of one remaining option. Is it possible to get the USB Key value from the BIOS? I could use that as the value in the xml file…
This would be illegal. Therefore, I will not discuss this here.
CG
- You must be logged in to reply to this topic.