updates

.openpublishing.redirection.windows-security.json

@@ -7962,32 +7962,32 @@
     },
     {
       "source_path": "windows/security/operating-system-security/network-security/windows-firewall/create-inbound-rules-to-support-rpc.md",
-      "redirect_url": "/windows/security/operating-system-security/network-security/windows-firewall/configure-rules-with-gpo",
+      "redirect_url": "/windows/security/operating-system-security/network-security/windows-firewall/configure",
       "redirect_document_id": false
     },
     {
       "source_path": "windows/security/operating-system-security/network-security/windows-firewall/create-an-outbound-program-or-service-rule.md",
-      "redirect_url": "/windows/security/operating-system-security/network-security/windows-firewall/configure-rules-with-gpo",
+      "redirect_url": "/windows/security/operating-system-security/network-security/windows-firewall/configure",
       "redirect_document_id": false
     },
     {
       "source_path": "windows/security/operating-system-security/network-security/windows-firewall/create-an-outbound-port-rule.md",
-      "redirect_url": "/windows/security/operating-system-security/network-security/windows-firewall/configure-rules-with-gpo",
+      "redirect_url": "/windows/security/operating-system-security/network-security/windows-firewall/configure",
       "redirect_document_id": false
     },
     {
       "source_path": "windows/security/operating-system-security/network-security/windows-firewall/create-an-inbound-program-or-service-rule.md",
-      "redirect_url": "/windows/security/operating-system-security/network-security/windows-firewall/configure-rules-with-gpo",
+      "redirect_url": "/windows/security/operating-system-security/network-security/windows-firewall/configure",
       "redirect_document_id": false
     },
     {
       "source_path": "windows/security/operating-system-security/network-security/windows-firewall/create-an-inbound-port-rule.md",
-      "redirect_url": "/windows/security/operating-system-security/network-security/windows-firewall/configure-rules-with-gpo",
+      "redirect_url": "/windows/security/operating-system-security/network-security/windows-firewall/configure",
       "redirect_document_id": false
     },
     {
       "source_path": "windows/security/operating-system-security/network-security/windows-firewall/create-an-inbound-icmp-rule.md",
-      "redirect_url": "/windows/security/operating-system-security/network-security/windows-firewall/configure-rules-with-gpo",
+      "redirect_url": "/windows/security/operating-system-security/network-security/windows-firewall/configure",
       "redirect_document_id": false
     },
     {
@@ -8034,6 +8034,11 @@
       "source_path": "windows/security/operating-system-security/network-security/windows-firewall/create-windows-firewall-rules-in-intune.md",
       "redirect_url": "/windows/security/operating-system-security/network-security/windows-firewall/configure",
       "redirect_document_id": false
+    },
+    {
+      "source_path": "windows/security/operating-system-security/network-security/windows-firewall/firewall-settings-lost-on-upgrade.md",
+      "redirect_url": "/windows/security/operating-system-security/network-security/windows-firewall",
+      "redirect_document_id": false
     }
   ]
 }

windows/security/operating-system-security/network-security/windows-firewall/configure-logging.md

@@ -2,7 +2,7 @@
 title: Configure Windows Firewall logging 
 description: Learn how to configure Windows Firewall to log dropped packets or successful connections with CSP and group policy.
 ms.topic: how-to
-ms.date: 11/14/2023
+ms.date: 11/21/2023
 ---
 
 # Configure Windows Firewall logging
@@ -75,7 +75,7 @@ Alternatively, you can configure devices using a [custom policy][INT-1] with the
 Here are some recommendations for configuring Windows Firewall logging:
 
 - Change the logging size to at least **20,480 KB (20 MB)** to ensure that the log file doesn't fill up too quickly. The maximum log size is 32,768 KB (32 MB)
-- For each profile (Domain, Private, and Public) change the name from `%windir%\system32\logfiles\firewall\pfirewall.log` to:
+- For each profile (Domain, Private, and Public) change the default log file name from `%windir%\system32\logfiles\firewall\pfirewall.log` to:
   - `%windir%\system32\logfiles\firewall\pfirewall_Domain.log`
   - `%windir%\system32\logfiles\firewall\pfirewall_Private.log`
   - `%windir%\system32\logfiles\firewall\pfirewall_Public.log`

