deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-06-21 13:23:36 +00:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

More details; cleanup

Browse Source
This commit is contained in:
Tudor Dobrila
2020-02-18 22:41:16 -08:00
parent 57b1726dd4
commit c9c874eb7e
3 changed files with 13 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
windows/security/threat-protection/microsoft-defender-atp/linux-install-manually.md
View File

@ -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

6
windows/security/threat-protection/microsoft-defender-atp/linux-install-with-ansible.md
View File

@ -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)

11
windows/security/threat-protection/microsoft-defender-atp/linux-install-with-puppet.md
View File

@ -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