Enrollment error

[jasoncrcsd]

We've been getting more and more of these, devices that appear not enrolled and when it tried to auto re-enroll fails, even the manual enrollment fails with the same error. We can powerwash them and fix them but it seems we've been getting a lot of these. Is there any way of telling why this is happening? Have the students found a way of breeaking them?

[panderson]

I wonder if this could be related to the Chrome OS 119 update failing issue?  

[jasoncrcsd]

This one is on ver 119

[zdanenyc]

We had a similar issue and was notified by Google Support that it's a result of devices not being used in a "long time" meaning 3 months or greater as outline below

1.- The devices remained inactive for a while.
2.- Something get stuck from the device itself.
3.- Connectivity issues from your environment or student's environment such as network configuration, low-bandwidth, internet bouncing.

They suggest using the chrome recovery tool to have the device re-enrolled (even though it already shows enrolled in the Google Admin Console)

[jasoncrcsd]

What is the chrome recovery tool?

[Kim_Nilsson]

This nice little thing.

pocpnlppkickgojjlmhdmidojbmbodfm

No, not gibberish. 🙂 It's the ID # for the Chrome extension.

[jasoncrcsd]

Oh, that. Yea we've used that. What I'm trying to find out is what is causing these to unenroll. A powerwash seesm to fix them but its happening more and more. I asked Google supt but they had nothing

[zdanenyc]

I couldn't agree more! I want to know the CAUSE so we can address that rather than providing bandaids. I'm glad I'm not going crazy haha. Thanks JasonCRCSD!

[jasoncrcsd]

Are you seeing this issue too?

[zdanenyc]

Yes. Unfortunately. We have an open ticket with Google Support to address the root cause. Fingers crossed 🙂