Autopilot Pre-Provisioning Fails with Error 0x80180014

Christine VACHER 21 Reputation points
2024-07-24T16:12:47.5433333+00:00

An AutoPilot registered device is being reused and had an AutoPilot Reset.

I tried several things:

  1. Delete the InTune record.
  2. Reset the device.
  3. Select language & keyboard before hitting Win key 5x.

What could be causing this issue?

MDM 20240722_103903 - caviar

Microsoft Intune Configuration
Microsoft Intune Configuration
Microsoft Intune: A Microsoft cloud-based management solution that offers mobile device management, mobile application management, and PC management capabilities.Configuration: The process of arranging or setting up computer systems, hardware, or software.
1,813 questions
Microsoft Intune Enrollment
Microsoft Intune Enrollment
Microsoft Intune: A Microsoft cloud-based management solution that offers mobile device management, mobile application management, and PC management capabilities.Enrollment: The process of requesting, receiving, and installing a certificate.
1,320 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. ZhoumingDuan-MSFT 11,055 Reputation points Microsoft Vendor
    2024-07-25T02:12:15.8766667+00:00

    @Christine VACHER, Thanks for posting in Q&A.

    From your description, I know you have done Autopilot pre-provisioning enrollment but failed with error 0x80180014.

    Based on my research, the error code may relate to Enrollment restrictions.

    Here are some suggestions you can try to fix the issue.

    1.Check Device Restrictions: Ensure that your device restrictions in Intune are not preventing the enrollment of your VM. You can do this by logging into the Microsoft Intune admin Center, clicking on Devices -> Enroll Devices -> Enrollment restrictions, and editing the policy applied to the users.

    User's image

    2.Delete the device record in Intune, Azure AD, also delete the csv record and re-import the csv file, re-create the pre-provisioning file, re-deploy it, if you have this machine setup in the Hybrid AAD Join mode, remove the local computer object as well and make sure the changes synced back to Azure AD.

    https://emsroute.com/2022/05/09/fix-autopilot-error-0x80180014-1/

    Non-official, just for reference.

    Please try above information, if there is any update, feel free to let me know.

    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments No comments

  2. Christine VACHER 21 Reputation points
    2024-07-25T22:02:20.3166667+00:00

    Hello @ZhoumingDuan-MSFT , thank you for your detailed answer.

    Device Restrictions

    We don't have any (that is, we only have the "All users" default).

    (Note that Enrollment restrictions is now under Devices | Enrollment.)

    Delete the device record in Autopilot

    This is what I want to avoid at (almost) all costs. It takes so much time and there will be cases when I don't have the device at hand. (They are not VMs).

    Probable cause

    I think that I should not have tried to Pre-Provision a device that was previously enrolled in InTune. Autopilot Reset (when working) does that Pre-Provisioning (that is the 2 first enrollment steps).

    What I have done

    I used the *__Reset this PC __*Windows procedure. I didn't need to delete Autopilot record.
    I re-enrolled the device using some licensed user account.

    I have Autopilot reset the device again.

    0 comments No comments