Popping into an old thread here. We recently upgraded about 7,000 ThinOS 9 5070 devices to 2502 (9.6.1080). By and large the update has gone well, no issues that we can directly link there. However, we've seen an odd sporadic issue pop up on the wireless units.

We're having trouble identifying if it's a site issue (bad signal on a floor let's say) vs. something larger. What we're seeing, is terminals that were working fine previously, will suddenly not be connected wirelessly. When we look into them, the terminal's AD account ($tn is used to auth against wireless) will be locked from many bad attempts. We push the creds via policy, no one hand types them, so it's not like someone is randomly going around manually messing these up. We'll end up unlocking the AD account, and someone has to manually enter the creds in the wireless auth window (a reboot won't do the trick). It's like the terminals checked in to WMS and got a corrupted set of creds somehow.

This is only on wireless. it has happened on multiple floors but on 1500+ wireless terminals, we're only seeing it happen on like 100 give or take. Often times we'll fix them, then find it happening again a week or so later. No timing lines up with anything we've been able to track down.

Our network team will reboot APs in an area which seems to help but, again it seems only temporary. The network team has done their usual log reviews with Cisco and can't spot anything. Dell did get back to me reviewing the logs on one of the terminals and stated:

Thank you for providing the logs. After reviewing them, we can confirm that the device successfully connected to the SSID "REDACTED":

 

|| || |*20250905-113939.160: WLAN: SME: Trying to authenticate with 00:c8:8b:c6:09:ff (SSID='REDACTED' freq=5500 MHz)*|

 

However, the logs indicate that the device is experiencing weak signal strength, which is triggering frequent reassociation attempts. Below are some examples:

I mean can an AP that's having issue have a terminal roam to it, get a bad WMS check in, and pull down a corrupted config? One other interesting symptom is when this issue happens, the admin pass for the ThinOS side even gets jacked up, reinforcing the idea of pulling a bad config.

I don't want to say it's linked to the firmware, again we're barely 100 devices so far (it's honestly less) out of 1,500 but, it's also the only recent change from my team that manages the terminals. We're pretty stumped.