WiFi breaks on v120

[SteveHarmon]

Recently we have had some Chromebooks (Lenovo 500e gen 2 and gen 3) slip past our version limit (currently at 118) to go to 120. Once it does that, then the Chromebook does not connect to our SSID. We can manually change to other SSIDs (the students cannot because they are not given the passkeys) but the one we use for our Chromebooks does not work. Has anyone experienced or heard of this? Does anyone have a solution or a setting change to suggest?

[Dave_Burek]

I have not seen or heard any reports of this happening with our Chromebooks. We do not limit OS versions and we do not have any of the Lenovo Chromebooks either.

[claycodes]

Hey Steve, do you have an 802.1x network? Have you filed a case with Google Support?

[SteveHarmon]

I haven't filed a case - just wanted to be sure I wasn't missing something easy before I contacted Google Support. This morning, our network engineer came in (he was out sick yesterday) and told us that he has a rule set up on the SSID which checks the operating system of the device for the word "Chrome" (this is to ensure that only Chromebooks are able to get onto that network). I guess in previous versions, "Chrome" (or "ChromeOS) is in the field that is checked, but in v120 the phrase is not there. Before we move forward to v120, I guess we will need to figure that piece out. I might submit a ticket with Google (or contact our account rep) to inform them of this change and how it affected us.

[kaned]

I have also not had any reports of this. We primarily run Dell here.