Forum Discussion
Windows Autopilot Hybrid Azure AD join fails
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
Unit2777thank you for your reply.
We already tried to delete the HWID then reupload it, sometimes it works, sometimes not.
We use the latest 1809 ISO from MSDN, not 1903, and it used to work perfectly for months before it started to fail randomly.
Hi all,
It was all about the ping... a few DCs were implemented in Azure with ICMP echo blocked from our on-prem network. Hope this will help others
- Sir, can you be more specific on what solve your issue?
I am pulling my hair out, running into the same issue, side all the troubleshooting you did, my laptops are able to ping the DC and intune connector but I can't get the ODJ blob on the laptops I've tried so many things and everything seems to fail
