Autopilot deployment

1. Write down the stage, not just “stuck”

Record the displayed stage, error code, time and the last item that completed. Compare with a known-good pilot device using the same profile and network.

In the Intune admin centre, open Enrollment Status Page within Windows enrolment and inspect the assigned ESP profile. Record the timeout and blocking-app settings before considering a change. Microsoft: ESP configuration.

2. Collect evidence before retrying

Where enabled and supported, use View Diagnostics or Ctrl + Shift + D. Microsoft limits this diagnostic page to supported Windows 11 user-driven deployments with a work or school account. At an ESP timeout, use the available log-collection option and your approved transfer location. Microsoft: diagnostics availability.

For an authorised technician collecting a classic user-driven Autopilot bundle from Command Prompt, Microsoft's documented pattern is:

mdmdiagnosticstool.exe -area Autopilot -cab "<approved-output-path>\Autopilot.cab"

Replace the placeholder with an existing, approved folder. This creates a diagnostic file; it does not repair the device. Logs can contain device and user identifiers. Keep the original in the restricted incident record and sanitise any copy shared outside the support team.

The bundle can include MDMDiagReport_RegistryDump.Reg. Open it as text to inspect tracking information; do not double-click it to import registry settings. The EnrollmentStatusTracking records can help identify a tracked Win32 app and its state. An error state identifies what to investigate, not the cause by itself. Microsoft: interpreting ESP evidence.

3. Match the evidence to the application

In Intune, open Apps → All apps, select the identified Win32 app and inspect its device installation status. Compare the application identifier, device and timestamps. Inspect the install command, detection rules, requirements, dependencies, install context and return-code handling.

On the device, Intune Management Extension logs are normally under C:\ProgramData\Microsoft\IntuneManagementExtension\Logs. Use the app-processing and installation records to distinguish a download, execution, detection or dependency problem. Record the original settings and ask the app owner to approve any correction. Microsoft: Win32 troubleshooting and logs.

5. Verify the school handover

Confirm that setup completes, the intended user can sign in, essential teaching apps work, and required management and access checks pass. Desktop access alone does not prove that every policy has finished applying.

If unresolved, hand over: deployment method, device and tenant references, exact stage and error, relevant app identifier, timestamps, log location, comparison with the working pilot, and changes already attempted. Do not delete registration or wipe devices merely because the screen stopped progressing.