Can't enroll the Samsung to Intune after removing from Google MDM
Hi experts, I'm pretty new to managing Android devices using MDM solution and I went to the issue that need advises. I have a Samsung Android for testing & evaluating the MDM solutions. I was testing on Intune & Google MDM. Here are step by step I have done to lead to this issue. I enrolled it to Intune by using the QR code successfully and finished the first test, then I wiped it fully I added it to corporate-owned device under Google MDM by using csv with serial number Enrolled it to Google MDM and finished the test with MDM. Then, I removed this device from corporate device, deleted it from devices tab from Google MDM and fully wiped (factory reset) this device I scanned the QR code again (the same one I scanned in step 1) but failed After few screens, like connect wifi, this device belongs to org, etc... it ended up with 'Something went wrong, please contact to your IT administartor. I tried to scan it multiple times without luck; other device still be able to scan the QR code for enrollment. There is no logs can be found in the Microsoft. Is there anything that I was missing? Thank you !!!
Android 15 Setup Wizard loops at “Accept Google Services” on Lenovo Tab M11 (TB311FU)
Hi all, I'm running into a blocking issue provisioning brand-new (and factory-reset) Lenovo Tab M11 - TB311FU devices on Android 15 with Android Management API (fully managed / dedicated, kiosk). On Android 14 everything worked fine with the exact same policy and enrollment flow. The issue only started after updating to Android 15. (this is my test device, i constantly factory reset it) Expected behavior: Standard QR (6-tap) provisioning to proceed past the “Accept Google Services” screen, install Android Device Policy, enroll to my enterprise, and apply the kiosk policy, install app, and done. What happens instead: After Wi-Fi and scanning the AMAPI QR token, Setup Wizard reaches “Accept Google Services”. Tapping Accept shows a spinner, then it returns to the same screen (loop). I simply cannot get past this point. If I reboot at this point, on the very first Welcome screen the device sometimes becomes unresponsive (neither 6-tap nor “Next” reacts) until I factory reset again. Is there a known Android 15 Setup Wizard issue that can cause a loop at “Accept Google Services” on Lenovo TB311FU? Any workarounds you'd recommend to get past the acceptance loop? When factory resetting, and setting up the tablet without scanning the qr code, i get past the Google Services no problem. When i install via qr-code on new fresh never used before tablets, that come pre-installed with Android 14, i don't have any issues. Same policy, same everything... except the Android version. Thanks in advance! /B
Bug? G-board removes additional languages post BYOD Enrollment?
We noticed a strange behaviour, If G-board has additional languages added apart from English like Polish or German, post enrolling into a work profile, the additional languages disappear from the keyboard. I was able to reproduce with Intune, WorkspaceOne and even TestDPC app. This is true even if no Device Restrictions are applied. It seems like a bug. Has anyone else seen this issue?
Looking for solutions to assist in Bulk Management (Wipe) of Android Enterprise devices
Hi everyone, I'm turning to the community to see if there are any solutions being used out in the wild that assist with bulk wiping Android devices. I suspect that what I'm asking may not be possible - mainly due to the nature of Android Developer Options, USB Debugging etc. - but I've been I've been tasked by our management to investigate and possibly propose a solution. As an example, we currently use several Cambrionix ThunderSync3 16 port devices to DFU both iOS and macOS devices but they don't offer a similar solution for Android. Are there any solutions that can be used either in tandem with docking stations like Cambrionix or some other. Our use case is Work Managed and we use Omnissa Workspace ONE UEM to manage the devices. The devices themselves are Pixels and Samsungs. and each device is loaded into either the Google Zero Touch Portal or the Samsung Knox Portal. The expectation is that when a large number of Androids are returned for whatever reason, we'd like to be able to plug the device into a "station" and programatically wipe them en masse. Personally, I think we need to simplify our returns process and use the MDM in a controlled environment but I have to have asked these questions, due diligence and all that. Thanks in advance for your input.
Disable random mac address during EMM enrollment
My company is trying to provision tablets via headwind MDM. We have no problem on some of our networks, but the location they are being provisioned at at-scale have a strict no-random-mac address rule on their network. Thus far I have been unable to figure out how to create a QR code that will disable random mac address on the SSID of the network the device connects to when enrolling in our MDM. Is there a field I am missing? Surely there must be a way to overcome this.
