New issue
Advanced search Search tips

Issue 835053 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: May 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

Remove Enterprise Management on Chromebook

Reported by standard...@gmail.com, Apr 20 2018

Issue description

Chrome Version: <64.0.3325.181>
Chrome OS Version: <64.0.3325.181: Chrome OS>
Chrome OS Platform: <Acer C720>

Please specify Cr-* of the system to which this bug/feature applies (add
the label below).

Steps To Reproduce:
(1) Enter recovery mode, Esc+Refresh+Power
(2)Follow on-screen instructions to get to "OS Verification Off" Screen
(3)At OS Verification Off screen, restart by pressing Refresh+Power
(4)Plug in recovery media USB to recover Chromebook. Make sure the OS Verification Off warning is shown when the computer checks the media integrity
(5) Wait for recovery process to finish, and unplug the USB to start set up again
(6) Follow on screen setup instructions on Chromebook until Enterprise Enrollment Screen
(7) Repeat steps 1-7 20-30 times, many tries increases likelihood

Expected Result: Forced Enterprise Enrollment

Actual Result: Chance of removal of enrollment, unmanaged computer

How frequently does this problem reproduce? (Always, sometimes, hard to
reproduce?) Sometimes reproduces. 

What is the impact to the user, and is there a workaround? If so, what is
it? This bug causes computers to exit Enterprise Enrollment, even if the admin has enabled forced re-enrollment on Admin Console. 


 
Components: Enterprise>Enrollment
Labels: -Pri-3 Pri-1
Owner: igorcov@chromium.org
It's a bit weird - sounds like in this case the admin has enabled FRE, but has not enabled dev-mode blocking? I'm surprised we allow that case.
The admin has dev mode blocked, but that only protects the computer from
being start up in dev mode. Rebooting while OS Verification off is not
disabled. Also, turn off dev mode before start up after recovery media.
Cc: ibezmenov@chromium.org
Status: WontFix (was: Unconfirmed)
Enterprise Test Team was not able to reproduce the issue, so closing it as "WontFix". Please feel free to reopen this providing more details (debug-logs, etc.).

Sign in to add a comment