Another customer reports similar issue with Asuka devices, case 17215590

Case owner for 17215590, the customer reported that in addition to happening with Asuka devices, it's also happening with Chrome OS 69 Acer Chromebooks.

poromov, who shall have a look here?

+Yves to clarify current server-side behavior

I think the client side is behaving as expected, receiving the "force re-enrollment" signal (not automatic re-enrollment) and acting upon it.

However, IIRC we may have stopped (parts of) auto-enrollment server-side as a response to issues with attestation which were suspected to be related. Yves, is that the case or am I confusing things?

Yes, AFAIK Yves disabled the auto-re-enrollment on server side for now.

Hello team,

I would just like a clarification about auto-enrollment being disabled on the server side. Is it disabled globally? Because I have a customer telling me other schools in his district have auto-enrollment working at the moment.

It is disabled globally except for some test domains. None of those should
be schools. Can you ask for the domain of the school, and if you can a
picture from a device showing the auto re-enrollment confirmation screen
(or whatever you think you can ask them to make sure they are not confused
about auto re-enrollment being on).

On Tue, Oct 30, 2018, 22:48 mventura via monorail <
monorail+v2.811859063@chromium.org wrote:

See #9

Our district looks forward to this feature working. It will save us tons of time. Students have discovered how to power wash and we have to go out to the school site and connect the Chromebook to the network and then enroll just to have the student to get back into the Chromebook. :-)