From 39ef4bc9a1053b5e036bbae7465a94dcd782f707 Mon Sep 17 00:00:00 2001 From: MaratMussabekov <48041687+MaratMussabekov@users.noreply.github.com> Date: Tue, 25 Aug 2020 16:57:10 +0500 Subject: [PATCH 01/76] Update microsoft-defender-atp-mac.md --- .../microsoft-defender-atp-mac.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/windows/security/threat-protection/microsoft-defender-atp/microsoft-defender-atp-mac.md b/windows/security/threat-protection/microsoft-defender-atp/microsoft-defender-atp-mac.md index 62d68dcdee..3f296b7a24 100644 --- a/windows/security/threat-protection/microsoft-defender-atp/microsoft-defender-atp-mac.md +++ b/windows/security/threat-protection/microsoft-defender-atp/microsoft-defender-atp-mac.md @@ -67,6 +67,18 @@ Beta versions of macOS are not supported. macOS Sierra (10.12) support ended on After you've enabled the service, you may need to configure your network or firewall to allow outbound connections between it and your endpoints. +### Licensing requirements + +Microsoft Defender Advanced Threat Protection for Mac requires one of the following Microsoft Volume Licensing offers: + +- Microsoft 365 E5 (M365 E5) +- Microsoft 365 E5 Security +- Microsoft 365 A5 (M365 A5) + +> [!NOTE] +> Eligible Licensed Users may use Microsoft Defender Advanced Threat Protection on up to five concurrent devices. +> Microsoft Defender Advanced Threat Protection is also available for purchase from a Cloud Solution Provider (CSP). When purchased via a CSP, it does not require Microsoft Volume Licensing offers listed. + ### Network connections The following downloadable spreadsheet lists the services and their associated URLs that your network must be able to connect to. You should ensure that there are no firewall or network filtering rules that would deny access to these URLs, or you may need to create an *allow* rule specifically for them. From 4607899d82de69af92819cff09dd4bfd77c71cdb Mon Sep 17 00:00:00 2001 From: MaratMussabekov <48041687+MaratMussabekov@users.noreply.github.com> Date: Tue, 25 Aug 2020 21:16:09 +0500 Subject: [PATCH 02/76] Update linux-install-manually.md --- .../linux-install-manually.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/windows/security/threat-protection/microsoft-defender-atp/linux-install-manually.md b/windows/security/threat-protection/microsoft-defender-atp/linux-install-manually.md index 1746f4fcb3..b756561136 100644 --- a/windows/security/threat-protection/microsoft-defender-atp/linux-install-manually.md +++ b/windows/security/threat-protection/microsoft-defender-atp/linux-install-manually.md @@ -48,6 +48,12 @@ In order to preview new features and provide early feedback, it is recommended t ### RHEL and variants (CentOS and Oracle Linux) +- Install `yum-utils` if it isn't installed yet: + + ```bash + sudo yum install yum-utils + ``` + - Note your distribution and version, and identify the closest entry for it under `https://packages.microsoft.com/config/`. In the below commands, replace *[distro]* and *[version]* with the information you've identified: @@ -71,12 +77,6 @@ In order to preview new features and provide early feedback, it is recommended t sudo rpm --import http://packages.microsoft.com/keys/microsoft.asc ``` -- Install `yum-utils` if it isn't installed yet: - - ```bash - sudo yum install yum-utils - ``` - - Download and make usable all the metadata for the currently enabled yum repositories: ```bash @@ -328,4 +328,4 @@ When upgrading your operating system to a new major version, you must first unin ## Uninstallation -See [Uninstall](linux-resources.md#uninstall) for details on how to remove Microsoft Defender ATP for Linux from client devices. \ No newline at end of file +See [Uninstall](linux-resources.md#uninstall) for details on how to remove Microsoft Defender ATP for Linux from client devices. From cee429d94e43e66837ff4b4d710461b3cba52f21 Mon Sep 17 00:00:00 2001 From: MaratMussabekov <48041687+MaratMussabekov@users.noreply.github.com> Date: Wed, 26 Aug 2020 12:11:52 +0500 Subject: [PATCH 03/76] Update windows/security/threat-protection/microsoft-defender-atp/microsoft-defender-atp-mac.md Co-authored-by: JohanFreelancer9 <48568725+JohanFreelancer9@users.noreply.github.com> --- .../microsoft-defender-atp/microsoft-defender-atp-mac.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/security/threat-protection/microsoft-defender-atp/microsoft-defender-atp-mac.md b/windows/security/threat-protection/microsoft-defender-atp/microsoft-defender-atp-mac.md index 3f296b7a24..6526e63f1a 100644 --- a/windows/security/threat-protection/microsoft-defender-atp/microsoft-defender-atp-mac.md +++ b/windows/security/threat-protection/microsoft-defender-atp/microsoft-defender-atp-mac.md @@ -76,7 +76,7 @@ Microsoft Defender Advanced Threat Protection for Mac requires one of the follow - Microsoft 365 A5 (M365 A5) > [!NOTE] -> Eligible Licensed Users may use Microsoft Defender Advanced Threat Protection on up to five concurrent devices. +> Eligible licensed users may use Microsoft Defender Advanced Threat Protection on up to five concurrent devices. > Microsoft Defender Advanced Threat Protection is also available for purchase from a Cloud Solution Provider (CSP). When purchased via a CSP, it does not require Microsoft Volume Licensing offers listed. ### Network connections From 146fb0e3db1993cd94e73d513bbcb9fabfc4a87f Mon Sep 17 00:00:00 2001 From: VARADHARAJAN K <3296790+RAJU2529@users.noreply.github.com> Date: Sat, 12 Sep 2020 18:05:56 +0530 Subject: [PATCH 04/76] removed download link, added explanation as per the user report #8242 , so I removed the download link and added an explanation. --- windows/client-management/troubleshoot-tcpip-netmon.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/client-management/troubleshoot-tcpip-netmon.md b/windows/client-management/troubleshoot-tcpip-netmon.md index f708897928..ed8b6090cf 100644 --- a/windows/client-management/troubleshoot-tcpip-netmon.md +++ b/windows/client-management/troubleshoot-tcpip-netmon.md @@ -19,7 +19,7 @@ In this topic, you will learn how to use Microsoft Network Monitor 3.4, which is > [Note] > Network Monitor is the archived protocol analyzer and is no longer under development. **Microsoft Message Analyzer** is the replacement for Network Monitor. For more details, see [Microsoft Message Analyzer Operating Guide](https://docs.microsoft.com/message-analyzer/microsoft-message-analyzer-operating-guide). -To get started, [download and run NM34_x64.exe](https://www.microsoft.com/download/details.aspx?id=4865). When you install Network Monitor, it installs its driver and hooks it to all the network adapters installed on the device. You can see the same on the adapter properties, as shown in the following image. +To get started, **run NM34_x64.exe**(we are leaving this page available for those who have downloaded the tool previously). When you install Network Monitor, it installs its driver and hooks it to all the network adapters installed on the device. You can see the same on the adapter properties, as shown in the following image. ![Adapters](images/nm-adapters.png) From 994a5681699589c5b76f7b6d7c21c46d5ebc037e Mon Sep 17 00:00:00 2001 From: MaratMussabekov <48041687+MaratMussabekov@users.noreply.github.com> Date: Wed, 16 Sep 2020 16:01:26 +0500 Subject: [PATCH 05/76] Update vpn-conditional-access.md --- .../identity-protection/vpn/vpn-conditional-access.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/windows/security/identity-protection/vpn/vpn-conditional-access.md b/windows/security/identity-protection/vpn/vpn-conditional-access.md index df414d1e79..c368ed6c90 100644 --- a/windows/security/identity-protection/vpn/vpn-conditional-access.md +++ b/windows/security/identity-protection/vpn/vpn-conditional-access.md @@ -72,8 +72,8 @@ Two client-side configuration service providers are leveraged for VPN device com - Provisions the Health Attestation Certificate received from the HAS - Upon request, forwards the Health Attestation Certificate (received from HAS) and related runtime information to the MDM server for verification ->[!NOTE] ->Currently, it is required that certificates be issued from an on-premises CA, and that SSO be enabled in the user’s VPN profile. This will enable the user to obtain Kerberos tickets in order to access resources on-premises. Kerberos currently does not support the use of Azure AD certificates. +> [!NOTE] +> Currently, it is required that certificates used for obtaining Kerberos tickets must be issued from an on-premises CA, and that SSO must be enabled in the user’s VPN profile. This will enable the user to access on-premises resources. ## Client connection flow The VPN client side connection flow works as follows: From 3ef62e034a03c7100773f4bdffd0aa561030895d Mon Sep 17 00:00:00 2001 From: VARADHARAJAN K <3296790+RAJU2529@users.noreply.github.com> Date: Fri, 18 Sep 2020 17:24:27 +0530 Subject: [PATCH 06/76] Update windows/client-management/troubleshoot-tcpip-netmon.md accepted Co-authored-by: Trond B. Krokli <38162891+illfated@users.noreply.github.com> --- windows/client-management/troubleshoot-tcpip-netmon.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/client-management/troubleshoot-tcpip-netmon.md b/windows/client-management/troubleshoot-tcpip-netmon.md index ed8b6090cf..f9f1d95096 100644 --- a/windows/client-management/troubleshoot-tcpip-netmon.md +++ b/windows/client-management/troubleshoot-tcpip-netmon.md @@ -16,7 +16,7 @@ manager: dansimp In this topic, you will learn how to use Microsoft Network Monitor 3.4, which is a tool for capturing network traffic. -> [Note] +> [!NOTE] > Network Monitor is the archived protocol analyzer and is no longer under development. **Microsoft Message Analyzer** is the replacement for Network Monitor. For more details, see [Microsoft Message Analyzer Operating Guide](https://docs.microsoft.com/message-analyzer/microsoft-message-analyzer-operating-guide). To get started, **run NM34_x64.exe**(we are leaving this page available for those who have downloaded the tool previously). When you install Network Monitor, it installs its driver and hooks it to all the network adapters installed on the device. You can see the same on the adapter properties, as shown in the following image. From 3d7029f03d2ceadcfc1bd519dab10f70d27e0a4c Mon Sep 17 00:00:00 2001 From: VARADHARAJAN K <3296790+RAJU2529@users.noreply.github.com> Date: Fri, 18 Sep 2020 23:58:39 +0530 Subject: [PATCH 07/76] Update windows/client-management/troubleshoot-tcpip-netmon.md accepted Co-authored-by: Trond B. Krokli <38162891+illfated@users.noreply.github.com> --- windows/client-management/troubleshoot-tcpip-netmon.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/client-management/troubleshoot-tcpip-netmon.md b/windows/client-management/troubleshoot-tcpip-netmon.md index f9f1d95096..7f7855bca2 100644 --- a/windows/client-management/troubleshoot-tcpip-netmon.md +++ b/windows/client-management/troubleshoot-tcpip-netmon.md @@ -19,7 +19,7 @@ In this topic, you will learn how to use Microsoft Network Monitor 3.4, which is > [!NOTE] > Network Monitor is the archived protocol analyzer and is no longer under development. **Microsoft Message Analyzer** is the replacement for Network Monitor. For more details, see [Microsoft Message Analyzer Operating Guide](https://docs.microsoft.com/message-analyzer/microsoft-message-analyzer-operating-guide). -To get started, **run NM34_x64.exe**(we are leaving this page available for those who have downloaded the tool previously). When you install Network Monitor, it installs its driver and hooks it to all the network adapters installed on the device. You can see the same on the adapter properties, as shown in the following image. +To get started, [download and run NM34_x64.exe](https://www.microsoft.com/download/details.aspx?id=4865). When you install Network Monitor, it installs its driver and hooks it to all the network adapters installed on the device. You can see the same on the adapter properties, as shown in the following image. ![Adapters](images/nm-adapters.png) From 6571339263ff06e2be3f1e05fc31e3838d10b38f Mon Sep 17 00:00:00 2001 From: MaratMussabekov <48041687+MaratMussabekov@users.noreply.github.com> Date: Wed, 23 Sep 2020 11:15:05 +0500 Subject: [PATCH 08/76] Update note about CA root requirements --- .../hello-for-business/hello-hybrid-cert-whfb-settings-pki.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/windows/security/identity-protection/hello-for-business/hello-hybrid-cert-whfb-settings-pki.md b/windows/security/identity-protection/hello-for-business/hello-hybrid-cert-whfb-settings-pki.md index 8a785dcf5f..a0855330fb 100644 --- a/windows/security/identity-protection/hello-for-business/hello-hybrid-cert-whfb-settings-pki.md +++ b/windows/security/identity-protection/hello-for-business/hello-hybrid-cert-whfb-settings-pki.md @@ -95,8 +95,7 @@ Sign-in a certificate authority or management workstations with _Enterprise Admi The certificate template is configured to supersede all the certificate templates provided in the certificate templates superseded templates list. However, the certificate template and the superseding of certificate templates is not active until you publish the certificate template to one or more certificate authorities. > [!NOTE] -> * The Domain Controller Certificate must be present in the NTAuth store. By default, Microsoft Enterprise CAs are added to the NTAuth store. -> * If you are using a 3rd party CA, add the certificate to the NTAuth store. If the Domain Controller Certificate is not present in the NTAuth store, user authentication will fail. +> The domain controller's certificate must chain to a root in the NTAuth store. By default, the Active Directory Certificate Authority's root certificate is added to the NTAuth store. If you are using a third-party CA, this may not be done by default. If the domain controller certificate does not chain to a root in the NTAuth store, user authentication will fail. ### Enrollment Agent certificate template From 296b0f622da566c4dea18ba731dca888c460c063 Mon Sep 17 00:00:00 2001 From: Marty Hernandez Avedon Date: Wed, 23 Sep 2020 16:16:05 -0400 Subject: [PATCH 09/76] clarifying behavior on network shares --- ...figure-advanced-scan-types-microsoft-defender-antivirus.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/windows/security/threat-protection/microsoft-defender-antivirus/configure-advanced-scan-types-microsoft-defender-antivirus.md b/windows/security/threat-protection/microsoft-defender-antivirus/configure-advanced-scan-types-microsoft-defender-antivirus.md index 93b12016f3..ee3e692d4a 100644 --- a/windows/security/threat-protection/microsoft-defender-antivirus/configure-advanced-scan-types-microsoft-defender-antivirus.md +++ b/windows/security/threat-protection/microsoft-defender-antivirus/configure-advanced-scan-types-microsoft-defender-antivirus.md @@ -59,8 +59,8 @@ Specify the level of subfolders within an archive folder to scan | Scan > Specif Specify the maximum size (in kilobytes) of archive files that should be scanned. The default, **0**, applies no limit | Scan > Specify the maximum size of archive files to be scanned | No limit | Not available Configure low CPU priority for scheduled scans | Scan > Configure low CPU priority for scheduled scans | Disabled | Not available ->[!NOTE] ->If real-time protection is enabled, files are scanned before they are accessed and executed. The scanning scope includes all files, including those on mounted removable devices such as USB drives. +> [!NOTE] +> If real-time protection is turned on, files are scanned before they are accessed and executed. The scanning scope includes all files, including files on mounted removable media, such as USB drives. If the device performing the scan has real-time protection or on-access protection turned on, the scan will also include network shares. ## Use PowerShell to configure scanning options From a085daa017093f21ad92d2879d44ed16828a06cb Mon Sep 17 00:00:00 2001 From: MaratMussabekov <48041687+MaratMussabekov@users.noreply.github.com> Date: Thu, 24 Sep 2020 11:52:00 +0500 Subject: [PATCH 10/76] Update hello-hybrid-key-whfb-settings-dir-sync.md --- .../hello-hybrid-key-whfb-settings-dir-sync.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/security/identity-protection/hello-for-business/hello-hybrid-key-whfb-settings-dir-sync.md b/windows/security/identity-protection/hello-for-business/hello-hybrid-key-whfb-settings-dir-sync.md index ce98019039..d4a889088a 100644 --- a/windows/security/identity-protection/hello-for-business/hello-hybrid-key-whfb-settings-dir-sync.md +++ b/windows/security/identity-protection/hello-for-business/hello-hybrid-key-whfb-settings-dir-sync.md @@ -39,7 +39,7 @@ Sign-in a domain controller or management workstation with _Domain Admin_ equiva 2. Click the **Users** container in the navigation pane. 3. Right-click **Key Admins** in the details pane and click **Properties**. 4. Click the **Members** tab and click **Add** -5. In the **Enter the object names to select** text box, type the name of the Azure AD Connect service account. Click **OK**. +5. In the **Enter the object names to select** text box, type the name of the service account used as an AD DS Connector account. Click **OK**. 6. Click **OK** to return to **Active Directory Users and Computers**. ### Section Review From 21c9b5278405cc3a9420ff2d96f86e5169023407 Mon Sep 17 00:00:00 2001 From: Denise Vangel-MSFT Date: Thu, 24 Sep 2020 11:39:36 -0700 Subject: [PATCH 11/76] Update manage-updates-baselines-microsoft-defender-antivirus.md --- ...-baselines-microsoft-defender-antivirus.md | 27 ++++++++++++++++++- 1 file changed, 26 insertions(+), 1 deletion(-) diff --git a/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md b/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md index 514ee0334b..8111a003d1 100644 --- a/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md +++ b/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md @@ -13,7 +13,7 @@ ms.author: deniseb ms.custom: nextgen ms.reviewer: manager: dansimp -ms.date: 09/10/2020 +ms.date: 09/24/2020 --- # Manage Microsoft Defender Antivirus updates and apply baselines @@ -66,6 +66,31 @@ All our updates contain: * integration improvements (Cloud, MTP)
+ September-2020 (Platform: | Engine: ) + + Security intelligence update version: **** + Released: **** + Platform: **** + Engine: **** + Support phase: **Security and Critical Updates** + +### What's new +- Require administrative privileges for quarantine restore +- Support for XML formatted events +- Provide CSP support to ignore exclusion merge +- New management interfaces for:
+ - UDP Inspection + - Network Protection on Server 2019 + - IP Address exclusions for Network Protection +- Improve visibility into TPM logs +- Improved Office VBA script scanning + +### Known Issues +No known issues +
+
+
+
August-2020 (Platform: 4.18.2008.9 | Engine: 1.1.17400.5)  Security intelligence update version: **1.323.9.0** From 55d6d377f63a65069a10a2d2774f301799ce7927 Mon Sep 17 00:00:00 2001 From: Denise Vangel-MSFT Date: Thu, 24 Sep 2020 11:50:29 -0700 Subject: [PATCH 12/76] Update manage-updates-baselines-microsoft-defender-antivirus.md --- ...tes-baselines-microsoft-defender-antivirus.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md b/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md index 8111a003d1..1dc23f0a42 100644 --- a/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md +++ b/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md @@ -61,17 +61,17 @@ For more information, see [Manage the sources for Microsoft Defender Antivirus p For information how to update or how to install the platform update, please see [Update for Windows Defender antimalware platform](https://support.microsoft.com/help/4052623/update-for-windows-defender-antimalware-platform). All our updates contain: -* performance improvements -* serviceability improvements -* integration improvements (Cloud, MTP) +- performance improvements +- serviceability improvements +- integration improvements (Cloud, MTP)
September-2020 (Platform: | Engine: ) - Security intelligence update version: **** - Released: **** - Platform: **** - Engine: **** + Security intelligence update version: **versionnumber** + Released: **releasedate** + Platform: **platformnumber** + Engine: **enginenumber**  Support phase: **Security and Critical Updates** ### What's new @@ -104,7 +104,7 @@ No known issues * Improved scan event telemetry * Improved behavior monitoring for memory scans * Improved macro streams scanning -* Added "AMRunningMode" to Get-MpComputerStatus Powershell CmdLet +* Added `AMRunningMode` to Get-MpComputerStatus PowerShell CmdLet ### Known Issues No known issues From dcc2f076ea41901eeb50b5da199f212975afb5db Mon Sep 17 00:00:00 2001 From: VARADHARAJAN K <3296790+RAJU2529@users.noreply.github.com> Date: Fri, 25 Sep 2020 19:45:23 +0530 Subject: [PATCH 13/76] addedm update links of 1903 , 1909 and 2004 as per the user report #8354 , so I added update links of 1903,1909 and 2004 --- windows/client-management/troubleshoot-stop-errors.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/windows/client-management/troubleshoot-stop-errors.md b/windows/client-management/troubleshoot-stop-errors.md index 7eabdf0411..0ed8e1db70 100644 --- a/windows/client-management/troubleshoot-stop-errors.md +++ b/windows/client-management/troubleshoot-stop-errors.md @@ -43,7 +43,9 @@ To troubleshoot Stop error messages, follow these general steps: 2. As a best practice, we recommend that you do the following: a. Make sure that you install the latest Windows updates, cumulative updates, and rollup updates. To verify the update status, refer to the appropriate update history for your system: - + - [Windows 10, version 2004](https://support.microsoft.com/help/4555932) + - [Windows 10, version 1909](https://support.microsoft.com/help/4529964) + - [Windows 10, version 1903](https://support.microsoft.com/help/4498140) - [Windows 10, version 1809](https://support.microsoft.com/help/4464619) - [Windows 10, version 1803](https://support.microsoft.com/help/4099479) - [Windows 10, version 1709](https://support.microsoft.com/help/4043454) From dbfaabe9b039eb3f19d3cee07b7ef169e33312f2 Mon Sep 17 00:00:00 2001 From: MaratMussabekov <48041687+MaratMussabekov@users.noreply.github.com> Date: Sat, 26 Sep 2020 23:03:36 +0500 Subject: [PATCH 14/76] Update windows/security/identity-protection/hello-for-business/hello-hybrid-key-whfb-settings-dir-sync.md Co-authored-by: JohanFreelancer9 <48568725+JohanFreelancer9@users.noreply.github.com> --- .../hello-hybrid-key-whfb-settings-dir-sync.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/security/identity-protection/hello-for-business/hello-hybrid-key-whfb-settings-dir-sync.md b/windows/security/identity-protection/hello-for-business/hello-hybrid-key-whfb-settings-dir-sync.md index d4a889088a..3bd0bbe112 100644 --- a/windows/security/identity-protection/hello-for-business/hello-hybrid-key-whfb-settings-dir-sync.md +++ b/windows/security/identity-protection/hello-for-business/hello-hybrid-key-whfb-settings-dir-sync.md @@ -39,7 +39,7 @@ Sign-in a domain controller or management workstation with _Domain Admin_ equiva 2. Click the **Users** container in the navigation pane. 3. Right-click **Key Admins** in the details pane and click **Properties**. 4. Click the **Members** tab and click **Add** -5. In the **Enter the object names to select** text box, type the name of the service account used as an AD DS Connector account. Click **OK**. +5. In the **Enter the object names to select** text box, type the name of the service account used as an AD DS Connector account and click **OK**. 6. Click **OK** to return to **Active Directory Users and Computers**. ### Section Review From fe887186cd821dda6759aa04fd584a526df5f364 Mon Sep 17 00:00:00 2001 From: Lindsay <45809756+lindspea@users.noreply.github.com> Date: Mon, 28 Sep 2020 09:27:17 +0200 Subject: [PATCH 15/76] Update account-lockout-threshold.md Added note. --- .../security-policy-settings/account-lockout-threshold.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/windows/security/threat-protection/security-policy-settings/account-lockout-threshold.md b/windows/security/threat-protection/security-policy-settings/account-lockout-threshold.md index 3db828212a..20f886d1ec 100644 --- a/windows/security/threat-protection/security-policy-settings/account-lockout-threshold.md +++ b/windows/security/threat-protection/security-policy-settings/account-lockout-threshold.md @@ -87,6 +87,9 @@ For more information about Windows security baseline recommendations for account This section describes how an attacker might exploit a feature or its configuration, how to implement the countermeasure, and the possible negative consequences of countermeasure implementation. +> [!NOTE] +> A lockout threshold policy will apply to both local member computer users and Domain Users, in order to allow mitigation of issues as described under "Vulnerability". The Built-In Administrator account however, whilst a highly privileged account, has a different risk profile and is excluded from this policy. This ensures there is no scenario where an administrator cannot logon to remediate an issue. As an administrator, there are additional mitigation strategies available, such as a strong password. See also [Appendix D: Securing Built-In Administrator Accounts in Active Directory](https://docs.microsoft.com/windows-server/identity/ad-ds/plan/security-best-practices/appendix-d--securing-built-in-administrator-accounts-in-active-directory). + ### Vulnerability Brute force password attacks can use automated methods to try millions of password combinations for any user account. The effectiveness of such attacks can be almost eliminated if you limit the number of failed sign-in attempts that can be performed. From 37fa946455d231fd9c80946dbec8819b3f9088d7 Mon Sep 17 00:00:00 2001 From: VARADHARAJAN K <3296790+RAJU2529@users.noreply.github.com> Date: Mon, 28 Sep 2020 14:15:30 +0530 Subject: [PATCH 16/76] fixed missing text as per the user report #8370 , so i added the word **Password** --- .../security-policy-settings/minimum-password-length.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/security/threat-protection/security-policy-settings/minimum-password-length.md b/windows/security/threat-protection/security-policy-settings/minimum-password-length.md index 35eaa8ac76..60d1136acd 100644 --- a/windows/security/threat-protection/security-policy-settings/minimum-password-length.md +++ b/windows/security/threat-protection/security-policy-settings/minimum-password-length.md @@ -76,7 +76,7 @@ Types of password attacks include dictionary attacks (which attempt to use commo ### Countermeasure -Configure the **** policy setting to a value of 8 or more. If the number of characters is set to 0, no password will be required. +Configure the **Password** policy setting to a value of 8 or more. If the number of characters is set to 0, no password will be required. In most environments, we recommend an eight-character password because it is long enough to provide adequate security, but not too difficult for users to easily remember. This configuration provides adequate defense against a brute force attack. Using the [Password must meet complexity requirements](password-must-meet-complexity-requirements.md) policy setting in addition to the **Minimum password length** setting helps reduce the possibility of a dictionary attack. From 4cae659e0a5849ab535c4c3fc559a987f1b4a7a4 Mon Sep 17 00:00:00 2001 From: VARADHARAJAN K <3296790+RAJU2529@users.noreply.github.com> Date: Mon, 28 Sep 2020 18:10:53 +0530 Subject: [PATCH 17/76] Update windows/security/threat-protection/security-policy-settings/minimum-password-length.md accepted Co-authored-by: Trond B. Krokli <38162891+illfated@users.noreply.github.com> --- .../security-policy-settings/minimum-password-length.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/security/threat-protection/security-policy-settings/minimum-password-length.md b/windows/security/threat-protection/security-policy-settings/minimum-password-length.md index 60d1136acd..74ed307f82 100644 --- a/windows/security/threat-protection/security-policy-settings/minimum-password-length.md +++ b/windows/security/threat-protection/security-policy-settings/minimum-password-length.md @@ -76,7 +76,7 @@ Types of password attacks include dictionary attacks (which attempt to use commo ### Countermeasure -Configure the **Password** policy setting to a value of 8 or more. If the number of characters is set to 0, no password will be required. +Configure the **Minimum password length** policy setting to a value of 8 or more. If the number of characters is set to 0, no password will be required. In most environments, we recommend an eight-character password because it is long enough to provide adequate security, but not too difficult for users to easily remember. This configuration provides adequate defense against a brute force attack. Using the [Password must meet complexity requirements](password-must-meet-complexity-requirements.md) policy setting in addition to the **Minimum password length** setting helps reduce the possibility of a dictionary attack. From 4e505d87b8094bf57886f2ddcedd10e43a847c78 Mon Sep 17 00:00:00 2001 From: Denise Vangel-MSFT Date: Mon, 28 Sep 2020 14:03:29 -0700 Subject: [PATCH 18/76] Update manage-updates-baselines-microsoft-defender-antivirus.md --- ...manage-updates-baselines-microsoft-defender-antivirus.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md b/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md index 087ceb8a30..819f0d2e96 100644 --- a/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md +++ b/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md @@ -74,9 +74,9 @@ All our updates contain: September-2020 (Platform: | Engine: )  Security intelligence update version: **versionnumber** - Released: **releasedate** - Platform: **platformnumber** - Engine: **enginenumber** + Released: **September 28, 2020** + Platform: **4.18.xxxx.x** + Engine: **1.1.14500.2**  Support phase: **Security and Critical Updates** ### What's new From f4ffb284c25858f152691bf00615eabd84d6aa32 Mon Sep 17 00:00:00 2001 From: Denise Vangel-MSFT Date: Mon, 28 Sep 2020 14:16:19 -0700 Subject: [PATCH 19/76] Update manage-updates-baselines-microsoft-defender-antivirus.md --- .../manage-updates-baselines-microsoft-defender-antivirus.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md b/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md index 819f0d2e96..b628cd0111 100644 --- a/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md +++ b/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md @@ -73,7 +73,7 @@ All our updates contain:
September-2020 (Platform: | Engine: ) - Security intelligence update version: **versionnumber** + Security intelligence update version: **1.xxx.x.x**  Released: **September 28, 2020**  Platform: **4.18.xxxx.x**  Engine: **1.1.14500.2** From 2ad5f1b2418209f0e2e5c02010a041cffb54a2e8 Mon Sep 17 00:00:00 2001 From: Lindsay <45809756+lindspea@users.noreply.github.com> Date: Wed, 30 Sep 2020 17:07:15 +0200 Subject: [PATCH 20/76] Update windows/security/threat-protection/security-policy-settings/account-lockout-threshold.md Co-authored-by: JohanFreelancer9 <48568725+JohanFreelancer9@users.noreply.github.com> --- .../security-policy-settings/account-lockout-threshold.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/security/threat-protection/security-policy-settings/account-lockout-threshold.md b/windows/security/threat-protection/security-policy-settings/account-lockout-threshold.md index 20f886d1ec..55f3b22031 100644 --- a/windows/security/threat-protection/security-policy-settings/account-lockout-threshold.md +++ b/windows/security/threat-protection/security-policy-settings/account-lockout-threshold.md @@ -88,7 +88,7 @@ For more information about Windows security baseline recommendations for account This section describes how an attacker might exploit a feature or its configuration, how to implement the countermeasure, and the possible negative consequences of countermeasure implementation. > [!NOTE] -> A lockout threshold policy will apply to both local member computer users and Domain Users, in order to allow mitigation of issues as described under "Vulnerability". The Built-In Administrator account however, whilst a highly privileged account, has a different risk profile and is excluded from this policy. This ensures there is no scenario where an administrator cannot logon to remediate an issue. As an administrator, there are additional mitigation strategies available, such as a strong password. See also [Appendix D: Securing Built-In Administrator Accounts in Active Directory](https://docs.microsoft.com/windows-server/identity/ad-ds/plan/security-best-practices/appendix-d--securing-built-in-administrator-accounts-in-active-directory). +> A lockout threshold policy will apply to both local member computer users and domain users, in order to allow mitigation of issues as described under "Vulnerability". The built-in Administrator account, however, whilst a highly privileged account, has a different risk profile and is excluded from this policy. This ensures there is no scenario where an administrator cannot sign in to remediate an issue. As an administrator, there are additional mitigation strategies available, such as a strong password. See also [Appendix D: Securing Built-In Administrator Accounts in Active Directory](https://docs.microsoft.com/windows-server/identity/ad-ds/plan/security-best-practices/appendix-d--securing-built-in-administrator-accounts-in-active-directory). ### Vulnerability From a0591322a45cf907c9f98cbc062e15cc6e151d29 Mon Sep 17 00:00:00 2001 From: ImranHabib <47118050+joinimran@users.noreply.github.com> Date: Wed, 30 Sep 2020 22:15:34 +0500 Subject: [PATCH 21/76] Link Update Updated a link to the correct source. Problem: https://github.com/MicrosoftDocs/windows-itpro-docs/issues/7972 --- .../create-wip-policy-using-intune-azure.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/security/information-protection/windows-information-protection/create-wip-policy-using-intune-azure.md b/windows/security/information-protection/windows-information-protection/create-wip-policy-using-intune-azure.md index 73946540c5..b3788ff49e 100644 --- a/windows/security/information-protection/windows-information-protection/create-wip-policy-using-intune-azure.md +++ b/windows/security/information-protection/windows-information-protection/create-wip-policy-using-intune-azure.md @@ -622,7 +622,7 @@ You can restrict which files are protected by WIP when they are downloaded from - [What is Azure Rights Management?](https://docs.microsoft.com/information-protection/understand-explore/what-is-azure-rms) -- [Create and deploy Windows Information Protection (WIP) app protection policy with Intune and MAM](https://docs.microsoft.com/intune/deploy-use/create-windows-information-protection-policy-with-intune) +- [Create and deploy Windows Information Protection (WIP) app protection policy with Intune and MAM](https://docs.microsoft.com/windows/security/information-protection/windows-information-protection/overview-create-wip-policy) - [Intune MAM Without Enrollment](https://blogs.technet.microsoft.com/configmgrdogs/2016/02/04/intune-mam-without-enrollment/) From 01259a7dbf009d8215b7900348e9554b6e4a83de Mon Sep 17 00:00:00 2001 From: Caroline Gitonga Date: Wed, 30 Sep 2020 22:46:32 +0300 Subject: [PATCH 22/76] Add spclient.wg.spotify.com Add spclient.wg.spotify.com to Windows Family and Home --- .../privacy/windows-endpoints-1909-non-enterprise-editions.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/windows/privacy/windows-endpoints-1909-non-enterprise-editions.md b/windows/privacy/windows-endpoints-1909-non-enterprise-editions.md index d0d7ff467f..7b104bdcb0 100644 --- a/windows/privacy/windows-endpoints-1909-non-enterprise-editions.md +++ b/windows/privacy/windows-endpoints-1909-non-enterprise-editions.md @@ -95,6 +95,7 @@ The following methodology was used to derive the network endpoints: |wdcp.microsoft.com|HTTPS|Used for Windows Defender when Cloud-based Protection is enabled |activity.windows.com|TLSV1.2|Used by Activity Feed Service which enables multiple cross-device data roaming scenarios on Windows |adl.windows.com|HTTP|Used for compatibility database updates for Windows +|spclient.wg.spotify.com|TLSV1.2|Used for Spotify Live Tile ## Windows 10 Pro @@ -159,6 +160,7 @@ The following methodology was used to derive the network endpoints: |windows.policies.live.net|HTTP|OneDrive |activity.windows.com|TLSV1.2|Used by Activity Feed Service which enables multiple cross-device data roaming scenarios on Windows |adl.windows.com|HTTP|Used for compatibility database updates for Windows +|spclient.wg.spotify.com|TLSV1.2|Used for Spotify Live Tile ## Windows 10 Education From 40b9101057aefe8a750fca3f005877f3410b662a Mon Sep 17 00:00:00 2001 From: Denise Vangel-MSFT Date: Wed, 30 Sep 2020 14:03:04 -0700 Subject: [PATCH 23/76] Update manage-updates-baselines-microsoft-defender-antivirus.md --- ...ates-baselines-microsoft-defender-antivirus.md | 15 +++++++-------- 1 file changed, 7 insertions(+), 8 deletions(-) diff --git a/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md b/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md index b628cd0111..c3033503c9 100644 --- a/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md +++ b/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md @@ -13,7 +13,7 @@ ms.author: deniseb ms.custom: nextgen ms.reviewer: manager: dansimp -ms.date: 09/28/2020 +ms.date: 09/30/2020 --- # Manage Microsoft Defender Antivirus updates and apply baselines @@ -33,8 +33,7 @@ There are two types of updates related to keeping Microsoft Defender Antivirus u > [!IMPORTANT] > Keeping Microsoft Defender Antivirus up to date is critical to assure your devices have the latest technology and features needed to protect against new malware and attack techniques. > This also applies to devices where Microsoft Defender Antivirus is running in [passive mode](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-antivirus/microsoft-defender-antivirus-compatibility). - -> [!NOTE] +> > You can use the below URL to find out what are the current versions: > [https://www.microsoft.com/security/encyclopedia/adlpackages.aspx?action=info](https://www.microsoft.com/security/encyclopedia/adlpackages.aspx?action=info) @@ -47,7 +46,7 @@ Microsoft Defender Antivirus uses [cloud-delivered protection](utilize-microsoft > Microsoft Defender Antivirus: KB2267602 > System Center Endpoint Protection: KB2461484 -The cloud-delivered protection is always on and requires an active connection to the Internet to function, while the security intelligence updates occur on a scheduled cadence (configurable via policy). See the [Utilize Microsoft cloud-provided protection in Microsoft Defender Antivirus](utilize-microsoft-cloud-protection-microsoft-defender-antivirus.md) topic for more details about enabling and configuring cloud-provided protection. +The cloud-delivered protection is always on and requires an active connection to the Internet to function, while the security intelligence updates occur on a scheduled cadence (configurable via policy). See [Use Microsoft cloud-provided protection in Microsoft Defender Antivirus](utilize-microsoft-cloud-protection-microsoft-defender-antivirus.md) for more details about enabling and configuring cloud-provided protection. Engine updates are included with the security intelligence updates and are released on a monthly cadence. @@ -73,10 +72,10 @@ All our updates contain:
September-2020 (Platform: | Engine: ) - Security intelligence update version: **1.xxx.x.x** - Released: **September 28, 2020** - Platform: **4.18.xxxx.x** - Engine: **1.1.14500.2** + Security intelligence update version: **1.323.2248.0** + Released: **September 30, 2020** + Platform: **4.18.2008.9** + Engine: **1.1.17400.5**  Support phase: **Security and Critical Updates** ### What's new From daf36105d2edd742ad443c51b2fd68ae3f668b3b Mon Sep 17 00:00:00 2001 From: Denise Vangel-MSFT Date: Wed, 30 Sep 2020 14:10:23 -0700 Subject: [PATCH 24/76] Update manage-updates-baselines-microsoft-defender-antivirus.md --- .../manage-updates-baselines-microsoft-defender-antivirus.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md b/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md index c3033503c9..adb4829210 100644 --- a/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md +++ b/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md @@ -46,7 +46,7 @@ Microsoft Defender Antivirus uses [cloud-delivered protection](utilize-microsoft > Microsoft Defender Antivirus: KB2267602 > System Center Endpoint Protection: KB2461484 -The cloud-delivered protection is always on and requires an active connection to the Internet to function, while the security intelligence updates occur on a scheduled cadence (configurable via policy). See [Use Microsoft cloud-provided protection in Microsoft Defender Antivirus](utilize-microsoft-cloud-protection-microsoft-defender-antivirus.md) for more details about enabling and configuring cloud-provided protection. +Cloud-delivered protection is always on and requires an active connection to the Internet to function. Security intelligence updates occur on a scheduled cadence (configurable via policy). See [Use Microsoft cloud-provided protection in Microsoft Defender Antivirus](utilize-microsoft-cloud-protection-microsoft-defender-antivirus.md) for more details about enabling and configuring cloud-provided protection. Engine updates are included with the security intelligence updates and are released on a monthly cadence. From b562dba450907a92fb7f6acb904b1344c4fa1711 Mon Sep 17 00:00:00 2001 From: Denise Vangel-MSFT Date: Wed, 30 Sep 2020 14:10:46 -0700 Subject: [PATCH 25/76] Update manage-updates-baselines-microsoft-defender-antivirus.md --- .../manage-updates-baselines-microsoft-defender-antivirus.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md b/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md index adb4829210..ac8877221c 100644 --- a/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md +++ b/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md @@ -52,7 +52,7 @@ Engine updates are included with the security intelligence updates and are relea ## Product updates -Microsoft Defender Antivirus requires [monthly updates (KB4052623)](https://support.microsoft.com/help/4052623/update-for-windows-defender-antimalware-platform) (known as "platform updates"), and will receive major feature updates alongside Windows 10 releases. +Microsoft Defender Antivirus requires [monthly updates (KB4052623)](https://support.microsoft.com/help/4052623/update-for-windows-defender-antimalware-platform) (known as *platform updates*), and will receive major feature updates alongside Windows 10 releases. You can manage the distribution of updates through [Windows Server Update Service (WSUS)](https://docs.microsoft.com/mem/configmgr/protect/deploy-use/endpoint-definitions-wsus#to-synchronize-endpoint-protection-definition-updates-in-standalone-wsus), with [Microsoft Endpoint Configuration Manager](https://docs.microsoft.com/configmgr/sum/understand/software-updates-introduction), or in the normal manner that you deploy Microsoft and Windows updates to endpoints in your network. For more information, see [Manage the sources for Microsoft Defender Antivirus protection updates](https://docs.microsoft.com/mem/configmgr/protect/deploy-use/endpoint-definitions-wsus#to-synchronize-endpoint-protection-definition-updates-in-standalone-wsus). From a697f1f09b394e2d0e84ab963dbbf3c478cf85ed Mon Sep 17 00:00:00 2001 From: Denise Vangel-MSFT Date: Wed, 30 Sep 2020 14:12:14 -0700 Subject: [PATCH 26/76] Update manage-updates-baselines-microsoft-defender-antivirus.md --- .../manage-updates-baselines-microsoft-defender-antivirus.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md b/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md index ac8877221c..f2e94d18d5 100644 --- a/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md +++ b/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md @@ -46,7 +46,7 @@ Microsoft Defender Antivirus uses [cloud-delivered protection](utilize-microsoft > Microsoft Defender Antivirus: KB2267602 > System Center Endpoint Protection: KB2461484 -Cloud-delivered protection is always on and requires an active connection to the Internet to function. Security intelligence updates occur on a scheduled cadence (configurable via policy). See [Use Microsoft cloud-provided protection in Microsoft Defender Antivirus](utilize-microsoft-cloud-protection-microsoft-defender-antivirus.md) for more details about enabling and configuring cloud-provided protection. +Cloud-delivered protection is always on and requires an active connection to the Internet to function. Security intelligence updates occur on a scheduled cadence (configurable via policy). For more information, see [Use Microsoft cloud-provided protection in Microsoft Defender Antivirus](utilize-microsoft-cloud-protection-microsoft-defender-antivirus.md). Engine updates are included with the security intelligence updates and are released on a monthly cadence. From c46a8872e0d506457aba79cba5990e415fc72f2c Mon Sep 17 00:00:00 2001 From: Denise Vangel-MSFT Date: Wed, 30 Sep 2020 14:14:51 -0700 Subject: [PATCH 27/76] Update manage-updates-baselines-microsoft-defender-antivirus.md --- ...age-updates-baselines-microsoft-defender-antivirus.md | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md b/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md index f2e94d18d5..9cbf64e44c 100644 --- a/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md +++ b/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md @@ -48,13 +48,18 @@ Microsoft Defender Antivirus uses [cloud-delivered protection](utilize-microsoft Cloud-delivered protection is always on and requires an active connection to the Internet to function. Security intelligence updates occur on a scheduled cadence (configurable via policy). For more information, see [Use Microsoft cloud-provided protection in Microsoft Defender Antivirus](utilize-microsoft-cloud-protection-microsoft-defender-antivirus.md). -Engine updates are included with the security intelligence updates and are released on a monthly cadence. +Engine updates are included with security intelligence updates and are released on a monthly cadence. ## Product updates Microsoft Defender Antivirus requires [monthly updates (KB4052623)](https://support.microsoft.com/help/4052623/update-for-windows-defender-antimalware-platform) (known as *platform updates*), and will receive major feature updates alongside Windows 10 releases. -You can manage the distribution of updates through [Windows Server Update Service (WSUS)](https://docs.microsoft.com/mem/configmgr/protect/deploy-use/endpoint-definitions-wsus#to-synchronize-endpoint-protection-definition-updates-in-standalone-wsus), with [Microsoft Endpoint Configuration Manager](https://docs.microsoft.com/configmgr/sum/understand/software-updates-introduction), or in the normal manner that you deploy Microsoft and Windows updates to endpoints in your network. +You can manage the distribution of updates through one of the following methods: + +- [Windows Server Update Service (WSUS)](https://docs.microsoft.com/mem/configmgr/protect/deploy-use/endpoint-definitions-wsus#to-synchronize-endpoint-protection-definition-updates-in-standalone-wsus) +- [Microsoft Endpoint Configuration Manager](https://docs.microsoft.com/configmgr/sum/understand/software-updates-introduction) +- The usual method you use to deploy Microsoft and Windows updates to endpoints in your network. + For more information, see [Manage the sources for Microsoft Defender Antivirus protection updates](https://docs.microsoft.com/mem/configmgr/protect/deploy-use/endpoint-definitions-wsus#to-synchronize-endpoint-protection-definition-updates-in-standalone-wsus). > [!NOTE] From d16b6f5426f6eaae8f929e7b9cd330b055bcb3a4 Mon Sep 17 00:00:00 2001 From: Denise Vangel-MSFT Date: Wed, 30 Sep 2020 14:16:21 -0700 Subject: [PATCH 28/76] Update manage-updates-baselines-microsoft-defender-antivirus.md --- .../manage-updates-baselines-microsoft-defender-antivirus.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md b/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md index 9cbf64e44c..53ca8e0b20 100644 --- a/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md +++ b/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md @@ -63,11 +63,11 @@ You can manage the distribution of updates through one of the following methods: For more information, see [Manage the sources for Microsoft Defender Antivirus protection updates](https://docs.microsoft.com/mem/configmgr/protect/deploy-use/endpoint-definitions-wsus#to-synchronize-endpoint-protection-definition-updates-in-standalone-wsus). > [!NOTE] -> We release these monthly updates in phases. This results in multiple packages showing up in your WSUS server. +> We release these monthly updates in phases. This results in multiple packages visible in your WSUS server. ## Monthly platform and engine versions -For information how to update or how to install the platform update, please see [Update for Windows Defender antimalware platform](https://support.microsoft.com/help/4052623/update-for-windows-defender-antimalware-platform). +For information how to update or how to install the platform update, see [Update for Windows Defender antimalware platform](https://support.microsoft.com/help/4052623/update-for-windows-defender-antimalware-platform). All our updates contain: - performance improvements From 968150f66320afdab8bdb38bc7623412dcacf2e7 Mon Sep 17 00:00:00 2001 From: Denise Vangel-MSFT Date: Wed, 30 Sep 2020 14:18:52 -0700 Subject: [PATCH 29/76] Update manage-updates-baselines-microsoft-defender-antivirus.md --- ...age-updates-baselines-microsoft-defender-antivirus.md | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md b/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md index 53ca8e0b20..8976e1952a 100644 --- a/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md +++ b/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md @@ -193,7 +193,7 @@ No known issues ### What's new * WDfilter improvements -* Add more actionable event data to ASR detection events +* Add more actionable event data to attack surface reduction detection events * Fixed version information in diagnostic data and WMI * Fixed incorrect platform version in UI after platform update * Dynamic URL intel for Fileless threat protection @@ -218,7 +218,7 @@ No known issues * CPU Throttling option added to [MpCmdRun](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-antivirus/command-line-arguments-microsoft-defender-antivirus) * Improve diagnostic capability -* reduce Security intelligence timeout (5min) +* reduce Security intelligence timeout (5 min) * Extend AMSI engine internal log capability * Improve notification for process blocking @@ -298,8 +298,7 @@ When this update is installed, the device needs the jump package 4.10.2001.10 to
## Microsoft Defender Antivirus platform support -As stated above, platform and engine updates are provided on a monthly cadence. -Customers must stay current with the latest platform update to be fully supported. Our support structure is now dynamic, evolving into two phases depending on the availability of the latest platform version: +Platform and engine updates are provided on a monthly cadence. To be fully supported, keep current with the latest platform updates. Our support structure is dynamic, evolving into two phases depending on the availability of the latest platform version: * **Security and Critical Updates servicing phase** - When running the latest platform version, you will be eligible to receive both Security and Critical updates to the anti-malware platform. @@ -333,6 +332,6 @@ Article | Description ---|--- [Manage how protection updates are downloaded and applied](manage-protection-updates-microsoft-defender-antivirus.md) | Protection updates can be delivered through a number of sources. [Manage when protection updates should be downloaded and applied](manage-protection-update-schedule-microsoft-defender-antivirus.md) | You can schedule when protection updates should be downloaded. -[Manage updates for endpoints that are out of date](manage-outdated-endpoints-microsoft-defender-antivirus.md) | If an endpoint misses an update or scheduled scan, you can force an update or scan at the next log on. +[Manage updates for endpoints that are out of date](manage-outdated-endpoints-microsoft-defender-antivirus.md) | If an endpoint misses an update or scheduled scan, you can force an update or scan at the next logon. [Manage event-based forced updates](manage-event-based-updates-microsoft-defender-antivirus.md) | You can set protection updates to be downloaded at startup or after certain cloud-delivered protection events. [Manage updates for mobile devices and virtual machines (VMs)](manage-updates-mobile-devices-vms-microsoft-defender-antivirus.md)| You can specify settings, such as whether updates should occur on battery power, that are especially useful for mobile devices and virtual machines. From f292385ae885ea2e5f5f0b3531d4f4ced1d33279 Mon Sep 17 00:00:00 2001 From: Denise Vangel-MSFT Date: Wed, 30 Sep 2020 14:22:33 -0700 Subject: [PATCH 30/76] Update manage-updates-baselines-microsoft-defender-antivirus.md --- .../manage-updates-baselines-microsoft-defender-antivirus.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md b/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md index 8976e1952a..4f7c4b6487 100644 --- a/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md +++ b/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md @@ -75,7 +75,7 @@ All our updates contain: - integration improvements (Cloud, MTP)
- September-2020 (Platform: | Engine: ) + September-2020 (Platform: 4.18.2008.9 | Engine: 1.1.17400.5)  Security intelligence update version: **1.323.2248.0**  Released: **September 30, 2020** From 4194c77adc002251cde61f060128a47c52a19653 Mon Sep 17 00:00:00 2001 From: Denise Vangel-MSFT Date: Wed, 30 Sep 2020 14:23:43 -0700 Subject: [PATCH 31/76] Update manage-updates-baselines-microsoft-defender-antivirus.md --- .../manage-updates-baselines-microsoft-defender-antivirus.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md b/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md index 4f7c4b6487..af9bf51dfc 100644 --- a/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md +++ b/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md @@ -84,8 +84,8 @@ All our updates contain:  Support phase: **Security and Critical Updates** ### What's new -- Require administrative privileges for quarantine restore -- Support for XML formatted events +- Admin permissions are required to restore files in quarantine +- XML formatted events are now supported - Provide CSP support to ignore exclusion merge - New management interfaces for:
- UDP Inspection From 2ab48a7377511cdca60e7ee3b21a6aaad3800e30 Mon Sep 17 00:00:00 2001 From: Denise Vangel-MSFT Date: Wed, 30 Sep 2020 14:25:12 -0700 Subject: [PATCH 32/76] Update manage-updates-baselines-microsoft-defender-antivirus.md --- ...anage-updates-baselines-microsoft-defender-antivirus.md | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md b/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md index af9bf51dfc..bd78df412c 100644 --- a/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md +++ b/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md @@ -73,8 +73,7 @@ All our updates contain: - performance improvements - serviceability improvements - integration improvements (Cloud, MTP) -
-
+
September-2020 (Platform: 4.18.2008.9 | Engine: 1.1.17400.5)  Security intelligence update version: **1.323.2248.0** @@ -86,12 +85,12 @@ All our updates contain: ### What's new - Admin permissions are required to restore files in quarantine - XML formatted events are now supported -- Provide CSP support to ignore exclusion merge +- CSP support for ignoring exclusion merge - New management interfaces for:
- UDP Inspection - Network Protection on Server 2019 - IP Address exclusions for Network Protection -- Improve visibility into TPM logs +- Improved visibility into TPM logs - Improved Office VBA script scanning ### Known Issues From 6efb4093ac61e9ea185e561f0a5b669f294a4a9c Mon Sep 17 00:00:00 2001 From: Denise Vangel-MSFT Date: Wed, 30 Sep 2020 14:27:37 -0700 Subject: [PATCH 33/76] Update manage-updates-baselines-microsoft-defender-antivirus.md --- .../manage-updates-baselines-microsoft-defender-antivirus.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md b/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md index bd78df412c..ee0b0a0392 100644 --- a/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md +++ b/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md @@ -325,7 +325,7 @@ The below table provides the Microsoft Defender Antivirus platform and engine ve Windows 10 release info: [Windows lifecycle fact sheet](https://support.microsoft.com/help/13853/windows-lifecycle-fact-sheet). -## In this section +## See also Article | Description ---|--- From 48767c0dfbcbe0007a46fa0328b3cbb66fb1052d Mon Sep 17 00:00:00 2001 From: Denise Vangel-MSFT Date: Wed, 30 Sep 2020 14:29:42 -0700 Subject: [PATCH 34/76] Update manage-updates-baselines-microsoft-defender-antivirus.md --- .../manage-updates-baselines-microsoft-defender-antivirus.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md b/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md index ee0b0a0392..4b5b85ad5e 100644 --- a/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md +++ b/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md @@ -73,7 +73,8 @@ All our updates contain: - performance improvements - serviceability improvements - integration improvements (Cloud, MTP) -
+
+
September-2020 (Platform: 4.18.2008.9 | Engine: 1.1.17400.5)  Security intelligence update version: **1.323.2248.0** @@ -97,7 +98,7 @@ All our updates contain: No known issues
-
+
August-2020 (Platform: 4.18.2008.9 | Engine: 1.1.17400.5) From a7829eab53c69983d7858208144a25df110aa651 Mon Sep 17 00:00:00 2001 From: Denise Vangel-MSFT Date: Wed, 30 Sep 2020 14:31:56 -0700 Subject: [PATCH 35/76] Update manage-updates-baselines-microsoft-defender-antivirus.md --- .../manage-updates-baselines-microsoft-defender-antivirus.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md b/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md index 4b5b85ad5e..d58c458af0 100644 --- a/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md +++ b/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md @@ -77,7 +77,7 @@ All our updates contain:
September-2020 (Platform: 4.18.2008.9 | Engine: 1.1.17400.5) - Security intelligence update version: **1.323.2248.0** + Security intelligence update version: **1.323.2254.0**  Released: **September 30, 2020**  Platform: **4.18.2008.9**  Engine: **1.1.17400.5** From a7165397977f54582e9e999236809a1b992da21a Mon Sep 17 00:00:00 2001 From: Denise Vangel-MSFT Date: Wed, 30 Sep 2020 14:36:16 -0700 Subject: [PATCH 36/76] Update manage-updates-baselines-microsoft-defender-antivirus.md --- ...updates-baselines-microsoft-defender-antivirus.md | 12 +++--------- 1 file changed, 3 insertions(+), 9 deletions(-) diff --git a/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md b/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md index d58c458af0..532efafb74 100644 --- a/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md +++ b/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md @@ -84,21 +84,15 @@ All our updates contain:  Support phase: **Security and Critical Updates** ### What's new -- Admin permissions are required to restore files in quarantine -- XML formatted events are now supported -- CSP support for ignoring exclusion merge -- New management interfaces for:
- - UDP Inspection - - Network Protection on Server 2019 - - IP Address exclusions for Network Protection -- Improved visibility into TPM logs -- Improved Office VBA script scanning +* Improved telemetry for BITS +* Improved Authenticode code signing certificate validation ### Known Issues No known issues
+
August-2020 (Platform: 4.18.2008.9 | Engine: 1.1.17400.5) From 2af14fefad3230d65e31e74d6dafc968d983d60b Mon Sep 17 00:00:00 2001 From: Denise Vangel-MSFT Date: Wed, 30 Sep 2020 14:39:34 -0700 Subject: [PATCH 37/76] Update manage-updates-baselines-microsoft-defender-antivirus.md --- ...-updates-baselines-microsoft-defender-antivirus.md | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git a/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md b/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md index 532efafb74..98d0b7997c 100644 --- a/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md +++ b/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md @@ -84,8 +84,15 @@ All our updates contain:  Support phase: **Security and Critical Updates** ### What's new -* Improved telemetry for BITS -* Improved Authenticode code signing certificate validation +- Admin permissions are required to restore files in quarantine +- XML formatted events are now supported +- CSP support for ignoring exclusion merge +- New management interfaces for:
+ - UDP Inspection + - Network Protection on Server 2019 + - IP Address exclusions for Network Protection +- Improved visibility into TPM logs +- Improved Office VBA script scanning ### Known Issues No known issues From d4b13d28e30a41158a378751cfb9d20bec2f05c4 Mon Sep 17 00:00:00 2001 From: Denise Vangel-MSFT Date: Wed, 30 Sep 2020 14:51:50 -0700 Subject: [PATCH 38/76] Update manage-updates-baselines-microsoft-defender-antivirus.md --- .../manage-updates-baselines-microsoft-defender-antivirus.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md b/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md index 98d0b7997c..5757a00f5f 100644 --- a/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md +++ b/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md @@ -75,11 +75,11 @@ All our updates contain: - integration improvements (Cloud, MTP)
- September-2020 (Platform: 4.18.2008.9 | Engine: 1.1.17400.5) + September-2020 (Platform: 4.18.2009.5 | Engine: 1.1.17400.5)  Security intelligence update version: **1.323.2254.0**  Released: **September 30, 2020** - Platform: **4.18.2008.9** + Platform: **4.18.2009.5**  Engine: **1.1.17400.5**  Support phase: **Security and Critical Updates** From 28b797679fc2c0cb4748b3da50a5e8ab2bb1ba44 Mon Sep 17 00:00:00 2001 From: Denise Vangel-MSFT Date: Wed, 30 Sep 2020 14:52:54 -0700 Subject: [PATCH 39/76] Update manage-updates-baselines-microsoft-defender-antivirus.md --- .../manage-updates-baselines-microsoft-defender-antivirus.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md b/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md index 5757a00f5f..6237e1b473 100644 --- a/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md +++ b/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md @@ -75,12 +75,12 @@ All our updates contain: - integration improvements (Cloud, MTP)
- September-2020 (Platform: 4.18.2009.5 | Engine: 1.1.17400.5) + September-2020 (Platform: 4.18.2009.5 | Engine: 1.1.17500.2)  Security intelligence update version: **1.323.2254.0**  Released: **September 30, 2020**  Platform: **4.18.2009.5** - Engine: **1.1.17400.5** + Engine: **1.1.17500.2**  Support phase: **Security and Critical Updates** ### What's new From 7f317ac2b550b65c4a1ff39f21883e05ffdeb636 Mon Sep 17 00:00:00 2001 From: ImranHabib <47118050+joinimran@users.noreply.github.com> Date: Thu, 1 Oct 2020 15:37:44 +0500 Subject: [PATCH 40/76] Update windows/security/information-protection/windows-information-protection/create-wip-policy-using-intune-azure.md Co-authored-by: JohanFreelancer9 <48568725+JohanFreelancer9@users.noreply.github.com> --- .../create-wip-policy-using-intune-azure.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/security/information-protection/windows-information-protection/create-wip-policy-using-intune-azure.md b/windows/security/information-protection/windows-information-protection/create-wip-policy-using-intune-azure.md index b3788ff49e..fa3972ea0e 100644 --- a/windows/security/information-protection/windows-information-protection/create-wip-policy-using-intune-azure.md +++ b/windows/security/information-protection/windows-information-protection/create-wip-policy-using-intune-azure.md @@ -622,7 +622,7 @@ You can restrict which files are protected by WIP when they are downloaded from - [What is Azure Rights Management?](https://docs.microsoft.com/information-protection/understand-explore/what-is-azure-rms) -- [Create and deploy Windows Information Protection (WIP) app protection policy with Intune and MAM](https://docs.microsoft.com/windows/security/information-protection/windows-information-protection/overview-create-wip-policy) +- [Create a Windows Information Protection (WIP) protection policy using Microsoft Intune](https://docs.microsoft.com/windows/security/information-protection/windows-information-protection/overview-create-wip-policy) - [Intune MAM Without Enrollment](https://blogs.technet.microsoft.com/configmgrdogs/2016/02/04/intune-mam-without-enrollment/) From c7650732e8652a74e98bc0656137e2156decafdc Mon Sep 17 00:00:00 2001 From: brbrahm <43386070+brbrahm@users.noreply.github.com> Date: Thu, 1 Oct 2020 10:30:10 -0700 Subject: [PATCH 41/76] Minor fixes to WDAC vs AppLocker Clarify wording in WDAC system requirements, remove 'legacy' reference, and add back AppLocker recommendation for not enforcing DLLs and drivers --- .../wdac-and-applocker-overview.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/windows/security/threat-protection/windows-defender-application-control/wdac-and-applocker-overview.md b/windows/security/threat-protection/windows-defender-application-control/wdac-and-applocker-overview.md index f076b612e7..9bde7a0cc3 100644 --- a/windows/security/threat-protection/windows-defender-application-control/wdac-and-applocker-overview.md +++ b/windows/security/threat-protection/windows-defender-application-control/wdac-and-applocker-overview.md @@ -44,7 +44,7 @@ Note that prior to Windows 10, version 1709, Windows Defender Application Contro ### WDAC System Requirements -WDAC policies can only be created on devices running Windows 10 build 1903+ on any SKU, pre-1903 Windows 10 Enterprise, or Windows Server 2016 and above. +WDAC policies can be created on any client edition of Windows 10 build 1903+ or on Windows Server 2016 and above. WDAC policies can be applied to devices running any edition of Windows 10 or Windows Server 2016 and above via a Mobile Device Management (MDM) solution like Intune, a management interface like Configuration Manager, or a script host like PowerShell. Group Policy can also be used to deploy WDAC policies to Windows 10 Enterprise edition or Windows Server 2016 and above, but cannot deploy policies to devices running non-Enterprise SKUs of Windows 10. @@ -65,12 +65,13 @@ AppLocker policies can be deployed using Group Policy or MDM. ## Choose when to use WDAC or AppLocker -Generally, it is recommended that customers who are able to implement application control using WDAC rather than AppLocker do so. WDAC is undergoing continual improvements and will be getting added support from Microsoft management platforms. AppLocker is a legacy technology which will continue to receive security fixes but will not undergo new feature improvements. +Generally, it is recommended that customers who are able to implement application control using WDAC rather than AppLocker do so. WDAC is undergoing continual improvements and will be getting added support from Microsoft management platforms. Although AppLocker will continue to receive security fixes, it will not undergo new feature improvements. In some cases, however, AppLocker may be the more appropriate technology for your organization. AppLocker is best when: - You have a mixed Windows operating system (OS) environment and need to apply the same policy controls to Windows 10 and earlier versions of the OS. - You need to apply different policies for different users or groups on shared computers. +- You do not want to enforce application control on application files such as DLLs or drivers. AppLocker can also be deployed as a complement to WDAC to add user- or group-specific rules for shared device scenarios where it is important to prevent some users from running specific apps. As a best practice, you should enforce WDAC at the most restrictive level possible for your organization, and then you can use AppLocker to further fine-tune the restrictions. From 97663ee37bbe6264fe7f79253e68ee5379ec00a6 Mon Sep 17 00:00:00 2001 From: brbrahm <43386070+brbrahm@users.noreply.github.com> Date: Thu, 1 Oct 2020 10:35:14 -0700 Subject: [PATCH 42/76] Add link to WDAC feature availability --- .../wdac-and-applocker-overview.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/windows/security/threat-protection/windows-defender-application-control/wdac-and-applocker-overview.md b/windows/security/threat-protection/windows-defender-application-control/wdac-and-applocker-overview.md index 9bde7a0cc3..9fe4c819a1 100644 --- a/windows/security/threat-protection/windows-defender-application-control/wdac-and-applocker-overview.md +++ b/windows/security/threat-protection/windows-defender-application-control/wdac-and-applocker-overview.md @@ -48,6 +48,8 @@ WDAC policies can be created on any client edition of Windows 10 build 1903+ or WDAC policies can be applied to devices running any edition of Windows 10 or Windows Server 2016 and above via a Mobile Device Management (MDM) solution like Intune, a management interface like Configuration Manager, or a script host like PowerShell. Group Policy can also be used to deploy WDAC policies to Windows 10 Enterprise edition or Windows Server 2016 and above, but cannot deploy policies to devices running non-Enterprise SKUs of Windows 10. +For more information on which individual WDAC features are available on which WDAC builds, see [WDAC feature availability](feature-availability.md). + ## AppLocker AppLocker was introduced with Windows 7 and allows organizations to control which applications are allowed to run on their Windows clients. AppLocker helps to prevent end users from running unapproved software on their computers, but it does not meet the servicing criteria for being a security feature. From 62d7263951667a33e02bb79dd4b5eb19e44f7b62 Mon Sep 17 00:00:00 2001 From: Denise Vangel-MSFT Date: Thu, 1 Oct 2020 13:54:44 -0700 Subject: [PATCH 43/76] Update manage-updates-baselines-microsoft-defender-antivirus.md --- ...e-updates-baselines-microsoft-defender-antivirus.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md b/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md index 6237e1b473..7f303320f6 100644 --- a/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md +++ b/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md @@ -75,12 +75,12 @@ All our updates contain: - integration improvements (Cloud, MTP)
- September-2020 (Platform: 4.18.2009.5 | Engine: 1.1.17500.2) + September-2020 (Platform: 4.18.2009.7 | Engine: 1.1.17500.4)  Security intelligence update version: **1.323.2254.0** - Released: **September 30, 2020** - Platform: **4.18.2009.5** - Engine: **1.1.17500.2** + Released: **October 6, 2020** + Platform: **4.18.2009.7** + Engine: **1.1.17500.4**  Support phase: **Security and Critical Updates** ### What's new @@ -92,7 +92,7 @@ All our updates contain: - Network Protection on Server 2019 - IP Address exclusions for Network Protection - Improved visibility into TPM logs -- Improved Office VBA script scanning +- Improved Office VBA module scanning ### Known Issues No known issues From a726b924a7c034e4899fc1f40ec970d8ab6a6c0d Mon Sep 17 00:00:00 2001 From: Denise Vangel-MSFT Date: Thu, 1 Oct 2020 13:57:59 -0700 Subject: [PATCH 44/76] Update manage-updates-baselines-microsoft-defender-antivirus.md --- .../manage-updates-baselines-microsoft-defender-antivirus.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md b/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md index 7f303320f6..cdf9ef435b 100644 --- a/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md +++ b/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md @@ -91,7 +91,7 @@ All our updates contain: - UDP Inspection - Network Protection on Server 2019 - IP Address exclusions for Network Protection -- Improved visibility into TPM logs +- Improved visibility into TPM measurements - Improved Office VBA module scanning ### Known Issues From 057b8059a6447fca3a24e6b1bab98bb529faf723 Mon Sep 17 00:00:00 2001 From: Denise Vangel-MSFT Date: Thu, 1 Oct 2020 13:59:37 -0700 Subject: [PATCH 45/76] Update manage-updates-baselines-microsoft-defender-antivirus.md --- .../manage-updates-baselines-microsoft-defender-antivirus.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md b/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md index cdf9ef435b..fca05b951d 100644 --- a/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md +++ b/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md @@ -72,7 +72,7 @@ For information how to update or how to install the platform update, see [Update All our updates contain: - performance improvements - serviceability improvements -- integration improvements (Cloud, MTP) +- integration improvements (Cloud, Microsoft 365 Defender)
September-2020 (Platform: 4.18.2009.7 | Engine: 1.1.17500.4) From 86bf65dbd58b6b5ab3c30550f55b0d0f9e9122f9 Mon Sep 17 00:00:00 2001 From: Kurt Sarens <56369685+kurtsarens@users.noreply.github.com> Date: Fri, 2 Oct 2020 19:40:58 +0200 Subject: [PATCH 46/76] Update prevent-end-user-interaction-microsoft-defender-antivirus.md Pausing a scan is not supported on Win10 --- ...revent-end-user-interaction-microsoft-defender-antivirus.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/windows/security/threat-protection/microsoft-defender-antivirus/prevent-end-user-interaction-microsoft-defender-antivirus.md b/windows/security/threat-protection/microsoft-defender-antivirus/prevent-end-user-interaction-microsoft-defender-antivirus.md index c3358561d8..be8c6c387a 100644 --- a/windows/security/threat-protection/microsoft-defender-antivirus/prevent-end-user-interaction-microsoft-defender-antivirus.md +++ b/windows/security/threat-protection/microsoft-defender-antivirus/prevent-end-user-interaction-microsoft-defender-antivirus.md @@ -64,6 +64,9 @@ See [Prevent users from locally modifying policy settings](configure-local-polic You can prevent users from pausing scans, which can be helpful to ensure scheduled or on-demand scans are not interrupted by users. +>[!NOTE] +>This setting is not supported on Windows 10 + ### Use Group Policy to prevent users from pausing a scan 1. On your Group Policy management machine, open the [Group Policy Management Console](https://docs.microsoft.com/previous-versions/windows/desktop/gpmc/group-policy-management-console-portal), right-click the Group Policy Object you want to configure and click **Edit**. From 1d1fbea6053d675f0a49e8388b1b2c03e0fc9b0a Mon Sep 17 00:00:00 2001 From: Denise Vangel-MSFT Date: Mon, 5 Oct 2020 10:28:21 -0700 Subject: [PATCH 47/76] Update windows/security/threat-protection/microsoft-defender-antivirus/prevent-end-user-interaction-microsoft-defender-antivirus.md Co-authored-by: JohanFreelancer9 <48568725+JohanFreelancer9@users.noreply.github.com> --- ...prevent-end-user-interaction-microsoft-defender-antivirus.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/security/threat-protection/microsoft-defender-antivirus/prevent-end-user-interaction-microsoft-defender-antivirus.md b/windows/security/threat-protection/microsoft-defender-antivirus/prevent-end-user-interaction-microsoft-defender-antivirus.md index be8c6c387a..9b9884c662 100644 --- a/windows/security/threat-protection/microsoft-defender-antivirus/prevent-end-user-interaction-microsoft-defender-antivirus.md +++ b/windows/security/threat-protection/microsoft-defender-antivirus/prevent-end-user-interaction-microsoft-defender-antivirus.md @@ -64,7 +64,7 @@ See [Prevent users from locally modifying policy settings](configure-local-polic You can prevent users from pausing scans, which can be helpful to ensure scheduled or on-demand scans are not interrupted by users. ->[!NOTE] +> [!NOTE] >This setting is not supported on Windows 10 ### Use Group Policy to prevent users from pausing a scan From 33c64ccd2690153d49b2d2f51b0d835688c15537 Mon Sep 17 00:00:00 2001 From: Denise Vangel-MSFT Date: Mon, 5 Oct 2020 10:28:27 -0700 Subject: [PATCH 48/76] Update windows/security/threat-protection/microsoft-defender-antivirus/prevent-end-user-interaction-microsoft-defender-antivirus.md Co-authored-by: JohanFreelancer9 <48568725+JohanFreelancer9@users.noreply.github.com> --- ...prevent-end-user-interaction-microsoft-defender-antivirus.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/security/threat-protection/microsoft-defender-antivirus/prevent-end-user-interaction-microsoft-defender-antivirus.md b/windows/security/threat-protection/microsoft-defender-antivirus/prevent-end-user-interaction-microsoft-defender-antivirus.md index 9b9884c662..7bf4c22d0e 100644 --- a/windows/security/threat-protection/microsoft-defender-antivirus/prevent-end-user-interaction-microsoft-defender-antivirus.md +++ b/windows/security/threat-protection/microsoft-defender-antivirus/prevent-end-user-interaction-microsoft-defender-antivirus.md @@ -65,7 +65,7 @@ See [Prevent users from locally modifying policy settings](configure-local-polic You can prevent users from pausing scans, which can be helpful to ensure scheduled or on-demand scans are not interrupted by users. > [!NOTE] ->This setting is not supported on Windows 10 +> This setting is not supported on Windows 10. ### Use Group Policy to prevent users from pausing a scan From 2318fedf5f9fbf986ca469b2a687e4e9d04b2d4b Mon Sep 17 00:00:00 2001 From: jaimeo Date: Mon, 5 Oct 2020 15:25:09 -0700 Subject: [PATCH 49/76] adding tags --- windows/deployment/update/waas-configure-wufb.md | 2 +- windows/deployment/update/waas-delivery-optimization.md | 1 + windows/deployment/update/waas-integrate-wufb.md | 3 +-- .../update/waas-servicing-strategy-windows-10-updates.md | 1 + windows/deployment/update/waas-wufb-group-policy.md | 2 +- 5 files changed, 5 insertions(+), 4 deletions(-) diff --git a/windows/deployment/update/waas-configure-wufb.md b/windows/deployment/update/waas-configure-wufb.md index d25d48f473..4b1673fbe0 100644 --- a/windows/deployment/update/waas-configure-wufb.md +++ b/windows/deployment/update/waas-configure-wufb.md @@ -5,7 +5,7 @@ manager: laurawi description: You can use Group Policy or your mobile device management (MDM) service to configure Windows Update for Business settings for your devices. ms.prod: w10 ms.mktglfcycl: deploy - +ms.collection: M365initiative-coredeploy audience: itpro author: jaimeo ms.localizationpriority: medium diff --git a/windows/deployment/update/waas-delivery-optimization.md b/windows/deployment/update/waas-delivery-optimization.md index 1def8466e7..9e93b51219 100644 --- a/windows/deployment/update/waas-delivery-optimization.md +++ b/windows/deployment/update/waas-delivery-optimization.md @@ -11,6 +11,7 @@ author: jaimeo ms.localizationpriority: medium ms.author: jaimeo ms.collection: M365-modern-desktop +- M365initiative-coredeploy ms.topic: article --- diff --git a/windows/deployment/update/waas-integrate-wufb.md b/windows/deployment/update/waas-integrate-wufb.md index 9d8afa433e..ac66d0b697 100644 --- a/windows/deployment/update/waas-integrate-wufb.md +++ b/windows/deployment/update/waas-integrate-wufb.md @@ -6,8 +6,7 @@ ms.mktglfcycl: manage author: jaimeo ms.localizationpriority: medium ms.author: jaimeo -ms.date: 07/27/2017 -ms.reviewer: +ms.collection: M365initiative-coredeploy manager: laurawi ms.topic: article --- diff --git a/windows/deployment/update/waas-servicing-strategy-windows-10-updates.md b/windows/deployment/update/waas-servicing-strategy-windows-10-updates.md index ae0773920a..a4e91744b3 100644 --- a/windows/deployment/update/waas-servicing-strategy-windows-10-updates.md +++ b/windows/deployment/update/waas-servicing-strategy-windows-10-updates.md @@ -9,6 +9,7 @@ ms.author: jaimeo ms.reviewer: manager: laurawi ms.topic: article +ms.collection: M365initiative-coredeploy --- # Prepare servicing strategy for Windows 10 updates diff --git a/windows/deployment/update/waas-wufb-group-policy.md b/windows/deployment/update/waas-wufb-group-policy.md index fc80d55002..bd7614abe8 100644 --- a/windows/deployment/update/waas-wufb-group-policy.md +++ b/windows/deployment/update/waas-wufb-group-policy.md @@ -6,7 +6,7 @@ ms.mktglfcycl: manage author: jaimeo ms.localizationpriority: medium ms.author: jaimeo -ms.reviewer: +ms.collection: M365initiative-coredeploy manager: laurawi ms.topic: article --- From de9237a2b2ea804abdb251a06675d8c3fe244caf Mon Sep 17 00:00:00 2001 From: jaimeo Date: Mon, 5 Oct 2020 15:31:54 -0700 Subject: [PATCH 50/76] trying to fix tag --- windows/deployment/update/waas-delivery-optimization.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/windows/deployment/update/waas-delivery-optimization.md b/windows/deployment/update/waas-delivery-optimization.md index 9e93b51219..29f4745c6b 100644 --- a/windows/deployment/update/waas-delivery-optimization.md +++ b/windows/deployment/update/waas-delivery-optimization.md @@ -1,6 +1,5 @@ --- title: Delivery Optimization for Windows 10 updates -ms.reviewer: manager: laurawi description: Delivery Optimization is a peer-to-peer distribution method in Windows 10 keywords: oms, operations management suite, wdav, updates, downloads, log analytics @@ -10,7 +9,8 @@ audience: itpro author: jaimeo ms.localizationpriority: medium ms.author: jaimeo -ms.collection: M365-modern-desktop +ms.collection: +- M365-modern-desktop - M365initiative-coredeploy ms.topic: article --- From 43272feaad78f60b40e20be8922dc19408ff1a07 Mon Sep 17 00:00:00 2001 From: jaimeo Date: Mon, 5 Oct 2020 15:50:57 -0700 Subject: [PATCH 51/76] fixing various typos --- windows/deployment/update/waas-configure-wufb.md | 4 ++-- windows/deployment/update/waas-integrate-wufb.md | 2 +- .../update/waas-servicing-strategy-windows-10-updates.md | 6 +++--- windows/deployment/update/waas-wufb-group-policy.md | 2 +- 4 files changed, 7 insertions(+), 7 deletions(-) diff --git a/windows/deployment/update/waas-configure-wufb.md b/windows/deployment/update/waas-configure-wufb.md index 4b1673fbe0..7aebbab370 100644 --- a/windows/deployment/update/waas-configure-wufb.md +++ b/windows/deployment/update/waas-configure-wufb.md @@ -220,7 +220,7 @@ The following are quick-reference tables of the supported policy values for Wind | GPO Key | Key type | Value | | --- | --- | --- | -| BranchReadinessLevel | REG_DWORD | 2: systems take Feature Updates for the Windows Insider build - Fast (added in Windows 10, version 1709)
4: systems take Feature Updates for the Windows Insider build - Slow (added in Windows 10, version 1709)
8: systems take Feature Updates for the Release Windows Insider build (added in Windows 10, version 1709)
16: for Windows 10, version 1703: systems take Feature Updates for the Current Branch (CB); for Windows 10, version 1709, 1803 and 1809: systems take Feature Updates from Semi-annual Channel (Targeted) (SAC-T); for Windows 10, version 1903 or later: systems take Feature Updates from Semi-annual Channel
32: systems take Feature Updates from Semi-annual Channel
Note: Other value or absent: receive all applicable updates | +| BranchReadinessLevel | REG_DWORD | 2: systems take Feature Updates for the Windows Insider build - Fast (added in Windows 10, version 1709)
4: systems take Feature Updates for the Windows Insider build - Slow (added in Windows 10, version 1709)
8: systems take Feature Updates for the Release Windows Insider build (added in Windows 10, version 1709)
16: for Windows 10, version 1703: systems take Feature Updates for the Current Branch (CB); for Windows 10, version 1709, 1803 and 1809: systems take Feature Updates from Semi-Annual Channel (Targeted) (SAC-T); for Windows 10, version 1903 or later: systems take Feature Updates from Semi-Annual Channel
32: systems take Feature Updates from Semi-Annual Channel
Note: Other value or absent: receive all applicable updates | | DeferQualityUpdates | REG_DWORD | 1: defer quality updates
Other value or absent: don’t defer quality updates | | DeferQualityUpdatesPeriodinDays | REG_DWORD | 0-35: defer quality updates by given days | | PauseQualityUpdatesStartTime | REG_DWORD | 1: pause quality updates
Other value or absent: don’t pause quality updates | @@ -234,7 +234,7 @@ The following are quick-reference tables of the supported policy values for Wind | MDM Key | Key type | Value | | --- | --- | --- | -| BranchReadinessLevel | REG_DWORD |2: systems take Feature Updates for the Windows Insider build - Fast (added in Windows 10, version 1709)
4: systems take Feature Updates for the Windows Insider build - Slow (added in Windows 10, version 1709)
8: systems take Feature Updates for the Release Windows Insider build (added in Windows 10, version 1709)
16: for Windows 10, version 1703: systems take Feature Updates for the Current Branch (CB); for Windows 10, version 1709, 1803 and 1809: systems take Feature Updates from Semi-annual Channel (Targeted) (SAC-T); for Windows 10, version 1903 or later: systems take Feature Updates from Semi-annual Channel
32: systems take Feature Updates from Semi-annual Channel
Note: Other value or absent: receive all applicable updates | +| BranchReadinessLevel | REG_DWORD |2: systems take Feature Updates for the Windows Insider build - Fast (added in Windows 10, version 1709)
4: systems take Feature Updates for the Windows Insider build - Slow (added in Windows 10, version 1709)
8: systems take Feature Updates for the Release Windows Insider build (added in Windows 10, version 1709)
16: for Windows 10, version 1703: systems take Feature Updates for the Current Branch (CB); for Windows 10, version 1709, 1803 and 1809: systems take Feature Updates from Semi-Annual Channel (Targeted) (SAC-T); for Windows 10, version 1903 or later: systems take Feature Updates from Semi-Annual Channel
32: systems take Feature Updates from Semi-Annual Channel
Note: Other value or absent: receive all applicable updates | | DeferQualityUpdatesPeriodinDays | REG_DWORD | 0-35: defer quality updates by given days | | PauseQualityUpdatesStartTime | REG_DWORD | 1: pause quality updates
Other value or absent: don’t pause quality updates | | DeferFeatureUpdatesPeriodinDays | REG_DWORD | 0-365: defer feature updates by given days | diff --git a/windows/deployment/update/waas-integrate-wufb.md b/windows/deployment/update/waas-integrate-wufb.md index ac66d0b697..2dc3cc3ff3 100644 --- a/windows/deployment/update/waas-integrate-wufb.md +++ b/windows/deployment/update/waas-integrate-wufb.md @@ -68,7 +68,7 @@ For Windows 10, version 1607, devices can now be configured to receive updates f - Device is configured to defer Quality Updates using Windows Update for Business and to be managed by WSUS - Device is configured to “receive updates for other Microsoft products” along with updates to Windows (**Update/AllowMUUpdateService** = enabled) -- Admin has also placed Microsoft Update, third-paprty, and locally-published update content on the WSUS server +- Admin has also placed Microsoft Update, non-Microsoft, and locally published update content on the WSUS server In this example, the deferral behavior for updates to Office and other non-Windows products is slightly different than if WSUS were not enabled. - In a non-WSUS case, these updates would be deferred just as any update to Windows would be. diff --git a/windows/deployment/update/waas-servicing-strategy-windows-10-updates.md b/windows/deployment/update/waas-servicing-strategy-windows-10-updates.md index a4e91744b3..1ee1fa50de 100644 --- a/windows/deployment/update/waas-servicing-strategy-windows-10-updates.md +++ b/windows/deployment/update/waas-servicing-strategy-windows-10-updates.md @@ -30,9 +30,9 @@ In the past, traditional Windows deployments tended to be large, lengthy, and ex Windows 10 spreads the traditional deployment effort of a Windows upgrade, which typically occurred every few years, over smaller, continuous updates. With this change, you must approach the ongoing deployment and servicing of Windows differently. A strong Windows 10 deployment strategy begins with establishing a simple, repeatable process for testing and deploying each feature update. Here’s an example of what this process might look like: - **Configure test devices.** Configure test devices in the Windows Insider Program so that Insiders can test feature updates before they’re available to the Semi-Annual Channel. Typically, this would be a small number of test devices that IT staff members use to evaluate pre-release builds of Windows. Microsoft provides current development builds to Windows Insider members approximately every week so that interested users can see the functionality Microsoft is adding. See the section Windows Insider for details on how to enroll in the Windows Insider Program on a Windows 10 device. -- **Identify excluded devices.** For some organizations, special-purpose devices such as those used to control factory or medical equipment or run ATMs require a stricter, less frequent feature update cycle than the Semi-annual Channel can offer. For those machines, you must install Windows 10 Enterprise LTSB to avoid feature updates for up to 10 years. Identify these devices, and separate them from the phased deployment and servicing cycles to help remove confusion for your administrators and ensure that devices are handled correctly. +- **Identify excluded devices.** For some organizations, special-purpose devices such as those used to control factory or medical equipment or run ATMs require a stricter, less frequent feature update cycle than the Semi-Annual Channel can offer. For those machines, you must install Windows 10 Enterprise LTSB to avoid feature updates for up to 10 years. Identify these devices, and separate them from the phased deployment and servicing cycles to help remove confusion for your administrators and ensure that devices are handled correctly. - **Recruit volunteers.** The purpose of testing a deployment is to receive feedback. One effective way to recruit pilot users is to request volunteers. When doing so, clearly state that you’re looking for feedback rather than people to just “try it out” and that there could be occasional issues involved with accepting feature updates right away. With Windows as a service, the expectation is that there should be few issues, but if an issue does arise, you want testers to let you know as soon as possible. When considering whom to recruit for pilot groups, be sure to include members who provide the broadest set of applications and devices to validate the largest number of apps and devices possible. -- **Update Group Policy.** Each feature update includes new group policies to manage new features. If you use Group Policy to manage devices, the Group Policy Admin for the Active Directory domain will need to download a .admx package and copy it to their [Central Store](https://support.microsoft.com/help/929841/how-to-create-the-central-store-for-group-policy-administrative-templa) (or to the [PolicyDefinitions](https://msdn.microsoft.com/library/bb530196.aspx) directory in the SYSVOL of a domain controller if not using a Central Store). Always manage new group polices from the version of Windows 10 they shipped with by using the Remote Server Administration Tools. The ADMX download package is created at the end of each development cycle and then posted for download. To find the ADMX download package for a given Windows build, search for “ADMX download for Windows build xxxx”. For details about Group Policy management, see [How to create and manage the Central Store for Group Policy Administrative Templates in Windows](https://support.microsoft.com/help/3087759/how-to-create-and-manage-the-central-store-for-group-policy-administra) +- **Update Group Policy.** Each feature update includes new group policies to manage new features. If you use Group Policy to manage devices, the Group Policy Admin for the Active Directory domain will need to download a .admx package and copy it to their [Central Store](https://support.microsoft.com/help/929841/how-to-create-the-central-store-for-group-policy-administrative-templa) (or to the [PolicyDefinitions](https://msdn.microsoft.com/library/bb530196.aspx) directory in the SYSVOL folder of a domain controller if not using a Central Store). Always manage new group polices from the version of Windows 10 they shipped with by using the Remote Server Administration Tools. The ADMX download package is created at the end of each development cycle and then posted for download. To find the ADMX download package for a given Windows build, search for “ADMX download for Windows build xxxx”. For details about Group Policy management, see [How to create and manage the Central Store for Group Policy Administrative Templates in Windows](https://support.microsoft.com/help/3087759/how-to-create-and-manage-the-central-store-for-group-policy-administra) - **Choose a servicing tool.** Decide which product you’ll use to manage the Windows updates in your environment. If you’re currently using Windows Server Update Services (WSUS) or Microsoft Endpoint Configuration Manager to manage your Windows updates, you can continue using those products to manage Windows 10 updates. Alternatively, you can use Windows Update for Business. In addition to which product you’ll use, consider how you’ll deliver the updates. With Windows 10, multiple peer-to-peer options are available to make update distribution faster. For a comparison of tools, see [Servicing tools](waas-overview.md#servicing-tools). - **Prioritize applications.** First, create an application portfolio. This list should include everything installed in your organization and any webpages your organization hosts. Next, prioritize this list to identify those that are the most business critical. Because the expectation is that application compatibility with Windows 10 will be high, only the most business critical applications should be tested before the pilot phase; everything else can be tested afterwards. For more information about identifying compatibility issues withe applications, see [Manage Windows upgrades with Upgrade Analytics](../upgrade/manage-windows-upgrades-with-upgrade-readiness.md). @@ -44,7 +44,7 @@ Windows 10 spreads the traditional deployment effort of a Windows upgrade, which Each time Microsoft releases a Windows 10 feature update, the IT department should use the following high-level process to help ensure that the broad deployment is successful: 1. **Validate compatibility of business critical apps.** Test your most important business-critical applications for compatibility with the new Windows 10 feature update running on your Windows Insider machines identified in the earlier “Configure test machines” step of the Predeployment strategy section. The list of applications involved in this validation process should be small because most applications can be tested during the pilot phase. For more information about device and application compatibility in Windows 10, see the section Compatibility. -2. **Target and react to feedback.** With Windows 10, Microsoft expects application and device compatibility to be high, but it’s still important to have targeted groups within both the IT department and business units to verify application compatibility for the remaining applications in your application portfolio. Because only the most business-critical applications are tested beforehand, this will represent the majority of application compatibility testing in your environment. This should not necessarily be a formal process but rather user validation through the use of a particular application. So, the next step is to deploy the feature update to early-adopting IT users and your targeted groups running in the Semi-annual channel that you identified in the “Recruit volunteers” step of the Predeployment strategy section. Be sure to communicate clearly that you’re looking for feedback as soon as possible, and state exactly how users can submit feedback to you. Should an issue arise, have a remediation plan in place to address it. +2. **Target and react to feedback.** With Windows 10, Microsoft expects application and device compatibility to be high, but it’s still important to have targeted groups within both the IT department and business units to verify application compatibility for the remaining applications in your application portfolio. Because only the most business-critical applications are tested beforehand, this will represent the majority of application compatibility testing in your environment. This should not necessarily be a formal process but rather user validation through the use of a particular application. So, the next step is to deploy the feature update to early-adopting IT users and your targeted groups running in the Semi-Annual channel that you identified in the “Recruit volunteers” step of the Predeployment strategy section. Be sure to communicate clearly that you’re looking for feedback as soon as possible, and state exactly how users can submit feedback to you. Should an issue arise, have a remediation plan in place to address it. 3. **Deploy broadly.** Finally, focus on the large-scale deployment using deployment rings, like the ones discussed in Table 1. Build deployment rings that target groups of computers in your selected update-management product. To reduce risk as much as possible, construct your deployment rings in a way that splits individual departments into multiple rings. This way, if you were to encounter an issue, you don’t prevent any critical business from continuing. By using this method, each deployment ring reduces risk as more and more people have been updated in any particular department. diff --git a/windows/deployment/update/waas-wufb-group-policy.md b/windows/deployment/update/waas-wufb-group-policy.md index bd7614abe8..9c1f05c751 100644 --- a/windows/deployment/update/waas-wufb-group-policy.md +++ b/windows/deployment/update/waas-wufb-group-policy.md @@ -138,7 +138,7 @@ When you set these policies, installation happens automatically at the specified We recommend that you use **Computer Configuration > Administrative Templates > Windows Components > Windows Update > Specify deadline for automatic updates and restarts** for feature and quality updates to ensure that devices stay secure on Windows 10, version 1709 and later. This works by enabling you to specify the number of days that can elapse after an update is offered to a device before it must be installed. Also you can set the number of days that can elapse after a pending restart before the user is forced to restart. -This policies also offers an option to opt out of automatic restarts until a deadline is reached by presenting an "engaged restart experience" until the deadline has actually expired. At that point the device will automatically schedule a restart regardles of active hours. +This policies also offers an option to opt out of automatic restarts until a deadline is reached by presenting an "engaged restart experience" until the deadline has actually expired. At that point the device will automatically schedule a restart regardless of active hours. These notifications are what the user sees depending on the settings you choose: From 1f41c566d32aa759f180702247ebe8fdcf049b5a Mon Sep 17 00:00:00 2001 From: jaimeo Date: Mon, 5 Oct 2020 15:51:46 -0700 Subject: [PATCH 52/76] another typo --- windows/deployment/update/waas-wufb-group-policy.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/update/waas-wufb-group-policy.md b/windows/deployment/update/waas-wufb-group-policy.md index 9c1f05c751..6f780e8656 100644 --- a/windows/deployment/update/waas-wufb-group-policy.md +++ b/windows/deployment/update/waas-wufb-group-policy.md @@ -59,7 +59,7 @@ Both Windows 10 feature and quality updates are automatically offered to devices To enable Microsoft Updates use the Group Policy Management Console go to **Computer Configuration > Administrative Templates > Windows Components > Windows Update > Configure Automatic Updates** and select **Install updates for other Microsoft products**. -Drivers are automatically enabled because they are beneficial to device systems. We recommend that you allow the driver policy to allow drivers to updated on devices (the default), but you can turn this setting off if you prefer to manage drivers manually. If you want to disable driver updates for some reason, use the Group Policy Management Console to go to **Computer Configuration > Administrative Templates > Windows Components > Windows Update > Do not include drivers with Windows Updates** and enable the policy. +Drivers are automatically enabled because they are beneficial to device systems. We recommend that you allow the driver policy to allow drivers to update on devices (the default), but you can turn this setting off if you prefer to manage drivers manually. If you want to disable driver updates for some reason, use the Group Policy Management Console to go to **Computer Configuration > Administrative Templates > Windows Components > Windows Update > Do not include drivers with Windows Updates** and enable the policy. We also recommend that you allow Microsoft product updates as discussed previously. From 9968fa8d67333a1714b628f116289ebb4eb60ed9 Mon Sep 17 00:00:00 2001 From: ManikaDhiman Date: Mon, 5 Oct 2020 15:56:36 -0700 Subject: [PATCH 53/76] Updated GP names for the newly added policies --- .../mdm/policy-csp-admx-ciphersuiteorder.md | 4 +- .../mdm/policy-csp-admx-com.md | 4 +- .../mdm/policy-csp-admx-digitallocker.md | 4 +- .../mdm/policy-csp-admx-dwm.md | 12 +- .../mdm/policy-csp-admx-eventforwarding.md | 2 +- .../policy-csp-admx-fileservervssprovider.md | 2 +- .../mdm/policy-csp-admx-filesys.md | 12 +- .../mdm/policy-csp-admx-folderredirection.md | 8 +- .../mdm/policy-csp-admx-help.md | 6 +- .../mdm/policy-csp-admx-helpandsupport.md | 8 +- .../mdm/policy-csp-admx-kdc.md | 8 +- .../mdm/policy-csp-admx-lanmanserver.md | 8 +- ...icy-csp-admx-linklayertopologydiscovery.md | 4 +- .../mdm/policy-csp-admx-mmc.md | 10 +- .../mdm/policy-csp-admx-mmcsnapins.md | 210 +++++++++--------- .../mdm/policy-csp-admx-msapolicy.md | 2 +- .../mdm/policy-csp-admx-nca.md | 8 +- .../mdm/policy-csp-admx-ncsi.md | 14 +- .../mdm/policy-csp-admx-netlogon.md | 70 +++--- .../mdm/policy-csp-admx-offlinefiles.md | 94 ++++---- .../mdm/policy-csp-admx-peertopeercaching.md | 18 +- .../policy-csp-admx-performancediagnostics.md | 8 +- .../mdm/policy-csp-admx-reliability.md | 8 +- .../mdm/policy-csp-admx-scripts.md | 24 +- .../mdm/policy-csp-admx-sdiageng.md | 6 +- .../mdm/policy-csp-admx-securitycenter.md | 2 +- .../mdm/policy-csp-admx-servicing.md | 2 +- ...csp-admx-shellcommandpromptregedittools.md | 6 +- 28 files changed, 282 insertions(+), 282 deletions(-) diff --git a/windows/client-management/mdm/policy-csp-admx-ciphersuiteorder.md b/windows/client-management/mdm/policy-csp-admx-ciphersuiteorder.md index 627b8ea61c..649079a937 100644 --- a/windows/client-management/mdm/policy-csp-admx-ciphersuiteorder.md +++ b/windows/client-management/mdm/policy-csp-admx-ciphersuiteorder.md @@ -97,7 +97,7 @@ For information about supported cipher suites, see [Cipher Suites in TLS/SSL (Sc ADMX Info: - GP English name: *SSL Cipher Suite Order* -- GP name: *Functions* +- GP name: *SSLCipherSuiteOrder* - GP path: *Network/SSL Configuration Settings* - GP ADMX file name: *CipherSuiteOrder.admx* @@ -180,7 +180,7 @@ CertUtil.exe -DisplayEccCurve ADMX Info: - GP English name: *ECC Curve Order* -- GP name: *EccCurves* +- GP name: *SSLCurveOrder* - GP path: *Network/SSL Configuration Settings* - GP ADMX file name: *CipherSuiteOrder.admx* diff --git a/windows/client-management/mdm/policy-csp-admx-com.md b/windows/client-management/mdm/policy-csp-admx-com.md index d7be4635d6..1da39a32a3 100644 --- a/windows/client-management/mdm/policy-csp-admx-com.md +++ b/windows/client-management/mdm/policy-csp-admx-com.md @@ -99,7 +99,7 @@ This setting appears in the Computer Configuration and User Configuration folder ADMX Info: - GP English name: *Download missing COM components* -- GP name: *COMClassStore* +- GP name: *AppMgmt_COM_SearchForCLSID_1* - GP path: *System* - GP ADMX file name: *COM.admx* @@ -174,7 +174,7 @@ This setting appears in the Computer Configuration and User Configuration folder ADMX Info: - GP English name: *Download missing COM components* -- GP name: *COMClassStore* +- GP name: *AppMgmt_COM_SearchForCLSID_2* - GP path: *System* - GP ADMX file name: *COM.admx* diff --git a/windows/client-management/mdm/policy-csp-admx-digitallocker.md b/windows/client-management/mdm/policy-csp-admx-digitallocker.md index 2d12ffdcdd..43d6152747 100644 --- a/windows/client-management/mdm/policy-csp-admx-digitallocker.md +++ b/windows/client-management/mdm/policy-csp-admx-digitallocker.md @@ -96,7 +96,7 @@ If you disable or do not configure this setting, Digital Locker can be run. ADMX Info: - GP English name: *Do not allow Digital Locker to run* -- GP name: *DoNotRunDigitalLocker* +- GP name: *Digitalx_DiableApplication_TitleText_1* - GP path: *Windows Components/Digital Locker* - GP ADMX file name: *DigitalLocker.admx* @@ -167,7 +167,7 @@ If you disable or do not configure this setting, Digital Locker can be run. ADMX Info: - GP English name: *Do not allow Digital Locker to run* -- GP name: *DoNotRunDigitalLocker* +- GP name: *Digitalx_DiableApplication_TitleText_2* - GP path: *Windows Components/Digital Locker* - GP ADMX file name: *DigitalLocker.admx* diff --git a/windows/client-management/mdm/policy-csp-admx-dwm.md b/windows/client-management/mdm/policy-csp-admx-dwm.md index 037491c5a5..ff5b9de5cc 100644 --- a/windows/client-management/mdm/policy-csp-admx-dwm.md +++ b/windows/client-management/mdm/policy-csp-admx-dwm.md @@ -109,7 +109,7 @@ If you disable or do not configure this policy setting, the default internal col ADMX Info: - GP English name: *Specify a default color* -- GP name: *DefaultColorizationColorState* +- GP name: *DwmDefaultColorizationColor_1* - GP path: *Windows Components/Desktop Window Manager/Window Frame Coloring* - GP ADMX file name: *DWM.admx* @@ -182,7 +182,7 @@ If you disable or do not configure this policy setting, the default internal col ADMX Info: - GP English name: *Specify a default color* -- GP name: *DefaultColorizationColorState* +- GP name: *DwmDefaultColorizationColor_2* - GP path: *Windows Components/Desktop Window Manager/Window Frame Coloring* - GP ADMX file name: *DWM.admx* @@ -253,7 +253,7 @@ Changing this policy setting requires a logoff for it to be applied. ADMX Info: - GP English name: *Do not allow window animations* -- GP name: *DisallowAnimations* +- GP name: *DwmDisallowAnimations_1* - GP path: *Windows Components/Desktop Window Manager* - GP ADMX file name: *DWM.admx* @@ -324,7 +324,7 @@ Changing this policy setting requires a logoff for it to be applied. ADMX Info: - GP English name: *Do not allow window animations* -- GP name: *DisallowAnimations* +- GP name: *DwmDisallowAnimations_2* - GP path: *Windows Components/Desktop Window Manager* - GP ADMX file name: *DWM.admx* @@ -396,7 +396,7 @@ If you disable or do not configure this policy setting, you allow users to chang ADMX Info: - GP English name: *Do not allow color changes* -- GP name: *DisallowColorizationColorChanges* +- GP name: *DwmDisallowColorizationColorChanges_1* - GP path: *Windows Components/Desktop Window Manager/Window Frame Coloring* - GP ADMX file name: *DWM.admx* @@ -468,7 +468,7 @@ If you disable or do not configure this policy setting, you allow users to chang ADMX Info: - GP English name: *Do not allow color changes* -- GP name: *DisallowColorizationColorChanges* +- GP name: *DwmDisallowColorizationColorChanges_2* - GP path: *Windows Components/Desktop Window Manager/Window Frame Coloring* - GP ADMX file name: *DWM.admx* diff --git a/windows/client-management/mdm/policy-csp-admx-eventforwarding.md b/windows/client-management/mdm/policy-csp-admx-eventforwarding.md index ba0dcbb61d..e47d548237 100644 --- a/windows/client-management/mdm/policy-csp-admx-eventforwarding.md +++ b/windows/client-management/mdm/policy-csp-admx-eventforwarding.md @@ -97,7 +97,7 @@ This setting applies across all subscriptions for the forwarder (source computer ADMX Info: - GP English name: *Configure forwarder resource usage* -- GP name: *MaxForwardingRate* +- GP name: *ForwarderResourceUsage* - GP path: *Windows Components/Event Forwarding* - GP ADMX file name: *EventForwarding.admx* diff --git a/windows/client-management/mdm/policy-csp-admx-fileservervssprovider.md b/windows/client-management/mdm/policy-csp-admx-fileservervssprovider.md index 78ba8174f4..37b6b9a826 100644 --- a/windows/client-management/mdm/policy-csp-admx-fileservervssprovider.md +++ b/windows/client-management/mdm/policy-csp-admx-fileservervssprovider.md @@ -94,7 +94,7 @@ By default, the RPC protocol message between File Server VSS provider and File S ADMX Info: - GP English name: *Allow or Disallow use of encryption to protect the RPC protocol messages between File Share Shadow Copy Provider running on application server and File Share Shadow Copy Agent running on the file servers.* -- GP name: *EncryptProtocol* +- GP name: *Pol_EncryptProtocol* - GP path: *System/File Share Shadow Copy Provider* - GP ADMX file name: *FileServerVSSProvider.admx* diff --git a/windows/client-management/mdm/policy-csp-admx-filesys.md b/windows/client-management/mdm/policy-csp-admx-filesys.md index c669f3279e..fbdc148b37 100644 --- a/windows/client-management/mdm/policy-csp-admx-filesys.md +++ b/windows/client-management/mdm/policy-csp-admx-filesys.md @@ -106,7 +106,7 @@ Available in Windows 10 Insider Preview Build 20185. Compression can add to the ADMX Info: - GP English name: *Do not allow compression on all NTFS volumes* -- GP name: *NtfsDisableCompression* +- GP name: *DisableCompression* - GP path: *System/Filesystem/NTFS* - GP ADMX file name: *FileSys.admx* @@ -237,7 +237,7 @@ Available in Windows 10 Insider Preview Build 20185. Encryption can add to the p ADMX Info: - GP English name: *Do not allow encryption on all NTFS volumes* -- GP name: *NtfsDisableEncryption* +- GP name: *DisableEncryption* - GP path: *System/Filesystem/NTFS* - GP ADMX file name: *FileSys.admx* @@ -300,7 +300,7 @@ Available in Windows 10 Insider Preview Build 20185. Encrypting the page file pr ADMX Info: - GP English name: *Enable NTFS pagefile encryption* -- GP name: *NtfsEncryptPagingFile* +- GP name: *EnablePagefileEncryption* - GP path: *System/Filesystem/NTFS* - GP ADMX file name: *FileSys.admx* @@ -428,7 +428,7 @@ If you enable short names on all volumes then short names will always be generat ADMX Info: - GP English name: *Short name creation options* -- GP name: *NtfsDisable8dot3NameCreation* +- GP name: *ShortNameCreationSettings* - GP path: *System/Filesystem/NTFS* - GP ADMX file name: *FileSys.admx* @@ -502,7 +502,7 @@ For more information, refer to the Windows Help section. ADMX Info: - GP English name: *Selectively allow the evaluation of a symbolic link* -- GP name: *SymlinkLocalToLocalEvaluation* +- GP name: *SymlinkEvaluation* - GP path: *System/Filesystem* - GP ADMX file name: *FileSys.admx* @@ -565,7 +565,7 @@ Available in Windows 10 Insider Preview Build 20185. TXF deprecated features inc ADMX Info: - GP English name: *Enable / disable TXF deprecated features* -- GP name: *NtfsEnableTxfDeprecatedFunctionality* +- GP name: *TxfDeprecatedFunctionality* - GP path: *System/Filesystem/NTFS* - GP ADMX file name: *FileSys.admx* diff --git a/windows/client-management/mdm/policy-csp-admx-folderredirection.md b/windows/client-management/mdm/policy-csp-admx-folderredirection.md index 268a4738fe..845c514983 100644 --- a/windows/client-management/mdm/policy-csp-admx-folderredirection.md +++ b/windows/client-management/mdm/policy-csp-admx-folderredirection.md @@ -329,7 +329,7 @@ If you disable or not configure this policy setting, Windows Vista, Windows 7, W ADMX Info: - GP English name: *Use localized subfolder names when redirecting Start Menu and My Documents* -- GP name: *LocalizeXPRelativePaths* +- GP name: *LocalizeXPRelativePaths_1* - GP path: *System/Folder Redirection* - GP ADMX file name: *FolderRedirection.admx* @@ -401,7 +401,7 @@ If you disable or not configure this policy setting, Windows Vista, Windows 7, W ADMX Info: - GP English name: *Use localized subfolder names when redirecting Start Menu and My Documents* -- GP name: *LocalizeXPRelativePaths* +- GP name: *LocalizeXPRelativePaths_2* - GP path: *System/Folder Redirection* - GP ADMX file name: *FolderRedirection.admx* @@ -474,7 +474,7 @@ If you disable or do not configure this policy setting and the user has redirect ADMX Info: - GP English name: *Redirect folders on primary computers only* -- GP name: *PrimaryComputerEnabledFR* +- GP name: *PrimaryComputer_FR_1* - GP path: *System/Folder Redirection* - GP ADMX file name: *FolderRedirection.admx* @@ -547,7 +547,7 @@ If you disable or do not configure this policy setting and the user has redirect ADMX Info: - GP English name: *Redirect folders on primary computers only* -- GP name: *PrimaryComputerEnabledFR* +- GP name: *PrimaryComputer_FR_2* - GP path: *System/Folder Redirection* - GP ADMX file name: *FolderRedirection.admx* diff --git a/windows/client-management/mdm/policy-csp-admx-help.md b/windows/client-management/mdm/policy-csp-admx-help.md index 6e38d6f3fa..d705d091a0 100644 --- a/windows/client-management/mdm/policy-csp-admx-help.md +++ b/windows/client-management/mdm/policy-csp-admx-help.md @@ -185,7 +185,7 @@ For additional options, see the "Restrict these programs from being launched fro ADMX Info: - GP English name: *Restrict potentially unsafe HTML Help functions to specified folders* -- GP name: *HelpQualifiedRootDir* +- GP name: *HelpQualifiedRootDir_Comp* - GP path: *System* - GP ADMX file name: *Help.admx* @@ -259,7 +259,7 @@ If you disable or do not configure this policy setting, users can run all applic ADMX Info: - GP English name: *Restrict these programs from being launched from Help* -- GP name: *DisableInHelp* +- GP name: *RestrictRunFromHelp* - GP path: *System* - GP ADMX file name: *Help.admx* @@ -332,7 +332,7 @@ If you disable or do not configure this policy setting, users can run all applic ADMX Info: - GP English name: *Restrict these programs from being launched from Help* -- GP name: *DisableInHelp* +- GP name: *RestrictRunFromHelp_Comp* - GP path: *System* - GP ADMX file name: *Help.admx* diff --git a/windows/client-management/mdm/policy-csp-admx-helpandsupport.md b/windows/client-management/mdm/policy-csp-admx-helpandsupport.md index c076fcbc0b..10d08651fc 100644 --- a/windows/client-management/mdm/policy-csp-admx-helpandsupport.md +++ b/windows/client-management/mdm/policy-csp-admx-helpandsupport.md @@ -100,7 +100,7 @@ If you disable or do not configure this policy setting, the default behavior app ADMX Info: - GP English name: *Turn off Active Help* -- GP name: *NoActiveHelp* +- GP name: *ActiveHelp* - GP path: *Windows Components/Online Assistance* - GP ADMX file name: *HelpAndSupport.admx* @@ -171,7 +171,7 @@ Users can use the control to provide feedback on the quality and usefulness of t ADMX Info: - GP English name: *Turn off Help Ratings* -- GP name: *NoExplicitFeedback* +- GP name: *HPExplicitFeedback* - GP path: *System/Internet Communication Management/Internet Communication settings* - GP ADMX file name: *HelpAndSupport.admx* @@ -239,7 +239,7 @@ If you disable or do not configure this policy setting, users can turn on the He ADMX Info: - GP English name: *Turn off Help Experience Improvement Program* -- GP name: *NoImplicitFeedback* +- GP name: *HPImplicitFeedback* - GP path: *System/Internet Communication Management/Internet Communication settings* - GP ADMX file name: *HelpAndSupport.admx* @@ -308,7 +308,7 @@ If you disable or do not configure this policy setting, users can access online ADMX Info: - GP English name: *Turn off Windows Online* -- GP name: *NoOnlineAssist* +- GP name: *HPOnlineAssistance* - GP path: *System/Internet Communication Management/Internet Communication settings* - GP ADMX file name: *HelpAndSupport.admx* diff --git a/windows/client-management/mdm/policy-csp-admx-kdc.md b/windows/client-management/mdm/policy-csp-admx-kdc.md index eeaae0037a..4a63715208 100644 --- a/windows/client-management/mdm/policy-csp-admx-kdc.md +++ b/windows/client-management/mdm/policy-csp-admx-kdc.md @@ -133,7 +133,7 @@ Impact on domain controller performance when this policy setting is enabled: ADMX Info: - GP English name: *KDC support for claims, compound authentication and Kerberos armoring* -- GP name: *EnableCbacAndArmor* +- GP name: *CbacAndArmor* - GP path: *System/KDC* - GP ADMX file name: *kdc.admx* @@ -204,7 +204,7 @@ To ensure consistent behavior, this policy setting must be supported and set ide ADMX Info: - GP English name: *Use forest search order* -- GP name: *UseForestSearch* +- GP name: *ForestSearch* - GP path: *System/KDC* - GP ADMX file name: *kdc.admx* @@ -420,7 +420,7 @@ If you disable or do not configure this policy setting, the threshold value defa ADMX Info: - GP English name: *Warning for large Kerberos tickets* -- GP name: *EnableTicketSizeThreshold* +- GP name: *TicketSizeThreshold* - GP path: *System/KDC* - GP ADMX file name: *kdc.admx* @@ -494,7 +494,7 @@ If you disable or do not configure this policy setting, the domain controller do ADMX Info: - GP English name: *Provide information about previous logons to client computers* -- GP name: *EmitLILI* +- GP name: *emitlili* - GP path: *System/KDC* - GP ADMX file name: *kdc.admx* diff --git a/windows/client-management/mdm/policy-csp-admx-lanmanserver.md b/windows/client-management/mdm/policy-csp-admx-lanmanserver.md index 0e85c41572..ddaddd01f1 100644 --- a/windows/client-management/mdm/policy-csp-admx-lanmanserver.md +++ b/windows/client-management/mdm/policy-csp-admx-lanmanserver.md @@ -116,7 +116,7 @@ Arrange the desired cipher suites in the edit box, one cipher suite per line, in ADMX Info: - GP English name: *Cipher suite order* -- GP name: *CipherSuiteOrder* +- GP name: *Pol_CipherSuiteOrder* - GP path: *Network/Lanman Server* - GP ADMX file name: *LanmanServer.admx* @@ -199,7 +199,7 @@ In circumstances where this policy setting is enabled, you can also select the f ADMX Info: - GP English name: *Hash Publication for BranchCache* -- GP name: *HashPublicationForPeerCaching* +- GP name: *Pol_HashPublication* - GP path: *Network/Lanman Server* - GP ADMX file name: *LanmanServer.admx* @@ -286,7 +286,7 @@ Hash version supported: ADMX Info: - GP English name: *Hash Version support for BranchCache* -- GP name: *HashSupportVersion* +- GP name: *Pol_HashSupportVersion* - GP path: *Network/Lanman Server* - GP ADMX file name: *LanmanServer.admx* @@ -358,7 +358,7 @@ If you disable or do not configure this policy setting, the SMB server will sele ADMX Info: - GP English name: *Honor cipher suite order* -- GP name: *HonorCipherSuiteOrder* +- GP name: *Pol_HonorCipherSuiteOrder* - GP path: *Network/Lanman Server* - GP ADMX file name: *LanmanServer.admx* diff --git a/windows/client-management/mdm/policy-csp-admx-linklayertopologydiscovery.md b/windows/client-management/mdm/policy-csp-admx-linklayertopologydiscovery.md index 8b7e93c9b9..d4f25831ab 100644 --- a/windows/client-management/mdm/policy-csp-admx-linklayertopologydiscovery.md +++ b/windows/client-management/mdm/policy-csp-admx-linklayertopologydiscovery.md @@ -96,7 +96,7 @@ If you disable or do not configure this policy setting, the default behavior of ADMX Info: - GP English name: *Turn on Mapper I/O (LLTDIO) driver* -- GP name: *EnableLLTDIO* +- GP name: *LLTD_EnableLLTDIO* - GP path: *Network/Link-Layer Topology Discovery* - GP ADMX file name: *LinkLayerTopologyDiscovery.admx* @@ -167,7 +167,7 @@ If you disable or do not configure this policy setting, the default behavior for ADMX Info: - GP English name: *Turn on Responder (RSPNDR) driver* -- GP name: *EnableRspndr* +- GP name: *LLTD_EnableRspndr* - GP path: *Network/Link-Layer Topology Discovery* - GP ADMX file name: *LinkLayerTopologyDiscovery.admx* diff --git a/windows/client-management/mdm/policy-csp-admx-mmc.md b/windows/client-management/mdm/policy-csp-admx-mmc.md index 0766bd3fa0..a86907a534 100644 --- a/windows/client-management/mdm/policy-csp-admx-mmc.md +++ b/windows/client-management/mdm/policy-csp-admx-mmc.md @@ -113,7 +113,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *ActiveX Control* -- GP name: *Restrict_Run* +- GP name: *MMC_ActiveXControl* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins* - GP ADMX file name: *MMC.admx* @@ -192,7 +192,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *Extended View (Web View)* -- GP name: *Restrict_Run* +- GP name: *MMC_ExtendView* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Extension snap-ins* - GP ADMX file name: *MMC.admx* @@ -271,7 +271,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *Link to Web Address* -- GP name: *Restrict_Run* +- GP name: *MMC_LinkToWeb* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins* - GP ADMX file name: *MMC.admx* @@ -344,7 +344,7 @@ If you disable this setting or do not configure it, users can enter author mode ADMX Info: - GP English name: *Restrict the user from entering author mode* -- GP name: *RestrictAuthorMode* +- GP name: *MMC_Restrict_Author* - GP path: *Windows Components\Microsoft Management Console* - GP ADMX file name: *MMC.admx* @@ -422,7 +422,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *Restrict users to the explicitly permitted list of snap-ins* -- GP name: *RestrictToPermittedSnapins* +- GP name: *MMC_Restrict_To_Permitted_Snapins* - GP path: *Windows Components\Microsoft Management Console* - GP ADMX file name: *MMC.admx* diff --git a/windows/client-management/mdm/policy-csp-admx-mmcsnapins.md b/windows/client-management/mdm/policy-csp-admx-mmcsnapins.md index 6b0df4c223..cdd93c1d97 100644 --- a/windows/client-management/mdm/policy-csp-admx-mmcsnapins.md +++ b/windows/client-management/mdm/policy-csp-admx-mmcsnapins.md @@ -408,7 +408,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *Administrative Templates (Computers)* -- GP name: *Restrict_Run* +- GP name: *MMC_ADMComputers_1* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Group Policy\Group Policy snap-in extensions* - GP ADMX file name: *MMCSnapins.admx* @@ -485,7 +485,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *Administrative Templates (Computers)* -- GP name: *Restrict_Run* +- GP name: *MMC_ADMComputers_2* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Group Policy\Resultant Set of Policy snap-in extensions* - GP ADMX file name: *MMCSnapins.admx* @@ -563,7 +563,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *Administrative Templates (Users)* -- GP name: *Restrict_Run* +- GP name: *MMC_ADMUsers_1* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Group Policy\Group Policy snap-in extensions* - GP ADMX file name: *MMCSnapins.admx* @@ -641,7 +641,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *Administrative Templates (Users)* -- GP name: *Restrict_Run* +- GP name: *MMC_ADMUsers_2* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Group Policy\Resultant Set of Policy snap-in extensions* - GP ADMX file name: *MMCSnapins.admx* @@ -719,7 +719,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *ADSI Edit* -- GP name: *Restrict_Run* +- GP name: *MMC_ADSI* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins* - GP ADMX file name: *MMCSnapins.admx* @@ -797,7 +797,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *Active Directory Domains and Trusts* -- GP name: *Restrict_Run* +- GP name: *MMC_ActiveDirDomTrusts* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins* - GP ADMX file name: *MMCSnapins.admx* @@ -875,7 +875,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *Active Directory Sites and Services* -- GP name: *Restrict_Run* +- GP name: *MMC_ActiveDirSitesServices* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins* - GP ADMX file name: *MMCSnapins.admx* @@ -953,7 +953,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *Active Directory Users and Computers* -- GP name: *Restrict_Run* +- GP name: *MMC_ActiveDirUsersComp* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins* - GP ADMX file name: *MMCSnapins.admx* @@ -1031,7 +1031,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *AppleTalk Routing* -- GP name: *Restrict_Run* +- GP name: *MMC_AppleTalkRouting* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Extension snap-ins* - GP ADMX file name: *MMCSnapins.admx* @@ -1109,7 +1109,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *Authorization Manager* -- GP name: *Restrict_Run* +- GP name: *MMC_AuthMan* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Extension snap-ins* - GP ADMX file name: *MMCSnapins.admx* @@ -1187,7 +1187,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *Certification Authority* -- GP name: *Restrict_Run* +- GP name: *MMC_CertAuth* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins* - GP ADMX file name: *MMCSnapins.admx* @@ -1264,7 +1264,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *Certification Authority Policy Settings* -- GP name: *Restrict_Run* +- GP name: *MMC_CertAuthPolSet* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Extension snap-ins* - GP ADMX file name: *MMCSnapins.admx* @@ -1341,7 +1341,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *Certificates* -- GP name: *Restrict_Run* +- GP name: *MMC_Certs* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins* - GP ADMX file name: *MMCSnapins.admx* @@ -1418,7 +1418,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *Certificate Templates* -- GP name: *Restrict_Run* +- GP name: *MMC_CertsTemplate* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins* - GP ADMX file name: *MMCSnapins.admx* @@ -1495,7 +1495,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *Component Services* -- GP name: *Restrict_Run* +- GP name: *MMC_ComponentServices* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins* - GP ADMX file name: *MMCSnapins.admx* @@ -1572,7 +1572,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *Computer Management* -- GP name: *Restrict_Run* +- GP name: *MMC_ComputerManagement* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins* - GP ADMX file name: *MMCSnapins.admx* @@ -1649,7 +1649,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *Connection Sharing (NAT)* -- GP name: *Restrict_Run* +- GP name: *MMC_ConnectionSharingNAT* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Extension snap-ins* - GP ADMX file name: *MMCSnapins.admx* @@ -1726,7 +1726,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *DCOM Configuration Extension* -- GP name: *Restrict_Run* +- GP name: *MMC_DCOMCFG* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Extension snap-ins* - GP ADMX file name: *MMCSnapins.admx* @@ -1803,7 +1803,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *Distributed File System* -- GP name: *Restrict_Run* +- GP name: *MMC_DFS* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins* - GP ADMX file name: *MMCSnapins.admx* @@ -1880,7 +1880,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *DHCP Relay Management* -- GP name: *Restrict_Run* +- GP name: *MMC_DHCPRelayMgmt* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Extension snap-ins* - GP ADMX file name: *MMCSnapins.admx* @@ -1957,7 +1957,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *Device Manager* -- GP name: *Restrict_Run* +- GP name: *MMC_DeviceManager_1* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Extension snap-ins* - GP ADMX file name: *MMCSnapins.admx* @@ -2034,7 +2034,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *Device Manager* -- GP name: *Restrict_Run* +- GP name: *MMC_DeviceManager_2* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins* - GP ADMX file name: *MMCSnapins.admx* @@ -2111,7 +2111,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *Disk Defragmenter* -- GP name: *Restrict_Run* +- GP name: *MMC_DiskDefrag* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins* - GP ADMX file name: *MMCSnapins.admx* @@ -2188,7 +2188,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *Disk Management* -- GP name: *Restrict_Run* +- GP name: *MMC_DiskMgmt* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins* - GP ADMX file name: *MMCSnapins.admx* @@ -2265,7 +2265,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *Enterprise PKI* -- GP name: *Restrict_Run* +- GP name: *MMC_EnterprisePKI* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins* - GP ADMX file name: *MMCSnapins.admx* @@ -2342,7 +2342,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *Event Viewer* -- GP name: *Restrict_Run* +- GP name: *MMC_EventViewer_1* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Extension snap-ins* - GP ADMX file name: *MMCSnapins.admx* @@ -2419,7 +2419,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *Event Viewer (Windows Vista)* -- GP name: *Restrict_Run* +- GP name: *MMC_EventViewer_2* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Extension snap-ins* - GP ADMX file name: *MMCSnapins.admx* @@ -2496,7 +2496,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *Event Viewer* -- GP name: *Restrict_Run* +- GP name: *MMC_EventViewer_3* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins* - GP ADMX file name: *MMCSnapins.admx* @@ -2573,7 +2573,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *Event Viewer (Windows Vista)* -- GP name: *Restrict_Run* +- GP name: *MMC_EventViewer_4* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins* - GP ADMX file name: *MMCSnapins.admx* @@ -2651,7 +2651,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *Event Viewer (Windows Vista)* -- GP name: *Restrict_Run* +- GP name: *MMC_EventViewer_2* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins* - GP ADMX file name: *MMCSnapins.admx* @@ -2728,7 +2728,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *FAX Service* -- GP name: *Restrict_Run* +- GP name: *MMC_FAXService* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins* - GP ADMX file name: *MMCSnapins.admx* @@ -2805,7 +2805,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *Failover Clusters Manager* -- GP name: *Restrict_Run* +- GP name: *MMC_FailoverClusters* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins* - GP ADMX file name: *MMCSnapins.admx* @@ -2882,7 +2882,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *Folder Redirection* -- GP name: *Restrict_Run* +- GP name: *MMC_FolderRedirection_1* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Group Policy\Group Policy snap-in extensions* - GP ADMX file name: *MMCSnapins.admx* @@ -2959,7 +2959,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *Folder Redirection* -- GP name: *Restrict_Run* +- GP name: *MMC_FolderRedirection_2* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Group Policy\Resultant Set of Policy snap-in extensions* - GP ADMX file name: *MMCSnapins.admx* @@ -3036,7 +3036,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *FrontPage Server Extensions* -- GP name: *Restrict_Run* +- GP name: *MMC_FrontPageExt* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins* - GP ADMX file name: *MMCSnapins.admx* @@ -3113,7 +3113,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *Group Policy Management* -- GP name: *Restrict_Run* +- GP name: *MMC_GroupPolicyManagementSnapIn* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Group Policy* - GP ADMX file name: *MMCSnapins.admx* @@ -3190,7 +3190,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *Group Policy Object Editor* -- GP name: *Restrict_Run* +- GP name: *MMC_GroupPolicySnapIn* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Group Policy* - GP ADMX file name: *MMCSnapins.admx* @@ -3269,7 +3269,7 @@ When the Group Policy tab is inaccessible, it does not appear in the site, domai ADMX Info: - GP English name: *Group Policy tab for Active Directory Tools* -- GP name: *Restrict_Run* +- GP name: *MMC_GroupPolicyTab* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Group Policy* - GP ADMX file name: *MMCSnapins.admx* @@ -3346,7 +3346,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *Health Registration Authority (HRA)* -- GP name: *Restrict_Run* +- GP name: *MMC_HRA* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins* - GP ADMX file name: *MMCSnapins.admx* @@ -3423,7 +3423,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *Internet Authentication Service (IAS)* -- GP name: *Restrict_Run* +- GP name: *MMC_IAS* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins* - GP ADMX file name: *MMCSnapins.admx* @@ -3500,7 +3500,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *IAS Logging* -- GP name: *Restrict_Run* +- GP name: *MMC_IASLogging* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Extension snap-ins* - GP ADMX file name: *MMCSnapins.admx* @@ -3577,7 +3577,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *Internet Explorer Maintenance* -- GP name: *Restrict_Run* +- GP name: *MMC_IEMaintenance_1* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Group Policy\Group Policy snap-in extensions* - GP ADMX file name: *MMCSnapins.admx* @@ -3654,7 +3654,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *Internet Explorer Maintenance* -- GP name: *Restrict_Run* +- GP name: *MMC_IEMaintenance_2* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Group Policy\Resultant Set of Policy snap-in extensions* - GP ADMX file name: *MMCSnapins.admx* @@ -3731,7 +3731,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *IGMP Routing* -- GP name: *Restrict_Run* +- GP name: *MMC_IGMPRouting* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Extension snap-ins* - GP ADMX file name: *MMCSnapins.admx* @@ -3808,7 +3808,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *Internet Information Services* -- GP name: *Restrict_Run* +- GP name: *MMC_IIS* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins* - GP ADMX file name: *MMCSnapins.admx* @@ -3885,7 +3885,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *IP Routing* -- GP name: *Restrict_Run* +- GP name: *MMC_IPRouting* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Extension snap-ins* - GP ADMX file name: *MMCSnapins.admx* @@ -3962,7 +3962,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *IP Security Policy Management* -- GP name: *Restrict_Run* +- GP name: *MMC_IPSecManage_GP* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Group Policy\Group Policy snap-in extensions* - GP ADMX file name: *MMCSnapins.admx* @@ -4039,7 +4039,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *IPX RIP Routing* -- GP name: *Restrict_Run* +- GP name: *MMC_IPXRIPRouting* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Extension snap-ins* - GP ADMX file name: *MMCSnapins.admx* @@ -4116,7 +4116,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *IPX Routing* -- GP name: *Restrict_Run* +- GP name: *MMC_IPXRouting* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Extension snap-ins* - GP ADMX file name: *MMCSnapins.admx* @@ -4193,7 +4193,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *IPX SAP Routing* -- GP name: *Restrict_Run* +- GP name: *MMC_IPXSAPRouting* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Extension snap-ins* - GP ADMX file name: *MMCSnapins.admx* @@ -4270,7 +4270,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *Indexing Service* -- GP name: *Restrict_Run* +- GP name: *MMC_IndexingService* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins* - GP ADMX file name: *MMCSnapins.admx* @@ -4347,7 +4347,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *IP Security Policy Management* -- GP name: *Restrict_Run* +- GP name: *MMC_IpSecManage* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins* - GP ADMX file name: *MMCSnapins.admx* @@ -4424,7 +4424,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *IP Security Monitor* -- GP name: *Restrict_Run* +- GP name: *MMC_IpSecMonitor* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins* - GP ADMX file name: *MMCSnapins.admx* @@ -4501,7 +4501,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *Local Users and Groups* -- GP name: *Restrict_Run* +- GP name: *MMC_LocalUsersGroups* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins* - GP ADMX file name: *MMCSnapins.admx* @@ -4578,7 +4578,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *Logical and Mapped Drives* -- GP name: *Restrict_Run* +- GP name: *MMC_LogicalMappedDrives* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Extension snap-ins* - GP ADMX file name: *MMCSnapins.admx* @@ -4655,7 +4655,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *Network Policy Server (NPS)* -- GP name: *Restrict_Run* +- GP name: *MMC_NPSUI* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins* - GP ADMX file name: *MMCSnapins.admx* @@ -4732,7 +4732,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *NAP Client Configuration* -- GP name: *Restrict_Run* +- GP name: *MMC_NapSnap* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins* - GP ADMX file name: *MMCSnapins.admx* @@ -4809,7 +4809,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *NAP Client Configuration* -- GP name: *Restrict_Run* +- GP name: *MMC_NapSnap_GP* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Group Policy\Group Policy snap-in extensions* - GP ADMX file name: *MMCSnapins.admx* @@ -4886,7 +4886,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *.Net Framework Configuration* -- GP name: *Restrict_Run* +- GP name: *MMC_Net_Framework* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins* - GP ADMX file name: *MMCSnapins.admx* @@ -4963,7 +4963,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *Online Responder* -- GP name: *Restrict_Run* +- GP name: *MMC_OCSP* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins* - GP ADMX file name: *MMCSnapins.admx* @@ -5040,7 +5040,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *OSPF Routing* -- GP name: *Restrict_Run* +- GP name: *MMC_OSPFRouting* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Extension snap-ins* - GP ADMX file name: *MMCSnapins.admx* @@ -5117,7 +5117,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *Performance Logs and Alerts* -- GP name: *Restrict_Run* +- GP name: *MMC_PerfLogsAlerts* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins* - GP ADMX file name: *MMCSnapins.admx* @@ -5194,7 +5194,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *Public Key Policies* -- GP name: *Restrict_Run* +- GP name: *MMC_PublicKey* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Extension snap-ins* - GP ADMX file name: *MMCSnapins.admx* @@ -5271,7 +5271,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *QoS Admission Control* -- GP name: *Restrict_Run* +- GP name: *MMC_QoSAdmission* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins* - GP ADMX file name: *MMCSnapins.admx* @@ -5348,7 +5348,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *RAS Dialin - User Node* -- GP name: *Restrict_Run* +- GP name: *MMC_RAS_DialinUser* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Extension snap-ins* - GP ADMX file name: *MMCSnapins.admx* @@ -5425,7 +5425,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *RIP Routing* -- GP name: *Restrict_Run* +- GP name: *MMC_RIPRouting* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Extension snap-ins* - GP ADMX file name: *MMCSnapins.admx* @@ -5502,7 +5502,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *Remote Installation Services* -- GP name: *Restrict_Run* +- GP name: *MMC_RIS* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Group Policy\Group Policy snap-in extensions* - GP ADMX file name: *MMCSnapins.admx* @@ -5579,7 +5579,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *Routing and Remote Access* -- GP name: *Restrict_Run* +- GP name: *MMC_RRA* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins* - GP ADMX file name: *MMCSnapins.admx* @@ -5656,7 +5656,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *Removable Storage Management* -- GP name: *Restrict_Run* +- GP name: *MMC_RSM* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins* - GP ADMX file name: *MMCSnapins.admx* @@ -5733,7 +5733,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *Removable Storage* -- GP name: *Restrict_Run* +- GP name: *MMC_RemStore* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Extension snap-ins* - GP ADMX file name: *MMCSnapins.admx* @@ -5810,7 +5810,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *Remote Access* -- GP name: *Restrict_Run* +- GP name: *MMC_RemoteAccess* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Extension snap-ins* - GP ADMX file name: *MMCSnapins.admx* @@ -5887,7 +5887,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *Remote Desktops* -- GP name: *Restrict_Run* +- GP name: *MMC_RemoteDesktop* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins* - GP ADMX file name: *MMCSnapins.admx* @@ -5964,7 +5964,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *Resultant Set of Policy snap-in* -- GP name: *Restrict_Run* +- GP name: *MMC_ResultantSetOfPolicySnapIn* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Group Policy* - GP ADMX file name: *MMCSnapins.admx* @@ -6041,7 +6041,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *Routing* -- GP name: *Restrict_Run* +- GP name: *MMC_Routing* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Extension snap-ins* - GP ADMX file name: *MMCSnapins.admx* @@ -6118,7 +6118,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *Security Configuration and Analysis* -- GP name: *Restrict_Run* +- GP name: *MMC_SCA* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins* - GP ADMX file name: *MMCSnapins.admx* @@ -6195,7 +6195,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *SMTP Protocol* -- GP name: *Restrict_Run* +- GP name: *MMC_SMTPProtocol* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Extension snap-ins* - GP ADMX file name: *MMCSnapins.admx* @@ -6272,7 +6272,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *SNMP* -- GP name: *Restrict_Run* +- GP name: *MMC_SNMP* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Extension snap-ins* - GP ADMX file name: *MMCSnapins.admx* @@ -6349,7 +6349,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *Scripts (Startup/Shutdown)* -- GP name: *Restrict_Run* +- GP name: *MMC_ScriptsMachine_1* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Group Policy\Group Policy snap-in extensions* - GP ADMX file name: *MMCSnapins.admx* @@ -6426,7 +6426,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *Scripts (Startup/Shutdown)* -- GP name: *Restrict_Run* +- GP name: *MMC_ScriptsMachine_2* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Group Policy\Resultant Set of Policy snap-in extensions* - GP ADMX file name: *MMCSnapins.admx* @@ -6503,7 +6503,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *Scripts (Logon/Logoff)* -- GP name: *Restrict_Run* +- GP name: *MMC_ScriptsUser_1* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Group Policy\Group Policy snap-in extensions* - GP ADMX file name: *MMCSnapins.admx* @@ -6580,7 +6580,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *Scripts (Logon/Logoff)* -- GP name: *Restrict_Run* +- GP name: *MMC_ScriptsUser_2* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Group Policy\Resultant Set of Policy snap-in extensions* - GP ADMX file name: *MMCSnapins.admx* @@ -6657,7 +6657,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *Security Settings* -- GP name: *Restrict_Run* +- GP name: *MMC_SecuritySettings_1* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Group Policy\Group Policy snap-in extensions* - GP ADMX file name: *MMCSnapins.admx* @@ -6734,7 +6734,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *Security Settings* -- GP name: *Restrict_Run* +- GP name: *MMC_SecuritySettings_2* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Group Policy\Resultant Set of Policy snap-in extensions* - GP ADMX file name: *MMCSnapins.admx* @@ -6811,7 +6811,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *Security Templates* -- GP name: *Restrict_Run* +- GP name: *MMC_SecurityTemplates* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins* - GP ADMX file name: *MMCSnapins.admx* @@ -6888,7 +6888,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *Send Console Message* -- GP name: *Restrict_Run* +- GP name: *MMC_SendConsoleMessage* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Extension snap-ins* - GP ADMX file name: *MMCSnapins.admx* @@ -6965,7 +6965,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *Server Manager* -- GP name: *Restrict_Run* +- GP name: *MMC_ServerManager* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins* - GP ADMX file name: *MMCSnapins.admx* @@ -7042,7 +7042,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *Service Dependencies* -- GP name: *Restrict_Run* +- GP name: *MMC_ServiceDependencies* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Extension snap-ins* - GP ADMX file name: *MMCSnapins.admx* @@ -7119,7 +7119,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *Services* -- GP name: *Restrict_Run* +- GP name: *MMC_Services* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins* - GP ADMX file name: *MMCSnapins.admx* @@ -7196,7 +7196,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *Shared Folders* -- GP name: *Restrict_Run* +- GP name: *MMC_SharedFolders* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins* - GP ADMX file name: *MMCSnapins.admx* @@ -7273,7 +7273,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *Shared Folders Ext* -- GP name: *Restrict_Run* +- GP name: *MMC_SharedFolders_Ext* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Extension snap-ins* - GP ADMX file name: *MMCSnapins.admx* @@ -7350,7 +7350,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *Software Installation (Computers)* -- GP name: *Restrict_Run* +- GP name: *MMC_SoftwareInstalationComputers_1* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Group Policy\Group Policy snap-in extensions* - GP ADMX file name: *MMCSnapins.admx* @@ -7427,7 +7427,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *Software Installation (Computers)* -- GP name: *Restrict_Run* +- GP name: *MMC_SoftwareInstalationComputers_2* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Group Policy\Resultant Set of Policy snap-in extensions* - GP ADMX file name: *MMCSnapins.admx* @@ -7504,7 +7504,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *Software Installation (Users)* -- GP name: *Restrict_Run* +- GP name: *MMC_SoftwareInstallationUsers_1* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Group Policy\Group Policy snap-in extensions* - GP ADMX file name: *MMCSnapins.admx* @@ -7581,7 +7581,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *Software Installation (Users)* -- GP name: *Restrict_Run* +- GP name: *MMC_SoftwareInstallationUsers_2* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Group Policy\Resultant Set of Policy snap-in extensions* - GP ADMX file name: *MMCSnapins.admx* @@ -7658,7 +7658,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *System Information* -- GP name: *Restrict_Run* +- GP name: *MMC_SysInfo* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins* - GP ADMX file name: *MMCSnapins.admx* @@ -7735,7 +7735,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *System Properties* -- GP name: *Restrict_Run* +- GP name: *MMC_SysProp* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Extension snap-ins* - GP ADMX file name: *MMCSnapins.admx* @@ -7812,7 +7812,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *TPM Management* -- GP name: *Restrict_Run* +- GP name: *MMC_TPMManagement* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins* - GP ADMX file name: *MMCSnapins.admx* @@ -7889,7 +7889,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *Telephony* -- GP name: *Restrict_Run* +- GP name: *MMC_Telephony* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins* - GP ADMX file name: *MMCSnapins.admx* @@ -7966,7 +7966,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *Remote Desktop Services Configuration* -- GP name: *Restrict_Run* +- GP name: *MMC_TerminalServices* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins* - GP ADMX file name: *MMCSnapins.admx* @@ -8043,7 +8043,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *WMI Control* -- GP name: *Restrict_Run* +- GP name: *MMC_WMI* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins* - GP ADMX file name: *MMCSnapins.admx* @@ -8120,7 +8120,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *Windows Firewall with Advanced Security* -- GP name: *Restrict_Run* +- GP name: *MMC_WindowsFirewall* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins* - GP ADMX file name: *MMCSnapins.admx* @@ -8197,7 +8197,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *Windows Firewall with Advanced Security* -- GP name: *Restrict_Run* +- GP name: *MMC_WindowsFirewall_GP* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Group Policy\Group Policy snap-in extensions* - GP ADMX file name: *MMCSnapins.admx* @@ -8274,7 +8274,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *Wired Network (IEEE 802.3) Policies* -- GP name: *Restrict_Run* +- GP name: *MMC_WiredNetworkPolicy* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Group Policy\Group Policy snap-in extensions* - GP ADMX file name: *MMCSnapins.admx* @@ -8351,7 +8351,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *Wireless Monitor* -- GP name: *Restrict_Run* +- GP name: *MMC_WirelessMon* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins* - GP ADMX file name: *MMCSnapins.admx* @@ -8428,7 +8428,7 @@ When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in windo ADMX Info: - GP English name: *Wireless Network (IEEE 802.11) Policies* -- GP name: *Restrict_Run* +- GP name: *MMC_WirelessNetworkPolicy* - GP path: *Windows Components\Microsoft Management Console\Restricted/Permitted snap-ins\Group Policy\Group Policy snap-in extensions* - GP ADMX file name: *MMCSnapins.admx* diff --git a/windows/client-management/mdm/policy-csp-admx-msapolicy.md b/windows/client-management/mdm/policy-csp-admx-msapolicy.md index fb3a2c7585..e8c35ac22e 100644 --- a/windows/client-management/mdm/policy-csp-admx-msapolicy.md +++ b/windows/client-management/mdm/policy-csp-admx-msapolicy.md @@ -93,7 +93,7 @@ By default, this setting is Disabled. This setting does not affect whether users ADMX Info: - GP English name: *Block all consumer Microsoft account user authentication* -- GP name: *DisableUserAuth* +- GP name: *MicrosoftAccount_DisableUserAuth* - GP path: *Windows Components\Microsoft account* - GP ADMX file name: *MSAPolicy.admx* diff --git a/windows/client-management/mdm/policy-csp-admx-nca.md b/windows/client-management/mdm/policy-csp-admx-nca.md index 9417e592bc..840af17067 100644 --- a/windows/client-management/mdm/policy-csp-admx-nca.md +++ b/windows/client-management/mdm/policy-csp-admx-nca.md @@ -122,7 +122,7 @@ You must configure this setting to have complete NCA functionality. ADMX Info: - GP English name: *Corporate Resources* -- GP name: *Probe* +- GP name: *CorporateResources* - GP path: *Network\DirectAccess Client Experience Settings* - GP ADMX file name: *nca.admx* @@ -187,7 +187,7 @@ Available in Windows 10 Insider Preview Build 20185. This policy setting specifi ADMX Info: - GP English name: *Custom Commands* -- GP name: *CustomCommand* +- GP name: *CustomCommands* - GP path: *Network\DirectAccess Client Experience Settings* - GP ADMX file name: *nca.admx* @@ -258,7 +258,7 @@ You must configure this setting to have complete NCA functionality. ADMX Info: - GP English name: *IPsec Tunnel Endpoints* -- GP name: *DTE* +- GP name: *DTEs* - GP path: *Network\DirectAccess Client Experience Settings* - GP ADMX file name: *nca.admx* @@ -401,7 +401,7 @@ If this setting is not configured, users do not have Connect or Disconnect optio ADMX Info: - GP English name: *Prefer Local Names Allowed* -- GP name: *NamePreferenceAllowed* +- GP name: *LocalNamesOn* - GP path: *Network\DirectAccess Client Experience Settings* - GP ADMX file name: *nca.admx* diff --git a/windows/client-management/mdm/policy-csp-admx-ncsi.md b/windows/client-management/mdm/policy-csp-admx-ncsi.md index bd18a2f3bd..3e575f3fdf 100644 --- a/windows/client-management/mdm/policy-csp-admx-ncsi.md +++ b/windows/client-management/mdm/policy-csp-admx-ncsi.md @@ -105,7 +105,7 @@ Available in Windows 10 Insider Preview Build 20185. This policy setting enable ADMX Info: - GP English name: *Specify corporate DNS probe host address* -- GP name: *DnsProbeContent* +- GP name: *NCSI_CorpDnsProbeContent* - GP path: *Network\Network Connectivity Status Indicator* - GP ADMX file name: *NCSI.admx* @@ -170,7 +170,7 @@ Available in Windows 10 Insider Preview Build 20185. This policy setting enables ADMX Info: - GP English name: *Specify corporate DNS probe host name* -- GP name: *DnsProbeHost* +- GP name: *NCSI_CorpDnsProbeHost* - GP path: *Network\Network Connectivity Status Indicator* - GP ADMX file name: *NCSI.admx* @@ -235,7 +235,7 @@ Available in Windows 10 Insider Preview Build 20185. This policy setting enables ADMX Info: - GP English name: *Specify corporate site prefix list* -- GP name: *SitePrefixes* +- GP name: *NCSI_CorpSitePrefixes* - GP path: *Network\Network Connectivity Status Indicator* - GP ADMX file name: *NCSI.admx* @@ -300,7 +300,7 @@ Available in Windows 10 Insider Preview Build 20185. This policy setting enables ADMX Info: - GP English name: *Specify corporate Website probe URL* -- GP name: *WebProbeUrl* +- GP name: *NCSI_CorpWebProbeUrl* - GP path: *Network\Network Connectivity Status Indicator* - GP ADMX file name: *NCSI.admx* @@ -368,7 +368,7 @@ Available in Windows 10 Insider Preview Build 20185. This policy setting enables ADMX Info: - GP English name: *Specify domain location determination URL* -- GP name: *DomainLocationDeterminationUrl* +- GP name: *NCSI_DomainLocationDeterminationUrl* - GP path: *Network\Network Connectivity Status Indicator* - GP ADMX file name: *NCSI.admx* @@ -433,7 +433,7 @@ Available in Windows 10 Insider Preview Build 20185. This policy setting enables ADMX Info: - GP English name: *Specify global DNS* -- GP name: *UseGlobalDns* +- GP name: *NCSI_GlobalDns* - GP path: *Network\Network Connectivity Status Indicator* - GP ADMX file name: *NCSI.admx* @@ -498,7 +498,7 @@ Available in Windows 10 Insider Preview Build 20185. This Policy setting enables ADMX Info: - GP English name: *Specify passive polling* -- GP name: *DisablePassivePolling* +- GP name: *NCSI_PassivePolling* - GP path: *Network\Network Connectivity Status Indicator* - GP ADMX file name: *NCSI.admx* diff --git a/windows/client-management/mdm/policy-csp-admx-netlogon.md b/windows/client-management/mdm/policy-csp-admx-netlogon.md index 51a9c850b2..782b57ba8c 100644 --- a/windows/client-management/mdm/policy-csp-admx-netlogon.md +++ b/windows/client-management/mdm/policy-csp-admx-netlogon.md @@ -201,7 +201,7 @@ If you do not configure this policy setting, it is not applied to any DCs, and D ADMX Info: - GP English name: *Specify address lookup behavior for DC locator ping* -- GP name: *AddressLookupOnPingBehavior* +- GP name: *Netlogon_AddressLookupOnPingBehavior* - GP path: *System\Net Logon\DC Locator DNS Records* - GP ADMX file name: *Netlogon.admx* @@ -274,7 +274,7 @@ If you do not configure this policy setting, DC Locator APIs can return IPv4/IPv ADMX Info: - GP English name: *Return domain controller address type* -- GP name: *AddressTypeReturned* +- GP name: *Netlogon_AddressTypeReturned* - GP path: *System\Net Logon\DC Locator DNS Records* - GP ADMX file name: *Netlogon.admx* @@ -347,7 +347,7 @@ If you disable this policy setting, when the AllowSingleLabelDnsDomain policy is ADMX Info: - GP English name: *Use DNS name resolution when a single-label domain name is used, by appending different registered DNS suffixes, if the AllowSingleLabelDnsDomain setting is not enabled.* -- GP name: *AllowDnsSuffixSearch* +- GP name: *Netlogon_AllowDnsSuffixSearch* - GP path: *System\Net Logon\DC Locator DNS Records* - GP ADMX file name: *Netlogon.admx* @@ -422,7 +422,7 @@ If you do not configure this policy setting, Net Logon will not allow the negoti ADMX Info: - GP English name: *Allow cryptography algorithms compatible with Windows NT 4.0* -- GP name: *AllowNT4Crypto* +- GP name: *Netlogon_AllowNT4Crypto* - GP path: *System\Net Logon* - GP ADMX file name: *Netlogon.admx* @@ -497,7 +497,7 @@ If you do not configure this policy setting, it is not applied to any computers, ADMX Info: - GP English name: *Use DNS name resolution with a single-label domain name instead of NetBIOS name resolution to locate the DC* -- GP name: *AllowSingleLabelDnsDomain* +- GP name: *Netlogon_AllowSingleLabelDnsDomain* - GP path: *System\Net Logon\DC Locator DNS Records* - GP ADMX file name: *Netlogon.admx* @@ -570,7 +570,7 @@ If you do not configure this policy setting, it is not applied to any DCs, and D ADMX Info: - GP English name: *Use automated site coverage by the DC Locator DNS SRV Records* -- GP name: *AutoSiteCoverage* +- GP name: *Netlogon_AutoSiteCoverage* - GP path: *System\Net Logon\DC Locator DNS Records* - GP ADMX file name: *Netlogon.admx* @@ -646,7 +646,7 @@ If you disable this policy setting, the DC location algorithm can use NetBIOS-ba ADMX Info: - GP English name: *Do not use NetBIOS-based discovery for domain controller location when DNS-based discovery fails* -- GP name: *AvoidFallbackNetbiosDiscovery* +- GP name: *Netlogon_AvoidFallbackNetbiosDiscovery* - GP path: *System\Net Logon\DC Locator DNS Records* - GP ADMX file name: *Netlogon.admx* @@ -721,7 +721,7 @@ If you do not configure this policy setting, it is not applied to any DCs. ADMX Info: - GP English name: *Contact PDC on logon failure* -- GP name: *AvoidPdcOnWan* +- GP name: *Netlogon_AvoidPdcOnWan* - GP path: *System\Net Logon* - GP ADMX file name: *Netlogon.admx* @@ -799,7 +799,7 @@ If the value of this setting is less than the value specified in the NegativeCac ADMX Info: - GP English name: *Use initial DC discovery retry setting for background callers* -- GP name: *BackgroundRetryInitialPeriod* +- GP name: *Netlogon_BackgroundRetryInitialPeriod* - GP path: *System\Net Logon* - GP ADMX file name: *Netlogon.admx* @@ -879,7 +879,7 @@ If the value for this setting is too small and the DC is not available, the freq ADMX Info: - GP English name: *Use maximum DC discovery retry interval setting for background callers* -- GP name: *BackgroundRetryMaximumPeriod* +- GP name: *Netlogon_BackgroundRetryMaximumPeriod* - GP path: *System\Net Logon* - GP ADMX file name: *Netlogon.admx* @@ -951,7 +951,7 @@ The default value for this setting is to not quit retrying (0). The maximum valu ADMX Info: - GP English name: *Use final DC discovery retry setting for background callers* -- GP name: *BackgroundRetryQuitTime* +- GP name: *Netlogon_BackgroundRetryQuitTime* - GP path: *System\Net Logon* - GP ADMX file name: *Netlogon.admx* @@ -1018,7 +1018,7 @@ Available in Windows 10 Insider Preview Build 20185. This policy setting determi ADMX Info: - GP English name: *Use positive periodic DC cache refresh for background callers* -- GP name: *BackgroundSuccessfulRefreshPeriod* +- GP name: *Netlogon_BackgroundSuccessfulRefreshPeriod* - GP path: *System\Net Logon* - GP ADMX file name: *Netlogon.admx* @@ -1093,7 +1093,7 @@ If you disable this policy setting or do not configure it, the default behavior ADMX Info: - GP English name: *Specify log file debug output level* -- GP name: *dbFlag* +- GP name: *Netlogon_DebugFlag* - GP path: *System\Net Logon* - GP ADMX file name: *Netlogon.admx* @@ -1192,7 +1192,7 @@ If you do not configure this policy setting, DCs use their local configuration. ADMX Info: - GP English name: *Specify DC Locator DNS records not registered by the DCs* -- GP name: *DnsAvoidRegisterRecords* +- GP name: *Netlogon_DnsAvoidRegisterRecords* - GP path: *System\Net Logon\DC Locator DNS Records* - GP ADMX file name: *Netlogon.admx* @@ -1268,7 +1268,7 @@ If you do not configure this policy setting, it is not applied to any DCs, and D ADMX Info: - GP English name: *Specify Refresh Interval of the DC Locator DNS records* -- GP name: *DnsRefreshInterval* +- GP name: *Netlogon_DnsRefreshInterval* - GP path: *System\Net Logon\DC Locator DNS Records* - GP ADMX file name: *Netlogon.admx* @@ -1344,7 +1344,7 @@ A reboot is not required for changes to this setting to take effect. ADMX Info: - GP English name: *Use lowercase DNS host names when registering domain controller SRV records* -- GP name: *DnsSrvRecordUseLowerCaseHostNames* +- GP name: *Netlogon_DnsSrvRecordUseLowerCaseHostNames* - GP path: *System\Net Logon\DC Locator DNS Records* - GP ADMX file name: *Netlogon.admx* @@ -1414,7 +1414,7 @@ If you do not configure this policy setting, it is not applied to any DCs, and D ADMX Info: - GP English name: *Set TTL in the DC Locator DNS Records* -- GP name: *DnsTtl* +- GP name: *Netlogon_DnsTtl* - GP path: *System\Net Logon\DC Locator DNS Records* - GP ADMX file name: *Netlogon.admx* @@ -1485,7 +1485,7 @@ If you do not configure this policy setting, it is not applied to any computers, ADMX Info: - GP English name: *Specify expected dial-up delay on logon* -- GP name: *ExpectedDialupDelay* +- GP name: *Netlogon_ExpectedDialupDelay* - GP path: *System\Net Logon* - GP ADMX file name: *Netlogon.admx* @@ -1560,7 +1560,7 @@ If you do not configure this policy setting, Force Rediscovery will be used by d ADMX Info: - GP English name: *Force Rediscovery Interval* -- GP name: *ForceRediscoveryInterval* +- GP name: *Netlogon_ForceRediscoveryInterval* - GP path: *System\Net Logon\DC Locator DNS Records* - GP ADMX file name: *Netlogon.admx* @@ -1633,7 +1633,7 @@ If you do not configure this policy setting, it is not applied to any GCs, and G ADMX Info: - GP English name: *Specify sites covered by the GC Locator DNS SRV Records* -- GP name: *GcSiteCoverage* +- GP name: *Netlogon_GcSiteCoverage* - GP path: *System\Net Logon\DC Locator DNS Records* - GP ADMX file name: *Netlogon.admx* @@ -1709,7 +1709,7 @@ If you disable or do not configure this policy setting, this DC processes incomi ADMX Info: - GP English name: *Do not process incoming mailslot messages used for domain controller location based on NetBIOS domain names* -- GP name: *IgnoreIncomingMailslotMessages* +- GP name: *Netlogon_IgnoreIncomingMailslotMessages* - GP path: *System\Net Logon\DC Locator DNS Records* - GP ADMX file name: *Netlogon.admx* @@ -1782,7 +1782,7 @@ If you do not configure this policy setting, it is not applied to any DCs, and D ADMX Info: - GP English name: *Set Priority in the DC Locator DNS SRV records* -- GP name: *LdapSrvPriority* +- GP name: *Netlogon_LdapSrvPriority* - GP path: *System\Net Logon\DC Locator DNS Records* - GP ADMX file name: *Netlogon.admx* @@ -1855,7 +1855,7 @@ If you do not configure this policy setting, it is not applied to any DCs, and D ADMX Info: - GP English name: *Set Weight in the DC Locator DNS SRV records* -- GP name: *LdapSrvWeight* +- GP name: *Netlogon_LdapSrvWeight* - GP path: *System\Net Logon\DC Locator DNS Records* - GP ADMX file name: *Netlogon.admx* @@ -1926,7 +1926,7 @@ If you disable or do not configure this policy setting, the default behavior occ ADMX Info: - GP English name: *Specify maximum log file size* -- GP name: *MaximumLogFileSize* +- GP name: *Netlogon_MaximumLogFileSize* - GP path: *System\Net Logon* - GP ADMX file name: *Netlogon.admx* @@ -1999,7 +1999,7 @@ If you do not configure this policy setting, it is not applied to any DCs, and D ADMX Info: - GP English name: *Specify sites covered by the application directory partition DC Locator DNS SRV records* -- GP name: *NdncSiteCoverage* +- GP name: *Netlogon_NdncSiteCoverage* - GP path: *System\Net Logon\DC Locator DNS Records* - GP ADMX file name: *Netlogon.admx* @@ -2071,7 +2071,7 @@ The default value for this setting is 45 seconds. The maximum value for this set ADMX Info: - GP English name: *Specify negative DC Discovery cache setting* -- GP name: *NegativeCachePeriod* +- GP name: *Netlogon_NegativeCachePeriod* - GP path: *System\Net Logon* - GP ADMX file name: *Netlogon.admx* @@ -2149,7 +2149,7 @@ If you enable this policy setting, domain administrators should ensure that the ADMX Info: - GP English name: *Set Netlogon share compatibility* -- GP name: *AllowExclusiveScriptsShareAccess* +- GP name: *Netlogon_NetlogonShareCompatibilityMode* - GP path: *System\Net Logon* - GP ADMX file name: *Netlogon.admx* @@ -2218,7 +2218,7 @@ The default value for this setting is 30 minutes (1800). The maximum value for t ADMX Info: - GP English name: *Specify positive periodic DC Cache refresh for non-background callers* -- GP name: *NonBackgroundSuccessfulRefreshPeriod* +- GP name: *Netlogon_NonBackgroundSuccessfulRefreshPeriod* - GP path: *System\Net Logon* - GP ADMX file name: *Netlogon.admx* @@ -2296,7 +2296,7 @@ If you do not configure this policy setting, it is not applied to any computers, ADMX Info: - GP English name: *Use urgent mode when pinging domain controllers* -- GP name: *PingUrgencyMode* +- GP name: *Netlogon_PingUrgencyMode* - GP path: *System\Net Logon* - GP ADMX file name: *Netlogon.admx* @@ -2373,7 +2373,7 @@ To enable the setting, click Enabled, and then specify the interval in seconds. ADMX Info: - GP English name: *Set scavenge interval* -- GP name: *ScavengeInterval* +- GP name: *Netlogon_ScavengeInterval* - GP path: *System\Net Logon* - GP ADMX file name: *Netlogon.admx* @@ -2446,7 +2446,7 @@ If you do not configure this policy setting, it is not applied to any DCs, and D ADMX Info: - GP English name: *Specify sites covered by the DC Locator DNS SRV records* -- GP name: *SiteCoverage* +- GP name: *Netlogon_SiteCoverage* - GP path: *System\Net Logon\DC Locator DNS Records* - GP ADMX file name: *Netlogon.admx* @@ -2519,7 +2519,7 @@ If you do not configure this policy setting, it is not applied to any computers, ADMX Info: - GP English name: *Specify site name* -- GP name: *SiteName* +- GP name: *Netlogon_SiteName* - GP path: *System\Net Logon* - GP ADMX file name: *Netlogon.admx* @@ -2597,7 +2597,7 @@ If you enable this policy setting, domain administrators should ensure that the ADMX Info: - GP English name: *Set SYSVOL share compatibility* -- GP name: *AllowExclusiveSysvolShareAccess* +- GP name: *Netlogon_SysvolShareCompatibilityMode* - GP path: *System\Net Logon* - GP ADMX file name: *Netlogon.admx* @@ -2672,7 +2672,7 @@ If you do not configure this policy setting, Try Next Closest Site DC Location w ADMX Info: - GP English name: *Try Next Closest Site* -- GP name: *TryNextClosestSite* +- GP name: *Netlogon_TryNextClosestSite* - GP path: *System\Net Logon\DC Locator DNS Records* - GP ADMX file name: *Netlogon.admx* @@ -2745,7 +2745,7 @@ If you do not configure this policy setting, it is not applied to any DCs, and D ADMX Info: - GP English name: *Specify dynamic registration of the DC Locator DNS Records* -- GP name: *UseDynamicDns* +- GP name: *Netlogon_UseDynamicDns* - GP path: *System\Net Logon\DC Locator DNS Records* - GP ADMX file name: *Netlogon.admx* diff --git a/windows/client-management/mdm/policy-csp-admx-offlinefiles.md b/windows/client-management/mdm/policy-csp-admx-offlinefiles.md index 4fcbf3566f..abd5e758fc 100644 --- a/windows/client-management/mdm/policy-csp-admx-offlinefiles.md +++ b/windows/client-management/mdm/policy-csp-admx-offlinefiles.md @@ -228,7 +228,7 @@ If you disable this setting or do not configure it, the system asks users whethe ADMX Info: - GP English name: *Subfolders always available offline* -- GP name: *AlwaysPinSubFolders* +- GP name: *Pol_AlwaysPinSubFolders* - GP path: *Network\Offline Files* - GP ADMX file name: *OfflineFiles.admx* @@ -302,7 +302,7 @@ If you do not configure this policy setting, no files or folders are made availa ADMX Info: - GP English name: *Specify administratively assigned Offline Files* -- GP name: *AssignedOfflineFolders* +- GP name: *Pol_AssignedOfflineFiles_1* - GP path: *Network\Offline Files* - GP ADMX file name: *OfflineFiles.admx* @@ -376,7 +376,7 @@ If you do not configure this policy setting, no files or folders are made availa ADMX Info: - GP English name: *Specify administratively assigned Offline Files* -- GP name: *AssignedOfflineFolders* +- GP name: *Pol_AssignedOfflineFiles_2* - GP path: *Network\Offline Files* - GP ADMX file name: *OfflineFiles.admx* @@ -447,7 +447,7 @@ If you disable or do not configure this policy setting, Windows performs a backg ADMX Info: - GP English name: *Configure Background Sync* -- GP name: *BackgroundSyncEnabled* +- GP name: *Pol_BackgroundSyncSettings* - GP path: *Network\Offline Files* - GP ADMX file name: *OfflineFiles.admx* @@ -528,7 +528,7 @@ This setting replaces the Default Cache Size setting used by pre-Windows Vista s ADMX Info: - GP English name: *Limit disk space used by Offline Files* -- GP name: *CacheQuotaLimitUnpinned* +- GP name: *Pol_CacheSize* - GP path: *Network\Offline Files* - GP ADMX file name: *OfflineFiles.admx* @@ -612,7 +612,7 @@ Also, see the "Non-default server disconnect actions" setting. ADMX Info: - GP English name: *Action on server disconnect* -- GP name: *GoOfflineAction* +- GP name: *Pol_CustomGoOfflineActions_1* - GP path: *Network\Offline Files* - GP ADMX file name: *OfflineFiles.admx* @@ -696,7 +696,7 @@ Also, see the "Non-default server disconnect actions" setting. ADMX Info: - GP English name: *Action on server disconnect* -- GP name: *GoOfflineAction* +- GP name: *Pol_CustomGoOfflineActions_2* - GP path: *Network\Offline Files* - GP ADMX file name: *OfflineFiles.admx* @@ -776,7 +776,7 @@ If you do not configure this setting, disk space for automatically cached files ADMX Info: - GP English name: *Default cache size* -- GP name: *DefCacheSize* +- GP name: *Pol_DefCacheSize* - GP path: *Network\Offline Files* - GP ADMX file name: *OfflineFiles.admx* @@ -850,7 +850,7 @@ If you do not configure this policy setting, Offline Files is enabled on Windows ADMX Info: - GP English name: *Allow or Disallow use of the Offline Files feature* -- GP name: *Enabled* +- GP name: *Pol_Enabled* - GP path: *Network\Offline Files* - GP ADMX file name: *OfflineFiles.admx* @@ -927,7 +927,7 @@ This setting is applied at user logon. If this setting is changed after user log ADMX Info: - GP English name: *Encrypt the Offline Files cache* -- GP name: *EncryptCache* +- GP name: *Pol_EncryptOfflineFiles* - GP path: *Network\Offline Files* - GP ADMX file name: *OfflineFiles.admx* @@ -1007,7 +1007,7 @@ To use this setting, in the "Enter" box, select the number corresponding to the ADMX Info: - GP English name: *Event logging level* -- GP name: *EventLoggingLevel* +- GP name: *Pol_EventLoggingLevel_1* - GP path: *Network\Offline Files* - GP ADMX file name: *OfflineFiles.admx* @@ -1087,7 +1087,7 @@ To use this setting, in the "Enter" box, select the number corresponding to the ADMX Info: - GP English name: *Event logging level* -- GP name: *EventLoggingLevel* +- GP name: *Pol_EventLoggingLevel_2* - GP path: *Network\Offline Files* - GP ADMX file name: *OfflineFiles.admx* @@ -1156,7 +1156,7 @@ If you disable or do not configure this policy setting, a user can create a file ADMX Info: - GP English name: *Enable file screens* -- GP name: *ExcludedFileTypes* +- GP name: *Pol_ExclusionListSettings* - GP path: *Network\Offline Files* - GP ADMX file name: *OfflineFiles.admx* @@ -1230,7 +1230,7 @@ To use this setting, type the file name extension in the "Extensions" box. To ty ADMX Info: - GP English name: *Files not cached* -- GP name: *ExcludeExtensions* +- GP name: *Pol_ExtExclusionList* - GP path: *Network\Offline Files* - GP ADMX file name: *OfflineFiles.admx* @@ -1314,7 +1314,7 @@ Also, see the "Non-default server disconnect actions" setting. ADMX Info: - GP English name: *Action on server disconnect* -- GP name: *GoOfflineAction* +- GP name: *Pol_GoOfflineAction_1* - GP path: *Network\Offline Files* - GP ADMX file name: *OfflineFiles.admx* @@ -1398,7 +1398,7 @@ Also, see the "Non-default server disconnect actions" setting. ADMX Info: - GP English name: *Action on server disconnect* -- GP name: *GoOfflineAction* +- GP name: *Pol_GoOfflineAction_2* - GP path: *Network\Offline Files* - GP ADMX file name: *OfflineFiles.admx* @@ -1472,7 +1472,7 @@ This setting appears in the Computer Configuration and User Configuration folder ADMX Info: - GP English name: *Prevent use of Offline Files folder* -- GP name: *NoCacheViewer* +- GP name: *Pol_NoCacheViewer_1* - GP path: *Network\Offline Files* - GP ADMX file name: *OfflineFiles.admx* @@ -1546,7 +1546,7 @@ This setting appears in the Computer Configuration and User Configuration folder ADMX Info: - GP English name: *Prevent use of Offline Files folder* -- GP name: *NoCacheViewer* +- GP name: *Pol_NoCacheViewer_2* - GP path: *Network\Offline Files* - GP ADMX file name: *OfflineFiles.admx* @@ -1620,7 +1620,7 @@ This setting appears in the Computer Configuration and User Configuration folder ADMX Info: - GP English name: *Prohibit user configuration of Offline Files* -- GP name: *NoConfigCache* +- GP name: *Pol_NoConfigCache_1* - GP path: *Network\Offline Files* - GP ADMX file name: *OfflineFiles.admx* @@ -1694,7 +1694,7 @@ This setting appears in the Computer Configuration and User Configuration folder ADMX Info: - GP English name: *Prohibit user configuration of Offline Files* -- GP name: *NoConfigCache* +- GP name: *Pol_NoConfigCache_2* - GP path: *Network\Offline Files* - GP ADMX file name: *OfflineFiles.admx* @@ -1767,7 +1767,7 @@ If you disable or do not configure this policy setting, users can manually speci ADMX Info: - GP English name: *Remove "Make Available Offline" command* -- GP name: *NoMakeAvailableOffline* +- GP name: *Pol_NoMakeAvailableOffline_1* - GP path: *Network\Offline Files* - GP ADMX file name: *OfflineFiles.admx* @@ -1840,7 +1840,7 @@ If you disable or do not configure this policy setting, users can manually speci ADMX Info: - GP English name: *Remove "Make Available Offline" command* -- GP name: *NoMakeAvailableOffline* +- GP name: *Pol_NoMakeAvailableOffline_2* - GP path: *Network\Offline Files* - GP ADMX file name: *OfflineFiles.admx* @@ -1917,7 +1917,7 @@ If you do not configure this policy setting, the "Make Available Offline" comman ADMX Info: - GP English name: *Remove "Make Available Offline" for these files and folders* -- GP name: *NoMakeAvailableOfflineList* +- GP name: *Pol_NoPinFiles_1* - GP path: *Network\Offline Files* - GP ADMX file name: *OfflineFiles.admx* @@ -1994,7 +1994,7 @@ If you do not configure this policy setting, the "Make Available Offline" comman ADMX Info: - GP English name: *Remove "Make Available Offline" for these files and folders* -- GP name: *NoMakeAvailableOfflineList* +- GP name: *Pol_NoPinFiles_2* - GP path: *Network\Offline Files* - GP ADMX file name: *OfflineFiles.admx* @@ -2074,7 +2074,7 @@ This setting appears in the Computer Configuration and User Configuration folder ADMX Info: - GP English name: *Turn off reminder balloons* -- GP name: *NoReminders* +- GP name: *Pol_NoReminders_1* - GP path: *Network\Offline Files* - GP ADMX file name: *OfflineFiles.admx* @@ -2154,7 +2154,7 @@ This setting appears in the Computer Configuration and User Configuration folder ADMX Info: - GP English name: *Turn off reminder balloons* -- GP name: *NoReminders* +- GP name: *Pol_NoReminders_2* - GP path: *Network\Offline Files* - GP ADMX file name: *OfflineFiles.admx* @@ -2227,7 +2227,7 @@ If you disable or do not configure this policy setting, remote files will be not ADMX Info: - GP English name: *Enable Transparent Caching* -- GP name: *OnlineCachingLatencyThreshold* +- GP name: *Pol_OnlineCachingSettings* - GP path: *Network\Offline Files* - GP ADMX file name: *OfflineFiles.admx* @@ -2298,7 +2298,7 @@ If you disable this setting or do not configure it, the system asks users whethe ADMX Info: - GP English name: *Subfolders always available offline* -- GP name: *AlwaysPinSubFolders* +- GP name: *Pol_AlwaysPinSubFolders* - GP path: *Network\Offline Files* - GP ADMX file name: *OfflineFiles.admx* @@ -2370,7 +2370,7 @@ If you disable this setting or do not configure it, automatically and manually c ADMX Info: - GP English name: *At logoff, delete local copy of user’s offline files* -- GP name: *PurgeOnlyAutoCacheAtLogoff* +- GP name: *Pol_PurgeAtLogoff* - GP path: *Network\Offline Files* - GP ADMX file name: *OfflineFiles.admx* @@ -2439,7 +2439,7 @@ If you disable this policy setting, all administratively assigned folders are sy ADMX Info: - GP English name: *Turn on economical application of administratively assigned Offline Files* -- GP name: *EconomicalAdminPinning* +- GP name: *Pol_QuickAdimPin* - GP path: *Network\Offline Files* - GP ADMX file name: *OfflineFiles.admx* @@ -2513,7 +2513,7 @@ This setting appears in the Computer Configuration and User Configuration folder ADMX Info: - GP English name: *Reminder balloon frequency* -- GP name: *ReminderFreqMinutes* +- GP name: *Pol_ReminderFreq_1* - GP path: *Network\Offline Files* - GP ADMX file name: *OfflineFiles.admx* @@ -2587,7 +2587,7 @@ This setting appears in the Computer Configuration and User Configuration folder ADMX Info: - GP English name: *Reminder balloon frequency* -- GP name: *ReminderFreqMinutes* +- GP name: *Pol_ReminderFreq_2* - GP path: *Network\Offline Files* - GP ADMX file name: *OfflineFiles.admx* @@ -2656,7 +2656,7 @@ This setting appears in the Computer Configuration and User Configuration folder ADMX Info: - GP English name: *Initial reminder balloon lifetime* -- GP name: *InitialBalloonTimeoutSeconds* +- GP name: *Pol_ReminderInitTimeout_1* - GP path: *Network\Offline Files* - GP ADMX file name: *OfflineFiles.admx* @@ -2725,7 +2725,7 @@ This setting appears in the Computer Configuration and User Configuration folder ADMX Info: - GP English name: *Initial reminder balloon lifetime* -- GP name: *InitialBalloonTimeoutSeconds* +- GP name: *Pol_ReminderInitTimeout_2* - GP path: *Network\Offline Files* - GP ADMX file name: *OfflineFiles.admx* @@ -2794,7 +2794,7 @@ This setting appears in the Computer Configuration and User Configuration folder ADMX Info: - GP English name: *Reminder balloon lifetime* -- GP name: *ReminderBalloonTimeoutSeconds* +- GP name: *Pol_ReminderTimeout_1* - GP path: *Network\Offline Files* - GP ADMX file name: *OfflineFiles.admx* @@ -2863,7 +2863,7 @@ This setting appears in the Computer Configuration and User Configuration folder ADMX Info: - GP English name: *Reminder balloon lifetime* -- GP name: *ReminderBalloonTimeoutSeconds* +- GP name: *Pol_ReminderTimeout_2* - GP path: *Network\Offline Files* - GP ADMX file name: *OfflineFiles.admx* @@ -2942,7 +2942,7 @@ If you disable this policy setting, computers will not use the slow-link mode. ADMX Info: - GP English name: *Configure slow-link mode* -- GP name: *SlowLinkEnabled* +- GP name: *Pol_SlowLinkSettings* - GP path: *Network\Offline Files* - GP ADMX file name: *OfflineFiles.admx* @@ -3016,7 +3016,7 @@ If this setting is disabled or not configured, the default threshold value of 64 ADMX Info: - GP English name: *Configure Slow link speed* -- GP name: *SlowLinkSpeed* +- GP name: *Pol_SlowLinkSpeed* - GP path: *Network\Offline Files* - GP ADMX file name: *OfflineFiles.admx* @@ -3094,7 +3094,7 @@ This setting appears in the Computer Configuration and User Configuration folder ADMX Info: - GP English name: *Synchronize all offline files before logging off* -- GP name: *SyncAtLogoff* +- GP name: *Pol_SyncAtLogoff_1* - GP path: *Network\Offline Files* - GP ADMX file name: *OfflineFiles.admx* @@ -3172,7 +3172,7 @@ This setting appears in the Computer Configuration and User Configuration folder ADMX Info: - GP English name: *Synchronize all offline files before logging off* -- GP name: *SyncAtLogoff* +- GP name: *Pol_SyncAtLogoff_2* - GP path: *Network\Offline Files* - GP ADMX file name: *OfflineFiles.admx* @@ -3250,7 +3250,7 @@ This setting appears in the Computer Configuration and User Configuration folder ADMX Info: - GP English name: *Synchronize all offline files when logging on* -- GP name: *SyncAtLogon* +- GP name: *Pol_SyncAtLogon_1* - GP path: *Network\Offline Files* - GP ADMX file name: *OfflineFiles.admx* @@ -3330,7 +3330,7 @@ This setting appears in the Computer Configuration and User Configuration folder ADMX Info: - GP English name: *Synchronize all offline files when logging on* -- GP name: *SyncAtLogon* +- GP name: *Pol_SyncAtLogon_2* - GP path: *Network\Offline Files* - GP ADMX file name: *OfflineFiles.admx* @@ -3402,7 +3402,7 @@ If you disable or do not configuring this setting, files are not synchronized wh ADMX Info: - GP English name: *Synchronize offline files before suspend* -- GP name: *SyncAtSuspend* +- GP name: *Pol_SyncAtSuspend_1* - GP path: *Network\Offline Files* - GP ADMX file name: *OfflineFiles.admx* @@ -3474,7 +3474,7 @@ If you disable or do not configuring this setting, files are not synchronized wh ADMX Info: - GP English name: *Synchronize offline files before suspend* -- GP name: *SyncAtSuspend* +- GP name: *Pol_SyncAtSuspend_2* - GP path: *Network\Offline Files* - GP ADMX file name: *OfflineFiles.admx* @@ -3543,7 +3543,7 @@ If this setting is disabled or not configured, synchronization will not run in t ADMX Info: - GP English name: *Enable file synchronization on costed networks* -- GP name: *SyncEnabledForCostedNetwork* +- GP name: *Pol_SyncOnCostedNetwork* - GP path: *Network\Offline Files* - GP ADMX file name: *OfflineFiles.admx* @@ -3612,7 +3612,7 @@ If you disable or do not configure this policy setting, the "Work offline" comma ADMX Info: - GP English name: *Remove "Work offline" command* -- GP name: *WorkOfflineDisabled* +- GP name: *Pol_WorkOfflineDisabled_1* - GP path: *Network\Offline Files* - GP ADMX file name: *OfflineFiles.admx* @@ -3681,7 +3681,7 @@ If you disable or do not configure this policy setting, the "Work offline" comma ADMX Info: - GP English name: *Remove "Work offline" command* -- GP name: *WorkOfflineDisabled* +- GP name: *Pol_WorkOfflineDisabled_2* - GP path: *Network\Offline Files* - GP ADMX file name: *OfflineFiles.admx* diff --git a/windows/client-management/mdm/policy-csp-admx-peertopeercaching.md b/windows/client-management/mdm/policy-csp-admx-peertopeercaching.md index 2dba3479b2..426fcbe069 100644 --- a/windows/client-management/mdm/policy-csp-admx-peertopeercaching.md +++ b/windows/client-management/mdm/policy-csp-admx-peertopeercaching.md @@ -125,7 +125,7 @@ Select one of the following: ADMX Info: - GP English name: *Turn on BranchCache* -- GP name: *Enable* +- GP name: *EnableWindowsBranchCache* - GP path: *Network\BranchCache* - GP ADMX file name: *PeerToPeerCaching.admx* @@ -203,7 +203,7 @@ Select one of the following: ADMX Info: - GP English name: *Set BranchCache Distributed Cache mode* -- GP name: *Enable* +- GP name: *EnableWindowsBranchCache_Distributed* - GP path: *Network\BranchCache* - GP ADMX file name: *PeerToPeerCaching.admx* @@ -287,7 +287,7 @@ Hosted cache clients must trust the server certificate that is issued to the hos ADMX Info: - GP English name: *Set BranchCache Hosted Cache mode* -- GP name: *Location* +- GP name: *EnableWindowsBranchCache_Hosted* - GP path: *Network\BranchCache* - GP ADMX file name: *PeerToPeerCaching.admx* @@ -374,7 +374,7 @@ Select one of the following: ADMX Info: - GP English name: *Enable Automatic Hosted Cache Discovery by Service Connection Point* -- GP name: *SCPDiscoveryEnabled* +- GP name: *EnableWindowsBranchCache_HostedCacheDiscovery* - GP path: *Network\BranchCache* - GP ADMX file name: *PeerToPeerCaching.admx* @@ -457,7 +457,7 @@ In circumstances where this setting is enabled, you can also select and configur ADMX Info: - GP English name: *Configure Hosted Cache Servers* -- GP name: *MultipleServers* +- GP name: *EnableWindowsBranchCache_HostedMultipleServers* - GP path: *Network\BranchCache* - GP ADMX file name: *PeerToPeerCaching.admx* @@ -534,7 +534,7 @@ In circumstances where this policy setting is enabled, you can also select and c ADMX Info: - GP English name: *Configure BranchCache for network files* -- GP name: *PeerCachingLatencyThreshold* +- GP name: *EnableWindowsBranchCache_SMB* - GP path: *Network\BranchCache* - GP ADMX file name: *PeerToPeerCaching.admx* @@ -618,7 +618,7 @@ In circumstances where this setting is enabled, you can also select and configur ADMX Info: - GP English name: *Set percentage of disk space used for client computer cache* -- GP name: *SizePercent* +- GP name: *SetCachePercent* - GP path: *Network\BranchCache* - GP ADMX file name: *PeerToPeerCaching.admx* @@ -699,7 +699,7 @@ In circumstances where this setting is enabled, you can also select and configur ADMX Info: - GP English name: *Set age for segments in the data cache* -- GP name: *SegmentTTL* +- GP name: *SetDataCacheEntryMaxAge* - GP path: *Network\BranchCache* - GP ADMX file name: *PeerToPeerCaching.admx* @@ -783,7 +783,7 @@ Select from the following versions ADMX Info: - GP English name: *Configure Client BranchCache Version Support* -- GP name: *PreferredContentInformationVersion* +- GP name: *SetDowngrading* - GP path: *Network\BranchCache* - GP ADMX file name: *PeerToPeerCaching.admx* diff --git a/windows/client-management/mdm/policy-csp-admx-performancediagnostics.md b/windows/client-management/mdm/policy-csp-admx-performancediagnostics.md index 7db02bd2e1..f02fb046cc 100644 --- a/windows/client-management/mdm/policy-csp-admx-performancediagnostics.md +++ b/windows/client-management/mdm/policy-csp-admx-performancediagnostics.md @@ -108,7 +108,7 @@ This policy setting will only take effect when the Diagnostic Policy Service is ADMX Info: - GP English name: *Configure Scenario Execution Level* -- GP name: *ScenarioExecutionEnabled* +- GP name: *WdiScenarioExecutionPolicy_1* - GP path: *System\Troubleshooting and Diagnostics\Windows Boot Performance Diagnostics* - GP ADMX file name: *PerformanceDiagnostics.admx* @@ -185,7 +185,7 @@ This policy setting will only take effect when the Diagnostic Policy Service is ADMX Info: - GP English name: *Configure Scenario Execution Level* -- GP name: *ScenarioExecutionEnabled* +- GP name: *WdiScenarioExecutionPolicy_2* - GP path: *System\Troubleshooting and Diagnostics\Windows System Responsiveness Performance Diagnostics* - GP ADMX file name: *PerformanceDiagnostics.admx* @@ -262,7 +262,7 @@ This policy setting will only take effect when the Diagnostic Policy Service is ADMX Info: - GP English name: *Configure Scenario Execution Level* -- GP name: *ScenarioExecutionEnabled* +- GP name: *WdiScenarioExecutionPolicy_3* - GP path: *System\Troubleshooting and Diagnostics\Windows Shutdown Performance Diagnostics* - GP ADMX file name: *PerformanceDiagnostics.admx* @@ -339,7 +339,7 @@ This policy setting will only take effect when the Diagnostic Policy Service is ADMX Info: - GP English name: *Configure Scenario Execution Level* -- GP name: *ScenarioExecutionEnabled* +- GP name: *WdiScenarioExecutionPolicy_4* - GP path: *System\Troubleshooting and Diagnostics\Windows Standby/Resume Performance Diagnostics* - GP ADMX file name: *PerformanceDiagnostics.admx* diff --git a/windows/client-management/mdm/policy-csp-admx-reliability.md b/windows/client-management/mdm/policy-csp-admx-reliability.md index 135c581f83..e466f85f86 100644 --- a/windows/client-management/mdm/policy-csp-admx-reliability.md +++ b/windows/client-management/mdm/policy-csp-admx-reliability.md @@ -105,7 +105,7 @@ If you do not configure this policy setting, the Persistent System Timestamp is ADMX Info: - GP English name: *Enable Persistent Time Stamp* -- GP name: *TimeStampEnabled* +- GP name: *EE_EnablePersistentTimeStamp* - GP path: *System* - GP ADMX file name: *Reliability.admx* @@ -180,7 +180,7 @@ Also see the "Configure Error Reporting" policy setting. ADMX Info: - GP English name: *Report unplanned shutdown events* -- GP name: *IncludeShutdownErrs* +- GP name: *PCH_ReportShutdownEvents* - GP path: *Windows Components\Windows Error Reporting\Advanced Error Reporting Settings* - GP ADMX file name: *Reliability.admx* @@ -258,7 +258,7 @@ If you do not configure this policy setting, the default behavior for the System ADMX Info: - GP English name: *Activate Shutdown Event Tracker System State Data feature* -- GP name: *SnapShot* +- GP name: *ShutdownEventTrackerStateFile* - GP path: *System* - GP ADMX file name: *Reliability.admx* @@ -338,7 +338,7 @@ If you do not configure this policy setting, the default behavior for the Shutdo ADMX Info: - GP English name: *Display Shutdown Event Tracker* -- GP name: *ShutdownReasonOn* +- GP name: *ShutdownReason* - GP path: *System* - GP ADMX file name: *Reliability.admx* diff --git a/windows/client-management/mdm/policy-csp-admx-scripts.md b/windows/client-management/mdm/policy-csp-admx-scripts.md index 3f1912da84..7f655514ef 100644 --- a/windows/client-management/mdm/policy-csp-admx-scripts.md +++ b/windows/client-management/mdm/policy-csp-admx-scripts.md @@ -124,7 +124,7 @@ If you disable or do not configure this policy setting, user account cross-fores ADMX Info: - GP English name: *Allow logon scripts when NetBIOS or WINS is disabled* -- GP name: *Allow-LogonScript-NetbiosDisabled* +- GP name: *Allow_Logon_Script_NetbiosDisabled* - GP path: *System\Scripts* - GP ADMX file name: *Scripts.admx* @@ -199,7 +199,7 @@ If you disable or do not configure this setting the system lets the combined set ADMX Info: - GP English name: *Specify maximum wait time for Group Policy scripts* -- GP name: *MaxGPOScriptWait* +- GP name: *MaxGPOScriptWaitPolicy* - GP path: *System\Scripts* - GP ADMX file name: *Scripts.admx* @@ -291,7 +291,7 @@ Within GPO C: C.cmd, C.ps1 ADMX Info: - GP English name: *Run Windows PowerShell scripts first at computer startup, shutdown* -- GP name: *RunComputerPSScriptsFirst* +- GP name: *Run_Computer_PS_Scripts_First* - GP path: *System\Scripts* - GP ADMX file name: *Scripts.admx* @@ -364,7 +364,7 @@ Also, see the "Run Logon Scripts Visible" setting. ADMX Info: - GP English name: *Run legacy logon scripts hidden* -- GP name: *HideLegacyLogonScripts* +- GP name: *Run_Legacy_Logon_Script_Hidden* - GP path: *System\Scripts* - GP ADMX file name: *Scripts.admx* @@ -435,7 +435,7 @@ If you disable or do not configure this policy setting, the instructions are sup ADMX Info: - GP English name: *Display instructions in logoff scripts as they run* -- GP name: *HideLogoffScripts* +- GP name: *Run_Logoff_Script_Visible* - GP path: *System\Scripts* - GP ADMX file name: *Scripts.admx* @@ -506,7 +506,7 @@ This policy setting appears in the Computer Configuration and User Configuration ADMX Info: - GP English name: *Run logon scripts synchronously* -- GP name: *RunLogonScriptSync* +- GP name: *Run_Logon_Script_Sync_1* - GP path: *System\Scripts* - GP ADMX file name: *Scripts.admx* @@ -577,7 +577,7 @@ This policy setting appears in the Computer Configuration and User Configuration ADMX Info: - GP English name: *Run logon scripts synchronously* -- GP name: *RunLogonScriptSync* +- GP name: *Run_Logon_Script_Sync_2* - GP path: *System\Scripts* - GP ADMX file name: *Scripts.admx* @@ -648,7 +648,7 @@ If you disable or do not configure this policy setting, the instructions are sup ADMX Info: - GP English name: *Display instructions in logon scripts as they run* -- GP name: *HideLogonScripts* +- GP name: *Run_Logon_Script_Visible* - GP path: *System\Scripts* - GP ADMX file name: *Scripts.admx* @@ -719,7 +719,7 @@ If you disable or do not configure this policy setting, the instructions are sup ADMX Info: - GP English name: *Display instructions in shutdown scripts as they run* -- GP name: *HideShutdownScripts* +- GP name: *Run_Shutdown_Script_Visible* - GP path: *System\Scripts* - GP ADMX file name: *Scripts.admx* @@ -793,7 +793,7 @@ If you disable or do not configure this policy setting, a startup cannot run unt ADMX Info: - GP English name: *Run startup scripts asynchronously* -- GP name: *RunStartupScriptSync* +- GP name: *Run_Startup_Script_Sync* - GP path: *System\Scripts* - GP ADMX file name: *Scripts.admx* @@ -867,7 +867,7 @@ If you disable or do not configure this policy setting, the instructions are sup ADMX Info: - GP English name: *Display instructions in startup scripts as they run* -- GP name: *HideStartupScripts* +- GP name: *Run_Startup_Script_Visible* - GP path: *System\Scripts* - GP ADMX file name: *Scripts.admx* @@ -962,7 +962,7 @@ This policy setting appears in the Computer Configuration and User Configuration ADMX Info: - GP English name: *Run Windows PowerShell scripts first at user logon, logoff* -- GP name: *RunUserPSScriptsFirst* +- GP name: *Run_User_PS_Scripts_First* - GP path: *System\Scripts* - GP ADMX file name: *Scripts.admx* diff --git a/windows/client-management/mdm/policy-csp-admx-sdiageng.md b/windows/client-management/mdm/policy-csp-admx-sdiageng.md index b462873456..ce4096ecc5 100644 --- a/windows/client-management/mdm/policy-csp-admx-sdiageng.md +++ b/windows/client-management/mdm/policy-csp-admx-sdiageng.md @@ -97,7 +97,7 @@ If you disable this policy setting, users can only access and search troubleshoo ADMX Info: - GP English name: *Troubleshooting: Allow users to access online troubleshooting content on Microsoft servers from the Troubleshooting Control Panel (via the Windows Online Troubleshooting Service - WOTS)* -- GP name: *EnableQueryRemoteServer* +- GP name: *BetterWhenConnected* - GP path: *System\Troubleshooting and Diagnostics\Scripted Diagnostics* - GP ADMX file name: *sdiageng.admx* @@ -168,7 +168,7 @@ Note that this setting also controls a user's ability to launch standalone troub ADMX Info: - GP English name: *Troubleshooting: Allow users to access and run Troubleshooting Wizards* -- GP name: *EnableDiagnostics* +- GP name: *ScriptedDiagnosticsExecutionPolicy* - GP path: *System\Troubleshooting and Diagnostics\Scripted Diagnostics* - GP ADMX file name: *sdiageng.admx* @@ -237,7 +237,7 @@ If you disable or do not configure this policy setting, the scripted diagnostics ADMX Info: - GP English name: *Configure Security Policy for Scripted Diagnostics* -- GP name: *ValidateTrust* +- GP name: *ScriptedDiagnosticsSecurityPolicy* - GP path: *System\Troubleshooting and Diagnostics\Scripted Diagnostics* - GP ADMX file name: *sdiageng.admx* diff --git a/windows/client-management/mdm/policy-csp-admx-securitycenter.md b/windows/client-management/mdm/policy-csp-admx-securitycenter.md index 482389c9e4..3f963a77cb 100644 --- a/windows/client-management/mdm/policy-csp-admx-securitycenter.md +++ b/windows/client-management/mdm/policy-csp-admx-securitycenter.md @@ -103,7 +103,7 @@ In Windows Vista, this policy setting monitors essential security settings to in ADMX Info: - GP English name: *Turn on Security Center (Domain PCs only)* -- GP name: *SecurityCenterInDomain* +- GP name: *SecurityCenter_SecurityCenterInDomain* - GP path: *Windows Components\Security Center* - GP ADMX file name: *Securitycenter.admx* diff --git a/windows/client-management/mdm/policy-csp-admx-servicing.md b/windows/client-management/mdm/policy-csp-admx-servicing.md index 5fddfc68cc..c18852e5ea 100644 --- a/windows/client-management/mdm/policy-csp-admx-servicing.md +++ b/windows/client-management/mdm/policy-csp-admx-servicing.md @@ -93,7 +93,7 @@ If you disable or do not configure this policy setting, or if the required files ADMX Info: - GP English name: *Specify settings for optional component installation and component repair* -- GP name: *RepairContentServerSource* +- GP name: *Servicing* - GP path: *System* - GP ADMX file name: *Servicing.admx* diff --git a/windows/client-management/mdm/policy-csp-admx-shellcommandpromptregedittools.md b/windows/client-management/mdm/policy-csp-admx-shellcommandpromptregedittools.md index bf58db7cf4..e8df85ad6d 100644 --- a/windows/client-management/mdm/policy-csp-admx-shellcommandpromptregedittools.md +++ b/windows/client-management/mdm/policy-csp-admx-shellcommandpromptregedittools.md @@ -174,7 +174,7 @@ To prevent users from using other administrative tools, use the "Run only specif ADMX Info: - GP English name: *Prevent access to registry editing tools* -- GP name: *DisableRegistryTools* +- GP name: *DisableRegedit* - GP path: *System* - GP ADMX file name: *Shell-CommandPrompt-RegEditTools.admx* @@ -250,7 +250,7 @@ This policy setting only prevents users from running programs that are started b ADMX Info: - GP English name: *Don't run specified Windows applications* -- GP name: *DisallowRun* +- GP name: *DisallowApps* - GP path: *System* - GP ADMX file name: *Shell-CommandPrompt-RegEditTools.admx* @@ -325,7 +325,7 @@ This policy setting only prevents users from running programs that are started b ADMX Info: - GP English name: *Run only specified Windows applications* -- GP name: *RestrictRun* +- GP name: *RestrictApps* - GP path: *System* - GP ADMX file name: *Shell-CommandPrompt-RegEditTools.admx* From d2a1b6c986674e03afaf03b5954ad401d3746b40 Mon Sep 17 00:00:00 2001 From: Gary Moore Date: Mon, 5 Oct 2020 16:18:10 -0700 Subject: [PATCH 54/76] Applied approved abbreviation --- windows/deployment/update/waas-delivery-optimization.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/update/waas-delivery-optimization.md b/windows/deployment/update/waas-delivery-optimization.md index 29f4745c6b..77c469b79d 100644 --- a/windows/deployment/update/waas-delivery-optimization.md +++ b/windows/deployment/update/waas-delivery-optimization.md @@ -112,7 +112,7 @@ In MDM, the same settings are under **.Vendor/MSFT/Policy/Config/DeliveryOptimiz Starting with Microsoft Intune version 1902, you can set many Delivery Optimization policies as a profile, which you can then apply to groups of devices. For more information, see [Delivery Optimization settings in Microsoft Intune](https://docs.microsoft.com/intune/delivery-optimization-windows)) -**Starting with Windows 10, version 1903,** you can use the Azure Active Directory (AAD) Tenant ID as a means to define groups. To do this set the value for DOGroupIdSource to its new maximum value of 5. +**Starting with Windows 10, version 1903,** you can use the Azure Active Directory (Azure AD) Tenant ID as a means to define groups. To do this set the value for DOGroupIdSource to its new maximum value of 5. ## Reference From 0e6c9f074d49f54eb1f0826154b9f6f527ce9409 Mon Sep 17 00:00:00 2001 From: Gary Moore Date: Mon, 5 Oct 2020 16:24:18 -0700 Subject: [PATCH 55/76] Removed unnecessary bold from table headings MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Table headings are bold by default. Adding bold ( or **) results in non-standard font weights—in this case, something that looked like half-weight bold. --- windows/deployment/update/waas-configure-wufb.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/windows/deployment/update/waas-configure-wufb.md b/windows/deployment/update/waas-configure-wufb.md index 7aebbab370..727ec90959 100644 --- a/windows/deployment/update/waas-configure-wufb.md +++ b/windows/deployment/update/waas-configure-wufb.md @@ -48,7 +48,7 @@ With Windows Update for Business, you can set a device to be on either Windows I **Release branch policies** -| Policy | Sets registry key under **HKLM\Software** | +| Policy | Sets registry key under HKLM\Software | | --- | --- | | GPO for Windows 10, version 1607 or later:
Computer Configuration > Administrative Templates > Windows Components > Windows Update > Defer Windows Updates > **Select when Feature Updates are received** | \Policies\Microsoft\Windows\WindowsUpdate\BranchReadinessLevel | | GPO for Windows 10, version 1511:
Computer Configuration > Administrative Templates > Windows Components > Windows Update > **Defer Upgrades and Updates** | \Policies\Microsoft\Windows\WindowsUpdate\DeferUpgrade | @@ -73,7 +73,7 @@ For example, a device on the Semi-Annual Channel with `DeferFeatureUpdatesPeriod

**Policy settings for deferring feature updates** -| Policy | Sets registry key under **HKLM\Software** | +| Policy | Sets registry key under HKLM\Software | | --- | --- | | GPO for Windows 10, version 1607 later:
Computer Configuration > Administrative Templates > Windows Components > Windows Update > Defer Windows Updates > **Select when Feature Updates are received** | \Policies\Microsoft\Windows\WindowsUpdate\DeferFeatureUpdates
\Policies\Microsoft\Windows\WindowsUpdate\DeferFeatureUpdatesPeriodInDays | | GPO for Windows 10, version 1511:
Computer Configuration > Administrative Templates > Windows Components > Windows Update > **Defer Upgrades and Updates** | \Policies\Microsoft\Windows\WindowsUpdate\DeferUpgradePeriod | @@ -97,7 +97,7 @@ In cases where the pause policy is first applied after the configured start date **Policy settings for pausing feature updates** -| Policy | Sets registry key under **HKLM\Software** | +| Policy | Sets registry key under HKLM\Software | | --- | --- | | GPO for Windows 10, version 1607 and later:
Computer Configuration > Administrative Templates > Windows Components > Windows Update > Defer Windows Updates > **Select when Feature Updates are received** | **1607:** \Policies\Microsoft\Windows\WindowsUpdate\PauseFeatureUpdates
**1703 and later:** \Policies\Microsoft\Windows\WindowsUpdate\PauseFeatureUpdatesStartTime | | GPO for Windows 10, version 1511:
Computer Configuration > Administrative Templates > Windows Components > Windows Update > **Defer Upgrades and Updates** | \Policies\Microsoft\Windows\WindowsUpdate\Pause | @@ -134,7 +134,7 @@ You can set your system to receive updates for other Microsoft products—known **Policy settings for deferring quality updates** -| Policy | Sets registry key under **HKLM\Software** | +| Policy | Sets registry key under HKLM\Software | | --- | --- | | GPO for Windows 10, version 1607 and later:
Computer Configuration > Administrative Templates > Windows Components > Windows Update > Defer Windows Updates > **Select when Quality Updates are received** | \Policies\Microsoft\Windows\WindowsUpdate\DeferQualityUpdates
\Policies\Microsoft\Windows\WindowsUpdate\DeferQualityUpdatesPeriodInDays | | GPO for Windows 10, version 1511:
Computer Configuration > Administrative Templates > Windows Components > Windows Update > **Defer Upgrades and Updates** | \Policies\Microsoft\Windows\WindowsUpdate\DeferUpdatePeriod | @@ -157,7 +157,7 @@ In cases where the pause policy is first applied after the configured start date **Policy settings for pausing quality updates** -| Policy | Sets registry key under **HKLM\Software** | +| Policy | Sets registry key under HKLM\Software | | --- | --- | | GPO for Windows 10, version 1607 and later:
Computer Configuration > Administrative Templates > Windows Components > Windows Update > Defer Windows Updates > **Select when Quality Updates are received** |**1607:** \Policies\Microsoft\Windows\WindowsUpdate\PauseQualityUpdates
**1703:** \Policies\Microsoft\Windows\WindowsUpdate\PauseQualityUpdatesStartTime | | GPO for Windows 10, version 1511:
Computer Configuration > Administrative Templates > Windows Components > Windows Update > **Defer Upgrades and Updates** | \Policies\Microsoft\Windows\WindowsUpdate\Pause | @@ -207,7 +207,7 @@ Starting with Windows 10, version 1607, you can selectively opt out of receiving **Policy settings to exclude drivers** -| Policy | Sets registry key under **HKLM\Software** | +| Policy | Sets registry key under HKLM\Software | | --- | --- | | GPO for Windows 10, version 1607 and later:
Computer Configuration > Administrative Templates > Windows Components > Windows Update > **Do not include drivers with Windows Updates** | \Policies\Microsoft\Windows\WindowsUpdate\ExcludeWUDriversInQualityUpdate | | MDM for Windows 10, version 1607 and later:
../Vendor/MSFT/Policy/Config/Update/
**ExcludeWUDriversInQualityUpdate** | \Microsoft\PolicyManager\default\Update\ExcludeWUDriversInQualityUpdate | From 3cc9c7c8794de8dbd002f3f98ab34302e90653ee Mon Sep 17 00:00:00 2001 From: Denise Vangel-MSFT Date: Tue, 6 Oct 2020 09:03:40 -0700 Subject: [PATCH 56/76] Update manage-updates-baselines-microsoft-defender-antivirus.md --- .../manage-updates-baselines-microsoft-defender-antivirus.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md b/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md index 26ec6cd69a..8456e86597 100644 --- a/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md +++ b/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md @@ -75,15 +75,16 @@ All our updates contain: - integration improvements (Cloud, Microsoft 365 Defender)
- September-2020 (Platform: 4.18.2009.7 | Engine: 1.1.17500.4) + September-2020 (Platform: 4.18.2009.x | Engine: 1.1.17500.4)  Security intelligence update version: **1.323.2254.0**  Released: **October 6, 2020** - Platform: **4.18.2009.7** + Platform: **4.18.2009.x**  Engine: **1.1.17500.4**  Support phase: **Security and Critical Updates** ### What's new + - Admin permissions are required to restore files in quarantine - XML formatted events are now supported - CSP support for ignoring exclusion merge From 675e90c75bc6917f15df7383af4abb24723c39d2 Mon Sep 17 00:00:00 2001 From: Shannon Leavitt Date: Tue, 6 Oct 2020 10:37:56 -0600 Subject: [PATCH 57/76] Pencil edit --- ...s-baselines-microsoft-defender-antivirus.md | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md b/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md index 8456e86597..d1cb0e3d28 100644 --- a/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md +++ b/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md @@ -111,15 +111,15 @@ No known issues  Support phase: **Security and Critical Updates** ### What's new -*Admin permissions are required to restore files in quarantine -*XML formatted events are now supported -*CSP support for ignoring exclusion merge -*New management interfaces for: -+UDP Inspection -+Network Protection on Server 2019 -+IP Address exclusions for Network Protection -*Improved visibility into TPM measurements -*Improved Office VBA module scanning +- Admin permissions are required to restore files in quarantine +- XML formatted events are now supported +- CSP support for ignoring exclusion merge +- New management interfaces for: + - UDP Inspection + - Network Protection on Server 2019 + - IP Address exclusions for Network Protection +- Improved visibility into TPM measurements +- Improved Office VBA module scanning ### Known Issues No known issues From 919bd754123d66a41ec0207e99cac043c9daf48e Mon Sep 17 00:00:00 2001 From: Gary Moore Date: Tue, 6 Oct 2020 15:05:42 -0700 Subject: [PATCH 58/76] Applied "> [!NOTE]" --- .../account-lockout-threshold.md | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/windows/security/threat-protection/security-policy-settings/account-lockout-threshold.md b/windows/security/threat-protection/security-policy-settings/account-lockout-threshold.md index 55f3b22031..ab09ef2ca5 100644 --- a/windows/security/threat-protection/security-policy-settings/account-lockout-threshold.md +++ b/windows/security/threat-protection/security-policy-settings/account-lockout-threshold.md @@ -77,8 +77,11 @@ None. Changes to this policy setting become effective without a computer restart ### Implementation considerations Implementation of this policy setting is dependent on your operational environment. You should consider threat vectors, deployed operating systems, and deployed apps, for example: + - The likelihood of an account theft or a DoS attack is based on the security design for your systems and environment. You should set the account lockout threshold in consideration of the known and perceived risk of those threats. + - When negotiating encryption types between clients, servers, and domain controllers, the Kerberos protocol can automatically retry account sign-in attempts that count toward the threshold limits that you set in this policy setting. In environments where different versions of the operating system are deployed, encryption type negotiation increases. + - Not all apps that are used in your environment effectively manage how many times a user can attempt to sign-in. For instance, if a connection drops repeatedly when a user is running the app, all subsequent failed sign-in attempts count toward the account lockout threshold. For more information about Windows security baseline recommendations for account lockout, see [Configuring Account Lockout](https://blogs.technet.microsoft.com/secguide/2014/08/13/configuring-account-lockout/). @@ -95,17 +98,23 @@ This section describes how an attacker might exploit a feature or its configurat Brute force password attacks can use automated methods to try millions of password combinations for any user account. The effectiveness of such attacks can be almost eliminated if you limit the number of failed sign-in attempts that can be performed. However, a DoS attack could be performed on a domain that has an account lockout threshold configured. An attacker could programmatically attempt a series of password attacks against all users in the organization. If the number of attempts is greater than the account lockout threshold, the attacker might be able to lock every account without needing any special privileges or being authenticated in the network. -> **Note:** Offline password attacks are not countered by this policy setting. +> [!NOTE] +> Offline password attacks are not countered by this policy setting. + ### Countermeasure Because vulnerabilities can exist when this value is configured and when it is not configured, two distinct countermeasures are defined. Organizations should weigh the choice between the two, based on their identified threats and the risks that they want to mitigate. The two countermeasure options are: + - Configure the **Account lockout threshold** setting to 0. This configuration ensures that accounts will not be locked, and it will prevent a DoS attack that intentionally attempts to lock accounts. This configuration also helps reduce Help Desk calls because users cannot accidentally lock themselves out of their accounts. Because it does not prevent a brute force attack, this configuration should be chosen only if both of the following criteria are explicitly met: + - The password policy setting requires all users to have complex passwords of 8 or more characters. - A robust audit mechanism is in place to alert administrators when a series of failed sign-ins occur in the environment. + - Configure the **Account lockout threshold** policy setting to a sufficiently high value to provide users with the ability to accidentally mistype their password several times before the account is locked, but ensure that a brute force password attack still locks the account. [Windows security baselines](https://docs.microsoft.com/windows/security/threat-protection/windows-security-baselines) recommend configuring a threshold of 10 invalid sign-in attempts, which prevents accidental account lockouts and reduces the number of Help Desk calls, but does not prevent a DoS attack. + Using this type of policy must be accompanied by a process to unlock locked accounts. It must be possible to implement this policy whenever it is needed to help mitigate massive lockouts caused by an attack on your systems. ### Potential impact From dcbeadfeada3227c4d52dd24ad616f2ed1b5247c Mon Sep 17 00:00:00 2001 From: Gary Moore Date: Tue, 6 Oct 2020 16:54:13 -0700 Subject: [PATCH 59/76] Added image border and spacing --- .../vpn/vpn-conditional-access.md | 22 ++++++++++++++----- 1 file changed, 16 insertions(+), 6 deletions(-) diff --git a/windows/security/identity-protection/vpn/vpn-conditional-access.md b/windows/security/identity-protection/vpn/vpn-conditional-access.md index c368ed6c90..fc09e68a62 100644 --- a/windows/security/identity-protection/vpn/vpn-conditional-access.md +++ b/windows/security/identity-protection/vpn/vpn-conditional-access.md @@ -48,25 +48,29 @@ The following client-side components are also required: - Trusted Platform Module (TPM) ## VPN device compliance + At this time, the Azure AD certificates issued to users do not contain a CRL Distribution Point (CDP) and are not suitable for Key Distribution Centers (KDCs) to issue Kerberos tokens. For users to gain access to on-premises resources such as files on a network share, client authentication certificates must be deployed to the Windows profiles of the users, and their VPNv2 profiles must contain the <SSO> section. Server-side infrastructure requirements to support VPN device compliance include: -- The VPN server should be configured for certificate authentication -- The VPN server should trust the tenant-specific Azure AD CA -- For client access using Kerberos/NTLM, a domain-trusted certificate is deployed to the client device and is configured to be used for single sign-on (SSO) +- The VPN server should be configured for certificate authentication. +- The VPN server should trust the tenant-specific Azure AD CA. +- For client access using Kerberos/NTLM, a domain-trusted certificate is deployed to the client device and is configured to be used for single sign-on (SSO). After the server side is set up, VPN admins can add the policy settings for conditional access to the VPN profile using the VPNv2 DeviceCompliance node. Two client-side configuration service providers are leveraged for VPN device compliance. -- VPNv2 CSP DeviceCompliance settings +- VPNv2 CSP DeviceCompliance settings: + - **Enabled**: enables the Device Compliance flow from the client. If marked as **true**, the VPN client attempts to communicate with Azure AD to get a certificate to use for authentication. The VPN should be set up to use certificate authentication and the VPN server must trust the server returned by Azure AD. - **Sso**: entries under SSO should be used to direct the VPN client to use a certificate other than the VPN authentication certificate when accessing resources that require Kerberos authentication. - **Sso/Enabled**: if this field is set to **true**, the VPN client looks for a separate certificate for Kerberos authentication. - **Sso/IssuerHash**: hashes for the VPN client to look for the correct certificate for Kerberos authentication. - **Sso/Eku**: comma-separated list of Enhanced Key Usage (EKU) extensions for the VPN client to look for the correct certificate for Kerberos authentication. + - HealthAttestation CSP (not a requirement) - functions performed by the HealthAttestation CSP include: + - Collects TPM data used to verify health states - Forwards the data to the Health Attestation Service (HAS) - Provisions the Health Attestation Certificate received from the HAS @@ -76,16 +80,22 @@ Two client-side configuration service providers are leveraged for VPN device com > Currently, it is required that certificates used for obtaining Kerberos tickets must be issued from an on-premises CA, and that SSO must be enabled in the user’s VPN profile. This will enable the user to access on-premises resources. ## Client connection flow + The VPN client side connection flow works as follows: -![Device compliance workflow when VPN client attempts to connect](images/vpn-device-compliance.png) +> [!div class="mx-imgBorder"] +> ![Device compliance workflow when VPN client attempts to connect](images/vpn-device-compliance.png) When a VPNv2 Profile is configured with \ \true<\/Enabled> the VPN client uses this connection flow: 1. The VPN client calls into Windows 10’s Azure AD Token Broker, identifying itself as a VPN client. + 2. The Azure AD Token Broker authenticates to Azure AD and provides it with information about the device trying to connect. The Azure AD Server checks if the device is in compliance with the policies. -3. If compliant, Azure AD requests a short-lived certificate + +3. If compliant, Azure AD requests a short-lived certificate. + 4. Azure AD pushes down a short-lived certificate to the Certificate Store via the Token Broker. The Token Broker then returns control back over to the VPN client for further connection processing. + 5. The VPN client uses the Azure AD-issued certificate to authenticate with the VPN server. ## Configure conditional access From e25ba0b403693a4cc75a650ade5a2cc5d715aabf Mon Sep 17 00:00:00 2001 From: Denise Vangel-MSFT Date: Tue, 6 Oct 2020 18:11:23 -0700 Subject: [PATCH 60/76] m365solution-scenario --- .../manage-atp-post-migration-configuration-manager.md | 4 +++- .../manage-atp-post-migration-group-policy-objects.md | 4 +++- .../manage-atp-post-migration-intune.md | 4 +++- .../manage-atp-post-migration-other-tools.md | 4 +++- .../microsoft-defender-atp/manage-atp-post-migration.md | 4 +++- .../mcafee-to-microsoft-defender-onboard.md | 1 + .../mcafee-to-microsoft-defender-prepare.md | 1 + .../mcafee-to-microsoft-defender-setup.md | 3 ++- .../microsoft-defender-atp/migration-guides.md | 1 + 9 files changed, 20 insertions(+), 6 deletions(-) diff --git a/windows/security/threat-protection/microsoft-defender-atp/manage-atp-post-migration-configuration-manager.md b/windows/security/threat-protection/microsoft-defender-atp/manage-atp-post-migration-configuration-manager.md index 6d04ee080e..c086033e55 100644 --- a/windows/security/threat-protection/microsoft-defender-atp/manage-atp-post-migration-configuration-manager.md +++ b/windows/security/threat-protection/microsoft-defender-atp/manage-atp-post-migration-configuration-manager.md @@ -14,7 +14,9 @@ author: denisebmsft ms.localizationpriority: medium manager: dansimp audience: ITPro -ms.collection: M365-security-compliance +ms.collection: +- M365-security-compliance +- m365solution-scenario ms.topic: article ms.date: 09/22/2020 ms.reviewer: chventou diff --git a/windows/security/threat-protection/microsoft-defender-atp/manage-atp-post-migration-group-policy-objects.md b/windows/security/threat-protection/microsoft-defender-atp/manage-atp-post-migration-group-policy-objects.md index 016d29c822..512edb5f3c 100644 --- a/windows/security/threat-protection/microsoft-defender-atp/manage-atp-post-migration-group-policy-objects.md +++ b/windows/security/threat-protection/microsoft-defender-atp/manage-atp-post-migration-group-policy-objects.md @@ -14,7 +14,9 @@ author: denisebmsft ms.localizationpriority: medium manager: dansimp audience: ITPro -ms.collection: M365-security-compliance +ms.collection: +- M365-security-compliance +- m365solution-scenario ms.topic: article ms.date: 09/22/2020 ms.reviewer: chventou diff --git a/windows/security/threat-protection/microsoft-defender-atp/manage-atp-post-migration-intune.md b/windows/security/threat-protection/microsoft-defender-atp/manage-atp-post-migration-intune.md index eeefc94bfd..eb630aad88 100644 --- a/windows/security/threat-protection/microsoft-defender-atp/manage-atp-post-migration-intune.md +++ b/windows/security/threat-protection/microsoft-defender-atp/manage-atp-post-migration-intune.md @@ -14,7 +14,9 @@ author: denisebmsft ms.localizationpriority: medium manager: dansimp audience: ITPro -ms.collection: M365-security-compliance +ms.collection: +- M365-security-compliance +- m365solution-scenario ms.topic: article ms.date: 09/22/2020 ms.reviewer: chventou diff --git a/windows/security/threat-protection/microsoft-defender-atp/manage-atp-post-migration-other-tools.md b/windows/security/threat-protection/microsoft-defender-atp/manage-atp-post-migration-other-tools.md index 4eb3a79282..111459747f 100644 --- a/windows/security/threat-protection/microsoft-defender-atp/manage-atp-post-migration-other-tools.md +++ b/windows/security/threat-protection/microsoft-defender-atp/manage-atp-post-migration-other-tools.md @@ -14,7 +14,9 @@ author: denisebmsft ms.localizationpriority: medium manager: dansimp audience: ITPro -ms.collection: M365-security-compliance +ms.collection: +- M365-security-compliance +- m365solution-scenario ms.topic: article ms.date: 09/22/2020 ms.reviewer: chventou diff --git a/windows/security/threat-protection/microsoft-defender-atp/manage-atp-post-migration.md b/windows/security/threat-protection/microsoft-defender-atp/manage-atp-post-migration.md index 417f5267d3..246b542364 100644 --- a/windows/security/threat-protection/microsoft-defender-atp/manage-atp-post-migration.md +++ b/windows/security/threat-protection/microsoft-defender-atp/manage-atp-post-migration.md @@ -14,7 +14,9 @@ author: denisebmsft ms.localizationpriority: medium manager: dansimp audience: ITPro -ms.collection: M365-security-compliance +ms.collection: +- M365-security-compliance +- m365solution-scenario ms.topic: conceptual ms.date: 09/22/2020 ms.reviewer: chventou diff --git a/windows/security/threat-protection/microsoft-defender-atp/mcafee-to-microsoft-defender-onboard.md b/windows/security/threat-protection/microsoft-defender-atp/mcafee-to-microsoft-defender-onboard.md index 3422d29ce9..d38a5977e8 100644 --- a/windows/security/threat-protection/microsoft-defender-atp/mcafee-to-microsoft-defender-onboard.md +++ b/windows/security/threat-protection/microsoft-defender-atp/mcafee-to-microsoft-defender-onboard.md @@ -17,6 +17,7 @@ audience: ITPro ms.collection: - M365-security-compliance - m365solution-McAfeemigrate +- m365solution-scenario ms.custom: migrationguides ms.topic: article ms.date: 09/24/2020 diff --git a/windows/security/threat-protection/microsoft-defender-atp/mcafee-to-microsoft-defender-prepare.md b/windows/security/threat-protection/microsoft-defender-atp/mcafee-to-microsoft-defender-prepare.md index a22a3a83d5..fe973d1a59 100644 --- a/windows/security/threat-protection/microsoft-defender-atp/mcafee-to-microsoft-defender-prepare.md +++ b/windows/security/threat-protection/microsoft-defender-atp/mcafee-to-microsoft-defender-prepare.md @@ -17,6 +17,7 @@ audience: ITPro ms.collection: - M365-security-compliance - m365solution-mcafeemigrate +- m365solution-scenario ms.topic: article ms.custom: migrationguides ms.date: 09/22/2020 diff --git a/windows/security/threat-protection/microsoft-defender-atp/mcafee-to-microsoft-defender-setup.md b/windows/security/threat-protection/microsoft-defender-atp/mcafee-to-microsoft-defender-setup.md index 7e0da8d519..8813e53523 100644 --- a/windows/security/threat-protection/microsoft-defender-atp/mcafee-to-microsoft-defender-setup.md +++ b/windows/security/threat-protection/microsoft-defender-atp/mcafee-to-microsoft-defender-setup.md @@ -16,7 +16,8 @@ manager: dansimp audience: ITPro ms.collection: - M365-security-compliance -- m365solution-mcafeemigrate +- m365solution-mcafeemigrate +- m365solution-scenario ms.topic: article ms.custom: migrationguides ms.date: 09/22/2020 diff --git a/windows/security/threat-protection/microsoft-defender-atp/migration-guides.md b/windows/security/threat-protection/microsoft-defender-atp/migration-guides.md index 193a2a1360..308308a4d0 100644 --- a/windows/security/threat-protection/microsoft-defender-atp/migration-guides.md +++ b/windows/security/threat-protection/microsoft-defender-atp/migration-guides.md @@ -11,6 +11,7 @@ ms.prod: w10 ms.localizationpriority: medium ms.collection: - M365-security-compliance +- m365solution-scenario ms.custom: migrationguides ms.reviewer: chriggs, depicker, yongrhee f1.keywords: NOCSH From 45967fe5b7eb7b85f088b21f92259a6db5bb402a Mon Sep 17 00:00:00 2001 From: Denise Vangel-MSFT Date: Tue, 6 Oct 2020 18:14:02 -0700 Subject: [PATCH 61/76] m365solution-scenario --- .../onboarding-endpoint-configuration-manager.md | 3 ++- .../microsoft-defender-atp/onboarding-endpoint-manager.md | 3 ++- .../threat-protection/microsoft-defender-atp/onboarding.md | 3 ++- .../microsoft-defender-atp/prepare-deployment.md | 3 ++- .../microsoft-defender-atp/production-deployment.md | 3 ++- 5 files changed, 10 insertions(+), 5 deletions(-) diff --git a/windows/security/threat-protection/microsoft-defender-atp/onboarding-endpoint-configuration-manager.md b/windows/security/threat-protection/microsoft-defender-atp/onboarding-endpoint-configuration-manager.md index d839dabec7..c09d936fcd 100644 --- a/windows/security/threat-protection/microsoft-defender-atp/onboarding-endpoint-configuration-manager.md +++ b/windows/security/threat-protection/microsoft-defender-atp/onboarding-endpoint-configuration-manager.md @@ -14,7 +14,8 @@ manager: dansimp audience: ITPro ms.collection: - M365-security-compliance -- m365solution-endpointprotect +- m365solution-endpointprotect +- m365solution-scenario ms.topic: article --- diff --git a/windows/security/threat-protection/microsoft-defender-atp/onboarding-endpoint-manager.md b/windows/security/threat-protection/microsoft-defender-atp/onboarding-endpoint-manager.md index 31593b47cc..76f2c2c7e7 100644 --- a/windows/security/threat-protection/microsoft-defender-atp/onboarding-endpoint-manager.md +++ b/windows/security/threat-protection/microsoft-defender-atp/onboarding-endpoint-manager.md @@ -14,7 +14,8 @@ manager: dansimp audience: ITPro ms.collection: - M365-security-compliance -- m365solution-endpointprotect +- m365solution-endpointprotect +- m365solution-scenario ms.topic: article --- diff --git a/windows/security/threat-protection/microsoft-defender-atp/onboarding.md b/windows/security/threat-protection/microsoft-defender-atp/onboarding.md index feeca610db..6ac048cf9d 100644 --- a/windows/security/threat-protection/microsoft-defender-atp/onboarding.md +++ b/windows/security/threat-protection/microsoft-defender-atp/onboarding.md @@ -14,7 +14,8 @@ manager: dansimp audience: ITPro ms.collection: - M365-security-compliance -- m365solution-endpointprotect +- m365solution-endpointprotect +- m365solution-scenario ms.topic: article --- diff --git a/windows/security/threat-protection/microsoft-defender-atp/prepare-deployment.md b/windows/security/threat-protection/microsoft-defender-atp/prepare-deployment.md index 1217b7de99..9e4e98ffb5 100644 --- a/windows/security/threat-protection/microsoft-defender-atp/prepare-deployment.md +++ b/windows/security/threat-protection/microsoft-defender-atp/prepare-deployment.md @@ -15,7 +15,8 @@ manager: dansimp audience: ITPro ms.collection: - M365-security-compliance -- m365solution-endpointprotect +- m365solution-endpointprotect +- m365solution-scenario ms.topic: article --- diff --git a/windows/security/threat-protection/microsoft-defender-atp/production-deployment.md b/windows/security/threat-protection/microsoft-defender-atp/production-deployment.md index 6e8ce89f59..4a974f0e24 100644 --- a/windows/security/threat-protection/microsoft-defender-atp/production-deployment.md +++ b/windows/security/threat-protection/microsoft-defender-atp/production-deployment.md @@ -15,7 +15,8 @@ manager: dansimp audience: ITPro ms.collection: - M365-security-compliance -- m365solution-endpointprotect +- m365solution-endpointprotect +- m365solution-scenario ms.topic: article --- From a58d7d00f1351e174404c6f38853505fb11386a0 Mon Sep 17 00:00:00 2001 From: schmurky Date: Wed, 7 Oct 2020 19:48:46 +0800 Subject: [PATCH 62/76] Update passive --- .../microsoft-defender-antivirus-compatibility.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/security/threat-protection/microsoft-defender-antivirus/microsoft-defender-antivirus-compatibility.md b/windows/security/threat-protection/microsoft-defender-antivirus/microsoft-defender-antivirus-compatibility.md index 74c6ee2735..be374197ff 100644 --- a/windows/security/threat-protection/microsoft-defender-antivirus/microsoft-defender-antivirus-compatibility.md +++ b/windows/security/threat-protection/microsoft-defender-antivirus/microsoft-defender-antivirus-compatibility.md @@ -77,7 +77,7 @@ The following table summarizes the functionality and features that are available |Automatic disabled mode |No |Yes |No |No |No | - In Active mode, Microsoft Defender Antivirus is used as the antivirus app on the machine. All configuration made with Configuration Manager, Group Policy, Intune, or other management products will apply. Files are scanned and threats remediated, and detection information are reported in your configuration tool (such as Configuration Manager or the Microsoft Defender Antivirus app on the machine itself). -- In Passive mode, Microsoft Defender Antivirus is not used as the antivirus app, and threats are not remediated by Microsoft Defender Antivirus. Files are scanned and reports are provided for threat detections which are shared with the Microsoft Defender ATP service. +- In Passive mode, Microsoft Defender Antivirus is not used as the antivirus app, and threats are not remediated by Microsoft Defender Antivirus. Files are scanned and reports are provided for threat detections which are shared with the Microsoft Defender ATP service. Therefore, you might encounter alerts in the Security Center console with Microsoft Defender Antivirus as a source, even when Microsoft Defender Antivirus is in Passive mode. - When [EDR in block mode](../microsoft-defender-atp/edr-in-block-mode.md) (currently in private preview) is turned on, Microsoft Defender Antivirus is not used as the primary antivirus solution, but can still detect and remediate malicious items. - In Automatic disabled mode, Microsoft Defender Antivirus is not used as the antivirus app. Files are not scanned and threats are not remediated. From 9021c8114720e4caa426776c5cc45b68dbd798ef Mon Sep 17 00:00:00 2001 From: VARADHARAJAN K <3296790+RAJU2529@users.noreply.github.com> Date: Wed, 7 Oct 2020 19:42:32 +0530 Subject: [PATCH 63/76] removed invalid path , added correct path while reading this article, i found an invalid registry path, so I removed the path and added the correct path and added a screenshot. --- .../microsoft-defender-atp/enable-network-protection.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/windows/security/threat-protection/microsoft-defender-atp/enable-network-protection.md b/windows/security/threat-protection/microsoft-defender-atp/enable-network-protection.md index a6090f9ae7..2d96393904 100644 --- a/windows/security/threat-protection/microsoft-defender-atp/enable-network-protection.md +++ b/windows/security/threat-protection/microsoft-defender-atp/enable-network-protection.md @@ -33,12 +33,14 @@ Check if network protection has been enabled on a local device by using Registry 1. Select the **Start** button in the task bar and type **regedit** to open Registry editor 1. Choose **HKEY_LOCAL_MACHINE** from the side menu -1. Navigate through the nested menus to **SOFTWARE** > **Policies** > **Microsoft** > **Windows Defender** > **Policy Manager** +1. Navigate through the nested menus to **SOFTWARE** > **Policies** > **Microsoft** > **Windows Defender** > **Windows Defender Exploit Guard** > **Network Protection** 1. Select **EnableNetworkProtection** to see the current state of network protection on the device * 0, or **Off** * 1, or **On** * 2, or **Audit** mode + + ![networkprotection](https://user-images.githubusercontent.com/3296790/95341270-b738b280-08d3-11eb-84a0-16abb140c9fd.PNG) ## Enable network protection @@ -107,7 +109,7 @@ Confirm network protection is enabled on a local computer by using Registry edit 1. Select **Start** and type **regedit** to open **Registry Editor**. -2. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows Defender\Windows Defender Exploit Guard\Network Protection +2. Navigate to **HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows Defender\Windows Defender Exploit Guard\Network Protection** 3. Select **EnableNetworkProtection** and confirm the value: * 0=Off From f6be1fd70afde097ac197fce2eaeaadded20ce8a Mon Sep 17 00:00:00 2001 From: Denise Vangel-MSFT Date: Wed, 7 Oct 2020 10:53:22 -0700 Subject: [PATCH 64/76] Update manage-updates-baselines-microsoft-defender-antivirus.md --- ...-baselines-microsoft-defender-antivirus.md | 29 ++----------------- 1 file changed, 2 insertions(+), 27 deletions(-) diff --git a/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md b/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md index d1cb0e3d28..69288217fe 100644 --- a/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md +++ b/windows/security/threat-protection/microsoft-defender-antivirus/manage-updates-baselines-microsoft-defender-antivirus.md @@ -74,39 +74,14 @@ All our updates contain: - serviceability improvements - integration improvements (Cloud, Microsoft 365 Defender)
-
- September-2020 (Platform: 4.18.2009.x | Engine: 1.1.17500.4) - - Security intelligence update version: **1.323.2254.0** - Released: **October 6, 2020** - Platform: **4.18.2009.x** - Engine: **1.1.17500.4** - Support phase: **Security and Critical Updates** - -### What's new - -- Admin permissions are required to restore files in quarantine -- XML formatted events are now supported -- CSP support for ignoring exclusion merge -- New management interfaces for:
- - UDP Inspection - - Network Protection on Server 2019 - - IP Address exclusions for Network Protection -- Improved visibility into TPM measurements -- Improved Office VBA module scanning - -### Known Issues -No known issues -
-
- September-2020 (Platform: 4.18.2009.X | Engine: 1.1.17500.4) + September-2020 (Platform: 4.18.2009.7 | Engine: 1.1.17500.4)  Security intelligence update version: **1.325.10.0**  Released: **October 01, 2020** - Platform: **4.18.2009.X** + Platform: **4.18.2009.7**  Engine: **1.1.17500.4**  Support phase: **Security and Critical Updates** From 69b918851e2664befcaf0155b5a43b0a75d41336 Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Wed, 7 Oct 2020 15:29:34 -0700 Subject: [PATCH 65/76] new procedure for drivers --- windows/deployment/upgrade/quick-fixes.md | 61 ++++++++++++++++++++++- 1 file changed, 60 insertions(+), 1 deletion(-) diff --git a/windows/deployment/upgrade/quick-fixes.md b/windows/deployment/upgrade/quick-fixes.md index fa2817f19b..c4a602aacd 100644 --- a/windows/deployment/upgrade/quick-fixes.md +++ b/windows/deployment/upgrade/quick-fixes.md @@ -38,6 +38,7 @@ The Microsoft Virtual Agent provided by [Microsoft Support](https://support.micr
  • Check the system drive for errors and attempt repairs. More information.
  • Run the Windows Update troubleshooter. More information.
  • Attempt to restore and repair system files. More information.
    • +
  • Check for unsigned drivers and update or uninstall them. More information.
  • Update Windows so that all available recommended updates are installed, and ensure the computer is rebooted if this is necessary to complete installation of an update. More information.
  • Temporarily uninstall non-Microsoft antivirus software. More information.
    • @@ -152,9 +153,67 @@ To check and repair system files: ``` > [!NOTE] - > It may take several minutes for the command operations to be completed. For more information, see [Repair a Windows Image](https://msdn.microsoft.com/windows/hardware/commercialize/manufacture/desktop/repair-a-windows-image). + > It may take several minutes for the command operations to be completed. For more information, see [Repair a Windows Image](https://msdn.microsoft.com/windows/hardware/commercialize/manufacture/desktop/repair-a-windows-image) and [Use the System File Checker tool](https://support.microsoft.com/help/929833/use-the-system-file-checker-tool-to-repair-missing-or-corrupted-system). +### Remove unsigned drivers + +Drivers that are not properly signed can block the upgrade process. To check your system for unsigned drivers: + +1. Click **Start**. +2. Type **command**. +3. Right-click **Command Prompt** and then left-click **Run as administrator**. +4. If you are prompted by UAC, click **Yes**. +5. Type **sigverif** and press ENTER. +6. The File Signature Verification tool will open. Click **Start**. +7. After the scanning process is complete, click **Advanced**, and then click **View Log**. +8. Locate drivers in the log file that are unsigned and remove or update them using Device Manager. For more information, see [Using Device Manager to uninstall devices and driver packages](https://docs.microsoft.com/windows-hardware/drivers/install/using-device-manager-to-uninstall-devices-and-driver-packages). + +>[!NOTE] +>If a file is corrupted, it might display as unsigned. Be sure to [repair the system drive](#repair-the-system-drive) and [repair system files](#repair-system-files) before attempting to replace unsigned drivers. + +#### Optional: Use sigcheck + +[Sigcheck](https://docs.microsoft.com/sysinternals/downloads/sigcheck) is a tool that you can download and use to review digital signature details of a file. + +To use sigcheck: + +1. Download [sigcheck.zip](https://download.sysinternals.com/files/Sigcheck.zip) and extract the tool to a directory on your computer, for example: **C:\sigcheck**. +2. Click **Start**. +2. Type **command**. +3. Right-click **Command Prompt** and then left-click **Run as administrator**. +4. If you are prompted by UAC, click **Yes**. +5. In the command window, use the **cd** command to switch to the directory where you extracted sigcheck, for example **cd c:\sigcheck**. +6. Next, generate a list of drivers using driverquery.exe. To do this, type **driverquery /v > c:\sigcheck\drivers.txt** and press ENTER. See the following example: + + ```cmd + C:\Sigcheck>Driverquery /v > C:\sigcheck\drivers.txt + + ``` +7. Open the drivers.txt file and locate the problem driver that was reported by sigverif in the procedure above. Copy the path to the driver. +8. To check the driver, type **sigcheck64 -u -e \** and press ENTER. See the following example: + + ``` + C:\Sigcheck>sigcheck64.exe -i c:\windows\system32\DolbyMATEnc.dll + + Sigcheck v2.80 - File version and signature viewer + Copyright (C) 2004-2020 Mark Russinovich + Sysinternals - www.sysinternals.com + + c:\windows\system32\DolbyMATEnc.dll: + Verified: Unsigned + Link date: 6:43 PM 9/20/2028 + Publisher: n/a + Company: Microsoft Corporation + Description: Dolby MAT Encoder DLL + Product: Microsoft« Windows« Operating System + Prod version: 10.0.18362.1 + File version: 10.0.18362.1 (WinBuild.160101.0800) + MachineType: 64-bit + + ``` +In addition to unsigned drivers, drivers might be signed with an invalid certificate, requring the driver to be updated or removed so that Windows upgrade can continue. + ### Update Windows You should ensure that all important updates are installed before attempting to upgrade. This includes updates to hardware drivers on your computer. From a979898513556b30d2ff01c437794b1307fc117c Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Wed, 7 Oct 2020 15:41:27 -0700 Subject: [PATCH 66/76] typo and add graphic --- windows/deployment/images/sigverif.png | Bin 0 -> 38498 bytes windows/deployment/upgrade/quick-fixes.md | 9 ++++++--- 2 files changed, 6 insertions(+), 3 deletions(-) create mode 100644 windows/deployment/images/sigverif.png diff --git a/windows/deployment/images/sigverif.png b/windows/deployment/images/sigverif.png new file mode 100644 index 0000000000000000000000000000000000000000..0ed0c2fd0c452ba73af39bdfa1ef0494fee155c8 GIT binary patch literal 38498 zcmc%xdpy(qA3u(Frj$d8a+*WYkxS(;hpik^$+1G_P$;nwbDB9^m7Hy)oJ~l$9F{Pa zQ$b$sh*`&HXx^V_z)$R3Vwy+dhD1y z<6iT*ymu2X?lJB{(miftE1YRy1qqeQ?cuY{D|(2^h|NQhAtp&jBw$r|AR~m<)4bv- z7O*ks${T#n-yG$ye{kKLbQRsG=dXh!b;J@#|E9tDRvy^HO*4IXSs5U zbhp|U=~Rt*jm>e5J)7N8YZ`wBHk}x>scF5B>21j|44v#!1f*HhcV9gGD_p|=?ph&# zgUAp63Fg!J*9A8fH|jJi*7I5!G{m`F)hZ?AqAr!PUprKM34A%-(7CZ~bC$SSu}~7l zE%|fr@SE>Y_pK_Q!-!m7!SRk=7hk*)1lk=zrehb4gh}vaA<3N;)^z2AjjkS-9b`<3k=H$=MH3B z1G)k;*RQ>_Yb<+`-T8+`y?>SAovYU~%l#z(+!ECtWnD}6xcz!>34-siA7h;y+X0+v3b zI&hbIIt%ISm3txhmH#CrLc{bZpEnw{8p59&HQb;?t@{BYS)54L*yu)1RMEy9Yg2s- zLt!Pr%SSe$CpRR~GKKO1@{OcN!znXOki23&C-{w0l!sn$vC_AcY4Hb6PFL6=E$qBl zL0I|AZLAFf%V1;0kH6B^%C+ZTTdN%9p8c~r(5bP)dE3>KPKOEmKE^o3I<)yQd=x!j zb8U>|_4{>?S|*8n_@l54n$8PX z{<7qe;o&Wif<|4LwX0GakrIzpA z4(B6lLQ=#l%O?wBuDdH`>Q%@$_WuRnr}gjHr$Q(M=x0sC;a&9_H2U^x|D;AuqkkA; zr+oJYU0GHfC?EON5F!H^Z=gpT_5SY(=&dKzcNh-BGu}t8n~f9`jPgRtz~znoO8wRP z$)^5(dwn?{uAUtDJ)z&%&8_`S-28&sNZ5R(Joh2ad1kN@VAeR0W{sb_;2|S&r=VeE zr>oWzgvE*f?~A@^@Samw9_#=06ZgFs>Bsv%R1A`wX&6!QUH-7cK{#=I*LTs_&o@fp zg0=sd;xK!AKJS_9>TX_Ga|3f{y$)VIh({7zU6{cNn8jc!C=IM_dJWeeNG!2t|DTKI z8|XVh>qPzgX+tIE6xlE02)z=)|<=g*x}E=VEH%mQ8-ZhS@!<{{3+fL zF#jW;zm^}hD$O5voz{qmr+~1*Wi%{G+`HI%r$!XBcrBYh3Smy;P;ewcI+UCLV=1%u# z+?rPQkDC95{3*UzD15~;YQ=L|=nxI$J-qVRVxpM>3VtR-A)hYjFnSw!M89QhCnw9m zw3Ox$??16AU~p{z>etPr|HgGufWUb$`@C4|YGP}tY{$IQM$?@Zrn`CRSZ~QQ8IhX> z9TBQl65gGQ$4ejl7jc6&0ph>%H@$doP^%x?E7wZ_$G0$^wKOiRwhq5XEjHo}s7%@Z zCrAc(!6lyj+5BHR5fgyxJscYr@6LGQKCSW5tNNti3KJZ?F!-SN(#aqHOCkmMaHVy~ z<4EhWJ)X$S`v2k>67qpDe^wR+wB|d7oDmH3d`vLn{qT%3a|Z=jhLjWshwdomIaxgb zMb4alH^<>mwCOYxY5n?3hObx{jKRhW`WAV%LPA7bMDk<#L_VkXCK$Up-2f@*kZ?;b zEu0;9a+jMHGh*gG|CP^8AXTm=WPcNod~v-ve-{`2Y>2Eu-`vbk8l)1(yG)c4gH~bn@Uv#L667F^g}XZjZN6MiUr(os z{Q(M(2O>SzWX>hiszOSMa<|?Zm)`rJi;&y59BzQJ#Z~E&^D0 zz{_vRKHU6QP&u9D@P8Shfp~b8UFRW#9}&@th9^!+C?DuDGC(wCT7&Ut_X5@$G(S?( zr=Xz!8wFZ1@)VK$!b>jX%)sfR1YENAF}=_pf1}d!iyF^{CWX#na>acQeR9uo6=^be z-^p-L?{>+7RQX96jcQtH-M+$fw5LJznXne;#8ITC!5cM$sCTbOmL)FDZ-f|r&XoCK zyhDc-XrRuW1&o+sHwRS>=B`C)4-L0*cK#`6{yApp)6g#$kXCl3N zZO9Eg`Qv#{*s+r?!nSe{x-6LmwJ>rfyT+GJTrSI=G$81MD$Mq2RTYz5xEn9umo$MO zWbMjH7@qFEo=Xc0Xzq(zWH-N8jZ%ooCBNhZBXV)U%aQ+94&T+)BLc9I&-9QgnhN)1 zz|p0JiUu=}vNErHve|uq)~_?a3emKlM9bk;O0eOy@8BpsRsW@-UwVYSj6ihpPoK)V z@|k~2)0PxBrt1o+=1t$*Z^H6G{Ice0a;oG>QM#(T|Ew3nXIn^1l0&btcwKSiC>7)C4epe6_gd^slGb?Fn(m; z^3is2)ti?+4z!!e6ORo%l{}6t{zpOeN)DZJxU@v1ZUr@^zMBP)eh>2dxWLvydor@^ zp-&y6;64F8Yln=Ql|HR~4J(6hu$>tz&m0pb4gRIDKOdiN;Cka9mTjs3{_$Be!Wc=E zhy0Zwr*U!sKOVBVIyF}{emI)@qM@t00-;dQGO@-WlE-mC+-4d5D#}xQCK1hYtk)P= zXB9_2octpND2Oid_1c4tGW^J1Eo2j{!R+OX+9)`gW?PWXuX?ulE4HfjG61F1~+%o)UqqDJzvnN2xFB+fh7@Pezj682UtM&9PF5K{HY5jyW?(STN z@AT5D^MoC=3Z15A7`1kVju_|C(Q0zRRS^a0?#nV`xkIh9YiPn@Oav|x0t-j=qVUK{ zgFk7$@Eq?hs2j!HK@lxvj)b?Il6Abz&zUh>Elt<%#qg`I4$J57o~^z3a`|n?811^) zd=69SR5E5`U~R<4P=U9RY?d4KoTn>F0`m;6GG16SG+R5ExzYxs3|KM0OxV&;K_9#L zZ!IxbST#UY$Q3ED(X`dq(b;Bls*g|-HviKv1}#n8TVe9+NDpr$_ir+2tAH5Yq ziHQEk!iXtI%l%gh4Agc1Ya&9O9$EiKcjg;@zWR^q|MdU(|I>q!IpW?)f2?u<%DQy# zZ)=9zwomJiN0Yu-p!(a3PV6`_@W+5VZF`pe+wZ1`yt4lH%I%Wge+;Jj-$oXHI)L5( zf4|vWLVbS3%KQ&?KLAx@N}laPj%3fZxy?#6MV%(kPmPVle*SL07|r0$&-K#siJqYw zYEyu6jOPh!O_JX8HUwS*wKZe@Ife~`E#m{0&_86OOj$a=#{yToSKAuv z#r#a#XY*x74Vof2n`3Q-1Ys`(e;!0coR1RkWvKSaR+VAas(5K7OQS9NA@V-RT;q@s zkJ;pWY4S?|CpP39iKv<9Nqdh~D31^>sTvEio}Y_zK@L^3@dauqw^FQEms-W zl0m4J76Z%?#5%~uy{m+gL*S7J_I$OrnQ_hDSzcBsAB({>MSuw$sDU1RGrutuZ4aF_ zkS@a(us-Xe6frMd+OinK*_0XX_cb!GIaYz~$q{b~`2rtZhuaeesq1^l`b{h`5(k#c zKM#HvZZ*mMJlqC0*T;;Q|A96(Dz&6qY~`-bRiifiJyDQ2vu(VsO@HHa-c)T+w~%A` z(W;ZATCv;CH>!%NfZs4GpaG*@)LOCeFlSzMofwWAnnAAPI|y~zRKd_+rr=^EV7SjI z;$m*DK4!3;p~h(9WILRm^7wIz#abAS^zmEd=T-*f-H1~C0yIMs;o+i;e2E$7g{ABk zHRYW{b>(&S_vw zxe($)JbA8oiz;&&m93pTjgepI=8@J_V$@d*)D9rd&;mrrCvpdcBJY&~{hfn)&(pVM zpi9o7!2Qs)#V;@eHBUn0LZp*3-};6Nrw#febpMwQt?R7HA&prydjLpiP4CysGOuFa zQO}%O*J8F1%JEoTa=4HFnf%0KljREmgkRzCjR(AR*`p+bFc3p9uc~_-AV`n=Z~j7} zaK4in0ELh7V%+l#QLR5SVx!lrsVysqP(gj8Oh(e!gfpeosW z%IW{~{D?SX#_;>A0$zJrepHW7(p%F+hcaFE{Z92Ct0JN6JE6S0EjsDsciNlhT#I0_ z&>_816^#3WZV7(%BkO59;khfSn)_8hvZ5RI_vu^#U;vCeGt44y62{w4?8;)3fZcWZ z%9rn{+3<1Uv|v;vG*f{y-mLvDf&ioIE*N0YiH94O@4TnIKQeGUDS^zKmBhs>lYgV18Sh@dQ$KH|AQM65Unlr zDTM_b`Ga0734RJfZ(bG9>;GbBb#NvZ;u_`7&||=@4A8wWv>ra54(AZ@dz5dV`szjf zMZX_XMa~U%N&gqOA~t9;A`LGF$S{1v{yn2gHo&F($!93XcB|BKx=F4dAb`%ssJpK7 zms-~f-Y#6){LXL~$X~lisRAxINb{h1|7I1t|NEi*wDa_lQee|&0F%vDZf^?FN1Z3j z8-fu;`?o=a8}x>sbq0k5%6r1$dvj?n^g(xsL4G&cKXDQc9yc6FWC*oo%W5U-q1R){ zw%!4t@7bKxg5Now*ZP2Bm54vGnPt8CEjelj8lGg`^`2Ss^_~JKd^|rb7P<%{aq%wr zaeqy6Jc-v0gkZ6=zUC(|FW)v1&cmdMZ3~R1P%)pX z^DcCSl_RgIWQT}ud=XWrIO;xc3&h#H)+Bil-X?1Ped{iPhIR4+=B3v*Ib(KGfS6A+ zZGKMnQ*mdm14v;OEmM>Q#En>Pd`ZL!ju;S(&#B)WA(x9a*P!b7FmK^L0cd6Ph&SXn zi`R+qgYtRypw(sg4DG3Ku0&BX3^EeVJT1z0c#qKhZXOG)if>*33q}Tt1xXvS&-9 zos#QbOYA`M@#Du%-O@LL9dH@XwHi~XIz(qz|*=kKaKvPK&^6FGn(5Gx_5i?8}a6L8cxt0x;IR%)9beE%kWXj8Tth9-t<+d zO(}RES+X!A)F8vSAaXxBoZloRSW}9=%BFG@e|~cW!h3d<+uY*!B{n9Kr2*O%E(fD> z{fZ$Qg$M2cWSpl#6U)c>!JIY~XEG&{8cb-<3gSR5K|+TBuQz+G`IeYLx`h#hF{!r% z%wsTdY`p@*dIZMU(6e?l9}%%p!Q%JU{`cFso^pE4pN5WR%EWCAQilsj!Z*^mG1~2(9pUW-E}h) z$ryCd3U2yX&SdS?)d_CY(jG>8vgS#zv{*I@+-aUYPfYocS5A*t_cEvd_`=D z>FVCppbn&mI@3vpRY0~}&-eF>kLdtAfRmH`lZ_W)>pyz|rDm9?OZG;*vDM}3TpH0z zdQWOb9^Xbc+(|8el#Q9B;`W)LOdrsfwMyuLAE%%->qo4bB0n_+Pxk1Uk=dP`=)b_6 zP(Zt%rGcL7Ke*}lKGZDE$KMMmdKcycqOQ~73jJd;I)CE%-F1Seafh~Q98pmnylH(k zs@f{5i@xSX_`rR?CriI(t_%hq1I`CAFn1NE&QvW2M#xj{!jcEj@G)5M&hK+UrS>0YmGZylrFtaUUgr%8H$rL@)btVg zV)L22N$)B#jY~|}w8CTU(C2N5J{6eLbYcZ!Zdfh<=^=MxP(-L9Hd00e=@Q%2@s_&6 z=qC|==2w;=oO$`tfb|ATgI3ZU{huZB;Dpxul`b-atFM}rVdc|9ua}S;w*Tf3ZB=8j^kb~gaE&fm z_>|)`gjbe_u^^GPW?$#t<_zG7213u0gJOZWsp{pR>%axQ+1whkk3l`8Q>Zq9JOc-_ z8wduivW)$?dgSd0)VZ8@FicaK-cB>S8>_Z|Y zY*9LRy(<8y0ZJNuI1+q^tkruGntz+q&_NoB5S9Aw{?eZ>{w|DI@Fx6r}?*`bROH_S{%d12eP9H*j>LvRnr$39+(aEh_ zb6^3wodwm7)UbO?h>R?2By*vKjnSs>FdxjKoF;ySzvi^pjUncO1ZpM_s)MaU%PN~U z%CDIX-EI^G@cmOu*#6W**6ETH z10jOe+sLAm@kF4pIPgkzqEUp9b?M20=qB~8QH{ziiP*=i*S$NiDb->u>WqfnTcDo; z)h@MsRAPOK`M4({G}M*cGkUU|aVeOa?MIy&jgvB3i*zz0G@do{vTPhFu7b*esCy02 zI=}QhkSl~tfaAXt7t{tgi|EE4?XJ45=rQ+x^{IVK$sPRlkf+MABNoM;K|Ya4A0+g z=UN2v>Km6`GiD=j>cZ~^*D%V|jpDoM9u%HlOTQy^r}D<7rR+&|3t#SY zm{KQG3XLVrkk7ODU#4jIfH|OyLJsUcb(0oJ2%_Unh2g;8$Q5-`-dJ0`dl>z}V!7=8 zAy-&a)cTc}@+*1b1M$nbW?NgJecvY?ee}pQ0$ifFK0<#H- z`_!?mn@U3^j9m6_@q4rMVD37EX#f^UsJDrws8R9iV^R>P!e3vA=l2Cgp7B)hBRow8 zqFSiuiHJ5bo8tDy^>`kg3>}56_qhMab|su|mhzlpI_I!+8J2%;yL@=9pmjY8w2{o` z@k3YhsXTyK)J_wG8YnCO%7WTv@Qk^>TU8g%!1Lw$XxPT%VGSH$entG_=)17?-2QAm zYyxDW4(XlOx>+CDwDgQWiHFE_ID%3(2S5qUya?l5*eC~#!m-v;0THVdK8MeqFX3;B z0XFA3yW^v{`TV6Z4L-wFebg^s^44Dg;5rLk#cpV};&^(}FEoAGmwhsR?I)+t>I4 z54vHIb;-sre9m`0dM4Pvxu4y#towIm3HfzBS@O1=%cy^>y<*9`u z3`fr?pFFT&y=WjnX@YjKphZ~;1AgUp>bdH-l88=M6CbndxZ&8J#T%|foIwnhQ=@CN z59TYE11sN<+Z~rrcMLo_F#Y5K(2t&5drLu!ZiGvPG9~MKo;Le_MbS6 zF|XxsR?NW<;^<-C72&it<>d`T-}09FliTd0k(#U0)O1oNlw{Q~AsDvHU50 zu~F_yy+VtMM8JVEm*!E>Ny~l9H$!3?G;VuLY3je1&oE7GX&616v}pCWil6qxpWqHs0mfU@;^K8d+gPKl|pO{5dH58eCfhg~SaF6W<1KQ_HtW~y!` zUsLL%#s%iP_nub9ocdVSd=PrYmvAc{xsWneO(;axVSDpD!oKvbvFr*q`QUJdPHS;E zJ*1^be^Ao9VBh6AdT_Jz9cbh|D0RwV$kgySn0R6!14R9uplu9?QR7N?mr?F=n0vFJ z2~;674bzje!w6f8@VgD0Q<%YH8XXeF7u~E&F~Y&6#?RLYwaXT@H)J(SBjU>I)w&ER5KUINCvX6ks% zbu;kPB{%o$Y~@;(TIaG>zWPAF`z7@e zbbz3STt}IaJINHkx;T(`4E`pXGeUo`unOV1Rf2rUZxA!rT&3*HZj?|qxYI}wx0gp9DaWaItsu`$+Uw8{ZBY~7I_7gIPrXHx6d+@hvwjlrDHm!>IYtQx>lTW3 zG|4t{F13BWZhp6Gbm6qJ+K%kv3ZyI7aKQOhvQB@<9->hh`{r}(t}c3~;~I6A>+qqE zmKTrNH@nQ{-wdC}|1GmV(^7ChjLJb54btj|r_@`gW^xZNS9kJvok5dn^wLr8`AxCz zz9t^0!;~=xs`6LM6<_o(uy&Q86o?jB`q!P$8-h!R)tx^OKd3#SyQu!00j}6fteqQ=ExqtCxL?Ms~r)Qb*2opK4X=J0}{S z>^Py+Q(1LcVmM_=m8h5;D=DVg5!f^U2bl+&Ok`V^$a^=V1Ud%Vu^zzRF-?d{eP|?% zlMt}PgIW-5^hBheDJSB1z(YDB^@nOZ8W2#*4(^5e9`Dc;{pd^@z+SoU4Fwl={xhXm zr2unr_o6p^nXDd;m8{oHwSVdEr?VZU-JvO@)d}~x^5_usN)<<`QR=Mc4kvE+0w8Kt zAs-bvJkw_y)`QPwZ9b_FPsyN>q8%}@jhN^Z*=I%(ri+FHPaRayujZ~n0Z(Qld=TJW zxXD^Dz39N>oL1Izgbi4A%&~dtEB8;IDW?7UH@*3s>Q+_R>GWxn9u-Y2xxLYuD6e(K?REQ-c!hH4NThPgh-o6r+U!HJR zBHTIIry!K7uKD-8Z}M)7*L{}nDsbYo0qxY4@FbNI_vVof6K`_gPz(nWDK+7g5mHd| z&`h7+vK~u^fKCidxci?rk_RWnArkCq0^1}a$ofvI=(1w(<4*4ZEq|nDtx}7G5>_E- zc>UDSkd%oNEH4>i(S6A`Rpc%qqP8x7=w)V+gM4)G>6q*F1_1=cugZ0CN?kbh#9HNZ z`W+xESlOuCgjT`_-#XKWDlyaE15PI0_flQz8qbsrqh9A?D@CvC4>ZMYZ7bleZsoyh zLHqUh%%X&v%M#zUMHdFAai#;=%_kPU`xr$Uw4y6yCmHqvmOab35RYsUX4>2|aa8)} zsR`7@M0@CP&(T7%(ci|epe=Q#cA6~`7O&1`|IFSW@-4GN&jrRKC09Dd!3ZHAE$hP{ z{duO>R)uc$m0PTM?i5^li5g*NVheGZ)J|5?2%r=q&62p{bV2iWXeusE*StMf#=Y`x zh5NZYkH*Wwm49`y6~vw5%k#V@w0G+DdwG)=sGe@4rcV)IGut1EIIA*Ge>LK3#+Ov#|C z%Si}*&J9qzE-Cx9WAv?Ojzt4zN!roDDwaN}x0WE1ig=rnCpoX-hbiG1qpHMHU#L?4 zgTNu3$Ag+L9cBGYBB4#GA(_oAW?ZW5@u4ZLrWLkE%NO~rO`8ePtz--9j%D72AUaJY zyR`PM1W){h4iJZw*F5mKw9Af?GAvm{3ZRlS+e_I_X_GPt1XNA$2v_}+YPWK=QX?Ar zZa?msI0D3hG_XK#ifGV5 zZ>sUuPSLP}q~QF*P=V;1JnxrOs@TWNH~m*~u|;;Y6Xfzzx5Slm+*L(VB1K2>J=LzZ zwfXc&VbSwkw_Y8^I`z*_9n9Ms5~}I9k|4<(mC-^GEd9(ri8V~ShnvK`{Q(2oNqmJ({Iq9zYC(?havp@S;AYv(SO$i3ES$8}t- zQmWHbWvY@oJqv@6Fg_(krv23R#dSgrxwsK-v$IOas&TxaZRw2IGCx7FVaG|TE#Fpj z2NXw#s%g0tSdxG8)4z&bJC5Jqd)b*)GD7e40xx1+223CeL!=O8a`caNoO3Ze4wQZm zF5_qO`ewCO-GRNnJ}j|?xE99#3ZLf{5uI=Ai-M>%I<(Rgc@Vn*8`$7TCaWS+=UV*48+85{nxu0)SPPL;& zu97y6v}(|mK9o`0b?a}4`bbmH^cg2LnN=YLoA zD1GijE@(?VoV^@-9a@Xs++!@yX?pd9!gaX;n=Z0DW`}n}(~X|jTsU2qEQ5kXy!1rD zrS(K~+UvgrCNnfAd@5B*%4IhwDgrJh2X=SZT_1<6Yk}KKflmi)f2Z>L--1-05j+0R znZ%yU`~4NzN<_4|&!NeKO6}!w{#Se_URMTG*esR-a4C~YQ<}v3Bkil+`!C*M`)ak@ z7w&r`AF|*>>ob$=+OMe)4Rn(MC@(fT95{wWUh;+N3-;YKlZncCzN}8zwMg!e!N1Hs zCP=En`tXKT(Qmn?ddG(FkO*)3#tFicFBNo0!vM5ZU%L*|0D8eu);0%5js5AZzN{4n zd8WG9yy)Zd*(jKPXQrUc@ zdrj()t9PG?<9ZoVf2;HVL!q^FvBMtimtL9L9&i0}VE?CK3J?8YU{&`u)>Kw(q4%8p zr(wK-(F2%?%aBCKRjoE;O^15-sgK69G-tG7!X3x`x3LejPGWpex}HmvCN1&rLka=P z*t*J3vYPa3o0*ZUrHpS);tx07q_^rMXsb?sFYrB=EZpVe(;adfndc=un<;i1Tm2&T zn3#k+)vU2vic#7pj5CE4PT961$<>_)^uJy7(B>%Br<+wKmv3`NCq5d`(%kd(N=bOi zXCVH8yWF>#ac`XEgwdOvBW8gyLk2E0_rEda;=dPH`MfgXaT@**SWkfUqE4jShJyE% zNA2RjY_MlNHMeKU2T)N>asFxdGk#sgy2~vxle2v& z@%-Vr3U&a%#zc$!&vk@v(kF4le3Kz=@!9eBgwGo{)5hVCE$d+un_>u8@><{BSjY8) zB@j@k*l!l4Z5e{M#%J9i#d;n?yN)`vBnEsbJ5usK#RCH!9Zr3Hn+;5OI}_S|p-L;e zKKF~CxckYHgU&NI3wH`vU&ajjr+LU5yGUGJ9+p#jYpe3^hj$-xWO`bxn*8jTm5qlM zUU8Q_rBBSZbufM7qA={TH$y#e>1_5Dyc2ct(w0UD{aO8|$sb;g{g;@YWiETM^qWtN z-x^mOkJ*o6YTjQYT=1}mI>k{OX6o~%Z|ZFOm7M*cB+g(+3GZA1o23c7!6itZ;hlO67Y1a@`$e&=ds=)FDRz<`yPI*Jt!FtL0MkZk?w0FiMc&FM#Yls{< z(|7I9sS2IFg2MSzVJ784oS!t~Vh5I+LLnhrI!hC3OkTQnV}{}^Qf>%r-re5#6z!9j zEsvPsme^+%{E32N(AxNWIJ2_ll}r{+wLgL0?6>$3cj{}UYGLQEuNZj7aA%f7NrP$X z1LuNCIFk=ZdUZPN?<<(Z|>uJ;D`8`y*e_T1% z)aC5uDC9M0teo_akAl({&vMAMbS5Lf!)lqG;#I&aZy(D5D<0hgXW&pWbDdWtc>uZv^rXe>?JnF>8EN~}D!G$bcgy@s=m7>=|`T+e;e+MNTO>h?E<>>UV3OBbe81b`Ow#|;N8PdveAN5QE!Y3 z>%d)swf#N{Xt5ti&AHzi$=NOl^~T>+V`kz0tG?s86hqP0G3z05XL(}+F-It?gy3XPG;0VjP-=gkRqLCa=2@v6D#{B9Vn595bZ3SWhwr2#odgQ5r@mm!g(}5pNtj+P* zf2-Se0l&Y6lq!8vB~}8MFZ}e05=xCJZp5;ULUp=QV;RP$YcenZHs+IqDxs>yc`^0)!M<9a$` z)Y~|-4&y-JYMaGlQBfSRMTOr6Sg=d#Dsjj=m2#}_y=-2<@(NNZMzSP0d7p_k{sFxy zt<_9#=u}7CDg4#klH38~M=Dd*(_;RZvlrtG!NUHvb*jsKQhjo66NY5G#hoI%g_V@@ z2H~eERCRKZAT2~c+G!%?rpzHly}i|m!I--5_@#8Qe>G)F(1NFqDR?JSrHoki)-mT(Gfs>7MgTv&RkYG5o@x9kgc9IGWVU< z`7(Dwe62_8RK4O*DmgNJd|10Ix#dG%58MxAZXt{r7(q z{5h*&j&n8VA_s8sjD(iOtF*roJMF4{H9HiWOP9Ivl?ER5@v!74oo8oaw2vL389PmW zJJL>~DU#yiZvhJbVdj0`eS7>bDfr!6vhD(@8&dtIUByg!fTAI5;~%x6hG0k1w64F} z>XMhioV7~3RrNnfAF`G7J^BMu#xd@mdUT^W7-G;~v8^sS(^^w~EoGAA3y&B7d8|Le zeh4;Q-!M3*$-mr2<;Zkaa*PY@&pA`hCImWOx6Nf!32QH}7`w1FJU?bmh3|h(@h&1v z>Ub}T9sB2qSRVxxmEf2`i4zFtmWaFjZg#}9+U+Rf!*N5wcahU@A7k$#UlmWdAKn4^ ziR1B71jMYm$xH0$U?Yb{_FRgQhsZj1^70K&Kd7k2y;Up7VveA{=XeGrwF! zi?y{OV&r>p-}2!u{Q<%E1zM&_qCaB9_3Oaf)_VO@`PAv6WMM(u1pmcwNGxRl2WE~e zPFwjGjhHy@y78J6@NFfN0wi~sXlq>t(~nse4s(^-oD=NFE8^b9+$mQ?0F)_(ac8}i za8mf{6gOv;W4c4|k{|Tz)x8q&$gpI2UV+KKNoTMn<~zaLZ(}KjiX}0bD??hwe(tfU_83N1)oIH7ymJg zY{A~}O^%=cDs?p(J9kA$+#y*Nm!1|Z%NVbKNffab%w6wP^|J09=uU3zD<2*v1FlW{ zk+)uBfxJ~4kN7b&Kg0dh9Px^ug7z=UN<7JBy8zA!5+E3TT&Uo4CS9wx5-oKAo#^=HH_8+f4#iM@{0C`u)w#4ly*b+R@kvp>QX6U-SKs_gEy| z06cG$3z0zkF*}*Jd>__RbW-}Kfkd6h$mxk-M&i=t0RuN5KeunWpY=@i+TUM2S2$&e z1r13x-ht?wKT4m#8RFmXl;=qqcQh0Kgnw?QApBk&>+82xz80{P#iBl$>aRms^6e6JJXT)9-r$ z(slZItBjai&gY}H22494aat)mbNBnMn#90~FxTi?#~l}Cn#H>E#xFxWupO#hj%pI_ z)B1fRAXP#9uKc376R|#6R@T(9NVpVxrrPi2bWDqElyyQ_Cd ztvi%+^5~^~So*u0Rz|&ls!~pj0F$@ImHM6PgOG1Y;Uiw8YPq~inGp{ULgW789&}gJ zo59}GbMsE@DLhbS3U*shN7X_`@MorgmkvEhCE2_&4KT#iVkg&;TG0+%g^Y`~hJ_eq zMzwh`@qkT-(Gz=`MT}w036um)+`U}Zu9kbt5!xqlZHgyy&|Q-^Z*(RNkl-shvEfnZBFiwj`l6{M4kr1$Fgb=Kp^EvSJ+X z{3=5^Lfkmz>9F6y17kiC0Z?9ppW|*|VPZg{a^(X`rEL1s&MLRK1;xHNDv>E8EB;fi zF7Fpjwe4VRi|{FL$7V&_e`s;1Dv=5Q#8+NDJuc=YEAffDCZ>FiP_zhE9|HQ`fo2Lv zwZt82K*m`fdWgHfK1lnOF1B@WOFZCrSLKQqoTZbW*&e5Hg?FZxV?XF*WbT)L6ag=+TSC^f>ghWTT(thD}CR7znaJAS&5An_fce` zt^|-a)rm^pATE5E4(W-=Qei6CXt*oXsR#H(#vkDv2`BR(pe7qt60Yo=i2eU)@#5yJ z8&4Qlup_>yHeH<1Sw!b_sN}CJH@QouE=Q($Vsva)vZX2yc$w;tEB0s=zG)vKoM9_{ z(Gt2X>XaFzb9?vsiSt)6W@+~sA&)I3*pAUnT!)I?z{^e~Iy|$#2peRHI-Bp_ldM~7 znyX^JF791MI}6xq=9yb5(5OG4+$d50pgvdJy~cr_+X?N4AjF}<)l;_MLg7lR5_X6P zKSUL$m9hLWBf_b^`n^2u*fG0(84hV4DMP6mL4x;+eKW-)9x`x-nG5V}m_;HQpPiZ* zROnh*N!k5lkp%FbtfuRYi=a^u6n*-CY)SgAuG(lIg=TX>Br+3(~`#4DBq>D6>P z&Rqef%nh6FKEjQtz=P0SnY4>$`X+ky_tZm5>sRLm(+qzgw&TFZj@Vn=M`4SxgU5}0 zV7E?Dn-HsSE3$BET?XUR)x-Vn5f+&4!9K7bY8}vp4`5-0My)W?0;TvUTDK3j?W8(0 zW#)F_rIDBEE!P470OfZ3-7+SlMN1YhiZwo!<7#Cq-I8S5Nt`3R;ov0eQjWYkXb)6 zb>^Foy(3?(h@PQ8uwWeD6#KrKQ}DX6P3fJ6(m{wtB`zUHa`LO zqvJT_r>qjPhydmN`U7#)n2F0tE5`^_9TS%u5P_;o7^7h~tFe)@x=_Fl!AtWa?m)MP zeHfqJ2P+$i>T#!PpLLeUAuqr$2in{!GbQZClC-)k*X|7joyq>*5hi%+jWLs)Y0~Tn zbv2)?pG`r(oO|YlVc8JkyQ!uNr&!>e|afI|YP>2H`k6qw8b%bvxvoH(&7%f9SQ%cw=2laVv zvGwhB)}RC87;96ZRhy8-d9e~gVrx-bP>c+y68f;@f zaLyRn7b8gq4QX9VMt)|>Ml$wz1d1GPdtj`mbq(-t+6I5ip@>kpy|1>^y|RVC0nNY$ z7W|WkT`yNWgXi>Nc1BeESY$ZdqjVT$-x#J8q-zP3`NV(<^J#>pT^GP^@@e<3S0cSa z@~9x1aW`nz*g%wcyQ+7p7cjua`Je|om}hRMzz9_bK7H!|FXav*T&s=(n(TB$HaB77 zw8h+KORF@Bs|r}E`<5NiTt5SI9{eVY#{jst-O;TFqg_-!*>8IO^db-C^Tj(t#g^AM zx*0aqd=;0RDq0V;9~fqp=b*ub@DDvIjG9{hw1yoeCz9Ra$iM?u8#Ok-)~c?ms?%CQ zBd7qL8kIb;wzZSmJZZcuM4(81U&_vi*)oBCV#)^;KWeFZ`AWcQq3yDn(ti>5OTkyV8RmfA=sGmtsa=|ZVjYR-gZk^*~g3j2}Z=(^p zvWtV@n+&0ep3u2SUXGR-@nZ)t7OKDC5D*Cqch4IkbEmn2Q+aAsbE`(uXPh)$4{_Em zg8-kZySg^%;6m#OE5|!y;F#8MD$+DK6e-1{!CqvaXC;2w%^=YyikzZ=YHPZ`-?2Lu z>+TKOeB3@3d#H~%-ZY3=JOe!JmP9{6QzbaRianw%?^Ce1mUS_w6n*D-*YWI9$0%{; zksGhI15(V15Lx$g(m+5BTw8Felw`FgwZ5T>DV66Q3_6fcubzyVKA1}}YD{jUNWpq7 zE6uf81=KN3fD|scyg6GM;J8U7`UQjL^|d`;?39jaI^W)Z?LR^#RYCr9pPO!AVy94K+Z8lMFP*Gg zL-l6r`C(dvkUMACt?OYA^Jvp`5^sXeOIJYh>jj~ALDgaZ8-3|-!^a$VHCzqs4w{V> zH4TUjUsC!YVOV18hivH}{{ude<-h7GQNiWRYE;NxHTs1Z2Q$e<(K@=) zH|_N3Z2bY1$(`OA$ztUrVpg9)wb$R+G_IzUPjj_B-w;RjIGKQuxuyKaH7}y(5jHmG zbJeB*QPT>BLfS55)*U7cb?*(*kL-6P;ZY#+#`yMmtC{|YMqX3`I=C_srs3h`06lpF zO9(B$+`}M4ZX3EHSYkK5HPi1BV<_uAzY7&sfVD1i^bF99Jo!716_uAiRKmMauY?`Q)U9 z#StVa@(?%R*#=ba^+Ozg9UEy>A&%s&0V+d6;+d|26}|C;9t4*0%oplju^y~yu%Id0TV z#u%${uucKAav)HFbedImp5c6A08iItw}1pEZV7^~!U{LC5=BUrL`tF)e>}nh4fw65 zTE}!v96tk@*Er!j#wlF&_N#AhJue~@{|L@gk#-x2m*HI&J*;(QGQnWV=kQnY-Xl4C z@6L@UVS7%pEglpF8^p$YB~5~66thcfw2bcrDRdNyx&v9TKm)D=8G0rx>I;hIoUKpd zjNGg3cC71|X6k9rT6a5gjpO~hg`NqdbWAgjNs1l3CK@B(v{*2?+#h?-oz^x`4Y;t# za7H7RGavTW`}vQ^0zOn?3E+hS#FE@YC;9?Abbd_zU+PSA^OY4|Rjk)SopTWj4l#Az z4atU6)glOD#=8ZyUJdo1H)sK649voswX2#z{Ci_i60U+>rJ`EkB&Ok41GtZ%osX>yNk#^F8bDdHTl|I?X3qGPG@TP4?& zdUof2d_OTf+Rww_n#WgG@n;vA?s#0Ria1z1HGA1NViGvVn*pHtg}8X^;PS z?i;yfQkD+FeHvASX9W7H5I&RhUOF|gk=P@ivi(qnsR3__$A1fDU6Xv<_tCr-CWM6&fmIVJ23};!EI)=M)a82 ze3{8gYTW2`G#XZq44?NX+X1S6KY&reyk`tgkw~&(eBD_Fw@GGG_w~Ibjrnw@ytnp259-Yoq4m0O9&UX;EUGSLkoT-sw;P)K zg+H2IIQO|FY-BmF;VU-A8P*}^@j|10ieqjn$^ryK~@xLn5vA^AohZQ7* zNN~H&jkT+pv^`z=%s z6FVK_{*>2mde&OzizzepRmbL`^!XT9UMShH$5y2dCKmR|va1Z?!?hKiiykNn@oM|w z7pUPFOVZ5!DQ&GziLqb7(=j=|j2-eM9NQr+K}(H#RRT$w?^X}}tC^tKao{xwo2Z0f zg6yyTEtj7`%x=b{`;(J&0@5wg&;KMf{IeA1TRvA``R0R&V$%2ch$|H=F#v^uZJ2?T z9_U5t7#0aD5Mi8$%PP7s@4!rZ)EVt zhj+Q|-45O8+tw2uEYNiIqe6MZ?u8^IQDY9#Tv>i6bJ|USs+^>Px!lHM3Xg^q@_JYB z)t>P8bPeRsUMZ+L>UD$|>-G4$&RJ=e7Ti;`fcW1pA<`N5ui5Q*`?4-3hE$nEU4Evw zXG_;uNvfWR2G`k9AbK{~#4FfjsPG16?04@pRer1J^w44-Mhgd6eQM~G#OrN`AkHPr zn$y&6)KN*VL*ubP1NF#QjkD-d4A`Ng@O?1n{%^%opS00dahEqHgi})L6KP_~`X7qy z>e4V~$vOG>Vycr#Q#fiv=-tGlaHr?0YcBf_c_5#>5oFNdgq&HuMBNO`?%z8}7CD2c z(-*|O9rv^qA!o{Vi4)|WO8B;^{ir5}LbHTO0dupxoDxk~l$ab4-~tQRF%Cx7O+G}d z<0JDXB>~QysGI-lKc1_fp+2}b{|qJJ%}LD0+x66+dxMX}9kWQS&?`TIq?*Z{;c4kH zsG848Vbn=#+NDpGz05k;1NrAkJhWtr9;zN zk)^#71NE9t;{wAuy>91{A9W_l>JYfqx?vAAy!g1P#HhRX51P;CpRVq_FkS1FKvC(k z5I-AyestQ*4KP5JiY7BiXEb3D#Sw2|UrpX`Jqq&fDLo2zbf zwI5)~viZTC%-caPcdb=NdZfz;%e8jd(*r4TD|5IHri3&VuCv!7+-rcF`TXN>L|Ia{ zJ^A987x8(F>J4HSdq_J>joco*aLjk|5~*0Ze_!lIn@{&HbgW~rf`yWX9;5PrrEM7Y zg5K>LWRfgD;+-vd@}4|+!yW_EgC}qmJMJqCv1F3uz>oP(YRl@lUD+^WV0g)}SgGhH z;Q)#DkY5S~n+6sR7O*qwPhIIi2?`STD-J$BFkZDAo!&z@JRw7IG)c6SN@R+tFpt|+ zTak|Bj78>wP!kSU5nuNw4xhoYkN*xy!DQ`rw4r-t;>w;G#%0a9RP-)7A!5;(rNl|n ze$G4W29b~RN;b&WkE=KailUovcz;lMerZ-1gi)JUmkQf$cXY#_<8br& zc4@^btX#V?JiKKacv`jF!x$uKbbsh+zekA*8-Q1n?-0O~PBlqnwlh`lqZ?099X{hK zR+Sln1l#KP z=^s0j*e^j;;3#o;TJ%Y}=#GKK<8R%>KdU*~fN#*yqJ#})k7+JJf(njKb@P=)Te#_d{j;Wis0}k4Q}(t&|52Do#+Ag>^Blf97LyH%c>Z%!rn!^P zk80NiIkJ=TitEE`Ce5w=Y(U(u>LVz0J30)1^K0EhcA74-=K9YSPXIOHL9DCh<@z%< zu`#6blfBroKjcW8Na-5uvrqB{e#WsSf4#MsQj`y*vtnNy-UrI~bIxygMyPA2HK?ytvxUbivAePt?OP z4aYMH;cZjZ+_M-1AJG{0LFTvsYp&mTk&o@rer`yWWIAMw^yW+m@ofZJ8|v@RGDNQ9 zo(lSZ{?G~BOznhSP(%KaqkL`gKa-#@pxahlqO$hl?;G_#TKYv-{qyse<@jY~wbFKw zcR1_>{Ogy`P>DcTe(rDu5Uo!J~v!Wr4jUEac zv$0DBVSI4U>d!EIm`W96jYx7EX?c|D1nCN9FATA}#<4n3${8!>bgq@mFL1a`Xffpn zKNf??Qv$l;;m_=!G&Hc!l0ZXS|}-uPKxZ9uI)j(^AJ^7x3K2$$RlY<~hh^Z;8rH~f-U96A(&uKU_5 zQ*c;v%~erl@v(Axz~@s>{g3N-95VO-e8~n9P8>CdXRYV z@xynBWb91_!m{m6m~AGmF|%hDx~y%SA<3X5OTulbeerIoo`Vr!f|GAok`4_( z14vtJ&o112m=9G8nRrbMGY($$M@O|xY_Pv7w40x|`wMpKbgxUz{1s?YGj*c;h0K`! z_3flq(01L(ex?v6yW@tUiOX#K-+mO|oV4Tfsv#Vd;6AjZYdZVz)%tJEIX{_Rj}3Qz}kl1>kk9c4yK=;EFB#oL~|yGk8Vcm zu$fAh4&|FdO6TMrx>7JmLJT>SS5WcCq5xxi_qk2; zv^x@=R7Yd|M4+VT@fV*tnfXpiG7~GCuEqmF4fj}$qh_!;b3rNO0jBEN=S>}|Bhj+> z)Es4T^PGcH7?7=bN{T(J50Yogmu^kGgT$d~%>bwe>FXnxyvY6zD^t5zuZEM0AX*F% znBwP1Ab#F&da!D;7t}+zif*@>a!S(>#Z4r!l<_aOui*Y^MB2RR7`I+{BpzxL@;&H? zcT+;eZD6KVT~g66YQEOF?lAu#ZZD6&{o=9K$hMalPhBY6QNWtM#IwKfQEQs3G}gm7 z92Dl=&9&2(g(wmEtSY)EneLekecVmOcnb(r8(J~g>+ISdHX5n&Q3}=c3Kdwu_VGq^ zM!dDc4wzj{@t4xJNQbl+D5Nlayv3?T&3txcJ1BgZ28+vhU0Hwj600`G^YrXUsrTgV zWi61mT|X1r5&g^=;>oL-`?S<6ZiC7+$`$I`@xM2%d=7H7*QDYu9^nQ1~{F z>l57rhmu%TkwHK^gq@iX&%Q)?{0U)y9~L1U)!af*&5<@wudnI3Nq&kq9^&Ys)y+i& z3&3V=O`%j?{EsSfD?A7llzSd^zML7J(gzYhN%d{>oq0OX)K1WQ%8j=wkV>{nAITOd z-W=lc;eAcdM5@II4~*uH058C>W&pCa0?b=)Q3{jF3bF4^{EiWgU{#3EyvDeSz!iQj#FO~+MwiLuM52JMJ=}k;EJ^u=*T*l) z6^I=&-Nm2i*Iak-1Ql;}F?|RB9HOwFa33inB&}G1`SxZjyz!!m4AWqCHfqU}9U*Fy zgim9C3U{`RGBF&YRO0Rm@v*+-RhmW56p9v^{1k}FhP_`t93JTma4W2~o#sUkQ7z@V zDle#8)Pb?Fq_}X#%H-1*_QqpTh&&ZwHR-DN(;RvZrmHjdytFQ#cAW&1w&6LCV#;?F zP%mzmX>_=D2-ZS!x5afjVO?2@G!1<1Xk$4(w2JHt5PWX?LkOW~QIoQ?ylFLsH zmDN@+{(f4JP)U#9KdKE6c1rddC3s%Ro^zS}G^aJbA!Vw{$J$#wSFz*~`;QUq^k&ci zd(dFZ*d%ED_*b#my&^VJGty{s8er6H9;oHERo|Gjyuq`Yg+8?@GQOl+is+6U@QXp4 z!Db>rUqv$O(D`cXAuL6bjXETww;0v?V3A}Y!*2lK9)8I())fvxePE)~z+~DgpDiC7 zmK}8gEi!l$^VWZQ)KsWjEl>U~6#EV@;X)A+@`%PK4Y9Cos}pLRM`P={&LKC?p;J-m zl^$(UduM|5f*24*5;llkK5kP@k)OZ7*y_G+yz*s3PNkIr$ zHhgY(6zfg8oIJ~oBrf;OX7y$!neY!*dl$a;4CT{H{+57wmwi4|L(g=54%w0n*eO%b zZs^yGe&JRB?SWf?2bQ?lJ-e{mPJb^Au?wTu{x>u+l*5~K!=p`oOU-R}YlS!;Eb0mh zy@^HRF6;?ju5}ymO2J~hlI2)TP-@68J6)w|7$K;4WSE;bu4fVC%0UA&-5CG_3UA@Cn{XL2{bq=HdA z==wdhxk8G)GeVn0l$E zyY7Wg>oK!Qw_uhYZ&+Qm;^d58d4SR$GZIykjjDtm?8uVQ%8xkwf(#HWq)8T1C17=Y z05aY~zu~)|b@kMFtv=pE1^c@G10S+Ez>z+8Uxlk#Sk63|Nf#KVLV5Si%N-Z%Z+y0J z4AOPNwzrGNU75Qdk2>BIzKN{x&A8MOuoK!dMWDj?0lEr3TBkSskHMYsA!tu+Zg)(u zX@bspcre-TsHOLbw7#ah@0*8hVm7q3?rwF?v|=oW?0yiOJb`6J?;BCdD=a{`2A6UL-y#I>9wPqChL8 zCcZly2-6p9#2k1#l=0i=bK{p9{`n`hmWgD?K1Puj;kh$bsm7wA5A^=YdZY1o?@N81uu|&zj^{C6yaWjWv(*(; z+B7PdH=28AwGmZ$@s#TGNlH1r$L#WitG$NmIf*K?^sH)F7tMW2?sAAy(JfP>GxgRd+M|9-;UO?N{sq)w#z?D&*v!yTr?=nmg3x94~?YzgLI&lGrN z412WqmRExNOr@REKGf{8CQld*@Gf{?n`rl&&8f+&!!CZAKtHTG>5p0lD(ip08rah* zi8G&s^=g6!7P61d&i23C;1!D~qyju0n_`HzCF{X03047}`Oevit@QaaCF;k$#93PT zT)b;D90FwtLfhlnP`$Y5zrX3AVJDD@2Lq8l_p3zlQH4pEmjR6T?#RPWWDaaGI3Wb> zkuKV5$;Ofgf_!q~!--RwxA94()fbgq1qX`=U2__emtP#}Xj2~UI2EbY3*li==QyrX z9*yAj7UUt5nYq`@_j77`O)FH=FqEZ#hN|~+NaVZ-Z|BofrP)t^TMRBlH4I?)azHSv z+I!j!Cx?uEEyUVs0f;8@%NR!F|-Mv(H zu#lkAHCk-(OOM3_mV5x*$m6Ds;!$&QeSS67gkGoi$ZPDS>9e!>-v7M56ic4o{r0jI z2#~hJdl3dy`f%-p$Dt96a2DIDoQT;5NpBQqv9gm?Y+*n#?9#RKC6H=DfzERF*#bT* zY9Q`IFJDiW#as%^$p?wkHGu3?P8cl5PqGrwSP2tV#vn503S*j2a;)@259WbQ4g(QO zL-FoXRjGUz245!c^zNW$28h#pnesmH1Y@rcTDn5T>VG$h@Ox7`j!&2k&t3p%K%Y3! z(&QinX^5)9lJ1#AvX1pyIKJ9du^i_T>~*$&;=EWtF7@oHy~Q=(jdIsTFVV>1=3O4^ z^xx-*4#B84z<-LQO2t#r!Je_dkPXS5<$E=F%D&R*6!5;kN0&W{myeO)I^7ybYih5K@lmy2u?1#%c_#_A}n02OFCdD^Z>LdW}`0V0Qfv^_yi+d-Z- z#C4!s%2R@P^M#cg*C_y+Co<{&fCZ(x-{3Fup6)un486Blm$xaO7H)HC9fqCrZ=G-F=Z=MTJt`IOUn2HY{kc$7z;+)~7v(~h>V1Au( z;y{cX>Pb(^M5s=Rwhk(SftLM_u=6%(G-rzT&s!MVjNDR6+GXiSvbN#sj0n|ID^~EE zd=H`I+ErS1`=p$Jm4bs&m&<#w#FRxVPa7V|zkI?0RT(_%Pr)lg?ne!^ zE!STD&uWiU6UL)BimC?@lCbcP)pFpNWMRP3l31-E0RI2jYK+CXWbStYH%3)pNMyi5 zpPL0%`>!`M-9p=p^f)B)=kRx?@jQG4;%yRao3uZ(BOgj49+x{Mq>Vhj)F$EXrhFM__C7w1pmx3*KRmkW6=OypCB&FWxoIw*ql*1{gJrfP9EG~tc_Qe4+t#|a2_8bo#kpaef8nOFsiv2eGgn=d+dtPFp+ECnLGvC7x+K}AWM{6cX+Zo*;05+ z-#!20V?6ni3rTzJZ9;RzTOHho((Ma2w^Za?kl3o zil$$Unna|1KJ=v%qz)J-H_IWL^2-mq7Y>-Y%5qyVb{lINnI>TmuMeN|(!Jz+lfun3 zJrPq2^5kbZLAK%g{7VV?%xV>;p2Gm|RHx|U5(3y-plo3*zOECw{0>Y6*QHV(CW zS>3Z3gSlT~ew``qAJs%g@cEfe`Sog+4TzCbC8OT>xmlr&2@oULIbM3W-%e_Ktnq+f zfkpB*;Q`p=9g?`CPp^bS%{zC}6c9xuk+B{F0d)$Y&Mh|k+9yr3|ww&tPi+z0SMZPUmxw)<=q3+FN3e<%fvPJ z0j7-}d^IrAV+^{y(Yf(d1JRE%OA|j$tzNp@J2J6mtWy#dTlR*bMjzvK1tN(*VQV{Q zqppPd3#EL$6kW1m;Q5`tK}mXl8Y?`yg2dAVFi}IRpi_Ku26gFbknCn{&o~qp<9&!! zu~<{n4Q1(!i|vQc$2On2)*Wfk#fUYPVN`9Bd+VJPQ0&{)w<%gRZu%&$o=|N>ZAhb& z{kuero+?qz1(Gn=6!RkUS7<*$V-ET*tjB_={}3u}jQ-;^XcF7(H-lc$MyJdIn|I#$ z!r@$B?{1M^o_NGU>wHT&M31Ms1!6we-ErHnfA$Xa9*`ye#uV(+Up>nLF(D_wO#4@^ zd5a|EY%~V3Xh(9LCBcgv3W5?)~^vlu1{G+K7!6}ImZy2od;!gX?!RxWh!Vm_YlIMVz&n&bHN zyAiwpTX6{`^Nsh2&>`#CKC$P-m6Lk-0D>b)VUj_^wNE!64c-J{0<3K@7A}u8sXCR8IaR^oq(G|~UCf()?d+bnf)F0F* zzCI~)zjR$-Z{e#pKL6i#=o6n^?2?Tpp8b7He0nshGP;kM79{pZ?p^PlK5}W1KP!=G z^DlP9OPZ;#xg zqGc<3McTL%f@YU`9;a|4mF)5z%yDSUKK^eJbk+NPVldzAssz1n518(?6J^4?Y*f>2 zoHwM;>-fZQy*8q0Js4Q1OMN-WJzn2&oP+QQzPLk74byuBorQRSBml%{PYZMqrJ8o6 z()z^hHZP8oS8k1Ogw-{yKP%<-z?1Ng9jhnNe`ENoMyye#Fn&&l>wS|wn2MZ)=;q2_ z%ibh!1X zaokx+!VZ|i>zVuxJkg|?I{`VBF0ya)HAc6IzlUqSIl6^P@{{XTseSv&2NYH3n2(_e z?+`Qge5U^bfZnYTIktF-jUU5?T@4f}A07s;K}d{ep-_?LJMKyB7!S)$sSaxxNncB% zhYr(-B(wmV>x=%85h{x{+-XNnlLoQ}&bT63_B|a#d(IHMZ@?LwzeG}>UJA8XGgfY@5=CPob}FdRN$#397TC^4ZnX(Djti$+mh3L{3B4zAp0d6rFPS zb*kuOBr+(`Bc3)Sw&R36&9k?d2KyoQjh{z*V+d}8yaZYkO|5{#o6=p(Y(Fj_gtHTR zX|wK@568b~;)~{t#b$T?)-s)2ggS0hkUDBF9>CJE_m&s z$Cyr@V&~$qg62Mz#mKf!nCR3^G$(+VjO&lw#tmj@U++L9g((EWL&^C2<4}gAl-Q7JQfwke1Lt3`db@2 zb3TWS5*mAWW!vOgk{n}uCLn@JSrH=R)AkMUM1%22_)mYAbx!9QxKX%@CS%Yy3gWQg zcRTdYmYmd2Dk8%U{Xl-oXjNR+4Ei6)lM-cDH^jrmOnHr!WAYTGoV?dnK&bLg#%fEP zI3WQNtKj13x^l3um55oZy9hmZ#@B}@63kmX7%pddMQ>S9XHGFA15vBmWJoUR7FckGbaO_eI*N}C`me3tz7iVU7-h1@*Y7Okivw^#-4sEyO z9BfOZ>m{h{BOSb-cB!BrQ+RteCRqz#n}jMR*?R$^-b+p-Cx&ys3}^yBAvgFOpjXcx z%C!970r5dIOro)rC@i&QB)kC0eZT>;hUSDT42@F5V z69HC4wj?Y7(d5QISgIzgb*~t?kctoLz$HgD((I&_wKM}}WS%+$JJB1Y`g&ZtK8`v( zt$DCY7ecB(CwjTWbRV|9gyaPJWQsf&ohWw3s$!Ay-tE8{guc2Ol}+Z)?tfi`CU!=o zaq7hvOmMihcW{ISx?0z)I`$) z!rDi&$1J2G?7$Edjei>K%a>@nN+>N6iSM!qDu~LTfAI#jQej-AIuPPHaNS5AQvd1y zo>5az1K1OG<@&_{&ujMs!w@wx$lXVb8yt_$;RJ^rZ0riQZ1XM-X`2gEmu40-Sa464 z?+kCjD&qa3Ozo?|;W7~WWs0XD5Lc<0ajE^JCosPZeK$|94dYpLL1iF*gG4Wg)q!$bkM-}cm2LV_tyxAHeq6GPG@ zxvdL*vjkkp-tSl+!Ky!xuSA_V2WUW#yHX&-2OOKPaqOMdPHUOEriEpIMHBWFm=JCZ zN{pCb3;hKie)=M*BmPX0x8Oj9E3=XeE`P^=j480TS9P1D%d=-C?+OR^&|QYH4~Gu6 zlk-Afk_(I{wU0tz)Z!mc{dol zy9BK&$VTBm>*8YmBfKMi<(^SulU$|gBmH+4UmewHQ;(Gs^qsI9EJ9ODawmn(mFwVy zmv_PHr_y^$w2+0rKz?v4+fGNZnQ8o>`HXNoAe<>rwT6_viOxOJx8`p4OrdqtRX?1muQN%} zd(K8&*FT-+$)O`OpN1X?B0AQSrFXUT`y^H%;m;3~7_PNEQ#?@d>(*k`Q(s za`vC^Xe{&9<*Lt)yr!>+uh0wPs_!O|gM}7AyfE52YFkkU2G6qGQ`wPF-8Z{``S?w0 zaG3FUN?0HN2@cfzbpF2ah%d1t8DI*W~B?p9%a*+t4m1>Ma(v^bE|1t=4S1TCdCHBv%fv{<*4D!%j ztCPKuEThqaxi?X82%l)By9mmP8p@&t;-@7b)IO(&Ffv@|c(%?T1aRncOp-qTu1W z3dSQkt8Yf-bx?9C%b;ayg zJ z2wwR8FWXm7T^v292h2~O!VMIRtUa-Nm@V922HV$iv(*uVve!jrOl6uoaNyeFwuJ#U z=A!<2A7o2_08}`OM}TlCXBt?$@C5(ix*MIr1!efB6+&X|4I<2Z+zs49mBLt=)WwwB zOWQLDxolfw)V9Itw?FdbtEDo&F-V1H*u{O|A`kDt)>HA?Xo5~-SRlY4cwF03Pb%{ux*Mh-UO-b7|fq!-R3$w_^oH&Z|Vg(2(AP!`lu z_-tr`Uh5O1uIEJ5@b@nLZTME%p;dh$^819sXNmtD)R1KsofVt|g$AM;qf6;ix;4!v zOly!333pCG#@rNm*yZFFay~^B5Nmmre6IT2nHZmlvL}V@6zZP>6xM4C;{Y((Q3rS* zLIB@2xkFK!GYY<;a2Jquukl$IOIrV%_*Mj5Nm#Q%Wg&SgRitKM>Kb^|cdPGc7he%j zCUp>dly$=+K1V=19%@rdSKN!yUKNgYZltOaP7Uu0vlFvyquJwr_*-re>2}G$hJ4uEM(ja9wS~c|8+QzSFENT-D zPMZv6?xRe4Y@m22Hmj#~(4+k=;oiAYIR)J(dzj?;;eD8+&L20IG-sP$IXPv`IQZ-u0PMzs(B6w&ifdw z?Pe+IkKe3sOR(Z=7Mez)lLk`y(WOK)QK61xSmWl%7X6lPC2HgBayJ%{xf*g?O^biy zQsu>tu$~$zPk$b+r(JA@2SPj==*G%dZ-O^sXEkc-4%WOwBpoE_HJ7wZm7T!FKxo>* zVrNJ$3dvXxI3LyQk0Ol{XvDb~PkN6&6H#%#E9&Q$;hFdRdzECFNAxBbv@P3?dk^np zn4o|87nbvlTe3hpo(%u8Ikog;0hkK_Gl~dV5vm5^##Z>hBt{9?uEbKb-+AX?}icmD-kr{c6F6S zLBjf3g#Hj8S8*KxttCXj+SB_Gr7G0L0esUDV~_HaWu)UfSy2IwO6Pjl0_5b;gS>&+ zOtvaCN$-QIaRb$G$R#6`dZRzy-@~TdzUj#L&J!hcBto#4hQ-G`RmX&G1G)treY5Yr z!wj@jU6iHkTol_Ey8VqiU1xl?mhnFm)@!OAdD^Y;_mUGqqjrJRj{6$WH0vh8JtLG! zpg}N|(w&XMRbl}z`Vg(&u{0?v0bSmdY2HMnG)pwertJO?AQmb)ifrdunCxg0NYxP@ zpfQdQyQE9b;S!%TA+E}`RJF*#cl%eZ(BGEeZeUp=EW7BdJlS&6VWxhF;g53W9De|b zDks)_E|@IX7;-^>Qr~*G79HAmpD`%uWh17dnhlLRCKajYcwksMkRce zGiW=QK`@$psTPDOG^67OZlze|A~(*QD&mF^mh!+hy+4=pYm>IfTOnvkPlucjMjN^P=xpu0fza)8ZY1aD%hqos|}7 zx;Y@$U_6_XJH(B&-RnNBT3Fsf5qrcQZw0dDlSQKM)AlNP4B(1iOpaaqaIdRT!C@M@DAT>0U!zO7m|Hg_?xfZ^md$|#+=cm&l%6gXz{SR@!(+G z))s0#6-S&aG>nVfbw50aeW;V>Z`omeysYi6?wBe<4uo^X$|4`Y(>%DwsD&=vsaV$?k?3E>Xbwaz=}7I&y9X*hm5`w5d+{vSECbMVpTI5SUvY-M z8sGzrSOu{~1jx0Q)Ghk{1Qp01?B@I&41jF_6q8ByZl{QRy1rvZ4g^blP@B6X~k(S6KjW%nuR(3Vq>iRw8|&7b$I;46DX7Z zOV-0O6ROiJsn?ogll#9X@8$UII(2g7BZ=OtRJ|VDv6J_+?Uz7739%h(Xqf_Sja2kqO}3Kr>If0)7c?b;+s+p0K%$Rax)8jFlyO5kV0Y0AqiFmTS9}(Lv1!uC(oU=wGLUq_wfnGCs3ZE##+}uaZ+tzmT~yo z@B^fO><5<52>01vd?#ylbzRkkj z0d}z>(5a&@xwHve{Y(6V7r3-hOsaam#MR}e$`ZN$6=M=2u@uo9_}PJnAlq>eGw~se zayLI-$xsO<5KeSNykRD{19|l8Qg2Hd9htiLQp)xNZFz6uk)b~gp%az|#t(ModNx)K z0`aBQJ5|4}LzOy#%_eI%h3eo3853)C!u%s_GsEiN=ge8JXAGja7!R@&SyWV4p2PER zT-wuOCk=JR)*hIJSb1jvU;J$4q zX}s!I3<1No*P7J&fudXkOiztU)Rh;FsbYV-^5;I!E#jgceI|GtoGbPv)H=)n;uXrP zVv@lz>9Uly0Y{{6AP-j>{P1HiJM0Y^Ax zc}|wai>m!}M8?=lL#p&C>`T@UNjP67|>a0$}`TH#(5DXHK%dOG5XW* zwA0=me{2x1xVUq7j7KRt;bbPV%&|3?s(J)%#MR!zFL!S0#;7eaeA^Vy>(izcRZ%x( zOIQG47}U;+3~;(hzXkVZO=ns2jrFE2oU$Wc7?e+Bm_YIE&PB%T@6`zJ)o|8ql2_IV zPtW`2a)^G$qK7)t5JNb4Uw5A?H~Rfm6MmL#_Eoq!zgAaPg-BxM-vB^uLat+b?HNvo zG$!c7xSaB=Un0uNUzGM68OlhUgSvaP z*dZ3kx>56Fj0VEFBPU*qk{<_)cb;+{o>u-sZ5$*Us6nQaXfH8bJ5=u-DG9|esp%fb1$L(Yhk{Jl1Q|ZjsHz&8z0Q+w7q^sn zI_#tFqTz>^0H?J&?cN?5fzn5V!MpemNmK1BG0EZ2YPxKb(m=j8@d*$B8gqzMq9ghg z@}i_!*aOup{K{Ec@ZWy(Ce`uvuUkSIX8yF4x<>r_Jmpn^rY_!M=pauYt_o4PLNZqV zXgh$cM3;##!qRyAPh3dzPJU8SUcjN(b4uqs7Wla>SewaEqdAl|Mj9Pii~f87eViA0 zdgn)C{lm2jf8q@vTx%6R3h)0>D57rw275GnP$8&xTK2EsF0FWxU72xVd zRO8mC=KjuT1r28t*e`VEL z!+&!9OSm}o)iX{3+(L8C`8#%U$G0v441oVHUndO!p;bcvUwP5>|NmzH&s&R-}U~=ukf^ z2im;m;J(!z3U*yw_9xTXhFRW*Vb;cKex8&rh0hh}wuO1P-f70_SZ5VAq z+vcwT@vnxMZ?Cg?BNXsi;Q!JYKf7hKT=MNmQ}KK1n;xH;VY7UfSb#X;WApEug~Tgh z|0v0e*ZtQ!eH=GcJpD(@Cw6|Q)hA~D^BcCN&&ssAvd>qh`y8<%-(mW|+=W~W8TBP9 zPN4<-nGgJL0Ecc^xj)>n^o2Sd6??Gnp-b%Y796pDUJ(`DME-g?YAY|w=-;RI4=Yid zcV3gU`YbBmnS1DNzi~Imrq|||{1|IX&S2y`Kg0gR`a3B+vrR|u17Nc9stJ_QSES@? zx9np^!{ZgJ3A=pQgVm$jkKbiVoFEw6)Y>r>y~X;Re;^y>0~o8?iJjvk62{Q03QE1w zbd>e9{Fw{r-**2fmAcd%jh&J=^%C$OPLgFK75I0|`YGx{c$(?MXRXJ=|7w`G2s-q3 z9{6nn4~avhjwOdCU@Y|A2=Lt4XZ}C{uV4Do^u<);ZvDhEq|qeum%p$?K~&B?fy(%j zU&ti;`SKP!ocC01?5FMHvD|S~P;B_J+*%>y519Laf`9qDA+!i0wRkUClt&E|@?yo5 ztzp0ow7|u?K(AQ+0vU$zU7%M$o7aD7t8rX8%b9*VxUO1U77UseqBoRMgOY00$7gL0 zCs9tR2G)?wH_b9p{3hqd5`v4T!Jb0{8=Ou?UkbGlsNWc zU}!mGN36F1y-&Yd8e4GVZC=IClR!`N^ZvTb@@0ruZxj61wohy0Jv1U7#+fdrT-$iD z)N+i|JI1)2^UjU23L7z<`Zq{&&3CWP9OJJeW~7-P|e*S#(X&#UIH?x zI2lCq`M+wr)}W@6ER0%~jLS;}k?imqR#8M8QE*lscZd@hP$2^gSOf?RG87NxWzYmn zMj$+fl?1cODvwkKA20$jGDtMUhyemP!Ylz2g$RfPMFL3>Lf*;V1kkPhxmDYB|J+-B zPn~o6bf50i-RG<^v zvFAJ9Ji&(jKCUlVl=#1OJA7yaOgyC-ie8A#^rdpids|LU&dPZU-DKW1`71E(l&T)B z1=9$nd}@kuia)=n+3|wNQe0#S6T?}1@`sk3vX!U_OxWka;q`J5YqYG|MyS;suC^u)S&MFD)6yS&)ea7 zB*Y6-VcMG9zDxb6^A5aYE>$#i)t{$rPb*xMd4tCu>qqbM%xaa(n7~H-{D}e7nt*dZ zZrB=vSqec$M@mXZCB-d3#y-c#OJVAz00BTW*TjgX8Rt5RF|@H3X-ri*C~IRTS@2Yf7=hsDq@3;hsR)% zul4^R%yv7dwoXzoH!a6XONKH>EQr(V>7}A21gT;Wx=`MbP|Dh4wk}ZyAop$!GySv{_ z>Q*~s#p}Z53_VZ5t%A>VHFmz*0juTV;{0p@qJqIvGcb(Y0yZb4arzYlS|@4feQ%ZK zUU@#NmS~JzT0zBjiiIKV#E_rn19%geovG=~JPi;{De(dT-0S2&YXx!L{#n+NnNc+3 z>a-zk{nep&2bU|wN6V$F zH_O8~@-T@&T!lX&2|Z3JNp5hO42sKCKMzij&`rP=25XCNskB@KgR9h~Dsq^D8LCc5 zeF~QdRyRd(g0nm)e!Z4|<{_+79V$h+@I5(K_S2vI88}i-b?(X}D_!;P$-bHyoQB}2 z`xl@JGMY_sf%Ozw3Rmp!w8m}^(<;e&G%8y22&%{^U~tAPT`ma3*&&Td)sR1R4br~+ zyWbtiKEgPVAXCg*?(z390}hl|bXT97DGVs{UbADzEs7NS8Z~^|i@52B52yn#8C*n1 zK6n|oj+kcM`fPE_&HB3#*Iwp6tMphiEW^yhOioFdgVMob*$G(>6b7l2In4}n%6|z<8EKUe&amK-^uBxAK@w<7!ch;@O`&3zKos&@ zENH!B=suL`hW1HW-(5bSIaYB@bka8aNR3OQJOYd;1*wLc_)rXm^~y z#2%Ztc+mOD9<#6!9u2R%^dNiKZ7j02 z=(5SWZrmRcekgDKqAvMFt-Sek(Or0Eux#uC$Uq-z_k#QDPqjdTZBbPgw=Cua*Hekf d5MQupSbux>oI~!etS|vfFf8<&R%k-uzX9vP2P*&o literal 0 HcmV?d00001 diff --git a/windows/deployment/upgrade/quick-fixes.md b/windows/deployment/upgrade/quick-fixes.md index c4a602aacd..b6a64d28e9 100644 --- a/windows/deployment/upgrade/quick-fixes.md +++ b/windows/deployment/upgrade/quick-fixes.md @@ -3,7 +3,7 @@ title: Quick fixes - Windows IT Pro ms.reviewer: manager: laurawi ms.author: greglin -description: Learn how to quickly resolve many problems which may come up during a Windows 10 upgrade. +description: Learn how to quickly resolve many problems, which may come up during a Windows 10 upgrade. keywords: deploy, error, troubleshoot, windows, 10, upgrade, code, rollback, ITPro ms.prod: w10 ms.mktglfcycl: deploy @@ -38,7 +38,7 @@ The Microsoft Virtual Agent provided by [Microsoft Support](https://support.micr
  • Check the system drive for errors and attempt repairs. More information.
  • Run the Windows Update troubleshooter. More information.
  • Attempt to restore and repair system files. More information.
    • -
  • Check for unsigned drivers and update or uninstall them. More information.
    • +
  • Check for unsigned drivers and update or remove them. More information.
  • Update Windows so that all available recommended updates are installed, and ensure the computer is rebooted if this is necessary to complete installation of an update. More information.
  • Temporarily uninstall non-Microsoft antivirus software. More information.
    • @@ -166,6 +166,9 @@ Drivers that are not properly signed can block the upgrade process. To check you 4. If you are prompted by UAC, click **Yes**. 5. Type **sigverif** and press ENTER. 6. The File Signature Verification tool will open. Click **Start**. + + ![File Signature Verification](../images/sigverif.png) + 7. After the scanning process is complete, click **Advanced**, and then click **View Log**. 8. Locate drivers in the log file that are unsigned and remove or update them using Device Manager. For more information, see [Using Device Manager to uninstall devices and driver packages](https://docs.microsoft.com/windows-hardware/drivers/install/using-device-manager-to-uninstall-devices-and-driver-packages). @@ -212,7 +215,7 @@ To use sigcheck: MachineType: 64-bit ``` -In addition to unsigned drivers, drivers might be signed with an invalid certificate, requring the driver to be updated or removed so that Windows upgrade can continue. +In addition to unsigned drivers, drivers might be signed with an invalid certificate, requiring the driver to be updated or removed so that Windows upgrade can continue. ### Update Windows From eb8290ee4e9c8549c262b119fe6b504af852d925 Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Wed, 7 Oct 2020 15:47:09 -0700 Subject: [PATCH 67/76] added txt --- windows/deployment/upgrade/quick-fixes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/upgrade/quick-fixes.md b/windows/deployment/upgrade/quick-fixes.md index b6a64d28e9..837199548a 100644 --- a/windows/deployment/upgrade/quick-fixes.md +++ b/windows/deployment/upgrade/quick-fixes.md @@ -215,7 +215,7 @@ To use sigcheck: MachineType: 64-bit ``` -In addition to unsigned drivers, drivers might be signed with an invalid certificate, requiring the driver to be updated or removed so that Windows upgrade can continue. +In addition to unsigned drivers, drivers might be signed with an invalid certificate, requiring the driver to be updated or removed so that Windows upgrade can continue. Sigcheck will report whether or not the certificate chain is valid. ### Update Windows From 697519637081d513b664800c47556840e8e712c5 Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Wed, 7 Oct 2020 15:53:11 -0700 Subject: [PATCH 68/76] fix link --- windows/deployment/upgrade/quick-fixes.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/windows/deployment/upgrade/quick-fixes.md b/windows/deployment/upgrade/quick-fixes.md index 837199548a..a4619b4f14 100644 --- a/windows/deployment/upgrade/quick-fixes.md +++ b/windows/deployment/upgrade/quick-fixes.md @@ -38,7 +38,7 @@ The Microsoft Virtual Agent provided by [Microsoft Support](https://support.micr
  • Check the system drive for errors and attempt repairs. More information.
  • Run the Windows Update troubleshooter. More information.
  • Attempt to restore and repair system files. More information.
    • -
  • Check for unsigned drivers and update or remove them. More information.
    • +
  • Check for unsigned drivers and update or remove them. More information.
  • Update Windows so that all available recommended updates are installed, and ensure the computer is rebooted if this is necessary to complete installation of an update. More information.
  • Temporarily uninstall non-Microsoft antivirus software. More information.
    • @@ -193,7 +193,7 @@ To use sigcheck: C:\Sigcheck>Driverquery /v > C:\sigcheck\drivers.txt ``` -7. Open the drivers.txt file and locate the problem driver that was reported by sigverif in the procedure above. Copy the path to the driver. +7. Open the drivers.txt file and locate the problem driver that was reported by sigverif in the [procedure above](#remove-unsigned-drivers). Copy the path to the driver. 8. To check the driver, type **sigcheck64 -u -e \** and press ENTER. See the following example: ``` From ffd4ebc8dca3e52f965f995c58fe7e15c6259f97 Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Wed, 7 Oct 2020 16:00:14 -0700 Subject: [PATCH 69/76] update resolution proc doc --- windows/deployment/upgrade/resolution-procedures.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/windows/deployment/upgrade/resolution-procedures.md b/windows/deployment/upgrade/resolution-procedures.md index a96205d6fd..6b8a9587d2 100644 --- a/windows/deployment/upgrade/resolution-procedures.md +++ b/windows/deployment/upgrade/resolution-procedures.md @@ -36,7 +36,7 @@ A frequently observed [result code](upgrade-error-codes.md#result-codes) is 0xC1 The device install log is particularly helpful if rollback occurs during the sysprep operation (extend code 0x30018). -To resolve a rollback that was caused by driver conflicts, try running setup using a minimal set of drivers and startup programs by performing a [clean boot](https://support.microsoft.com/kb/929135) before initiating the upgrade process. +To resolve a rollback that was caused by driver conflicts, try running setup using a minimal set of drivers and startup programs by performing a [clean boot](https://support.microsoft.com/kb/929135) before initiating the upgrade process. Also check to be sure that your drivers are properly signed. For more information, see [Remove unsigned drivers](quick-fixes.md#remove-unsigned-drivers). See the following general troubleshooting procedures associated with a result code of 0xC1900101:

    @@ -49,7 +49,7 @@ See the following general troubleshooting procedures associated with a result co | 0xC1900101 - 0x30018 | Disconnect all peripheral devices that are connected to the system, except for the mouse, keyboard and display.
    Contact your hardware vendor to obtain updated device drivers.
    Ensure that "Download and install updates (recommended)" is accepted at the start of the upgrade process. | A device driver has stopped responding to setup.exe during the upgrade process. | | 0xC1900101 - 0x3000D | Disconnect all peripheral devices that are connected to the system, except for the mouse, keyboard and display.
    Update or uninstall the display driver. | Installation failed during the FIRST_BOOT phase while attempting the MIGRATE_DATA operation.
    This can occur due to a problem with a display driver. | | 0xC1900101 - 0x4000D | Check supplemental rollback logs for a setupmem.dmp file, or event logs for any unexpected reboots or errors.
    Review the rollback log and determine the stop code.
    The rollback log is located in the $Windows.~BT\Sources\Rollback folder. An example analysis is shown below. This example is not representative of all cases:
     
    Info SP Crash 0x0000007E detected
    Info SP Module name :
    Info SP Bugcheck parameter 1 : 0xFFFFFFFFC0000005
    Info SP Bugcheck parameter 2 : 0xFFFFF8015BC0036A
    Info SP Bugcheck parameter 3 : 0xFFFFD000E5D23728
    Info SP Bugcheck parameter 4 : 0xFFFFD000E5D22F40
    Info SP Cannot recover the system.
    Info SP Rollback: Showing splash window with restoring text: Restoring your previous version of Windows.
     
    Typically, there is a dump file for the crash to analyze. If you are not equipped to debug the dump, then attempt the following basic troubleshooting procedures:
     
    1. Make sure you have enough disk space.
    2. If a driver is identified in the bug check message, disable the driver or check with the manufacturer for driver updates.
    3. Try changing video adapters.
    4. Check with your hardware vendor for any BIOS updates.
    5. Disable BIOS memory options such as caching or shadowing. | A rollback occurred due to a driver configuration issue.
    Installation failed during the second boot phase while attempting the MIGRATE_DATA operation.
    This can occur because of incompatible drivers. | -| 0xC1900101 - 0x40017 | Clean boot into Windows, and then attempt the upgrade to Windows 10. For more information, see [How to perform a clean boot in Windows](https://support.microsoft.com/kb/929135).
     
    Ensure that you select the option to "Download and install updates (recommended)."
     
    Computers that run Citrix VDA
    You may see this message after you upgrade a computer from Windows 10, version 1511 to Windows 10, version 1607. After the second system restart, the system generates this error and then rolls back to the previous version. This problem has also been observed in upgrades to Windows 8.1 and Windows 8.
     
    This problem occurs because the computer has Citrix Virtual Delivery Agent (VDA) installed. Citrix VDA installs device drivers and a file system filter driver (CtxMcsWbc). This Citrix filter driver prevents the upgrade from writing changes to the disk, so the upgrade cannot complete and the system rolls back.
     
    **Resolution**
     
    To resolve this problem, install [Cumulative update for Windows 10 Version 1607 and Windows Server 2016: November 8, 2016](https://support.microsoft.com/help/3200970/cumulative-update-for-windows-10-version-1607-and-windows-server-2016).
     
    You can work around this problem in two ways:
     
    **Workaround 1**
     
    1. Use the VDA setup application (VDAWorkstationSetup_7.11) to uninstall Citrix VDA.
    2. Run the Windows upgrade again.
    3. Reinstall Citrix VDA.
     
    **Workaround 2**
     
    If you cannot uninstall Citrix VDA, follow these steps to work around this problem:
     
    1. In Registry Editor, go to the following subkey:
    **HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e967-e325-11ce-bfc1-08002be10318}\CtxMcsWbc**
    2. Change the value of the **Start** entry from **0** to **4**. This change disables the Citrix MCS cache service.
    3. Go to the following subkey:
    **HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e967-e325-11ce-bfc1-08002be10318}**
    4. Delete the **CtxMcsWbc** entry.
    5. Restart the computer, and then try the upgrade again.
     
    **Non-Microsoft information disclaimer**
    The non-Microsoft products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products. | Windows 10 upgrade failed after the second reboot.
    This is usually caused by a faulty driver. For example: antivirus filter drivers or encryption drivers. | +| 0xC1900101 - 0x40017 | Clean boot into Windows, and then attempt the upgrade to Windows 10. For more information, see [How to perform a clean boot in Windows](https://support.microsoft.com/kb/929135).
     
    Ensure that you select the option to "Download and install updates (recommended)." Also be sure to [remove unsigned drivers](quick-fixes.md#remove-unsigned-drivers).
     
    Computers that run Citrix VDA
    You may see this message after you upgrade a computer from Windows 10, version 1511 to Windows 10, version 1607. After the second system restart, the system generates this error and then rolls back to the previous version. This problem has also been observed in upgrades to Windows 8.1 and Windows 8.
     
    This problem occurs because the computer has Citrix Virtual Delivery Agent (VDA) installed. Citrix VDA installs device drivers and a file system filter driver (CtxMcsWbc). This Citrix filter driver prevents the upgrade from writing changes to the disk, so the upgrade cannot complete and the system rolls back.
     
    **Resolution**
     
    To resolve this problem, install [Cumulative update for Windows 10 Version 1607 and Windows Server 2016: November 8, 2016](https://support.microsoft.com/help/3200970/cumulative-update-for-windows-10-version-1607-and-windows-server-2016).
     
    You can work around this problem in two ways:
     
    **Workaround 1**
     
    1. Use the VDA setup application (VDAWorkstationSetup_7.11) to uninstall Citrix VDA.
    2. Run the Windows upgrade again.
    3. Reinstall Citrix VDA.
     
    **Workaround 2**
     
    If you cannot uninstall Citrix VDA, follow these steps to work around this problem:
     
    1. In Registry Editor, go to the following subkey:
    **HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e967-e325-11ce-bfc1-08002be10318}\CtxMcsWbc**
    2. Change the value of the **Start** entry from **0** to **4**. This change disables the Citrix MCS cache service.
    3. Go to the following subkey:
    **HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e967-e325-11ce-bfc1-08002be10318}**
    4. Delete the **CtxMcsWbc** entry.
    5. Restart the computer, and then try the upgrade again.
     
    **Non-Microsoft information disclaimer**
    The non-Microsoft products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products. | Windows 10 upgrade failed after the second reboot.
    This is usually caused by a faulty driver. For example: antivirus filter drivers or encryption drivers. | ## 0x800xxxxx From 4f348378a25dd517ec6ad2c951d3ca9bbb0a70d9 Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Wed, 7 Oct 2020 16:12:42 -0700 Subject: [PATCH 70/76] update --- windows/deployment/upgrade/quick-fixes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/upgrade/quick-fixes.md b/windows/deployment/upgrade/quick-fixes.md index a4619b4f14..3f2fc11c16 100644 --- a/windows/deployment/upgrade/quick-fixes.md +++ b/windows/deployment/upgrade/quick-fixes.md @@ -187,7 +187,7 @@ To use sigcheck: 3. Right-click **Command Prompt** and then left-click **Run as administrator**. 4. If you are prompted by UAC, click **Yes**. 5. In the command window, use the **cd** command to switch to the directory where you extracted sigcheck, for example **cd c:\sigcheck**. -6. Next, generate a list of drivers using driverquery.exe. To do this, type **driverquery /v > c:\sigcheck\drivers.txt** and press ENTER. See the following example: +6. A list of drivers with their path is displayed in the File Signature Verification tool (step #7 in the previous procedure). Optionally, you can generate a list of drivers using driverquery.exe. To use driverquery, type **driverquery /v > c:\sigcheck\drivers.txt** and press ENTER. See the following example: ```cmd C:\Sigcheck>Driverquery /v > C:\sigcheck\drivers.txt From 8afbba9a89f8d304b7db5db7e68d2d642b25d07a Mon Sep 17 00:00:00 2001 From: ManikaDhiman Date: Wed, 7 Oct 2020 16:44:47 -0700 Subject: [PATCH 71/76] Updated topic titles and filenames --- .openpublishing.redirection.json | 45 +++++++++++++++++++ windows/client-management/mdm/TOC.md | 16 +++---- .../mdm/enable-admx-backed-policies-in-mdm.md | 2 +- ...ew-in-windows-mdm-enrollment-management.md | 2 +- ... => policies-in-policy-csp-admx-backed.md} | 10 ++--- ...n-policy-csp-supported-by-group-policy.md} | 10 ++--- ...d-by-hololens-1st-gen-commercial-suite.md} | 6 +-- ...y-hololens-1st-gen-development-edition.md} | 6 +-- ...s-in-policy-csp-supported-by-hololens2.md} | 6 +-- ...es-in-policy-csp-supported-by-iot-core.md} | 6 +-- ...policy-csp-supported-by-iot-enterprise.md} | 6 +-- ...in-policy-csp-supported-by-surface-hub.md} | 6 +-- ...n-policy-csp-that-can-be-set-using-eas.md} | 6 +-- .../policy-configuration-service-provider.md | 30 ++++++------- .../mdm/policy-csp-controlpolicyconflict.md | 2 +- 15 files changed, 102 insertions(+), 57 deletions(-) rename windows/client-management/mdm/{policy-csps-admx-backed.md => policies-in-policy-csp-admx-backed.md} (99%) rename windows/client-management/mdm/{policy-csps-supported-by-group-policy.md => policies-in-policy-csp-supported-by-group-policy.md} (99%) rename windows/client-management/mdm/{policy-csps-supported-by-hololens-1st-gen-commercial-suite.md => policies-in-policy-csp-supported-by-hololens-1st-gen-commercial-suite.md} (95%) rename windows/client-management/mdm/{policy-csps-supported-by-hololens-1st-gen-development-edition.md => policies-in-policy-csp-supported-by-hololens-1st-gen-development-edition.md} (95%) rename windows/client-management/mdm/{policy-csps-supported-by-hololens2.md => policies-in-policy-csp-supported-by-hololens2.md} (98%) rename windows/client-management/mdm/{policy-csps-supported-by-iot-core.md => policies-in-policy-csp-supported-by-iot-core.md} (97%) rename windows/client-management/mdm/{policy-csps-supported-by-iot-enterprise.md => policies-in-policy-csp-supported-by-iot-enterprise.md} (96%) rename windows/client-management/mdm/{policy-csps-supported-by-surface-hub.md => policies-in-policy-csp-supported-by-surface-hub.md} (97%) rename windows/client-management/mdm/{policy-csps-that-can-be-set-using-eas.md => policies-in-policy-csp-that-can-be-set-using-eas.md} (90%) diff --git a/.openpublishing.redirection.json b/.openpublishing.redirection.json index 8d507ba71a..b15fa65bb2 100644 --- a/.openpublishing.redirection.json +++ b/.openpublishing.redirection.json @@ -14565,41 +14565,86 @@ "redirect_url": "https://docs.microsoft.com/windows/client-management/mdm/policy-csps-supported-by-surface-hub", "redirect_document_id": false }, + { + "source_path": "windows/client-management/mdm/policy-csps-supported-by-surface-hub.md", + "redirect_url": "https://docs.microsoft.com/windows/client-management/mdm/policies-in-policy-csp-supported-by-surface-hub", + "redirect_document_id": false + }, { "source_path": "windows/client-management/mdm/policies-supported-by-iot-enterprise.md", "redirect_url": "https://docs.microsoft.com/windows/client-management/mdm/policy-csps-supported-by-iot-enterprise", "redirect_document_id": false }, + { + "source_path": "windows/client-management/mdm/policy-csps-supported-by-iot-enterprise.md", + "redirect_url": "https://docs.microsoft.com/windows/client-management/mdm/policies-in-policy-csp-supported-by-iot-enterprise", + "redirect_document_id": false + }, { "source_path": "windows/client-management/mdm/policies-supported-by-iot-core.md", "redirect_url": "https://docs.microsoft.com/windows/client-management/mdm/policy-csps-supported-by-iot-core", "redirect_document_id": false }, + { + "source_path": "windows/client-management/mdm/policy-csps-supported-by-iot-core.md", + "redirect_url": "https://docs.microsoft.com/windows/client-management/mdm/policies-in-policy-csp-supported-by-iot-core", + "redirect_document_id": false + }, { "source_path": "windows/client-management/mdm/policies-supported-by-hololens2.md", "redirect_url": "https://docs.microsoft.com/windows/client-management/mdm/policy-csps-supported-by-hololens2", "redirect_document_id": false }, + { + "source_path": "windows/client-management/mdm/policy-csps-supported-by-hololens2.md", + "redirect_url": "https://docs.microsoft.com/windows/client-management/mdm/policies-in-policy-csp-supported-by-hololens2", + "redirect_document_id": false + }, { "source_path": "windows/client-management/mdm/policies-supported-by-hololens-1st-gen-development-edition.md", "redirect_url": "https://docs.microsoft.com/windows/client-management/mdm/policy-csps-supported-by-hololens-1st-gen-development-edition", "redirect_document_id": false }, + { + "source_path": "windows/client-management/mdm/policy-csps-supported-by-hololens-1st-gen-development-edition.md", + "redirect_url": "https://docs.microsoft.com/windows/client-management/mdm/policies-in-policy-csp-supported-by-hololens-1st-gen-development-edition", + "redirect_document_id": false + }, { "source_path": "windows/client-management/mdm/policies-supported-by-hololens-1st-gen-commercial-suite.md", "redirect_url": "https://docs.microsoft.com/windows/client-management/mdm/policy-csps-supported-by-hololens-1st-gen-commercial-suite", "redirect_document_id": false }, + { + "source_path": "windows/client-management/mdm/policy-csps-supported-by-hololens-1st-gen-commercial-suite.md", + "redirect_url": "https://docs.microsoft.com/windows/client-management/mdm/policies-in-policy-csp-supported-by-hololens-1st-gen-commercial-suite", + "redirect_document_id": false + }, { "source_path": "windows/client-management/mdm/policies-admx-backed.md", "redirect_url": "https://docs.microsoft.com/windows/client-management/mdm/policy-csps-admx-backed", "redirect_document_id": false }, + { + "source_path": "windows/client-management/mdm/policy-csps-admx-backed.md", + "redirect_url": "https://docs.microsoft.com/windows/client-management/mdm/policies-in-policy-csp-admx-backed", + "redirect_document_id": false + }, { "source_path": "windows/client-management/mdm/policies-supported-by-group-policy.md", "redirect_url": "https://docs.microsoft.com/windows/client-management/mdm/policy-csps-supported-by-group-policy", "redirect_document_id": false }, + { + "source_path": "windows/client-management/mdm/policy-csps-supported-by-group-policy.md", + "redirect_url": "https://docs.microsoft.com/windows/client-management/mdm/policies-in-policy-csp-supported-by-group-policy", + "redirect_document_id": false + }, + { + "source_path": "windows/client-management/mdm/policy-csps-that-can-be-set-using-eas.md", + "redirect_url": "https://docs.microsoft.com/windows/client-management/mdm/policies-in-policy-csp-that-can-be-set-using-eas", + "redirect_document_id": false + }, { "source_path": "windows/keep-secure/collect-wip-audit-event-logs.md", "redirect_url": "https://docs.microsoft.com/windows/threat-protection/windows-information-protection/collect-wip-audit-event-logs", diff --git a/windows/client-management/mdm/TOC.md b/windows/client-management/mdm/TOC.md index a7fbff363b..6b92d9991b 100644 --- a/windows/client-management/mdm/TOC.md +++ b/windows/client-management/mdm/TOC.md @@ -159,14 +159,14 @@ #### [Personalization DDF file](personalization-ddf.md) ### [Policy CSP](policy-configuration-service-provider.md) #### [Policy DDF file](policy-ddf-file.md) -#### [Policy CSPs supported by Group Policy](policy-csps-supported-by-group-policy.md) -#### [ADMX-backed policy CSPs](policy-csps-admx-backed.md) -#### [Policy CSPs supported by HoloLens 2](policy-csps-supported-by-hololens2.md) -#### [Policy CSPs supported by HoloLens (1st gen) Commercial Suite](policy-csps-supported-by-hololens-1st-gen-commercial-suite.md) -#### [Policy CSPs supported by HoloLens (1st gen) Development Edition](policy-csps-supported-by-hololens-1st-gen-development-edition.md) -#### [Policy CSPs supported by Windows 10 IoT Enterprise](policy-csps-supported-by-iot-enterprise.md) -#### [Policy CSPs supported by Windows 10 IoT Core](policy-csps-supported-by-iot-core.md) -#### [Policy CSPs supported by Microsoft Surface Hub](policy-csps-supported-by-surface-hub.md) +#### [Policies in Policy CSP supported by Group Policy](policy-csps-supported-by-group-policy.md) +#### [ADMX-backed policies in Policy CSP](policy-csps-admx-backed.md) +#### [Policies in Policy CSP supported by HoloLens 2](policy-csps-supported-by-hololens2.md) +#### [Policies in Policy CSP supported by HoloLens (1st gen) Commercial Suite](policy-csps-supported-by-hololens-1st-gen-commercial-suite.md) +#### [Policies in Policy CSP supported by HoloLens (1st gen) Development Edition](policy-csps-supported-by-hololens-1st-gen-development-edition.md) +#### [Policies in Policy CSP supported by Windows 10 IoT Enterprise](policy-csps-supported-by-iot-enterprise.md) +#### [Policies in Policy CSP supported by Windows 10 IoT Core](policy-csps-supported-by-iot-core.md) +#### [Policies in Policy CSP supported by Microsoft Surface Hub](policy-csps-supported-by-surface-hub.md) #### [Policy CSPs that can be set using Exchange Active Sync (EAS)](policy-csps-that-can-be-set-using-eas.md) #### [AboveLock](policy-csp-abovelock.md) #### [Accounts](policy-csp-accounts.md) diff --git a/windows/client-management/mdm/enable-admx-backed-policies-in-mdm.md b/windows/client-management/mdm/enable-admx-backed-policies-in-mdm.md index 805f9ee481..d79b428c0e 100644 --- a/windows/client-management/mdm/enable-admx-backed-policies-in-mdm.md +++ b/windows/client-management/mdm/enable-admx-backed-policies-in-mdm.md @@ -33,7 +33,7 @@ See [Support Tip: Ingesting Office ADMX-backed policies using Microsoft Intune]( ## Enable a policy > [!NOTE] -> See [Understanding ADMX-backed policy CSPs](https://docs.microsoft.com/windows/client-management/mdm/understanding-admx-backed-policies). +> See [Understanding ADMX-backed policies in Policy CSP](https://docs.microsoft.com/windows/client-management/mdm/understanding-admx-backed-policies). 1. Find the policy from the list [ADMX-backed policies](policy-csps-admx-backed.md). You need the following information listed in the policy description. - GP English name diff --git a/windows/client-management/mdm/new-in-windows-mdm-enrollment-management.md b/windows/client-management/mdm/new-in-windows-mdm-enrollment-management.md index d919c5f1a7..ba8dc31c1f 100644 --- a/windows/client-management/mdm/new-in-windows-mdm-enrollment-management.md +++ b/windows/client-management/mdm/new-in-windows-mdm-enrollment-management.md @@ -2515,7 +2515,7 @@ How do I turn if off? | The service can be stopped from the "Services" console o

    Added a new section:

    diff --git a/windows/client-management/mdm/policy-csps-admx-backed.md b/windows/client-management/mdm/policies-in-policy-csp-admx-backed.md similarity index 99% rename from windows/client-management/mdm/policy-csps-admx-backed.md rename to windows/client-management/mdm/policies-in-policy-csp-admx-backed.md index a580f4a524..75ac21a8b3 100644 --- a/windows/client-management/mdm/policy-csps-admx-backed.md +++ b/windows/client-management/mdm/policies-in-policy-csp-admx-backed.md @@ -1,6 +1,6 @@ --- -title: ADMX-backed policy CSPs -description: ADMX-backed policy CSPs +title: ADMX-backed policies in Policy CSP +description: ADMX-backed policies in Policy CSP ms.reviewer: manager: dansimp ms.author: dansimp @@ -12,12 +12,12 @@ ms.localizationpriority: medium ms.date: 08/18/2020 --- -# ADMX-backed policy CSPs +# ADMX-backed policies in Policy CSP > [!div class="op_single_selector"] > -> - [Policy CSPs supported by Group Policy](policy-csps-supported-by-group-policy.md) -> - [ADMX-backed policy-CSPs](policy-csps-admx-backed.md) +> - [Policies in Policy CSP supported by Group Policy](policy-csps-supported-by-group-policy.md) +> - [ADMX-backed policies in Policy CSP](policy-csps-admx-backed.md) > - [ActiveXControls/ApprovedInstallationSites](./policy-csp-activexcontrols.md#activexcontrols-approvedinstallationsites) diff --git a/windows/client-management/mdm/policy-csps-supported-by-group-policy.md b/windows/client-management/mdm/policies-in-policy-csp-supported-by-group-policy.md similarity index 99% rename from windows/client-management/mdm/policy-csps-supported-by-group-policy.md rename to windows/client-management/mdm/policies-in-policy-csp-supported-by-group-policy.md index 651f088e72..09c680512c 100644 --- a/windows/client-management/mdm/policy-csps-supported-by-group-policy.md +++ b/windows/client-management/mdm/policies-in-policy-csp-supported-by-group-policy.md @@ -1,6 +1,6 @@ --- -title: Policy CSPs supported by Group Policy -description: Policy CSPs supported by Group Policy +title: Policies in Policy CSP supported by Group Policy +description: Policies in Policy CSP supported by Group Policy ms.reviewer: manager: dansimp ms.author: dansimp @@ -12,12 +12,12 @@ ms.localizationpriority: medium ms.date: 07/18/2019 --- -# Policy CSPs supported by Group Policy +# Policies in Policy CSP supported by Group Policy > [!div class="op_single_selector"] > -> - [Policy CSPs supported by Group Policy](policy-csps-supported-by-group-policy.md) -> - [ADMX-backed policy CSPs](policy-csps-admx-backed.md) +> - [Policies in Policy CSP supported by Group Policy](policy-csps-supported-by-group-policy.md) +> - [ADMX-backed policies in Policy CSP](policy-csps-admx-backed.md) > - [AboveLock/AllowCortanaAboveLock](./policy-csp-abovelock.md#abovelock-allowcortanaabovelock) diff --git a/windows/client-management/mdm/policy-csps-supported-by-hololens-1st-gen-commercial-suite.md b/windows/client-management/mdm/policies-in-policy-csp-supported-by-hololens-1st-gen-commercial-suite.md similarity index 95% rename from windows/client-management/mdm/policy-csps-supported-by-hololens-1st-gen-commercial-suite.md rename to windows/client-management/mdm/policies-in-policy-csp-supported-by-hololens-1st-gen-commercial-suite.md index f77d3c1308..0a8beec733 100644 --- a/windows/client-management/mdm/policy-csps-supported-by-hololens-1st-gen-commercial-suite.md +++ b/windows/client-management/mdm/policies-in-policy-csp-supported-by-hololens-1st-gen-commercial-suite.md @@ -1,6 +1,6 @@ --- -title: Policy CSPs supported by HoloLens (1st gen) Commercial Suite -description: Policy CSPs supported by HoloLens (1st gen) Commercial Suite +title: Policies in Policy CSP supported by HoloLens (1st gen) Commercial Suite +description: Policies in Policy CSP supported by HoloLens (1st gen) Commercial Suite ms.reviewer: manager: dansimp ms.author: dansimp @@ -12,7 +12,7 @@ ms.localizationpriority: medium ms.date: 09/17/2019 --- -# Policy CSPs supported by HoloLens (1st gen) Commercial Suite +# Policies in Policy CSP supported by HoloLens (1st gen) Commercial Suite > [!div class="op_single_selector"] > diff --git a/windows/client-management/mdm/policy-csps-supported-by-hololens-1st-gen-development-edition.md b/windows/client-management/mdm/policies-in-policy-csp-supported-by-hololens-1st-gen-development-edition.md similarity index 95% rename from windows/client-management/mdm/policy-csps-supported-by-hololens-1st-gen-development-edition.md rename to windows/client-management/mdm/policies-in-policy-csp-supported-by-hololens-1st-gen-development-edition.md index 2dec2fdb8b..256ddb3528 100644 --- a/windows/client-management/mdm/policy-csps-supported-by-hololens-1st-gen-development-edition.md +++ b/windows/client-management/mdm/policies-in-policy-csp-supported-by-hololens-1st-gen-development-edition.md @@ -1,6 +1,6 @@ --- -title: Policy CSPs supported by HoloLens (1st gen) Development Edition -description: Policy CSPs supported by HoloLens (1st gen) Development Edition +title: Policies in Policy CSP supported by HoloLens (1st gen) Development Edition +description: Policies in Policy CSP supported by HoloLens (1st gen) Development Edition ms.reviewer: manager: dansimp ms.author: dansimp @@ -12,7 +12,7 @@ ms.localizationpriority: medium ms.date: 07/18/2019 --- -# Policy CSPs supported by HoloLens (1st gen) Development Edition +# Policies in Policy CSP supported by HoloLens (1st gen) Development Edition > [!div class="op_single_selector"] > diff --git a/windows/client-management/mdm/policy-csps-supported-by-hololens2.md b/windows/client-management/mdm/policies-in-policy-csp-supported-by-hololens2.md similarity index 98% rename from windows/client-management/mdm/policy-csps-supported-by-hololens2.md rename to windows/client-management/mdm/policies-in-policy-csp-supported-by-hololens2.md index e5cdb0f0ca..4757f9c46c 100644 --- a/windows/client-management/mdm/policy-csps-supported-by-hololens2.md +++ b/windows/client-management/mdm/policies-in-policy-csp-supported-by-hololens2.md @@ -1,6 +1,6 @@ --- -title: Policy CSPs supported by HoloLens 2 -description: Policy CSPs supported by HoloLens 2 +title: Policies in Policy CSP supported by HoloLens 2 +description: Policies in Policy CSP supported by HoloLens 2 ms.reviewer: manager: dansimp ms.author: dansimp @@ -12,7 +12,7 @@ ms.localizationpriority: medium ms.date: 05/11/2020 --- -# Policy CSPs supported by HoloLens 2 +# Policies in Policy CSP supported by HoloLens 2 > [!div class="op_single_selector"] > diff --git a/windows/client-management/mdm/policy-csps-supported-by-iot-core.md b/windows/client-management/mdm/policies-in-policy-csp-supported-by-iot-core.md similarity index 97% rename from windows/client-management/mdm/policy-csps-supported-by-iot-core.md rename to windows/client-management/mdm/policies-in-policy-csp-supported-by-iot-core.md index c43363b357..f3143ed222 100644 --- a/windows/client-management/mdm/policy-csps-supported-by-iot-core.md +++ b/windows/client-management/mdm/policies-in-policy-csp-supported-by-iot-core.md @@ -1,6 +1,6 @@ --- -title: Policy CSPs supported by Windows 10 IoT Core -description: Policy CSPs supported by Windows 10 IoT Core +title: Policies in Policy CSP supported by Windows 10 IoT Core +description: Policies in Policy CSP supported by Windows 10 IoT Core ms.reviewer: manager: dansimp ms.author: dansimp @@ -12,7 +12,7 @@ ms.localizationpriority: medium ms.date: 09/16/2019 --- -# Policy CSPs supported by Windows 10 IoT Core +# Policies in Policy CSP supported by Windows 10 IoT Core > [!div class="op_single_selector"] > diff --git a/windows/client-management/mdm/policy-csps-supported-by-iot-enterprise.md b/windows/client-management/mdm/policies-in-policy-csp-supported-by-iot-enterprise.md similarity index 96% rename from windows/client-management/mdm/policy-csps-supported-by-iot-enterprise.md rename to windows/client-management/mdm/policies-in-policy-csp-supported-by-iot-enterprise.md index 8e70dd707e..afb79c5bfe 100644 --- a/windows/client-management/mdm/policy-csps-supported-by-iot-enterprise.md +++ b/windows/client-management/mdm/policies-in-policy-csp-supported-by-iot-enterprise.md @@ -1,6 +1,6 @@ --- -title: Policy CSPs supported by Windows 10 IoT Enterprise -description: Policy CSPs supported by Windows 10 IoT Enterprise +title: Policies in Policy CSP supported by Windows 10 IoT Enterprise +description: Policies in Policy CSP supported by Windows 10 IoT Enterprise ms.reviewer: manager: dansimp ms.author: dansimp @@ -12,7 +12,7 @@ ms.localizationpriority: medium ms.date: 07/18/2019 --- -# Policy CSPs supported by Windows 10 IoT Enterprise +# Policies in Policy CSP supported by Windows 10 IoT Enterprise > [!div class="op_single_selector"] > diff --git a/windows/client-management/mdm/policy-csps-supported-by-surface-hub.md b/windows/client-management/mdm/policies-in-policy-csp-supported-by-surface-hub.md similarity index 97% rename from windows/client-management/mdm/policy-csps-supported-by-surface-hub.md rename to windows/client-management/mdm/policies-in-policy-csp-supported-by-surface-hub.md index 1d89eb88de..e39b0aef27 100644 --- a/windows/client-management/mdm/policy-csps-supported-by-surface-hub.md +++ b/windows/client-management/mdm/policies-in-policy-csp-supported-by-surface-hub.md @@ -1,6 +1,6 @@ --- -title: Policy CSPs supported by Microsoft Surface Hub -description: Policy CSPs supported by Microsoft Surface Hub +title: Policies in Policy CSP supported by Microsoft Surface Hub +description: Policies in Policy CSP supported by Microsoft Surface Hub ms.reviewer: manager: dansimp ms.author: dansimp @@ -12,7 +12,7 @@ ms.localizationpriority: medium ms.date: 07/22/2020 --- -# Policy CSPs supported by Microsoft Surface Hub +# Policies in Policy CSP supported by Microsoft Surface Hub - [ApplicationManagement/AllowAppStoreAutoUpdate](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-applicationmanagement#applicationmanagement-allowappstoreautoupdate) diff --git a/windows/client-management/mdm/policy-csps-that-can-be-set-using-eas.md b/windows/client-management/mdm/policies-in-policy-csp-that-can-be-set-using-eas.md similarity index 90% rename from windows/client-management/mdm/policy-csps-that-can-be-set-using-eas.md rename to windows/client-management/mdm/policies-in-policy-csp-that-can-be-set-using-eas.md index 171652aa2b..4fa3380c87 100644 --- a/windows/client-management/mdm/policy-csps-that-can-be-set-using-eas.md +++ b/windows/client-management/mdm/policies-in-policy-csp-that-can-be-set-using-eas.md @@ -1,6 +1,6 @@ --- -title: Policy CSPs that can be set using Exchange Active Sync (EAS) -description: Policy CSPs that can be set using Exchange Active Sync (EAS) +title: Policies in Policy CSP that can be set using Exchange Active Sync (EAS) +description: Policies in Policy CSP that can be set using Exchange Active Sync (EAS) ms.reviewer: manager: dansimp ms.author: dansimp @@ -12,7 +12,7 @@ ms.localizationpriority: medium ms.date: 07/18/2019 --- -# Policy CSPs that can be set using Exchange Active Sync (EAS) +# Policies in Policy CSP that can be set using Exchange Active Sync (EAS) - [Camera/AllowCamera](policy-csp-camera.md#camera-allowcamera) - [Cellular/ShowAppCellularAccessUI](policy-csp-cellular.md#cellular-showappcellularaccessui) diff --git a/windows/client-management/mdm/policy-configuration-service-provider.md b/windows/client-management/mdm/policy-configuration-service-provider.md index 0349f6cde6..ba400e3ffb 100644 --- a/windows/client-management/mdm/policy-configuration-service-provider.md +++ b/windows/client-management/mdm/policy-configuration-service-provider.md @@ -4901,27 +4901,27 @@ The following diagram shows the Policy configuration service provider in tree fo -## Policy CSPs supported by Group Policy and ADMX-backed policy CSPs -- [Policy CSPs supported by Group Policy](policy-csps-supported-by-group-policy.md) -- [ADMX-backed policy CSPs](policy-csps-admx-backed.md) +## Policies in Policy CSP supported by Group Policy and ADMX-backed policies in Policy CSP +- [Policies in Policy CSP supported by Group Policy](policy-csps-supported-by-group-policy.md) +- [ADMX-backed policies in Policy CSP](policy-csps-admx-backed.md) > [!NOTE] -> Not all Policy CSPs supported by Group Policy are ADMX-backed. For more details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md). +> Not all Policies in Policy CSP supported by Group Policy are ADMX-backed. For more details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md). -## Policy CSPs supported by HoloLens devices -- [Policy CSPs supported by HoloLens 2](policy-csps-supported-by-hololens2.md) -- [Policy CSPs supported by HoloLens (1st gen) Commercial Suite](policy-csps-supported-by-hololens-1st-gen-commercial-suite.md) -- [Policy CSPs supported by HoloLens (1st gen) Development Edition](policy-csps-supported-by-hololens-1st-gen-development-edition.md) +## Policies in Policy CSP supported by HoloLens devices +- [Policies in Policy CSP supported by HoloLens 2](policy-csps-supported-by-hololens2.md) +- [Policies in Policy CSP supported by HoloLens (1st gen) Commercial Suite](policy-csps-supported-by-hololens-1st-gen-commercial-suite.md) +- [Policies in Policy CSP supported by HoloLens (1st gen) Development Edition](policy-csps-supported-by-hololens-1st-gen-development-edition.md) -## Policy CSPs supported by Windows 10 IoT -- [Policy CSPs supported by Windows 10 IoT Enterprise](policy-csps-supported-by-iot-enterprise.md) -- [Policy CSPs supported by Windows 10 IoT Core](policy-csps-supported-by-iot-core.md) +## Policies in Policy CSP supported by Windows 10 IoT +- [Policies in Policy CSP supported by Windows 10 IoT Enterprise](policy-csps-supported-by-iot-enterprise.md) +- [Policies in Policy CSP supported by Windows 10 IoT Core](policy-csps-supported-by-iot-core.md) -## Policy CSPs supported by Microsoft Surface Hub -- [Policy CSPs supported by Microsoft Surface Hub](policy-csps-supported-by-surface-hub.md) +## Policies in Policy CSP supported by Microsoft Surface Hub +- [Policies in Policy CSP supported by Microsoft Surface Hub](policy-csps-supported-by-surface-hub.md) -## Policy CSPs that can be set using Exchange ActiveSync (EAS) -- [Policy CSPs that can be set using Exchange ActiveSync (EAS)](policy-csps-that-can-be-set-using-eas.md) +## Policies in Policy CSP that can be set using Exchange ActiveSync (EAS) +- [Policies in Policy CSP that can be set using Exchange ActiveSync (EAS)](policy-csps-that-can-be-set-using-eas.md) ## Related topics diff --git a/windows/client-management/mdm/policy-csp-controlpolicyconflict.md b/windows/client-management/mdm/policy-csp-controlpolicyconflict.md index 9a867b0778..2cde160250 100644 --- a/windows/client-management/mdm/policy-csp-controlpolicyconflict.md +++ b/windows/client-management/mdm/policy-csp-controlpolicyconflict.md @@ -100,7 +100,7 @@ The [Policy DDF](policy-ddf-file.md) contains the following tags to identify the - \ - \ -For the list MDM-GP mapping list, see [Policy CSPs supported by Group Policy +For the list MDM-GP mapping list, see [Policies in Policy CSP supported by Group Policy ](policy-csps-supported-by-group-policy.md). The MDM Diagnostic report shows the applied configurations states of a device including policies, certificates, configuration sources, and resource information. The report includes a list of blocked GP settings because MDM equivalent is configured, if any. To get the diagnostic report, go to **Settings** > **Accounts** > **Access work or school** > and then click the desired work or school account. Scroll to the bottom of the page to **Advanced Diagnostic Report** and then click **Create Report**. From 06fb11bd53e606a642a9c3daa863c7455d505bcc Mon Sep 17 00:00:00 2001 From: Aasawari Navathe Date: Wed, 7 Oct 2020 18:06:22 -0700 Subject: [PATCH 72/76] Boolean value that indicates compliance with the enterprise encryption policy for OS (system) drives --- windows/client-management/mdm/devicestatus-csp.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/client-management/mdm/devicestatus-csp.md b/windows/client-management/mdm/devicestatus-csp.md index 06e4d21323..97daf7a3ce 100644 --- a/windows/client-management/mdm/devicestatus-csp.md +++ b/windows/client-management/mdm/devicestatus-csp.md @@ -107,7 +107,7 @@ Supported operation is Get. Node for the compliance query. **DeviceStatus/Compliance/EncryptionCompliance** -Boolean value that indicates compliance with the enterprise encryption policy. The value is one of the following: +Boolean value that indicates compliance with the enterprise encryption policy for OS (system) drives. The value is one of the following: - 0 - not encrypted - 1 - encrypted From 5713121545fdc0cf96777a410047500c510d1837 Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Thu, 8 Oct 2020 02:12:53 -0700 Subject: [PATCH 73/76] update --- windows/deployment/upgrade/quick-fixes.md | 88 ++++++++++--------- .../upgrade/resolution-procedures.md | 4 +- 2 files changed, 49 insertions(+), 43 deletions(-) diff --git a/windows/deployment/upgrade/quick-fixes.md b/windows/deployment/upgrade/quick-fixes.md index 3f2fc11c16..e69527eeb0 100644 --- a/windows/deployment/upgrade/quick-fixes.md +++ b/windows/deployment/upgrade/quick-fixes.md @@ -38,7 +38,7 @@ The Microsoft Virtual Agent provided by [Microsoft Support](https://support.micr
  • Check the system drive for errors and attempt repairs. More information.
  • Run the Windows Update troubleshooter. More information.
  • Attempt to restore and repair system files. More information.
    • -
  • Check for unsigned drivers and update or remove them. More information.
    • +
  • Check for unsigned drivers and update or repair them. More information.
  • Update Windows so that all available recommended updates are installed, and ensure the computer is rebooted if this is necessary to complete installation of an update. More information.
  • Temporarily uninstall non-Microsoft antivirus software. More information.
    • @@ -156,9 +156,15 @@ To check and repair system files: > It may take several minutes for the command operations to be completed. For more information, see [Repair a Windows Image](https://msdn.microsoft.com/windows/hardware/commercialize/manufacture/desktop/repair-a-windows-image) and [Use the System File Checker tool](https://support.microsoft.com/help/929833/use-the-system-file-checker-tool-to-repair-missing-or-corrupted-system). -### Remove unsigned drivers +### Repair unsigned drivers -Drivers that are not properly signed can block the upgrade process. To check your system for unsigned drivers: +Drivers that are not properly signed can block the upgrade process. Drivers might not be properly signed if you: +- Disabled driver signature verification (highly not recommended). +- A catalog file used to sign a driver is corrupt or missing. + +Catalog files are used to sign drivers. If a catalog file is corrupt or missing, the driver will appear to be unsigned, even though it should be signed. This can cause the upgrade process to fail. To restore the catalog file, reinstall the driver or copy the catalog file from another device. You might need to analyze another device to determine the catalog file that is associated with the unsigned driver. All drivers should be signed to ensure the upgrade process works. + +To check your system for unsigned drivers: 1. Click **Start**. 2. Type **command**. @@ -169,53 +175,53 @@ Drivers that are not properly signed can block the upgrade process. To check you ![File Signature Verification](../images/sigverif.png) -7. After the scanning process is complete, click **Advanced**, and then click **View Log**. -8. Locate drivers in the log file that are unsigned and remove or update them using Device Manager. For more information, see [Using Device Manager to uninstall devices and driver packages](https://docs.microsoft.com/windows-hardware/drivers/install/using-device-manager-to-uninstall-devices-and-driver-packages). +7. After the scanning process is complete, if you see **Your files have been scanned and verified as digitally signed** then you have no unsigned drivers. Otherwise, you will see **The following files have not been digitally signed** and a list will be provided with name, location, and version of all unsigned drivers. +8. To view and save a log file, click **Advanced**, and then click **View Log**. Save the log file if desired. +9. Locate drivers in the log file that are unsigned, write down the location and file names. Also write down the catalog that is associated to the driver if it is provided. If the name of a catalog file is not provided you might need to analyze another device that has the same driver with sigverif and sigcheck (described below). +10. Download [sigcheck.zip](https://download.sysinternals.com/files/Sigcheck.zip) and extract the tool to a directory on your computer, for example: **C:\sigcheck**. ->[!NOTE] ->If a file is corrupted, it might display as unsigned. Be sure to [repair the system drive](#repair-the-system-drive) and [repair system files](#repair-system-files) before attempting to replace unsigned drivers. - -#### Optional: Use sigcheck - -[Sigcheck](https://docs.microsoft.com/sysinternals/downloads/sigcheck) is a tool that you can download and use to review digital signature details of a file. - -To use sigcheck: - -1. Download [sigcheck.zip](https://download.sysinternals.com/files/Sigcheck.zip) and extract the tool to a directory on your computer, for example: **C:\sigcheck**. -2. Click **Start**. -2. Type **command**. -3. Right-click **Command Prompt** and then left-click **Run as administrator**. -4. If you are prompted by UAC, click **Yes**. -5. In the command window, use the **cd** command to switch to the directory where you extracted sigcheck, for example **cd c:\sigcheck**. -6. A list of drivers with their path is displayed in the File Signature Verification tool (step #7 in the previous procedure). Optionally, you can generate a list of drivers using driverquery.exe. To use driverquery, type **driverquery /v > c:\sigcheck\drivers.txt** and press ENTER. See the following example: - - ```cmd - C:\Sigcheck>Driverquery /v > C:\sigcheck\drivers.txt + [Sigcheck](https://docs.microsoft.com/sysinternals/downloads/sigcheck) is a tool that you can download and use to review digital signature details of a file. To use sigcheck: +11. In the command window, use the **cd** command to switch to the directory where you extracted sigcheck, for example **cd c:\sigcheck**. +12. Using the list of unsigned drivers and their associated paths that you obtained from the File Signature Verification tool, run sigcheck to obtain details about the driver, including the catalog file used for signing. Type **sigcheck64 -u -e \** and press ENTER. See the following example: ``` -7. Open the drivers.txt file and locate the problem driver that was reported by sigverif in the [procedure above](#remove-unsigned-drivers). Copy the path to the driver. -8. To check the driver, type **sigcheck64 -u -e \** and press ENTER. See the following example: - - ``` - C:\Sigcheck>sigcheck64.exe -i c:\windows\system32\DolbyMATEnc.dll + C:\Sigcheck>sigcheck64.exe -i c:\windows\system32\drivers\afd.sys Sigcheck v2.80 - File version and signature viewer Copyright (C) 2004-2020 Mark Russinovich Sysinternals - www.sysinternals.com - - c:\windows\system32\DolbyMATEnc.dll: - Verified: Unsigned - Link date: 6:43 PM 9/20/2028 - Publisher: n/a - Company: Microsoft Corporation - Description: Dolby MAT Encoder DLL - Product: Microsoft« Windows« Operating System - Prod version: 10.0.18362.1 - File version: 10.0.18362.1 (WinBuild.160101.0800) - MachineType: 64-bit + c:\windows\system32\drivers\afd.sys: + Verified: Signed + Signing date: 6:18 PM 11/29/2017 + Signing date: 6:18 PM 11/29/2017 + Catalog: C:\Windows\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\Package_163_for_KB4054518~31bf3856ad364e35~x86~~6.1.1.2.cat + Signers: + Microsoft Windows + Cert Status: This certificate or one of the certificates in the certificate chain is not time valid. + Valid Usage: NT5 Crypto, Code Signing + Cert Issuer: Microsoft Windows Verification PCA + Serial Number: 33 00 00 00 4B 76 63 2D 24 A2 39 9A 8B 00 01 00 00 00 4B + Thumbprint: B8037C46D0DB7A8CEE502407469B0EE3234D3365 + Algorithm: sha1RSA + Valid from: 11:46 AM 3/1/2017 + Valid to: 11:46 AM 5/9/2018 + (output truncated) ``` -In addition to unsigned drivers, drivers might be signed with an invalid certificate, requiring the driver to be updated or removed so that Windows upgrade can continue. Sigcheck will report whether or not the certificate chain is valid. + +13. Optionally, you can generate a list of drivers using driverquery.exe, which is included with Windows. To save a list of signed and unsigned drivers with driverquery, type **driverquery /si > c:\drivers.txt** and press ENTER. See the following example: + + ```cmd + C:\>Driverquery /si + + DeviceName InfName IsSigned Manufacturer + ============================== ============= ======== ========================= + Microsoft ISATAP Adapter nettun.inf TRUE Microsoft + Generic volume shadow copy volsnap.inf TRUE Microsoft + Generic volume volume.inf TRUE Microsoft + (truncated) + ``` + For more information about using driverquery, see [Two Minute Drill: DriverQuery.exe](https://techcommunity.microsoft.com/t5/ask-the-performance-team/two-minute-drill-driverquery-exe/ba-p/374977) and [driverquery](https://docs.microsoft.com/windows-server/administration/windows-commands/driverquery). ### Update Windows diff --git a/windows/deployment/upgrade/resolution-procedures.md b/windows/deployment/upgrade/resolution-procedures.md index 6b8a9587d2..1d75d19367 100644 --- a/windows/deployment/upgrade/resolution-procedures.md +++ b/windows/deployment/upgrade/resolution-procedures.md @@ -36,7 +36,7 @@ A frequently observed [result code](upgrade-error-codes.md#result-codes) is 0xC1 The device install log is particularly helpful if rollback occurs during the sysprep operation (extend code 0x30018). -To resolve a rollback that was caused by driver conflicts, try running setup using a minimal set of drivers and startup programs by performing a [clean boot](https://support.microsoft.com/kb/929135) before initiating the upgrade process. Also check to be sure that your drivers are properly signed. For more information, see [Remove unsigned drivers](quick-fixes.md#remove-unsigned-drivers). +To resolve a rollback that was caused by driver conflicts, try running setup using a minimal set of drivers and startup programs by performing a [clean boot](https://support.microsoft.com/kb/929135) before initiating the upgrade process. Also check to be sure that your drivers are properly signed. For more information, see [Remove unsigned drivers](quick-fixes.md#repair-unsigned-drivers). See the following general troubleshooting procedures associated with a result code of 0xC1900101:

    @@ -49,7 +49,7 @@ See the following general troubleshooting procedures associated with a result co | 0xC1900101 - 0x30018 | Disconnect all peripheral devices that are connected to the system, except for the mouse, keyboard and display.
    Contact your hardware vendor to obtain updated device drivers.
    Ensure that "Download and install updates (recommended)" is accepted at the start of the upgrade process. | A device driver has stopped responding to setup.exe during the upgrade process. | | 0xC1900101 - 0x3000D | Disconnect all peripheral devices that are connected to the system, except for the mouse, keyboard and display.
    Update or uninstall the display driver. | Installation failed during the FIRST_BOOT phase while attempting the MIGRATE_DATA operation.
    This can occur due to a problem with a display driver. | | 0xC1900101 - 0x4000D | Check supplemental rollback logs for a setupmem.dmp file, or event logs for any unexpected reboots or errors.
    Review the rollback log and determine the stop code.
    The rollback log is located in the $Windows.~BT\Sources\Rollback folder. An example analysis is shown below. This example is not representative of all cases:
     
    Info SP Crash 0x0000007E detected
    Info SP Module name :
    Info SP Bugcheck parameter 1 : 0xFFFFFFFFC0000005
    Info SP Bugcheck parameter 2 : 0xFFFFF8015BC0036A
    Info SP Bugcheck parameter 3 : 0xFFFFD000E5D23728
    Info SP Bugcheck parameter 4 : 0xFFFFD000E5D22F40
    Info SP Cannot recover the system.
    Info SP Rollback: Showing splash window with restoring text: Restoring your previous version of Windows.
     
    Typically, there is a dump file for the crash to analyze. If you are not equipped to debug the dump, then attempt the following basic troubleshooting procedures:
     
    1. Make sure you have enough disk space.
    2. If a driver is identified in the bug check message, disable the driver or check with the manufacturer for driver updates.
    3. Try changing video adapters.
    4. Check with your hardware vendor for any BIOS updates.
    5. Disable BIOS memory options such as caching or shadowing. | A rollback occurred due to a driver configuration issue.
    Installation failed during the second boot phase while attempting the MIGRATE_DATA operation.
    This can occur because of incompatible drivers. | -| 0xC1900101 - 0x40017 | Clean boot into Windows, and then attempt the upgrade to Windows 10. For more information, see [How to perform a clean boot in Windows](https://support.microsoft.com/kb/929135).
     
    Ensure that you select the option to "Download and install updates (recommended)." Also be sure to [remove unsigned drivers](quick-fixes.md#remove-unsigned-drivers).
     
    Computers that run Citrix VDA
    You may see this message after you upgrade a computer from Windows 10, version 1511 to Windows 10, version 1607. After the second system restart, the system generates this error and then rolls back to the previous version. This problem has also been observed in upgrades to Windows 8.1 and Windows 8.
     
    This problem occurs because the computer has Citrix Virtual Delivery Agent (VDA) installed. Citrix VDA installs device drivers and a file system filter driver (CtxMcsWbc). This Citrix filter driver prevents the upgrade from writing changes to the disk, so the upgrade cannot complete and the system rolls back.
     
    **Resolution**
     
    To resolve this problem, install [Cumulative update for Windows 10 Version 1607 and Windows Server 2016: November 8, 2016](https://support.microsoft.com/help/3200970/cumulative-update-for-windows-10-version-1607-and-windows-server-2016).
     
    You can work around this problem in two ways:
     
    **Workaround 1**
     
    1. Use the VDA setup application (VDAWorkstationSetup_7.11) to uninstall Citrix VDA.
    2. Run the Windows upgrade again.
    3. Reinstall Citrix VDA.
     
    **Workaround 2**
     
    If you cannot uninstall Citrix VDA, follow these steps to work around this problem:
     
    1. In Registry Editor, go to the following subkey:
    **HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e967-e325-11ce-bfc1-08002be10318}\CtxMcsWbc**
    2. Change the value of the **Start** entry from **0** to **4**. This change disables the Citrix MCS cache service.
    3. Go to the following subkey:
    **HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e967-e325-11ce-bfc1-08002be10318}**
    4. Delete the **CtxMcsWbc** entry.
    5. Restart the computer, and then try the upgrade again.
     
    **Non-Microsoft information disclaimer**
    The non-Microsoft products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products. | Windows 10 upgrade failed after the second reboot.
    This is usually caused by a faulty driver. For example: antivirus filter drivers or encryption drivers. | +| 0xC1900101 - 0x40017 | Clean boot into Windows, and then attempt the upgrade to Windows 10. For more information, see [How to perform a clean boot in Windows](https://support.microsoft.com/kb/929135).
     
    Ensure that you select the option to "Download and install updates (recommended)." Also be sure to [remove unsigned drivers](quick-fixes.md#repair-unsigned-drivers).
     
    Computers that run Citrix VDA
    You may see this message after you upgrade a computer from Windows 10, version 1511 to Windows 10, version 1607. After the second system restart, the system generates this error and then rolls back to the previous version. This problem has also been observed in upgrades to Windows 8.1 and Windows 8.
     
    This problem occurs because the computer has Citrix Virtual Delivery Agent (VDA) installed. Citrix VDA installs device drivers and a file system filter driver (CtxMcsWbc). This Citrix filter driver prevents the upgrade from writing changes to the disk, so the upgrade cannot complete and the system rolls back.
     
    **Resolution**
     
    To resolve this problem, install [Cumulative update for Windows 10 Version 1607 and Windows Server 2016: November 8, 2016](https://support.microsoft.com/help/3200970/cumulative-update-for-windows-10-version-1607-and-windows-server-2016).
     
    You can work around this problem in two ways:
     
    **Workaround 1**
     
    1. Use the VDA setup application (VDAWorkstationSetup_7.11) to uninstall Citrix VDA.
    2. Run the Windows upgrade again.
    3. Reinstall Citrix VDA.
     
    **Workaround 2**
     
    If you cannot uninstall Citrix VDA, follow these steps to work around this problem:
     
    1. In Registry Editor, go to the following subkey:
    **HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e967-e325-11ce-bfc1-08002be10318}\CtxMcsWbc**
    2. Change the value of the **Start** entry from **0** to **4**. This change disables the Citrix MCS cache service.
    3. Go to the following subkey:
    **HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e967-e325-11ce-bfc1-08002be10318}**
    4. Delete the **CtxMcsWbc** entry.
    5. Restart the computer, and then try the upgrade again.
     
    **Non-Microsoft information disclaimer**
    The non-Microsoft products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products. | Windows 10 upgrade failed after the second reboot.
    This is usually caused by a faulty driver. For example: antivirus filter drivers or encryption drivers. | ## 0x800xxxxx From 96a295c4f02ced1e7a2ea0f33f9ee8a9d84535bf Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Thu, 8 Oct 2020 02:34:44 -0700 Subject: [PATCH 74/76] up --- windows/deployment/upgrade/quick-fixes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/upgrade/quick-fixes.md b/windows/deployment/upgrade/quick-fixes.md index e69527eeb0..f1d655d44b 100644 --- a/windows/deployment/upgrade/quick-fixes.md +++ b/windows/deployment/upgrade/quick-fixes.md @@ -183,7 +183,7 @@ To check your system for unsigned drivers: [Sigcheck](https://docs.microsoft.com/sysinternals/downloads/sigcheck) is a tool that you can download and use to review digital signature details of a file. To use sigcheck: 11. In the command window, use the **cd** command to switch to the directory where you extracted sigcheck, for example **cd c:\sigcheck**. -12. Using the list of unsigned drivers and their associated paths that you obtained from the File Signature Verification tool, run sigcheck to obtain details about the driver, including the catalog file used for signing. Type **sigcheck64 -u -e \** and press ENTER. See the following example: +12. Using the list of unsigned drivers and their associated paths that you obtained from the File Signature Verification tool, run sigcheck to obtain details about the driver, including the catalog file used for signing. Type **sigcheck64 -i \** and press ENTER (or sigcheck -i for a 32 bit OS). See the following example: ``` C:\Sigcheck>sigcheck64.exe -i c:\windows\system32\drivers\afd.sys From bf9fdab616073a163800b1c819fd847803cb5ea5 Mon Sep 17 00:00:00 2001 From: Tina Burden Date: Thu, 8 Oct 2020 08:54:03 -0700 Subject: [PATCH 75/76] pencil edit --- windows/client-management/mdm/devicestatus-csp.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/windows/client-management/mdm/devicestatus-csp.md b/windows/client-management/mdm/devicestatus-csp.md index 97daf7a3ce..6ab35ba018 100644 --- a/windows/client-management/mdm/devicestatus-csp.md +++ b/windows/client-management/mdm/devicestatus-csp.md @@ -36,9 +36,8 @@ Supported operation is Get. **DeviceStatus/CellularIdentities** Required. Node for queries on the SIM cards. -> **Note**  Multiple SIMs are supported. - - +>[!NOTE] +>Multiple SIMs are supported. **DeviceStatus/CellularIdentities/***IMEI* The unique International Mobile Station Equipment Identity (IMEI) number of the mobile device. An IMEI is present for each SIM card on the device. From fce88befcc084ff10f297162d632cc11c86ed68a Mon Sep 17 00:00:00 2001 From: ManikaDhiman Date: Thu, 8 Oct 2020 09:34:01 -0700 Subject: [PATCH 76/76] minor update to trigger build --- .../client-management/mdm/policies-in-policy-csp-admx-backed.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/client-management/mdm/policies-in-policy-csp-admx-backed.md b/windows/client-management/mdm/policies-in-policy-csp-admx-backed.md index 75ac21a8b3..5a62b30b51 100644 --- a/windows/client-management/mdm/policies-in-policy-csp-admx-backed.md +++ b/windows/client-management/mdm/policies-in-policy-csp-admx-backed.md @@ -9,7 +9,7 @@ ms.prod: w10 ms.technology: windows author: manikadhiman ms.localizationpriority: medium -ms.date: 08/18/2020 +ms.date: 10/08/2020 --- # ADMX-backed policies in Policy CSP