Jan 30 2019 01:39 PM
Jan 30 2019 01:39 PM
We have many users that want to purchase Huawei as a preferred personal phone in our company, and i have recently purchased a P20 Pro with Android 8.1 to test in my environment for Android Work Profile.
Now i have configured everything after specs, with managed google play and approved what needs to be approved, but attempting to enroll the device, it stops at the "Halfway there" page, and then nothing happens. Is there a problem enrolling Huawei devices with a Work Profile?
The specifications to Google merely says Android 5.0 as a minimum requirement.
So what am i doing wrong, or is Huawei not supported for this?
Jan 31 2019 02:52 AM
I sorry but I did not tried to enroll to enroll a P20 since September last year so I could not say if there is a specific problem for the moment.
I remember, that I have experienced some glitches including with the Intune company portal.
You can try a factory reset on your test device which, of course might be difficult to perform on an "in-use" personal device, and start again.
A few questions:
Jan 31 2019 04:13 AM - edited Jan 31 2019 04:14 AM
Since this is a phone for testing, i can pretty much to what i want too it:)
I have done at least 5 factory resets when testing, each attempt failed at the same level using Android Work Profile.
So i assume hard reset is more effective then soft reset, so that should answer those questions.
EMS License is added, and this this the enrollment process, MAM is not in the loop, we only use MDM.
This device is isolated to the Work Profile restrictions for this specific test user as other devices use the normal Android enrollment process. Min version number is set to 5.0+ so it should be good.
Managed Google Play is configured in Intune, Company Portal, Outlook and and Authenticator are approved as apps for this purpose.
Everything seems in order, the process hangs when The personal company portal seems to try and launch the work profile company portal to install this.
After reviewing many google searches/twitter, it seems MS is aware that this is a problem, so it might be a Huawei issue.
Feb 04 2019 11:12 AM
In past I have seen issues with Android legacy device management on Huawei devices. Google provides Android Enterprise (AFW) recommended devices and Huawei P20 Pro is listed so technically it should work in countries outside China.
Feb 28 2019 02:32 PM
Yes, Technically it should, but it doesnt yet.
Im waiting for the Android Pie to come out, should be around the corner now i hope, since they are a bit delayed.
but if Pie also fails, i will have consider this a failure for AFW policy config.
Mar 15 2019 02:39 AM
Hello Thomas, I had the same issue, its one bug with HUAWEY phones.
Mar 15 2019 04:10 AM - edited Mar 15 2019 04:10 AM
Gather an adb bugreport and raise a ticket with Huawei (I would not wait for Android Pie to fix this fault)
The bug report output will be fairly lengthy, however should contain some clue as to why it stopped working.
You may also want to check in with Microsoft Support to see if they have seen this issue before.
Mar 21 2019 03:39 PM
Mar 27 2019 03:23 PM
Apr 08 2019 06:21 AM - edited Apr 08 2019 06:21 AM
@Tomas Tuba No.
Im going to go through my setup here, so if anyone reads something that might be off.
1. I have created a seperate Device Type Restriction profile that has only 1 purpose. The only platform allowed is Android Work Profile, and Android 5.0 including Personally owned allowed. This profile is assigned to the test person.
This test person downloads company portal and install on a newly updated Huawei P20 Pro, with 184.108.40.206 OS installed.
I get the following error now. se attachment
Apr 08 2019 08:39 AM
@Alexander VanyurikhinExplain please?
I Have followed https://docs.microsoft.com/en-us/intune/connect-intune-android-enterprise and configured everything according to the specifications.
And device is listed in the directory.
This is a brand new phone, never been registered before, and attempting to registered it with the Android Work Profile enrollment, not Android Enrollment.
https://docs.microsoft.com/en-us/intune/android-work-profile-enroll If i set Android Work Profile as allowed, and Android as Block, it states it will try and enroll all Android Devices as conventional Device if AWP doesnt work.
Since conventional Device registration is blocked, i belive that i causing my error.. hence, Logic dictates Work Profile doesnt work.
or is my Logic wrong?
Apr 09 2019 04:29 AM
I tried register issued device with the Android enrollment, not Android for Work Enrollment (Restrictions: Android Allowed; Android 4 Work disallowed) with no success.
Only I can set to this device, are MAM policies and assign them to apps...
It looks like bug in Intune MDM..
Apr 09 2019 05:11 AM
Based on what I have read so far I would not jump to Intune being the issue (well not a bug anyway).
You have setup Android Enterprise and want to use Work Profile (do not use the traditional Device Admin setup), other users have this device model working with Intune and it is listed as Android Enterprise Recommended on googles site (this is a very small list and takes a lot more work to get the AER badge).
Apr 09 2019 11:09 PM
We have setup Android Enterprise and restrictions.....
We have many models and types of mobile devices and now only HONOR X, HUAWEI P20 Pro, P10 lite and P9 lite are issued..
HONOR and HUAWEI P20Pro are brand new devices..
HUAWEI P10 lite was SUCCESSFULLY enrolled to Intune and used from 2/2018 in our Company. After 3/2019 work profile on this device stopped working and now its impossible to enroll this device..
I also tested this issue on old HUAWEI P8lite and there wasn´t any issue with creating Work Profile.
So i thing it is bug in Intune after some update on some versions of Android OS.
Apr 10 2019 03:36 AM