SOLVED

Intune Autopilot device registration error

%3CLINGO-SUB%20id%3D%22lingo-sub-1312231%22%20slang%3D%22en-US%22%3EIntune%20Autopilot%20device%20registration%20error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1312231%22%20slang%3D%22en-US%22%3E%3CP%3EDear%20forum%20members%2C%3C%2FP%3E%3CP%3EI%20am%20autopiloting%20a%20mini%20PC%2C%20it%20was%20successful%20for%20the%20first%20time.%20Then%20the%20other%20day%20we%20sent%20a%20Wipe%20command%20to%20reset%20the%20device%2C%20once%20it%20came%20back%2C%20it%20stopped%20working%20during%20the%20Autopilot%20process%20with%20the%20following%20error%3A%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3EFailed%20registering%20your%20device%20to%20mobile%20management%20with%20error%20code%200x80180014%3C%2FSTRONG%3E.%3C%2FP%3E%3CP%3EAnyone%20could%20recommend%20any%20troubleshooting%20ideas%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20I%20already%20have%20tried%20is%20to%20delete%20the%20device%20from%20the%20Intune%2C%20AAD%20and%20Autopilot%20program.%20I%20re-upload%20the%20machine%20ID%20(csv%20file)%20back%20to%20Autopilot%20program.%20It%20created%20the%20AAD%20object%20successfully%2C%20but%20not%20under%20the%20Intune%20Device%20blade.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20all.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1312231%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EIntune%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMobile%20Device%20Management%20(MDM)%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1314495%22%20slang%3D%22en-US%22%3ERe%3A%20Intune%20Autopilot%20device%20registration%20error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1314495%22%20slang%3D%22en-US%22%3EFirst%20troubleshooting%20idea%20comes%20to%20my%20mind%20is%20to%20check%20your%20Enrollment%20restriction%20Rules%20for%20devices%2C%20if%20all%20looks%20good%2C%20try%20below%3A%3CBR%20%2F%3E%3CBR%20%2F%3ECreate%20new%20Security%20Group%20(not%20Dynamic)%20and%20add%20it%20%E2%80%98member%E2%80%99%20(make%20sure%20the%20status%20change%20to%20assigned)%20and%20give%20it%20another%20try.%3CBR%20%2F%3E%3CBR%20%2F%3EIf%20still%20not%20working%2C%20I%20would%20create%20new%20deployment%20profile%20and%20assign%20the%20new%20security%20group.%3CBR%20%2F%3E%3CBR%20%2F%3EHope%20this%20helps!%3CBR%20%2F%3EMoe%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1314793%22%20slang%3D%22en-US%22%3ERe%3A%20Intune%20Autopilot%20device%20registration%20error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1314793%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F503735%22%20target%3D%22_blank%22%3E%40Moe_Kinani%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20shall%20try%20re-create%20the%20group%20and%20assigned%20the%20device%20as%20direct%20member.%20Failing%20that%2C%20re-create%20the%20Autopilot%20profile%20will%20be%20my%20next%20step.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20Enrollment%20restrictions%20look%20okay.%20There%20is%20a%20rule%20that%20has%20been%20assigned%20to%20the%20device%20group%20already.%20The%20Windows%20MDM%20is%20to%20allow%20and%20Personal%20is%20to%20block.%20The%20Autopilot%20device%20should%20automatically%20become%20corporate%20owned%2C%20I%20guess.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EJust%20to%20clarify%2C%20the%20device%20will%20hit%20the%20restrictions%20rules%20starting%20from%20the%20highest%20priority%20to%20lower%20ones.%20As%20soon%20as%20there%20is%20a%20hit%2C%20the%20restriction%20will%20apply%20(allow%20or%20block)%20and%20other%20lower%20priority%20rules%20will%20not%20process.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20for%20your%20help%20Moe.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1317453%22%20slang%3D%22en-US%22%3ERe%3A%20Intune%20Autopilot%20device%20registration%20error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1317453%22%20slang%3D%22en-US%22%3EYes%2C%20agree.%20Highest%20priority%20rules%20always%20win!%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1317663%22%20slang%3D%22en-US%22%3ERe%3A%20Intune%20Autopilot%20device%20registration%20error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1317663%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F503735%22%20target%3D%22_blank%22%3E%40Moe_Kinani%3C%2FA%3E%2C%20the%20error%20I%20am%20getting%20at%20the%20Autopilot%20enrollment%20status%20page%20is%20%22failed%3A%206%2C%200x80180014%22.%20Google%20the%20error%20code%20takes%20me%20to%20the%20enrollment%20restriction%20page%20but%20I%20can't%20see%20how%20the%20current%20restriction%20settings%20are%20causing%20this.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1318536%22%20slang%3D%22en-US%22%3ERe%3A%20Intune%20Autopilot%20device%20registration%20error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1318536%22%20slang%3D%22en-US%22%3EAuto%20Pilot%20errors%20codes%20are%20not%20%25100%20accurate%2C%20I%20have%20been%20on%20the%20same%20boat%20before.%3CBR%20%2F%3E%3CBR%20%2F%3EHave%20you%20tried%20creating%20new%20deployment%20profile%20and%20assign%20to%20Security%20Group%20that%20includes%20the%20effected%20device%3F%20I%20don%E2%80%99t%20see%20your%20Restriction%20rule%20will%20affect%20it%20as%20it%20hits%20personal%20devices.%3CBR%20%2F%3E%3CBR%20%2F%3EI%20would%20leave%20disabling%20the%20existing%20restriction%20rule%20as%20last%20resort.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1340312%22%20slang%3D%22en-US%22%3ERe%3A%20Intune%20Autopilot%20device%20registration%20error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1340312%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F503735%22%20target%3D%22_blank%22%3E%40Moe_Kinani%3C%2FA%3E%2C%20I%20logged%20a%20support%20case%20and%20here%20is%20the%20official%20answer%20from%20Microsoft.%3C%2FP%3E%3CP%3EThe%20user%20created%20enrollment%20restrictions%20only%20apply%20to%20user-driven%20enrollment.%20It%20is%20not%20supported%20for%20user-less%20enrollment%20using%20the%20Self-Deploying%20methods.%20So%20it%20will%20hit%20the%20default%20rule.%3C%2FP%3E%3CP%3EAs%20soon%20as%20I%20allowed%20Windows%20MDM%20in%20the%20default%20enrollment%20restriction%2C%20it%20started%20working.%3C%2FP%3E%3CP%3EThanks%20for%20your%20help%20my%20friend.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1340327%22%20slang%3D%22en-US%22%3ERe%3A%20Intune%20Autopilot%20device%20registration%20error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1340327%22%20slang%3D%22en-US%22%3EThanks%20for%20the%20update%20wangjueliang!%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E
Contributor

