Forum Replies Created
-
Posts
-
I don’t have the skills, but I assume that someone adept with Linux could figure out how to install the Wyse build without making use of a Wyse installation process. The main difficulty anymore is the lack of repository for all those old licensed images. It’s a shame all that hardware has been semi-orphaned in that fashion. The later generations,through the early years of the Dell takeover, were respectable hardware, even by today’s standards.
Jim – it took me awhile to figure out which Wyse-coded OS container applied to the C90LEW, but I’ve uploaded the one I had, Build S718.
If I follow your intentions, I don’t believe the Wyse machines will allow you to install their Linux builds on a machine licensed for WES7. Perhaps if you are able to hack their license-enforcing firmware…
I probably have a copy of at least one of the last C90LEW images. Is there a means to share that with Samir?
The last I have is BXB8_0858_8192. I have a more recent 16GB flash model arriving soon, so it is likely still within service. I have not tried to access images under the new regime, so I will have to see how that works out. I don’t have any contract arrangement with Dell.
Thanks, no problem. It’s a shame Dell has decided to deprecate Wyse’ good reputation by no longer providing such a simple level of support for those older machines.
I have a collection of quite a lot of those older images, I was just wanting to see what the latest X90L image might be.
At the moment, images for the X90M7, but next time it could be for another model.
Thanks for the suggestion, 5.7.2 is running now.
For a couple of 7020 series clients with older HAgents, when they check in and I do the HAgent update, the update appears to work OK so far as WDM is concerned, but the client hangs at the blue screen indicating update in process. I can shut the client down, and reboot fine.
Also, how do I log in to the WebUI? I cannot figure out what credentials are required. The server and repository credentials specified during installation don’t work. There is currently no password specified for the server user account itself, yet the WebUI requires a password to use the user account name.
Software requirement for 5.7.2 changed to Win 7 x64 Enterprise from Win 7 x64 and I have Ultimate on the PC I use for WDM.
I will try 5.7.2 anyway.
I regularly have used “roll to boot” to recover problem devices or install new boot drives, using 4.9.1, and I see that it uses TFTP during this process. Do I need to specify the TFTP option, as well as HTTP, during installation (Workplace version)?
I got this as a used unit and it turns out the installation on the flash was Microsoft’s Windows 7, not a Wyse image. After working unsuccessfully with Wyse CS yesterday on BIOS settings and various permutations of thumb drives and USB installers, we at least got the BIOS updated to 1.0L. Later I happened to try the Boot Mode as Legacy – which I’m pretty sure I recall trying unsuccessfully with the previous 1.0F BIOS, in fact it was set that way when I got the unit – and the unit booted into the existing Windows installation.
While looking through the WE8S B913 release notes for another matter, I saw mention that the resulting partition structure is based on GPT. The flash in the unit was MBR. Swapping in another flash with GPT structure, and setting the Boot Mode back to UEFI, installation of B907 using a thumb drive and the v1.21 USB installer was a success.
The release notes for the newly released B913 are much more detailed and better formatted than past iterations. Lucky me! They should write a partition structure check into the installer, so it doesn’t just hang or feed back confusing error messages.
Sorry, somehow missed your question about the image. I’ve tried both B907 (downloaded twice for hash check) and the recent B913, both via WDM 4.9.1 (+4 Hotfixes) and both via USB Installer V2.0.9.15. I’ve tried the older image via USB v1.20 as well. I’ve used various thumb drives, 16GB and 32GB, and have tried two additional flash modules in the device as well. BIOS is 1.0F. Error is always exactly the same message.
Have also tried altering the BIOS Legacy/UEFI setting, and AHCI/IDE.
Yes, the unit has a Windows 8 sticker, the info is listed on the tag, and the product number checks as the same. I’ve looked at the drive to make sure what it is, and the BIOS reports 16GB. The error doesn’t look like a license key issue, the installer is reporting the disk as only 512.
