Hey everyone, I’m posting this on behalf of our admin team because we’ve hit a blocker while enrolling Samsung devices as Profile Owner using Android Enterprise.
Here’s what’s happening in our setup:
We’re enforcing authentication using Google Workspace during enrollment. The flow starts off fine — we install Hexnode for Work, scan the Profile Owner QR code, sign in with Google credentials, and even complete the work account creation and accept the terms.
But right after that, the device suddenly asks for Google authentication again. When we re-enter the same credentials, the enrollment fails with an error saying:
“This account already exists on your device.”
A couple of things we’ve already verified:
- Android Enterprise is properly configured with our Google domain
- Enrollment works without authentication
- It also works if we enforce authentication using local users with Google credentials
The issue only shows up when Google Workspace authentication is enforced. At the moment, this is blocking us from rolling out Android Enterprise under our domain. Has anyone seen this before?
11 Views
