Forum Discussion
Windows Autopilot Hybrid Azure AD join fails
Hi
I've observed this behaviour before, I found that if I rebuilt an existing device (already built by Autopilot) it would fail to get the Hybrid Join configuration policy (dynamic group membership issue I think). I now completely delete the device from Intune and AAD every time I rebuild, including removing the HWID. Then re-import the HWID.
Regards
- Those operations take time, we lose all the benefits of Autopilot deployment if we have to perform such actions every time we have to repurpose a device.
For the moment it still works fine, the only thing I do is deleting computer object from ADDS during wipe.Unfortunately it still does not work...
Premier support has no idea why it is failing, I'm going crazy!
This week-end we found out if we launch an Hybrid Autopilot process, let it fail once the 25 minutes timeout happens (0x80070774) then wait 24 hours the machine becomes domain joined! But I still have to reset it since the autopilot process failed...
Both ADDS computer object "whencreated" property and the ODJConnector event IDs (30130 + 30140) show that it happened 24 hours later, 24 hours too late... Why?
How can get rid of it? Any idea? Michael Niehaus maybe?
Mathieu Aït Azzouzène I believe I came across a similar issue that was resolved by updating the version of Windows I had on my USB stick.
Downloaded the latest 1903 ISO and flashed to USB with the media creation tool, then reinstalled on the device, deleted HWID and reuploaded, then it seemed to work
