EMM

158 Topics

Is there any way to disable Google Play Protect (GPP) from an EMM or to otherwise whitelist apps from scanning?
I am very concerned about the Enhanced GPP features coming soon that are currently being piloted in other regions. https://security.googleblog.com/2023/10/enhanced-google-play-protect-real-time.html This is not a welcome feature whatsoever for the fully managed space where we have business apps written internally that are being installed on business devices, owned by that business. In no way do we want Google sitting in between deciding whether a very legitimate app written internally for an organization should be installed on devices that are purchased and owned by the same organization on fully managed devices. I would like a way to disable GPP completely, or at a minimum whitelist applications from scanning as we don't want Google interfering in the business operations. GPP is a helpful consumer protection features but fully managed devices should have the ability to be opted in or out of the program. Otherwise GPP can incorrectly flag a mission critical app and disable or remove it from a device, thereby bringing down a line-of-business application and an end customers operations. While the intentions of GPP are good, by blocking business apps Google themselves is becoming the malicious actor that GPP is ironically trying. to prevent.
Solved
mattdermody
2 years ago Place General discussions
41KViews
17likes
58Comments
How to set up qr code after factory reset
Ogechiclinton44
3 years ago Place General discussions
29KViews
1like
4Comments
How to register to be a Google Partner?
Dear Community Members, We are considering registering to be a Google Partner. After submitting our application, we were declined without specific reasons. Are there any instructions on Google Partner requirements that we could follow? Any help would be appreciated.
Snowball
2 years ago Place General discussions
18KViews
1like
16Comments
Missing Apps in managed Play Store
We are enrolling devices as corporate-owned with work profile, as well as fully managed devices without work profile. All devices receive a device-based Google-Account via EMM registration on enrollment. Our EMM is Workspace One. The issue started around the end of July. On a few devices many approved apps didn't show up at the frontage catalog in the managed Play Store. The missing apps could still be found via search. After delete app-data for the Play Store the missing apps reappeared. Now a month later the issues seems to be getting worse. The issue is happening on nearly every device. Some devices are even unable to find the missing apps via search, even though they are assigned for that app. Deleting app-data for the Play Store does no longer bring back the missing apps. Even waiting for 24h or longer changes nothing. Sending an install command for a missing app from the EMM console to the devices installs the app without issues but still does not add it to the managed Play Store. Regarding devices, we are mainly using Samsung A-Series with latest patches. I also tested on a Fairphone 4 with Android 12 (August 2023 Patch) and Google Play system update of August 2022 which has the same issue and a Pixel 6a. There were no changes in our environment since that time. The only thing that changed is the security patch level for the devices and the Google Play Services. We are not sure if this is an issue with the devices OS, with the EMM or if Google is having troubles on their side. Can someone relate to this issue or know if and how this can be seen in Android Logcat or maybe other logs?
Solved
TomMuc
3 years ago Place General discussions
11KViews
0likes
9Comments
Assistance Needed: Fetching IMEI Number Programmatically in Android
Dear Android Community, I am currently working on an Android application where I need to fetch the IMEI (International Mobile Equipment Identity) number programmatically. However, I am facing some challenges in implementing this functionality, especially with regards to the latest Android versions and privacy considerations. I am reaching out to seek your expertise and guidance on the best practices to fetch the IMEI number in compliance with the Android security standards. I want to ensure that my application adheres to all the necessary permissions and privacy policies to access this sensitive information. If you have any relevant resources, code examples, or tips on how to retrieve the IMEI number programmatically in Android, I would be extremely grateful for your support.
DeepakChauhan
3 years ago Place General discussions
10KViews
1like
5Comments
Android device enrolment issue - Third party MDM app is not being installed during the sign-in process
Hello Android Enterprise Team, We are experiencing a new issue with our Android device enrolments where the third-party MDM app(CyberArk MDM App) is not being installed during the sign-in process. App is configured in Android Management between our CyberArk tenant and Google domain, and user accounts are configured to do set-up for device owner enrolment. Previous device enrolments are still working as expected, and we first noticed this issue on 13-11-2023. No changes have been made to either the CyberArk configuration/device policy or to Google Admin. This issue is affecting all new Android device enrolments, even across Android versions (Android 10-14 affected). Could you please help to fix this issue? Thanks in advance Error Log: 11-24 14:35:49.411 3842 4105 I Auth : (REDACTED) [BroadcastManager] [BroadcastManager] Broadcasting bad device management=%s 11-24 14:35:49.414 3842 4105 I Auth : [AccountStatusChecker] Error when fetching package info [CONTEXT service_id=343 ] 11-24 14:35:49.414 3842 4105 I Auth : sdq: Invalid package signature for app=com.google.android.apps.work.clouddpc 11-24 14:35:49.414 3842 4105 I Auth : at sdr.c(:com.google.android.gms@234414022@23.44.14 (100400-580326705):190) 11-24 14:35:49.414 3842 4105 I Auth : at sdr.a(:com.google.android.gms@234414022@23.44.14 (100400-580326705):39) 11-24 14:35:49.414 3842 4105 I Auth : at sbq.a(:com.google.android.gms@234414022@23.44.14 (100400-580326705):221) 11-24 14:35:49.414 3842 4105 I Auth : at sbp.p(:com.google.android.gms@234414022@23.44.14 (100400-580326705):34) 11-24 14:35:49.414 3842 4105 I Auth : at sbp.q(:com.google.android.gms@234414022@23.44.14 (100400-580326705):8) 11-24 14:35:49.414 3842 4105 I Auth : at sbp.m(:com.google.android.gms@234414022@23.44.14 (100400-580326705):11) 11-24 14:35:49.414 3842 4105 I Auth : at sss.a(:com.google.android.gms@234414022@23.44.14 (100400-580326705):610) 11-24 14:35:49.414 3842 4105 I Auth : at ssy.b(:com.google.android.gms@234414022@23.44.14 (100400-580326705):94) 11-24 14:35:49.414 3842 4105 I Auth : at ssv.a(:com.google.android.gms@234414022@23.44.14 (100400-580326705):642) 11-24 14:35:49.414 3842 4105 I Auth : at slx.h(:com.google.android.gms@234414022@23.44.14 (100400-580326705):3) 11-24 14:35:49.414 3842 4105 I Auth : at ncu.n(:com.google.android.gms@234414022@23.44.14 (100400-580326705):284) 11-24 14:35:49.414 3842 4105 I Auth : at ncu.c(:com.google.android.gms@234414022@23.44.14 (100400-580326705):1087) 11-24 14:35:49.414 3842 4105 I Auth : at ncu.h(:com.google.android.gms@234414022@23.44.14 (100400-580326705):2) 11-24 14:35:49.414 3842 4105 I Auth : at ncu.fe(:com.google.android.gms@234414022@23.44.14 (100400-580326705):147) 11-24 14:35:49.414 3842 4105 I Auth : at mzt.onTransact(:com.google.android.gms@234414022@23.44.14 (100400-580326705):117) 11-24 14:35:49.414 3842 4105 I Auth : at android.os.Binder.transact(Binder.java:949) 11-24 14:35:49.414 3842 4105 I Auth : at bdrr.onTransact(:com.google.android.gms@234414022@23.44.14 (100400-580326705):10) 11-24 14:35:49.414 3842 4105 I Auth : at android.os.Binder.transact(Binder.java:949) 11-24 14:35:49.414 3842 4105 I Auth : at awwb.onTransact(:com.google.android.gms@234414022@23.44.14 (100400-580326705):147) 11-24 14:35:49.414 3842 4105 I Auth : at android.os.Binder.execTransactInternal(Binder.java:1056) 11-24 14:35:49.414 3842 4105 I Auth : at android.os.Binder.execTransact(Binder.java:1029) 11-24 14:35:49.414 3842 4105 I Auth : Caused by: android.content.pm.PackageManager$NameNotFoundException: com.google.android.apps.work.clouddpc 11-24 14:35:49.414 3842 4105 I Auth : at android.app.ApplicationPackageManager.getPackageInfoAsUser(ApplicationPackageManager.java:275) 11-24 14:35:49.414 3842 4105 I Auth : at android.app.ApplicationPackageManager.getPackageInfo(ApplicationPackageManager.java:244) 11-24 14:35:49.414 3842 4105 I Auth : at akut.e(:com.google.android.gms@234414022@23.44.14 (100400-580326705):7) 11-24 14:35:49.414 3842 4105 I Auth : at sdr.c(:com.google.android.gms@234414022@23.44.14 (100400-580326705):16) 11-24 14:35:49.414 3842 4105 I Auth : ... 20 more 11-24 14:35:49.414 3842 4105 I Auth : [AccountStatusChecker] Canceling DM notification because of DM suppression [CONTEXT service_id=343 ] 11-24 14:35:49.416 3842 4105 W Auth : [GetToken] GetToken failed with status code: ThirdPartyDeviceManagementRequired
mdas86
2 years ago Place General discussions
9.9KViews
0likes
15Comments
Android 15 - Cannot set default password app
We use Microsoft Intune to manage devices. For the devices which have upgraded to Android 15, the end users can no longer select Microsoft Authenticator as their default application for auto filling passwords. I cannot find any settings in Intune to allow it. All devices are fully managed corporate owned devices. The devices are all Google Pixel 8 or 8a devices. Is this a bug in 15 or am I missing something?
tngvmd
2 years ago Place General discussions
9.4KViews
15likes
57Comments
[Community tips] What to consider when choosing an enterprise mobility management solution?
Hello everyone, I hope you are having a good week. A management solution helps you to set up, secure and manage your devices in your organisation. I see it like a comfy hub for you to ensure that your devices are working as you expect (whatever size your company is). So understandably, one of the biggest decisions when getting started with Android at work is choosing the right EMM (Enterprise Mobility Management) for your needs. There is a solution out there to meet almost every need and use case, and sometimes knowing where to start can be tricky. We are lucky here in the community, that many people have already been through this decision and there is a huge amount of experience. The Solutions Directory is a useful place to explore partners and solution options, but there are also many questions and things to consider beforehand, so this got me thinking it would be great to share community tips/advice around this. What tips would you recommend to someone considering and researching EMMs management solutions? Are there any tips you wish you knew at the beginning? Perhaps you have tips on how best to research the different options? If you are currently going through the process, please do comment too, it would be great to hear from you. Looking forward to hearing from you. Thanks so much, Lizzie
Lizzie
2 years ago Place General discussions
9.2KViews
0likes
12Comments
getting 'can't set up device' after getting ready for work setup
I've been trying to enroll my Honor pad x9 using qr code method . But I keep getting stuck after "Getting ready for work setup" I'm new to this and don't have much idea on the topic.
Solved
nazmulhawk
2 years ago Place General discussions
8.8KViews
1like
6Comments
[EMM] My Android EMM Registered account is forced to re-register Android Enterprise.
Hello all, I have my business account registered with Android EMM Registration for about 5 years. About a month ago, there was a problem with API connection with an error message 'UNAUTHENTICATED' reason 'CREDENTIALS_MISSING' which impact on device enrollment and app push service. I have no luck finding ways to fix it and I cannot open any support case with my free account. I decided to reconfigure Android EMM Registration with the same account. Google directed me to newly register enterprise account ended up with same account but different 'Client ID' and 'Google Service Account Email Address'. All my apps in private store and previous managed app are missing. Is there any way to bind my email account back to Google Client ID? so I don't have to separate manage apps and devices on my EMM system. Note When I login to Play Work, I still can see my previous 'Client ID' profile. However, on EMM system, it shows my new client profile. Regards, BKP
BKP1200
2 years ago Place General discussions
6.8KViews
3likes
6Comments