Are you experiencing issues with Windows Autopilot device enrollment, specifically encountering error code 801C03ED (sometimes 0x801C03ED)? Don't worry, I've got you covered! In this post, I will guide you through resolving this error, which can occur when provisioning a device using Windows Autopilot. Let's dive in!
Understanding the Issue
When you experience unexpected behavior during the out-of-box experience (OOBE) with Autopilot, your first step should be to check if the device has received an Autopilot profile. Depending on your Windows client release, you have various methods to verify and adjust the profile settings.
Streamlining Device Management with Intune and Autopilot
Let's talk about how leveraging Intune and Autopilot can help you pre-configure, reset, repurpose, and recover devices without the need for re-imaging. This approach can save you significant time in device management. Now, who doesn't like saving time?
Enrolling Windows 11 PCs in Intune
Achieving the enrollment of Windows 11 PCs in Intune can be done through multiple methods, including using MDM auto-enrollment from Azure AD for Windows 10/11 devices and harnessing Intune Group Policy for Hybrid Azure AD joined devices. Pretty cool, right?
Resolving Common Errors
If you come across the "Something went wrong and Can’t connect to the URL of your organization’s MDM terms of use. Try again" error during OOBE, it's often related to licensing issues.
Addressing Error 0x801C03ED
This error can pop up during device setup or when a user tries to enroll a Windows device. It comes with messages such as "Something went wrong, confirm you are using the correct sign-in information and that your organization uses this feature."
Troubleshooting Steps
To troubleshoot Error 801C03ED, you can examine log entries using Event Viewer within
- Application and Services Logs >
- Microsoft >
- Windows >
- ModernDeployment-Diagnostics-Provider >
- Autopilot
Depending on the issue, various events may be recorded.
Fixing Error 801C03ED
You can often resolve these errors by instructing administrators to reimport the device hardware hash. Deleting and then reimporting this hash can recreate the associated object in Azure AD. You got this!
Managing Autopilot Devices in Intune
Exercise caution to avoid deleting or deactivating the Azure AD device object created upon import, as it serves as Autopilot's anchor for group membership and targeting. Deleting this object may result in joining errors. So be careful with that delete button!
If it's just deactivated, you can easily reactivate it by searching for the serial number the autopilot device overview:
- Intune > Devices > Enroll devices > Devices
- Search and select the device (by serial number)
- Click on the Azure AD device
- Click "Enable"
Validating User Scope in Azure AD Device Settings
Make sure that the Azure AD setting "Users might join devices to Azure AD" is not set to "None," as this can prevent Intune enrollment. Update this setting to "All" or a group where the desired users are part of. Like this you allow users to join their devices to Azure AD.
May recommendation: Let's make sure everyone has access to what they need.
The setting if found here:
- Azure AD
- Devices
- Device settings
By following these steps actively, you can resolve the Autopilot enrollment error 0x801C03ED and successfully initiate the Autopilot deployment without encountering further issues. You're now ready to be the Autopilot master! 🚀
