mdmdiagnosticstool.exe hresult:0x800700a1

mdmdiagnosticstool.exe hresult:0x800700a1

You should also always look at the smsts.log file during OSD to track down errors. You can open log files (.evtx files) in Event Viewer on a Windows A 10 PC that has the November 2015 Update installed. 

You can collect on-demand diagnostic log files from Windows 10 through the MDM channel. For holographs already registered with MDM, MDM logs can be collected remotely through the MDM channel using CSP DiagnosticLog. After the logs are collected on the device, the files can be retrieved through the MDM channel using the FileDownload part of the DiagnosticLog CSP. 


To help diagnose device enrollment or management issues on WindowsA 10 devices managed by an MDM server, you can view the MDM logs collected from the desktop. When troubleshooting Windows 10 MDM in Microsoft Endpoint Manager, there are several client logs and diagnostics that are useful in the vast majority of cases. In this post, I will provide information on using the MDM diagnostic tool and its results, as the right information is very helpful in troubleshooting MDM managed devices running Windows 10. 

Use command to collect logs directly from Windows 10 PCs

You can also collect the MDM Diagnostic Information logs using the following command:

XML

mdmdiagnosticstool.exe -area DeviceEnrollment;DeviceProvisioning;Autopilot -zip c:\users\public\documents\MDMDiagReport.zip
 

In File Explorer, navigate to c:\Users\Public\Documents\MDMDiagnostics to see the report.


Understanding zip structure

The zip file will have logs according to the areas that were used in the command. This explanation is based on DeviceEnrollment, DeviceProvisioning and Autopilot areas. It applies to the zip files collected via command line or Feedback Hub

  • DiagnosticLogCSP_Collector_Autopilot_*: Autopilot etls
  • DiagnosticLogCSP_Collector_DeviceProvisioning_*: Provisioning etls (Microsoft-Windows-Provisioning-Diagnostics-Provider)
  • MDMDiagHtmlReport.html: Summary depiction of MDM space setups and approaches. Incorporates, the executives url, MDM server gadget ID, authentications, approaches.
  • MdmDiagLogMetadata, json: mdmdiagnosticstool metadata record, contains order line contentions used to run the device
  • MDMDiagReport.xml: contains a more detail view into the MDM space arrangements, e.g enlistment factors
  • MdmDiagReport_RegistryDump.reg: contains dumps from normal MDM library areas
  • MdmLogCollectorFootPrint.txt: mdmdiagnosticslog apparatus logs from running the order
  • *.evtx: Common occasion watcher logs microsoft-windows-devicemanagement-undertaking diagnostics-supplier admin.evtx fundamental one that contains MDM occasions.

How to troubleshoot Windows Autopilot using the MDM diagnostic tool

Let's try to understand how to troubleshoot Windows Autopilot using the MDM diagnostic tool as a first step, and then understand the benefits of the MDM diagnostic tool. MDM Diagnostics is a command-line tool that can collect events related to Windows Autopilot. The MDM Diagnostic Tool can be used in less than three (3) troubleshooting areas to collect predefined areas and logs. Depending on the MDM region you select, the MDM diagnostics tool will collect related events, logs, logs, and more, bundled into a single folder or file. 

The first use case is a general use case for displaying only MDM diagnostic information in a given folder. The following example lists all available options, including event logs, log files, command output, and log. The second use case is to collect predefined area logs and create a .cab file with the results. The ZIP file will contain logs based on the scopes used in the command. 



First, it's useful to understand what's in the resulting CAB file (focus on Windows 10 1903 - older versions have fewer files), then browse the list. Also, here is a link to the diskpart command and diskpart command line options. 

Be aware that it is available in Windows 10 version 1903 or later (Insider) builds and can be used with an MDM service such as Intune. The following ETL file will include system actions captured during device provisioning in Windows Autopilot and Intune. AutopilotDDSZTDFile.json High This file contains the Windows Autopilot profile settings used for the device. 


MdmDiagReport_RegistryDump.reg

MdmDiagReport_RegistryDump.reg - This log file contains exported log information related to Autopilot, Device Provisioning, and Policy Manager. LicensingDiag.cab (and its associated LicensingDiag_Output.txt) - These files contain licensing and diagnostic information. LicensingDiag.cab Low If you're having trouble activating Windows, this might interest you, but is otherwise useless for Windows Autopilot troubleshooting. 

Then, open the autopilot event log (microsoft-windows-moderndeployment-diagnostics-provider-autopilot.evtx) and look for errors. Run the command line below to collect Windows Autopilot events from the system for troubleshooting purposes. If you get an error like `` OOBEIDPS '', check the microsoft-windows-shell-core-operational.evtx and setupact.log event logs to see if they report any network errors. 

Microsoft-Windows-Shell-Core.evtx: This event log contains a lot of information related mainly to login and run activities on the device. Microsoft-Windows-AAD.evtx: This event log contains information (and errors) related to Azure AD communication. DiagnosticLogCSP_Collector_Autopilot.etl - This event trace log file contains information about the device autopilot process trace. The log records activities or activities during the OOBE phase of Windows Autopilot. 

How to Use MDM Diagnostics Tool

