Microsoft Defender for Endpoint
Endpoint protection

Run Analyzer Linux

In brief

The guide now lists three ways to collect diagnostics: locally from the command line, remotely through live response, or through an investigation package from the device page. On Linux, investigation packages include Client Analyzer diagnostics.

What Defender admins need to know

Administrators can use the documented collection method that best fits their investigation workflow; no configuration change is required.

Summaries are generated from the documentation change itself.

Documentation change

The comparison below shows only the changed extract. Use the full-page view for complete context.

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's a diagnostic tool that helps 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.

This article explains how to use the tool on your device or with live response. You can use eithercollect Client Analyzer diagnostics in any of the following ways:

  1. Command line: Run the Client Analyzer locally on the device. See run-the-binary-version-of-the-client-analyzer or run-the-python-based-client-analyzer.
  2. Live response: Run the Client Analyzer remotely during a Python-based solution or a binary version that doesn't need Python.

    live response session. See use-live-response-to-collect-diagnostics-log
  3. Investigation package: Collect an investigation package from the device page in the Microsoft Defender portal. On Linux, the package includes Client Analyzer diagnostics. See collect-investigation-package-from-devices

Tip