Event banner
AMA: Enrolling modern devices with Windows Autopilot
Event Ended
Thursday, Jul 21, 2022, 08:00 AM PDTEvent details
Interested in the simplified Autopilot device enrollment flows? Do you have questions about pre-provisioned devices? Curious about advanced app and policy configuration during Windows Autopilot enro...
Heather_Poulsen
Updated Dec 27, 2024
Justin_Staples
Jul 21, 2022Copper Contributor
We are using Hybrid Join with our Autopilot (i know! i know!) That said, we tend to see the enrollment error 80180005 pretty frequently with no real pattern towards cause. Our Domain Join naming is very simplified as well. Any other tricks to look at to identify why we see this error so much?
- Hung_DangJul 21, 2022
Microsoft
That's a pretty generic error. You could try to look in the device's event logs for events that reference that error code, and see if the events around it provide the detailed reason.- Justin_StaplesJul 21, 2022Copper ContributorSo for additional context we have worked with our Fast Track team for over a month to really dig in to this issue and as of yesterday they still don't have a solid answer for our configuration. At first were able to delete the Autopilot pc object as well as the AAD object related to and then reupload the device hash and reassign all our profiles, and several devices that previously would fail could then complete. But now we have devices that wont work even after the above steps done several times. We use Lenovo as our OEM, and a pretty much "retail" Enterprise ISO Win 10/Win 11.