Skip to content

Commit e831972

Browse files
committed
Update enable-network-protection.md
1 parent bfa8f72 commit e831972

File tree

1 file changed

+14
-18
lines changed

1 file changed

+14
-18
lines changed

defender-endpoint/enable-network-protection.md

Lines changed: 14 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -64,16 +64,12 @@ You can use Registry Editor to check the status of network protection.
6464

6565
To enable network protection, you can use one of the following methods:
6666

67-
68-
6967
- [Microsoft Intune](#microsoft-intune)
7068
- [Mobile Device Management (MDM)](#mobile-device-management-mdm)
7169
- [Group Policy](#group-policy)
7270
- [Microsoft Configuration Manager](#microsoft-configuration-manager)
7371
- [PowerShell](#powershell)
7472

75-
76-
7773
### Microsoft Intune
7874

7975
#### Microsoft Defender for Endpoint Baseline method
@@ -128,13 +124,11 @@ To enable network protection, you can use one of the following methods:
128124

129125
8. Review all the information, and then select **Create**.
130126

131-
132127
### Mobile device management (MDM)
133128

134-
1. Use the [EnableNetworkProtection](/windows/client-management/mdm/policy-csp-defender#enablenetworkprotection) configuration service provider (CSP) to enable or disable network protection or enable audit mode.
135-
136-
2. [Update Microsoft Defender antimalware platform to the latest version](https://support.microsoft.com/topic/update-for-microsoft-defender-antimalware-platform-92e21611-8cf1-8e0e-56d6-561a07d144cc) before you enable or disable network protection or enable audit mode.
129+
1. Use the [EnableNetworkProtection](/windows/client-management/mdm/policy-csp-defender#enablenetworkprotection) configuration service provider (CSP) to turn network protection on or off, or to enable audit mode.
137130

131+
2. [Update Microsoft Defender anti-malware platform to the latest version](https://support.microsoft.com/topic/update-for-microsoft-defender-antimalware-platform-92e21611-8cf1-8e0e-56d6-561a07d144cc) before you turn network protection on or off.
138132

139133
### Group Policy
140134

@@ -144,26 +138,25 @@ Use the following procedure to enable network protection on domain-joined comput
144138

145139
*-Or-*
146140

147-
On a domain-joined Group Policy management computer, open the [Group Policy Management Console](https://technet.microsoft.com/library/cc731212.aspx), right-click the Group Policy Object you want to configure and select **Edit**.
141+
On a domain-joined Group Policy management computer, open the [Group Policy Management Console](https://technet.microsoft.com/library/cc731212.aspx). Right-click the Group Policy Object you want to configure and select **Edit**.
148142

149143
2. In the **Group Policy Management Editor**, go to **Computer configuration** and select **Administrative templates**.
150144

151145
3. Expand the tree to **Windows components** \> **Microsoft Defender Antivirus** \> **Microsoft Defender Exploit Guard** \> **Network protection**.
152146

153-
Note that on older versions of Windows, the Group Policy path might have *Windows Defender Antivirus* instead of *Microsoft Defender Antivirus*.
147+
On older versions of Windows, the Group Policy path might have *Windows Defender Antivirus* instead of *Microsoft Defender Antivirus*.
154148

155149
4. Double-click the **Prevent users and apps from accessing dangerous websites** setting and set the option to **Enabled**. In the options section, you must specify one of the following options:
156150

157151
- **Block** - Users can't access malicious IP addresses and domains.
158152
- **Disable (Default)** - The Network protection feature won't work. Users aren't blocked from accessing malicious domains.
159-
- **Audit Mode** - If a user visits a malicious IP address or domain, an event will be recorded in the Windows event log. However, the user won't be blocked from visiting the address.
153+
- **Audit Mode** - If a user visits a malicious IP address or domain, an event is recorded in the Windows event log. However, the user won't be blocked from visiting the address.
160154

161155
> [!IMPORTANT]
162156
> To fully enable network protection, you must set the Group Policy option to **Enabled** and also select **Block** in the options drop-down menu.
163157
164158
5. (This step is optional.) Follow the steps in [Check if network protection is enabled](#check-if-network-protection-is-enabled) to verify that your Group Policy settings are correct.
165159

166-
167160
### Microsoft Configuration Manager
168161

169162
1. Open the Configuration Manager console.
@@ -185,23 +178,25 @@ Use the following procedure to enable network protection on domain-joined comput
185178

186179
7. From the ribbon, select **Deploy** to deploy the policy to a collection.
187180

188-
189181
### PowerShell
190182

191-
1. On your Windows device, select Start, type `powershell`, right-click **Windows PowerShell**, and then select **Run as administrator**.
183+
1. On your Windows device, click Start, type `powershell`, right-click **Windows PowerShell**, and then select **Run as administrator**.
192184

193185
2. Run the following cmdlet:
194186

195187
```PowerShell
196188
Set-MpPreference -EnableNetworkProtection Enabled
197189
```
198190

199-
1. For Windows Server, use the additional commands that listed in the following table:
191+
3. For Windows Server, use the additional commands listed in the following table:
200192

201193
| Windows Server version | Commands |
202194
|---|---|
203195
|Windows Server 2019 and later | `set-mpPreference -AllowNetworkProtectionOnWinServer $true` |
204-
|Windows Server 2016 <br/>Windows Server 2012 R2 with the [unified agent for Microsoft Defender for Endpoint](/defender-endpoint/enable-network-protection) | `set-MpPreference -AllowNetworkProtectionDownLevel $true` <br/> `set-MpPreference -AllowNetworkProtectionOnWinServer $true` <br/> `set-MpPreference -AllowDatagramProcessingOnWinServer $true` <br/>Important: For Domain Controllers and Microsoft Exchange servers, it is recommended to set the AllowDatagramProcessingOnWinServer parameter to $false. These server roles typically generate substantial UDP network traffic, which can negatively impact network performance and reliability if datagram processing is enabled. Disabling this setting helps optimize network stability and resource utilization in high-load environments.|
196+
|Windows Server 2016 <br/>Windows Server 2012 R2 with the [unified agent for Microsoft Defender for Endpoint](/defender-endpoint/enable-network-protection) | `set-MpPreference -AllowNetworkProtectionDownLevel $true` <br/> `set-MpPreference -AllowNetworkProtectionOnWinServer $true` <br/> `set-MpPreference -AllowDatagramProcessingOnWinServer $true`|
197+
198+
[!IMPORTANT]
199+
> For Domain Controllers and Microsoft Exchange servers, set the `AllowDatagramProcessingOnWinServer` parameter to `$false`. These roles often generate high volumes of UDP traffic, which can affect network performance and reliability when datagram processing is enabled. Disabling this setting helps maintain network stability and optimize resource usage in demanding environments.
205200
206201
4. (This step is optional.) To set network protection to audit mode, use the following cmdlet:
207202

@@ -213,10 +208,11 @@ Use the following procedure to enable network protection on domain-joined comput
213208

214209
#### Important information about removing Exploit Guard settings from a device
215210

216-
Once an Exploit Guard policy is deployed using Configuration Manager, Exploit Guard settings aren't removed from the clients if you remove the deployment. Furthermore, if you remove the client's Exploit Guard deployment, `Delete not supported` is recorded in the client's `ExploitGuardHandler.log` in Configuration Manager.
211+
When you deploy an Exploit Guard policy using Configuration Manager, the settings remain on the client even if you later remove the deployment. If the deployment is removed, the client logs `Delete` not supported in the `ExploitGuardHandler.log` file.
212+
217213
<!--CMADO8538577-->
218214

219-
Use the following PowerShell script in the SYSTEM context to remove Exploit Guard settings correctly:
215+
Use the following PowerShell script in the `SYSTEM` context to remove Exploit Guard settings correctly:
220216
<!--CMADO9907132-->
221217

222218
```powershell

0 commit comments

Comments
 (0)