You need to run MDDiagnosticsTool on Windows 10 1809 and above to collect logs. As a reminder, we have a similar option to collect Win32 app installation log files if the installation fails when installing Win32 through the Intune management extension. There could be 101 other possible reasons for failure that could end up in multiple logs or even ETL trace files (you could try Windows Performance Analyzer, Microsoft Message Analyzer, TRACEFMT or similar - more demanding). If you receive a "Something went wrong" error with error code 8018*, check microsoft-windows-devicemanagement-enterprise-diagnostics-provider-admin.evtx to see what caused the MDM enrollment error. 

The updated DiagnosticLog CSP is a new MDM feature in Windows 10, and Intune as an MDM service is used in this procedure to use the DiagnosticLog CSP. 



The data collection XML structure represents the actual request to collect diagnostic data for the client. The results.xml file tracks the results of individual data collection directives in the HRESULT attribute. 

Hope to help others who need to answer people's questions about how Autopilot works, there are many great answers in the diagnostic tools built into Windows 10.


Result of the MDM Diagnostics Tool

The result of the different use choices of the MDM Diagnostics Tool is additionally unique. As utilization choice 2 and 3 contain a similar data and I can't actually utilize choice 4, we should examine the result of choice 1 and 2. The following is a fast outline of the result, trailed by a clarification of the symptomatic information that is accessible in the result.


 


  1. MDM Diagnostics - Autopilot
  2. MDM Diagnostics - Device enlistment
  3.  MDM Diagnostics - Device provisioning
  4. MDM Diagnostics - TPM

Result of utilization choice 1


The principal utilization choice gives the nonexclusive MDM diagnostics that contains the accompanying data:

  • DeviceManagement-Enterprise-Diagnostics-Provider.evtx - This occasion log contains the data (and mistakes) in regards to the MDM meetings of the gadget. It additionally shows the MDM PolicyManager mistakes.
  • MDMDiagReport.html (and related xml) - This is the very report that can be created by utilizing the Settings board and producing the Advanced Diagnostics Report. That report shows the applied arrangement conditions of the gadgets, including Policy CSP settings, endorsements, setup sources, and asset data.
  • Microsoft-Windows-AAD.evtx - This occasion log contains data (and mistakes) connected with Azure AD correspondences. From gadget enlistment until token solicitations.
  • Microsoft-Windows-Shell-Core.evtx - This occasion log contains a great deal of data for the most part connected with logon errands and runonce activities on the gadget.
  • Result of utilization choice 2 (Autopilot)
  • The second utilization choice, with the Autopilot region indicated, gives conventional MDM diagnostics and explicit Autopilot related diagnostics that contains the accompanying data:
  • AgentExecutor.log - This log document contains data about the PowerShell scripts that are executed by the Intune Management Extention.
  • AutopilotConciergeFile.json - This json record contains the language and console design data during a self organization.
  • AutopilotDDSZTDFile.json - This json record contains the setup data during a standard organization.
  • ClientHealth.log - This log document contains the wellbeing data of the Intune Management Extention.
  • DeviceHash_DESKTOP-U1JNF0E.csv - This csv document contains the gadget hash data of the gadget.
  • DiagnosticLogCSP_Collector_Autopilot.etl - This occasion follow log record contains follow data of the Autopilot cycle of the gadget.
  • DiagnosticLogCSP_Collector_DeviceEnrollment.etl - This occasion follow log record contains follow data of the gadget enlistment cycle of the gadget.
  • DiagnosticLogCSP_Collector_DeviceProvisioning.etl - This occasion follow log document contains follow data of the gadget provisioning interaction of the gadget.
  • IntuneManagementExtension.log - This log document contains data about the Win32 application arrangements that are performed by the Intune Management Extension.
  • LicensingDiag.cab (and related LicensingDiag_Output.txt) - These documents contain authorizing and analytic data.
  • MDMDiagReport.html (and related xml) - This is the very report that can be created by utilizing the Settings board and producing the Advanced Diagnostics Report. That report shows the applied arrangement conditions of the gadgets, including Policy CSP settings, endorsements, setup sources, and asset data.
  • MdmDiagReport_RegistryDump.reg - This library document contains traded vault data connected with Autopilot, yet additionally connected with the provisioning of the gadget and the arrangement chief. Essentially everything connected with MDM the executives.
  • microsoft-windows-aad-operational.evtx - This occasion log contains functional data (and blunders) connected with Azure AD correspondences. From gadget enrollment until token solicitations.
  • microsoft-windows-appxdeploymentserver-operational.evtx - This occasion log contains functional data (and blunders) connected with bundling, sending, or questioning application bundles.
  • microsoft-windows-assignedaccess-admin.evtx - This occasion log contains administrator data (and blunders) connected with doled out access (stand mode).
  • microsoft-windows-assignedaccessbroker-admin.evtx - This occasion log contains administrator data (and blunders) connected with the specialist of allocated admittance (booth mode).
  • microsoft-windows-assignedaccessbroker-operational.evtx - This occasion log contains functional data (and mistakes) connected with the agent of alloted access (booth mode).
  • microsoft-windows-assignedaccess-operational.evtx - This occasion log contains functional data (and blunders) connected with allocated admittance (booth mode).
  • microsoft-windows-devicemanagement-undertaking diagnostics-supplier admin.evtx - This occasion log contains administrator data (and blunders) in regards to the MDM meetings of the gadget.
  • microsoft-windows-devicemanagement-venture diagnostics-supplier debug.evtx - This occasion log contains investigate data (and blunders) with respect to the MDM meetings of the gadget.
  • microsoft-windows-devicemanagement-undertaking diagnostics-supplier operational.evtx - This occasion log contains functional data (and mistakes) with respect to the MDM meetings of the gadget.
  • microsoft-windows-moderndeployment-diagnostics-supplier autopilot.evtx - This occasion log contains the functional data (and blunders) with respect to the Autopilot profile settings and OOBE stream of the gadget.
  • microsoft-windows-moderndeployment-diagnostics-supplier managementservice.evtx - This occasion log contains the functional data (and mistakes) with respect to the administration of the gadget.
  • microsoft-windows-provisioning-diagnostics-supplier admin.evtx - This occasion log contains the administrator data (and blunders) with respect to adding bundles to the gadget.
  • microsoft-windows-shell-center operational.evtx - This occasion log contains a ton of data predominantly connected with logon assignments and runonce activities on the gadget.
  • microsoft-windows-client gadget enlistment admin.evtx - This occasion log contains administrator data (and blunders) in regards to the gadget enrollment (status).
  • setupact.log - This log record contains data about the blunders that happen during the Windows establishment interaction of the gadget.
  • TpmHliInfo_Output.txt - This record contains data about the help of TPM 2.0 for the TPM of the gadget.

