New issue
Advanced search Search tips

Issue 904651 link

Starred by 1 user
Status: Assigned
Owner:
drcrash@chromium.org
Cc:
dkalin@google.com
pmarko@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Zero-Touch enrollment should return better error messages when a device isn't pre-provisioned

Project Member Reported by drcrash@google.com, Nov 13 
If a device attempts Zero-Touch but hasn't been pre-provisioned properly (which may happen as the trigger to do ZT and the pre-provisioned information are in different stores), EnrollmentHandlerChromeOS gets an EnrollmentStatus of 2 (https://cs.chromium.org/chromium/src/chrome/browser/chromeos/policy/enrollment_handler_chromeos.cc?rcl=58605429dc978099c398d0d183017e9543a26425&l=827), REGISTRATION_FAILED, but the error diagnosis is IDS_POLICY_DM_STATUS_REQUEST_INVALID which is very generic and doesn't help the user.

Comment 1 by pmarko@chromium.org, Nov 13 

Does it make sense to retry soon in this case? (i.e., would this be a transient server-side race condition where the two stores are not in sync, or would this require admin action to fix on the server?)

Comment 2 by drcrash@google.com, Nov 13 

Such an error is most likely not transient.
►

Sign in to add a comment