You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: defender-endpoint/linux-install-with-puppet.md
+73-5Lines changed: 73 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -41,7 +41,7 @@ This article describes how to deploy Defender for Endpoint on Linux using Puppet
41
41
42
42
## Prerequisites and system requirements
43
43
44
-
For a description of prerequisites and system requirements for the current software version, see [the main Defender for Endpoint on Linux page](microsoft-defender-endpoint-linux.md).
44
+
For a description of prerequisites and system requirements, see [the main Defender for Endpoint on Linux page](microsoft-defender-endpoint-linux.md).
45
45
46
46
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. Refer to the [Puppet documentation](https://puppet.com/docs) for details.
47
47
@@ -111,7 +111,57 @@ You need to create a Puppet manifest for deploying Defender for Endpoint on Linu
111
111
└── init.pp
112
112
```
113
113
114
-
### Contents of `install_mdatp/manifests/init.pp`
114
+
### Create manifest file
115
+
116
+
There are two ways to create manifest:
117
+
118
+
1. create manifest using installer script
119
+
120
+
1. create manifest by configuring repositories manually
121
+
122
+
#### Create manifest to deploy Defender for Endpoint using Installer Script
123
+
124
+
Add below contents to the `install_mdatp/manifests/init.pp` file. You can also download the file directly from [GitHub](https://teams.microsoft.com/l/message/19:2c1dc910-b8b7-415a-a9fd-2cd04843b43c_cb7ab2ef-8a66-4fcf-8c66-1723507f52df@unq.gbl.spaces/1734343607885?context=%7B%22contextType%22%3A%22chat%22%7D)
125
+
126
+
```puppet
127
+
# Puppet manifest to install Microsoft Defender for Endpoint on Linux.
128
+
# @param channel The release channel based on your environment, insider-fast or prod.
129
+
130
+
class install_mdatp (
131
+
$channel = 'prod',
132
+
) {
133
+
# Ensure that the directory /tmp/mde_install exists
require => File['/tmp/mde_install/mde_installer.sh', '/tmp/mde_install/mdatp_onboard.json'], # Ensure the script is copied before running the installer
160
+
}
161
+
162
+
}
163
+
```
164
+
#### Create manifest to deploy Defender for Endpoint by configuring repositories manually
115
165
116
166
Defender for Endpoint on Linux can be deployed from one of the following channels:
117
167
@@ -135,6 +185,8 @@ In the below commands, replace *[distro]* and *[version]* with the information y
135
185
> [!NOTE]
136
186
> In case of RedHat, Oracle Linux, Amazon Linux 2, and CentOS 8, replace *[distro]* with 'rhel'.
137
187
188
+
Add below contents to the `install_mdatp/manifests/init.pp` file
189
+
138
190
```puppet
139
191
# Puppet manifest to install Microsoft Defender for Endpoint on Linux.
140
192
# @param channel The release channel based on your environment, insider-fast or prod.
@@ -202,7 +254,7 @@ class install_mdatp (
202
254
203
255
```
204
256
205
-
## Deployment
257
+
## Include the manifest inside the site.pp file
206
258
207
259
Include the above manifest in your `site.pp` file:
208
260
@@ -255,9 +307,25 @@ If the product is not healthy, the exit code (which can be checked through `echo
255
307
- `1`if the device isn't onboarded yet.
256
308
- `3` if the connection to the daemon cannot be established.
257
309
258
-
## Log installation issues
310
+
## Troubleshoot installation issues
311
+
312
+
For self-troubleshooting, do the following
313
+
314
+
1. Refer to [Log installation issues](https://github.com/meghapriyams/defender-docs-pr/blob/docs-editor/linux-install-with-ansible-1731590880/defender-endpoint/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.
315
+
316
+
1. Refer to [Installation issues](/defender-endpoint/linux-support-install) for more information on commonly occurring installation issues
317
+
318
+
1. If health of the device is false, refer to [MDE agent health issues](/defender-endpoint/health-status)
319
+
320
+
1. For product performance issues, refer to [Troubleshoot performance issues](/defender-endpoint/linux-support-perf), [performance tuning](/defender-endpoint/linux-support-perf?branch=main)
321
+
322
+
1. For proxy and connectivity issues, refer to [Troubleshoot cloud connectivity issues](/defender-endpoint/linux-support-connectivity)
323
+
324
+
To get support from Microsoft, raise a support ticket and provide log dump by [running client analyser](/defender-endpoint/run-analyzer-macos-linux)
325
+
326
+
## How to configure policies for Microsoft Defender on Linux
259
327
260
-
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).
328
+
You can configure AV/EDR settings on your endpoints using following methods 3. Refer to [set preferences](/defender-endpoint/linux-preferences) to learn more about the available settings 4. Refer to [security settings management](/mem/intune/protect/mde-security-integration) to configure settings via Microsoft Defender Portal
0 commit comments