windows/security/operating-system-security/network-security/windows-firewall/configure-with-command-line.md

@@ -2,7 +2,7 @@
 title: Manage Windows Firewall with the command line
 description: Learn how to manage Windows Firewall from the command line. This guide provides examples how to manage Windows Firewall with PowerShell and Netsh. 
 ms.topic: conceptual
-ms.date: 11/20/2023
+ms.date: 11/21/2023
 ---
 
 # Manage Windows Firewall with the command line

windows/security/operating-system-security/network-security/windows-firewall/configure.md

@@ -2,7 +2,7 @@
 title: Configure firewall rules with group policy
 description: Learn how to configure firewall rules using group policy with the Windows Firewall with Advanced Security console.
 ms.topic: how-to
-ms.date: 11/14/2023
+ms.date: 11/21/2023
 ---
 
 # Configure rules with group policy
@@ -20,45 +20,45 @@ If you are configuring a single device, you must have administrative rights on t
 This type of rule allows ICMP requests and responses to be received by devices on the network. To create an inbound ICMP rule:
 
 1. Open the *Windows Firewall with Advanced Security* console
-1. In the navigation pane, select**Inbound Rules**
+1. In the navigation pane, select **Inbound Rules**
-1. Select **Action**, and then select**New rule**
+1. Select **Action**, and then select **New rule**
-1. On the **Rule Type** page of the New Inbound Rule Wizard, select**Custom**, and then select**Next**
+1. On the **Rule Type** page of the New Inbound Rule Wizard, select **Custom**, and then select **Next**
-1. On the **Program** page, select**All programs**, and then select**Next**
+1. On the **Program** page, select **All programs**, and then select **Next**
 1. On the **Protocol and Ports** page, select **ICMPv4** or **ICMPv6** from the **Protocol type** list. If you use both IPv4 and IPv6 on your network, you must create a separate ICMP rule for each
 1. Select **Customize**
 1. In the **Customize ICMP Settings** dialog box, do one of the following:
-    - To allow all ICMP network traffic, select**All ICMP types**, and then select**OK**
+    - To allow all ICMP network traffic, select **All ICMP types**, and then select **OK**
-    - To select one of the predefined ICMP types, select**Specific ICMP types**, and then select each type in the list that you want to allow. Select **OK**
+    - To select one of the predefined ICMP types, select **Specific ICMP types**, and then select each type in the list that you want to allow. Select **OK**
-    - To select an ICMP type that does not appear in the list, select**Specific ICMP types**, select the **Type** number from the list, select the **Code** number from the list, select**Add**, and then select the newly created entry from the list. Select **OK**
+    - To select an ICMP type that does not appear in the list, select **Specific ICMP types**, select the **Type** number from the list, select the **Code** number from the list, select **Add**, and then select the newly created entry from the list. Select **OK**
 1. Select **Next**
-1. On the **Scope** page, you can specify that the rule applies only to network traffic to or from the IP addresses entered on this page. Configure as appropriate for your design, and then select**Next**
+1. On the **Scope** page, you can specify that the rule applies only to network traffic to or from the IP addresses entered on this page. Configure as appropriate for your design, and then select **Next**
-1. On the **Action** page, select **Allow the connection**, and then select**Next**
+1. On the **Action** page, select **Allow the connection**, and then select **Next**
-1. On the **Profile** page, select the network location types to which this rule applies, and then select**Next**
+1. On the **Profile** page, select the network location types to which this rule applies, and then select **Next**
-1. On the **Name** page, type a name and description for your rule, and then select**Finish**
+1. On the **Name** page, type a name and description for your rule, and then select **Finish**
 
 ## Create an inbound port rule
 
 This type of rule allows any program that listens on a specified TCP or UDP port to receive network traffic sent to that port. To create an inbound port rule:
 
 1. Open the *Windows Firewall with Advanced Security* console
