Built-in software âdeath datesâ are sending thousands of schoolsâ Chromebooks to the recycling bin
Built-in software âdeath datesâ are sending thousands of schoolsâ Chromebooks to the recycling bin
The problem comes down to education institutions. I remember when we got Chromebooks in my highschool (8 years ago) admins forgot to turn of developer mode and half the school unenrolled the Chromebook managing to bypass all restrictions. This went on for half a year until one day our school needed to run a state exam (more for measure of schools performance not as a college entrance exam or anything).
The computerized testing program required deploying a specific chrome app accessible when chrome book is logged out (canât just download from chrome web store). When they tried to push the client since half of Chromebooks were unenrolled it failed. This required the school it to recall pretty much all chrome books to manually re enroll all of them and disable developer mode (prevents unenrolling and prevents sideloading Linux).
At least thatâs my two cents (not a school it admin just a memory from the past đ).
Problem is if older Chromebooks are used for Linux in an educational environment there would be nothing stopping a student from whipping up a bootable USB and dumping another distro (bypassing restrictions). Iâm also not sure if there is a enrollment mode equivalent Linux (there may be but not sure).
Actually in your case our school has a BYOD program (bring your own device) in which you can bring your own laptop with whatever flavor of OS. Firewall would restrict you, your device would be considered untrusted, and in testing a loaner locked down chromebook would be provided. The issue comes with non BYOD devices.
Now lets assume a school has 1k students. If they allowed os unlocking and allowed students to tinker with the os. Then they would need 2k chromebooks 1k unlockable 1k locked down for exam administration (assume the whole school needs to take it at the same time). From a admin/IT perspective why should the school need to pay double the number of chrome books just for a few students to install their favorite brand of linux.
Even under the best circumstances where support queries arenât increased (from students softbricking/ not knowing how to use linux) and say they are able to preserve 1k unlockable chromebooks, admins would still need to replace the other 1k locked down chrome books at end of software to stay in compliance with testing software (negating any financial benefit).
You blame the school instead of your parenting which is at fault*
Usually kids âmisbehaveâ in public because of close-minded parents or parents who try to control their kid too much, and most of all parents who donât encourage good behaviour correctly. Parents really like to blame their kid for behavioural issues when in reality theyâre the reason itâs a problem. (Especially with e.g. people who have disabilities like Bipolar, Autism, ADHD, parents internally blame their kid for everything and punish the kid, even though the disturbances caused by the disorders are something you can address and help the kid with with good parenting)
I suspect most of the kids who do that kind of stuff are neurodivergent and either undiagnosed or not treated correctly by their parents and not given proper treatment
I never really understood the need for that strickt controll of the hardware
Federal laws and rules for educational technology:
CIPPA - www.fcc.gov/âŚ/childrens-internet-protection-act
COPPA - ftc.gov/âŚ/childrens-online-privacy-protection-rulâŚ
and to an extent
Problem is if older Chromebooks are used for Linux in an educational environment there would be nothing stopping a student from whipping up a bootable USB and dumping another distro (bypassing restrictions). Iâm also not sure if there is a enrollment mode equivalent Linux (there may be but not sure).
They could just disable booting from USB drives in the bios and password protect it. They could install something like Fedora Silverblue, or even customize the image used to include whatever modifications they want. Any changes they made to the image would be propagated through autoupdates. Kids wouldnât have root, so they couldnât forcibly install a different OS. Of course they could install flatpaks to their home directory, which is probably something administrators would want to prevent, but a knowledgeable student can always find ways to do what they want.
This of course requires schools/districts to hire people to manage that stuff, which could be a problem.
(prevents unenrolling and prevents sideloading Linux)
Should note that itâs not completely foolproof, I know because I did it. Itâs just not easy and technically you can get in trouble for it. Never got a âvacationâ for it though đ