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: memdocs/configmgr/protect/deploy-use/defender-advanced-threat-protection.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -51,7 +51,7 @@ Instructions to [Onboarding to Microsoft Defender for Endpoint with Configuratio
51
51
52
52
Different operating systems have different needs for onboarding to Microsoft Defender for Endpoint. Up-level devices, such as Windows Server version 1803, need the onboarding configuration file. Starting Current Branch 2207, For down-level server operating system devices, you can choose between Microsoft Defender for Endpoint (MDE) Client (recommended) or Microsoft Monitoring Agent (MMA) (legacy) in the Client Settings. For Windows 8.1 devices, you need to use Microsoft Monitoring Agent (MMA) (legacy) in the Client Settings.
53
53
54
-
:::image type="content" source="media/9265511-mde-downlevel-support-client-settings.png" alt-text="MDE Downlevel Support Client Settings Download" lightbox="media/9265511-mde-downlevel-support-client-settings.png":::
54
+
:::image type="content" source="media/9265511-mde-downlevel-support-client-settings.png" alt-text="Screenshot of Client Settings for Endpoint Protection." lightbox="media/9265511-mde-downlevel-support-client-settings.png":::
55
55
56
56
If you choose to use MMA, you need the **Workspace key** and **Workspace ID** to onboard. Configuration Manager also installs the Microsoft Monitoring Agent (MMA) when needed by onboarded devices but it doesn't update the agent automatically.
57
57
@@ -115,7 +115,7 @@ Down-level operating systems that support MDE Client include:
115
115
1. In the Configuration Manager console, navigate to **Administration** > **Client Settings**.
116
116
1. Create custom Client Device Settings or go to the properties of the required client setting and select **Endpoint Protection**
117
117
1. For **Microsoft Defender for Endpoint Client on Windows Server 2012 R2 and Windows Server 2016** setting, The default value is set as **Microsoft Monitoring Agent (legacy)** which needs to be changed to **MDE Client (recommended)**.
118
-
:::image type="content" source="media/9265511-mde-downlevel-support-client-settings.png" alt-text="MDE Downlevel Support Client Settings Download" lightbox="media/9265511-mde-downlevel-support-client-settings.png":::
118
+
:::image type="content" source="media/9265511-mde-downlevel-support-client-settings.png" alt-text="Screenshot of Client Settings for Endpoint Protection showing different options for down-level server operating system devices." lightbox="media/9265511-mde-downlevel-support-client-settings.png":::
119
119
1. In the Configuration Manager console, navigate to **Assets and Compliance** > **Endpoint Protection** > **Microsoft Defender ATP Policies** and select **Create Microsoft Defender ATP Policy**. The policy wizard opens.
120
120
1. Type the **Name** and **Description** for the Microsoft Defender for Endpoint policy and select **Onboarding**.
121
121
1.**Browse** to the configuration file you extracted from the downloaded .zip file.
@@ -137,7 +137,7 @@ Down-level operating systems that support MDE Client include:
137
137
1. Choose **Microsoft Endpoint Configuration Manager current branch and later** for the deployment method.
:::image type="content" source="media/5229962-onboarding-configuration.png" alt-text="Screenshot of onboarding configuration file download." lightbox="media/5229962-onboarding-configuration.png":::
141
141
142
142
1. Download the compressed archive (.zip) file and extract the contents.
143
143
1. Select **Settings**, then select **Onboarding** under the **Device management** heading.
@@ -160,7 +160,7 @@ Down-level operating systems that support MDE Client include:
160
160
1.**Browse** to the configuration file you extracted from the downloaded .zip file.
161
161
1. Supply the **Workspace key** and **Workspace ID** then select **Next**.
162
162
- Verify that the **Workspace key** and **Workspace ID** are in the correct fields. The order in the console may vary from the order in Microsoft Defender for Endpoint online service. <!--8538605-->
163
-
:::image type="content" source="media/5229962-create-atp-policy-wizard.png" alt-text="Create Microsoft Defender for Endpoint Policy Wizard" lightbox="media/5229962-create-atp-policy-wizard.png":::
163
+
:::image type="content" source="media/5229962-create-atp-policy-wizard.png" alt-text="Screenshot of Microsoft Defender for Endpoint policy configuration wizard." lightbox="media/5229962-create-atp-policy-wizard.png":::
164
164
165
165
1. Specify the file samples that are collected and shared from managed devices for analysis.
0 commit comments