Skip to content

Commit 4a302c5

Browse files
committed
Update network-protection.md
1 parent da81b2f commit 4a302c5

File tree

1 file changed

+12
-8
lines changed

1 file changed

+12
-8
lines changed

defender-endpoint/network-protection.md

Lines changed: 12 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -369,7 +369,7 @@ For more information, see [Turn on network protection](enable-network-protection
369369

370370
#### Network protection suggested registry keys
371371

372-
For Windows Server 2012 R2 and Windows Server 2016 using the [modern unified solution](/defender-endpoint/configure-server-endpoints#functionality-in-the-modern-unified-solution), Windows Server version 1803 or later, and Windows 10 Enterprise Multi-Session 1909 and later (used in Windows Virtual Desktop on Azure), enable additional registry keys, as follows:
372+
For Windows Server 2012 R2 and Windows Server 2016 using the [modern unified solution](/defender-endpoint/configure-server-endpoints#functionality-in-the-modern-unified-solution), Windows Server version 1803 or later, and Windows 10 Enterprise Multi-Session 1909 and later (used in Windows Virtual Desktop on Azure), enable other registry keys, as follows:
373373

374374
1. Go to **HKEY_LOCAL_MACHINE** > **SOFTWARE** > **Microsoft** > **Windows Defender** > **Windows Defender Exploit Guard** > **Network Protection**.
375375

@@ -382,22 +382,26 @@ For Windows Server 2012 R2 and Windows Server 2016 using the [modern unified sol
382382
> [!NOTE]
383383
> Depending on your infrastructure, volume of traffic, and other conditions, **HKEY_LOCAL_MACHINE** > **SOFTWARE** > **Policies** > **Microsoft** > **Windows Defender** > **NIS** > **Consumers** > **IPS** - **AllowDatagramProcessingOnWinServer (dword) 1 (hex)** can have an effect on network performance.
384384
385-
For additional information, see: [Turn on network protection](enable-network-protection.md)
385+
For more information, see: [Turn on network protection](enable-network-protection.md)
386386

387387
#### Windows Servers and Windows Multi-session configuration requires PowerShell
388388

389-
For Windows Servers and Windows Multi-session, there are additional items that you must enable by using PowerShell cmdlets. For Windows Server 2012 R2 and Windows Server 2016 unified client, Windows Server version 1803 or newer, Windows Server 2019 or newer, and Windows 10 Enterprise Multi-Session 1909 and up, used in Windows Virtual Desktop on Azure.
389+
For Windows Servers and Windows Multi-session, there are other items that you must enable by using PowerShell cmdlets. For Windows Server 2012 R2 and Windows Server 2016 using the [modern unified solution](/defender-endpoint/configure-server-endpoints#functionality-in-the-modern-unified-solution), Windows Server version 1803 or later, and Windows 10 Enterprise Multi-Session 1909 and later, used in Windows Virtual Desktop on Azure, run the following PowerShell commands:
390390

391-
1. Set-MpPreference -EnableNetworkProtection Enabled
391+
```powershell
392+
393+
Set-MpPreference -EnableNetworkProtection Enabled
392394
393-
1. Set-MpPreference -AllowNetworkProtectionOnWinServer 1
395+
Set-MpPreference -AllowNetworkProtectionOnWinServer 1
394396
395-
1. Set-MpPreference -AllowNetworkProtectionDownLevel 1
397+
Set-MpPreference -AllowNetworkProtectionDownLevel 1
396398
397-
1. Set-MpPreference -AllowDatagramProcessingOnWinServer 1
399+
Set-MpPreference -AllowDatagramProcessingOnWinServer 1
400+
401+
```
398402

399403
> [!NOTE]
400-
> In some cases, depending on your infrastructure, volume of traffic, and other conditions, `Set-MpPreference -AllowDatagramProcessingOnWinServer 1` can have an effect on network performance.
404+
> In some cases, depending on your infrastructure, volume of traffic, and other conditions, `Set-MpPreference -AllowDatagramProcessingOnWinServer 1` can affect network performance.
401405
402406
## Network protection troubleshooting
403407

0 commit comments

Comments
 (0)