Forum Discussion
Intune Enrollment via GPO User eXperience
Yes, the machines are showing as Hybrid Azure AD Join but not as enrolled in Intune.
Stuart
StuartK73 I had similar issues with on my tenant where devices will show in Azure AD Devices as Hybrid Azure AD Join but not in All Devices and the MDM state is shown as none. The fix for my case was to set 2 GPO policy settings (As per MS Support, the first device registration policy adds the device to Azure AD and MDM part enrolls the device to intune, and we need to have both to get the devices fully managed via intune/MDM)
If you do not see the policy, it may be because you don’t have the ADMX installed for Windows 10, version 1803 or version 1809. To fix the issue, follow these steps:
- Download:
1803 -->https://www.microsoft.com/en-us/download/details.aspx?id=56880 or
1809 --> https://www.microsoft.com/en-us/download/details.aspx?id=57576. - Install the package on the Primary Domain Controller (PDC).
- Navigate, depending on the version to the folder: 1803 --> C:\Program Files (x86)\Microsoft Group Policy\Windows 10 April 2018 Update (1803) v2, or
1809 --> C:\Program Files (x86)\Microsoft Group Policy\Windows 10 October 2018 Update (1809) v2 - Copy policy definitions folder to C:\Windows\SYSVOL\domain\Policies.
- Restart the Primary Domain Controller for the policy to be available. This procedure will work for any future version as well.
My environment is as follows:-
On Premise AD
Hybrid Azure AD Joined devices using AD Connect
I was also facing the same situation where the status of the MDM was None rather than Microsoft Intune for my Windows 10 devices.
Ambarish I followed that extra step to Register domain joined computers as devices and now it seem to work. I would why this setting is needed given the device is already Hybrid Azure AD Joined?
Previously I did get this to work but only when the device was line of sight to my on premise AD. i.e. in the office. So I thought that was just the limitation of auto enrolment.
Because all my users are now WFH due for COVID I will need to try this with some other devices but it now looks more positive.
Chris-Yue It is actually required as part of the GPO Policy for Hybrid-joined devices. It should be worth noting that when configuring GPO for devices, you only need to change Computer Config policies and never duplicate the same policy on the User Config.
Here's a preview of mine.
Thanks for the tip.
On the articles I have seen, I saw reference to Enable automatic MDM enrolment using default Azure Ad but not the device registration one.
Another thing I have noticed is the following.
Where a user picture has been assigned to Office 365, which is visible in office.com and mobile apps, should this appear on Windows 10 devices at the login screen?
I got this once, but since retiring the device and re-enrolling again, I don't see it anymore.
That's very interesting, using the 2 GPO's.
I had that setup already, then removed the Device Registration one as I was advised that this was NOT needed for Hybrid Azure AD Join, as all domain devices register as Hybrid Azure AD Join once AADC has been configured this way.
I will re-implement the Device Registration policy and keep you posted.
Thanks again
- Verify that the user who is going to enroll the device has a valid Intune license.
- Make sure that your auto-enrollment (MDM user scope to "All") settings are configured under Microsoft Intune instead of Microsoft Intune Enrollment.
- Verify that the Enable Automatic MDM enrollment using default Azure AD credentials group policy (Computer Configuration > Policies > Administrative Templates > Windows Components > MDM) is properly deployed to all devices which should be enrolled into Intune.
- Verify that Microsoft Intune should allow enrollment of Windows devices (Device enrollment restrictions in Endpoint Manager portal)
I recently had another instance where the AzureAdPrt was NO, an MS support agent gave me the following steps:
1) whoami /upn Run the command in commad prompt UPN should be same in cloud .
2) Add the URL in IE
· https://protect-eu.mimecast.com/s/7cNrC3yo2FVq0ytqUWXJ?domain=nam06.safelinks.protection.outlook.com
· https://protect-eu.mimecast.com/s/rta3C5Rq9tOE4Xu2Qph_?domain=nam06.safelinks.protection.outlook.com
· https://protect-eu.mimecast.com/s/NYinC7pvLU9lo8uRKqKj?domain=nam06.safelinks.protection.outlook.com
· https://protect-eu.mimecast.com/s/8FAAC9DxQiPQ9lsZZskZ?domain=nam06.safelinks.protection.outlook.com
3) Open task scheduler(AS admin )> Microsoft>Windows> Work place join>right click on “Auto work place join” and make sure it is in “running” state.
4) Then re-start machine and run dsregcmd /status , check for Azure prt status.
5) dsregcmd /debug /leave in admin mode.
6) Once machine up run dsregcmd /debug /join in admin mode.
