From 43b78167007a616c21e39afef1fa0dc80e259eed Mon Sep 17 00:00:00 2001 From: Ansemler <45408203+Ansemler@users.noreply.github.com> Date: Tue, 12 Apr 2022 14:56:41 -0700 Subject: [PATCH 1/4] Update manage connections for new search binary In Windows 11 the search binary is now searchhost.exe so I have updated the documentation for creating a firewall rule for cortana/search --- ...indows-operating-system-components-to-microsoft-services.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md index 39f281139e..dcda65933f 100644 --- a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md +++ b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md @@ -306,6 +306,7 @@ You can also apply the Group Policies using the following registry keys: 3. On the **Rule Type** page, click **Program**, and then click **Next**. 4. On the **Program** page, click **This program path**, type **%windir%\\systemapps\\Microsoft.Windows.Cortana\_cw5n1h2txyewy\\SearchUI.exe**, and then click **Next**. + - On Windows 11 instead type **"%windir%\\SystemApps\\MicrosoftWindows.Client.CBS_cw5n1h2txyewy\\SearchHost.exe"** 5. On the **Action** page, click **Block the connection**, and then click **Next**. @@ -327,6 +328,8 @@ You can also apply the Group Policies using the following registry keys: - Create a new REG_SZ registry setting named **{0DE40C8E-C126-4A27-9371-A27DAB1039F7}** in **HKEY_LOCAL_MACHINE\\SOFTWARE\\Policies\\Microsoft\\WindowsFirewall\\FirewallRules** and set it to a value of **v2.25|Action=Block|Active=TRUE|Dir=Out|Protocol=6|App=%windir%\\SystemApps\\Microsoft.Windows.Cortana_cw5n1h2txyewy\\searchUI.exe|Name=Block outbound Cortana|** +- On Windows 11 instead follow the previous section and use the Group Policy editor + If your organization tests network traffic, do not use a network proxy as Windows Firewall does not block proxy traffic. Instead, use a network traffic analyzer. Based on your needs, there are many network traffic analyzers available at no cost. From b6f5a59ba742185a007fc51cfd9d6b12ebd620cd Mon Sep 17 00:00:00 2001 From: Ansemler <45408203+Ansemler@users.noreply.github.com> Date: Wed, 13 Apr 2022 09:42:13 -0700 Subject: [PATCH 2/4] Update windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md Co-authored-by: JohanFreelancer9 <48568725+JohanFreelancer9@users.noreply.github.com> --- ...windows-operating-system-components-to-microsoft-services.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md index dcda65933f..ac146a44e8 100644 --- a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md +++ b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md @@ -328,7 +328,7 @@ You can also apply the Group Policies using the following registry keys: - Create a new REG_SZ registry setting named **{0DE40C8E-C126-4A27-9371-A27DAB1039F7}** in **HKEY_LOCAL_MACHINE\\SOFTWARE\\Policies\\Microsoft\\WindowsFirewall\\FirewallRules** and set it to a value of **v2.25|Action=Block|Active=TRUE|Dir=Out|Protocol=6|App=%windir%\\SystemApps\\Microsoft.Windows.Cortana_cw5n1h2txyewy\\searchUI.exe|Name=Block outbound Cortana|** -- On Windows 11 instead follow the previous section and use the Group Policy editor +- On Windows 11, follow the previous section instead and use the Group Policy editor. If your organization tests network traffic, do not use a network proxy as Windows Firewall does not block proxy traffic. Instead, use a network traffic analyzer. Based on your needs, there are many network traffic analyzers available at no cost. From c975c785f4721dcd6faa9a9fce2a9996afed6c60 Mon Sep 17 00:00:00 2001 From: Ansemler <45408203+Ansemler@users.noreply.github.com> Date: Wed, 13 Apr 2022 09:42:19 -0700 Subject: [PATCH 3/4] Update windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md Co-authored-by: JohanFreelancer9 <48568725+JohanFreelancer9@users.noreply.github.com> --- ...indows-operating-system-components-to-microsoft-services.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md index ac146a44e8..d3a03542fc 100644 --- a/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md +++ b/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services.md @@ -306,7 +306,8 @@ You can also apply the Group Policies using the following registry keys: 3. On the **Rule Type** page, click **Program**, and then click **Next**. 4. On the **Program** page, click **This program path**, type **%windir%\\systemapps\\Microsoft.Windows.Cortana\_cw5n1h2txyewy\\SearchUI.exe**, and then click **Next**. - - On Windows 11 instead type **"%windir%\\SystemApps\\MicrosoftWindows.Client.CBS_cw5n1h2txyewy\\SearchHost.exe"** + + - On Windows 11, type **"%windir%\\SystemApps\\MicrosoftWindows.Client.CBS_cw5n1h2txyewy\\SearchHost.exe"** instead. 5. On the **Action** page, click **Block the connection**, and then click **Next**. From a502f8aef1262c920ce53c5a048676f16fa67d4a Mon Sep 17 00:00:00 2001 From: Nathan McNulty <6653432+nathanmcnulty@users.noreply.github.com> Date: Thu, 14 Apr 2022 09:55:41 -0700 Subject: [PATCH 4/4] Fix typo Changed sand to and --- .../hello-for-business/hello-feature-dynamic-lock.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/security/identity-protection/hello-for-business/hello-feature-dynamic-lock.md b/windows/security/identity-protection/hello-for-business/hello-feature-dynamic-lock.md index 7d4e7d36ed..7025fb4173 100644 --- a/windows/security/identity-protection/hello-for-business/hello-feature-dynamic-lock.md +++ b/windows/security/identity-protection/hello-for-business/hello-feature-dynamic-lock.md @@ -38,7 +38,7 @@ The Group Policy Editor, when the policy is enabled, creates a default signal ru >[!IMPORTANT] >Microsoft recommends using the default values for this policy settings. Measurements are relative based on the varying conditions of each environment. Therefore, the same values may produce different results. Test policy settings in each environment prior to broadly deploying the setting. -For this policy setting, the **type** and **scenario** attribute values are static and cannot change. The **classofDevice** is configurable but Phone is the only currently supported configuration. The attribute defaults to Phones sand uses the values from the following table: +For this policy setting, the **type** and **scenario** attribute values are static and cannot change. The **classofDevice** is configurable but Phone is the only currently supported configuration. The attribute defaults to Phones and uses the values from the following table: |Description|Value| |:-------------|:-------:|