Dear forum members,

I am autopiloting a mini PC, it was successful for the first time. Then the other day we sent a Wipe command to reset the device, once it came back, it stopped working during the Autopilot process with the following error: 

Failed registering your device to mobile management with error code 0x80180014.

Anyone could recommend any troubleshooting ideas?

 

What I already have tried is to delete the device from the Intune, AAD and Autopilot program. I re-upload the machine ID (csv file) back to Autopilot program. It created the AAD object successfully, but not under the Intune Device blade.

 

Thanks all.

7 Replies
Best Response confirmed by wangjueliang (Contributor)
Solution
First troubleshooting idea comes to my mind is to check your Enrollment restriction Rules for devices, if all looks good, try below:

Create new Security Group (not Dynamic) and add it ‘member’ (make sure the status change to assigned) and give it another try.

If still not working, I would create new deployment profile and assign the new security group.

Hope this helps!
Moe

Thanks @Moe_Kinani 

I shall try re-create the group and assigned the device as direct member. Failing that, re-create the Autopilot profile will be my next step.

 

The Enrollment restrictions look okay. There is a rule that has been assigned to the device group already. The Windows MDM is to allow and Personal is to block. The Autopilot device should automatically become corporate owned, I guess.

 

Just to clarify, the device will hit the restrictions rules starting from the highest priority to lower ones. As soon as there is a hit, the restriction will apply (allow or block) and other lower priority rules will not process. 

 

Thanks for your help Moe.

Yes, agree. Highest priority rules always win!

Hi @Moe_Kinani, the error I am getting at the Autopilot enrollment status page is "failed: 6, 0x80180014". Google the error code takes me to the enrollment restriction page but I can't see how the current restriction settings are causing this.

Auto Pilot errors codes are not %100 accurate, I have been on the same boat before.

Have you tried creating new deployment profile and assign to Security Group that includes the effected device? I don’t see your Restriction rule will affect it as it hits personal devices.

I would leave disabling the existing restriction rule as last resort.

Hi @Moe_Kinani, I logged a support case and here is the official answer from Microsoft.

The user created enrollment restrictions only apply to user-driven enrollment. It is not supported for user-less enrollment using the Self-Deploying methods. So it will hit the default rule.

As soon as I allowed Windows MDM in the default enrollment restriction, it started working.

Thanks for your help my friend.

Thanks for the update wangjueliang!