Forum Discussion
Device enrolment issue/question
Hi AMR_01,
You can take a look at Autopilot self deploying mode.
Windows Autopilot self-deploying mode (Public Preview) | Microsoft Docs
But for a correct answer, what is the goal you want to achieve, what is the reason why you don't want that the user has to log on with their work account on the device?
Kind regards,
Rene
Hi Mr_Helaas - Rene,
Thanks for replying, the real reason or two is i have one user who has a company PC (at home) and has logged in to his work account and the device shows up as Azure AD joined but fails to enrol into Endpoint Manager. The other reason is i have sent a machine direct from the manufacturer to the user and he has managed to login to his work account but the device is only AD registered and also not enrolled in to endpoint. Both are on the Enterprise Mobility + Security E3 license. I'm not sure where it has failed as there's no logs i can investigate so i thought the best way is to take it out of the user's hands to enrol? What do you think are the best options for me?
Thanks,,
Abs
- Hi... I didnt read that part about azure ad joined devices that arent enrolled into intune. Thats something to look into...
My first guess would be the MDM scope , I am explaining the whole process and differences between aadj/aadr and mdm/mam scope
https://call4cloud.nl/2021/08/the-battle-between-aadj-and-aadr/
Were those license purchased before the devices were azure ad joined ? if so you will need to enroll them manually into mdm /intune
https://call4cloud.nl/2020/05/intune-auto-mdm-enrollment-for-devices-already-azure-ad-joined/Thanks - informative blogs.
I have a question about Auto Pilot. I managed to get 4k HH from HP and added them to the Auto Pilot devices but when it comes to doing an Auto Pilot reset it is not available:Going back to the device in Auto Pilot it shows it hasn't been enrolled and no MDM:
Any ideas why its not allowing me to perform a reset?
- After you got the 4k HH you still need to manually reset the device and perform the autopilot enrollment. Only uploading the 4k hash isn't enough
- I can confirm the OP's complaint. I have several BYOD devices in my tenant that are AAD Registered, show Intune as the MDM authority in my Azure portal, but do NOT appear in my Intune portal. They are accessing company information, but are completely unmanaged and also Not compliant. My tenant has been set up from the outset to force enroll all devices, and all users are properly licensed, but these devices have fallen through the cracks. MSFT Support is telling me that everyone has to enroll via Settings -> Accounts -> Work or school account, but I've enrolled computers with nothing more than a login to Teams. That leaves aside the fact that my ability to dictate how people enroll their BYOD devices from home is severely limited. For me, it's a big problem that I have to compare my Azure device list to my Intune list to find what might be missing.
To the OP, if you want to get up-to-speed on Intune very quickly, I highly recommend Scott Duffey's _Learning Microsoft Endpoint Manager_
https://www.barnesandnoble.com/w/learning-microsoft-endpoint-manager-scott-duffey/1139064650?ean=9780645127904- Thanks for the advice - leaving device owners to enrol their devices is where all my issues start from 🙂
Hi AMR_01,
I think your best option is to fix the enrollment issue. Intune will help you with managing the company devices.
Can you check if your MDM enrollment settings are correct configured within Intune as I can see joining azure AD is not the problem, but only the enrollment in Intune.
Can you check also the enrollment restrictions and Device limit restrictions?
Autopilot will not fix your problem if you are not able to join your Intune environment. Autopilot will fix your AAD registered problem, but the enrollment needs to be fixed first.
You can find some logs in event viewer logged under Applications and Services Logs/Microsoft/Windows/DeviceManagement-Enterprise-Diagnostics-Provider
Did you already check this Microsoft doc page?
Troubleshooting Windows device enrollment problems in Intune - Intune | Microsoft Docs
Can you try to download the company portal app on a device and check if you are able logon and manage the device by your organization? Please upload a print screen or log files if you see any errors.
Kind regards,
Rene
- Thanks for your reply, doing some digging around and found that auto enrolment is confined to a group that only has one member in it to its down to the device owner to enrol. Have understood this correctly that if i set the scope to all every one that signs in the AAD with the correct license get auto enrolled? Or if it still on the device owner to go through the enrolment steps on the device ?
"if i set the scope to all every one that signs in the AAD with the correct license get auto enrolled? Or if it still on the device owner to go through the enrolment steps on the device ?"
In my experience, it's all on the owner to enroll the device correctly. According to Microsoft's documentation, and the techs at MSFT Support, checking "All" gives the device owner the *option* to auto-enroll, but does not force the enrollment. They can still end up with an unmanaged device accessing company data. The only real control you have is Conditional Access, but that only allows you to block access if enrollment is not done properly. That's not "auto-enrollment." It's just an "I can't access my email" support call. I'm curious if there really is any way to auto-enroll BYOD devices? If there isn't, there should be a better way to control this process than what we have presently.
Hi AMR_01,
If the PC is connected to the internet and properly configured in Endpoint Manager to use Auto Pilot, the user shouldn't have problems enrolling the pc and showing in Endpoint Manager.
One thought, you can enroll the pcs with DEM account and then send it to the user. You just have to change the primary user after pc is enrolled and showing Compliant in Endpoint Manager.
Hope this helps!
Moe
https://docs.microsoft.com/en-us/mem/intune/enrollment/device-enrollment-manager-enroll
- Hi Moe, The PCs are not in Endpoint Manager and i dont have Auto Pilot configured. In our setup the PC is AAD joined before it is managed by Endpoint. I think i need to look into Auto Pilot to see if this can help me solve these non enrolment issues.
Thanks,
Abs
