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
+93-74Lines changed: 93 additions & 74 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,7 +25,7 @@ ms.date: 10/11/2024
25
25
**Applies to**:
26
26
27
27
- Microsoft Defender for Endpoint Server
28
-
-[Microsoft Defender for Servers](/azure/defender-for-cloud/integration-defender-for-endpoint)
28
+
-[Microsoft Defender for Servers](/azure/defender-for-cloud/integration-defender-for-endpoint)
29
29
30
30
> Want to experience Defender for Endpoint? [Sign up for a free trial.](https://signup.microsoft.com/create-account/signup?products=7f379fee-c4f9-4278-b0a1-e4c8c2fcdf7e&ru=https://aka.ms/MDEp2OpenTrial?ocid=docs-wdatp-investigateip-abovefoldlink)
31
31
@@ -113,7 +113,7 @@ You need to create a Puppet manifest for deploying Defender for Endpoint on Linu
113
113
114
114
### Create manifest file
115
115
116
-
There are two ways to create manifest:
116
+
There are two ways to create manifest file:
117
117
118
118
1. create manifest using installer script
119
119
@@ -190,65 +190,96 @@ Add below contents to the `install_mdatp/manifests/init.pp` file
190
190
```puppet
191
191
# Puppet manifest to install Microsoft Defender for Endpoint on Linux.
192
192
# @param channel The release channel based on your environment, insider-fast or prod.
193
-
# @param distro The Linux distribution in lowercase. In case of RedHat, Oracle Linux, Amazon Linux 2, and CentOS 8, the distro variable should be 'rhel'.
194
-
# @param version The Linux distribution release number, e.g. 7.4.
default: { fail("${facts['os']['family']} is currently not supported.")}
282
+
default: { fail("${facts['os']['family']} is currently not supported.")}
252
283
}
253
284
}
254
285
@@ -272,40 +303,28 @@ Enrolled agent devices periodically poll the Puppet Server and install new confi
272
303
273
304
## Monitor Puppet deployment
274
305
275
-
On the agent device, you can also check the onboarding status by running:
306
+
On the agent device, you can also check the deployment status by running:
276
307
277
308
```bash
278
309
mdatp health
279
310
```
280
311
281
312
```console
282
313
...
314
+
healthy :true
315
+
health_issues : []
283
316
licensed :true
284
317
org_id :"[your organization identifier]"
285
318
...
286
319
```
287
320
288
-
- **licensed**: This confirms that the device is tied to your organization.
289
-
290
-
- **orgId**: This is your Defender for Endpoint organization identifier.
291
-
292
-
## Check onboarding status
321
+
- **healthy:** This confirm that Defender for Endpoint is successfully deployed and operational
293
322
294
-
You can check that devices have been correctly onboarded by creating a script. For example, the following script checks enrolled devices for onboarding status:
323
+
- **health_issues**: This states the issues which caused the healthy status to become false.
295
324
296
-
```bash
297
-
mdatp health --field healthy
298
-
```
299
-
300
-
The above command prints `1`if the product is onboarded and functioning as expected.
301
-
302
-
> [!IMPORTANT]
303
-
> When the product starts for the first time, it downloads the latest antimalware definitions. Depending on your Internet connection, this can take up to a few minutes. During this time the above command returns a value of `0`.
304
-
305
-
If the product is not healthy, the exit code (which can be checked through `echo $?`) indicates the problem:
325
+
- **licensed**: This confirms that the device is tied to your organization.
306
326
307
-
- `1`if the device isn't onboarded yet.
308
-
- `3` if the connection to the daemon cannot be established.
327
+
- **orgId**: This is your Defender for Endpoint organization identifier.
0 commit comments