Merge pull request #7023 from jdmartinez36/jdmartinez36-linux-branch

[DO NOT MERGE] Edits for linux support articles
This commit is contained in:
Tina Burden 2020-07-06 14:51:32 -07:00 committed by GitHub
commit 734b9d9524
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
5 changed files with 61 additions and 58 deletions

View File

@ -33,7 +33,7 @@ This topic describes how to deploy Microsoft Defender ATP for Linux using Puppet
## Prerequisites and system requirements ## Prerequisites and system requirements
Before you get started, please see [the main Microsoft Defender ATP for Linux page](microsoft-defender-atp-linux.md) for a description of prerequisites and system requirements for the current software version. For a description of prerequisites and system requirements for the current software version, see [the main Microsoft Defender ATP for Linux page](microsoft-defender-atp-linux.md).
In addition, for Puppet deployment, you need to be familiar with Puppet administration tasks, have Puppet configured, and know how to deploy packages. Puppet has many ways to complete the same task. These instructions assume availability of supported Puppet modules, such as *apt* to help deploy the package. Your organization might use a different workflow. Please refer to the [Puppet documentation](https://puppet.com/docs) for details. In addition, for Puppet deployment, you need to be familiar with Puppet administration tasks, have Puppet configured, and know how to deploy packages. Puppet has many ways to complete the same task. These instructions assume availability of supported Puppet modules, such as *apt* to help deploy the package. Your organization might use a different workflow. Please refer to the [Puppet documentation](https://puppet.com/docs) for details.
@ -205,7 +205,7 @@ If the product is not healthy, the exit code (which can be checked through `echo
## Log installation issues ## Log installation issues
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. For more information on how to find the automatically generated log that is created by the installer when an error occurs, see [Log installation issues](linux-resources.md#log-installation-issues).
## Operating system upgrades ## Operating system upgrades

View File

@ -44,7 +44,7 @@ curl -w ' %{url_effective}\n' 'https://x.cp.wd.microsoft.com/api/report' 'https:
The output from this command should be similar to: The output from this command should be similar to:
``` ```bash
OK https://x.cp.wd.microsoft.com/api/report OK https://x.cp.wd.microsoft.com/api/report
OK https://cdn.x.cp.wd.microsoft.com/ping OK https://cdn.x.cp.wd.microsoft.com/ping
``` ```

View File

@ -27,19 +27,22 @@ ms.topic: conceptual
## Verify if installation succeeded ## Verify if installation succeeded
An error in installation may or may not result in a meaningful error message by the package manager. To verify if the installation succeeded, one can obtain and check the installation logs using: An error in installation may or may not result in a meaningful error message by the package manager. To verify if the installation succeeded, one can obtain and check the installation logs using:
```bash ```bash
$ sudo journalctl | grep 'microsoft-mdatp' > installation.log $ sudo journalctl | grep 'microsoft-mdatp' > installation.log
$ grep 'postinstall end' installation.log $ grep 'postinstall end' installation.log
microsoft-mdatp-installer[102243]: postinstall end [2020-03-26 07:04:43OURCE +0000] 102216 microsoft-mdatp-installer[102243]: postinstall end [2020-03-26 07:04:43OURCE +0000] 102216
``` ```
An output from the previous command with correct date and time of installation indicates success. An output from the previous command with correct date and time of installation indicates success.
Also check the [Client configuration](linux-install-manually.md#client-configuration) to verify the health of the product and detect the EICAR text file. Also check the [Client configuration](linux-install-manually.md#client-configuration) to verify the health of the product and detect the EICAR text file.
## Installation failed ## Installation failed
Check if the mdatp service is running Check if the mdatp service is running:
```bash ```bash
$ systemctl status mdatp $ systemctl status mdatp
@ -56,9 +59,9 @@ $ systemctl status mdatp
## Steps to troubleshoot if mdatp service isn't running ## Steps to troubleshoot if mdatp service isn't running
1. Check if “mdatp” user exists: 1. Check if "mdatp" user exists:
```bash ```bash
$ id “mdatp” $ id "mdatp"
``` ```
If theres no output, run If theres no output, run
```bash ```bash
@ -96,7 +99,7 @@ $ sudo chmod 0755 /opt/microsoft/mdatp/sbin/wdavdaemon
``` ```
and retry running step 2. and retry running step 2.
6. Ensure that the file system containing wdavdaemon isn't mounted with “noexec”. 6. Ensure that the file system containing wdavdaemon isn't mounted with "noexec".
## If mdatp service is running, but EICAR text file detection doesn't work ## If mdatp service is running, but EICAR text file detection doesn't work

View File

@ -81,4 +81,4 @@ The following steps can be used to troubleshoot and mitigate these issues:
4. Configure Microsoft Defender ATP for Linux with exclusions for the processes or disk locations that contribute to the performance issues and re-enable real-time protection. 4. Configure Microsoft Defender ATP for Linux with exclusions for the processes or disk locations that contribute to the performance issues and re-enable real-time protection.
See [Configure and validate exclusions for Microsoft Defender ATP for Linux](linux-exclusions.md) for details. For more details, see [Configure and validate exclusions for Microsoft Defender ATP for Linux](linux-exclusions.md).

View File

@ -27,7 +27,7 @@ ms.topic: conceptual
## 101.00.75 ## 101.00.75
- Added support for the following file system types: `ecryptfs`, `fuse`, `fuseblk`, `jfs`, `nfs`, `overlay`, `ramfs`, `reiserfs`, `udf`, and `vfat` - Added support for the following file system types: `ecryptfs`, `fuse`, `fuseblk`, `jfs`, `nfs`, `overlay`, `ramfs`, `reiserfs`, `udf`, and `vfat`
- New syntax for the command-line tool. For more information, see [this page](linux-resources.md#configure-from-the-command-line). - New syntax for the [command-line tool](linux-resources.md#configure-from-the-command-line).
- Performance improvements & bug fixes - Performance improvements & bug fixes
## 100.90.70 ## 100.90.70