Enrolment
38 Topics[Enhancement Request] Allow push notifications during OOBE setup process
Android does not allow any push notifications during the OOBE (out of box experience) setup process. This presents challenges during Intune enrollment because we require users to satisfy MFA (SMS or MS Authenticator) in order to complete Entra AD device registration and device enrollment. The inability to receive push notifications on the new Android they are configuring requires users to configure their MFA on a secondary device before starting the setup of the new device, or obtain a temporary access pass from our Security Team. If OOBE supported push notifications it would resolve this and provide a much simpler and easier enrollment/user experience.2.3KViews3likes4Commentsrequirements for provisioning an app on android 13
I have an app that I designed private for my company .... which gets permissions imei android ID block the use of factory restore unlock OEM unlock lock and unlock screen kiosk mode , and I install it by adb command and work perfect with all devices I have more than 170 devices made in this way and takes a lot of time , I would like to provision my app and placed as device owner through the QR the problem is that I do not know how to do it correctly try many things I saw on the internet , like for example the signed app get the sha256 from the apk and pass it to base64 make the json but I don't understand if I have to configure something else in the app for the provisioning I tried to scan a generated qr with everything correct and it didn't work it says contact your IT support for more information if someone can guide me it would be great, android 12+ a friend sent me some java and kt files for provisioning that worked for him, but for my app it doesn't work. my app has no icon because I need to pass silently and already does but as I say the problem is that I do not know if I am missing a file or a specific configuration I am missing only this and I would be grateful if someone can help complete it or guide me, I saw options like google workspace but I could not modify the block screen to be customized, try with the api google managament android and also does not let you create the company by command then I'm desperate and do not know what to do Thanks for read224Views1like2CommentsMissing Apps in managed Play Store
Hi everyone, I did see in previous posts, that we had a problem with missing apps a year ago. (https://www.androidenterprise.community/t5/general-discussions/fixed-service-announcement-available-work-apps-missing-in/td-p/811) Since yesterday we have a problem, that all optional apps are not visibile in the managed Play store. Our users see only the required apps but not the optional apps or webclips. This happens only for users enrolling a new device. Existing users does not have the problem "yet". Is there anybody else seeing this problem. We use Ivanti EPMM. Kind regards MelkonSolved743Views1like2CommentsBYOD AE Work Profile - Samsung Device with Android 12, 13 - Sharing Serial no/IMEI details with Intune MDM
We are observing, Intune started displaying the Serial no's /IMEI's of Samsung Android 12, 13 device and device type is BYOD -> Work Profile. did you see this in your environment? Model affected are SM-A,G,S,G,M SERIES.3.2KViews1like5CommentsZTE don't enroll the device
Hello, I using ZTE to enroll all of our Android devices into our MDM Meraki. But I've noticed that I have to perform a manual action each time to complete the enrollment : Why ZTE don't enroll automatically the device into my MDM ? Regards, **Code hidden for security reasons2.1KViews1like5CommentsCOPE Enrollment Fails for Single and Multi-Kiosk Mode
Description: We are encountering an issue with the Corporate-Owned, Personally Enabled (COPE) enrollment where single and multi-kiosk mode are not working as expected. This issue has been observed during our deployment and testing phases. Steps to Reproduce: Initiate COPE enrollment on an Android device. Complete the enrollment process. Attempt to configure the device in single or multi-kiosk mode. Expected Behavior: The device should enter the specified kiosk mode (single or multi) without any issues. Actual Behavior: The device fails to switch to single or multi-kiosk mode. Instead, it either remains in its previous state or exhibits unexpected behavior. Android Version:Android 9 and 12 GMS Device Model: Pixel 3a (Android 12 GMS), RT55 (Android 9 GMS) Kiosk Mode Setup: Just add one application in the single kiosk mode, no other setting applied Error Messages: See my screen capture below1.7KViews1like3CommentsAllow only one domain in Work Profile
Hi All, We have registered Android EMM with Managed Play Account (gmail) in Workspace ONE. We use Google Workspace for Google apps like email, calendar etc. I need to allow only adding our domain (mycompany.com) in Google Apps inside Work Profile. Is this possible? If yes, please guide me. PS: We are not registering Android EMM with Google Workspace because the email domain is different from our IDP (Okta). Thanks.2.9KViews1like3CommentsDevice enrollment
Need help and/or feedback. We are looking at rolling out several hundred android devices for ordering purposes over the next year and I am running into an issue getting these devices registered. Running into the issue where it tells me "MAXIMUM NUMBER OF DEVICES ALLOWED TO ENROLL INTO THIS ANDROID ENTERPRISE USER ACCOUNT HAS BEEN REACHED". after look into this I've noticed that the USER ACCOUNT has a limit of 10 devices. Is there another way to add more devices or will I need to create more user accounts?Solved3.5KViews1like6CommentsProvisioning a Android 11 device intended to be in Kiosk Mode
So I have these android 11 tablet devices with no camera and no nfc and I am trying to enroll the device under android management so we can push the singular app we need via managed google play and silently update said device when needed . 1) Do I have to provision the device under fully managed in order to use it in kiosk mode? 2) How do I do this with no camera or NFC?4.9KViews1like7CommentsForce settings on Dedicated devices during enrollment
Hello all, I'm trying to deploy a Dedicated device profile in Microsoft Intune, I created the configuration profiles and the compliance policy with some settings, in specific about PIN creation and complexity, but during the setup users are not asked to enter any PIN, and at the end the device result non-compliant until the PIN is set and is fulfilling the rules I set. Is there by any chance a way to force the PIN creation request during the enrollment phase as happens for user-associated devices? Thanks in advance /Lucius5KViews1like7Comments