Forum Discussion
HarshJ8
Feb 14, 2024Copper Contributor
Error Code 80180018
While Enrolling windows devices in Intune with EMS E3 licenses assigned to users we are getting the error code 80180018
HarshJ8
Feb 14, 2024Copper Contributor
Hello LeonPavesic we have already tried the above mentioned steps but we are still not able to enroll devices in Intune
Feb 14, 2024
Did you run the troubleshooter (the only one that helps 🙂 ) in the intune portal itself as i also mention in part 5.3: https://call4cloud.nl/2022/06/enrollmenterrorsintune/#part5
Even when you assigned the proper license, it could be that it doesn't flip on the intune part of the license....
Besides the error you mention, in the events logs that i also mention in that blog any other useful error in it that could tell you more about whats going on
Also.... how are you enrolling the device... as an existing device? hybrid? autopilot?
Even when you assigned the proper license, it could be that it doesn't flip on the intune part of the license....
Besides the error you mention, in the events logs that i also mention in that blog any other useful error in it that could tell you more about whats going on
Also.... how are you enrolling the device... as an existing device? hybrid? autopilot?
- HarshJ8Feb 15, 2024Copper Contributor
Rudy_Ooms_MVP we have already run the troubleshooter it shows Account is enabled and license is assigned . We are trying to enroll device through the Autopilot mode, we have also tried other ways to enroll the device such as enrolling the device through the company portal app, directly enrolling the device to Azure AD.
- Feb 15, 2024Thats kinda weird because:
https://learn.microsoft.com/en-us/windows/client-management/mdm-diagnose-enrollment
0x80180018 "idErrorMDMLicenseError", // MENROLL_E_USERLICENSE There was an error with your license. You can try to do this again or contact your system administrator with the error code {0}.
Is everyone getting the same error who you are trying to enroll?- HarshJ8Feb 15, 2024Copper ContributorYes we tried with 3 different users and 4 different devices but the same error pops up