Wiki source code of RangeeOS - Microsoft Defender einrichten
Last modified by Tobias Wintrich on 2025/09/04 12:50
Show last authors
author | version | line-number | content |
---|---|---|---|
1 | It is possible to install and configure **Microsoft Defender for Endpoint** on RangeeOS. | ||
2 | |||
3 | {{info}} | ||
4 | This article was created and tested with the following software versions: | ||
5 | |||
6 | * Firmware 13.00 Build 103 | ||
7 | * microsoft-defender_24082.0001-x64 13.00 Build 003 | ||
8 | {{/info}} | ||
9 | |||
10 | = Installation = | ||
11 | |||
12 | Install the software module **microsoft-defender_24082.0001-x64** on your Thin Client or TCMS. | ||
13 | |||
14 | Instructions for installing updates can be found here: [[RangeeOS - Firmware13 - Update / Upgrade / Downgrade>>path:/HowTos/RangeeOS%20-%20Firmware-%20und%20Softwareupdate/]] | ||
15 | If the software module is not yet available for download, please contact: [[**support@rangee.com**>>mailto:support@rangee.com]] | ||
16 | |||
17 | = Configuration = | ||
18 | |||
19 | After installation, you can configure Defender via **Connections & Applications** -> **Microsoft Defender for Endpoint**. | ||
20 | |||
21 | == Onboarding == | ||
22 | |||
23 | To onboard the client into your Defender environment, you need the onboarding package from the Microsoft Defender portal: | ||
24 | [[https:~~/~~/learn.microsoft.com/en-us/defender-endpoint/linux-install-with-ansible#download-the-onboarding-package-applicable-to-both-the-methods>>https://learn.microsoft.com/en-us/defender-endpoint/linux-install-with-ansible#download-the-onboarding-package-applicable-to-both-the-methods]] | ||
25 | |||
26 | {{info}} | ||
27 | Unlike described there, the onboarding package can be created under **System** -> **Settings** -> **Endpoints** -> **Device Management** -> **Onboarding** (as of 04.09.2025) | ||
28 | {{/info}} | ||
29 | |||
30 | The downloaded ZIP file contains the file "MicrosoftDefenderATPOnboardingLinuxServer.py". Upload this file to your device using the corresponding option. | ||
31 | This step must be repeated on every device where Defender is to be used. | ||
32 | |||
33 | After successful onboarding, the current Defender status will be displayed under "Information": | ||
34 | |||
35 | [[image:1756982689475-844.png]] | ||
36 | |||
37 | The client/TCMS will also appear online in the Microsoft Security Center approximately 5–20 minutes after onboarding. | ||
38 | |||
39 | == Options == | ||
40 | |||
41 | Once the client is onboarded, you can perform the following actions under **Connections & Applications** -> **Microsoft Defender for Endpoint**: | ||
42 | |||
43 | * Enable Microsoft Defender for Endpoint: activates the Defender service | ||
44 | * Enable cloud protection | ||
45 | * Enable cloud diagnostics data collection | ||
46 | * Enable real-time protection | ||
47 | * Sign out device: removes the Defender configuration (Offboarding) | ||
48 | * Log file: displays the last scan log | ||
49 | * Quick scan: performs a quick system scan | ||
50 | * Full scan: performs a full system scan | ||
51 | |||
52 | Findings and unusual events are also reported in the Microsoft Security Portal. |