Skip to content

Commit 8f135e0

Browse files
Merge pull request #3005 from MicrosoftDocs/client-analyzer-links
Client analyzer links
2 parents 1ec99a2 + d93c741 commit 8f135e0

File tree

3 files changed

+18
-8
lines changed

3 files changed

+18
-8
lines changed

defender-endpoint/analyzer-report.md

Lines changed: 15 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ ms.collection:
1515
ms.topic: conceptual
1616
ms.subservice: onboard
1717
search.appverid: met150
18-
ms.date: 02/15/2024
18+
ms.date: 03/04/2025
1919
---
2020

2121
# 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
2828

2929
Use the following example to understand the report.
3030

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:
3234

3335
:::image type="content" source="media/147cbcf0f7b6f0ff65d200bf3e4674cb.png" alt-text="The MDE Client Analyzer Results page" lightbox="media/147cbcf0f7b6f0ff65d200bf3e4674cb.png":::
3436

3537
- On top, the script version and script runtime are listed for reference
38+
3639
- 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.
3842

3943
:::image type="content" source="media/85f56004dc6bd1679c3d2c063e36cb80.png" alt-text="The Check Results Summary page" lightbox="media/85f56004dc6bd1679c3d2c063e36cb80.png":::
4044

4145
- On **Check Results Summary**, you'll have an aggregated count for error,
4246
warning, or informational events detected by the analyzer.
47+
4348
- On **Detailed Results**, you'll see a list (sorted by severity) with
4449
the results and the guidance based on the observations made by the analyzer.
4550

4651
## Open a support ticket to Microsoft and include the Analyzer results
4752

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:
5054

5155
:::image type="content" source="media/508c189656c3deb3b239daf811e33741.png" alt-text="An attachment prompt" lightbox="media/508c189656c3deb3b239daf811e33741.png":::
5256

5357
> [!NOTE]
5458
> 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+
5565
[!INCLUDE [Microsoft Defender for Endpoint Tech Community](../includes/defender-mde-techcommunity.md)]

defender-endpoint/overview-client-analyzer.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ ms.collection:
1717
ms.topic: conceptual
1818
ms.subservice: ngp
1919
search.appverid: met150
20-
ms.date: 02/27/2024
20+
ms.date: 03/04/2025
2121
---
2222

2323
# Troubleshoot sensor health using Microsoft Defender for Endpoint Client Analyzer
@@ -26,7 +26,7 @@ ms.date: 02/27/2024
2626
- [Microsoft Defender for Endpoint Plan 1](microsoft-defender-endpoint.md)
2727
- [Microsoft Defender for Endpoint Plan 2](microsoft-defender-endpoint.md)
2828

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.
3030

3131
Besides obvious sensor health issues, MDECA can collect other traces, logs, and diagnostic information for troubleshooting complex scenarios such as:
3232

defender-endpoint/troubleshoot-collect-support-log.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ ms.collection:
1414
ms.topic: troubleshooting
1515
ms.subservice: edr
1616
search.appverid: met150
17-
ms.date: 02/03/2025
17+
ms.date: 03/04/2025
1818
---
1919

2020
# Collect support logs in Microsoft Defender for Endpoint using live response

0 commit comments

Comments
 (0)