Seeking help - New Android Enterpise - Device Owned - Deployment for Samsung Galaxy A9+

[NickDickerson]

Greetings Community,

I am hoping to get some help with my MDM/System Manager deployment for some tablets I recently acquired.

Tablet: Samsung Galaxy A9+ (Android 13, I believe)

Goal: Lock my tablet down to only be allowed to use Chrome on a specific website (my ERP system).

Trying to follow this guide

https://documentation.meraki.com/SM/Deployment_Guides/Android_Enterprise_Deployment_Guide

Verified that I meet the requirements.

My MDM has an active Android Enterprise account enrolled as "Meraki Managed Deployment" and assigned a Gmail account as the admin email.

On the very first screen, having tapped said screen 6 times to scan the complex QR code, the device doesn't do anything. I tested scanning the standard QR code, and it gave me an error saying it's not the correct code, so at least I know the camera is trying to scan. I even printed the complex QR code, thinking that would help, but alas, it did not.

I have since gone through the guide a couple of times and can only get the work profile / BYOD to work (it allows too much freedom to the device and isn't a viable solution for my environment. I have also noticed the guide doesn't quite follow what I'm seeing on my device, and I may be using the wrong guide...although all references lead me back to the link above. The madness of a guide referencing itself is amusing.

I am currently stuck trying to get the new devices added, but I am unable to do so. I have a case open but really haven't gotten anywhere yet. I was hoping maybe someone could help point me in the right direction.

-Nick

[PaulF · Accepted solution]

Hi Nick

Obviously, being on Android 13 may pose a few challenges, but we have some options

The first would be to try and enroll AFTER the device has been set up, but NOT using work profile.

This can be achieved by following the instructions here: https://documentation.meraki.com/SM/Device_Enrollment/Enabling_Device_Owner_Mode_using_Android_Debug...

It involves setting the device up as a regular device, enabling developer options, then enabling USB diagnostics, that then allows you to use ADB

This will get you up and running and able to test out your requirements.

Speaking of which, https://community.meraki.com/t5/Mobile-Device-Management/Urgent-need-Zebra-CC6000-on-Android-Lock-to... will be really helpful in testing out managed chrome vs web clips to access you ERP

Paul

[KFoster]

Hi Nick,

We've had a rough time with scanning the QR codes with the A9+ devices. The camera seems to be of a lesser quality and as such has a wicked hard time of reading it. The old QR code (which is no longer supported) scans immediately though. 

I ended up going the automatic route using zero touch provisioning, which has made life much better.

[NickDickerson]

Howdy Fellas,

Thank you for the information.  I'm going to spend some time this afternoon and work through your suggestions. I greatly appreciate the input as I was going insane yesterday hahah. 

-Nick

[NickDickerson]

TIL - ADB tools

Got the device set into the "device owner" mode. Logged in as my user to system manager with green check marks on all the items.  I am however unable to see the tablet in my devices menu.  I believe it has a license assigned to it (I'm testing with 2 devices so I am using 2 of 2 licenses). I'll see if I can figure out how to verify the license between the device and MDM.  I must be missing something simple. 🙂

[NickDickerson]

I was able to track the device down by going System Manager > Configure > tags > enrollment type > Android fully managed.  I have a tag I've been using for the tablets and noticed it was missing.  This didn't solve the device being absent from the System Manager > Monitor > devices, but at least I was able to find it.