Troubleshooting Windows Autopilot Failures During Out of Box Experience

Explore Our Microsoft Intune Training →

Windows Autopilot is a powerful tool for IT admins, but sometimes it can fail during the Out of Box Experience (OOBE). This post will help you understand and resolve common issues that arise during OOBE.

Common OOBE Failure Points

Here are some areas where problems often occur:

– Hardware hash registration issues
– ESP (Enrollment Status Page) timeout problems
– Network and DNS requirements during OOBE

Collecting Autopilot Diagnostics

When you encounter an OOBE failure, follow these steps to gather diagnostic logs:

1. Press Shift+F10 at the failure screen.
2. Run `mdmdiagnosticstool.exe -area Autopilot -cab C:\autopilot.cab`

Verifying Hardware Hash Registration

Once you have the logs, check if the hardware hash is registered correctly in Intune:

1. Navigate to Devices > Windows > Windows Autopilot devices.
2. Verify that your device’s hardware hash matches the one registered in Intune.

Checking ESP Profile Timeout Settings

If the device times out on the Enrollment Status Page, check if the timeout settings are causing issues:

1. In the Intune console, go to Windows > Troubleshoot > ESP profile.
2. Review the timeout settings (default 60 minutes may be too short for heavy app installs).

Ensuring DNS Resolution Works

Make sure that your network can resolve the necessary DNS names:

1. Verify that ztd.dds.microsoft.com and cs.dds.microsoft.com resolve correctly.

Refreshing Autopilot Registration

If you’re experiencing repeated failures, use the following PowerShell script to refresh registration:

1. Run `Get-WindowsAutoPilotInfo -Online`

Conclusion

Mastering Windows Autopilot will streamline your corporate laptop deployments. For comprehensive training on Microsoft Intune, including Autopilot and more, check out the courses offered by ITP Training.
}

Explore Our Microsoft Intune Training →