@@ -342,6 +342,37 @@ The data file can be read using the command:
342
342
343
343
` perf report -i <pid>.data`
344
344
345
+ # ### Run connectivity test
346
+ This modes test if the cloud resources needed by MDE is reachable or not.
347
+
348
+ ` ` ` console
349
+ -h, --help show this help message and exit
350
+ -o ONBOARDING_SCRIPT, --onboarding-script ONBOARDING_SCRIPT
351
+ Path to onboarding script
352
+ -g GEO, --geo GEO Geo string to test < US| UK| EU| AU| CH| IN>
353
+ ` ` `
354
+ Usage example: ` sudo ./MDESupportTool connectivitytest -o ~ /MicrosoftDefenderATPOnboardingLinuxServer.py`
355
+
356
+ The result will be printed in the screen.
357
+
358
+
359
+ # ### Collect different installation/onboarding reports
360
+ This mode collects installation related info like disto info, system requirements, etc.
361
+
362
+ ` ` ` console
363
+ -h, --help show this help message and exit
364
+ -d, --distro Check for distro support
365
+ -a, --all Run all checks
366
+ ` ` `
367
+
368
+ Usage example: ` sudo ./MDESupportTool installation --all`
369
+
370
+ A single report ` installation_report.json` will be generated. The keys in the file are as:
371
+ | Key | Remarks |
372
+ | ------------- | ------------- |
373
+ | agent_version | Version of MDE installed |
374
+ | onboarding_status | The onboarding and ring info |
375
+
345
376
346
377
# ### Use OS trace (for macOS only)
347
378
0 commit comments