Skip to content

Commit 0468504

Browse files
authored
Merge branch 'main' into v-smandalika-9792656-B3
2 parents 3d919ea + 745f0f6 commit 0468504

File tree

2 files changed

+54
-21
lines changed

2 files changed

+54
-21
lines changed

defender-endpoint/api/get-assessment-software-vulnerabilities.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -395,7 +395,7 @@ Each returned record contains all the data from the full export software vulnera
395395
|ExploitabilityLevel|String|The exploitability level of this vulnerability (NoExploit, ExploitIsPublic, ExploitIsVerified, ExploitIsInKit)|ExploitIsInKit|
396396
|FirstSeenTimestamp|String|First time the CVE of this product was seen on the device.|2020-11-03 10:13:34.8476880|
397397
|ID|String|Unique identifier for the record.|123ABG55_573AG&mnp!|
398-
|LastSeenTimestamp|String|Last time the CVE was reported on the device.|2020-11-03 10:13:34.8476880|
398+
|LastSeenTimestamp|String|Last time the software was reported on the device.|2020-11-03 10:13:34.8476880|
399399
|OSPlatform|String|Platform of the operating system running on the device; specific operating systems with variations within the same family, such as Windows 10 and Windows 11. See Microsoft Defender Vulnerability Management supported operating systems and platforms for details.|Windows10 and Windows 11|
400400
|RbacGroupName|String|The role-based access control (RBAC) group. If this device isn't assigned to any RBAC group, the value is "Unassigned." If the organization doesn't contain any RBAC groups, the value is "None."|Servers|
401401
|RecommendationReference|string|A reference to the recommendation ID related to this software.|va--microsoft--silverlight|

defender-endpoint/linux-install-manually.md

Lines changed: 53 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -2,8 +2,8 @@
22
title: Deploy Microsoft Defender for Endpoint on Linux manually
33
description: Describes how to deploy Microsoft Defender for Endpoint on Linux manually from the command line.
44
ms.service: defender-endpoint
5-
ms.author: deniseb
6-
author: denisebmsft
5+
ms.author: ewalsh
6+
author: emmwalshh
77
ms.reviewer: gopkr
88
ms.localizationpriority: medium
99
manager: deniseb
@@ -15,7 +15,7 @@ ms.collection:
1515
ms.topic: conceptual
1616
ms.subservice: linux
1717
search.appverid: met150
18-
ms.date: 02/10/2025
18+
ms.date: 02/11/2025
1919
---
2020

2121
# Deploy Microsoft Defender for Endpoint on Linux manually
@@ -50,10 +50,6 @@ In order to preview new features and provide early feedback, it's recommended th
5050
> [!WARNING]
5151
> Switching the channel after the initial installation requires the product to be reinstalled. To switch the product channel: uninstall the existing package, reconfigure your device to use the new channel, and follow the steps in this document to install the package from the new location.
5252
53-
## Installer script
54-
55-
To use the installer script method, see [Use the installer script to deploy Microsoft Defender for Endpoint on Linux](linux-installer-script.md).
56-
5753
## Application installation
5854

