Featured Content
Recent discussions
Ability to block Chrome dinosaur game on Android
I'm looking for a way to block the dinosaur game in chrome on Android. I see the AllowDinosaurEasterEgg managed configuration but that is only for desktop Chrome. Are there any plans to implement this for Android? Is there another way to achieve this? This is a high priority request from our customer to the point where we see the only solution is to switch browsers. Thank YouSolvedjverlinden9 days agoLevel 1.6: Donut134Views1like10CommentsEMM Bind Credentials Lost
I work for an MSP. We have taken on a new customer that has lost the password for their EMM Bind account (EMM is Intune). Has anyone else been through a recover process for this and have any advice? The have approx 200 devices enrolled, so we can't risk them having to be enrolled.Solvedsambenenge16 days agoLevel 1.5: Cupcake50Views0likes3CommentsWhat happned if the device used for personal usage although it is in zero touch portal and emm bind? Is it illigal based on google policy?
I have some customer who uses my EMM console integrated with Zero touch services. Some of his previous used device added in zero touch portal but not activate the device as enterprise device that means not enroll in emm portal. Rather using the devices as personal.Is it violate the google zero touch policy?Solvedmhfaruk26 days agoLevel 2.0: Eclair61Views0likes5CommentsCan't add a private app to devices
I'm being very confused when trying to add a private app into the Stix EMM, and I'm not sure where the problem lies, so I'm asking here! I successfully loaded it in: But when I then click on that and then try to click Select app... nothing happens. Nothing on screen, nothing in the dev console, no network traffic... Nothing. And so I can't add this app to my devices. And I'm entirely lost as to what's going on. Is this a Stix thing? Or an Android Enterprise thing?Solvedsimon_tikpay2 months agoLevel 1.6: Donut105Views0likes11CommentsManaged Play Store keeps asking for Google Play services Update
Hey! I noticed a little bug today and wanted to ask if anyone else is experiencing this. With the update to Play Store 46.1.37-31 [0] [PR] 755161904, a push message informs you that Google Play Services must be updated. With a COPE device, this only occurs in the work profile. Even if Google Play Services is updated to the latest version (25.18.33 (190400-756823100)), the message appears as soon as you open the Managed Play Store. Lizzie Is there anything known here? The Managed Play Store works normally despite the warning in the push message. I would also have logs if required.SolvedAlex_Muc2 months agoLevel 3.0: Honeycomb1.7KViews4likes44CommentsManaged configuration to Gboard has disappeared from MDM
The ability to apply a managed configuration to Gbaord has disappeared. We think this is due to a recent change to the Gboard app where Google has removed this ability. Environment: MDM = Omnissa Workspace One UEM (we are also hearing reports of this impacting SOTI customers as well) Rugged Zebra Mobile devices, majority running either A11 or A13 Leads: Managed App configs are still present on Chrome & ServiceNow Now Agent, hence why we believe this is not an MDM Console issue. We have escalated to Omnissa support anyway, who have in turn escalated to Google. Is anyone else seeing this issue?Solvedbadams12 months agoLevel 1.6: Donut699Views3likes30CommentsSetup using another device wizard screen removal
Is there a way to skip the "setup using another device" wizard screen? We don't see the benefit of showing up this option, on company environment, having MDM managed devices with Zero touch enrollment setup. That screen is specifically, the 3rd screen, when setting up a new device, after selecting the language and the insert SIM card instrucctions screens. As those screens are right before the Network setup screen the device won't be able to connect with Google services to get MDM server and the custom profile, so not sure how to disable it? ThanksSolvedagonzaleze2 months agoLevel 1.5: Cupcake72Views0likes5CommentsDevices not receiving managed configuration after enrollment
My team uses Android Management API to manage our enterprise's devices. Our management policy includes managed configurations for our Kiosk application, in order to correctly enroll our devices into our services. If this is not done, device provisioning fails. Over the past few months (first report we received was on January 13th), we have observed that certain devices are failing to receive the managed configurations, and thus fail to go through the process correctly. They fail to receive configurations on a policy change as well, which affects our existing devices. Before, removing the devices from our policies and enrolling again would succeed in sending the managed configurations to the affected devices. However, this issue is now persisting across attempts and happening more frequently. We have devices affected on both Android 13 and 14.Solvedltejada3 months agoLevel 1.5: Cupcake100Views0likes2CommentsUnable to add additional owners and administrators to Manage Google Play Store
We recently disconnected our Managed Google Play account from Intune, which was initially set up with a standard Google Account. Now, we are reconnecting Intune to our Managed Google Play account using a Managed Google account that is synchronized with our Entra ID SSO. This means we can sign in with our company domain (@mycompany.com) using our Entra ID password. We are able to enroll our Android phones into Android Enterprise and publish apps to our Managed Google Play store without issues. To ensure redundancy, Google highly recommends creating a secondary owner account in case the primary account is compromised. See Google KB . I'm following the guide on assigning roles in enterprises from the Managed Google Play Help. However, my Play Store account admin screen appears quite limited compared to what I should be seeing. Here’s a screenshot of my current view: Previously, when we used a personal Google account for our Managed Google Play Store, I could invite other users to become owners. This option seems to be missing since we switched to the managed account. Could there be additional permissions in the Google Workspace admin portal that we need to grant to the Managed Google Play account to enable the option to add additional owners?Solved162Views0likes4CommentsPrivate app shared with partner organization cannot be onboarded in their UEM solution.
I have added a private app to our managed play store (MS Intune) and followed the steps documented in Distribute private apps to make this available to a partner organization but unfortunately when they attempt to add the app to their UEM solution (Omnissa Workspace ONE) by play store URL they receive a http 404 response and cannot proceed. We have shared an app with them previously (same app, different productFlavor with app id suffix) and that worked seamlessly so we are bit stumped. Reaching out to our respective vendors has not been fruitful so it's not entirely clear what to do next, would appreciate any advice you have!Solvedecpaul3 months agoLevel 1.6: Donut176Views0likes6Comments
Explore other customer resources
Help Center
Explore step-by-step how-to guides.
Solutions Directory
Find solutions and partners.
Website
Discover more about Android's features.