We recently deployed a new cart containing 20 of Samsung’s new $250 Chromebook. If you haven’t been able to get your hands on one of these new machines, let me just say that they’re really quite nice, especially for the price. Yes, the build-quality is a bit, well, plastic-y, but what can you really ask of a machine that costs that little? We’re a Google Apps campus, so Chromebooks are a great choice for a lot of things, and if we need some software that doesn’t run on them, we have other laptop carts.
A day or so after we first deployed the cart, though, we ran into a pretty major (but avoidable) hiccup–they were killing our network. Some students were able to log in but unable to get to the site they needed, while others weren’t even able to log in. Worse, students with their own laptops were also unable to get online, or their connection speeds were about what you would expect if you dialed into AOL with your Pentium 2 PC.
Why did this happen, and how can it be avoided in the future, you ask?
These machines shipped with Chrome OS version 23-point-something, and the current production release of Chrome OS is 25-point-something. The machines also needed a firmware update. This accounted for something on the order of 300MB of data that each machine needed to pull down. That would kill just about any AP. While our machines are enterprise-enrolled and thus had gone on the network at least once before they were first used in class in order to get them enrolled in our domain, none of them had been online for more than 30 seconds. In our domain management dashboard, we were able to set our machines to scatter automatic updates over a period of days to prevent this problem from recurring (the available range is 1-14 days), but, as a preventative measure before we did this, we pulled out the new machines two or three at a time and forced them to update.
As of this writing, I have received reports of 16 of the 20 Chromebooks being used at the same time by a class with no abnormal slowdowns in the network.
I must acknowledge the help and advice offered by members of the Chromium OS dev team who came to our aid quickly and helped us solve this issue in an afternoon.