deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-05-28 05:07:23 +00:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

acrolinx

Browse Source
This commit is contained in:
Daniel Simpson 2020-12-17 11:25:07 -08:00
parent e68dbc8f3b
commit 474f267b8a
1 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
windows/security/threat-protection/windows-firewall/firewall-settings-lost-on-upgrade.md
View File

@ -1,5 +1,5 @@
---
title: Firewall settings lost on upgrade
title: Troubleshooting Windows Firewall settings after a Windows upgrade
description: Firewall settings lost on upgrade
ms.reviewer:
ms.author: v-bshilpa
@ -15,9 +15,9 @@ ms.collection:
ms.topic: troubleshooting
---
# Troubleshooting Windows Firewall settings that are missing after an upgrade
# Troubleshooting Windows Firewall settings after a Windows upgrade
This article describes a scenario where previously enabled firewall rules revert to disabled after upgrading to a new version of Windows.
Use this article to troubleshoot firewall settings that are turned off after upgrading to a new version of Windows.
## Rule groups
@ -34,8 +34,8 @@ Get-NetFirewallRule -Group <groupName>
```
> [!NOTE]
> We recommend to enable or disable an entire group instead of individual rules.
> Microsoft recommends to enable or disable an entire group instead of individual rules.
We recommended that you enable/disable all of the rules within a group instead of one or two individual rules. This is because groups are not only used to organize rules and allow batch rule modification by type, but they also represent a 'unit' by which rule state is maintained across a Windows upgrade. Rule groups, as opposed to individual rules, are the unit by which the update process determines what should be enabled/disabled when the upgrade is complete.
Microsoft recommends that you enable/disable all of the rules within a group instead of one or two individual rules. This is because groups are not only used to organize rules and allow batch rule modification by type, but they also represent a 'unit' by which rule state is maintained across a Windows upgrade. Rule groups, as opposed to individual rules, are the unit by which the update process determines what should be enabled/disabled when the upgrade is complete.
For example, using the Remote Desktop group consists of three rules. To ensure that the rule set is properly migrated during an upgrade, all three rules must be enabled. If only one rule is enabled, the upgrade process will see that two of three rules are disabled and subsequently disable the entire group in an effort to maintain a clean out-of-the-box configuration. This scenario brings with it the unintended consequence of breaking Remote Desktop Protocol (RDP) connectivity to the host.
For example, the Remote Desktop group consists of three rules. To ensure that the rule set is properly migrated during an upgrade, all three rules must be enabled. If only one rule is enabled, the upgrade process will see that two of three rules are disabled and subsequently disable the entire group to maintain a clean, out-of-the-box configuration. This scenario has the unintended consequence of breaking Remote Desktop Protocol (RDP) connectivity to the host.