Result of use choice 2 (DeviceEnrollment)

 
The second use choice, with the DeviceEnrollment region determined, gives nonexclusive MDM diagnostics and explicit gadget enlistment related diagnostics that contains the accompanying data:

  • DiagnosticLogCSP_Collector_DeviceEnrollment.etl - This occasion follow log document contains follow data of the gadget enlistment cycle of the gadget.
  • MDMDiagHtmlReport.html (and related xml) - This is the very report that can be created by utilizing the Settings board and producing the Advanced Diagnostics Report. That report shows the applied arrangement conditions of the gadgets, including Policy CSP settings, endorsements, setup sources, and asset data.
  • MdmDiagReport_RegistryDump.reg - This vault record contains sent out library data connected with Autopilot, yet additionally connected with the provisioning of the gadget and the arrangement chief. Essentially everything connected with MDM the board.
  • microsoft-windows-aad-operational.evtx - This occasion log contains functional data (and mistakes) connected with Azure AD correspondences. From gadget enlistment until token solicitations.
  • microsoft-windows-appxdeploymentserver-operational.evtx - This occasion log contains functional data (and mistakes) connected with bundling, conveying, or questioning application bundles.
  • microsoft-windows-devicemanagement-endeavor diagnostics-supplier admin.evtx - This occasion log contains administrator data (and blunders) in regards to the MDM meetings of the gadget.
  • microsoft-windows-devicemanagement-endeavor diagnostics-supplier debug.evtx - This occasion log contains investigate data (and blunders) in regards to the MDM meetings of the gadget.
  • microsoft-windows-devicemanagement-undertaking diagnostics-supplier operational.evtx - This occasion log contains functional data (and mistakes) in regards to the MDM meetings of the gadget.
  • microsoft-windows-moderndeployment-diagnostics-supplier managementservice.evtx - This occasion log contains the functional data (and mistakes) with respect to the administration of the gadget.
  • microsoft-windows-provisioning-diagnostics-supplier admin.evtx - This occasion log contains the administrator data (and blunders) in regards to adding bundles to the gadget.
  • Result of use choice 2 (DeviceProvisioning)
  • The second use choice, with the DeviceProvisiong region indicated, gives nonexclusive MDM diagnostics and explicit gadget provisioning related diagnostics that contains the accompanying data:
  • DiagnosticLogCSP_Collector_DeviceProvisioning.etl - This occasion follow log document contains follow data of the gadget provisioning interaction of the gadget.
  • MDMDiagHtmlReport.html (and related xml) - This is the very report that can be created by utilizing the Settings board and producing the Advanced Diagnostics Report. That report shows the applied setup conditions of the gadgets, including Policy CSP settings, declarations, arrangement sources, and asset data.
  • MdmDiagReport_RegistryDump.reg - This library record contains sent out vault data connected with Autopilot, yet additionally connected with the provisioning of the gadget and the strategy supervisor. Essentially everything connected with MDM the executives.
  • microsoft-windows-aad-operational.evtx - This occasion log contains functional data (and mistakes) connected with Azure AD correspondences. From gadget enrollment until token solicitations.
  • microsoft-windows-devicemanagement-endeavor diagnostics-supplier admin.evtx - This occasion log contains administrator data (and mistakes) with respect to the MDM meetings of the gadget.
  • microsoft-windows-provisioning-diagnostics-supplier admin.evtx

 

Comments

Popular posts from this blog

lootboy 2021 redeem codes october 2021 today latest redeem code

Moonshot Wheels