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/run-analyzer-linux.md
+64-49Lines changed: 64 additions & 49 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,15 +1,15 @@
1
1
---
2
2
title: Run the client analyzer on Linux
3
3
description: Run the Defender for Endpoint client analyzer on Linux
4
-
author: batamig
5
-
ms.author: bagol
4
+
author: paulinbar
5
+
ms.author: painbar
6
6
manager: bagol
7
7
ms.reviewer: yongrhee
8
8
ms.service: defender-endpoint
9
9
ms.subservice: linux
10
10
ms.localizationpriority: medium
11
11
ms.topic: troubleshooting-general
12
-
ms.date: 05/24/2025
12
+
ms.date: 09/23/2025
13
13
ms.custom: partner-contribution
14
14
ms.collection:
15
15
- m365-security
@@ -29,42 +29,48 @@ f1.keywords: NOCSH
29
29
30
30
> Want to experience Defender for Endpoint? [Sign up for a free trial.](https://go.microsoft.com/fwlink/p/?linkid=2225630)
31
31
32
-
If you have issues with Microsoft Defender for Endpoint on Linux and need support, you might be asked to provide the output from the Client Analyzer tool. This article explains how to use the tool on your device or with live response. You can use either a Python-based solution or a binary version that doesn't need Python.
32
+
If you have issues with Microsoft Defender for Endpoint on Linux and need support, you might be asked to provide the output from the Client Analyzer tool. It is a diagnostic tool which help administrators and support teams troubleshoot issues with Microsoft Defender for Endpoint. It collects detailed information about installation, configuration, service health, logs, connectivity status, etc. This tool is primarily used for checking system health, validating configurations, and helping troubleshoot potential issues.
33
+
34
+
This article explains how to use the tool on your device or with live response. You can use either a Python-based solution or a binary version that doesn't need Python.
33
35
34
36
> [!TIP]
35
37
> Watch this video to get an overview of the client analyzer: [Defender for Endpoint client analyzer overview](https://www.youtube.com/watch?v=GnqDsvYYL6w)
36
38
37
-
## Running the binary version of the client analyzer
39
+
## Run the binary version of the client analyzer
40
+
The binary version of client analyzer is made available in two ways:
41
+
- Shipped with Microsoft Defender for Linux
42
+
- Shipped as a standalone tool
38
43
39
-
### Run ClientAnalyzer binary shipped MDE:
44
+
### Run the Client Analyzer binary shipped with Microsoft Defender for Linux:
40
45
> [!NOTE]
41
-
> Starting with the Defender for Endpoint version `101.25062.0000`, the Client Analyzer is shipped with agent. It can be found at the location `/opt/microsoft/mdatp/conf/client_analyzer/binary`
46
+
> Starting with the Defender for Endpoint version `101.25082.0000`, the Client Analyzer is shipped with an agent. It can be found at the following location: `/opt/microsoft/mdatp/tools/client_analyzer/binary`
47
+
48
+
To run this client analyzer follow these steps:
42
49
43
-
To run this client analyzer follow the steps:
44
-
1. Go to directory `/opt/microsoft/mdatp/conf/client_analyzer/binary`:
50
+
1. Go to the directory `/opt/microsoft/mdatp/tools/client_analyzer/binary`:
45
51
46
52
```bash
47
-
cd /opt/microsoft/mdatp/conf/client_analyzer/binary
53
+
cd /opt/microsoft/mdatp/tools/client_analyzer/binary
48
54
```
49
-
2. Run the tool as _root_ to generate diagnostic package:
55
+
2. Run the tool as _root_ to generate a diagnostic package:
50
56
51
57
```bash
52
58
sudo ./MDESupportTool -d
53
59
```
54
-
### Download and run ClientAnalyzer binary
60
+
### Download and run the Client Analyzer standalone binary tool
55
61
56
-
Follow the below steps if you are using Defender for Endpoint older than `101.25062.0000`
62
+
Follow the steps below to use the standalone ClientAnalyzer binary
57
63
58
-
1. Download the [XMDE Client Analyzer Binary](https://aka.ms/XMDEClientAnalyzerBinary) tool to the Linux machine that you're to investigating. If you're using a terminal, download the tool by entering the following command:
64
+
1. Download the [XMDE Client Analyzer Binary](https://aka.ms/XMDEClientAnalyzerBinary) tool to the Linux machine that you need to investigate. If you're using a terminal, download the tool by entering the following command:
3. Extract the contents of `XMDEClientAnalyzerBinary.zip` on the machine.
@@ -81,21 +87,26 @@ Follow the below steps if you are using Defender for Endpoint older than `101.25
81
87
82
88
5. Two new zip files are produced:
83
89
84
-
- **SupportToolLinuxBinary.zip**: For all Linux devices
85
-
- **SupportToolMacOSBinary.zip**: For Mac devices
90
+
- **SupportToolLinuxamd64Binary.zip**: For x86 Linux devices
91
+
- **SupportToolLinuxarm64Binary.zip**: For ARM Linux devices
86
92
87
-
6. Unzip `SupportToolLinuxBinary.zip` file.
93
+
6. Unzip the sepecific zip based on your Linux OS architecture. For example, we use here the `SupportToolLinuxamd64Binary.zip` file.
88
94
89
95
```bash
90
-
unzip -q SupportToolLinuxBinary.zip
96
+
unzip -q SupportToolLinuxamd64Binary.zip
91
97
```
92
-
7. Run the tool as _root_ to generate diagnostic package:
98
+
7. Run the tool as _root_ to generate a diagnostic package:
93
99
94
100
```bash
95
101
sudo ./MDESupportTool -d
96
102
```
97
103
98
-
## Running the Python-based client analyzer
104
+
## Run the Python-based client analyzer
105
+
106
+
The python version of client analyzer is made available in two ways:
107
+
108
+
- Shipped with Microsoft Defender for Linux
109
+
- Shipped as a standalone tool
99
110
100
111
> [!NOTE]
101
112
> - The analyzer depends on a few extra PIP packages (`decorator`, `sh`, `distro`, `lxml`, and `psutil`) which are installed in the operating system when in root to produce the result output. If not installed, the analyzer attempts to fetch it from the [official repository for Python packages](https://pypi.org/search/?q=lxml).
@@ -105,15 +116,17 @@ Follow the below steps if you are using Defender for Endpoint older than `101.25
105
116
> [!WARNING]
106
117
> Running the Python-based client analyzer requires the installation of PIP packages which could cause some issues in your environment. To avoid issues from occurring, we recommend that you install the packages into a user PIP environment.
107
118
108
-
### Run ClientAnalyzer python version shipped MDE
119
+
### Run Client Analyzer python version shipped with Microsoft Defender for Linux
120
+
109
121
> [!NOTE]
110
-
> Starting with the Defender for Endpoint version `101.25062.0000`, the Client Analyzer is shipped with agent. It can be found at the location `/opt/microsoft/mdatp/conf/client_analyzer/python`
122
+
> Starting with the Defender for Endpoint version `101.25082.0000`, the Client Analyzer is shipped with an agent. It can be found at the following location: `/opt/microsoft/mdatp/tools/client_analyzer/python`
123
+
124
+
To run this client analyzer follow these steps:
111
125
112
-
To run this client analyzer follow the steps:
113
-
1. Go to directory `/opt/microsoft/mdatp/conf/client_analyzer/python`:
126
+
1. Go to directory `/opt/microsoft/mdatp/tools/client_analyzer/python`:
114
127
115
128
```bash
116
-
cd /opt/microsoft/mdatp/conf/client_analyzer/python
129
+
cd /opt/microsoft/mdatp/tools/client_analyzer/python
117
130
```
118
131
2. Run as a root user to install required dependencies.
119
132
@@ -126,45 +139,45 @@ To run this client analyzer follow the steps:
126
139
sudo ./mde_support_tool.sh -d
127
140
```
128
141
129
-
### Download and run ClientAnalyzer python version
142
+
### Download and run the Client Analyzer standalone python version
130
143
131
144
1. Download the [XMDE Client Analyzer](https://aka.ms/XMDEClientAnalyzer) tool on the Linux machine you need to investigate. If you're using a terminal, download the tool by entering the following command:
6. Run as a nonroot user to install required dependencies.
174
+
6. Run as a nonroot user to install required dependencies:
162
175
163
176
```bash
164
177
./mde_support_tool.sh
165
178
```
166
179
167
-
7. To collect the diagnostic package and generate the result archive file, run again as root.
180
+
7. To collect the diagnostic package and generate the result archive file, run again as root:
168
181
169
182
```bash
170
183
sudo ./mde_support_tool.sh -d
@@ -174,7 +187,8 @@ To run this client analyzer follow the steps:
174
187
> Watch this video to learn more about onboarding issues: [Defender for Endpoint client analyzer onboarding issues](https://www.youtube.com/watch?v=HdhePgMBqs8)
175
188
176
189
## Command line options
177
-
Below are the command line options provided by client analyzer
190
+
191
+
Below are the command line options provided by client analyzer:
178
192
179
193
```console
180
194
@@ -237,8 +251,7 @@ optional arguments:
237
251
238
252
### Diagnostics mode
239
253
240
-
Diagnostics mode is used to collect extensive set of machine information, such as memory, disk, and MDATP logs.
241
-
This set of files gives the primary set of information required to debug any issue related to Defender For Endpoint.
254
+
Diagnostics mode is used to collect extensive set of machine information, such as memory, disk, and MDATP logs. This set of files gives the primary set of information required to debug any issue related to Defender For Endpoint.
242
255
243
256
The options supported are as follows:
244
257
@@ -339,6 +352,7 @@ The files generated when using this mode are summarized in the following table:
339
352
|`top_summary.txt`| Memory and CPU usage analytics of the process running |
340
353
341
354
### Optional arguments for Client Analyzer
355
+
342
356
Client Analyzer provides the following optional arguments for extra data collection:
343
357
344
358
#### Collect performance info
@@ -453,7 +467,8 @@ This mode adds exclusions for `audit-d` monitoring.
453
467
454
468
```
455
469
456
-
Usage example:
470
+
Usage example:
471
+
457
472
```console
458
473
sudo ./MDESupportTool exclude -d /var/foo/bar`
459
474
```
@@ -470,6 +485,7 @@ This option sets the rate limit globally for AuditD causing a drop in all the au
470
485
```
471
486
472
487
Usage example:
488
+
473
489
```console
474
490
sudo ./mde_support_tool.sh ratelimit -e true
475
491
```
@@ -489,6 +505,7 @@ This option enables you to skip the faulty rules added in the auditd rules file
@@ -511,8 +528,8 @@ The XMDE Client Analyzer tool can be downloaded as a [binary](https://aka.ms/XMD
511
528
512
529
Download and extract the XMDE Client Analyzer. You can use either the binary or Python version, as follows:
513
530
514
-
- [Binary version of the Client Analyzer](run-analyzer-linux.md#running-the-binary-version-of-the-client-analyzer)
515
-
- [Python version of the Client Analyzer](run-analyzer-linux.md#running-the-python-based-client-analyzer)
531
+
- [Binary version of the Client Analyzer](run-analyzer-linux.md#run-the-binary-version-of-the-client-analyzer)
532
+
- [Python version of the Client Analyzer](run-analyzer-linux.md#run-the-python-based-client-analyzer)
516
533
517
534
Due to the limited commands available in live response, the steps detailed must be executed in a bash script. By splitting the installation and execution portion of these commands, it's possible to run the install script once, and run the execution script multiple times.
518
535
@@ -521,7 +538,7 @@ Due to the limited commands available in live response, the steps detailed must
521
538
522
539
#### Binary client analyzer install script
523
540
524
-
The following script performs the first six steps of the [Running the Binary version of the Client Analyzer](run-analyzer-linux.md#running-the-binary-version-of-the-client-analyzer). When complete, the XMDE Client Analyzer binary is available from the `/tmp/XMDEClientAnalyzerBinary/ClientAnalyzer` directory.
541
+
The following script performs the first six steps of the [Running the Binary version of the Client Analyzer](run-analyzer-linux.md#run-the-binary-version-of-the-client-analyzer). When complete, the XMDE Client Analyzer binary is available from the `/tmp/XMDEClientAnalyzerBinary/ClientAnalyzer` directory.
525
542
526
543
1. Create a bash file `InstallXMDEClientAnalyzer.sh` and paste the following content into it.
527
544
@@ -547,7 +564,7 @@ The following script performs the first six steps of the [Running the Binary ver
547
564
548
565
#### Python client analyzer install script
549
566
550
-
The following script performs the first six steps of the [Running the Python version of the Client Analyzer](run-analyzer-linux.md#running-the-python-based-client-analyzer). When complete, the XMDE Client Analyzer Python scripts are available from the `/tmp/XMDEClientAnalyzer` directory.
567
+
The following script performs the first six steps of the [Running the Python version of the Client Analyzer](run-analyzer-linux.md#run-the-python-based-client-analyzer). When complete, the XMDE Client Analyzer Python scripts are available from the `/tmp/XMDEClientAnalyzer` directory.
551
568
552
569
1. Create a bash file `InstallXMDEClientAnalyzer.sh` and paste the following content into it.
553
570
@@ -673,8 +690,6 @@ The Python version of the client analyzer accepts command line parameters to per
673
690
674
691
- [Address false positives/negatives in Microsoft Defender for Endpoint](/defender-endpoint/defender-endpoint-false-positives-negatives)
675
692
676
-
677
-
678
693
[!INCLUDE [Microsoft Defender for Endpoint Tech Community](../includes/defender-mde-techcommunity.md)]
0 commit comments