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
This command deploys the latest agent version to the production channel, check for min system requisites and onboard the device to Defender Portal.
87
89
88
-
This command deploys the latest agent version to the production channel, check for min system requisites and onboard the device to Defender Portal.
89
-
90
-
Additionally you can pass more parameter based on your requirements to modify the installation. Check help for all the available options:
90
+
Additionally you can pass more parameter based on your requirements to modify the installation. Check help for all the available options:
91
91
92
-
```bash
92
+
```bash
93
93
94
94
❯ ./mde_installer.sh --help
95
95
mde_installer.sh v0.7.0
@@ -124,15 +124,15 @@ Before you get started, see [Microsoft Defender for Endpoint on Linux](microsoft
124
124
125
125
| Scenario | Command |
126
126
|---|---|
127
-
|Install a specific agent version | `sudo ~/mde_installer.sh --install --channel prod --onboard ~/MicrosoftDefenderATPOnboardingLinuxServer.py --min_req -y –-mdatp 101.24082.0004 ` |
128
-
| To upgrade to the latest version | `sudo ~/mde_installer.sh --upgrade -y` |
129
-
| For upgrading to a specific version | `sudo ~/mde_installer.sh --upgrade -y –-mdatp 101.24082.0004` |
130
-
| To downgrade to a specific version | `sudo ~/mde_installer.sh --downgrade -y –-mdatp 101.24082.0004` |
131
-
| To remove `mdatp` | `sudo ~/mde_installer.sh --remove -y` |
132
-
133
-
134
-
> [!NOTE]
135
-
> Upgrading your operating system to a new major version after the product installation requires the product to be reinstalled. You need to uninstall the existing Defender for Endpoint on Linux, upgrade the operating system, and then reconfigure Defender for Endpoint on Linux.
127
+
|Install a specific agent version | `sudo ./mde_installer.sh --install --channel prod --onboard ./MicrosoftDefenderATPOnboardingLinuxServer.py --min_req –-mdatp 101.24082.0004 ` |
128
+
|Upgrade to the latest agent version | `sudo ./mde_installer.sh --upgrade` |
129
+
|Upgrade to a specific agent version | `sudo ./mde_installer.sh --upgrade –-mdatp 101.24082.0004` |
130
+
|Downgrade to a specific agent version | `sudo ./mde_installer.sh --downgrade –-mdatp 101.24082.0004` |
> Upgrading your operating system to a new major version after the product installation requires the product to be reinstalled. You need to uninstall the existing Defender for Endpoint on Linux, upgrade the operating system, and then reconfigure Defender for Endpoint on Linux.
136
136
137
137
## Verify deployment status
138
138
@@ -170,14 +170,20 @@ Before you get started, see [Microsoft Defender for Endpoint on Linux](microsoft
170
170
mdatp threat list
171
171
```
172
172
173
-
3. Run an EDR detection test and simulate a detection to verify that the device is properly onboarded and reporting to the service. Perform the following steps on the newly onboarded device:
174
-
175
-
1. Verify that the onboarded Linux server appears in the Microsoft Defender portal. If this is the first onboarding of the machine, it can take up to 20 minutes until it appears.
173
+
1. Run an EDR detection test and simulate a detection to verify that the device is properly onboarded and reporting to the service. Perform the following steps on the newly onboarded device:
176
174
177
-
2. Download and extract the [script file](https://aka.ms/MDE-Linux-EDR-DIY) to an onboarded Linux server, and run the following command:
178
-
179
-
`./mde_linux_edr_diy.sh`
175
+
1. Download and extract the [script file](https://aka.ms/MDE-Linux-EDR-DIY) to an onboarded Linux server.
176
+
177
+
1. Grant executable permissions to the script:
180
178
179
+
```bash
180
+
chmod +x mde_linux_edr_diy.sh
181
+
```
182
+
183
+
1. Run the following command:
184
+
```bash
185
+
./mde_linux_edr_diy.sh
186
+
```
181
187
3. After a few minutes, a detection should be raised in the Microsoft Defender XDR.
182
188
183
189
4. Check the alert details, machine timeline, and perform your typical investigation steps.
0 commit comments