From c9c874eb7e2d7f3ae55f9dae61317d4e7b6c4aac Mon Sep 17 00:00:00 2001 From: Tudor Dobrila Date: Tue, 18 Feb 2020 22:41:16 -0800 Subject: [PATCH] More details; cleanup --- .../microsoft-defender-atp/linux-install-manually.md | 4 ++-- .../linux-install-with-ansible.md | 6 +++++- .../linux-install-with-puppet.md | 11 ++++++----- 3 files changed, 13 insertions(+), 8 deletions(-) diff --git a/windows/security/threat-protection/microsoft-defender-atp/linux-install-manually.md b/windows/security/threat-protection/microsoft-defender-atp/linux-install-manually.md index a7d5745aeb..cbb09354b6 100644 --- a/windows/security/threat-protection/microsoft-defender-atp/linux-install-manually.md +++ b/windows/security/threat-protection/microsoft-defender-atp/linux-install-manually.md @@ -189,7 +189,7 @@ Download the onboarding package from Microsoft Defender Security Center: $ ls -l total 8 -rw-r--r-- 1 test staff 5752 Feb 18 11:22 WindowsDefenderATPOnboardingPackage.zip - + $ unzip WindowsDefenderATPOnboardingPackage.zip Archive: WindowsDefenderATPOnboardingPackage.zip inflating: WindowsDefenderATPOnboarding.py @@ -218,7 +218,7 @@ Download the onboarding package from Microsoft Defender Security Center: [your organization identifier] ``` -4. A few minutes following the completion of the installation, you can see the status by running the following command. A return value of `'1'` denotes that the product is functioning as expected. +4. A few minutes following the completion of the installation, you can see the status by running the following command. A return value of `1` denotes that the product is functioning as expected. ```bash $ mdatp --health healthy diff --git a/windows/security/threat-protection/microsoft-defender-atp/linux-install-with-ansible.md b/windows/security/threat-protection/microsoft-defender-atp/linux-install-with-ansible.md index e45283ab7d..471190a7e3 100644 --- a/windows/security/threat-protection/microsoft-defender-atp/linux-install-with-ansible.md +++ b/windows/security/threat-protection/microsoft-defender-atp/linux-install-with-ansible.md @@ -77,7 +77,7 @@ Download the onboarding package from Microsoft Defender Security Center: ## Create Ansible YAML files -Create subtask / role files which contribute to an actual task. Create below files under `/etc/ansible/roles` directory. +Create subtask / role files which contribute to an actual task. Create the below files under the `/etc/ansible/roles` directory. - Copy onboarding package to all client machines @@ -238,6 +238,10 @@ Now run the tasks files under `/etc/ansible/playbooks/` `# ansible-playbook /etc/ansible/playbooks/uninstall_mdatp.yml -i /etc/ansible/hosts` +## Logging installation issues + +See [Logging installation issues](linux-resources.md#logging-installation-issues) for more information on how to find the automatically generated log that is created by the installer when an error occurs. + ## References - [Add or remove YUM repositories](https://docs.ansible.com/ansible/2.3/yum_repository_module.html) diff --git a/windows/security/threat-protection/microsoft-defender-atp/linux-install-with-puppet.md b/windows/security/threat-protection/microsoft-defender-atp/linux-install-with-puppet.md index dfd667c83c..5fdc1c6ff3 100644 --- a/windows/security/threat-protection/microsoft-defender-atp/linux-install-with-puppet.md +++ b/windows/security/threat-protection/microsoft-defender-atp/linux-install-with-puppet.md @@ -35,7 +35,7 @@ This topic describes how to deploy Microsoft Defender ATP for Linux through Pupp 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. -In addition, for Puppet deployment, you need to be familiar with Puppet administration tasks, have a 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. ## Download onboarding package @@ -53,6 +53,7 @@ Download the onboarding package from Microsoft Defender Security Center: $ ls -l total 8 -rw-r--r-- 1 test staff 4984 Feb 18 11:22 WindowsDefenderATPOnboardingPackage.zip + $ unzip WindowsDefenderATPOnboardingPackage.zip Archive: WindowsDefenderATPOnboardingPackage.zip inflating: mdatp_onboard.json ``` @@ -152,9 +153,9 @@ orgId : "[your organization identifier]" ... ``` -- **licensed**: This confirms that the device has an ATP license. +- **licensed**: This confirms that the device is tied to your organization. -- **orgid**: your Microsoft Defender ATP org id; it will be the same for your organization. +- **orgId**: your Microsoft Defender ATP organization identifier. ## Check onboarding status @@ -164,12 +165,12 @@ You can check that devices have been correctly onboarded by creating a script. F $ mdatp --health healthy ``` -The above command prints "1" if the product is onboarded and functioning as expected. +The above command prints `1` if the product is onboarded and functioning as expected. If the product is not healthy, the exit code (which can be checked through `echo $?`) indicates the problem: - 1 if the device is not yet onboarded -- 3 if the connection to the daemon cannot be established—for example, if the daemon is not running +- 3 if the connection to the daemon cannot be established ## Logging installation issues