We appear to have an issue with Xiaomi devices that are enrolled through a UEM and Android Enterprise. The issue is that our app requires a VPN to be automatically started when the device is rebooted which does not occur. Users are forced to open the app to get the VPN started.
We have some performed extensive testing and determined that this issue only appears on devices that have more than one profile present (e.g. COPE) and we have noticed this consistent behaviour with different UEMs, namely Microsoft Intune and VMWare Workspace One. Additionally, we believe that this is not an issue when there is a single profile on the device (e.g. COBO). We have been able to identify this as exclusively a Xiaomi issue having tested this on a Xiaomi Redmi Note 7, other OEMs appear not to have this issue.
Are there any known issues with VPN autostart permissions when a device is deployed through Android Enterprise with multiple profiles?
Does anyone know whether this can be resolved?
We have some performed extensive testing and determined that this issue only appears on devices that have more than one profile present (e.g. COPE) and we have noticed this consistent behaviour with different UEMs, namely Microsoft Intune and VMWare Workspace One. Additionally, we believe that this is not an issue when there is a single profile on the device (e.g. COBO). We have been able to identify this as exclusively a Xiaomi issue having tested this on a Xiaomi Redmi Note 7, other OEMs appear not to have this issue.
Are there any known issues with VPN autostart permissions when a device is deployed through Android Enterprise with multiple profiles?
Does anyone know whether this can be resolved?
Last edited:
