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/device-control-deploy-manage-gpo.md
+43-8Lines changed: 43 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,10 +1,10 @@
1
1
---
2
2
title: Deploy and manage device control in Microsoft Defender for Endpoint with Group Policy
3
3
description: Learn how to deploy and manage device control in Defender for Endpoint using Group Policy
4
-
author: denisebmsft
5
-
ms.author: deniseb
4
+
author: emmwalshh
5
+
ms.author: ewalsh
6
6
manager: deniseb
7
-
ms.date: 01/09/2025
7
+
ms.date: 01/31/2025
8
8
ms.topic: overview
9
9
ms.service: defender-endpoint
10
10
ms.subservice: asr
@@ -43,7 +43,7 @@ If you're using Group Policy to manage Defender for Endpoint settings, you can u
43
43
44
44
## Set default enforcement
45
45
46
-
You can set default access such as,`Deny` or `Allow` for all device control features, such as`RemovableMediaDevices`, `CdRomDevices`, `WpdDevices`, and `PrinterDevices`.
46
+
You can set default access, such as `Deny` or `Allow` for all device control features including`RemovableMediaDevices`, `CdRomDevices`, `WpdDevices`, and `PrinterDevices`.
47
47
48
48
:::image type="content" source="media/set-default-enforcement-deny-gp.png" alt-text="Screenshot of set default enforcement." lightbox="media/set-default-enforcement-deny-gp.png":::
49
49
@@ -87,12 +87,12 @@ To configure the device types that a device control policy is applied, follow th
87
87
88
88
1. On a device running Windows, go to **Computer Configuration** > **Administrative Templates** > **Windows Components** > **Microsoft Defender Antivirus** > **Device Control** > **Define device control policy groups**.
89
89
90
-
2. In the **Define device control policy groups** window, specify the network share file path containing the XML groups data.
90
+
2. In the **Defined device control policy groups** window, specify the network share file path containing the XML groups data.
91
91
92
92
You can create different group types. Here's one group example XML file for any removable storage and CD-ROM, Windows portable devices, and approved USBs group: [XML file](https://github.com/microsoft/mdatp-devicecontrol/blob/main/windows/device/Group%20Policy/Scenario%202%20GPO%20Removable%20Storage%20Group.xml)
93
93
94
94
> [!NOTE]
95
-
> Comments using XML comment notation `<!--COMMENT-->` can be used in the Rule and Group XML files, but they must be inside the first XML tag, not the first line of the XML file.
95
+
> Comments using XML comment notation `<!--COMMENT-->` can be used in the Rule and Group XML files, but they must be inside the first XML tag, not the frontline of the XML file.
96
96
97
97
## Define Policies
98
98
@@ -101,7 +101,7 @@ You can create different group types. Here's one group example XML file for any
101
101
102
102
1. Create one XML file for access policy rule.
103
103
104
-
2. Use the properties in removable storage access policy rule(s) to create an XML for each group's removable storage access policy rule.
104
+
2. Use the properties in removable storage access policy rules to create an XML for each group's removable storage access policy rule.
105
105
106
106
Ensure root node of the XML is PolicyRules, for example, the following XML:
107
107
@@ -121,10 +121,45 @@ You can create different group types. Here's one group example XML file for any
121
121
122
122
2. In the **Define device control policy rules** window, select **Enabled**, and then specify the network share file path containing the XML rules data.
123
123
124
+
## Validating XML files
125
+
126
+
Mpcmdrun built in functionality to validate XML files that are used for GPO deployments. This feature enables customers to detect any syntax errors the DC engine might encounter while parsing the settings. To perform this validation, administrators should copy the following PowerShell script and provide the appropriate file path for their XML files containing the Device Control rules and groups.
127
+
128
+
```
129
+
#Path to PolicyRules xml. Provide the filepath of the device control rules XML file
130
+
$RulesXML="C:\Policies\PolicyRules.xml"
131
+
132
+
#Path to Groups XML. Provide the filepath of the device control groups XML file
If there are no errors, the following output will be printed in the PowerShell console:
147
+
148
+
149
+
```
150
+
DC policy rules parsing succeeded
151
+
Verifying absolute rules data against the original data
152
+
Rules verified with success
153
+
DC policy groups parsing succeeded
154
+
Verifying absolute groups data against the original data
155
+
Groups verified with success
156
+
Has Group Dependency Loop: no
157
+
```
158
+
124
159
> [!NOTE]
125
160
> To capture evidence of files being copied or printed, use [Endpoint DLP.](/purview/dlp-copy-matched-items-get-started?tabs=purview-portal%2Cpurview)
126
161
>
127
-
> Comments using XML comment notation `<!-- COMMENT -->` can be used in the Rule and Group XML files, but they must be inside the first XML tag, not the first line of the XML file.
162
+
> Comments using XML comment notation `<!-- COMMENT -->` can be used in the Rule and Group XML files, but they must be inside the first XML tag, not the frontline of the XML file.
0 commit comments