Forum Replies Created
-
AuthorPosts
-
And i found one bug when i use multifarm
if password of user was expired, the login popup is above the modification popup
Hello.
No, we cannot send commands to the devices.
As they get their ip address by dhcp, we cannot ping them anymore.
Hello.
We have 9.0.4024 and 9.1.1131 versions of ThinOs.
What are the exact versions of ThinOS is installed? Can you send commands to the non-compliant devices?
Hi,
Don’t know what happened but it’s suddenly working!
Just another small question:
The 5070 comes with newer firmware then i currently have configured on my 3040’s out of the box.
It tries to download the older firmware (and fails). Any way to avoid this?
Hello.
I have upgraded my device to ThinOs 9.1.5067 and to the latest bios version.
I have configured my WMS as advised in your document (with the admi/password/domain and without the enrollment password).
I still have an issue as the logs say :
W/WebUIProc/WebUIModule (1/1) scep autoEnrollment error: “scep cannot get enrollment password”
What do you mean when you “you either change the Enrollment password each time or you have disabled the expiration of the password on the SCEP server” ?
Do I have to configure PasswordValidity to 0 to configure UseSinglePassword to 0 ?
Thank you for you job.
Well, it kind of was, you just happen to be several versions behind.
January 12, 2022 at 10:28 am in reply to: How to best migrate Terminals with separate mac.ini filer to WMS #106954What settings are you applying with Mac INI?
January 12, 2022 at 10:27 am in reply to: Pushing WES7 image to clients results in endless boot loop. #106953I recently went through this myself.
Now that you have upgraded your WMS server before updating your WDA on the device you will have to manually install using admin login. I used WDA_14.5.5.5_Unified.exe
With the device able to talk with WMS 3.5, I was able to push MerlinPackage_Common401_rev4.exe from WMS.
I went further and was able to then push a 5060 that had WES 7 to Windows 10 IOT. You might not be able to go to Windows 10 IOT if your device was not purchased with upgrade rights.
If you are using ThinOS 9.0.1136, you cannot upgrade the ThinOS firmware or install application packages after September 2021. You must disable the time server on ThinOS, change the system time to Aug 2021, and then upgrade the ThinOS firmware or install the application package. Once you have this done download ThinOS 9.0 to ThinOS 9.1.3129 Image file for Dell Wyse 3040, 5070, 5470 and 5470 All-in-One Thin Clients
Then you will be able to upgrade to ThinOS 9.1.3129 or later to ThinOS 9.1.5067 Image file for Dell Wyse 3040, 5070, 5470, and 5470 All-in-One Thin Clients
Hi Jim,
Nope, that’s why I tried upgrading to see if that would help at all.
Currently have 2 of the 5070’s connected that have this issue, 1 with 9.1.3129 and 1 with 9.1.5067
Did the 5070 work at version 9.1.3129?
I have passed along this issue to Dell PG, hopefully, we will get an answer.
Let me position this question, would there be interest in me hosting a Zoom session where we can discuss issues and possible answers to issues? I will be one of the first to say WMS and other TC management tools are not perfect, but with some collaboration, we might be able to find a working solution with WMS Standard (Free version).
Alright, figured out how to get the Imaging Tool to work.
The USB Stick wasn’t found, because “Boot from USB” was disabled. Since then I got one Wyse working with a ThinOS 8.6 File, the others are getting error code 233. Which means, I don’t have the right version. But the question is, how do I get the Thin OS Lite Version as an Image?
Pulling the image/file from a working Wyse gave me the error code 300.
Any idea what to do next?
-
AuthorPosts