nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

2 UI issues since upgrading to 200.15.6.12.304

gritech

Per the release notes "User interface enhancements in terms of UI label changes, panel enhancements, and optimization."

Issues present in 200.15.6.12.304, worked in 200.14.6.1.203.

Chrome OS devices are no longer recognized. There is no icon in the OS column and "OS Vendor Type" and "Device Model" are blank in client details.

More of the columns are under Clients are not resizable or have a minimum width wider than needed which results in more horizontal scrolling. Please allow all columns to be resized to any width desired.

Find more posts tagged with

Accepted answers

All comments

gritech

Update - The ChromeOS issue might be due to the latest Chromebook update. My up-to-date Chromebooks don't show an OS, but an old one stuck a few OS versions behind is working. I'll see when students are in the building again tomorrow. Might just need a signature update for the OS detection.

syamantakomer

Hello @gritech,

Thank you for reporting the issue, we will look into it.

In the meantime, please provide below details.

Chromebook model number
Software version (working vs non-working)
WLAN card driver software version.

gritech

Hello syamantakomer,

Thank you for looking into my issues.

I'm pretty sure just the latest update broke the OS identification. As of Friday student Chromebooks were detected correctly and most hadn't updated yet from 119.0.6045.214. It's possible/likely that there were a few updated and undetected that I didn't notice.

Detected: 119.0.6045.214 and earlier (last stable release)
Not detected: 120.0.6099.203 (current stable release, Jan 8 but rolls out slowly unless manually updated)

We have a mix of Samsung Chromebook 4, Dell 3100, and Dell 3110.

I'm not sure the WLAN driver version is relevant or easily determined as it's baked in to ChromeOS and can't be changed by the user or admin.

sanjay_kumar

Hi @gritech

Can you provide me the screen shot of the OS details not showing along with the below logs which will be easier for us to diagnose the issue?

1. Go to Administration >> Diagnostics >> Debug Info >> Check the "Enable Debug Components >> Select all the components >> Click on Apply >> . If you have more APs, then just enable below components.

2. Try connecting the client and reproduce the issue.
3. Go to Administration >> Diagnostics >> Client troubleshooting >> Locate the client >> And click on Start.

4. Once the issue is reproduces, click Stop and Click on Export icon.
5. Go back to Debug Logs tab, click on Save debug logs.

Please share both the files so that we can check.

Anye02

I Also noticed my AP after updating will randomly restart and it always says application reboot under logs. But I reverted back to 200.14 and been good so far. I also noticed that it won’t display traffic flowing through it, and displaying pretty much what is going on with it, and the only thing that gets rid of this is by power cycling it… not ideal, but I would just revert

gritech

Sorry I had replied but somehow it disappeared.

The ChromeOS detection is mostly working fine, but occasionally there are a few that randomly aren't detected until disconnecting and reconnecting. Not repeatable as it was when I first posted.

Since it's mentioned here by Anye02, I'm also having the AP Restart : application reboot issue on both 200.15 releases.

Anye02

Bump.
I had a H350 and used that for my primary master, ( WI-FI disabled with the option “ if the Unleashed network contains three or more connected APs, the master won’t provide WI-FI service.” ) and the R750 as a slave instead of master. Which did stabilize it, but still have heartbeat loss problems, and AP application reboot. Originally, I had my R750 as master.