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."
just other people's computers.
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.
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.
"manually joining a WiFi network on 10,000+ Chromebooks is a nightmare."
Oh my god! Call an ambulance! Call the lawyers!! All this typing! Oh the humanity! Think of the helpless little children that can't configure a wifi!
Chromebooks are Linux based, aren't they?
The dumb children should learn to read the Man page. Right?
Or perhaps an info database should be made available. GNU info is a robust source of help, no?
Maybe, just maybe, they don't want the students to actually KNOW the WiFi password, with which they can connect unauthorized devices to the network. Thus, someone with the password has to go around to type it in on all the devices around the school when the network policy shits the bed.
-=This sig has nothing to do with my comment. Move along now=-
So implement MAC control or something similar -- only devices with approved MACs get on. All other devices are either banned or throttled. Yeah, yeah, students can still spoof a MAC, but they can steal a WiFi password too.
I can't recall ever having had to read one bit of a man page to set up wi-fi. In both Linux Mint & windows, all I've had to do was click the icon in the tray, select the network, and enter the password. Surely, Chromebooks would be just as simple, since they're designed to be used on wi-fi?
Chromebook -- a cloud-centric device that even the owner doesn't control. Basically, time-share computing updated for the 2000s -- should anyone be surprised that the people (Google) calling the shots occasionally screw up and screw their users? (I won't say "customers", since Google's real "customers" are advertisers and firms that buy customer data.)
..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.
Yeah, really, I mean, keeping a paper copy or two of basic setup bullshit is just too much to ask, right? And a blackboard? What the hell is that?!
You people are crazy, making these kids dependent on crap machines and telling them it doesn't get better than this.
"The battery blew up" or "The network was down" will be the new version of "The dog ate my homework".
which hammered our Windows servers for more than a week since it was a 1.1 GB update, and they for some reason decided to save the update in 11 KB files with another about 10 KB index file for every one of those files.
Manually joining 10000 chromebooks? There are 10,000 students and their care givers. Teach them to join wi-fi. It is a school! Teach them!.
sed -e 's/Chuck Norris/Rajnikant/g' joke > fact
Can't be that hard to change the wifi password to password1234 for the afternoon...
Isn't this what they wanted? To put all their eggs in one basket? Even though they knew Google was the one holding the basket.
Better known as 318230.
Hyperbole much?
Linux?
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.
... without a chromebook. The Children will be fine for 3 hours without one.
or go home
For a moment there, I thought this was an announcement about a new product called Google Glitch.
40 units were the only ones affected. We have about 175 devices total.
We have two schools, both with special-ed populations. One is taxpayer funded, the other is not.
Administration has things to do besides spend money - take attendance, communicate with child study groups and parents, complete IEP documentation, deal with medical issues and records...etc. All of these tasks require technology - practically nothing is done with paper anymore.
How do schools run in your area? With magic and free volunteers?
Google glitch sounds like a new product. How did it take machines offline again?
Google couldn't collect and exploit children's web usage data for a few hours. That must have really stung. I'm sure they'll make it up by doing something twice as evil.
by their incompetent educators handing them out to a greedy corporation.
As always, what I'd call the post-industrial transformation: the customers become the wares.
Instead of outsourcing your very core competences (and selling out your students to The Google and The Microsoft), why not build up enough in-house know-how and do your stuff yourselves, thus setting an example for your students? That's your fucking job, dammit!
It's not as if that was new. There are reams of .edus out there you might turn to for help. You're small? Find out about similar ones, band together.
Gosh. If you haven't any spine, how could you expect your students to grow one?
I know Microsoft getâ(TM)s a bad rap for forcing updates, especially when they have caused issues. Chrome OS is not unlike Microsoft is pushing updates with no real world way to reverse them if something goes wrong. My understanding was the workaround was simply to re establish the WiFi connection. Although more problematic with schools who have a administrator setup so students and many times teachers cannot access this information. My wife a teacher has Chromebooks for her classroom and in a similar issue she had to wait days for a tech to come out and reapply settings. No good, would be nice if updates were better vetted before release. But even Chromebooks have become a rather big ecosystem with many models and hardware. Microsoftâ(TM)s Windows has a even harder task with its vast amount of hardware support. Auto updates are simply asking for trouble.
So how did all those Chromebooks get the updated wifi push when their wifi was screwed up? If each really had to be manually done, then Google should VOLUNTARILY (if not then forced) pay a certain amount for each and every Chromebook to reimburse the manual labor, not to mention lost productivity.
What happened to Beta testing where Google would have pushed out to just some of their own Chromebooks before taking down everyone?
Don't individuals go to jail if they disrupt networks or machines?
Since companies are now people too, their top 5 layers should have to go to jail even if for symbolic 30 days each. OH, and prohibit from using computer technology or anything network for a year!!!