COPE Enrollment Fails for Single and Multi-Kiosk Mode
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-26-2024 07:19 AM
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 below
- Labels:
-
Apps
-
Enrolment
-
Work Profile
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-26-2024 07:21 AM
testing result
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-27-2024 12:04 AM - edited 06-27-2024 12:19 AM
I think this is more an expected behavior than an issue.
On our MDM we don't have the possibility to set up a kiosk for a COPE device (even doesn't make sense in my opinion). You may look more likely into COBO (fully managed) device enrollment.
COPE (Company owned privately enabled) is for having a private part, free to use by enduser, on the device with more manage functionalitys for the admin than on a BYOD (Bring your own device) device but in general same environment. So a kiosk mode here won't make sense.
A COBO (Company owned business only = fully managed) device will be able to be used as a kiosk device as in this case it may make sense because those devices are used only for business use without personal data part.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-10-2024 07:52 AM
@Moombas Thanks for your response. It was really helpful
- Zero-Touch is unavailable in General discussions
- eSIM setup during device enrolment in General discussions
- Managed Google Play Android enrollment by intune.microsoft.com in General discussions
- Samsung devices getting stuck during enrolment when using zero-touch or QR in Germany in General discussions
- Enroll Device Using Qr Code in General discussions