Skip to content

Commit bf69017

Browse files
committed
Update run-analyzer-macos-linux.md
1 parent 6f6ff7c commit bf69017

File tree

1 file changed

+17
-17
lines changed

1 file changed

+17
-17
lines changed

defender-endpoint/run-analyzer-macos-linux.md

Lines changed: 17 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -52,9 +52,7 @@ If you're using a terminal, download the tool by entering the following command:
5252
```
5353

5454

55-
2. Extract the contents of _XMDEClientAnalyzerBinary.zip_ on the machine.
56-
57-
If you're using a terminal, extract the files by entering the following command:
55+
2. Extract the contents of `XMDEClientAnalyzerBinary.zip` on the machine. If you're using a terminal, extract the files by entering the following command:
5856
5957
```bash
6058
unzip -q XMDEClientAnalyzerBinary.zip -d XMDEClientAnalyzerBinary
@@ -71,9 +69,7 @@ If you're using a terminal, download the tool by entering the following command:
7169
- **SupportToolLinuxBinary.zip** : For all Linux devices
7270
- **SupportToolMacOSBinary.zip** : For Mac devices
7371

74-
5. Unzip one of the above 2 zip files based on the machine you need to investigate.
75-
76-
When using a terminal, unzip the file by entering one of the following commands based on OS type:
72+
5. Unzip one of the above 2 zip files based on the machine you need to investigate. When using a terminal, unzip the file by entering one of the following commands based on OS type:
7773

7874
- Linux
7975

@@ -103,15 +99,13 @@ If you're using a terminal, download the tool by entering the following command:
10399
> [!WARNING]
104100
> 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.
105101
106-
1. Download the [XMDE Client Analyzer](https://aka.ms/XMDEClientAnalyzer) tool to the macOS or Linux machine you need to investigate.
107-
108-
If you're using a terminal, download the tool by running the following command:
102+
1. Download the [XMDE Client Analyzer](https://aka.ms/XMDEClientAnalyzer) tool to the macOS or Linux machine you need to investigate. If you're using a terminal, download the tool by running the following command:
109103
110104
```bash
111105
wget --quiet -O XMDEClientAnalyzer.zip https://aka.ms/XMDEClientAnalyzer
112106
```
113107
114-
2. Verify the download
108+
2. Verify the download.
115109
116110
- Linux
117111
@@ -125,8 +119,7 @@ If you're using a terminal, download the tool by entering the following command:
125119
echo '84C9718FF3D29DA0EEE650FB2FC0625549A05CD1228AC253DBB92C8B1D9F1D11 XMDEClientAnalyzer.zip' | shasum -a 256 -c
126120
```
127121
128-
3. Extract the contents of XMDEClientAnalyzer.zip on the machine.
129-
If you're using a terminal, extract the files by using the following command:
122+
3. Extract the contents of XMDEClientAnalyzer.zip on the machine. If you're using a terminal, extract the files by using the following command:
130123
131124
```bash
132125
unzip -q XMDEClientAnalyzer.zip -d XMDEClientAnalyzer
@@ -138,19 +131,19 @@ If you're using a terminal, download the tool by entering the following command:
138131
cd XMDEClientAnalyzer
139132
```
140133
141-
5. Give the tool executable permission:
134+
5. Give the tool executable permission.
142135
143136
```bash
144137
chmod a+x mde_support_tool.sh
145138
```
146139
147-
6. Run as a non-root user to install required dependencies:
140+
6. Run as a non-root user to install required dependencies.
148141
149142
```bash
150143
./mde_support_tool.sh
151144
```
152145
153-
7. To collect actual diagnostic package and generate the result archive file, run again as root:
146+
7. To collect actual diagnostic package and generate the result archive file, run again as root.
154147
155148
```bash
156149
sudo ./mde_support_tool.sh -d
@@ -161,6 +154,7 @@ If you're using a terminal, download the tool by entering the following command:
161154
### All command line options
162155
163156
```console
157+
164158
usage: MDESupportTool [-h] [--output OUTPUT] [--outdir OUTDIR] [--no-zip]
165159
[--force] [--diagnostic] [--skip-mdatp]
166160
[--bypass-disclaimer] [--interactive] [--delay DELAY]
@@ -215,15 +209,18 @@ optional arguments:
215209
--max-log-size MAX_LOG_SIZE
216210
Maximum log file size in MB before rotating(Will
217211
restart mdatp).
212+
218213
```
219214
220215
### Diagnostics mode
221216
222217
This is used to collected etensive set of machine information, such as memory, disk, MDATP logs, etc.
223218
These set of files give us primary set of information required to debug any issue related to MDE.
224219
225-
The options supported for this is:
220+
The options supported are as follows:
221+
226222
```console
223+
227224
optional arguments:
228225
-h, --help show this help message and exit
229226
--output OUTPUT, -o OUTPUT
@@ -247,10 +244,13 @@ optional arguments:
247244
--max-log-size MAX_LOG_SIZE
248245
Maximum log file size in MB before rotating(Will
249246
restart mdatp).
247+
250248
```
249+
251250
Usage example: `sudo ./MDESupportTool -d`
252251
253-
NOTE: The log level auto-reset feature only available in 2405 or newer client version.
252+
> [!NOTE]
253+
> The log level auto-reset feature only available in 2405 or newer client version.
254254
255255
The files generated when using this mode:
256256
| File | Remarks |

0 commit comments

Comments
 (0)