Applies to: Windows 10
Windows Autopilot is designed to simplify all parts of the Windows device lifecycle, but there are always situations where issues may arise. When troubleshooting an issue, it is helpful to understand:
- The Windows Autopilot process flow
- How Windows Autopilot device profiles are downloaded
- Key activities to perform during troubleshooting
Windows Autopilot flow
Whether you're performing user-driven or self-deploying device deployments, the troubleshooting process is about the same. It's useful to understand the flow for a specific device:
- A network connection is established. The connection can be a wireless (Wi-fi) or wired (Ethernet) connection.
- The Windows Autopilot profile is downloaded. When you use a wired connection, or manually establish a wireless connection, the profile downloads from the Autopilot deployment service as soon as the network connection is in place.
- User authentication occurs. When performing a user-driven deployment, the user will enter their Azure Active Directory credentials, which will be validated.
- Azure Active Directory join occurs. For user-driven deployments, the device will be joined to Azure AD using the specified user credentials. For self-deploying scenarios, the device will be joined without specifying any user credentials.
- Automatic MDM enrollment occurs. As part of the Azure AD join process, the device will enroll in the MDM service configured in Azure AD (for example, Microsoft Intune).
- Settings are applied. If the enrollment status page is configured, most settings will be applied while the enrollment status page is displayed. If not configured or available, settings will be applied after the user is signed in.
When an Internet-connected Windows 10 device boots up, it will attempt to connect to the Autopilot service and download an Autopilot profile. Note: It's important that a profile exists at this stage so that a blank profile isn't cached locally on the PC. To remove the currently cached local profile in Windows 10 version 1803 and earlier, it's necessary to re-generalize the OS using sysprep /generalize /oobe, reinstall the OS, or re-image the PC. In Windows 10 version 1809 and later, you can retrieve a new profile by rebooting the PC.
When a profile is downloaded depends upon the version of Windows 10 that is running on the PC. See the following table.
|Windows 10 version||Profile download behavior|
|1709||The profile is downloaded after the OOBE network connection page. This page isn't displayed when using a wired connection. In this case, the profile is downloaded before the EULA screen.|
|1803||The profile is downloaded as soon as possible. If wired, it's downloaded at the start of OOBE. If wireless, it's downloaded after the network connection page.|
|1809||The profile is downloaded as soon as possible (same as 1803), and again after each reboot.|
If you need to reboot a computer during OOBE:
- Press Shift-F10 to open a command prompt.
- Enter shutdown /r /t 0 to restart immediately, or shutdown /s /t 0 to shut down immediately.
For more information, see Windows Setup Command-Line Options.
Key troubleshooting activities
For troubleshooting, key activities to perform are:
- Review configuration: Has Azure Active Directory and Microsoft Intune (or an equivalent MDM service) been configured as specified in Windows Autopilot configuration requirements?
- Check network connectivity: Can the device access the services described in Windows Autopilot networking requirements?
- Autopilot out-of-box experience (OOBE) behavior: Are the expected OOBE screens displayed? Is the Azure AD credentials page customized with organization-specific details as expected?
- Azure AD join issues: Is the device able to join Azure Active Directory?
- MDM enrollment issues: IS the device able to enroll in Microsoft Intune (or an equivalent MDM service)?
See the following topics for help troubleshooting specific issues:
- Troubleshoot device enrollment
- Troubleshoot OOBE issues
- Troubleshoot AAD join issues
- Policy conflicts
- Known issues