Usage1: C:\WINDOWS\system32\MdmDiagnosticsTool.exe -out
csv export to import directly into the Autopilot service (Tested on build 18298)īefore Windows 10 RS5 (It also works on RS5) Licensingdiag.exe is the tool to get diagnostic data from your deviceĪn example is the AutoPilotDiagEvent.evtx It creates a lot of useful logfiles – On Windows 10 RS6 insider build it is including the Windows Autopilot. If you are troubleshooting Windows Autopilot after RS5 then you can use MdmDiagnosticsTool.exe – with the parameter -area and -cab (At this moment when I point to a location for my export files need to be places they all end up in %Temp%) Then you are getting the result of what is stored in the hardware hash If you run the command : oa3tool.exe /DecodeHwHash= It is not customer data that are stored, but business data which enables Microsoft to provide a serviceįirst you need to download the Windows ADK from – Note you need to use at least ADK version 1703 or above.Īfter installation of Microsoft ADK you can find the tool you need here:Ĭ:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\amd64\Licensing\OA30\oa3tool.exe Windows Autopilot data is stored in the United States (US), and not in the region where your AAD tenant is places. Where is Windows autopilot device information stored? The minimum requirement for unique values in the SMBIOS: When we look at what information there is in the Autopilot hardware hash – then we also get the idea why we need a new hardware hash after e motherboard replacement.
I hoping to help others that are having to answer questions to people on how Autopilot is working, there is a lot of great answers in the diagnostic tools that are build onto Windows 10. In my work with Windows Autopilot over the last year, I also found some different diagnostic tools that I have tried to get into this blog post.
Autopilot hardware hash is a mystery for many IT admins – I often get a question on what data the hardware hash contains.
0 kommentar(er)
