Recent discussions
Need Help with QR Enrollment for Multiple Devices in Educational Environment – Is External MDM Required?
Hi everyone, I'm managing a large number of Android tablets in an educational environment. I'm trying to enroll the devices using Android Enterprise with QR code enrollment, but I'm having trouble getting the QR method to appear. So far, only Zero-Touch shows as an option, but most of our devices were not purchased through Zero-Touch resellers, so we can't use that method. My main question is: Is it strictly necessary to use an external MDM (like Miradore, Intune, etc.) to generate the QR code, or is there a way to create and use it directly from the Google Admin console or natively through Android Enterprise? We want to deploy the tablets efficiently and avoid entering accounts manually. Ideally, each device would automatically enroll with our managed Google Play account by scanning a QR code after a factory reset. This is especially important in a school context, where we have many students and limited time for configuration. We are already registered in Google Workspace, and the tablets are in a dedicated organizational unit for students. The admin account is managed, and we are using the Android Enterprise platform linked to our domain. For reference, here are two YouTube videos showing the configuration steps I followed (which reflect our current setup): https://www.youtube.com/watch?v=jI-C_y1u8jE https://www.youtube.com/watch?v=h__pvfp559Q Any advice or clarification would be greatly appreciated. Especially if there’s a native way to enable QR enrollment without needing a full external MDM platform. Thanks in advance!OTA cache host is down
Hello peeps I fancied running automated network connectivity checks in one of my apps. Pulled in the list from the Devices category of network requirements and it looks like one of the OTA cache servers has been down for at least a week. ota-cache2.googlezip.net I raised it quietly but figured it was worth calling out here also.
Zero Touch Portal - Error Message
Hi Team, I have created a new configuration item and linked it to Microsoft Intune token. Then I have decided to remove the Intune token configuration before removing the configuration file from Zero touch (which I dont think it should matter). Then I went to remove the configuration item from Zero touch and was getting a strange error message, see below. Now I'm left with a configuration item in Zero touch that I can't remove. Can someone please help or reach out, that would be great. Also, let me know if there is anything else you require from my end.No Response After Submitting Android Enterprise Contact Form
Dear Android Enterprise Team and Community, I hope you're doing well. I submitted the “Get in touch” form on the Android Enterprise website and received the confirmation email on May 30, which I have already responded to. However, I haven’t received any follow-up or contact from a specialist since then. We are exploring Android Enterprise solutions for our business and are interested in understanding the next steps to get started. Could someone from the team or community please assist or guide me on how to proceed? If additional information is required from my side, I’d be happy to provide it. Thank you for your support. Best regards, Deepak Alobha Technologies Pvt Ltd (This post was edited to remove personal information, in compliance with our guidelines)Managed Google Play Collections
The Managed Play Store and the Google Play iFrame play a major role in Android Enterprise Management and the Collections are important for managing and displaying apps in the Managed Store. Basically, the collections work well, but I also see room for improvement there. These would not only be useful for admins, but also for users. But first a step back: There are two different layouts: Basic and Custom. A collection (or ‘cluster’) can have up to 100 apps. Basic is a single collection Custom allows up to 30 collections Easier sorting in the iFrame The apps are sorted in the iFrame using arrows next to the app icons. Especially with large collections, it becomes a task of patience when an app has to be sorted to the back. A drag & drop feature would make customisation much more convenient. Backup / restore of collections A restore function for collections was asked for in another topic. In addition to ‘edit’, ‘delete’ and ‘duplicate’, “export” and ‘import’ would also be useful in the iFrame. (see above screenshot) Collections could be backed up and restored in this way. Be it to have only one backup, to configure a collection in a test environment exactly as in the production environment or to design a collection externally with tools and then upload it. (e.g. manual customisation of the json data of a backup) More variation for collections in the custom layout In the ‘Custom’ store layout, the collections are displayed one below the other. The mixture of vertical (between the collections) and horizontal (within the collection) scrolling can become somewhat confusing. In addition, you cannot recognise at first glance whether it is a very large or rather small collection, as usually only 3 apps are displayed. As long as you don't have many apps, the basic store layout is often much cleaner. It could therefore be useful to define a number of (app) lines per collection that are displayed in the MGP. (with 1 line as default) Or an option where a collection is displayed completely in MGP instead of scrolling sideways. There are different types of collections in the normal Google Play Store. It would be useful to be able to choose between the different variants. (See ‘Popular apps’ / Business tools") Do you have any other ideas and suggestions for MGP Collections? 😃Does anyone allow multiple users on their Androids?
I've got a use case for some multi-user Android tablets and I'm trying to figure out the best solution. I know Android allows you to create secondary users by default but it appears that Microsoft Intune is disabling this setting automatically. Doesn't seem to be a way to allow it given that the only options are block or not configured. I put in a ticket with Microsoft and I'm sure their answer will be to use Microsoft Entra Shared Mode and the Managed Home Screen but that doesn't work very well. Also, it appears multi-user functionality is documented by Google and an EMM can set it up so the user can create secondary users using the standard Android settings or the DPC can create the secondary user. Also looks like there's some work to be done as far as making sure the DPC can still manage the secondary users as well. https://developer.android.com/work/dpc/dedicated-devices/multiple-users So I am curious for those using other EMMs: do you allow secondary users on any of your Android devices?
MDM configuration became lost
A few years ago we added an MDM configuration to our app, according to the straightforward guide Setup managed configuration Previous month we released a new 15.0.0 version of our app, IQ SmartApp Enterprise Besides other changes, in this release we removed one option from the MDM configuration XML, a deprecated boolean parameter. Indeed the XML validity wasn't broken, no related changes in the app Manifest or so on. However our customers started to complain, that app lost the ability to configure MDM parameters. Also, when adding the app to Approved list on MDM Solutions (we checked on HMD and TinyMDM), in the app details was lost a badge "Tis app offers managed configuration". If download AAB and/or APK from Google Play Console and unpack them, or open them in Android Studio, the required Android Manifest parameter "android.content.APP_RESTRICTIONS" is present and pints to MDM XML config file which is also present in the AAB or APK. If check the APK, taken from Google Play Console, locally with TestDPC app, the managed configuration is also present. Can you please help to understand, what's going on? As for me, removing one of the MDM parameter from the managed configuration config shouldn't be a reason of disappearing the whole managed configuration. Which is actually present in the AAB or APK builds.
getting ready for work setup get the issue of something went wrong your app cannot become device owner by the qr code provisison by json in android
i am facing the issue in android 14 or 15 when ever i build the unsigned build it work fine for the android 13 after that it give the error like something went wrong please contact to the it admin and i am build the singed build it give error for the checksum error cannot setup but same thing if i make my app as a device owner by adb command it work fine for me let me know how to fix this issue? i try to replace the checksum and i match both checksum both are same it getting error for me why? below is my mention qr code json, {"android.app.extra.PROVISIONING_DEVICE_ADMIN_COMPONENT_NAME": "com.abc.abc/com.abc.abc.utils.receiver.MyDeviceAdminReceiver", "android.app.extra.PROVISIONING_DEVICE_ADMIN_SIGNATURE_CHECKSUM": "F-EJlegNKdVupdJupPmWz34s2INjWVUDS5ErL-DuETc=", "android.app.extra.PROVISIONING_DEVICE_ADMIN_PACKAGE_DOWNLOAD_LOCATION": "https://downloadapk", "android.app.extra.PROVISIONING_LEAVE_ALL_SYSTEM_APPS_ENABLED": true}
"This item isn't available in your country" showing on isolated apps on isolated devices.
All of a sudden I'm having issues installing apps through Managed Play on isolated devices. When navigating to the app directly I can see "This item isn't available in your country." The devices are in the US. Location services confirms this, the external device IP is also US based as well. I have cleared cache and app storage of Google Play and Google Play Services. I have upgraded Google Play Services. The devices are fully managed with manage service accounts. I have reset the account assigned to the device. I have tried to set the Country manually in Google Play setting but am unable to do so. It does not show a current country. I also see an option for "Switch to the United States Play Store" but tapping on it doesn't do anything. Any ideas or suggestions here?OEM Unlock toggle not available
Hi all, Recently joined the community, first time poster here. TL;DR at the bottom. Hopefully my question has a simple solution but I've looked everywhere (except here of course). I'll try to keep this as simple as possible. Everything is in UAT if that matters. The important bits: Pixel 8a Build BP1A.250505.005.B1 No SIM or eSIM Android Enterprise registered to my UAT Tenant I'm testing some scenarios for automating device compliance with Omnissa using Workspace ONE Intelligence. To test this successfully I'm going to need to flash back to an older Build and probably more than once for demo purposes. The OEM Unlock toggle is not available however, and I this is preventing me from doing my testing. I've read conflicting posts elsewhere regarding carrier unlock, SIM and/or eSIM etc. ADB is working fine but flashing older images is just not working. Any help from the community on how to get OEM unlock enabled would be greatly appreciated. TL;DR: Need to flash a pre 250505 build to my Pixel 8a. Can't toggle OEM unlock as it's greyed out.
