From 09cad8c3f4e9d417145ea3a944aa5bb3602163dd Mon Sep 17 00:00:00 2001 From: Siddarth Mandalika Date: Fri, 22 Oct 2021 11:34:38 +0530 Subject: [PATCH] Update diagnosticlog-csp.md --- windows/client-management/mdm/diagnosticlog-csp.md | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/windows/client-management/mdm/diagnosticlog-csp.md b/windows/client-management/mdm/diagnosticlog-csp.md index ef0c719086..4be05d3fad 100644 --- a/windows/client-management/mdm/diagnosticlog-csp.md +++ b/windows/client-management/mdm/diagnosticlog-csp.md @@ -247,8 +247,14 @@ la--- 1/4/2021 2:45 PM 2 la--- 12/2/2020 6:27 PM 2701 results.xml ``` Each data gathering directive from the original `Collection` XML corresponds to a folder in the output. -For example, the first directive was:HKLM\Software\Policies - then folder `1` will contain the corresponding `export.reg` file. +For example, the first directive was: + +```xml + + HKLM\Software\Policies + +``` +then folder `1` will contain the corresponding `export.reg` file. The `results.xml` file is the authoritative map to the output. It includes a status code for each directive. The order of the directives in the file corresponds to the order of the output folders. Using `results.xml` the administrator can see what data was gathered, what failures may have occurred, and which folders contain which output. For example, the following `results.xml` content indicates that registry export of HKLM\Software\Policies was successful and the data can be found in folder `1`. It also indicates that `netsh.exe wlan show profiles` command failed.