Chrombeook Management: New Forced Re-Enrollment device policy feature

WOO WHOOO!

Taken straight from an email I received..not sure of a link that states this to direct people to.


New Forced Re-Enrollment device policy feature
Shortly after the release of Chrome OS v35 in the coming weeks, we’re also updating the device re-enrollment process with a new Forced Re-Enrollment device policy. This new feature is a more robust way to ensure that wiped or recovered devices remain managed when they’re distributed to users.

With Forced Re-Enrollment, users will be required to re-enroll into the specific domain that previously managed that device. Until they’ve completed re-enrollment, they won’t be able to use the device, which includes browsing in guest mode and accessing the sign-in page. The existing auto-enrollment feature for wiped devices—where users enroll the device the same time they sign in—will be replaced by this new Forced Re-Enrollment policy in v35.

Note: If your devices were enrolled before the Chrome OS v35 update, they won't automatically have the new Forced Re-Enrollment feature. The next Chrome OS release (v36, approximately 6 weeks after the v35 release) will apply Forced Re-Enrollment as the default for all devices, no matter when they were enrolled. However, if you’d like to use Forced Re-Enrollment on your existing enrolled devices before the v36 release, you can wipe and manually re-enroll your domain’s devices after updating to v35. Visit the Chrome Releases blog for more information about this feature as we approach the release of v35.