Tagged: Wyse 3040 5040 AIO
- This topic has 26 replies, 9 voices, and was last updated 1 year, 1 month ago by nick.vandeven.
-
AuthorPosts
-
November 15, 2019 at 3:10 pm #51219
In the WMS 1.4.1 Release Notes for Known Issues: The quarantine verbiage is throwing me off, but sounds similar to your issue.
- WMS141-375 – Occasionally, when a device is registered through DNS and DHCP
discovery method to quarantine group for the first time, the device
restarts continuously – There is no workaround in this release.
https://topics-cdn.dell.com/pdf/wyse-wms_release-notes21_en-us.pdf
November 18, 2019 at 9:35 am #51224I had the same issue. Unrgister the device from wms, than hit the G key, to reset the device. After that the device register again to WMS (I also use DHCP option)
The FW 8.6_024 works fine for me, if you need IEEE802.1x Authentication.
June 24, 2020 at 12:22 pm #52428Hello,
I have also this reboot loop issue with few our Dell 3040 and Dell Wyse T10 (Dell 3010).
We have 80% OK and 20% NOK
For 3040 : ThinOS v8.6_303
For 3010 : ThinOS v8.6_206
My Wyse Management Suite version is 2.0.
I tried with Full Policy deployment by WMS and not by FTP with wnos.ini
configuration is basic and we use Citrix broker.
June 24, 2020 at 12:38 pm #52429Hi,
have you try to unregister the device from the WMS?
June 24, 2020 at 1:57 pm #52430Not yet, i had to rollback the configuration.
My Wyse on test lab is OK 🙁 all wyse with issue are remotly located.
June 24, 2020 at 2:19 pm #52431Unrgister the device from WMS, than hit the G key, to reset the device. After that the device register again to WMS.
If you can’t hit the G key, try Factory reset from WMS, then click the Unregister
June 24, 2020 at 2:25 pm #52432Thank you Bialand for your help.
I can’t push G Key on wyse.
But i already tried the factory Reset by WMS and also with VNC remote control on wyse.
June 24, 2020 at 2:37 pm #52433after that the reboot loop issue is resolved?
June 29, 2020 at 2:24 pm #52447Hello,
No, reset factory don’t change anything.
I had 3 wyses 3040 on my lab with this issue this morning.
the issue appears by the terminal name parameter.
Before, it was : 19TC-$PF-&right($MAC,6)
After name changed 19TC-$PF-&right($MAC,4) and factory reset, it was OK
So, it’s an issue with terminal name but i don’t understand why some wyse are ok and few NOK. All Dell 3030LT are OK (never issue)
First time, i left the “terminal name” parameter blank for wyse to get her default name. then issue appears…
July 5, 2020 at 1:15 pm #52477Dell has released a new firmware.
Try that one.CG
July 11, 2020 at 9:40 am #52597Hello,
New firmware didn’t change any things.
i pushed the new configuration from WMS and i forced the name for wyse.
after few factory reset it’s ok now.
thank you
February 24, 2023 at 7:06 am #108041I’m having the same problem with firmware 8.6.710 and WMS 4.0.
What I tried and did NOT help was:
- Upgrading to Firmware 8.6.810
- Upgrading the BIOS to 1.2.5
- Removing the DHCP option tag 199 for GroupToken
Downgrading the firmware to 8.6.013 resolved the issue for me, but marks the TC’s as ‘Non compliant’ in WMS, because this firmware version uses a “Vulnerable Hash”.
I would still be interested to know how we can solve it and still use firmware 8.6.810.
- WMS141-375 – Occasionally, when a device is registered through DNS and DHCP
-
AuthorPosts
- You must be logged in to reply to this topic.