5955
### RHEL and variants (CentOS, Fedora, Oracle Linux, Amazon Linux 2, Rocky, and Alma)
@@ -198,7 +194,7 @@ Download the onboarding package from Microsoft Defender portal.
198194
> To run this command, you must have `python` or `python3` installed on the device depending on the distro and version. If needed, see [Step-by-step Instructions for Installing Python on Linux](https://opensource.com/article/20/4/install-python-linux).
199195
200196
> [!NOTE]
201-
> To onboard a device that was previously offboarded you must remove the mdatp_offboard.json file located at /etc/opt/microsoft/mdatp.
197+
> To onboard a device that was previously offboard, you must remove the mdatp_offboard.json file located at /etc/opt/microsoft/mdatp.
202198
203199
If you're running RHEL 8.x or Ubuntu 20.04 or higher, you need to use `python3`.
204200

@@ -225,11 +221,11 @@ Download the onboarding package from Microsoft Defender portal.
225221
```
226222

227223
> [!IMPORTANT]
228-
> When the product starts for the first time, it downloads the latest anti-malware definitions. This process may take up to a few minutes depending on the network connectivity. During this time, the command mentioned earlier returns a value of `false`. You can check the status of the definition update using the following command:
224+
> When the product starts for the first time, it downloads the latest anti-malware definitions. This process might take up to a few minutes depending on the network connectivity. During this time, the command mentioned earlier returns a value of `false`. You can check the status of the definition update using the following command:
229225
>
230226
> `mdatp health --field definitions_status`
231227
>
232-
> Note that you may also need to configure a proxy after completing the initial installation. See [Configure Defender for Endpoint on Linux for static proxy discovery: Post-installation configuration](linux-static-proxy-configuration.md#post-installation-configuration).
228+
> You might also need to configure a proxy after completing the initial installation. See [Configure Defender for Endpoint on Linux for static proxy discovery: Post-installation configuration](linux-static-proxy-configuration.md#post-installation-configuration).
233229
234230
1. Run an AV detection test to verify that the device is properly onboarded and reporting to the service. Perform the following steps on the newly onboarded device:
235231

@@ -284,7 +280,7 @@ The following external package dependencies exist for the mdatp package:
284280
285281
> [!NOTE]
286282
> Starting with version `101.24082.0004`, Defender for Endpoint on Linux no longer supports the `Auditd` event provider. We're transitioning completely to the more efficient eBPF technology.
287-
> If eBPF is not supported on your machines, or if there are specific requirements to remain on Auditd, and your machines are using Defender for Endpoint on Linux version `101.24072.0001` or lower, the following other dependencies on the auditd package exist for mdatp:
283+
> If eBPF isn't supported on your machines, or if there are specific requirements to remain on Auditd, and your machines are using Defender for Endpoint on Linux version `101.24072.0001` or lower, the following other dependencies on the auditd package exist for mdatp:
288284
> - The mdatp RPM package requires `audit`, `semanage`.
289285
> - For DEBIAN, the mdatp package requires `auditd`.
290286
> - For Mariner, the mdatp package requires `audit`.
@@ -298,19 +294,32 @@ The `mde-netfilter` package also has the following package dependencies:
298294
If the Microsoft Defender for Endpoint installation fails due to missing dependencies errors, you can manually download the prerequisite dependencies.
299295
300296
301-
## Log installation issues
297+
## Troubleshoot installation issues
298+
299+
- For details on how to find the log that's generated when an installation error occurs, see [Log installation issues](/defender-endpoint/linux-resources#log-installation-issues).
300+
301+
- For information about common installation issues, see [Installation issues](/defender-endpoint/linux-support-install).
302+
303+
- If the health of the device is false, see [Investigate agent health issues](health-status.md).
302304

303-
See [Log installation issues](linux-resources.md#log-installation-issues) for more information on how to find the automatically generated log that is created by the installer when an error occurs.
305+
- For product performance issues, see [Troubleshoot performance issues for Microsoft Defender for Endpoint on Linux](linux-support-perf.md).
304306

305-
## How to migrate from Insiders-Fast to Production channel
307+
- For proxy and connectivity issues, see [Troubleshoot cloud connectivity issues for Microsoft Defender for Endpoint on Linux](linux-support-connectivity.md).
308+
309+
- To get support from Microsoft, open a support ticket, and provide the log files created by using the [Microsoft Defender for Endpoint client analyzer tool](run-analyzer-linux.md).
310+
311+
312+
## How to switch between channels
313+
314+
For example, to change channel from Insiders-Fast to Production, do the following:
306315

307316
1. Uninstall the `Insiders-Fast channel` version of Defender for Endpoint on Linux.
308317

309318
```bash
310319
sudo yum remove mdatp
311320
```
312321

313-
1. Disable the Defender for Endpoint on Linux Insiders-Fast repo
322+
2. Disable the Defender for Endpoint on Linux Insiders-Fast repo.
314323

315324
```bash
316325
sudo yum repolist
@@ -323,14 +332,38 @@ See [Log installation issues](linux-resources.md#log-installation-issues) for mo
323332
sudo yum-config-manager --disable packages-microsoft-com-fast-prod
324333
```
325334

326-
1. Redeploy Microsoft Defender for Endpoint on Linux using the Production channel.
335+
3. Redeploy Microsoft Defender for Endpoint on Linux using the Production channel.
336+
337+
Defender for Endpoint on Linux can be deployed from one of the following channels (denoted as [channel]): 
338+
339+
- `insiders-fast`
340+
- `insiders-slow`
341+
- `prod`
342+
343+
Each of these channels corresponds to a Linux software repository. This article describes how to configure your device to use one of these repositories.
344+
345+
The choice of channel determines the type and frequency of updates that are offered to your device. Devices in insiders-fast are the first to receive updates and new features, followed later by insiders-slow and lastly by prod.
346+
347+
In order to preview new features and provide early feedback, it's recommended that you configure some devices in your enterprise to use either `insiders-fast` or `insiders-slow`.
348+
349+
> [!WARNING]
350+
> Switching channels after the initial installation requires the product to be reinstalled. To switch the product channel: uninstall the existing package, reconfigure your device to use the new channel, and follow the steps in this document to install the package from the new location.
351+
352+
## How to configure policies for Microsoft Defender for Endpoint on Linux
353+
354+
You can configure antivirus and EDR settings on your endpoints. For more information, see the following articles:
355+
356+
- [Set preferences for Microsoft Defender for Endpoint on Linux](/defender-endpoint/linux-preferences) describes the available settings
357+
- [Security settings management](/mem/intune/protect/mde-security-integration) describes how to configure settings in the Microsoft Defender portal.
327358
328-
## Uninstallation
359+
## Uninstall Microsoft Defender for Endpoint on Linux
329360
330-
See [Uninstall](linux-resources.md#uninstall-defender-for-endpoint-on-linux) for details on how to remove Defender for Endpoint on Linux from client devices.
361+
For manual uninstallation, execute the below command as per your Linux distribution.
331362
332-
## See also
363+
- `sudo yum remove mdatp` for RHEL and variants(CentOS and Oracle Linux).
364+
- `sudo zypper remove mdatp` for SLES and variants.
365+
- `sudo apt-get purge mdatp` for Ubuntu and Debian systems.
366+
- `sudo dnf remove mdatp` for Mariner
333367
334-
- [Investigate agent health issues](health-status.md)
335368
336369
[!INCLUDE [Microsoft Defender for Endpoint Tech Community](../includes/defender-mde-techcommunity.md)]

0 commit comments

Comments
 (0)