Thanks for being the first to demonstrate the new Android Device Staging enrolment on UA-cam. I got to test out the new enrolment method this week since it was announced. I tested the enrolment on Android Enterprise Corporate-owned fully managed. However, I observed an issue with the PIN code setup during testing. Current Behaviour: • Users do not receive a prompt to set up a device PIN code after completing device registration. • Intune marks the device as non-compliant and emails the user to set up a PIN code. Desired Behaviour: • The process should prompt users to set up a PIN code either before or immediately after device registration. Observations: • There is no notification prompt for PIN code setup when users sign in to the Intune app to complete device registration. • The prompt only appears after the device syncs with Intune and undergoes a compliance policy check. • This approach is not user-friendly and could pose a security risk if a device is left unprotected without a PIN code. Have you noticed that yet?
Exactly the same experience here. Big down side with regards to forcing the user to set a pin. That will unfortunately cause more help desk tickets. Another thing I struggled to get fully deployed during the staging was the MS Launcher. All policies and profiles relating to the launcher were device assigned, but I just couldn't get the launcher to be the default home screen during the staging. This led to a less than perfect user experience, receiving a phone without company branding and without a customised home screen until a few mins after they sign into Intune Company Portal. Missed opportunity to give a really smooth user experience.
Thanks for video, do you know if this is compatible with Google Zero Touch? It's a shame the user enrollment stage isn't slightly more simple, I'm not sure our end users would be able to figure this out on their own (especially being that they sign into 'Intune' rather than 'Company Portal' which they are used to). I will give this a try with a small group of users.
Thanks for being the first to demonstrate the new Android Device Staging enrolment on UA-cam. I got to test out the new enrolment method this week since it was announced. I tested the enrolment on Android Enterprise Corporate-owned fully managed.
However, I observed an issue with the PIN code setup during testing.
Current Behaviour:
• Users do not receive a prompt to set up a device PIN code after completing device registration.
• Intune marks the device as non-compliant and emails the user to set up a PIN code.
Desired Behaviour:
• The process should prompt users to set up a PIN code either before or immediately after device registration.
Observations:
• There is no notification prompt for PIN code setup when users sign in to the Intune app to complete device registration.
• The prompt only appears after the device syncs with Intune and undergoes a compliance policy check.
• This approach is not user-friendly and could pose a security risk if a device is left unprotected without a PIN code.
Have you noticed that yet?
Exactly the same experience here. Big down side with regards to forcing the user to set a pin. That will unfortunately cause more help desk tickets.
Another thing I struggled to get fully deployed during the staging was the MS Launcher. All policies and profiles relating to the launcher were device assigned, but I just couldn't get the launcher to be the default home screen during the staging. This led to a less than perfect user experience, receiving a phone without company branding and without a customised home screen until a few mins after they sign into Intune Company Portal. Missed opportunity to give a really smooth user experience.
Thanks good feedback
@@ScottdMest looks like I'll be sticking with the old method until Google/Intune figure out a better way to deploy the policies correctly
Am going to look into this issues
Also, the sign-in to the intune app should be forced without anyway to bypass otherwise some will just never sign in
Thanks for sharing the knowledge ❤
Thanks for the video, it was helpful. What virtualisation software did you use for the Android? Or was that just a remote tool?
Thanks for video, do you know if this is compatible with Google Zero Touch? It's a shame the user enrollment stage isn't slightly more simple, I'm not sure our end users would be able to figure this out on their own (especially being that they sign into 'Intune' rather than 'Company Portal' which they are used to). I will give this a try with a small group of users.
I’m guessing they will be 2 different enrolment options as G zero touch is there to simplify the whole enrolment experience, but worth looking into 👍