Intune - Autopilot Troubleshooting
Sometimes during the Autopilot process you will encounter errors. Here are some tips for diagnosing the issue.
Microsoft provides some general Autopilot troubleshooting here:https://learn.microsoft.com/en-us/autopilot/troubleshooting-faq
Verify Autopilot Status in the Intune Portal
Before starting any troubleshooting, make sure that hardware hash for the computer is uploaded to Intune and that the Profile Assignement status in the Intune Portal is "Assigned". If you started the Pre-Provisioning or User Driven enrollment and the profile was not assigned yet, you'll want wipe and install Windows clean on that computer. Then start the OOBE process again.
Bring up Event Viewer During OOBE
Press Shift-F10 to open CMD go to eventvwr.exe and navigate to Application and Service Logs >> Microsoft >> Windows >> Modern Deployment
Viewing Errors
If you have an error during the Autopilot process you may be given the option to view diagnostics.
Click the triangle next to a section that has an Exclamation Point icon to view the error. You can also choose to Export logs to a USB drive. When you click the Export logs button you will prompted to save the logs to a folder on another drive.
Common issues are an application that fails to install during the Autopilot process. You'll be given a Application ID which correlates with application. Here are some standard Autopilot applications and there associated App IDs.
| Application Name | AppID |
| MIT - OOBE - Acrobat Reader DC | 4a13bf25-ed08-40bf-87db-fa0051188233 |
| MIT - OOBE - CertAid | 4e79330a-141f-440f-9fb2-da11dacc54af |
| MIT - OOBE - Chrome | 87e49033-fde1-45d8-bfde-415b19f532e1 |
| MIT - OOBE - Company Portal | fa2e218c-71c7-41b0-81d5-520d38d64e9a |
| MIT - OOBE - CrashPlan | ff28cdc1-4a7d-4048-9529-f262bd3dcf44 |
| MIT - OOBE - CrowdStrike Falcon | 5e8d5dfe-646e-4fd0-8439-dc040c8c136f |
| MIT - OOBE - Dropbox | 811b9b58-8914-4baf-895f-804bac2fe737 |
| MIT - OOBE - Firefox ESR | 48ae048d-bb09-4d2c-9a27-eb8cce189f19 |
| MIT - OOBE - GlobalProtect | fdd7729a-e321-49db-b797-d25892e29c42 |
| MIT - OOBE - MECM Client | 3cc4ca9f-193c-4865-98fb-9499deab0caa |
| MIT - OOBE - Kerberos for Windows | 98c3ad2b-4c55-4345-92a0-36ea9090aa02 |
| MIT - OOBE - Office 365 | b15bdf0f-7a8f-4a27-aa8f-fc270ff942c0 |
| MIT - OOBE - Slack | b2492feb-3b1a-4319-847d-96f4fae010cc |
| MIT - OOBE - Sophos Central | c05acb50-cde4-4a30-8818-164172c3af95 |
| MIT - OOBE - Time Zone Auto Update | 08bce378-05c0-49e3-97b4-0195b7e6b8af |
| MIT - OOBE - Zoom | 363b0226-5d78-4417-851e-d963fd908146 |
Intune Logs
Once you're at the Windows desktop you can view additional logs located on the computer
Intune agent logs on the client machine are in:
C:\ProgramData\Microsoft\IntuneManagementExtension\Logs
To check Device Provisioning Status, please check Logs are at:
C:\ProgramData\Microsoft\Windows\ESP\Logs
You can view these logs using the CMtrace.exe tool located at C:\Windows\CCM\CMTrace.exe
