Device owner enrolment not working for Android 12Solved

Participant
Discussion
3 years ago

Hi, Hexnode!

Recently we decided to add a new line of devices to our kiosk line-up, all running the latest update. However, we are facing an issue with device owner enrolment using QR codes. We received an error that says you can’t set up the device and contact the IT admin for help. This issue seems specific to Android 12 devices since we tried updating one of our old devices and enrolling it again, but it did not work. Is this a known issue with fixes?

 

Replies (4)

Marked SolutionPending Review
Participant
3 years ago
Marked SolutionPending Review

We had the same issue… If it is a known issue, we should have been given an update by now. The Android 12 update has been out for a while now… A lot of people are counting on this!

Marked SolutionPending Review
Participant
3 years ago
Marked SolutionPending Review

Found something that matches your case here: https://docs.microsoft.com/en-us/answers/questions/613506/android-12-pixel-6-pro-enrolment-failure-with-39us.html

 

Found something similar on reddit: https://www.reddit.com/r/meraki/comments/s38ub3/device_owner_issues_with_android_12/

Seems like enrolling with ADB is a solid workaround for now. But without a solid fix, it is going to be a headache to manage so many devices.

Device Owner issues with Android 12
byu/michaewlewis inmeraki

Marked SolutionPending Review
Hexnode Expert
3 years ago
Marked SolutionPending Review

Hi all!

Thank you for using Hexnode Connect!

This bug was specific to the new Android 12 update, about which we notified Google. It seems as if the issue has been fixed. Both QR code enrolment and afw# methods should work fine now.

Refer to this forum if you face any issues with the afw method:

Please feel free to reach out to us in case of any hiccups.

Regards
Ethan Miller
Hexnode UEM

Marked SolutionPending Review
Participant
2 years ago
Marked SolutionPending Review

Hey @William , have you tried the other methods of enrolment, does afw#hexnodemdm work on your device, I faced a similar issue, and this worked for me…