Event details
When troubleshooting AP registration, what should we look for in logs (event viewer, ime logs, get-autopilotdiagnostics) and registry that are key indicators of an issue?
MicrosoftHi kamal380. An device has no way of knowing whether it is registered or not until it queries the Autopilot service and if it's not properly registered, the Autopilot service will simply tell it this. This will result in an event in the DeviceManagement-Enterprise-Diagnostic-Provider event log stating that the device is not Autopilot registered. This is truly the only local artifact of a device not being properly Autopilot registered and thus, there's nothing local to check or find on a device that is not properly registered with the Autopilot service.
Autopilot profile not downloading can be caused by multiple things though including not having proper connectivity to the Autopilot service which will also result in an event in the same event log stating this.
Beyond that, most troubleshooting will have to be on the service side for devices that do or cannot start the Autopilot provisioning process.
A lot more info on Autopilot troubleshooting is at Windows Autopilot troubleshooting FAQ | Microsoft Learn.
- Hung_Dang
When a device contacts the Autopilot Service to get an AP profile, the device stores a copy of the file at c:\windows\ServiceState\wmansvc\AutopilotDDSZTDFile.json. You can look in that file for clues as well. e.g., it has certain messages that may be useful for your troubleshooting. There are also some troubleshooting steps for self-deploying and pre-provisioning mode that I posted here: https://techcommunity.microsoft.com/event/windowsevents/ama-windows-autopilot/4429103/comments/4438435
Hope this helps.
