Google Glitch Took Thousands of Chromebooks Offline (geekwire.com)
Slashdot reader Bismillah was the first to notice stories about Chromebooks going offline. GeekWire reports:
Tens of thousands, perhaps millions, of Google Chromebooks, widely prized by schools due to their low cost and ease of configuration, were reported to be offline for several hours on Tuesday. The apparent cause? A seemingly botched WiFi policy update pushed out by Google that caused many Chromebooks to forget their approved network connection, leaving students disconnected.
Google eventually issued a new network policy without the glitch -- but not everyone was satisfied. The Director of Technology at one school district complains Google waited three and a half hours before publicly acknowledging the problem -- adding that "manually joining a WiFi network on 10,000+ Chromebooks is a nightmare."
Google eventually issued a new network policy without the glitch -- but not everyone was satisfied. The Director of Technology at one school district complains Google waited three and a half hours before publicly acknowledging the problem -- adding that "manually joining a WiFi network on 10,000+ Chromebooks is a nightmare."
manually joining a WiFi network on 10,000+ Chromebooks is a nightmare
Yep.
Bet you're happy they've quit putting Ethernet ports on everything huh? You know, with an Ethernet port, even if they almost never used them, you could dust it off, plug in a cable later and get the update that would fix your WiFi issue. If only you had the port.
I stay mad at Macbooks over the lack of Ethernet jacks these days, Chromebooks are a mixed lot, but one thing I do know, Samsung put out some really thin systems with a fold-down Ethernet port so there's no excuse not to have and and having one is much more reasonable than expecting everyone to keep up with a dongle.
The preceding post was not a Slashvertisement.
Quite true, considering that Chromebooks are aimed at users using other people's computers (students using school's computers, employees using company's computers, etc.), I'd say they pretty much cover the role.
You get a cheap gadget created a a giant corporation used for collecting and re-selling information about the "users" and expect to use that as a PC. What'd you expect?
I don't respond to AC's.
We were impacted by this glitch. We are a small school, so manually connecting 40 or so chromebooks was not a huge deal.
However, this is not the first time we have been impacted by a Google screwup. We've had outages where Google's authentication service failed and no one could login to their chromebooks.
We've since decided that we are walking back Chromebooks for staff members and putting them back on Windows laptops. Between the functional limitations of a chromebook, and the centralized parts we can't control, we've decided that an entirely cloud strategy for students and teachers is too risky.
Admin and teachers will be provisioned on on-prem systems. Students will be cloud provisioned. At least this way when Google's infrastructure shits the bed, the business side of the school can keep going.
..because the vendor pushed out an untested update again. Now we are teaching children to accept being dependent on a single point of tech failure. Good old pen and paper is still better, your brain retains the info better too.
-Time to seed my lawn, get off.
No school today...because the vendor pushed out an untested update again.
Let me help you, as it appears you didn't do 30 seconds of Googling to help yourself. Chrome OS is heavily beta tested, and is built upon Chromium OS, which it itself is heavily beta tested. As a Google admin for a public K-12 school (~1200 Chromebooks), I have the option of assigning all my Chrome devices into one of three categories of development. Google "recommends" I activate a policy that will randomly assign 5% of all devices to a beta channel* to assist them with testing and development, though our district chooses to use stable-only software.
Occasionally, a serious bug actually does make it through to a stable, but if it is found, Google has been incredibly quick to prioritize its fix and release an update. It's only when there's a doozie like this where suddenly everyone starts the finger-shaming.
* The first time I turned this on, the very next day, we had about five Chromebooks all come into our office. Every one of them had Chrome crashing randomly, usually within about 30 seconds of it opening up. All had the exact same version of Chrome on it, v.51 I think, when every other one of our Chromebooks had v.50 or below. The only way we were able to fix them was to use a CrOS repair drive utility to reinstall CrOS with a previous version. When I saw that other Chromebooks that had v.50 couldn't be upgraded to v.51, I reasoned that these were the beta tested Chromebooks. I turned that feature back off, but I still saw a few more Chromebooks trickle into my office over the next few days that also "got lucky". After that, never again.