-1. In the navigation pane, select**Inbound Rules**
+1. In the navigation pane, select **Inbound Rules**
-1. Select **Action**, and then select**New rule**
+1. Select **Action**, and then select **New rule**
-1. On the **Rule Type** page of the New Inbound Rule Wizard, select**Custom**, and then select**Next**
+1. On the **Rule Type** page of the New Inbound Rule Wizard, select **Custom**, and then select **Next**
    > [!NOTE]
    > Although you can create rules by selecting **Program** or **Port**, those choices limit the number of pages presented by the wizard. If you select **Custom**, you see all of the pages, and have the most flexibility in creating your rules.
-1. On the **Program** page, select**All programs**, and then select**Next**
+1. On the **Program** page, select **All programs**, and then select **Next**
    > [!NOTE]
    > This type of rule is often combined with a program or service rule. If you combine the rule types, you get a firewall rule that limits traffic to a specified port and allows the traffic only when the specified program is running. The specified program cannot receive network traffic on other ports, and other programs cannot receive network traffic on the specified port. If you choose to do this, follow the steps in the [Create an Inbound Program or Service Rule](#create-an-inbound-program-or-service-rule) procedure in addition to the steps in this procedure to create a single rule that filters network traffic using both program and port criteria.
 1. On the **Protocol and Ports** page, select the protocol type that you want to allow. To restrict the rule to a specified port number, you must select either **TCP** or **UDP**. Because this is an incoming rule, you typically configure only the local port number
    If you select another protocol, then only packets whose protocol field in the IP header match this rule are permitted through the firewall.\
    To select a protocol by its number, select **Custom** from the list, and then type the number in the **Protocol number** box.\
-   When you have configured the protocols and ports, select**Next**.
+   When you have configured the protocols and ports, select **Next**.
-1. On the **Scope** page, you can specify that the rule applies only to network traffic to or from the IP addresses entered on this page. Configure as appropriate for your design, and then select**Next**
+1. On the **Scope** page, you can specify that the rule applies only to network traffic to or from the IP addresses entered on this page. Configure as appropriate for your design, and then select **Next**
-1. On the **Action** page, select **Allow the connection**, and then select**Next**
+1. On the **Action** page, select **Allow the connection**, and then select **Next**
-1. On the **Profile** page, select the network location types to which this rule applies, and then select**Next**
+1. On the **Profile** page, select the network location types to which this rule applies, and then select **Next**
    > [!NOTE]
    > If this GPO is targeted at server computers running Windows Server 2008 that never move, consider modifying the rules to apply to all network location type profiles. This prevents an unexpected change in the applied rules if the network location type changes due to the installation of a new network card or the disconnection of an existing network card's cable. A disconnected network card is automatically assigned to the Public network location type.
-1. On the **Name** page, type a name and description for your rule, and then select**Finish**
+1. On the **Name** page, type a name and description for your rule, and then select **Finish**
 
 ## Create an outbound port rule
 
@@ -88,17 +88,17 @@ This type of rule allows the program to listen and receive inbound network traff
 To create an inbound firewall rule for a program or service:
 
 1. Open the *Windows Firewall with Advanced Security* console
-1. In the navigation pane, select**Inbound Rules**
+1. In the navigation pane, select **Inbound Rules**
-1. Select **Action**, and then select**New rule**
+1. Select **Action**, and then select **New rule**
-1. On the **Rule Type** page of the New Inbound Rule Wizard, select **Custom**, and then select**Next**
+1. On the **Rule Type** page of the New Inbound Rule Wizard, select **Custom**, and then select **Next**
     > [!NOTE]
     > Information the user should notice even if skimmingAlthough you can create rules by selecting **Program** or **Port**, those choices limit the number of pages presented by the wizard. If you select **Custom**, you see all of the pages, and have the most flexibility in creating your rules.
-1. On the **Program** page, select**This program path**
+1. On the **Program** page, select **This program path**
 1. Type the path to the program in the text box. Use environment variables, where applicable, to ensure that programs installed in different locations on different computers work correctly.
 1. Do one of the following:
-    - If the executable file contains a single program, select**Next**
+    - If the executable file contains a single program, select **Next**
-    - If the executable file is a container for multiple services that must all be allowed to receive inbound network traffic, select**Customize**, select **Apply to services only**, select**OK**, and then select**Next**
+    - If the executable file is a container for multiple services that must all be allowed to receive inbound network traffic, select **Customize**, select **Apply to services only**, select **OK**, and then select **Next**
-    - If the executable file is a container for a single service or contains multiple services but the rule only applies to one of them, select**Customize**, select **Apply to this service**, and then select the service from the list. If the service does not appear in the list, select**Apply to service with this service short name**, and then type the short name for the service in the text box. Select **OK**, and then select**Next**
+    - If the executable file is a container for a single service or contains multiple services but the rule only applies to one of them, select **Customize**, select **Apply to this service**, and then select the service from the list. If the service does not appear in the list, select **Apply to service with this service short name**, and then type the short name for the service in the text box. Select **OK**, and then select **Next**
 
     > [!IMPORTANT]
     > To use the **Apply to this service** or **Apply to service with this service short name** options, the service must be configured with a security identifier (SID) with a type of **RESTRICTED** or **UNRESTRICTED**. To check the SID type of a service, run the following command: `sc qsidtype <ServiceName>`
@@ -109,11 +109,11 @@ To create an inbound firewall rule for a program or service:
 
     In the preceding command, the value of `<Type>` can be `UNRESTRICTED` or `RESTRICTED`. Although the command also permits the value of `NONE`, that setting means the service cannot be used in a firewall rule as described here. By default, most services in Windows are configured as `UNRESTRICTED`. If you change the SID type to `RESTRICTED`, the service might fail to start. We recommend that you change the SID type only on services that you want to use in firewall rules, and that you change the SID type to `UNRESTRICTED`.
 
-1. It is a best practice to restrict the firewall rule for the program to only the ports it needs to operate. On the **Protocols and Ports** page, you can specify the port numbers for the allowed traffic. If the program tries to listen on a port different from the one specified here, it is blocked. For more information about protocol and port options, see [Create an Inbound Port Rule](#create-an-inbound-port-rule). After you have configured the protocol and port options, select**Next**
+1. It is a best practice to restrict the firewall rule for the program to only the ports it needs to operate. On the **Protocols and Ports** page, you can specify the port numbers for the allowed traffic. If the program tries to listen on a port different from the one specified here, it is blocked. For more information about protocol and port options, see [Create an Inbound Port Rule](#create-an-inbound-port-rule). After you have configured the protocol and port options, select **Next**
-1. On the **Scope** page, you can specify that the rule applies only to network traffic to or from the IP addresses entered on this page. Configure as appropriate for your design, and then select**Next**
+1. On the **Scope** page, you can specify that the rule applies only to network traffic to or from the IP addresses entered on this page. Configure as appropriate for your design, and then select **Next**
-1. On the **Action** page, select **Allow the connection**, and then select**Next**
+1. On the **Action** page, select **Allow the connection**, and then select **Next**
-1. On the **Profile** page, select the network location types to which this rule applies, and then select**Next**
+1. On the **Profile** page, select the network location types to which this rule applies, and then select **Next**
-1. On the **Name** page, type a name and description for your rule, and then select**Finish**
+1. On the **Name** page, type a name and description for your rule, and then select **Finish**
 
 ## Create an outbound program or service rule
 
@@ -149,30 +149,30 @@ Using the two rules configured as described in this topic helps to protect your
 ### RPC Endpoint Mapper service
 
 1. Open the *Windows Firewall with Advanced Security* console
-1. In the navigation pane, select**Inbound Rules**
+1. In the navigation pane, select **Inbound Rules**
-1. Select **Action**, and then select**New rule**
+1. Select **Action**, and then select **New rule**
-1. On the **Rule Type** page of the New Inbound Rule Wizard, select**Custom**, and then select**Next**
+1. On the **Rule Type** page of the New Inbound Rule Wizard, select **Custom**, and then select **Next**
-1. On the **Program** page, select**This Program Path**, and then type `%systemroot%\system32\svchost.exe`
+1. On the **Program** page, select **This Program Path**, and then type `%systemroot%\system32\svchost.exe`
 1. Select **Customize**.
-1. In the **Customize Service Settings** dialog box, select**Apply to this service**, select **Remote Procedure Call (RPC)** with a short name of **RpcSs**, select**OK**, and then select**Next**
+1. In the **Customize Service Settings** dialog box, select **Apply to this service**, select **Remote Procedure Call (RPC)** with a short name of **RpcSs**, select **OK**, and then select **Next**
-1. On the warning about Windows service-hardening rules, select**Yes**
+1. On the warning about Windows service-hardening rules, select **Yes**
 1. On the **Protocol and Ports** dialog box, for **Protocol type**, select **TCP**
-1. For **Local port**, select **RPC Endpoint Mapper**, and then select**Next**
+1. For **Local port**, select **RPC Endpoint Mapper**, and then select **Next**
-1. On the **Scope** page, you can specify that the rule applies only to network traffic to or from the IP addresses entered on this page. Configure as appropriate for your design, and then select**Next**
+1. On the **Scope** page, you can specify that the rule applies only to network traffic to or from the IP addresses entered on this page. Configure as appropriate for your design, and then select **Next**
-1. On the **Action** page, select **Allow the connection**, and then select**Next**
+1. On the **Action** page, select **Allow the connection**, and then select **Next**
-1. On the **Profile** page, select the network location types to which this rule applies, and then select**Next**
+1. On the **Profile** page, select the network location types to which this rule applies, and then select **Next**
-1. On the **Name** page, type a name and description for your rule, and then select**Finish**
+1. On the **Name** page, type a name and description for your rule, and then select **Finish**
 
 ### RPC-enabled network services
 
-1. On the same GPO you edited in the preceding procedure, select**Action**, and then select**New rule**
+1. On the same GPO you edited in the preceding procedure, select **Action**, and then select **New rule**
-1. On the **Rule Type** page of the New Inbound Rule Wizard, select**Custom**, and then select**Next**
+1. On the **Rule Type** page of the New Inbound Rule Wizard, select **Custom**, and then select **Next**
-1. On the **Program** page, select**This Program Path**, and then type the path to the executable file that hosts the network service. Select **Customize**
+1. On the **Program** page, select **This Program Path**, and then type the path to the executable file that hosts the network service. Select **Customize**
-1. In the **Customize Service Settings** dialog box, select**Apply to this service**, and then select the service that you want to allow. If the service doesn't appear in the list, then select**Apply to service with this service short name**, and then type the short name of the service in the text box
+1. In the **Customize Service Settings** dialog box, select **Apply to this service**, and then select the service that you want to allow. If the service doesn't appear in the list, then select **Apply to service with this service short name**, and then type the short name of the service in the text box
-1. Select **OK**, and then select**Next**
+1. Select **OK**, and then select **Next**
 1. On the **Protocol and Ports** dialog box, for **Protocol type**, select **TCP**
-1. For **Local port**, select **RPC Dynamic Ports**, and then select**Next**
+1. For **Local port**, select **RPC Dynamic Ports**, and then select **Next**
-1. On the **Scope** page, you can specify that the rule applies only to network traffic to or from the IP addresses entered on this page. Configure as appropriate for your design, and then select**Next**
+1. On the **Scope** page, you can specify that the rule applies only to network traffic to or from the IP addresses entered on this page. Configure as appropriate for your design, and then select **Next**
-1. On the **Action** page, select **Allow the connection**, and then select**Next**
+1. On the **Action** page, select **Allow the connection**, and then select **Next**
-1. On the **Profile** page, select the network location types to which this rule applies, and then select**Next**
+1. On the **Profile** page, select the network location types to which this rule applies, and then select **Next**
-1. On the **Name** page, type a name and description for your rule, and then select**Finish**
+1. On the **Name** page, type a name and description for your rule, and then select **Finish**

windows/security/operating-system-security/network-security/windows-firewall/filter-origin-documentation.md

@@ -2,7 +2,7 @@
 title: Filter origin audit log improvements
 description: Filter origin documentation audit log improvements
 ms.topic: troubleshooting
-ms.date: 11/07/2023
+ms.date: 11/21/2023
 ---
 
 # Filter origin audit log improvements

windows/security/operating-system-security/network-security/windows-firewall/firewall-settings-lost-on-upgrade.md

@@ -1,31 +0,0 @@
----
-title: Troubleshooting Windows Firewall settings after a Windows upgrade
-description: Firewall settings lost on upgrade
-ms.topic: troubleshooting
-ms.date: 11/07/2023
----
-
-# Troubleshooting Windows Firewall settings after a Windows upgrade
-
-Use this article to troubleshoot firewall settings that are turned off after upgrading to a new version of Windows.
-
-## Rule groups
-
-To help you organize your list, individual built-in firewall rules are categorized within a group. For example, the following rules form part of the Remote Desktop group.
-
-- Remote Desktop - Shadow (TCP-In)
-- Remote Desktop - User Mode (TCP-In)
-- Remote Desktop - User-Mode (UDP-In)
-
-Other group examples include **core networking**, **file and print sharing**, and **network discovery**. Grouping allows administrators to manage sets of similar rules by filtering on categories in the firewall interface (wf.msc). Do this filtering by right-clicking on either **Inbound** or **Outbound Rules** and selecting **Filter by Group**. Optionally, you can use PowerShell using the `Get-NetFirewallRule` cmdlet with the `-Group` switch.
-
-```Powershell
-Get-NetFirewallRule -Group <groupName>
-```
-
-> [!NOTE]
-> Microsoft recommends to enable or disable an entire group instead of individual rules.
-
-Microsoft recommends that you enable/disable all of the rules within a group instead of one or two individual rules. This recommendation is because groups aren't 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, 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 then 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.

windows/security/operating-system-security/network-security/windows-firewall/hyper-v-firewall.md

@@ -2,7 +2,7 @@
 title: Hyper-V firewall 
 description: Learn how to configure Hyper-V firewall rules and settings using PowerShell or Configuration Service Provider (CSP).
 ms.topic: how-to
-ms.date: 11/08/2023
+ms.date: 11/21/2023
 appliesto:
 - ✅ <a href="https://learn.microsoft.com/windows/release-health/supported-versions-windows-client" target="_blank">Windows 11</a>
 ---

windows/security/operating-system-security/network-security/windows-firewall/index.md

@@ -2,7 +2,7 @@
 title: Windows Firewall overview 
 description: Learn overview information about the Windows Firewall security feature.
 ms.topic: conceptual
-ms.date: 11/20/2023
+ms.date: 11/21/2023
 ---
 
 # Windows Firewall overview

windows/security/operating-system-security/network-security/windows-firewall/quarantine.md

@@ -1,8 +1,8 @@
 ---
 title: Quarantine behavior
 description: Learn about Windows Firewall and the quarantine feature behavior.
-ms.topic: conceptual
+ms.topic: concept-article
-ms.date: 11/14/2023
+ms.date: 11/21/2023
 ---
 
 # Quarantine behavior

windows/security/operating-system-security/network-security/windows-firewall/rules.md

@@ -1,7 +1,7 @@
 ---
 title: Windows Firewall rules
 description: Learn about Windows Firewall rules and design recommendations.
-ms.date: 11/15/2023
+ms.date: 11/21/2023
 ms.topic: concept-article
 ---
 

windows/security/operating-system-security/network-security/windows-firewall/toc.yml

@@ -25,5 +25,3 @@ items:
         href: filter-origin-documentation.md
       - name: Quarantine behavior
         href: quarantine.md
-      - name: Firewall settings lost on upgrade
-        href: firewall-settings-lost-on-upgrade.md

windows/security/operating-system-security/network-security/windows-firewall/tools.md

@@ -136,7 +136,7 @@ From the following dropdown, select one of tools to learn how to configure Windo
 > [!div class="op_single_selector"]
 >
 > - [Configure with Microsoft Intune 🔗][INT-1]
-> - [Configure with GPO](configure.md)
+> - [Configure with group policy](configure.md)
 > - [Configure with command line tools](configure-with-command-line.md)
 
 <!--links-->