Updated 04/18/25: Based on customer feedback around challenges with setting up the connector with build 6.2501.2000.5, we have released an updated build with improved functionality and updated our tr...
Updated Apr 18, 2025
Version 5.0
Blog Post
Autopilot Hybrid Join Deployment – Stuck at "Waiting for ODJ blob"
Hello everyone, I'm currently facing an issue with an Autopilot deployment in Hybrid Azure AD Join mode. I’ve followed the setup as described and configured the Intune Connector for Active Directory accordingly.
I also ran the Get-AutopilotDiagnostics script, which confirms that the process hangs at the following stages for over 20 minutes:
Waiting for ODJ blob
Starting wait for ODJ blob
Profile downloaded
Eventually, I get this error:
Could not establish connectivity
Timed out waiting for ODJ blob or connectivity
Context:
The Autopilot profile is properly assigned in Intune I'm using the latest version of the ODJ with a managed service account (MSA/gMSA)
The device has network connectivity (DNS resolution and DC ping are successful)
No computer object is created in the target OU
The Microsoft Intune Connector Service has been restarted
No critical errors found in the Event Viewer logs on the connector server
Any suggestions, insights, or shared experiences would be greatly appreciated. Thanks in advance for your help!
I last had this a couple of months ago (before this shift to an MSA)... it was because the computer account being used by the Connector had not been delegated permissions to the target OU. So, it couldn't write the computer objects. You'll want to examine the permissions on the relevant OU(s) and check that the MSA has the expected permissions. It took me days to even consider this, as I had forgotten a colleague replaced my original Connector server with a new one without knowing the Connector needed to be on it. I put it back without even considering the OU permissions. Research online led me in the wrong direction. It had been as simple as permissions.
