Recent discussions
[Community survey] Feedback on Android Enterprise Secure logs
Hello everyone, I'm a big fan of surveys and we haven't had one for a little while - so here we are! We'd love to hear your feedback on a potential improvement to the Android Enterprise logs. Android Enterprise logs provide critical insights into device activity and security, empowering organizations to manage and secure their mobile ecosystems effectively. These logs are divided into: Security logs, which capture key events like app installations, failed authentications, and policy changes, and Network event logs, which track network activities such as app connections and destinations. Logs are currently stored in the normal world (REE - Rich Execution Environment). We are exploring a feature enhancement to enable this storage in a secure environment (Virtual Machine) so that they are better protected. This feature enhancement has a few options / levels and we want to understand their importance to you: Logs stored in secure environment: If the OS is compromised, the logs are much harder to access and tamper Tamper evident logs: This would allow the OS to indicate if the logs were tampered with Tamper proof logs: This makes it not possible for logs to be tampered with. Logs would only be available in small quantities (4mb on average, depending on chipset capability) If you have a spare moment, please take the short survey below. If you have any additional questions, please to reply to this topic below (by clicking 'Reply'). Thank you for your time and feedback. Lizzie (and the Customer Community team)
New devices only receive "Enterprise Default Profile" instead of default profile
Hey there, this is my first post here as I could not find a ticket system for Zero Touch. Since a couple of weeks all new devices only getting the "Enterprise Default Profile" automatically assigned which I deleted during zero touch tenant setup in "Configurations". The default profile I created does not get automatically applied anymore. Unfortunately I can change the default assignment profile to whatever I want but newly added devices still are getting the "Enterprise Default Profile". Changing the device profile after the initial upload (including wrong DPC info) to the created target profile works in bulk. Once changed manually the devices apply the correct DPC. Multiple zero touch instances are affected. How to fix the default assignment profile for newly added devices? Any suggestions?
How to set policy through my emm in zero touch enable devices?
I have integrated zero touch iframe in my emm console and able to link zero touch customer account succesfully. My query is after linking the customer account and set configuration how to set policy to these devices like app push and system settings configuration through my emm console. Thanks in advance.
How to Handle Delisted Apps in Google EMM During or After Device Provisioning?
Hi everyone, We’re facing an issue where managed Android devices get stuck, preventing app installations when an app included in a policy is delisted from the Play Store. For example, we had the package “com.Xplayer” in a device policy, but when calling Products: get, it returned: “googleapi: Error 404: No product was found for the given ID., notFound.” However, this app was available earlier, and despite its removal, using the Devices: update API still updates the policy without any error or warning. Additionally, there’s a possibility that an app is present on the Play Store when it is approved and added to the policy but later gets removed or delisted by Google. This could lead to installation failures and devices getting stuck. Has anyone encountered this before? How can we prevent devices from getting stuck when an app is delisted? Does EMM automatically remove such apps from policies, or do we need to handle it manually by checking each package ID? Is there any way to get notified when an app is removed from the Play Store? Without a proactive mechanism, devices remain in a stuck state, making large-scale device management challenging. Any insights or best practices would be greatly appreciated! Thanks!Issue with G Suite Apps Being Marked as Disabled in Play Store
Hi everyone, We are facing an issue where G Suite apps like Google Sheets, Google Drive, and Google Docs are installed on our managed devices, but when we check them in the Google Play Store, they appear as disabled. In some cases, the apps are randomly disabled, requiring manual re-enabling. We have verified: Google Device Policy settings Apps are approved and allowed in the managed Play Store Despite these checks, the issue persists across multiple devices with G Suite apps. Has anyone else experienced this issue? If so, do you know of any workarounds or if there is an ongoing Google-side issue causing this? For reference, I have attached a screenshot showing the issue. Looking forward to insights from the community! Thanks, Rupesh
Problem Joining Work Profile From Android Device
I created an enrollment token for an enterprise for work profile, and I ensured that setAllowPersonalUsage("PERSONAL_USAGE_ALLOWED"); was set for the token. How ever when I try to join from my android 11(tecno) and android 14(google pixel 7) device with work profile via the ADP app, I get : Can't add work Profile A work profile can't be added to this Pixel. If you have questions, contact your IT admin. However from my emulator device running Android 15, I could join the enterprise using work profile.
Managed Play Store Web App Fullscreen not working anymore
Hi, We've been using a Managed Play Store Web App set to "Fullscreen" deployed to Samsung Galaxy Tabs using Knox / Intune for a couple of years now. Running in Corporate Dedicated / KIOSK mode Multi App (to have QuickSupport available as well). Recently we're seeing devices (a pattern emerges of this applying to all freshly rolled out devices, although we've seen it on ~5% of older devices as well) where the Web App doesn't open up in full screen mode anymore. No redirects are happening and all content is being loaded from the Web App URL (meaning no external calls). What should we chase next in troubleshooting?Sporadic problems with Managed Google Play after enrollment
Hi! We had problems with a few devices after enrollment today. The Managed Play Store did not work properly. Restarting and waiting seems to help. Symptoms Empty collection in Managed Google Play Spaceship error, because supposedly no apps were made available Installation commands from the UEM did not work in some cases Apps assigned in UEM cannot be found in Play I was only able to reproduce the problem in one of 3 attempts. A few automatic app installations worked for me. However, it was not possible to search for the apps manually. Restarting the device and then waiting a while seems to help. However, a colleague had a strange error in Managed Google Play after a restart when he tried to install an app manually. "The item you want to buy could not be found." However, it is not a purchased app or an app with in-app purchases. Is anyone else currently having problems with Managed Google Play?
