Skip to content

Commit cbea362

Browse files
committed
Learn Editor: Update run-analyzer-linux.md
1 parent f5fce55 commit cbea362

File tree

1 file changed

+43
-11
lines changed

1 file changed

+43
-11
lines changed

defender-endpoint/run-analyzer-linux.md

Lines changed: 43 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -189,6 +189,39 @@ This section provides instructions on how to run the tool locally on the Linux m
189189

190190
### Run the binary version of the client analyzer
191191

192+
Summary:
193+
194+
1. Obtain from [https://aka.ms/xmdeclientanalyzerbinary](https://aka.ms/xmdeclientanalyzerbinary)
195+
196+
or if your Linux server has internet access use wget to download the file
197+
198+
199+
```bash
200+
wget --quiet -O XMDEClientAnalyzerBinary.zip https://aka.ms/XMDEClientAnalyzerBinary
201+
```
202+
203+
1. Unzip the file that is downloaded, and then of the extracted files unzip again the SupportToolLinuxBinary.zip
204+
205+
206+
```bash
207+
unzip -q XMDEClientAnalyzerBinary.zip -d XMDEClientAnalyzerBinary
208+
209+
```
210+
211+
1. Run the binary
212+
213+
```
214+
sudo ./MDESupportTool -d --mdatp-log debug
215+
```
216+
217+
1. Follow the on-screen instructions and then follow up with at the end of the log collection, the logs will be located in the /tmp directory
218+
219+
1. The log set will be owned by root user so you may need root privileges to remove the log set
220+
221+
1. Upload the file for the support engineer
222+
223+
Details:
224+
192225
1. Download the [XMDE Client Analyzer Binary](https://aka.ms/XMDEClientAnalyzerBinary) tool to the Linux machine you need to investigate.
193226

194227
If you're using a terminal, download the tool by entering the following command:
@@ -217,18 +250,17 @@ This section provides instructions on how to run the tool locally on the Linux m
217250
cd XMDEClientAnalyzerBinary
218251
```
219252

220-
4. Two new zip files are produced:
253+
1. Two new zip files are produced:
221254

222255
- `SupportToolLinuxBinary.zip`: For all Linux devices
223-
- `SupportToolMacOSBinary.zip`: For Mac devices
224-
225-
5. Depending on the operating system, unzip the appropriate file for the machine you want to investigate.
226-
227-
| OS type | Command |
228-
|--|--|
229-
| Linux | `unzip -q SupportToolLinuxBinary.zip` |
230-
| Mac | `unzip -q SupportToolMacOSBinary.zip` |
256+
- `SupportToolMacOSBinary.zip`: For Mac devices, ignore this one.
257+
258+
1. Unzip the SupportToolLinuxBinary.zip for the Linux machine you want to investigate.
231259

260+
```bash
261+
unzip -q SupportToolLinuxBinary.zip
262+
```
263+
232264
6. Run the tool as root to generate diagnostic package:
233265

234266
```bash
@@ -245,11 +277,11 @@ This section provides instructions on how to run the tool locally on the Linux m
245277
> [!WARNING]
246278
> Running the Python-based client analyzer requires the installation of PIP packages which may cause some issues in your environment. To avoid issues from occurring, it is recommended that you install the packages into a user PIP environment.
247279
248-
1. Download the [XMDE Client Analyzer](https://aka.ms/XMDEClientAnalyzer) tool to the macOS or Linux machine you need to investigate.
280+
1. Download the [XMDE Client Analyzer](https://aka.ms/XMDEClientAnalyzer) tool to the Linux machine you need to investigate.
249281

250282
If you're using a terminal, download the tool by running the following command:
251283

252-
```bash
284+
```bash
253285
wget --quiet -O XMDEClientAnalyzer.zip https://aka.ms/XMDEClientAnalyzer
254286
```
255287

0 commit comments

Comments
 (0)