TomHutchinson

Think of it that everyone above have saved you money, because I recon @dhicks would have paid a lot to not have loud bangs, especially if it was anywhere near live production servers. The happy days are when all the flashy lights are still flashing 🙂

If the device is just hitting CMD after starting to load up the scripts, switch to C:, and do a DIR. If there is a folder on there called MININT, try deleting that folder completely, then reboot and try deploying again.

Cheers for the urge.

Hi All, I randomly turned on one of our devices that had stopped working, to find it was working again. Tried another 4 devices... all connect straight to wifi and updated their Google Workspace policies with the changes we've done since they've been off. We never got time to dispose of ours over the summer, but this makes me glad. (p.s. yes I know its not ideal as they are so old, and I'm still pushing management to invest in replacements but clearly this issue was either not Googles intensions or have reversed/fixed what caused them all to stop working abruptly)

I'm fully aware of this, but with funding being hard to get having a device that was still working great in the environment then its a resource that sad to see no longer operate. The point is the way in which it's a hard lock out. Shouldn't have to be EoL just because new OS/firmware is (not*) being released, but a nudge to be unsupported. *edit

I've also now exhausted all lines I thought possible to try (spoke with google, firmware, powerwash, settings, deprovision, custom/other chromeos image) and get round this issue, but it looks like its game over. We have around 200 old Viglen/XMA Chromebook11 devices which, albeit old and 4 years out of updates, still operated. With the age of them, and ones that had no battery replacements, have been great to hand to students to use from home where there was no facilities, all now completely unusable. I'm still waiting for 'further response' after having a chat to someone in Google Workspace Device support, who unfortunately was very shy on speaking about the issue when I said Im aware they are out of update period. They definitely should have had a fall back where you could at least deprovision the device so that after a reimage or powerwash it could see it was released off the Workspace and work solo.

Just a heads up, you appear to be using Google's very old (10 year ish) MX DNS entries, albeit same errors as us all.