- This topic has 11 replies, 7 voices, and was last updated 2 years, 2 months ago by Twilley.
-
AuthorPosts
-
February 2, 2022 at 10:13 am #107017
Hello all,
I would like to ask you for help. This popup started appearing after the update to thinOS 9.1.5067.
Any idea how to hide this popup?February 2, 2022 at 12:02 pm #107020I put in a ticket for this with Dell and it has been pretty quite about it. In my case though I’m seeing it happen on a certain switch in my test lab the Cisco catalyst 3560-cg series. On this switch the 9.1.5 software am getting a 1 hour ip lease if I roll back the software to 9.1.4 I get a 12 lease and also with all 8.6 thinos. Look at your lease time in the event log but just so you know that pop up will come up every time your device renews the lease and will also stop you from typing and forcing you to click on the screen to make it go in the back ground.
On our normal switches I get a 12 hour lease and it doesn’t matter what thinos I use.
February 2, 2022 at 1:42 pm #107024Thank you Chris for the response.
Yes, as you wrote, it is related to the DHCP lease.It’s very annoying. I hope that dell fix it
Thank you
Martin
February 9, 2022 at 3:36 pm #107101We’re also seeing this with our PILOT testing for ThinOS 9.1.5067. Most of users are only seeing this at startup. We have 2 users so far that are receiving the msg throughout the day and both are on mesh networks at home.
I’m so frustrated, all of our devices in the org are still on ThinOS 9.1.1131. Dell has yet to deliver a solid upgrade without issues.
Has Dell offered a solution to this or provided a workaround?
Thanks,
February 22, 2022 at 7:20 am #107170This seems to be specific to 9.1.5067 (we skipped 9.1.4234) I’ve noticed it when changing access points at home on WiFi or when the device picks up a new DHCP lease. The other thing I’ve noticed is my device at home doesn’t seem to honor the DHCP lease time I have set to 24 hours. It seems to pickup an address whenever it likes. We have thousands of devices throughout our firm both internal and at home but no complaints or calls about it in particular. I’m hopeful something will address it in the next release.
February 22, 2022 at 10:25 am #107171I uploaded some logs from 9.1.4 and 9.1.5 for Dell and they have not said a lot I’m afraid. I did some more trouble shooting and here is what if found. It only happens on my lab switches in our environment which are cisco catalyst 3560CG series and 3560CG poe. Also it doesn’t happen on the wireless for us either. I’ll let you know if I hear something which I hope will be pretty soon.
February 28, 2022 at 3:46 am #107213Hello All,
it look like dell released a new version of ThinOS 9.1.6108, so we will see if the popup will be still shown. I hope that no.
February 28, 2022 at 12:34 pm #107215I tested the new firmware 9.1.6 and it seemed to fix the lease time but they didn’t fix the thin client getting its name from dhcp option 12 tag.
February 28, 2022 at 12:34 pm #107216I tested the new firmware 9.1.6 and it seemed to fix the lease time but they didn’t fix the thin client getting its name from dhcp option 12 tag.
March 1, 2022 at 3:44 am #107218Hello,
Does anyone know with 9.1.6 if the error has been fixed that the hostname is set to default WESXXXX when switching groups?
I also had problems with SCEP with 9.15, suddenly my Client certificate was no longer integrated, which worked with 9.14.
best Regards,
Wulf
March 2, 2022 at 9:42 am #107280Try using $TN in the Terminal Name Field. To make this a Global setting, place it in your Default Policy.
This will make WMS remember the Device name set.
March 2, 2022 at 11:19 am #107291Hi Jim,
I went and tried this and it doesn’t seem to work either. I factory wiped it and rebooted it several times. I am using or trying to use client name to name them and I was assuming that the second screen shot was for naming them manually in WMS.
March 11, 2022 at 4:05 pm #107346ThinOS 9.1.6108 fixes the renaming issue when changing groups. We could not migrate devices to a new server using the 9.1.5067 build without having to manually rename the device again. Now it works fine.
-
AuthorPosts
- You must be logged in to reply to this topic.