The MDM is tied to the S/N ******and stays in the NVRAM somewhat persistently. The only way it gets removed is a power flush. ***It will eventually be restored once you connect it to the internet. Once it sees it has the MDM tie,*** ***it sticks with persistence again. It's effectively a death loop. The sysadmin has to remove the Chromebook from their management system to get rid of it (be it Google MDM or JAMF, to name two).***
-
-
+
The MDM is tied to the S/N, and the managed status is persistently stored in NVRAM. The only way it gets removed is a power flush. ***It will eventually be restored once you connect it to the internet. Once it sees it has the MDM tie,*** ***it sticks with persistence again. It's effectively a death loop. The sysadmin has to remove the Chromebook from their management system to get rid of it (be it Google MDM or JAMF, to name two).***
This can't be removed any other way. If the folks with the chops to reverse engineer these (or at least, figure it out) could find a way around it we's know and the method would be somewhat widespread. Ex MDM Chromebooks would be trophies to make the people who doubted it could be done as a way to make them look like fools. I'd even have a shot at a few and preserve the S/N myself to clown the sysadmin at my high school who was a pain.
Tied to the S/N and firmware locked once enrolled at the BIOS level. There's no removing this without the original admin doing it at the Google admin console (or if it's 3rd party like JAMF, JAMF admin).
+
The MDM is tied to the S/N ******and stays in the NVRAM somewhat persistently. The only way it gets removed is a power flush. ***It will eventually be restored once you connect it to the internet. Once it sees it has the MDM tie,*** ***it sticks with persistence again. It's effectively a death loop. The sysadmin has to remove the Chromebook from their management system to get rid of it (be it Google MDM or JAMF, to name two).***
-
This can't be removed any other way. If we could do this without admin getting in the way with a firmware and S/N locked registration, do you not think I'd have some fun with a few cheap "locked" units and retain the original S/N to prove it's doable? You need to change the S/N or motherboard to kill the admin tie (which costs as much as a good one).
+
+
+
This can't be removed any other way. If the folks with the chops to reverse engineer these (or at least, figure it out) could find a way around it we's know and the method would be somewhat widespread. Ex MDM Chromebooks would be trophies to make the people who doubted it could be done as a way to make them look like fools. I'd even have a shot at a few and preserve the S/N myself to clown the sysadmin at my high school who was a pain.
Tied to the S/N and firmware locked once enrolled at the BIOS level. There's no removing this without the original admin doing it at the Google admin console (or if it's 3rd party like JAMF, JAMF admin).
-
This can't be removed any other way. If we could do this without admin getting in the way with a firmware and S/N locked registration, do you not think I'd have some fun with a few cheap "locked" units and retain the original S/N to prove it's doable? You need to change the S/N or motherboard to kill the admin tie.
+
This can't be removed any other way. If we could do this without admin getting in the way with a firmware and S/N locked registration, do you not think I'd have some fun with a few cheap "locked" units and retain the original S/N to prove it's doable? You need to change the S/N or motherboard to kill the admin tie (which costs as much as a good one).
Tied to the S/N and firmware locked once enrolled at the BIOS level. There's no removing this without the original admin doing it at the Google admin console (or if it's 3rd party like JAMF, JAMF admin).
-
This can't be removed any other way. If we could do this without admin getting in the way with a firmware and S/N locked registration, do you not think I'd have some fun with a few cheap "locked" units and retain the S/N to prove it's doable?
+
This can't be removed any other way. If we could do this without admin getting in the way with a firmware and S/N locked registration, do you not think I'd have some fun with a few cheap "locked" units and retain the original S/N to prove it's doable? You need to change the S/N or motherboard to kill the admin tie.
Tied to the S/N and firmware locked once enrolled at the BIOS level. There's no removing this without the original admin doing it at the Google admin console (or if it's 3rd party like JAMF, JAMF admin).
This can't be removed any other way. If we could do this without admin getting in the way with a firmware and S/N locked registration, do you not think I'd have some fun with a few cheap "locked" units and retain the S/N to prove it's doable?