You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: defender-endpoint/analyzer-report.md
+15-5Lines changed: 15 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,7 @@ ms.collection:
15
15
ms.topic: conceptual
16
16
ms.subservice: onboard
17
17
search.appverid: met150
18
-
ms.date: 02/15/2024
18
+
ms.date: 03/04/2025
19
19
---
20
20
21
21
# Understand the client analyzer HTML report
@@ -28,28 +28,38 @@ The client analyzer produces a report in HTML format. Learn how to review the re
28
28
29
29
Use the following example to understand the report.
30
30
31
-
Example output from the analyzer on a machine onboarded to expired Org ID and failing to reach one of the required Microsoft Defender for Endpoint URLs:
31
+
## Example output
32
+
33
+
In this example, the [Defender for Endpoint Client Analyzer](/defender-endpoint/overview-client-analyzer) produced information about a device that was onboarded to an expired Org ID and failed to reach a required Defender for Endpoint URL:
- On top, the script version and script runtime are listed for reference
38
+
36
39
- The **Device Information** section provides basic OS and device identifiers to uniquely identify the device on which the analyzer has run.
37
-
- The **Endpoint Security Details** provides general information about Microsoft Defender for Endpoint-related processes including Microsoft Defender Antivirus and the sensor process. If important processes aren't online as expected, the color will change to red.
40
+
41
+
- The **Endpoint Security Details** provides general information about Microsoft Defender for Endpoint-related processes including Microsoft Defender Antivirus and the sensor process. If important processes aren't online as expected, the color changes to red.
- On **Check Results Summary**, you'll have an aggregated count for error,
42
46
warning, or informational events detected by the analyzer.
47
+
43
48
- On **Detailed Results**, you'll see a list (sorted by severity) with
44
49
the results and the guidance based on the observations made by the analyzer.
45
50
46
51
## Open a support ticket to Microsoft and include the Analyzer results
47
52
48
-
To include analyzer result files [when opening a support ticket](contact-support.md#open-a-service-request), make sure you use the **Attachments** section and include the
49
-
`MDEClientAnalyzerResult.zip` file:
53
+
To include analyzer result files [when opening a support ticket](contact-support.md#open-a-service-request), make sure you use the **Attachments** section and include the `MDEClientAnalyzerResult.zip` file:
> If the file size is larger than 25 MB, the support engineer assigned to your case will provide a dedicated secure workspace to upload large files for analysis.
59
+
60
+
## See also
61
+
62
+
-[Troubleshoot sensor health using Microsoft Defender for Endpoint Client Analyzer](overview-client-analyzer.md)
63
+
64
+
55
65
[!INCLUDE [Microsoft Defender for Endpoint Tech Community](../includes/defender-mde-techcommunity.md)]
Copy file name to clipboardExpand all lines: defender-endpoint/overview-client-analyzer.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,7 +17,7 @@ ms.collection:
17
17
ms.topic: conceptual
18
18
ms.subservice: ngp
19
19
search.appverid: met150
20
-
ms.date: 02/27/2024
20
+
ms.date: 03/04/2025
21
21
---
22
22
23
23
# Troubleshoot sensor health using Microsoft Defender for Endpoint Client Analyzer
@@ -26,7 +26,7 @@ ms.date: 02/27/2024
26
26
-[Microsoft Defender for Endpoint Plan 1](microsoft-defender-endpoint.md)
27
27
-[Microsoft Defender for Endpoint Plan 2](microsoft-defender-endpoint.md)
28
28
29
-
The Microsoft Defender for Endpoint Client Analyzer (MDECA) can be useful when diagnosing sensor health or reliability issues on [onboarded devices](onboard-configure.md) running either Windows, Linux, or macOS. For example, you may want to run the analyzer on a machine that appears to be unhealthy according to the displayed [sensor health status](fix-unhealthy-sensors.md) (Inactive, No Sensor Data or Impaired Communications) in the security portal.
29
+
The [Microsoft Defender for Endpoint Client Analyzer](https://aka.ms/MDEClientAnalyzer) (MDECA) can be useful when diagnosing sensor health or reliability issues on [onboarded devices](onboard-configure.md) running either Windows, Linux, or macOS. For example, you may want to run the analyzer on a machine that appears to be unhealthy according to the displayed [sensor health status](fix-unhealthy-sensors.md) (Inactive, No Sensor Data or Impaired Communications) in the security portal.
30
30
31
31
Besides obvious sensor health issues, MDECA can collect other traces, logs, and diagnostic information for troubleshooting complex scenarios such as:
0 commit comments