Date: Thu, 26 May 2022 15:31:50 -0700
Subject: [PATCH 20/61] Update
network-security-restrict-ntlm-ntlm-authentication-in-this-domain.md
---
...-security-restrict-ntlm-ntlm-authentication-in-this-domain.md | 1 -
1 file changed, 1 deletion(-)
diff --git a/windows/security/threat-protection/security-policy-settings/network-security-restrict-ntlm-ntlm-authentication-in-this-domain.md b/windows/security/threat-protection/security-policy-settings/network-security-restrict-ntlm-ntlm-authentication-in-this-domain.md
index 5b35621c9b..0c1396e74f 100644
--- a/windows/security/threat-protection/security-policy-settings/network-security-restrict-ntlm-ntlm-authentication-in-this-domain.md
+++ b/windows/security/threat-protection/security-policy-settings/network-security-restrict-ntlm-ntlm-authentication-in-this-domain.md
@@ -14,7 +14,6 @@ manager: dansimp
audience: ITPro
ms.collection: M365-security-compliance
ms.topic: conceptual
-ms.date: 04/19/2017
ms.technology: windows-sec
---
From afa7f95d1972a9e4934a66f06e1bc01d77614bcf Mon Sep 17 00:00:00 2001
From: itsrlyAria <82474610+itsrlyAria@users.noreply.github.com>
Date: Fri, 27 May 2022 14:42:36 -0700
Subject: [PATCH 21/61] Update windows/deployment/update/wufb-wsus.md
Co-authored-by: JohanFreelancer9 <48568725+JohanFreelancer9@users.noreply.github.com>
---
windows/deployment/update/wufb-wsus.md | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/windows/deployment/update/wufb-wsus.md b/windows/deployment/update/wufb-wsus.md
index 6df97965dc..a93c10f142 100644
--- a/windows/deployment/update/wufb-wsus.md
+++ b/windows/deployment/update/wufb-wsus.md
@@ -57,7 +57,8 @@ To help you better understand the scan source policy, see the default scan behav
> [!TIP]
> The only two relevant policies for where your updates come from are the specify scan source policy and whether or not you have configured a WSUS server. This should simplify the configuration options.
-Note - If you have devices configured for WSUS and do not configure the scan source policy for feature updates to come from Windows update or set any Windows Update for Business offering policies, then users who click "Check online for updates" on the Settings page may see the optional upgrade to Windows 11. We recommend configuring the scan source policy or a Windows Update for Business offering policy to prevent such.
+> [!NOTE]
+> If you have devices configured for WSUS and do not configure the scan source policy for feature updates to come from Windows update or set any Windows Update for Business offering policies, then users who select "Check online for updates" on the Settings page may see the optional upgrade to Windows 11. We recommend configuring the scan source policy or a Windows Update for Business offering policy to prevent such.
## Configure the scan sources
From 0c2b0bc5fdf4aebcb5860cd202def33ecf676a90 Mon Sep 17 00:00:00 2001
From: Michael Morten Sonne <49366751+michaelmsonne@users.noreply.github.com>
Date: Sun, 29 May 2022 15:25:41 +0200
Subject: [PATCH 22/61] Update bitlocker-overview-and-requirements-faq.yml
Add Windows 11
---
.../bitlocker/bitlocker-overview-and-requirements-faq.yml | 1 +
1 file changed, 1 insertion(+)
diff --git a/windows/security/information-protection/bitlocker/bitlocker-overview-and-requirements-faq.yml b/windows/security/information-protection/bitlocker/bitlocker-overview-and-requirements-faq.yml
index 2b8382dfa8..df962a8ff5 100644
--- a/windows/security/information-protection/bitlocker/bitlocker-overview-and-requirements-faq.yml
+++ b/windows/security/information-protection/bitlocker/bitlocker-overview-and-requirements-faq.yml
@@ -23,6 +23,7 @@ title: BitLocker Overview and Requirements FAQ
summary: |
**Applies to**
- Windows 10
+ - Windows 11
sections:
From 0dfd31ea4be36b1ce71afa70eec8609cbd018f09 Mon Sep 17 00:00:00 2001
From: Michael Morten Sonne <49366751+michaelmsonne@users.noreply.github.com>
Date: Sun, 29 May 2022 15:28:41 +0200
Subject: [PATCH 23/61] Update bitlocker-overview.md
Change titel
---
.../information-protection/bitlocker/bitlocker-overview.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/windows/security/information-protection/bitlocker/bitlocker-overview.md b/windows/security/information-protection/bitlocker/bitlocker-overview.md
index a5d4bf4e49..41c1be27f1 100644
--- a/windows/security/information-protection/bitlocker/bitlocker-overview.md
+++ b/windows/security/information-protection/bitlocker/bitlocker-overview.md
@@ -1,5 +1,5 @@
---
-title: BitLocker (Windows 10)
+title: BitLocker
description: This topic provides a high-level overview of BitLocker, including a list of system requirements, practical applications, and deprecated features.
ms.assetid: 40526fcc-3e0d-4d75-90e0-c7d0615f33b2
ms.author: dansimp
@@ -102,4 +102,4 @@ When installing the BitLocker optional component on a server you will also need
| [Protect BitLocker from pre-boot attacks](./bitlocker-countermeasures.md)| This detailed guide will help you understand the circumstances under which the use of pre-boot authentication is recommended for devices running Windows 11, Windows 10, Windows 8.1, Windows 8, or Windows 7; and when it can be safely omitted from a device’s configuration. |
| [Troubleshoot BitLocker](troubleshoot-bitlocker.md) | This guide describes the resources that can help you troubleshoot BitLocker issues, and provides solutions for several common BitLocker issues. |
| [Protecting cluster shared volumes and storage area networks with BitLocker](protecting-cluster-shared-volumes-and-storage-area-networks-with-bitlocker.md)| This topic for IT pros describes how to protect CSVs and SANs with BitLocker.|
-| [Enabling Secure Boot and BitLocker Device Encryption on Windows IoT Core](/windows/iot-core/secure-your-device/SecureBootAndBitLocker) | This topic covers how to use BitLocker with Windows IoT Core |
\ No newline at end of file
+| [Enabling Secure Boot and BitLocker Device Encryption on Windows IoT Core](/windows/iot-core/secure-your-device/SecureBootAndBitLocker) | This topic covers how to use BitLocker with Windows IoT Core |
From 4c089352feeee03b4eb6c2452cc30b4e5fda6974 Mon Sep 17 00:00:00 2001
From: Alekhya Jupudi <89069896+alekyaj@users.noreply.github.com>
Date: Mon, 30 May 2022 11:18:44 +0530
Subject: [PATCH 24/61] Fixing format
---
windows/client-management/mdm/dmclient-csp.md | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/windows/client-management/mdm/dmclient-csp.md b/windows/client-management/mdm/dmclient-csp.md
index 4f5e9e65c0..6a0e95812a 100644
--- a/windows/client-management/mdm/dmclient-csp.md
+++ b/windows/client-management/mdm/dmclient-csp.md
@@ -514,11 +514,11 @@ This node tracks the status of a Recovery request from the InitiateRecovery node
0 - No Recovery request has been processed.
1 - Recovery is in Process.
-2 - Recovery has finished successfully.
+2 - Recovery has finished successfully.
3 - Recovery has failed to start because TPM is not available.
-4 - Recovery has failed to start because AAD keys are not protected by the TPM.
-5 - Recovery has failed to start because the MDM keys are already protected by the TPM.
-6 - Recovery has failed to start because the TPM is not ready for attestation.
+4 - Recovery has failed to start because AAD keys are not protected by the TPM.
+5 - Recovery has failed to start because the MDM keys are already protected by the TPM.
+6 - Recovery has failed to start because the TPM is not ready for attestation.
7 - Recovery has failed because the client cannot authenticate to the server.
8 - Recovery has failed because the server has rejected the client's request.
From 93ca4045a0270658f4f05abda27b7e488c03d376 Mon Sep 17 00:00:00 2001
From: Harman Thind <63820404+hathin@users.noreply.github.com>
Date: Tue, 31 May 2022 08:52:31 -0700
Subject: [PATCH 25/61] Update check name
Windows 10 update rings to
Update rings for Windows 10 or later
---
.../windows-autopatch/prepare/windows-autopatch-fix-issues.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/windows/deployment/windows-autopatch/prepare/windows-autopatch-fix-issues.md b/windows/deployment/windows-autopatch/prepare/windows-autopatch-fix-issues.md
index 8dff734be5..eeb5801be0 100644
--- a/windows/deployment/windows-autopatch/prepare/windows-autopatch-fix-issues.md
+++ b/windows/deployment/windows-autopatch/prepare/windows-autopatch-fix-issues.md
@@ -38,7 +38,7 @@ This setting must be turned on to avoid a "lack of permissions" error when we in
| ----- | ----- |
| Not ready | Allow access to unlicensed admins should be turned on. Without this setting enabled, errors can occur when we try to access your Azure AD organization for service. You can safely enable this setting without worrying about security implications. The scope of access is defined by the roles assigned to users, including our operations staff.For more information, see [Unlicensed admins](/mem/intune/fundamentals/unlicensed-admins). |
-### Windows 10 update rings
+### Update rings for Windows 10 or later
Your "Windows 10 update ring" policy in Intune must not target any Windows Autopatch devices.
From 71e4ce24d1efd46a54f55b43b6021cede7b62630 Mon Sep 17 00:00:00 2001
From: Andre Della Monica
Date: Tue, 31 May 2022 11:28:21 -0500
Subject: [PATCH 26/61] Updates to docs
---
.../windows-autopatch-register-devices.md | 23 +++++++++++++------
1 file changed, 16 insertions(+), 7 deletions(-)
diff --git a/windows/deployment/windows-autopatch/deploy/windows-autopatch-register-devices.md b/windows/deployment/windows-autopatch/deploy/windows-autopatch-register-devices.md
index 7a6f929085..7d549fcbea 100644
--- a/windows/deployment/windows-autopatch/deploy/windows-autopatch-register-devices.md
+++ b/windows/deployment/windows-autopatch/deploy/windows-autopatch-register-devices.md
@@ -1,7 +1,7 @@
---
title: Register your devices
description: This article details how to register devices in Autopatch
-ms.date: 05/30/2022
+ms.date: 05/31/2022
ms.prod: w11
ms.technology: windows
ms.topic: how-to
@@ -9,7 +9,7 @@ ms.localizationpriority: medium
author: tiaraquan
ms.author: tiaraquan
manager: dougeby
-msreviewer: hathind
+msreviewer: andredm7
---
# Register your devices
@@ -25,16 +25,22 @@ Windows Autopatch to take over software updates management of supported devices
- [Microsoft Edge updates](../operate/windows-autopatch-edge.md)
- [Microsoft Teams updates](../operate/windows-autopatch-teams.md)
-You must choose what devices to manage with Windows Autopatch by adding either devices through direct membership or by adding other Azure Active Directory (Azure AD) dynamic groups into the Azure Active Directory assigned **Windows Autopatch Device Registration** group. Windows Autopatch runs every hour to discover new devices added to this group. Once new devices are discovered, Windows Autopatch attempts to register these devices into its service.
+You must choose what devices to manage with Windows Autopatch by adding either devices through direct membership or by adding other Azure Active Directory (Azure AD) dynamic/assigned groups into the Azure Active Directory assigned **Windows Autopatch Device Registration** group. Windows Autopatch runs every hour to discover new devices added to this group. Once new devices are discovered, Windows Autopatch attempts to register these devices into its service.
+
+> [!TIP]
+> You can also use the **Discover Devices** button in either the Ready or Not Ready tabs to discover devices from the Windows Autopatch Device Registration Azure AD group on demand.
To be eligible for Windows Autopatch management, devices must meet a minimum set of required software-based prerequisites:
## Prerequisites
-- Supported Windows OS Enterprise edition version.
+- Windows 10/11 Enterprise edition 1809+.
- Either hybrid or Azure AD joined (personal devices aren't supported).
- Managed by Microsoft Endpoint Manager (either Microsoft Endpoint Manager-Intune or Microsoft Endpoint Manager-Configuration Manager Co-management).
-- Microsoft Endpoint Manager-Configuration Manager Co-management workloads (Windows Updates policies, Device configuration and Office Click-to-run) must be set to Pilot Intune or Intune.
+- Microsoft Endpoint Manager-Configuration Manager Co-management workloads swung over to Microsoft Endpoint Manager-Intune (either set to Pilot Intune or Intune).
+ - Windows Updates policies
+ - Device configuration
+ - Office Click-to-run
- Last Intune device check-in completed within the last 28 days.
For more information about each prerequisite check, see the [Prerequisites](../prepare/windows-autopatch-prerequisites.md) article.
@@ -45,14 +51,17 @@ Windows Autopatch introduces a new user interface to help IT admins manage devic
| Tab | Purpose |
| ----- | ----- |
-| Ready tab | The purpose of the Ready tab is to show devices that were successfully registered to the Windows Autopatch service and that have met device health requirements. |
+| Ready tab | The purpose of the Ready tab is to show devices that were successfully registered to the Windows Autopatch service and that have met on-going device health requirements. |
| Not ready tab | The purpose of the Not ready tab is to show devices that didn't successfully register into the Windows Autopatch service, or didn't pass one of the device readiness checks. This tab is intended to help customers identify and remediate devices that don't meet device readiness checks.Devices successfully registered and healthy don't show up in the Not ready tab. |
+> [!WARNING]
+> The **Not Ready** tab will not be available during the first week of the Public preview.
+
## Built-in roles required for device registration
A role defines the set of permissions granted to users assigned to that role. You can use one of the following built-in roles in Windows Autopatch to register devices:
-- Global Administrator
+- Azure AD Global Administrator
- Intune Service Administrator
- Modern Workplace Intune Administrator
From 53fbd8b369eb9c8947219a5dccc44bdf6a185c28 Mon Sep 17 00:00:00 2001
From: Tiara Quan <95256667+tiaraquan@users.noreply.github.com>
Date: Tue, 31 May 2022 10:12:48 -0700
Subject: [PATCH 27/61] Reviewing Andre's changes
Reviewing Andre's changes. Made some corrections.
---
.../deploy/windows-autopatch-register-devices.md | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/windows/deployment/windows-autopatch/deploy/windows-autopatch-register-devices.md b/windows/deployment/windows-autopatch/deploy/windows-autopatch-register-devices.md
index 7d549fcbea..8e01aec2b0 100644
--- a/windows/deployment/windows-autopatch/deploy/windows-autopatch-register-devices.md
+++ b/windows/deployment/windows-autopatch/deploy/windows-autopatch-register-devices.md
@@ -28,7 +28,7 @@ Windows Autopatch to take over software updates management of supported devices
You must choose what devices to manage with Windows Autopatch by adding either devices through direct membership or by adding other Azure Active Directory (Azure AD) dynamic/assigned groups into the Azure Active Directory assigned **Windows Autopatch Device Registration** group. Windows Autopatch runs every hour to discover new devices added to this group. Once new devices are discovered, Windows Autopatch attempts to register these devices into its service.
> [!TIP]
-> You can also use the **Discover Devices** button in either the Ready or Not Ready tabs to discover devices from the Windows Autopatch Device Registration Azure AD group on demand.
+> You can also use the **Discover Devices** button in either the Ready or Not ready tabs to discover devices from the Windows Autopatch Device Registration Azure AD group on demand.
To be eligible for Windows Autopatch management, devices must meet a minimum set of required software-based prerequisites:
@@ -45,7 +45,7 @@ To be eligible for Windows Autopatch management, devices must meet a minimum set
For more information about each prerequisite check, see the [Prerequisites](../prepare/windows-autopatch-prerequisites.md) article.
-## About Devices Ready and Not Ready tabs
+## About Devices Ready and Not ready tabs
Windows Autopatch introduces a new user interface to help IT admins manage devices and troubleshoot device readiness statuses seamlessly with actionable in-UI device readiness reports for unregistered devices or unhealthy devices.
@@ -54,8 +54,8 @@ Windows Autopatch introduces a new user interface to help IT admins manage devic
| Ready tab | The purpose of the Ready tab is to show devices that were successfully registered to the Windows Autopatch service and that have met on-going device health requirements. |
| Not ready tab | The purpose of the Not ready tab is to show devices that didn't successfully register into the Windows Autopatch service, or didn't pass one of the device readiness checks. This tab is intended to help customers identify and remediate devices that don't meet device readiness checks.
Devices successfully registered and healthy don't show up in the Not ready tab. |
-> [!WARNING]
-> The **Not Ready** tab will not be available during the first week of the Public preview.
+> [!IMPORTANT]
+> The **Not ready** tab will not be available during the first week of the public preview.
## Built-in roles required for device registration
From 1c17fbc36ed29b3cce84c1be329d0bfae875b46e Mon Sep 17 00:00:00 2001
From: Tiara Quan <95256667+tiaraquan@users.noreply.github.com>
Date: Tue, 31 May 2022 10:19:36 -0700
Subject: [PATCH 28/61] Moving note for discoverability
---
.../deploy/windows-autopatch-register-devices.md | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/windows/deployment/windows-autopatch/deploy/windows-autopatch-register-devices.md b/windows/deployment/windows-autopatch/deploy/windows-autopatch-register-devices.md
index 8e01aec2b0..47c812ba6a 100644
--- a/windows/deployment/windows-autopatch/deploy/windows-autopatch-register-devices.md
+++ b/windows/deployment/windows-autopatch/deploy/windows-autopatch-register-devices.md
@@ -49,14 +49,14 @@ For more information about each prerequisite check, see the [Prerequisites](../p
Windows Autopatch introduces a new user interface to help IT admins manage devices and troubleshoot device readiness statuses seamlessly with actionable in-UI device readiness reports for unregistered devices or unhealthy devices.
+> [!IMPORTANT]
+> The **Not ready** tab will not be available during the first week of the public preview.
+
| Tab | Purpose |
| ----- | ----- |
| Ready tab | The purpose of the Ready tab is to show devices that were successfully registered to the Windows Autopatch service and that have met on-going device health requirements. |
| Not ready tab | The purpose of the Not ready tab is to show devices that didn't successfully register into the Windows Autopatch service, or didn't pass one of the device readiness checks. This tab is intended to help customers identify and remediate devices that don't meet device readiness checks.
Devices successfully registered and healthy don't show up in the Not ready tab. |
-> [!IMPORTANT]
-> The **Not ready** tab will not be available during the first week of the public preview.
-
## Built-in roles required for device registration
A role defines the set of permissions granted to users assigned to that role. You can use one of the following built-in roles in Windows Autopatch to register devices:
From a236ea828f91cda3753201f96e90b9376b111647 Mon Sep 17 00:00:00 2001
From: Tarun Maganur <104856032+Tarun-Edu@users.noreply.github.com>
Date: Tue, 31 May 2022 10:20:42 -0700
Subject: [PATCH 29/61] Update windows-11-se-overview.md
name change : Sensocloud test to Sensocloud
---
education/windows/windows-11-se-overview.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/education/windows/windows-11-se-overview.md b/education/windows/windows-11-se-overview.md
index be73736a92..c32223b772 100644
--- a/education/windows/windows-11-se-overview.md
+++ b/education/windows/windows-11-se-overview.md
@@ -82,7 +82,7 @@ Windows 11 SE comes with some preinstalled apps. The following apps can also run
|Safe Exam Browser |3.3.2.413 |Win32 |Safe Exam Browser|
|Secure Browser |14.0.0 |Win32 |Cambium Development|
|Secure Browser |4.8.3.376 |Win32 |Questar, Inc|
-|SensoCloud test |2021.11.15.0 |Win32|Senso.Cloud|
+|SensoCloud |2021.11.15.0 |Win32|Senso.Cloud|
|SuperNova Magnifier & Screen Reader |21.02 |Win32 |Dolphin Computer Access|
|Zoom |5.9.1 (2581)|Win32 |Zoom|
|ZoomText Fusion |2022.2109.10|Win32 |Freedom Scientific|
From de80eac3a953e3493af020ad47f464edef6b7fb8 Mon Sep 17 00:00:00 2001
From: tiaraquan
Date: Tue, 31 May 2022 11:50:21 -0700
Subject: [PATCH 30/61] Fixing broken link.
---
.../operate/windows-autopatch-update-management.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/windows/deployment/windows-autopatch/operate/windows-autopatch-update-management.md b/windows/deployment/windows-autopatch/operate/windows-autopatch-update-management.md
index fb113c593d..a157492b2c 100644
--- a/windows/deployment/windows-autopatch/operate/windows-autopatch-update-management.md
+++ b/windows/deployment/windows-autopatch/operate/windows-autopatch-update-management.md
@@ -22,7 +22,7 @@ Keeping your devices up to date is a balance of speed and stability. Windows Aut
| ----- | ----- |
| Window quality update | Windows Autopatch uses four update rings to manage Windows quality updates. For more detailed information, see [Windows quality updates](../operate/windows-autopatch-wqu-overview.md). |
| Anti-virus definition | Updated with each scan. |
-| Microsoft 365 Apps for enterprise | For more information, see Microsoft 365 Apps for enterprise. |
+| Microsoft 365 Apps for enterprise | For more information, see [Microsoft 365 Apps for enterprise](windows-autopatch-microsoft-365-apps-enterprise.md). |
| Microsoft Edge | For more information, see [Microsoft Edge](../operate/windows-autopatch-edge.md). |
| Microsoft Teams | For more information, see [Microsoft Teams](../operate/windows-autopatch-teams.md). |
From e30d1f040c82927cc8a6f909bf133b75345ab206 Mon Sep 17 00:00:00 2001
From: Andre Della Monica
Date: Tue, 31 May 2022 16:46:38 -0500
Subject: [PATCH 31/61] Updates to the AP docs
---
.../windows-autopatch-register-devices.md | 29 ++++++++++++++-----
.../windows-autopatch-deregister-devices.md | 9 ++++--
2 files changed, 28 insertions(+), 10 deletions(-)
diff --git a/windows/deployment/windows-autopatch/deploy/windows-autopatch-register-devices.md b/windows/deployment/windows-autopatch/deploy/windows-autopatch-register-devices.md
index 47c812ba6a..39efb1d422 100644
--- a/windows/deployment/windows-autopatch/deploy/windows-autopatch-register-devices.md
+++ b/windows/deployment/windows-autopatch/deploy/windows-autopatch-register-devices.md
@@ -25,7 +25,18 @@ Windows Autopatch to take over software updates management of supported devices
- [Microsoft Edge updates](../operate/windows-autopatch-edge.md)
- [Microsoft Teams updates](../operate/windows-autopatch-teams.md)
-You must choose what devices to manage with Windows Autopatch by adding either devices through direct membership or by adding other Azure Active Directory (Azure AD) dynamic/assigned groups into the Azure Active Directory assigned **Windows Autopatch Device Registration** group. Windows Autopatch runs every hour to discover new devices added to this group. Once new devices are discovered, Windows Autopatch attempts to register these devices into its service.
+You must choose what devices to manage with Windows Autopatch by adding either devices through direct membership or by nesting other Azure Active Directory (Azure AD) dynamic/assigned groups into the Azure Active Directory assigned **Windows Autopatch Device Registration** group. Windows Autopatch runs every hour to discover new devices added to this group. Once new devices are discovered, Windows Autopatch attempts to register these devices into its service.
+
+### Other nested Azure AD group supported scenarios
+
+Windows Autopatch also supports the following Azure AD nested group scenarios:
+
+- Azure AD groups synced up from:
+ - On-premises Active Directory groups (Windows server type).
+ - [Configuration Manager collections](https://docs.microsoft.com/mem/configmgr/core/clients/manage/collections/create-collections#bkmk_aadcollsync).
+
+> [!IMPORTANT]
+> The **Windows Autopatch Device Registration** Azure AD group only supports one level of Azure AD nested groups.
> [!TIP]
> You can also use the **Discover Devices** button in either the Ready or Not ready tabs to discover devices from the Windows Autopatch Device Registration Azure AD group on demand.
@@ -34,13 +45,14 @@ To be eligible for Windows Autopatch management, devices must meet a minimum set
## Prerequisites
-- Windows 10/11 Enterprise edition 1809+.
+- Windows 10/11 64-bit Enterprise edition 1809+.
- Either hybrid or Azure AD joined (personal devices aren't supported).
-- Managed by Microsoft Endpoint Manager (either Microsoft Endpoint Manager-Intune or Microsoft Endpoint Manager-Configuration Manager Co-management).
-- Microsoft Endpoint Manager-Configuration Manager Co-management workloads swung over to Microsoft Endpoint Manager-Intune (either set to Pilot Intune or Intune).
- - Windows Updates policies
- - Device configuration
- - Office Click-to-run
+- Managed by Microsoft Endpoint Manager
+ - Microsoft Endpoint Manager-Intune or Microsoft Endpoint Manager-Configuration Manager Co-management.
+ - Microsoft Endpoint Manager-Configuration Manager Co-management workloads swung over to Microsoft Endpoint Manager-Intune (either set to Pilot Intune or Intune).
+ - Windows Updates policies
+ - Device configuration
+ - Office Click-to-run
- Last Intune device check-in completed within the last 28 days.
For more information about each prerequisite check, see the [Prerequisites](../prepare/windows-autopatch-prerequisites.md) article.
@@ -80,6 +92,9 @@ A role defines the set of permissions granted to users assigned to that role. Yo
Once devices or Azure AD groups containing devices are added to the **Windows Autopatch Device Registration** group, Windows Autopatch discovers these devices and runs device-level prerequisite checks to try to register them.
+> [!IMPORTANT]
+> It might take up to an hour for devices to change its statuses from **Ready for User** to **Active** in the Ready tab during the public preview.
+
## Other device lifecycle management scenarios
There are a few more device lifecycle management scenarios to consider when planning to register devices in Windows Autopatch.
diff --git a/windows/deployment/windows-autopatch/operate/windows-autopatch-deregister-devices.md b/windows/deployment/windows-autopatch/operate/windows-autopatch-deregister-devices.md
index 0f18908fb4..bfb6b35250 100644
--- a/windows/deployment/windows-autopatch/operate/windows-autopatch-deregister-devices.md
+++ b/windows/deployment/windows-autopatch/operate/windows-autopatch-deregister-devices.md
@@ -1,7 +1,7 @@
---
title: Deregister a device
description: This article explains how to deregister devices
-ms.date: 05/30/2022
+ms.date: 05/31/2022
ms.prod: w11
ms.technology: windows
ms.topic: how-to
@@ -9,7 +9,7 @@ ms.localizationpriority: medium
author: tiaraquan
ms.author: tiaraquan
manager: dougeby
-msreviewer: hathind
+msreviewer: andredm7
---
# Deregister a device
@@ -26,7 +26,10 @@ To avoid end-user disruption, device de-registration in Windows Autopatch only d
## Excluded devices
-When you deregister a device from the Windows Autopatch service, the device is flagged as "excluded". Windows Autopatch doesn't try to re-register the device into the service again, because the de-registration command doesn't trigger device membership removal from the **Windows Autopatch Device Registration** Azure Active Directory group. This is due to a direct membership removal limitation present in Azure Active Directory dynamic groups.
+When you deregister a device from the Windows Autopatch service, the device is flagged as "excluded" so Windows Autopatch doesn't try to re-register the device into the service again, since the de-registration command doesn't trigger device membership removal from the **Windows Autopatch Device Registration** Azure Active Directory group.
+
+> [!IMPORTANT]
+> The Azure AD team doesn't recommend appending query statements to remove specific device from a dynamic query due to dynamic query performance issues.
If you want to re-register a device that was previously deregistered from Windows Autopatch, you must [submit a support request](../operate/windows-autopatch-support-request.md) with the Windows Autopatch Service Engineering Team to request the removal of the "excluded" flag set during the de-registration process. After the Windows Autopatch Service Engineering Team removes the flag, you can re-register a device or a group of devices.
From bb1e37c4f32246d3f5cfe2a8d99a4d6d80ff145b Mon Sep 17 00:00:00 2001
From: Tiara Quan <95256667+tiaraquan@users.noreply.github.com>
Date: Tue, 31 May 2022 15:14:43 -0700
Subject: [PATCH 32/61] Update windows-autopatch-register-devices.md
fixed link
---
.../deploy/windows-autopatch-register-devices.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/windows/deployment/windows-autopatch/deploy/windows-autopatch-register-devices.md b/windows/deployment/windows-autopatch/deploy/windows-autopatch-register-devices.md
index 39efb1d422..2a9c8e22e5 100644
--- a/windows/deployment/windows-autopatch/deploy/windows-autopatch-register-devices.md
+++ b/windows/deployment/windows-autopatch/deploy/windows-autopatch-register-devices.md
@@ -33,7 +33,7 @@ Windows Autopatch also supports the following Azure AD nested group scenarios:
- Azure AD groups synced up from:
- On-premises Active Directory groups (Windows server type).
- - [Configuration Manager collections](https://docs.microsoft.com/mem/configmgr/core/clients/manage/collections/create-collections#bkmk_aadcollsync).
+ - [Configuration Manager collections](/mem/configmgr/core/clients/manage/collections/create-collections#bkmk_aadcollsync).
> [!IMPORTANT]
> The **Windows Autopatch Device Registration** Azure AD group only supports one level of Azure AD nested groups.
From bf07802bbc8fbf5d3e3dfd7b56f6b0394843578d Mon Sep 17 00:00:00 2001
From: Tiara Quan <95256667+tiaraquan@users.noreply.github.com>
Date: Tue, 31 May 2022 15:16:39 -0700
Subject: [PATCH 33/61] Update windows-autopatch-register-devices.md
fixed noun agreement
---
.../deploy/windows-autopatch-register-devices.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/windows/deployment/windows-autopatch/deploy/windows-autopatch-register-devices.md b/windows/deployment/windows-autopatch/deploy/windows-autopatch-register-devices.md
index 2a9c8e22e5..1b7aa1e52f 100644
--- a/windows/deployment/windows-autopatch/deploy/windows-autopatch-register-devices.md
+++ b/windows/deployment/windows-autopatch/deploy/windows-autopatch-register-devices.md
@@ -93,7 +93,7 @@ A role defines the set of permissions granted to users assigned to that role. Yo
Once devices or Azure AD groups containing devices are added to the **Windows Autopatch Device Registration** group, Windows Autopatch discovers these devices and runs device-level prerequisite checks to try to register them.
> [!IMPORTANT]
-> It might take up to an hour for devices to change its statuses from **Ready for User** to **Active** in the Ready tab during the public preview.
+> It might take up to an hour for a device to change its statuses from **Ready for User** to **Active** in the Ready tab during the public preview.
## Other device lifecycle management scenarios
From 142add568a9e6d0af72fc23246f6bd1357f04d51 Mon Sep 17 00:00:00 2001
From: Andre Della Monica
Date: Tue, 31 May 2022 19:41:03 -0500
Subject: [PATCH 34/61] More updates to device registration
---
.../windows-autopatch-register-devices.md | 38 +++++++++++++------
1 file changed, 27 insertions(+), 11 deletions(-)
diff --git a/windows/deployment/windows-autopatch/deploy/windows-autopatch-register-devices.md b/windows/deployment/windows-autopatch/deploy/windows-autopatch-register-devices.md
index 1b7aa1e52f..4a8b3060dc 100644
--- a/windows/deployment/windows-autopatch/deploy/windows-autopatch-register-devices.md
+++ b/windows/deployment/windows-autopatch/deploy/windows-autopatch-register-devices.md
@@ -18,16 +18,21 @@ Before Microsoft can manage your devices in Windows Autopatch, you must have dev
## Before you begin
-Windows Autopatch to take over software updates management of supported devices as soon as an IT admin decides to have their tenant managed by Windows Autopatch. Windows Autopatch update management scope includes:
+Windows Autopatch can take over software updates management of supported devices as soon as an IT admin decides to have their tenant managed by the service. The Windows Autopatch software updates management scope includes:
- [Windows quality updates](../operate/windows-autopatch-wqu-overview.md)
- [Microsoft 365 Apps for enterprise updates](../operate/windows-autopatch-microsoft-365-apps-enterprise.md)
- [Microsoft Edge updates](../operate/windows-autopatch-edge.md)
- [Microsoft Teams updates](../operate/windows-autopatch-teams.md)
-You must choose what devices to manage with Windows Autopatch by adding either devices through direct membership or by nesting other Azure Active Directory (Azure AD) dynamic/assigned groups into the Azure Active Directory assigned **Windows Autopatch Device Registration** group. Windows Autopatch runs every hour to discover new devices added to this group. Once new devices are discovered, Windows Autopatch attempts to register these devices into its service.
+### About the use of an Azure AD group to register devices
-### Other nested Azure AD group supported scenarios
+You must choose what devices to manage with Windows Autopatch by either adding them through direct membership or by nesting other Azure AD dynamic/assigned groups into the **Windows Autopatch Device Registration** Azure AD assigned group. Windows Autopatch automatically runs every hour to discover new devices added to this group. Once new devices are discovered, Windows Autopatch attempts to register these devices into its service.
+
+> [!NOTE]
+> All devices that are intended to be managed by the Windows Autopatch service **must** be added into the **Windows Autopatch Device Registration** Azure AD assigned group. Devices can only be added to this group if they have an Azure AD device ID. Windows Autopatch scans the Azure AD group hourly to discover newly added devices to be registered.
+
+#### Supported scenarios when nesting other Azure AD groups
Windows Autopatch also supports the following Azure AD nested group scenarios:
@@ -41,10 +46,10 @@ Windows Autopatch also supports the following Azure AD nested group scenarios:
> [!TIP]
> You can also use the **Discover Devices** button in either the Ready or Not ready tabs to discover devices from the Windows Autopatch Device Registration Azure AD group on demand.
-To be eligible for Windows Autopatch management, devices must meet a minimum set of required software-based prerequisites:
-
## Prerequisites
+To be eligible for Windows Autopatch management, devices must meet a minimum set of required software-based prerequisites:
+
- Windows 10/11 64-bit Enterprise edition 1809+.
- Either hybrid or Azure AD joined (personal devices aren't supported).
- Managed by Microsoft Endpoint Manager
@@ -55,7 +60,7 @@ To be eligible for Windows Autopatch management, devices must meet a minimum set
- Office Click-to-run
- Last Intune device check-in completed within the last 28 days.
-For more information about each prerequisite check, see the [Prerequisites](../prepare/windows-autopatch-prerequisites.md) article.
+For more details on each prerequisite check, see the [Prerequisites](../prepare/windows-autopatch-prerequisites.md) article.
## About Devices Ready and Not ready tabs
@@ -66,19 +71,29 @@ Windows Autopatch introduces a new user interface to help IT admins manage devic
| Tab | Purpose |
| ----- | ----- |
-| Ready tab | The purpose of the Ready tab is to show devices that were successfully registered to the Windows Autopatch service and that have met on-going device health requirements. |
-| Not ready tab | The purpose of the Not ready tab is to show devices that didn't successfully register into the Windows Autopatch service, or didn't pass one of the device readiness checks. This tab is intended to help customers identify and remediate devices that don't meet device readiness checks.Devices successfully registered and healthy don't show up in the Not ready tab. |
+| Ready tab | The purpose of the Ready tab is to show devices that were successfully registered to the Windows Autopatch service and that have met post-registration device health requirements. |
+| Not ready tab | The purpose of the Not ready tab is to show devices that didn't successfully register into the Windows Autopatch service, or didn't pass one of the post-registration health requirements. This tab is intended to help customers identify and remediate devices that don't meet either pre or post-registration device readiness checks.
Devices successfully registered and healthy don't show up in the Not ready tab. |
## Built-in roles required for device registration
A role defines the set of permissions granted to users assigned to that role. You can use one of the following built-in roles in Windows Autopatch to register devices:
- Azure AD Global Administrator
+- Service Support Administrator
- Intune Service Administrator
- Modern Workplace Intune Administrator
+See [Azure AD built-in roles](https://docs.microsoft.com/azure/active-directory/roles/permissions-reference) and [Role-based access control (RBAC) with Microsoft Intune](https://docs.microsoft.com/mem/intune/fundamentals/role-based-access-control) for more details.
+
> [!NOTE]
-> The Modern Workplace Intune Admin role is a custom created role in Windows Autopatch. This role can assign administrators to Endpoint Manager roles, and allows you to create and configure custom Endpoint Manager roles.
+> The Modern Workplace Intune Admin role is a custom created role during the Windows Autopatch tenant enrollment process. This role can assign administrators to Endpoint Manager roles, and allows you to create and configure custom Endpoint Manager roles.
+
+## Details about the device registration process
+
+The process of registering your devices in Windows Autopatch does the following:
+
+1. Makes a record of devices in the service.
+2. Assign devices into the ring groups and other groups required for software updates management.
## Steps to register devices
@@ -93,7 +108,7 @@ A role defines the set of permissions granted to users assigned to that role. Yo
Once devices or Azure AD groups containing devices are added to the **Windows Autopatch Device Registration** group, Windows Autopatch discovers these devices and runs device-level prerequisite checks to try to register them.
> [!IMPORTANT]
-> It might take up to an hour for a device to change its statuses from **Ready for User** to **Active** in the Ready tab during the public preview.
+> It might take up to an hour for a device to change its status from **Ready for User** to **Active** in the Ready tab during the public preview.
## Other device lifecycle management scenarios
@@ -115,4 +130,5 @@ If you need to repair a device that was previously registered into the Windows A
When one of these hardware changes occurs, Azure AD creates a new device ID record for that device, even if it's technically the same device.
-Any device that needs to be registered into the Windows Autopatch service must be added into the **Windows Autopatch Device Registration** Azure AD assigned group. Devices can only be added to this group if they have an Azure AD device record ID. Windows Autopatch scans the Azure AD group to discover the new device and brings it in to be registered.
+> [!IMPORTANT]
+> If a new Azure AD device ID is generated for a device that was previously registered into Windows Autopatch, even technically being the same device, the new Azure AD device ID has to be added either through device direct membership or through nested Azure AD dynamic/assigned group into the Windows Autopatch Device Registration group. This process guarantees the newly generated Azure AD device ID is registered into the Windows Autopatch service and it can keep having its software updates managed by the service.
\ No newline at end of file
From e3cd67b1c788f6b2d746b5fc4446e99b8d851d1e Mon Sep 17 00:00:00 2001
From: Tiara Quan <95256667+tiaraquan@users.noreply.github.com>
Date: Tue, 31 May 2022 21:27:58 -0700
Subject: [PATCH 35/61] Update windows-autopatch-register-devices.md
Reviewed for grammar, and broken links.
---
.../deploy/windows-autopatch-register-devices.md | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/windows/deployment/windows-autopatch/deploy/windows-autopatch-register-devices.md b/windows/deployment/windows-autopatch/deploy/windows-autopatch-register-devices.md
index 4a8b3060dc..31f250df19 100644
--- a/windows/deployment/windows-autopatch/deploy/windows-autopatch-register-devices.md
+++ b/windows/deployment/windows-autopatch/deploy/windows-autopatch-register-devices.md
@@ -18,7 +18,7 @@ Before Microsoft can manage your devices in Windows Autopatch, you must have dev
## Before you begin
-Windows Autopatch can take over software updates management of supported devices as soon as an IT admin decides to have their tenant managed by the service. The Windows Autopatch software updates management scope includes:
+Windows Autopatch can take over software update management of supported devices as soon as an IT admin decides to have their tenant managed by the service. The Windows Autopatch software update management scope includes:
- [Windows quality updates](../operate/windows-autopatch-wqu-overview.md)
- [Microsoft 365 Apps for enterprise updates](../operate/windows-autopatch-microsoft-365-apps-enterprise.md)
@@ -72,7 +72,7 @@ Windows Autopatch introduces a new user interface to help IT admins manage devic
| Tab | Purpose |
| ----- | ----- |
| Ready tab | The purpose of the Ready tab is to show devices that were successfully registered to the Windows Autopatch service and that have met post-registration device health requirements. |
-| Not ready tab | The purpose of the Not ready tab is to show devices that didn't successfully register into the Windows Autopatch service, or didn't pass one of the post-registration health requirements. This tab is intended to help customers identify and remediate devices that don't meet either pre or post-registration device readiness checks.
Devices successfully registered and healthy don't show up in the Not ready tab. |
+| Not ready tab | The purpose of the Not ready tab is to show devices that didn't successfully register into the Windows Autopatch service, or didn't pass one of the post-registration health requirements. This tab is intended to help customers identify and remediate devices that don't meet either pre or post-registration device readiness checks.
Devices successfully registered and healthy don't appear in the Not ready tab. |
## Built-in roles required for device registration
@@ -83,14 +83,14 @@ A role defines the set of permissions granted to users assigned to that role. Yo
- Intune Service Administrator
- Modern Workplace Intune Administrator
-See [Azure AD built-in roles](https://docs.microsoft.com/azure/active-directory/roles/permissions-reference) and [Role-based access control (RBAC) with Microsoft Intune](https://docs.microsoft.com/mem/intune/fundamentals/role-based-access-control) for more details.
+For more information, see [Azure AD built-in roles](/azure/active-directory/roles/permissions-reference) and [Role-based access control (RBAC) with Microsoft Intune](/mem/intune/fundamentals/role-based-access-control).
> [!NOTE]
> The Modern Workplace Intune Admin role is a custom created role during the Windows Autopatch tenant enrollment process. This role can assign administrators to Endpoint Manager roles, and allows you to create and configure custom Endpoint Manager roles.
## Details about the device registration process
-The process of registering your devices in Windows Autopatch does the following:
+Registering your devices in Windows Autopatch does the following:
1. Makes a record of devices in the service.
2. Assign devices into the ring groups and other groups required for software updates management.
@@ -131,4 +131,4 @@ If you need to repair a device that was previously registered into the Windows A
When one of these hardware changes occurs, Azure AD creates a new device ID record for that device, even if it's technically the same device.
> [!IMPORTANT]
-> If a new Azure AD device ID is generated for a device that was previously registered into Windows Autopatch, even technically being the same device, the new Azure AD device ID has to be added either through device direct membership or through nested Azure AD dynamic/assigned group into the Windows Autopatch Device Registration group. This process guarantees the newly generated Azure AD device ID is registered into the Windows Autopatch service and it can keep having its software updates managed by the service.
\ No newline at end of file
+> If a new Azure AD device ID is generated for a device that was previously registered into Windows Autopatch, even if it's the same device, the new Azure AD device ID must be added either through device direct membership or through nested Azure AD dynamic/assigned group into the **Windows Autopatch Device Registration** group. This process guarantees the newly generated Azure AD device ID is registered with Windows Autopatch and that the device continues to have its software updates managed by the service.
From ac861feda773673f657f7a8eadb6d5a666eb2e72 Mon Sep 17 00:00:00 2001
From: tiaraquan
Date: Wed, 1 Jun 2022 09:51:35 -0700
Subject: [PATCH 36/61] Fixed a link, removed redundancy.
---
.../windows-autopatch/overview/windows-autopatch-faq.md | 4 ++--
.../windows-autopatch/prepare/windows-autopatch-fix-issues.md | 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/windows/deployment/windows-autopatch/overview/windows-autopatch-faq.md b/windows/deployment/windows-autopatch/overview/windows-autopatch-faq.md
index 3fad61cc1f..d2c0bbd292 100644
--- a/windows/deployment/windows-autopatch/overview/windows-autopatch-faq.md
+++ b/windows/deployment/windows-autopatch/overview/windows-autopatch-faq.md
@@ -19,7 +19,7 @@ msreviewer: hathind
| Question | Answer |
| ----- | ----- |
| What Windows versions are supported? | Windows Autopatch works with all [supported versions of Windows 10 and Windows 11 Enterprise edition](/windows/release-health/supported-versions-windows-client). |
-| What is the difference between Windows Updates for Business and Windows Autopatch? | Windows Autopatch is a service that removes the need for organizations to plan and operate the update process. Windows Autopatch moves the burden from your IT to Microsoft. Windows Autopatch uses [Windows Update for Business](/windows/deployment/update/deployment-service-overview) and other service components to update devices. Both are part of Windows Enterprise E3. |
+| What is the difference between Windows Update for Business and Windows Autopatch? | Windows Autopatch is a service that removes the need for organizations to plan and operate the update process.
Windows Autopatch moves the burden from your IT to Microsoft. Windows Autopatch uses [Windows Update for Business](/windows/deployment/update/deployment-service-overview) and other service components to update devices. Both are part of Windows Enterprise E3. |
| Is Windows 365 for Enterprise supported with Windows Autopatch? | Windows Autopatch supports Windows 365 for Enterprise. Windows 365 for Business isn't supported.|
| Does Windows Autopatch support Windows Education (A3) or Windows Front Line Worker (F3) licensing? | Autopatch isn't available for 'A' or 'F' series licensing. |
| Will Windows Autopatch support local domain join Windows 10? | Windows Autopatch doesn't support local (on-premise) domain join. Windows Autopatch supports [Hybrid AD join](/azure/active-directory/devices/concept-azure-ad-join-hybrid) or pure [Azure AD join](/azure/active-directory/devices/concept-azure-ad-join-hybrid). |
@@ -30,7 +30,7 @@ msreviewer: hathind
| Question | Answer |
| ----- | ----- |
| What are the prerequisites for Windows Autopatch? |
- [Supported Windows 10/11 Enterprise edition versions](/windows/release-health/supported-versions-windows-client)
- [Azure Active Directory (Azure AD) Premium](/azure/active-directory/fundamentals/active-directory-whatis#what-are-the-azure-ad-licenses)
- [Hybrid Azure AD-Joined](/azure/active-directory/devices/concept-azure-ad-join-hybrid) or [Azure AD-joined only](/azure/active-directory/devices/concept-azure-ad-join-hybrid)
- [Microsoft Intune](https://www.microsoft.com/cloud-platform/microsoft-intune)
- [Co-management](/prepare/windows-autopatch-prerequisites.md#co-management-requirements)
- [Configuration Manager version 2010 or later](/mem/configmgr/core/plan-design/changes/whats-new-in-version-2010)
- [Switch workloads for device configuration, Windows Update and Microsoft 365 Apps from Configuration Manager to Intune](/mem/configmgr/comanage/how-to-switch-workloads) (minimum Pilot Intune)
|
-| What are the licensing requirements for Windows Autopatch? |- Windows Autopatch is included with Window 10/11 Enterprise E3 or higher. For more information, see More about licenses.
- [Azure AD Premium](/azure/active-directory/fundamentals/active-directory-whatis#what-are-the-azure-ad-licenses) (for Co-management)
- [Microsoft Intune](/mem/intune/fundamentals/licenses) (includes Configuration Manager 2010 or greater via co-management)
|
+| What are the licensing requirements for Windows Autopatch? |- Windows Autopatch is included with Window 10/11 Enterprise E3 or higher. For more information, see [More about licenses](../prepare/windows-autopatch-prerequisites.md#more-about-licenses).
- [Azure AD Premium](/azure/active-directory/fundamentals/active-directory-whatis#what-are-the-azure-ad-licenses) (for Co-management)
- [Microsoft Intune](/mem/intune/fundamentals/licenses) (includes Configuration Manager 2010 or greater via co-management)
|
| Are there hardware requirements for Windows Autopatch? | No, Windows Autopatch doesn't require any specific hardware. However, general hardware requirements for updates are still applicable. For example, to deliver Windows 11 to your Autopatch devices they must meet [specific hardware requirements](/windows/windows-11-specifications?r=1). Windows devices must be supported by your hardware OEM. |
## Device registration
diff --git a/windows/deployment/windows-autopatch/prepare/windows-autopatch-fix-issues.md b/windows/deployment/windows-autopatch/prepare/windows-autopatch-fix-issues.md
index 8dff734be5..9f65feb92f 100644
--- a/windows/deployment/windows-autopatch/prepare/windows-autopatch-fix-issues.md
+++ b/windows/deployment/windows-autopatch/prepare/windows-autopatch-fix-issues.md
@@ -66,7 +66,7 @@ Windows Autopatch requires the following licenses:
| Result | Meaning |
| ----- | ----- |
-| Not ready | Windows Autopatch requires Windows 10/11 Enterprise E3 (or higher) to be assigned to your users. Additionally, Azure Active Directory Premium, Microsoft Intune and Windows 10/11 Enterprise are required. For more information, see [more about licenses](../prepare/windows-autopatch-prerequisites.md#more-about-licenses). |
+| Not ready | Windows Autopatch requires Windows 10/11 Enterprise E3 (or higher) to be assigned to your users. Additionally, Azure Active Directory Premium, and Microsoft Intune are required. For more information, see [more about licenses](../prepare/windows-autopatch-prerequisites.md#more-about-licenses). |
### Windows Autopatch service accounts
From 34bc2d44ae61657cdfa5c8f60eae692cab996215 Mon Sep 17 00:00:00 2001
From: tiaraquan
Date: Wed, 1 Jun 2022 10:30:48 -0700
Subject: [PATCH 37/61] Fixing typo
---
windows/deployment/windows-autopatch/TOC.yml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/windows/deployment/windows-autopatch/TOC.yml b/windows/deployment/windows-autopatch/TOC.yml
index c6fe58c845..871a52e791 100644
--- a/windows/deployment/windows-autopatch/TOC.yml
+++ b/windows/deployment/windows-autopatch/TOC.yml
@@ -49,7 +49,7 @@
href: operate/windows-autopatch-edge.md
- name: Microsoft Teams
href: operate/windows-autopatch-teams.md
- - name: Deregister a devices
+ - name: Deregister a device
href: operate/windows-autopatch-deregister-devices.md
- name: Submit a support request
href: operate/windows-autopatch-support-request.md
From 1122507a7e3d451540902ecd8575abdf7461fcf4 Mon Sep 17 00:00:00 2001
From: Tarun Maganur <104856032+Tarun-Edu@users.noreply.github.com>
Date: Wed, 1 Jun 2022 14:55:57 -0700
Subject: [PATCH 38/61] Update windows-11-se-overview.md
line 77 changed from |Pearson TestNav |1.10.2.0 |Win32|Pearson| to |Pearson TestNav |1.10.2.0 |Store |Pearson|
---
education/windows/windows-11-se-overview.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/education/windows/windows-11-se-overview.md b/education/windows/windows-11-se-overview.md
index c32223b772..e22acdf422 100644
--- a/education/windows/windows-11-se-overview.md
+++ b/education/windows/windows-11-se-overview.md
@@ -74,7 +74,7 @@ Windows 11 SE comes with some preinstalled apps. The following apps can also run
|NextUp Talker |1.0.49 |Win32 |NextUp Technologies|
|NonVisual Desktop Access |2021.3.1 |Win32 |NV Access|
|NWEA Secure Testing Browser |5.4.300.0 |Win32 |NWEA|
-|Pearson TestNav |1.10.2.0 |Win32 |Pearson|
+|Pearson TestNav |1.10.2.0 |Store |Pearson|
|Questar Secure Browser |4.8.3.376 |Win32 |Questar|
|ReadAndWriteForWindows |12.0.60.0 |Win32 |Texthelp Ltd.|
|Remote Help |3.8.0.12 |Win32 |Microsoft|
From 3515ad41c53b3b3851c47a88046d65b194161d36 Mon Sep 17 00:00:00 2001
From: Jitin Mathew
Date: Thu, 2 Jun 2022 03:29:55 +0530
Subject: [PATCH 39/61] Updated-6038484
Bulk metadata update.
---
windows/whats-new/contribute-to-a-topic.md | 3 ---
windows/whats-new/get-started-with-1709.md | 3 ---
windows/whats-new/ltsc/index.md | 4 ----
windows/whats-new/ltsc/whats-new-windows-10-2015.md | 4 ----
windows/whats-new/ltsc/whats-new-windows-10-2016.md | 4 ----
windows/whats-new/ltsc/whats-new-windows-10-2019.md | 3 ---
windows/whats-new/ltsc/whats-new-windows-10-2021.md | 3 ---
.../whats-new/whats-new-windows-10-version-1507-and-1511.md | 3 ---
windows/whats-new/whats-new-windows-10-version-1607.md | 3 ---
windows/whats-new/whats-new-windows-10-version-1703.md | 4 ----
windows/whats-new/whats-new-windows-10-version-1709.md | 3 ---
windows/whats-new/whats-new-windows-10-version-1803.md | 3 ---
windows/whats-new/whats-new-windows-10-version-1809.md | 3 ---
windows/whats-new/whats-new-windows-10-version-1903.md | 4 ----
windows/whats-new/whats-new-windows-10-version-1909.md | 4 ----
windows/whats-new/whats-new-windows-10-version-2004.md | 4 ----
windows/whats-new/whats-new-windows-10-version-20H2.md | 4 ----
windows/whats-new/whats-new-windows-10-version-21H1.md | 4 ----
windows/whats-new/whats-new-windows-10-version-21H2.md | 3 ---
windows/whats-new/windows-10-insider-preview.md | 2 --
windows/whats-new/windows-11-overview.md | 4 ----
windows/whats-new/windows-11-plan.md | 3 ---
windows/whats-new/windows-11-prepare.md | 3 ---
windows/whats-new/windows-11-requirements.md | 4 ----
24 files changed, 82 deletions(-)
diff --git a/windows/whats-new/contribute-to-a-topic.md b/windows/whats-new/contribute-to-a-topic.md
index b99b7a48ad..77dfd79528 100644
--- a/windows/whats-new/contribute-to-a-topic.md
+++ b/windows/whats-new/contribute-to-a-topic.md
@@ -1,10 +1,7 @@
---
title: Edit an existing topic using the Edit link
description: Instructions about how to edit an existing topic by using the Edit link on docs.microsoft.com.
-keywords: contribute, edit a topic
ms.prod: w10
-ms.mktglfcycl: explore
-ms.sitesec: library
ms.date: 10/13/2017
ms.reviewer:
manager: dansimp
diff --git a/windows/whats-new/get-started-with-1709.md b/windows/whats-new/get-started-with-1709.md
index c2522f3e4c..4384b7e11e 100644
--- a/windows/whats-new/get-started-with-1709.md
+++ b/windows/whats-new/get-started-with-1709.md
@@ -1,10 +1,7 @@
---
title: Get started with Windows 10, version 1709
description: Learn about features, review requirements, and plan your deployment of Windows 10, version 1709, including IT Pro content, release information, and history.
-keywords: ["get started", "windows 10", "fall creators update", "1709"]
ms.prod: w10
-ms.mktglfcycl: deploy
-ms.sitesec: library
author: dansimp
ms.author: dansimp
ms.date: 10/16/2017
diff --git a/windows/whats-new/ltsc/index.md b/windows/whats-new/ltsc/index.md
index dfb0df5731..04888d2873 100644
--- a/windows/whats-new/ltsc/index.md
+++ b/windows/whats-new/ltsc/index.md
@@ -1,11 +1,7 @@
---
title: Windows 10 Enterprise LTSC
description: New and updated IT Pro content about new features in Windows 10, LTSC (also known as Windows 10 LTSB).
-keywords: ["What's new in Windows 10", "Windows 10", "Windows 10 LTSC", "Windows 10 LTSB"]
ms.prod: w10
-ms.mktglfcycl: deploy
-ms.sitesec: library
-audience: itpro
author: aczechowski
ms.author: aaroncz
manager: dougeby
diff --git a/windows/whats-new/ltsc/whats-new-windows-10-2015.md b/windows/whats-new/ltsc/whats-new-windows-10-2015.md
index c1c29d8f63..9bec3fd8c7 100644
--- a/windows/whats-new/ltsc/whats-new-windows-10-2015.md
+++ b/windows/whats-new/ltsc/whats-new-windows-10-2015.md
@@ -4,11 +4,7 @@ ms.reviewer:
manager: dougeby
ms.author: aaroncz
description: New and updated IT Pro content about new features in Windows 10 Enterprise LTSC 2015 (also known as Windows 10 Enterprise 2015 LTSB).
-keywords: ["What's new in Windows 10", "Windows 10", "Windows 10 Enterprise LTSC 2015"]
ms.prod: w10
-ms.mktglfcycl: deploy
-ms.sitesec: library
-audience: itpro
author: aczechowski
ms.localizationpriority: low
ms.topic: article
diff --git a/windows/whats-new/ltsc/whats-new-windows-10-2016.md b/windows/whats-new/ltsc/whats-new-windows-10-2016.md
index 354488f563..7ee18df927 100644
--- a/windows/whats-new/ltsc/whats-new-windows-10-2016.md
+++ b/windows/whats-new/ltsc/whats-new-windows-10-2016.md
@@ -4,11 +4,7 @@ ms.reviewer:
manager: dougeby
ms.author: aaroncz
description: New and updated IT Pro content about new features in Windows 10 Enterprise LTSC 2016 (also known as Windows 10 Enterprise 2016 LTSB).
-keywords: ["What's new in Windows 10", "Windows 10", "Windows 10 Enterprise LTSC 2016"]
ms.prod: w10
-ms.mktglfcycl: deploy
-ms.sitesec: library
-audience: itpro
author: aczechowski
ms.localizationpriority: low
ms.topic: article
diff --git a/windows/whats-new/ltsc/whats-new-windows-10-2019.md b/windows/whats-new/ltsc/whats-new-windows-10-2019.md
index 40a615660a..747857cdd1 100644
--- a/windows/whats-new/ltsc/whats-new-windows-10-2019.md
+++ b/windows/whats-new/ltsc/whats-new-windows-10-2019.md
@@ -4,10 +4,7 @@ ms.reviewer:
manager: dougeby
ms.author: aaroncz
description: New and updated IT Pro content about new features in Windows 10 Enterprise LTSC 2019 (also known as Windows 10 Enterprise 2019 LTSB).
-keywords: ["What's new in Windows 10", "Windows 10", "Windows 10 Enterprise LTSC 2019"]
ms.prod: w10
-ms.mktglfcycl: deploy
-ms.sitesec: library
author: aczechowski
ms.localizationpriority: low
ms.topic: article
diff --git a/windows/whats-new/ltsc/whats-new-windows-10-2021.md b/windows/whats-new/ltsc/whats-new-windows-10-2021.md
index 1e10461eea..ccde2ab561 100644
--- a/windows/whats-new/ltsc/whats-new-windows-10-2021.md
+++ b/windows/whats-new/ltsc/whats-new-windows-10-2021.md
@@ -4,10 +4,7 @@ ms.reviewer:
manager: dougeby
ms.author: aaroncz
description: New and updated IT Pro content about new features in Windows 10 Enterprise LTSC 2021.
-keywords: ["What's new in Windows 10", "Windows 10", "Windows 10 Enterprise LTSC 2021"]
ms.prod: w10
-ms.mktglfcycl: deploy
-ms.sitesec: library
author: aczechowski
ms.localizationpriority: low
ms.topic: article
diff --git a/windows/whats-new/whats-new-windows-10-version-1507-and-1511.md b/windows/whats-new/whats-new-windows-10-version-1507-and-1511.md
index e7ad13d805..3b820e3b76 100644
--- a/windows/whats-new/whats-new-windows-10-version-1507-and-1511.md
+++ b/windows/whats-new/whats-new-windows-10-version-1507-and-1511.md
@@ -1,11 +1,8 @@
---
title: What's new in Windows 10, versions 1507 and 1511 (Windows 10)
description: What's new in Windows 10 for Windows 10 (versions 1507 and 1511).
-ms.assetid: 75F285B0-09BE-4821-9B42-37B9BE54CEC6
ms.reviewer:
ms.prod: w10
-ms.mktglfcycl: deploy
-ms.sitesec: library
author: aczechowski
manager: dougeby
ms.author: aaroncz
diff --git a/windows/whats-new/whats-new-windows-10-version-1607.md b/windows/whats-new/whats-new-windows-10-version-1607.md
index 509b7d10a0..33d826641f 100644
--- a/windows/whats-new/whats-new-windows-10-version-1607.md
+++ b/windows/whats-new/whats-new-windows-10-version-1607.md
@@ -1,10 +1,7 @@
---
title: What's new in Windows 10, version 1607 (Windows 10)
description: What's new in Windows 10 for Windows 10 (version 1607).
-keywords: ["What's new in Windows 10", "Windows 10", "anniversary update"]
ms.prod: w10
-ms.mktglfcycl: deploy
-ms.sitesec: library
ms.localizationpriority: high
ms.reviewer:
author: aczechowski
diff --git a/windows/whats-new/whats-new-windows-10-version-1703.md b/windows/whats-new/whats-new-windows-10-version-1703.md
index a62e914365..7b22f584f5 100644
--- a/windows/whats-new/whats-new-windows-10-version-1703.md
+++ b/windows/whats-new/whats-new-windows-10-version-1703.md
@@ -1,12 +1,8 @@
---
title: What's new in Windows 10, version 1703
description: New and updated features in Windows 10, version 1703 (also known as the Creators Updated).
-keywords: ["What's new in Windows 10", "Windows 10", "creators update"]
ms.prod: w10
-ms.mktglfcycl: deploy
-ms.sitesec: library
ms.localizationpriority: high
-ms.assetid: dca7c655-c4f6-45f8-aa02-64187b202617
ms.reviewer:
author: aczechowski
manager: dougeby
diff --git a/windows/whats-new/whats-new-windows-10-version-1709.md b/windows/whats-new/whats-new-windows-10-version-1709.md
index 905d4ff2dd..4470bbd82a 100644
--- a/windows/whats-new/whats-new-windows-10-version-1709.md
+++ b/windows/whats-new/whats-new-windows-10-version-1709.md
@@ -1,10 +1,7 @@
---
title: What's new in Windows 10, version 1709
description: New and updated features in Windows 10, version 1709 (also known as the Fall Creators Update).
-keywords: ["What's new in Windows 10", "Windows 10", "Fall Creators Update"]
ms.prod: w10
-ms.mktglfcycl: deploy
-ms.sitesec: library
ms.reviewer:
author: aczechowski
manager: dougeby
diff --git a/windows/whats-new/whats-new-windows-10-version-1803.md b/windows/whats-new/whats-new-windows-10-version-1803.md
index f2f4dc5964..c9df6c099a 100644
--- a/windows/whats-new/whats-new-windows-10-version-1803.md
+++ b/windows/whats-new/whats-new-windows-10-version-1803.md
@@ -1,10 +1,7 @@
---
title: What's new in Windows 10, version 1803
description: New and updated features in Windows 10, version 1803 (also known as the Windows 10 April 2018 Update).
-keywords: ["What's new in Windows 10", "Windows 10", "April 2018 Update"]
ms.prod: w10
-ms.mktglfcycl: deploy
-ms.sitesec: library
ms.reviewer:
author: aczechowski
manager: dougeby
diff --git a/windows/whats-new/whats-new-windows-10-version-1809.md b/windows/whats-new/whats-new-windows-10-version-1809.md
index 9ce31284cc..fc59be8136 100644
--- a/windows/whats-new/whats-new-windows-10-version-1809.md
+++ b/windows/whats-new/whats-new-windows-10-version-1809.md
@@ -2,10 +2,7 @@
title: What's new in Windows 10, version 1809
ms.reviewer:
description: Learn about features for Windows 10, version 1809, including features and fixes included in previous cumulative updates to Windows 10, version 1803.
-keywords: ["What's new in Windows 10", "Windows 10", "Windows 10 October 2018 Update"]
ms.prod: w10
-ms.mktglfcycl: deploy
-ms.sitesec: library
author: aczechowski
manager: dougeby
ms.author: aaroncz
diff --git a/windows/whats-new/whats-new-windows-10-version-1903.md b/windows/whats-new/whats-new-windows-10-version-1903.md
index 35ed9f16c3..94bd3f7f89 100644
--- a/windows/whats-new/whats-new-windows-10-version-1903.md
+++ b/windows/whats-new/whats-new-windows-10-version-1903.md
@@ -1,11 +1,7 @@
---
title: What's new in Windows 10, version 1903
description: New and updated features in Windows 10, version 1903 (also known as the Windows 10 May 2019 Update).
-keywords: ["What's new in Windows 10", "Windows 10", "May 2019 Update"]
ms.prod: w10
-ms.mktglfcycl: deploy
-ms.sitesec: library
-audience: itpro
author: aczechowski
ms.author: aaroncz
manager: dougeby
diff --git a/windows/whats-new/whats-new-windows-10-version-1909.md b/windows/whats-new/whats-new-windows-10-version-1909.md
index 3b33b31e96..d78a5d5369 100644
--- a/windows/whats-new/whats-new-windows-10-version-1909.md
+++ b/windows/whats-new/whats-new-windows-10-version-1909.md
@@ -1,11 +1,7 @@
---
title: What's new in Windows 10, version 1909
description: New and updated features in Windows 10, version 1909 (also known as the Windows 10 November 2019 Update).
-keywords: ["What's new in Windows 10", "Windows 10", "November 2019 Update"]
ms.prod: w10
-ms.mktglfcycl: deploy
-ms.sitesec: library
-audience: itpro
author: aczechowski
ms.author: aaroncz
manager: dougeby
diff --git a/windows/whats-new/whats-new-windows-10-version-2004.md b/windows/whats-new/whats-new-windows-10-version-2004.md
index 726580724f..453aa06e93 100644
--- a/windows/whats-new/whats-new-windows-10-version-2004.md
+++ b/windows/whats-new/whats-new-windows-10-version-2004.md
@@ -1,11 +1,7 @@
---
title: What's new in Windows 10, version 2004
description: New and updated features in Windows 10, version 2004 (also known as the Windows 10 May 2020 Update).
-keywords: ["What's new in Windows 10", "Windows 10", "May 2020 Update"]
ms.prod: w10
-ms.mktglfcycl: deploy
-ms.sitesec: library
-audience: itpro
author: aczechowski
ms.author: aaroncz
manager: dougeby
diff --git a/windows/whats-new/whats-new-windows-10-version-20H2.md b/windows/whats-new/whats-new-windows-10-version-20H2.md
index 436dc92f0d..b3f400dbeb 100644
--- a/windows/whats-new/whats-new-windows-10-version-20H2.md
+++ b/windows/whats-new/whats-new-windows-10-version-20H2.md
@@ -1,11 +1,7 @@
---
title: What's new in Windows 10, version 20H2
description: New and updated features in Windows 10, version 20H2 (also known as the Windows 10 October 2020 Update).
-keywords: ["What's new in Windows 10", "Windows 10", "October 2020 Update"]
ms.prod: w10
-ms.mktglfcycl: deploy
-ms.sitesec: library
-audience: itpro
author: aczechowski
ms.author: aaroncz
manager: dougeby
diff --git a/windows/whats-new/whats-new-windows-10-version-21H1.md b/windows/whats-new/whats-new-windows-10-version-21H1.md
index 2fdba9bd26..f598d1913b 100644
--- a/windows/whats-new/whats-new-windows-10-version-21H1.md
+++ b/windows/whats-new/whats-new-windows-10-version-21H1.md
@@ -1,11 +1,7 @@
---
title: What's new in Windows 10, version 21H1
description: New and updated features in Windows 10, version 21H1 (also known as the Windows 10 May 2021 Update).
-keywords: ["What's new in Windows 10", "Windows 10", "May 2021 Update"]
ms.prod: w10
-ms.mktglfcycl: deploy
-ms.sitesec: library
-audience: itpro
author: aczechowski
ms.author: aaroncz
manager: dougeby
diff --git a/windows/whats-new/whats-new-windows-10-version-21H2.md b/windows/whats-new/whats-new-windows-10-version-21H2.md
index d536eb04eb..da72022d30 100644
--- a/windows/whats-new/whats-new-windows-10-version-21H2.md
+++ b/windows/whats-new/whats-new-windows-10-version-21H2.md
@@ -3,9 +3,6 @@ title: What's new in Windows 10, version 21H2 for IT pros
description: Learn more about what's new in Windows 10 version 21H2, including servicing updates, Windows Subsystem for Linux, the latest CSPs, and more.
manager: dougeby
ms.prod: w10
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.pagetype: mobile
ms.author: aaroncz
author: aczechowski
ms.localizationpriority: medium
diff --git a/windows/whats-new/windows-10-insider-preview.md b/windows/whats-new/windows-10-insider-preview.md
index 2e6f2191f7..61a499904f 100644
--- a/windows/whats-new/windows-10-insider-preview.md
+++ b/windows/whats-new/windows-10-insider-preview.md
@@ -2,8 +2,6 @@
title: Documentation for Windows 10 Insider Preview (Windows 10)
description: Preliminary documentation for some Windows 10 features in Insider Preview.
ms.prod: w10
-ms.mktglfcycl: deploy
-ms.sitesec: library
author: dansimp
ms.date: 04/14/2017
ms.reviewer:
diff --git a/windows/whats-new/windows-11-overview.md b/windows/whats-new/windows-11-overview.md
index 623e6caba5..ec5cd6f23f 100644
--- a/windows/whats-new/windows-11-overview.md
+++ b/windows/whats-new/windows-11-overview.md
@@ -3,14 +3,10 @@ title: Windows 11 overview for administrators
description: Learn more about Windows 11. Read about the features IT professionals and administrators should know about Windows 11, including security, using apps, using Android apps, the new desktop, and deploying and servicing PCs.
ms.reviewer:
manager: dougeby
-ms.audience: itpro
author: aczechowski
ms.author: aaroncz
ms.prod: w10
-ms.mktglfcycl: deploy
-ms.sitesec: library
ms.localizationpriority: medium
-audience: itpro
ms.topic: article
ms.collection: highpri
ms.custom: intro-overview
diff --git a/windows/whats-new/windows-11-plan.md b/windows/whats-new/windows-11-plan.md
index 91a6d66855..7f67c4a774 100644
--- a/windows/whats-new/windows-11-plan.md
+++ b/windows/whats-new/windows-11-plan.md
@@ -1,10 +1,7 @@
---
title: Plan for Windows 11
description: Windows 11 deployment planning, IT Pro content.
-keywords: ["get started", "windows 11", "plan"]
ms.prod: w11
-ms.mktglfcycl: deploy
-ms.sitesec: library
author: aczechowski
ms.author: aaroncz
manager: dougeby
diff --git a/windows/whats-new/windows-11-prepare.md b/windows/whats-new/windows-11-prepare.md
index 262bf50024..532493e1e3 100644
--- a/windows/whats-new/windows-11-prepare.md
+++ b/windows/whats-new/windows-11-prepare.md
@@ -1,10 +1,7 @@
---
title: Prepare for Windows 11
description: Prepare your infrastructure and tools to deploy Windows 11, IT Pro content.
-keywords: ["get started", "windows 11"]
ms.prod: w11
-ms.mktglfcycl: deploy
-ms.sitesec: library
author: aczechowski
ms.author: aaroncz
manager: dougeby
diff --git a/windows/whats-new/windows-11-requirements.md b/windows/whats-new/windows-11-requirements.md
index 8384e85778..b2aef79c6d 100644
--- a/windows/whats-new/windows-11-requirements.md
+++ b/windows/whats-new/windows-11-requirements.md
@@ -2,14 +2,10 @@
title: Windows 11 requirements
description: Hardware requirements to deploy Windows 11
manager: dougeby
-ms.audience: itpro
author: aczechowski
ms.author: aaroncz
ms.prod: w11
-ms.mktglfcycl: deploy
-ms.sitesec: library
ms.localizationpriority: medium
-audience: itpro
ms.topic: article
ms.custom: seo-marvel-apr2020
ms.collection: highpri
From cd72b10d8846fcd2996710fd56c1da4b60d047df Mon Sep 17 00:00:00 2001
From: tiaraquan
Date: Wed, 1 Jun 2022 21:49:51 -0700
Subject: [PATCH 40/61] Fixed link, provided more clarity.
---
.../windows-autopatch/overview/windows-autopatch-faq.md | 2 +-
.../windows-autopatch/prepare/windows-autopatch-fix-issues.md | 4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/windows/deployment/windows-autopatch/overview/windows-autopatch-faq.md b/windows/deployment/windows-autopatch/overview/windows-autopatch-faq.md
index d2c0bbd292..f42d4e4606 100644
--- a/windows/deployment/windows-autopatch/overview/windows-autopatch-faq.md
+++ b/windows/deployment/windows-autopatch/overview/windows-autopatch-faq.md
@@ -31,7 +31,7 @@ msreviewer: hathind
| ----- | ----- |
| What are the prerequisites for Windows Autopatch? | - [Supported Windows 10/11 Enterprise edition versions](/windows/release-health/supported-versions-windows-client)
- [Azure Active Directory (Azure AD) Premium](/azure/active-directory/fundamentals/active-directory-whatis#what-are-the-azure-ad-licenses)
- [Hybrid Azure AD-Joined](/azure/active-directory/devices/concept-azure-ad-join-hybrid) or [Azure AD-joined only](/azure/active-directory/devices/concept-azure-ad-join-hybrid)
- [Microsoft Intune](https://www.microsoft.com/cloud-platform/microsoft-intune)
- [Co-management](/prepare/windows-autopatch-prerequisites.md#co-management-requirements)
- [Configuration Manager version 2010 or later](/mem/configmgr/core/plan-design/changes/whats-new-in-version-2010)
- [Switch workloads for device configuration, Windows Update and Microsoft 365 Apps from Configuration Manager to Intune](/mem/configmgr/comanage/how-to-switch-workloads) (minimum Pilot Intune)
|
| What are the licensing requirements for Windows Autopatch? |- Windows Autopatch is included with Window 10/11 Enterprise E3 or higher. For more information, see [More about licenses](../prepare/windows-autopatch-prerequisites.md#more-about-licenses).
- [Azure AD Premium](/azure/active-directory/fundamentals/active-directory-whatis#what-are-the-azure-ad-licenses) (for Co-management)
- [Microsoft Intune](/mem/intune/fundamentals/licenses) (includes Configuration Manager 2010 or greater via co-management)
|
-| Are there hardware requirements for Windows Autopatch? | No, Windows Autopatch doesn't require any specific hardware. However, general hardware requirements for updates are still applicable. For example, to deliver Windows 11 to your Autopatch devices they must meet [specific hardware requirements](/windows/windows-11-specifications?r=1). Windows devices must be supported by your hardware OEM. |
+| Are there hardware requirements for Windows Autopatch? | No, Windows Autopatch doesn't require any specific hardware. However, general hardware requirements for updates are still applicable. For example, to deliver Windows 11 to your Autopatch devices they must meet [specific hardware requirements](/windows/whats-new/windows-11-requirements). Windows devices must be supported by your hardware OEM. |
## Device registration
diff --git a/windows/deployment/windows-autopatch/prepare/windows-autopatch-fix-issues.md b/windows/deployment/windows-autopatch/prepare/windows-autopatch-fix-issues.md
index 9f65feb92f..56770f8dd7 100644
--- a/windows/deployment/windows-autopatch/prepare/windows-autopatch-fix-issues.md
+++ b/windows/deployment/windows-autopatch/prepare/windows-autopatch-fix-issues.md
@@ -45,7 +45,7 @@ Your "Windows 10 update ring" policy in Intune must not target any Windows Autop
| Result | Meaning |
| ----- | ----- |
| Not ready | You have an "update ring" policy that targets all devices, all users, or both. Change the policy to use an assignment that targets a specific Azure Active Directory (AD) group that doesn't include any Windows Autopatch devices.After enrolling into Autopatch, make sure that any update ring policies you have exclude the **Modern Workplace Devices - All** Azure Active Directory (AD) group.
For more information, see [Manage Windows 10 software updates in Intune](/mem/intune/protect/windows-update-for-business-configure).
|
-| Advisory | Both the **Modern Workplace Devices - All** and **Modern Workplace - All** Azure AD groups are groups that we create after you enroll in Windows Autopatch.This advisory appears after enrolling into Autopatch. Check the following:
- Make sure that any update ring policies you have exclude the **Modern Workplace Devices - All** Azure Active Directory (AD) group.
- If you have assigned Azure AD user groups to these policies, make sure that any update ring policies you have also exclude the **Modern Workplace - All** Azure AD group that you add your Windows Autopatch users to (or an equivalent group).
For more information, see [Manage Windows 10 software updates in Intune](/mem/intune/protect/windows-update-for-business-configure). |
+| Advisory | Both the **Modern Workplace Devices - All** and **Modern Workplace - All** Azure AD groups are groups that we create after you enroll in Windows Autopatch. This advisory is flagging an action you should take after enrolling into the service:- Make sure that any update ring policies you have exclude the **Modern Workplace Devices - All** Azure Active Directory (AD) group.
- If you have assigned Azure AD user groups to these policies, make sure that any update ring policies you have also exclude the **Modern Workplace - All** Azure AD group that you add your Windows Autopatch users to (or an equivalent group).
For more information, see [Manage Windows 10 software updates in Intune](/mem/intune/protect/windows-update-for-business-configure). |
## Azure Active Directory settings
@@ -53,7 +53,7 @@ You can access Azure Active Directory (AD) settings in the [Azure portal](https:
### Conditional access policies
-Conditional access policies must not prevent Windows Autopatch from connecting to your Intune tenant.
+Conditional access policies must not prevent Windows Autopatch from connecting to your tenant.
| Result | Meaning |
| ----- | ----- |
From 3b0cfd0adb5aa87780fdf2eff07e78da1153990b Mon Sep 17 00:00:00 2001
From: tiaraquan
Date: Thu, 2 Jun 2022 09:27:55 -0700
Subject: [PATCH 41/61] Changed FAQ format, updated FAQ cross-references, word
clarity, updated hardware link.
---
windows/deployment/windows-autopatch/TOC.yml | 2 +-
.../windows-autopatch-register-devices.md | 21 ++--
.../deployment/windows-autopatch/index.yml | 2 +-
.../windows-autopatch-support-request.md | 2 +-
.../overview/windows-autopatch-faq.md | 65 -----------
.../overview/windows-autopatch-faq.yml | 106 ++++++++++++++++++
6 files changed, 120 insertions(+), 78 deletions(-)
delete mode 100644 windows/deployment/windows-autopatch/overview/windows-autopatch-faq.md
create mode 100644 windows/deployment/windows-autopatch/overview/windows-autopatch-faq.yml
diff --git a/windows/deployment/windows-autopatch/TOC.yml b/windows/deployment/windows-autopatch/TOC.yml
index 871a52e791..97e466d258 100644
--- a/windows/deployment/windows-autopatch/TOC.yml
+++ b/windows/deployment/windows-autopatch/TOC.yml
@@ -7,7 +7,7 @@
- name: What is Windows Autopatch?
href: overview/windows-autopatch-overview.md
- name: FAQ
- href: overview/windows-autopatch-faq.md
+ href: overview/windows-autopatch-faq.yml
- name: Prepare
href: prepare/index.md
items:
diff --git a/windows/deployment/windows-autopatch/deploy/windows-autopatch-register-devices.md b/windows/deployment/windows-autopatch/deploy/windows-autopatch-register-devices.md
index 31f250df19..bc01a30400 100644
--- a/windows/deployment/windows-autopatch/deploy/windows-autopatch-register-devices.md
+++ b/windows/deployment/windows-autopatch/deploy/windows-autopatch-register-devices.md
@@ -36,9 +36,10 @@ You must choose what devices to manage with Windows Autopatch by either adding t
Windows Autopatch also supports the following Azure AD nested group scenarios:
-- Azure AD groups synced up from:
- - On-premises Active Directory groups (Windows server type).
- - [Configuration Manager collections](/mem/configmgr/core/clients/manage/collections/create-collections#bkmk_aadcollsync).
+Azure AD groups synced up from:
+
+- On-premises Active Directory groups (Windows server type).
+- [Configuration Manager collections](/mem/configmgr/core/clients/manage/collections/create-collections#bkmk_aadcollsync).
> [!IMPORTANT]
> The **Windows Autopatch Device Registration** Azure AD group only supports one level of Azure AD nested groups.
@@ -52,17 +53,17 @@ To be eligible for Windows Autopatch management, devices must meet a minimum set
- Windows 10/11 64-bit Enterprise edition 1809+.
- Either hybrid or Azure AD joined (personal devices aren't supported).
-- Managed by Microsoft Endpoint Manager
- - Microsoft Endpoint Manager-Intune or Microsoft Endpoint Manager-Configuration Manager Co-management.
- - Microsoft Endpoint Manager-Configuration Manager Co-management workloads swung over to Microsoft Endpoint Manager-Intune (either set to Pilot Intune or Intune).
- - Windows Updates policies
- - Device configuration
- - Office Click-to-run
+- Managed by Microsoft Endpoint Manager.
+ - Microsoft Endpoint Manager-Intune or Microsoft Endpoint Manager-Configuration Manager Co-management.
+ - Microsoft Endpoint Manager-Configuration Manager Co-management workloads swung over to Microsoft Endpoint Manager-Intune (either set to Pilot Intune or Intune).
+ - Windows updates policies
+ - Device configuration
+ - Office Click-to-run
- Last Intune device check-in completed within the last 28 days.
For more details on each prerequisite check, see the [Prerequisites](../prepare/windows-autopatch-prerequisites.md) article.
-## About Devices Ready and Not ready tabs
+## About the Ready and Not ready tabs
Windows Autopatch introduces a new user interface to help IT admins manage devices and troubleshoot device readiness statuses seamlessly with actionable in-UI device readiness reports for unregistered devices or unhealthy devices.
diff --git a/windows/deployment/windows-autopatch/index.yml b/windows/deployment/windows-autopatch/index.yml
index 888ce01b0c..b99aeb0317 100644
--- a/windows/deployment/windows-autopatch/index.yml
+++ b/windows/deployment/windows-autopatch/index.yml
@@ -27,7 +27,7 @@ landingContent:
- text: What is Windows Autopatch?
url: ./overview/windows-autopatch-overview.md
- text: Windows Autopatch FAQ
- url: ./overview/windows-autopatch-faq.md
+ url: ./overview/windows-autopatch-faq.yml
# Card (optional)
- title: Articles and blog posts
diff --git a/windows/deployment/windows-autopatch/operate/windows-autopatch-support-request.md b/windows/deployment/windows-autopatch/operate/windows-autopatch-support-request.md
index f6e0614363..06eeae4e4d 100644
--- a/windows/deployment/windows-autopatch/operate/windows-autopatch-support-request.md
+++ b/windows/deployment/windows-autopatch/operate/windows-autopatch-support-request.md
@@ -64,7 +64,7 @@ Once a support request is mitigated, it can no longer be edited. If a request ha
## Microsoft FastTrack
-[Microsoft FastTrack](https://www.microsoft.com/en-us/fasttrack) offers Microsoft 365 deployment guidance for customers with 150 or more licenses of an eligible subscription at no additional cost. FastTrack Specialists can help customers work through the Windows Autopatch technical prerequisites described in the [FAQ](../overview/windows-autopatch-faq.md). For more information, visit the [FastTrack website](https://www.microsoft.com/en-ca/fasttrack?rtc=1).
+[Microsoft FastTrack](https://www.microsoft.com/en-us/fasttrack) offers Microsoft 365 deployment guidance for customers with 150 or more licenses of an eligible subscription at no additional cost. FastTrack Specialists can help customers work through the Windows Autopatch technical prerequisites described in the [FAQ](../overview/windows-autopatch-faq.yml). For more information, visit the [FastTrack website](https://www.microsoft.com/en-ca/fasttrack?rtc=1).
Customers who need help with Microsoft 365 workloads can sign in to https://fasttrack.microsoft.com/ with a valid Azure ID and submit a Request for Assistance.
diff --git a/windows/deployment/windows-autopatch/overview/windows-autopatch-faq.md b/windows/deployment/windows-autopatch/overview/windows-autopatch-faq.md
deleted file mode 100644
index f42d4e4606..0000000000
--- a/windows/deployment/windows-autopatch/overview/windows-autopatch-faq.md
+++ /dev/null
@@ -1,65 +0,0 @@
----
-title: FAQ
-description: This article answers frequently asked questions about Windows Autopatch
-ms.date: 05/30/2022
-ms.prod: w11
-ms.technology: windows
-ms.topic: troubleshooting
-ms.localizationpriority: medium
-author: tiaraquan
-ms.author: tiaraquan
-manager: dougeby
-msreviewer: hathind
----
-
-# FAQ
-
-## General
-
-| Question | Answer |
-| ----- | ----- |
-| What Windows versions are supported? | Windows Autopatch works with all [supported versions of Windows 10 and Windows 11 Enterprise edition](/windows/release-health/supported-versions-windows-client). |
-| What is the difference between Windows Update for Business and Windows Autopatch? | Windows Autopatch is a service that removes the need for organizations to plan and operate the update process. Windows Autopatch moves the burden from your IT to Microsoft. Windows Autopatch uses [Windows Update for Business](/windows/deployment/update/deployment-service-overview) and other service components to update devices. Both are part of Windows Enterprise E3. |
-| Is Windows 365 for Enterprise supported with Windows Autopatch? | Windows Autopatch supports Windows 365 for Enterprise. Windows 365 for Business isn't supported.|
-| Does Windows Autopatch support Windows Education (A3) or Windows Front Line Worker (F3) licensing? | Autopatch isn't available for 'A' or 'F' series licensing. |
-| Will Windows Autopatch support local domain join Windows 10? | Windows Autopatch doesn't support local (on-premise) domain join. Windows Autopatch supports [Hybrid AD join](/azure/active-directory/devices/concept-azure-ad-join-hybrid) or pure [Azure AD join](/azure/active-directory/devices/concept-azure-ad-join-hybrid). |
-| Will Windows Autopatch be available for state and local government customers? | Windows Autopatch is available for all Windows E3 customers using Azure commercial cloud. However, Autopatch isn't currently supported for government cloud (GCC) customers. |
-
-## Requirements
-
-| Question | Answer |
-| ----- | ----- |
-| What are the prerequisites for Windows Autopatch? |
- [Supported Windows 10/11 Enterprise edition versions](/windows/release-health/supported-versions-windows-client)
- [Azure Active Directory (Azure AD) Premium](/azure/active-directory/fundamentals/active-directory-whatis#what-are-the-azure-ad-licenses)
- [Hybrid Azure AD-Joined](/azure/active-directory/devices/concept-azure-ad-join-hybrid) or [Azure AD-joined only](/azure/active-directory/devices/concept-azure-ad-join-hybrid)
- [Microsoft Intune](https://www.microsoft.com/cloud-platform/microsoft-intune)
- [Co-management](/prepare/windows-autopatch-prerequisites.md#co-management-requirements)
- [Configuration Manager version 2010 or later](/mem/configmgr/core/plan-design/changes/whats-new-in-version-2010)
- [Switch workloads for device configuration, Windows Update and Microsoft 365 Apps from Configuration Manager to Intune](/mem/configmgr/comanage/how-to-switch-workloads) (minimum Pilot Intune)
|
-| What are the licensing requirements for Windows Autopatch? |- Windows Autopatch is included with Window 10/11 Enterprise E3 or higher. For more information, see [More about licenses](../prepare/windows-autopatch-prerequisites.md#more-about-licenses).
- [Azure AD Premium](/azure/active-directory/fundamentals/active-directory-whatis#what-are-the-azure-ad-licenses) (for Co-management)
- [Microsoft Intune](/mem/intune/fundamentals/licenses) (includes Configuration Manager 2010 or greater via co-management)
|
-| Are there hardware requirements for Windows Autopatch? | No, Windows Autopatch doesn't require any specific hardware. However, general hardware requirements for updates are still applicable. For example, to deliver Windows 11 to your Autopatch devices they must meet [specific hardware requirements](/windows/whats-new/windows-11-requirements). Windows devices must be supported by your hardware OEM. |
-
-## Device registration
-
-| Question | Answer |
-| ----- | ----- |
-| Can Autopatch customers individually approve or deny devices? | No you can't individually approve or deny devices. Once a device is registered with Windows Autopatch, updates are rolled out to the devices according to its ring assignment. Individual device level control isn't supported. |
-
-## Update management
-
-| Question | Answer |
-| ----- | ----- |
-| What systems does Windows Autopatch update? |- Windows 10/11 quality updates: Windows Autopatch manages all aspects of update rings.
- Microsoft 365 Apps for enterprise updates: All devices registered for Windows Autopatch will receive updates from the Monthly Enterprise Channel.
- Microsoft Edge: Windows Autopatch configures eligible devices to benefit from Microsoft Edge's progressive rollouts on the Stable channel and will provide support for issues with Microsoft Edge updates.
- Microsoft Teams: Windows Autopatch allows eligible devices to benefit from the standard automatic update channels and will provide support for issues with Teams updates.
|
-| What does Windows Autopatch do to ensure updates are done successfully? | For Windows quality updates, updates are applied to device in the Test ring first. The devices are evaluated, and then rolled out to the First, Fast then Broad rings. There's an evaluation period at each progression.This process is dependent on customer testing and verification of all updates during these rollout stages. The outcome is to ensure that registered devices are always up to date and disruption to business operations is minimized to free up your IT department from that ongoing task. |
-| What happens if there's an issue with an update? | Autopatch relies on the following capabilities to help resolve update issues.
- Pausing and resuming: If Windows Autopatch detects an issue with a Windows quality release, we may decide that it's necessary to pause that release. Once the issue is resolved, the release will be resumed. For more information, see [Pausing and resuming a Windows quality release](../operate/windows-autopatch-wqu-overview.md#pausing-and-resuming-a-release).
- Rollback: If Windows Autopatch detects issues between versions of Microsoft 365 Apps for enterprise, we might force all devices to roll back to the previous version. For more information, see [Update controls for Microsoft 365 Apps for enterprise](../operate/windows-autopatch-microsoft-365-apps-enterprise.md#update-controls).
|
-| Will Windows quality updates be released more quickly after vulnerabilities are identified, or what is the regular cadence of updates? | For zero-day threats, Autopatch will have an [expedited release cadence](../operate/windows-autopatch-wqu-overview.md#expedited-releases). For normal updates Autopatch uses a [regular release cadence](../operate/windows-autopatch-wqu-overview.md#windows-quality-update-releases) starting with devices in the Test ring and completing with general rollout to the Broad ring. |
-| Can customers configure when to move to the next ring or is it controlled by Windows Autopatch? | The decision of when to move to the next ring is handled by Windows Autopatch; it isn't customer configurable. |
-| Can you customize the scheduling of an update rollout to only install on certain days and times? | No, you can't customize update scheduling. However, you can specify [active hours](../operate/windows-autopatch-wqu-end-user-exp.md#servicing-window) to prevent users from updating during business hours. |
-| Does Autopatch support include and exclude groups, or dynamic groups to define ring membership? | Windows autopatch doesn't support managing update ring membership using your Azure AD groups. For more information, see [Move devices between rings](../operate/windows-autopatch-update-management.md#moving-devices-between-rings). |
-| Does Autopatch have two release cadences per update or are there two release cadences per-ring? | The release cadences are defined based on the update type. For example, a [regular cadence](../operate/windows-autopatch-wqu-overview.md#windows-quality-update-releases) (for a Windows quality update would be a gradual rollout from the Test ring to the Broad ring over 14 days whereas an [expedited release](../operate/windows-autopatch-wqu-overview.md#expedited-releases) would roll out more rapidly. |
-
-## Support
-
-| Question | Answer |
-| ----- | ----- |
-| What support is available for customers who need help with onboarding to Windows Autopatch? | The FastTrack Center is the primary mode of support for customers who need assistance from Microsoft to meet the pre-requisites (such as Intune and Azure or Hybrid AD) for onboarding to Windows Autopatch. For more information, see [Microsoft FastTrack for Windows Autopatch](../operate/windows-autopatch-support-request.md#microsoft-fasttrack).When you've onboarded with Windows Autopatch, you can [submit a support request](../operate/windows-autopatch-support-request.md) with the Windows Autopatch Service Engineering Team. |
-
-## Other
-
-| Question | Answer |
-| ----- | ----- |
-| Are there Autopatch specific APIs or PowerShell scripts available? | Programmatic access to Autopatch isn't currently available. |
diff --git a/windows/deployment/windows-autopatch/overview/windows-autopatch-faq.yml b/windows/deployment/windows-autopatch/overview/windows-autopatch-faq.yml
new file mode 100644
index 0000000000..31785f6f55
--- /dev/null
+++ b/windows/deployment/windows-autopatch/overview/windows-autopatch-faq.yml
@@ -0,0 +1,106 @@
+### YamlMime:FAQ
+metadata:
+ title: Windows Autopatch - Frequently Asked Questions (FAQ)
+ description: Answers to frequently asked questions about Windows Autopatch.
+ ms.prod: w11
+ ms.topic: faq
+ ms.date: 06/02/2022
+ audience: itpro
+ ms.localizationpriority: medium
+ manager: dougeby
+ author: tiaraquan
+ ms.author: tiaraquan
+ ms.reviwer: hathind
+title: Frequently Asked Questions about Windows Autopatch
+summary: This article answers frequently asked questions about Windows Autopatch.
+sections:
+ - name: General
+ questions:
+ - question: What Windows versions are supported?
+ answer: |
+ Windows Autopatch works with all [supported versions of Windows 10 and Windows 11 Enterprise edition](/windows/release-health/supported-versions-windows-client).
+ - question: What is the difference between Windows Update for Business and Windows Autopatch?
+ answer: |
+ Windows Autopatch is a service that removes the need for organizations to plan and operate the update process. Windows Autopatch moves the burden from your IT to Microsoft. Windows Autopatch uses [Windows Update for Business](/windows/deployment/update/deployment-service-overview) and other service components to update devices. Both are part of Windows Enterprise E3.
+ - question: Is Windows 365 for Enterprise supported with Windows Autopatch?
+ answer: |
+ Windows Autopatch supports Windows 365 for Enterprise. Windows 365 for Business isn't supported.
+ - question: Does Windows Autopatch support Windows Education (A3) or Windows Front Line Worker (F3) licensing?
+ answer: |
+ Autopatch isn't available for 'A' or 'F' series licensing.
+ - question: Will Windows Autopatch support local domain join Windows 10?
+ answer: |
+ Windows Autopatch doesn't support local (on-premise) domain join. Windows Autopatch supports [Hybrid AD join](/azure/active-directory/devices/concept-azure-ad-join-hybrid) or pure [Azure AD join](/azure/active-directory/devices/concept-azure-ad-join-hybrid).
+ - question: Will Windows Autopatch be available for state and local government customers?
+ answer: |
+ Windows Autopatch is available for all Windows E3 customers using Azure commercial cloud. However, Autopatch isn't currently supported for government cloud (GCC) customers.
+ - name: Requirements
+ questions:
+ - question: What are the prerequisites for Windows Autopatch?
+ answer: |
+ - [Supported Windows 10/11 Enterprise edition versions](/windows/release-health/supported-versions-windows-client)
+ - [Azure Active Directory (Azure AD) Premium](/azure/active-directory/fundamentals/active-directory-whatis#what-are-the-azure-ad-licenses)
+ - [Hybrid Azure AD-Joined](/azure/active-directory/devices/concept-azure-ad-join-hybrid) or [Azure AD-joined only](/azure/active-directory/devices/concept-azure-ad-join-hybrid)
+ - [Microsoft Intune](https://www.microsoft.com/cloud-platform/microsoft-intune)
+ - [Co-management](/prepare/windows-autopatch-prerequisites.md#co-management-requirements)
+ - [Configuration Manager version 2010 or later](/mem/configmgr/core/plan-design/changes/whats-new-in-version-2010)
+ - [Switch workloads for device configuration, Windows Update and Microsoft 365 Apps from Configuration Manager to Intune](/mem/configmgr/comanage/how-to-switch-workloads) (minimum Pilot Intune)
+ - question: What are the licensing requirements for Windows Autopatch?
+ answer: |
+ - Windows Autopatch is included with Window 10/11 Enterprise E3 or higher. For more information, see [More about licenses](../prepare/windows-autopatch-prerequisites.md#more-about-licenses).
+ - [Azure AD Premium](/azure/active-directory/fundamentals/active-directory-whatis#what-are-the-azure-ad-licenses) (for Co-management)
+ - [Microsoft Intune](/mem/intune/fundamentals/licenses) (includes Configuration Manager 2010 or greater via co-management)
+ - question: Are there hardware requirements for Windows Autopatch?
+ answer: |
+ No, Windows Autopatch doesn't require any specific hardware. However, general hardware requirements for updates are still applicable. For example, to deliver Windows 11 to your Autopatch devices they must meet [specific hardware requirements](/windows/whats-new/windows-11-requirements). Windows devices must be supported by your hardware OEM.
+ - name: Device registration
+ questions:
+ - question: Can Autopatch customers individually approve or deny devices?
+ answer: |
+ No you can't individually approve or deny devices. Once a device is registered with Windows Autopatch, updates are rolled out to the devices according to its ring assignment. Individual device level control isn't supported.
+ - name: Update Management
+ questions:
+ - question: What systems does Windows Autopatch update?
+ answer: |
+ - Windows 10/11 quality updates: Windows Autopatch manages all aspects of update rings.
+ - Microsoft 365 Apps for enterprise updates: All devices registered for Windows Autopatch will receive updates from the Monthly Enterprise Channel.
+ - Microsoft Edge: Windows Autopatch configures eligible devices to benefit from Microsoft Edge's progressive rollouts on the Stable channel and will provide support for issues with Microsoft Edge updates.
+ - Microsoft Teams: Windows Autopatch allows eligible devices to benefit from the standard automatic update channels and will provide support for issues with Teams updates.
+ - question: What does Windows Autopatch do to ensure updates are done successfully?
+ answer: For information about the Microsoft Admin Center, see [Manage third-party app subscriptions for your organization](/microsoft-365/commerce/manage-saas-apps).
+ - question: What does Windows Autopatch do to ensure updates are done successfully?
+ answer: |
+ For Windows quality updates, updates are applied to device in the Test ring first. The devices are evaluated, and then rolled out to the First, Fast then Broad rings. There's an evaluation period at each progression. This process is dependent on customer testing and verification of all updates during these rollout stages. The outcome is to ensure that registered devices are always up to date and disruption to business operations is minimized to free up your IT department from that ongoing task.
+ - question: What happens if there's an issue with an update?
+ answer: |
+ Autopatch relies on the following capabilities to help resolve update issues:
+ - Pausing and resuming: If Windows Autopatch detects an issue with a Windows quality release, we may decide that it's necessary to pause that release. Once the issue is resolved, the release will be resumed. For more information, see [Pausing and resuming a Windows quality release](../operate/windows-autopatch-wqu-overview.md#pausing-and-resuming-a-release).
+ - Rollback: If Windows Autopatch detects issues between versions of Microsoft 365 Apps for enterprise, we might force all devices to roll back to the previous version. For more information, see [Update controls for Microsoft 365 Apps for enterprise](../operate/windows-autopatch-microsoft-365-apps-enterprise.md#update-controls).
+ - question: Will Windows quality updates be released more quickly after vulnerabilities are identified, or what is the regular cadence of updates?
+ answer: |
+ For zero-day threats, Autopatch will have an [expedited release cadence](../operate/windows-autopatch-wqu-overview.md#expedited-releases). For normal updates Autopatch uses a [regular release cadence](../operate/windows-autopatch-wqu-overview.md#windows-quality-update-releases) starting with devices in the Test ring and completing with general rollout to the Broad ring.
+ - question: Can customers configure when to move to the next ring or is it controlled by Windows Autopatch?
+ answer: |
+ The decision of when to move to the next ring is handled by Windows Autopatch; it isn't customer configurable.
+ - question: Can you customize the scheduling of an update rollout to only install on certain days and times?
+ answer: |
+ No, you can't customize update scheduling. However, you can specify [active hours](../operate/windows-autopatch-wqu-end-user-exp.md#servicing-window) to prevent users from updating during business hours.
+ - question: Does Autopatch support include and exclude groups, or dynamic groups to define ring membership?
+ answer: |
+ Windows autopatch doesn't support managing update ring membership using your Azure AD groups. For more information, see [Move devices between rings](../operate/windows-autopatch-update-management.md#moving-devices-between-rings).
+ - question: Does Autopatch have two release cadences per update or are there two release cadences per-ring?
+ answer: |
+ The release cadences are defined based on the update type. For example, a [regular cadence](../operate/windows-autopatch-wqu-overview.md#windows-quality-update-releases) (for a Windows quality update would be a gradual rollout from the Test ring to the Broad ring over 14 days whereas an [expedited release](../operate/windows-autopatch-wqu-overview.md#expedited-releases) would roll out more rapidly.
+ - name: Support
+ questions:
+ - question: What support is available for customers who need help with onboarding to Windows Autopatch?
+ answer: |
+ The FastTrack Center is the primary mode of support for customers who need assistance from Microsoft to meet the pre-requisites (such as Intune and Azure or Hybrid AD) for onboarding to Windows Autopatch. For more information, see [Microsoft FastTrack for Windows Autopatch](../operate/windows-autopatch-support-request.md#microsoft-fasttrack). When you've onboarded with Windows Autopatch, you can [submit a support request](../operate/windows-autopatch-support-request.md) with the Windows Autopatch Service Engineering Team.
+ - name: Other
+ questions:
+ - question: Are there Autopatch specific APIs or PowerShell scripts available?
+ answer: |
+ Programmatic access to Autopatch isn't currently available.
+additionalContent: |
+ ## Additional Content
+ [Provide feedback](https://go.microsoft.com/fwlink/?linkid=2195593) or start a discussion in our [Windows Autopatch Tech Community](https://aka.ms/Community/WindowsAutopatch
\ No newline at end of file
From 0ddd9c33ab959237b775d9274b6dd4cf480bb8ce Mon Sep 17 00:00:00 2001
From: Priscilla Madrigal <104532333+pmadrigalm@users.noreply.github.com>
Date: Thu, 2 Jun 2022 09:52:14 -0700
Subject: [PATCH 42/61] Update quick-assist.md
---
windows/client-management/quick-assist.md | 22 +++-------------------
1 file changed, 3 insertions(+), 19 deletions(-)
diff --git a/windows/client-management/quick-assist.md b/windows/client-management/quick-assist.md
index 9591465cfc..30b7cf1123 100644
--- a/windows/client-management/quick-assist.md
+++ b/windows/client-management/quick-assist.md
@@ -14,7 +14,7 @@ ms.collection: highpri
# Use Quick Assist to help users
-Quick Assist is a Windows application that enables a person to share their device with another person over a remote connection. Your support staff can use it to remotely connect to a user's device and then view its display, make annotations, or take full control. In this way, they can troubleshoot, diagnose technological issues, and provide instructions to users directly on their devices.
+Quick Assist is a Microsoft Store application that enables a person to share their device with another person over a remote connection. Your support staff can use it to remotely connect to a user's device and then view its display, make annotations, or take full control. In this way, they can troubleshoot, diagnose technological issues, and provide instructions to users directly on their devices.
## Before you begin
@@ -42,7 +42,6 @@ Both the helper and sharer must be able to reach these endpoints over port 443:
| `*.api.support.microsoft.com` | API access for Quick Assist |
| `*.vortex.data.microsoft.com` | Used for diagnostic data |
| `*.channelservices.microsoft.com` | Required for chat services within Quick Assist |
-| `*.skype.com` | Skype requests may vary based on geography. If connection issues persist, test this endpoint. |
| `*.remoteassistanceprodacs.communication.azure.com` | Azure Communication Services (ACS) technology the Quick Assist app uses. |
| `*.turn.azure.com` | Protocol used to help endpoint. |
| `browser.pipe.aria.microsoft.com` | Required diagnostic data for client and services used by Quick Assist. |
@@ -105,23 +104,8 @@ Either the support staff or a user can start a Quick Assist session.
## If Quick Assist is missing
-If for some reason a user doesn't have Quick Assist on their system or it's not working properly, try to uninstall and reinstall it.
-
-### Uninstall Quick Assist
-
-1. Start the Settings app, and then select **Apps**.
-2. Select **Optional features**.
-3. In the **Installed features** search bar, type *Quick Assist*.
-4. Select **Microsoft Quick Assist**, and then select **Uninstall**.
-
-### Reinstall Quick Assist
-
-1. Start the Settings app, and then select **Apps**.
-2. Select **Optional features**.
-3. Select **Add a feature**.
-4. In the new dialog that opens, in the **Add an optional feature** search bar, type *Quick Assist*.
-5. Select the check box for **Microsoft Quick Assist**, and then select **Install**.
-6. Restart the device.
+If for some reason a user doesn't have Quick Assist on their system or it's not working properly, try to uninstall and reinstall it.
+[Install Quick Assist] (https://support.microsoft.com/en-us/windows/install-quick-assist-c17479b7-a49d-4d12-938c-dbfb97c88bca).
## Next steps
From af97d0ba7c5d28c57a0da8257749e08875c9b62c Mon Sep 17 00:00:00 2001
From: Anthony Swierkosz
Date: Thu, 2 Jun 2022 14:36:26 -0400
Subject: [PATCH 43/61] Replace credential guard group policy image
---
.../credential-guard-manage.md | 2 +-
.../images/credguard-gp-2.png | Bin 442435 -> 0 bytes
.../credential-guard/images/credguard-gp.png | Bin 33295 -> 276638 bytes
3 files changed, 1 insertion(+), 1 deletion(-)
delete mode 100644 windows/security/identity-protection/credential-guard/images/credguard-gp-2.png
diff --git a/windows/security/identity-protection/credential-guard/credential-guard-manage.md b/windows/security/identity-protection/credential-guard/credential-guard-manage.md
index a5041cd575..d234f67cc4 100644
--- a/windows/security/identity-protection/credential-guard/credential-guard-manage.md
+++ b/windows/security/identity-protection/credential-guard/credential-guard-manage.md
@@ -48,7 +48,7 @@ You can use Group Policy to enable Windows Defender Credential Guard. This will
5. In the **Secure Launch Configuration** box, choose **Not Configured**, **Enabled** or **Disabled**. Check [this article](../../threat-protection/windows-defender-system-guard/system-guard-secure-launch-and-smm-protection.md) for more details.
- 
+ :::image type="content" source="images/credguard-gp.png" alt-text="Windows Defender Credential Guard Group Policy setting.":::
6. Close the Group Policy Management Console.
diff --git a/windows/security/identity-protection/credential-guard/images/credguard-gp-2.png b/windows/security/identity-protection/credential-guard/images/credguard-gp-2.png
deleted file mode 100644
index ead9410405532311722ee16211486f868a63372f..0000000000000000000000000000000000000000
GIT binary patch
literal 0
HcmV?d00001
literal 442435
zcmYgX18}6*d^Y&b@C{byru{?)vv$
zy_df)OkPeL0Tve)1Ox;@QbI%#1O!~;^Mwb1`uwIdR!!9d
z2eiBeio6j7y60S|Sl$5kPdzqF`9NL@l=wwj6Y6`ypY&p~tVyAeo^%Q#bi^w8fwwhX
zJ@;!XMU&}H>z(`)W2bA7v3=)ue3c6~%brDj-h4oai;H^+MDk;ThY0`yS#VjRLoY^70ErPGGzSaM20;mf
z5cSIqC6*4A1Oz>!QY(5v4Y53tPD;j-iiV?8E9OhYZqF(xDEK=JlPBx1xYkTRys1J<
zQuAv-NDvu=C_YJCQ>DtIe|-vn2=?gA4kG^MCrV5bL%dtG`Xy1Boz{TNrg2uR;kNCc
zjs3m5je^`^iNIn}B$9^VvE*Nc>ktfA1tjLR3@~ZrC#7m%Vo?mke3~aseHgC>eSFbsen%
zwxn0&Eh)_B;qJZXDcY4g%HvwV3*)3{O7j2ncD*;U*&WCnf<%;wOuO+=O$RsVz#cxn
z%tp2es+z({C1m)m3)8NPn45iSzjP5csRgd^aTTQ%EW{*BX`$|M-T*`JWg+f)qkwXkij&^`fp}noE8d
zuH0i%H}4tkzwlL@G^BQA9*~E-tX!>WXVhGKnC=}=7f_+Y?%q7nljdH1%};pjh(2)t
zRhVKOy`rh46o31mbW)UP;KW$E!HWmImNkI+cu&SC##maRE2LN
zcX!Zx_~7PKJ*tz!Qenu3d6Ie)Qv`#8fGa(XU+mBeE}yov;G*@@sd?|DvpLx!b@*m%
z&k?5id2C^WZaBQeN8mKga)p7^+H(R6ntD&{LQYHZloK&UhGK~#NWur6FN}(|phLL^
zgAqBQvB>NFzZXU~bU4H!b+JK~Jx%sL@q{4zV=|es%~y#y$b9b!?c|$--tsYxUeb9&
z4BetzJ%MKHQN0Vv=$>PlhT8C)hLZcq8+D|&8KlvM&Hm3TiX94#$Sj4)()fMm_dJ|7
z9xGHdGdYu+pv$o;_)h043WA%!;LXpJTT
zTAo*~EsWu4@JUOVRwIM^(A9`wiSlx&%%A!Bddp~J!&)>w!1Rb?9l2`fb+rrr55wxF
z*!uE{3fsI%t!J=-1v{SMmHQjt_V+?bRk&`Ja`+0ht{Yi_ZB9a}OKm_WFe)x);JSMJ
z;HG@v(R$eO(?tP#V+IBW80Y77qOKo03k&z1Toz>i@vB}PR0}-Ixn5f7w}|WnLf0;$
z$PneBhUra6*}s4Pp06&nP}I}g7Q#ZEjBCa@xNfNVB_2
z78i3Gr~lZDqs`inqa9FmxTAZ2wf{QVxi&OPRJNNa$?CQjh=k4I&RyC01{z;DW^|mO
zA(I7!4En}bS}v4%u+?%d7WDhIRgp$=0CZ|~^)&^WM3rzQj*HramQ>|j5t~2#BgEV~
z3VXn~7^rKew2-7o;o!)8{p3~Z3N0AZrmiI=#v#g(Q=eF(UE+#w7V$zDt#bOT@xIL+
zb(2!r=^nQyvW*hNE(OygPcitSCnTYy6|q~WpK8kT{%Ocr9A?zZ2_`oY0!m6s*Uhiq
zR@T<9Jr^1Ogv7@U0ZS_|y)DVuFi88p_D+zN;(Y%5OQ)nI*qnOBSTI)aZf3m@olDmA!yV@aSD
zr7#&M03C@JX?rZXk1ZO?>61U@;Lcg2FkV^#1g%j?lOK+x_a-FlomjBJKfN-PKGTQ)
z1UP;+4vxl|l$|!Xv>6gZ-n_Gb#|4Z}O-FP(5E+qbL~&Y!YdW7W_7c?ml^6{2zdJbA
zHjLP;h@nS_?oVWlqJ0B)7c1m(J~Sq?T%K;>d$~cjzpVD%^Q?}Zd-C^YORHXPw^lWQ
znwBSzX{MQJ*mQ~C;HkIe_mxHeVLtyUsY#^z+|h3stIaUzvY;bgB$u&h+j?fc(ZRdc
z;*zJ;Xp0@v4T+^4Q+7^Uzv|XlCR`0Wyq`2#&xh-acoc-Q&s)a#^%TSE(2JLH!#TqQsRGqMQH~E?
zUVNRR;co6kpKBY}J!luSon&ilrm_X`y)L`UblY*wNnnLS=?OpF$U(DPT5!!3ruc8}
zFouCMp^{0$+O21?gM|4?2Z-1q{swhsgBSPvBctLz7E6#j2m73eNhVj&}AcgwxqQKjg`VZC_uRM2mi_S%#c&wCEj
z{Rh>ugZB_V=(BmZuI+llf{K)Ms<%dYYcChk1>(_i3E>P$CGpJ0tO(iJ-!F9Bo{yLz
z{E3nID(pz&^AWN|PLC<7;biGFfLVD_Tu~-gzwgj!qz{o7eeh_bSA*(K5rqK3+Y_zt
zL!k=2ppwI5pa$1!l6rQG`|(_)q+zjh$*Ls9$de1fB?K$G8CN@;hf}>U{&9E|2Z>UU
z!~!&H`-UV@JT#0{_+Kh|{ygJQ?9kt}LxRGh74PjaBTZifp!@*Jm&!-M@(=WCh&fe~c)vO{N_Re93i7ki0+3K))c2Rl4>_D?J7II$
z>pPNfJUqSd6M~U-5FPgs*sRPQbJ@`(cFHWr*Rf_6qXLD1LOMX11ieuR{MAG69w&9+
zcc|9$dPdt7hQ{s%eh!7dYlo||U<2&(9v1d`eWc~$n$N39zR?L2QEVejLm`_QWPn|!
z*V&M=#ARB@uHqVl=g>v8Lcp4-b``P%*3P8X)EhS1?4q-I`TLQpmYDO`WOGNW7C
zUVN76zLl@xSXPMBADBU>o@p${%MRb{ho}$zqRdK%sYz4EC4#%iOsJ3a^sNF&Ohy^%
zs|lIz$A`3(%X8Smb`F>_Qvf|chc4T%fj^rL8LlaBn=R_i1oA{kw#&XIW;Ean+g_~S
zSU?Imo=sOas(M(A{tx{x!;mfles(R~^IiZ>LWpdLCe+W;a4HBx8D#{FL)RAz`fU?p
z)sT%{T>uTz>g&P=TRK`4|Boq1Ff`>5VybLX@&X(WP_ieq(
z9Ej9N2*^UYM?VIF)-BKF2u0-05->2hSqqBGSIoC12LCZ8qh+nr`(9xS`53He?6Bez
zL9$Gcl5g-r(4qnriy{nq(cweow09=-dXByH98PQF3x=NVUENoyd2rl-PLLcp8ZxRR
zXE2yL0dyk_6v6;fK)lTK05tCJ1!lWH@b~FEUs_7q~&dwPv{O3rWWXD(dy4
zG^4{Vbs!bFPT~+qnV|rKn)qN8R0Jl&pNl;4K2`h##~4AcIFTSk#gObtnQ2`w}c@NZH*>TTfUa$fKVCnc@Zz!(Y-w<lHdYn`wy}Ok(NMhJVU5utQ?i>qh9EKAmGf6Ferp=IvfH+H9~E0~SF~;i{FQ=J#gzoh=zbKpEnFiI%wesxQ3t>DHbltv
zVFl2;YdD{#^4#pMy<};mPN*5Qx_sJw;6jb^rT;JsEb7XUkU(Hhlz=^Le~EV6Dk*vVjCOI2Sm0mjbonB@
zAI=5`Ykvdq)STwCvu+-De0L6weC2q0vxNuGQaVAMMP_mJF&e<6LD=kF`kUc_dtlah
z@}NG|A<*Z|S*&tT7@6Qtaid=wBX=7-D@pSGC>>v)PxY=VJNd*a8P=BmFf|>dZdA+i
zfakq@XXd`&K2&1t1HWH6q4WZJmzeS;&C7y{B1!r028=T7M7^8~Y;BI>bF6X((N+MldVp~IGKEf_fj01g7p_Mm>;x_P
zbr%CLMQ^x+?99@Tk%(*N8!nzLcu?XOovgv3@@t->F3xQ5kr%f;hb?&G@7vni`hB4a
ztL`r@0t7LGtXqr^(K+JLgx0geU5EPi-N6TnG%yJP^Yb@H-?t5b58HU@e3#ZOxGlUp
zrtC4`>CYfwlI<3xLqhMerk$>E;EcEv++EQUt6ly@S5taKGCtNxjCvCct)~G7*v{vx
zDL!w{1{$i@q!THuKPq%uXR3|F;d}K5B5~AJVKAE7uCGh2XLBe+s=x4@)j`h|eS@SE
zDun^Vc3-mRHRW+W@asj|Erk9Uvq)a;^T2~`h^DFS!-Pe+J!^%I=6`0iAxo4WOAbYI
z>l<9V`mu62SIw)_;@rd3V0vCAWsQ~#J^3XX*rQ6oZG^2gTdu`H@r^)S=Z)KS&BXUl
z#e@P)%TPeX*Vb_1msdZNx#}cS2HqEE-PQ|(24?Qs7s7VHt3_nXmNi4$7BwB{gN`F%
zJ3P42ATM*v>BLbW!{&7a8JhIN~!;3
zjvJ(XWT)}FD}HvY!-`UW)dkGzpMAER&y0*tuLHQmZnMnxsg>>kNIlKJgT_X?-Df|?
zYFH8Z*^})(=8plnr;s2x67=yOX#A>)B}S)~&p?Bjv|_KgQg
z?|WkR7cnNcU43*!*!Yu*&TxKyd${Tq?2+DaGeL>-&Ic02_a%^28_1EJ>K`8iwDJ43
zdy`wl|J+jexXGa#r1#$Ov1Bo&j0mfo?PVX&pVq+=xNNGR7Qh&&#bF1n-Sw2x*i_M!V^o|Wr=1J{-{9Ll?+p((Np@MDc6o1gY`%KFP7fZw
z1ioGAAPqYFdYT4$T-5Q8|70jk+#>pDi#}g#tu^rGr8@I{J-vwrBW!nl=5sPrIrdxv
z`))w*`Eb~uUkItJwEIXzH1_l+XL`3ylkW(4OM%Dnq2U0sMU^2e;?Pib480F#4v-?H
zT4((pNjzO`rL5*L8m{B|*dE1x8*`!_{@cFvU<_$hwR(16-o?(1vz*@xFHQPId_i&ICCV^j
z1UORtVK5u<{cQ4mN7(8vo!pE50_|`WY&L!IsOL14<7@n|mf6RYnIrvBjqkGx=Hu{g
z$k6NqnXJnm};GS^aAZ7G2$$GES7tu)V0eHOjN6pq2Q
ztnxJW+d2Fu-7|M6!y_@3+9MAwAED6)^B|*~-kayz&QJ8}uu>9U*XiyfFss0A?t}mr
ztCKFIrDh|fV|EFA81fX#e8gmzHs*7U7MCN@YU-A1KY3$6T(Cbz+~cS958vEvZ>=`z
z_5xUa`{)Yj(#
ze(}Wb8GASo^U;>q)98=lZ6Hs!>BC|NLzqASIs26g
zA52AGy+3%>`G%=x{G`iRJv)1z*-B)5sDcHaxO)?^wqgBQ*mBRlwrTo0H?bq7(m9*4U?g06h0-A!Mg9!Zl
zJn%>RWoP8&ySkF$?XlX)%@i|2D2?r@H=m)^;o9!md_$FS%Zm0FhI^i88CbtFw03jC
zhD2x>mw6l(+40-sC!L0qD+1e&tHQnj6}`sHyy$mkB??(v3@w*Al%mTXCnM14^;YMD
zVahBB$Y$%;=sqwYBF`@N{+PBbpP3+FYlgyS&Ws4t!%9OO4Fl^nYGtBR$`g|YNqwLa
zieR|@;Vms4fvvpAafJ5v>8hFzf%LmV>CnT&dVC^n@{T*GbaJ`=%2|iBQA12z*?&6w
zSBWI9cM&k6*dd=ijL)`E3a{tAsmb;3@K`!m{N8A?lAhj2;(W;~-KVXUH4!zZGeD}W
z+fLr7H#?Gt7*yT;(WQOB@<-kb3chCFmi{xFLdp7p{ltA{eiX%6kL%|5BD%R%A
z82oTXQ`7UJ_`<;ZLpnrzC~;w3yz?Dt+F?bDdHExFVohw;s?yhCaWZS?P!HIBRm4BQ
zIDy;SHA}dc*;>T3m5~U%9_ke!41&x_?lZ2BDO+0AaDW|rd$yzzt=nd#drh^xUnxPF
zHDjQ-fFiEtyi>8BHTcG&;ir-g)JM|wwW5$^P?xZTO-%RMzG{1(gCll%9m|zedK}h;
zuCllNOox+LU@U~Dx_HoZO)A$A^G$91>`2^}W?z>S+`*3J(NTgyyqZks=C!}?0J^qg#Xkl#%n)Y6xY60L
z@GF{4$S@Z4!Yk|0_WZIw(%qH#L`#a!2OqX9KXJ7n?X5fv<6M&0mlSItE$3j#v
z=>uRtRpw8dbU0F3@0$F>h&M|P#Ej}#%@?|}r5iI2YZnBKVfjexhcS{_t>@&?31K4)
zdKtDeJ#9&&MuptfpWw|hykHwwU!h@1!-r8tV-O#B9|#9jd8#H=q1xdC&wTCC5kL$=
zqTg9l-=ervS`ID2njQman|B&c{4r!wxI-8SI==OC-x}vjMw@w)uedHHr?Apchb6*u
zmNI_(=}sR0Wz5iYq1q;^*ZqFHK$1@LkE=gvkke->vxWaqdb0$QK&t387yHI((Ip@y
z+K#&iiIeH|e1Sdi2V2YxK9Be1qLb+BR~NtCkEkc+wU+PuKNl!BTeB1N?^mgvnc%s<
zp9UFNM;n|9yp*?2R|IxjRr2=!-n)5PZ&=we!MFFqZ*f?idPL6S~GDuBg19B!f3^C9Dxp7ywu<MiFb?Ja#xv?=
z&DsFsMN;WMMLIWWehJ3j^JG@hYc6wM#cadjsPF?Lv3Q3;;4R{D%fF>EA78SXPaDl{
zS_RFnUvkv!KW6Qiw~^wxw(1r*A6|pCnXM6$;ZsKH8)bJwcm|zb+IO1YCcZb{H8i>(
z4|B<+H>I0p5`e1{^8&!MNwHW2;>#dc6&$z+KUxBCyRiK1yJ`;W&s^!WRLT=On0k++
z%^Wuc!HaD!uQK}6U7r1cZ`+>JcVr|Ko%}B{gqXXINIxC%w_NI5?oBGy
zm#JN$4tH6&*1OY$z7bxBYF7b|DfpE3qqncC2tr>zgwWg0qNiizpWhxVD?
zTl`HF$i^B#JJ^kv_t-X`T1*~V=T0Y4G&&@>f3X0((LK>P-VfyIuPYHH;;ksl4f!#R
zi$)I@wbnXfS=pZ9QMatE~=7oSpC|A>`QbxARFYWs~ZvoV#+iDKIGprWi?dm)a4)Wd)PZawP~Q_NHN!<^=F
zwaGN7!I+@x14SmQhK!4{(VUlm)rN>hlvh?g-TN9u_kCq2_U;d8eVjtx#9j+eX5W>+
zBC9lIr`!e6dwzdUnNXozN+0v!E0GWtRJt?lB=7@u{7F%&=C46NX}?7#wj&U-$4$$)e?}t+~6G1ouNfBbSIE-AKDIvCD3-hsR=Oag5uXjk>
z&L@hB&L_-@r&(~|)w*`3N2~vj%+)T|O0LK>GVGUb&Gi)StOx$|?z(0t?2mQ2fuCuE
zk5@#j7T2T$QNG`bRFg@9NMRSEYv2q6w0q7l%w{hlrOm;-h{{EwKq(35qa7|}W?G7A
zuGbfRYtQaqs=Q>s$oFcP5e|IG)BCa`D90V7p8j=HWM3{_s<2st#B8R@m>T+i^(Rsh
z!%qoS35iTUx`yPvnus6vN04gqc8Y+EW#pka`m&wllMvR!ww&0w)?XW$4g8F+Rzmp>
z6=uR`G7abVN=X%wayP>0E)uw3k7)c4*c_$|yxku4kS=?B5px=*DeU}@PDWq%1Du-9
zGGnP~62>eUaBuN4-5*gdg{7>L1B(rwgRnR+i?b9MbGV7NA*wD2p=-S4jHexh3w7j7r!4a?|6o>c-@pY+MnI!QT@U}N95Q5#+6of
zgmXr3-WZ8FZ6e)oM?6a#eb3H>*-y{>oe+4*ieE`KA)9WE@y*KQ6*|{Qk
zgFSLcShNknpxvL%b3*#VpaG6rlL7^SC~Sw{4=Ro{_Xh~cf(}60`xA-kRHj+Yg5xww
zS0kR)0eo$oW@E3&`+i|N_Um0i`rHfBRIsty@=eNh$%ThP=2r|8o(|l2ZcAa@+dWrg
z@XhbK)@;AM`2Fj(s5Ny1TYUweuSIwKnbqHTiN?>6i}(MeF&_Lzc|e2h8ezV8Q{&3s
zfazPWD~_qRQg!MAeYu%anw+X#m>AQmV@px`Z_r^6LJsp%1YQ5Y+)IJ#g!wC@vlH2l
z=)AFgS72q^J)zN{tjYEq4!x9GHZ4(e
zLVTH&ZRsP%V5SS`(qj`-pM|BN{zp9L{bM|`pHi_wXZ!P1jYS90_`rxtw<%GVVt*b5sK|R_^aRfBVD0%^=tKqy*y4AGjN>vgh(`6yl}*R$l*J!
zf`m7SXK&WfG8}yK?SK~b>)ERrojhRlZN@6V*De~e<$2hBE)~yy8;{FRpv&a_$@_9^
z_&iu@&H_Gm7jZPdv?>0vkcAM8oZlOO6VKFg+BM^Whh)#&eYc=HNY4=kf?G9?YukB5
z!tHV>YqF=wrZeiaj6-=n$j=w5xEXKIbtKNb|Fn?DSwL!~Hr9Xm%)6e^tT~9GnL~jx
z5~xqW2=qc5%<^U*pY|%Yns7Sqs>QxdbGq`1S1DDUdVuEND(9dySaSbUt|xXdLBMt1
zv}2F|L!);8vTtWH5R8A!VWi6k_^=9>z1dRwqo((MCC=s^1vMSn$9Gti3LnTg_%qLT
z*N+!z4pRb*LJsf8bOCP>d`nze5q*Eh2`FfXS+&;@jgRlT=<+zDvx9YfvYuC%>%bpk
zm+Qz;hIYRT=OZZ+H8ObN9uV8sClYq$J&XyA$`TJ<6Dot+83(
z!Qr<_NJ!i1!iy-+DyQfR=2lB)NT3`~Gk+!U3SPo~6?LkM94oV%{`)H$3CM!+QyCId
z%SBhuK*0M?sy)!*shmKr*UK-Dd+p$l7STUr
zPbt3M3i|mVkqf}JLXI|HVXK%pfj+5B0tm_2aZgwooz`PzCu^#r62e7$g8gvCt@~IU
z$Bd?Wv%5(CdROw$bmK4H^wPcZcyOrY?%C5@roo>=Y~6P!6HboBF%^PIIThZbGILkz
zMZBXyMK|O%*3O|l0CVsf<&k654)^TQsWHJDT5KVe4-KS^0JQa$U+%t}
z&E%}HTem0rPxDDp+F}f2U_}Pp83^h^T{*>GsZrpCg%6sjs6G1x@&l_QkddAc>aLoC!Daf-uSV9E2D@%+K_~0sT5w
zrez#_Z)bj8?=xAsr~V^0c9S}jqj2fwmvtV6M=CGd<~xsf`@!*qa2(tAJ&$D^C?4yL
zpRSU0ik=hPFZlTvmybr#Qw1xo*kYdd>o#VXW0~FEKi-0VFN+CK)*gP}W<31kgyiFz
zPBFZo#}UWB?m(YYdBVBJ%Kk0dCu}04)v%8Ba6JzVOP39Rfk9F+YQ1^7k={Q$`JQID
z4rWnfy!GSss<$_#+L-t5?kNdXCKKF;{@bcA!I|f6*Wn`p_t_j?o)MND&z-dplC{#u
zBJjO05c>?F#rb@K1e&OSl(AE&(??v1DnY%qA2A!uCBEEQiTTOB-3wB6Xde>oqxt(Dlz_Ts$jV?Ateq2$JfI(R>Kw*8nTNcVo1zn*5ZvNV^W
zGf6B>cIx|vnA1KTt@%BfTy8ttmbESuL@C
z=L4(qj{T=65xY&>^D)^UIx6YPmo->Jr&_7|(*S!c_3H_oo!(#b`ln8Ag8Vh1ni$C$
zIL5i9Nqm^7fQ9wU0pInf7%bhauCid2$PaUzNtyIXR;8rt?Ohchmn*}=+l`5B$BE$k
z{g9rU)oX3r-Mu+q>J`+a#c@YmZ9x=G7Gg1@
z{U?PL}!CxI<6Dzqx9rxpP_Nk{%s^rbz#tF=FyoPFZ972%%!z|V+_{z3N9IQXFjslo
zy_tYfv{`Zp+61tb`WV15(Jgl)nHQ-lyt(xf^lxZzhS`Pm9(o(Q(julY$ie~r1k_(`*B8y)k;918^GO)jzu
zXTe{P*XT7a5dKj`rK73pK|!2UZRQRFjYSFNKd44`pG~nCk1GzAC7JE*tI9%xWJq#y
zDhR7C+wkl0YGAA!GDxG06!elMCmsTmhQtODV@Vl`txUqByrDaBJ`|tJK
z06%dvW|NtJp;fS*PyYO5&}q@fhRWb}k!pB2o`>sY($w(jfT^O3AO^%J&g6+l_XS{R
z9pDe<q%71>AOH=oc!Wm+uL?ql3b!_;7!K7~za
zT?tZg5aw$OcaGRJwE%X2h2ax-FQGpS>6CHYq9ztHsk}&qeFy2Kb9$<6Hai|Iar^@n
z20;u(F)3s#HuWQ6X6eeAzg!A7QmJxkGZZMdR*qyS7D|?R+m|SG{hXogQSR(wNeOG+
zTd%S)?(9(L-GZKLQ5G_{4pVI!ksyYEm`I&$Zl!2~XL>0+T1YiT8jS4_MXFt7#rQh;
zreCUjOIQ);y1DvVx+1Ij69R{zqTh}#@4ZPkHU=`9huOhiy9r{>)_oyW1~JJ?@Np%SkK;pRhvX5bz7TOa
zMDL*oBTt{2f#D?cs31`QHO9q<4aUtMIqL94nT|H>?jm*WuD!jfDU0;MWG+dNr(!p3
zl_g_zXrn?gc31`ai(CCc%Q!&YCPA5wz=jRJ@Sti0_+x$ZP1lB+x=;x;$%!fMB2Tl}
zzMcKH_q#MC+fRG=e-{zs6PMVmQuB!sr5q?Ssnzf!n;u*s$UK-{U4@UiRgg;QGf#YA
zZdg}QRrRqrn}lsaRu@L={=#3I!tTJ8A{HE{iBsQ;IVy&o
zU9Uub1-Pt6E`YL!Z4#J3GTP5E;tl!(KkfwuMwCE?<)%R6AZeshk0=>VCgOMC4{)#_
zcGt+)1KAK1X>>(b7xZHk&4nK@LU{&lmSH#OuD1Qn4`GbQzKNy?Z|zkC2r3&lcJ|E0
z?cmPwhgg}l5u@B4S{XME*U;w2wS&xLbO?YaK@fl%t$>7dT_2?F51J#Pz_Km9mp~>7
z;-j&rPO1S2N#(@H49D#lYPPV|oGi1k&7q(b6&8l<*6yeen=RC95ukr708v6*zYUNYpNR
ztB(rg&S-Q>jm!YBAev+ESaRvXGJktv>seBHRHEWhHieDVAh5Eyk^?2|lmcx~soVr}
z_YR2=U3VPb7Q4|Dv&_skqWYgH3ICD~^iZ|~hWAQF;ex>ouyYe~tE*9_xP{6#1~xh+
ziz_Rkom)p?3KVIo4f`$D4U9N?8DanOT*8%YLbP)J(YN3UF+o0~BkemOlA2cma9mhP
zDqmSlCKNM0_6TgBX3Z;FZD64%sirm#4p-ZqBRHWhO!sQ?gcHDorB
z#LT#y4oTw-2Wk>~=eF3H9ix@a7ZOePNs;pa1zzYd*A+z&P=7iDG-NzV$0gHK8P#~Y
zk~iAmYlp;$AAO{eR5=TT6+-+F@fsw1@(Mh=BTRv#nn_qR&OG~Z8
z%d+X`7eI_^CuBkaD-+n55t2_3_5Q{>XDtObA{<5sE3T!8|T8Yd`N3
z?QXn@MrR^wZQ>2QGEg8uKY{E|wi>EJn5DmeYZ9c5?hP5UC^VR`k4QX^vm2u4ytV9x~8JMP22I`*QAO;%Pk=IBtR%k)#U-h%%Jss&zGjMK@)S_$DwgMm7l3C3^gbw?Rpj1UMySC&WaAMYF$(
zHDT6J$e_s~MPQwR6^-(u-{2H2I*%
zLoy;k^Dkc-%lrHSB!@M`vz_t3Ap;U-#HxfONn(u4;R)j+b-M0cREyTLp|n5P%BZk&G|>Fv=q{FmjbT!j#035+0Bdr}7tUncoAlL4hskYFy
z;`Xq4+9*?3KzTEC#YkaE7^Iv$CcHsLLeyB_%F<&TOSs@;IS0ga(fNp5Qr#m
zmWoUbIwAv~f98z>9*|X2I{u)E9-?6E
zjIqHuIEQb-Mda4V;>fLh(XjZ|GD?w#IWH|KUcK0{AlEhirx8gYaxM{LhRa+IpHjrd
zk>NJIZ6Ucfqj|M*+<&w7QUQD;lT?ZZ8%hR$0onktRO|lTqnG@Ao4L%<(vDAS0eMU+pR2(!-Ogr^zNCAC(
z5&e>CdxTV1ofNs^-V#l|4vi07s1-J8h(rhL6@&;$jZ0sust!y&fkg3X*$@rH)(;2s
zcBBRTZuGcrMmjWj<{pMb@QDpVc9%*YGUYH-HlB{$h#SXzG?MXBI|X@C-NBh&me^=P
zBsh#%I1I=&UG~+25<+EWAp%N{ByShMjS*-S%>9SLL7Em!)|`AjU)|CEEy=L|nT0!Q
zAev5^)VZEZ7>XF&Yf=P7QO{Z?!HkHheMm>nKaQ_MkIdB9zj8KYP(m?d;O&m!bt*z4
zLp3SbO2|CNtJP!#fE1Kfr!pKfRe$@vgtF7f3X2_OS3cJdHiNT|RtVtsCICxPY2%6&t+KykbGw1q(^
zluRj_u$C@oX!D6i17ymnn`FmW0d`DC!n_q_Wds~k7u(&Hf?2Jl`l`yKLbiG_)MUSE
z%y3jlVvZR_;&q6vm=sH(HdM|Qr5P?stHyAY9@TMN%Cju@zl;
z7I!Lor70yM1`i5~7(hpY5X2^L$jgTV#saaMi>r*7a|;0Tk2H+Ir*)K!
z$W>xoXey+{mgRM>vzI)!yW+F|%x6#`a#Zlw36q@A{vnHkrKQI-g^3rOX1^bx5NB16s5c~D*?4T9()7g4+Y5OE`*iI3$?-wl(f2NfsGNn;=wzN3n}tTeyPcI
zhh&2RXbyBupEz@^+M2-z6-Wpma-Zd~X6dw$V6=hbv
zu1zsyA3bc
zupk8ee?c5=MVFh=GaJ!B3=X4&^!Irbpod{7XJKX6mCM;hOQ=$5M%zWCWsBt6+pOt9
zi}FoXhqIX8B5pQI=3>9idC@f@kEbPZfqMv2@Kt!d6+$}ZIsIpj^GPYpA{v1aE1MLQ
zj>N2Mf*$ZqR4ku(;m)%Gi(bTFdWZ86)B{vY);x*+g)7*Zk!FN8PqdJedJ3Z*vjMhf
zTF7&&QVML<#}dbx-?hjzTY4jeRs5I}dW?I_+V#|!36v#JD{MWoDOa08ZYtse{iW@#qP
zueDEZ-SJ`57>vhJdP=ao`_6tbN=ahdNwYybz0Wc~V_QFLR(ngJfAE_~B8lz685GR02j10&@Fov;_0Kl9{m~TAj6wu87Ry<48+Qr1ddCAmL
zX@3w`B_}6YhI1V)+!=f^RxuVC7!Dm9x*2%LxJZz~n8wwdxpGX?7xX3M#Wo$>!3Eb#f{&sFev9JcrsC!b)X)WR)J
z#HgL@-|Y8#xzq!1IU
zUkxD^THq&->V?rZyVXB|6+5y&xBfO|uvi>3O`)T{Qw#&_{3C!)V0@7pgv082Cmo}x0N-BZra<=P!O
z9CXer!nNM$Jkh2vzmfuNaNG*R%_P;MLeHfRqx@~34k^^Rn`m~8sfOg^UZ|+uuQfFq
zWLAV6=#3Wy8+m0$2kY7##cN2327UzSTP-H3o~x@G4|KCL+T97S)Y;3zO;YhAI#ydF
zbWnN&Qg3pMb>pG|DGri!qco%O(-9`m>QO-^qv~QPqhm%~M=XVUx~5ip2ha_)L=Pkf
z`j_?4D_g}TP%D;rSQ2*yqG!owm+H-(`+456zr51Dw2!g1K9d04ros>_%T9TFK9BhB
zrhIKA-i>6`W26N}-*=Z4JU7|$*LK{lh7lQwQLulp00)A#Z?J`X2z4*L?7nU2Z-xwS
zPcwWWIVWDXZ?D|i=Mn#!N0(jdU-w1F`zCr=T~wx0{`|86){@lkK*uI5UdwAt8GX8|
zkS;hpGnB%@rPSv*b663yk8SR%Q8OkuteBk;tlKP6d8#B&0L)u0iRXtJbe%oh}JM-mcw;I`x`?-{4EL8;x)GIXw!AmXWh!RbS(^q
zJh(Nnq7DQ#nc{!$Vs((#8bTzJf^0^AMTMVZo6BjWI@3m*JU4|1%W({y;JOP_n2j_g
zgL6wxJZtEye6HXLc28ZqO3jINdt}}|OexD{w@Iv+pt`@EFnSN)$EUcljXxje~
zTOwWlQGM`HBmKwjSQ|U}ecgNP;nLCP;$Mg1ll&k1MEL$16KRpH30s)h@4$jBhB_NN
zl!{to7JCI`$&5aI{yfG2u$E3XFry8Ql&vD(_=X0D(v)FJ+T@gWQa{@D>I3hH$P$XzA{ZF9&caHa8
z@b%i5gkkX}6jR7cm$GIGGVPhvMIB5Wd_baEr`o+G^K2WCCtAIN`6|fWP2I1^masdqu^bqPH)bK0#Rs$HG5LD>12
zzFkJ{Vc`)SUprEr9wu4TJLp|WH2+^d5-t8OSPv9scQJ4eq=lO1|5-&SP5pLl3{s%l
zeFizUfxIO>V;sI!4{!VFw1rj#RQOjUCm%KhY~c-LiBlHE4&h_6w)<}-P48G+{UC_s
zVc$LLnz}F%#-T^I^VaarLF2h^dYcmSr`SM^oeg6t0eTkffy?g^b
zS1sr;83Yf{^pfT+yBQNPKHHDkk5it-<9;UC5WXRH7#Lu5$k=M^vm@SH^@{`i2FN!r
zFOAj(b=)p$U3n;Y{wJkvxB-a?NO{V)^g&9fVuQJsxb)iMlWf$L!hP40Pd>1MJ>HV;
zB)lZrKk#;yP6HO6ewyQoIhTc=+{8IN150x;oc~wPcwVBh;^X3Xrs6)XI&}50e=4A3
zvQF0P4z{=g1j!^*eQM1_`CF7hTDR!o?Zu&U{nq>sFP3oyzU&24f2mzA<6=8HUrQDm
zG_Wd!OKNtnuKXoUC`Ko7Qa+z5lW7L*E8sf53EHlecG?81sl7N$CJjNw-Nufu_O2_`
z*U0VeN&Np$RAcU^ag@&$~`?hJT;0)zi9uux5S(#o(=NE6JVb`!8Wyx?UCK4;ghHcVtvLurn
z3%viJ1ZA+n?^4-9(;Oty`u*;Fh
z4}Pb|iru}^pj5=5Nt9lQ4$(iN${70bD8^bEcDNU#@>!K_LN36WH7G%9dl{Oizb8ga
zN7VnXL?_23Vdk45l1%($4OwC74{FwSn@t=_X>qdioeKu!@K=pexpIl0f)lErRfjh`
z@hXdACB;$1VhyXYyZ=z{JTp6EFAwF=Qf4K0*AO_b5d17d4Wmkr
zk8P!BmRk!I&Pdp;k<&PDr;B;|NcN-ec*D=LP2N~Hm~&D-o93ucWvbx*u58bB+|nbf9@2@O6N^(t0s@m{MSpb?Nzav3;aEIs^@
z!r5T6?S+(7m}{(*5bmKu5pmo?T`FIKonQXTiqBjVS9g{+-sAa^Kz@vh!bDOE*Rg<%
zhDENV3R`z}0t0j1)m}Hd+%h)F)|-6BWxbsZ9j@}Qe%?RSsbKA?PCo*QdkdH4K!3P4%9>@NNp{C{SHc(
z-&n>f)7;?ya&=9oSY#!{p$n@*u$Luf54X9$M%Z&PL{O8@r@<11tee|aSOX-ur
zQ5!HU?D?2xiX*;z|BqeHdtE{iLw35yMVB=d;nBOjM(y1HF~Ye!IY?&S<*&@@=KxxFUH0CfqHj|Hi&k!zt1x{I*V|S0^TmsQ>z}y!
zAkMW;c645M?6vQbbglQZ4(5L3RQK8219!Ygc2+wRl|*+ZSPNb=8*L1VM0kxE5`Bz6
zCXWOp(*knL6j>FoqQmUca2DxH6ABObCiKCw@EQCrfj-Y})i(WVoVHItSD%sXcicJZ
zqbhE|Y;`W;iX5M(*=evMb{u&Sy1z}cJL^(qkLQ)r#(_Sn7}KT7D$!#(=q8KgeDm}3
z6Ptl%`c-+XHdjj@;m$A5PqaUh%678ek$u1Jmo1mxSaUz2c;)lM)8nrQQ`#158PD{NlJd2I
zbbC?L(f8B%;D$McBi4=&?s7~q&zw|ww}^D_VDnev@>O}>LedD_ua8$577cmZ`_|SH
zROA$jGYFMtTb`5+dGW)1#c5!L;(*A6e2uG1Cs*8ciCGR#yER!Kqt8Ji{%dc7veRI;
zn=7cniC7SvnDU@8t1%{Szrz8H;pbo4M=+X=-&JY}Olow|NG{a4N^JZNn&O5G#P^r
zw=@_lEl9&shl1EsyW9lExHzWQ*1}9Zacm#GcL?IG$s#il
zP;IR?cf!aC_?;u`(*dDgx9e1CR5}ysFze=++5wYcI+CNB#Jn{DUr3?WgI;WT{$?|j
z4i&_rDPLJrNeXWG=Aw3Pk_@kl#o4g|Vz)c6=z*cw+vs?*S{>r7
z^KCGHAm4CDC(4*iDJ$+@1F+|7(!#0Ds(q@i*4jjfrd|H{RFUb>&;)EQxCgzMbihJ?
z@kY~`7fTwRC!c1YWJgrQu&}VmDJlxlpvStP5l8v*MVN#D2|c2h@qxa$R4cYzhcTou
zarz0d`*&Gc1enYpB=s@du%)#%tbaSO+dw1-rH0;U*_A}&T^T*Z0OdQC1x$@FN<7bXp><(-=7C8nFBqd1^6Gm+C)9*nF_GYl4K6sja
zr`$hba!B7*BBY(ak|Ebh_rMZCbZGnVRYUxjqyqfB_cfzD@sUWVv!b%k&t==c=_c^=
zQ)`Yy{fr7aHd?#RV$(`=O1t~k2+E}76f_tDp3hhAzM3a!gVeF+TqSis4RAp5QhlmX
zCM!)2)*A1=j~NHM5iv%KyRCw0(Lh?~C+>G(X3wmn&OyqbHgUo4b!H~W)+x!>X%F3Q
zHl8BWlmbzJ-5-O(yibSy#`oV}6dsBF9`zqb%-#~9hUcAH7^3w)^&V5ja!k-;114h(
zpLNGb%+PiS(1GpC4>6VoHwuKm#*7X;Gz663e*lJ!0>K2m6N8qtxMJdx6m+P3{WXdv
zL5IrvMr(f`Gb%0qF)1c_DT|^*NmmYe*)i>8cf4V~O%uPMX1^YHm^|G34O9m71E}W%
zwc#f@>CILi*>16+Vs~4A6{W6fCu4AsVGi-~6;r6;?u(L%50FtFptCZ?)RmeF#n*1B
zJ)!7l#YYdm|EeuIet2`?x}3|%c6xe1b*v07DVT6U?XR7*ftOM}fU42rso{87Gtm{T
zm6e?@0avpRgKK3INa8Rryv8KViNvjj4&SJaao6vGln2gJ{Gc;mpg~V2r9@$Avb+oXoin|+!3Lna05_HK&l?Yy
z+yBjz0kl-ec0U9iDP+*J_P=yzMisfAT5V)*UMj(+BC8BTk|-TJyi1F%{!^ARqC{KL
z5bNn5tL)v`lJx8Ws`XkE*7~Gk0ee=iXa8~iR1R-_k@VfT(!Q4vGG#&{)&PVHqkzJkK;=lIS6H?8C#
zfZnYF{4_i_fru+N{)wVT_E-I}+SS^SiApw)u(+%NHEpy38D$)IFx>0!;jaz0zy+#G
zXLPEOP*ycSiK+ecw*|C3pgmyN+Ib#4;!M*1ri5tS-|cAa89~86-#29pL>Rn?^|bEE
z&#ecRC1#^(s{HInJV|zZBH&9!AIUOK&5D<1YIn|PM&&D;t4dWV?7G)arMt0Xr5KK4
z^m0_`u_$7w^DZ>Ex4D|89$U8Sq8x|>(qfX4{rY>xDQENm%hlKP$fDjYZE{&`*pn(=EoLPp)6SZ9RhI7^YX}TSnyZanXN;nq6$lSvZbl`n%11WF|s
z(c3CJl$r9=>+AZ_l!%e_Q!a$6s(?pbf;0tLtfW{Z^tlK{yp;7a@EA6aE8{HRCkwT5
zjgQ}0Q^83lI`exogL(W{7q2I4^@(GZ*D1ljOmM&HQ?Og7akjO+8iO!J-KtLr+I(W9
z!)~0j_EU?9O*U6FB?n>K3k+z{IH=?==J4&9osOIdM!QDRaN?vU&$^QYta(DL+!Lgc
z(r|OyJ%r-*aC*acj}OjdH=1}4ozX-;DnscqL1Jk!zbSh^Jv|MCI#`Q}j5#aP2mV$U
zmfNe&7xbnQt1C)9ZomDoJU>So$Quik$G^(HbzTmHv#=Uwcz1TzsP@PbbSF3ne3naQ
zmQ7Wvf|Qz|Y?1z!B*Qhh!>?kqx?{gPTNL)I{+WR`sEMRS8NoPcyd@>8S+KKf?-Kv_
zG)}HCXCZ-h8I@mVj2IPJ7;}Cu=4SJSCCK_ng9mw*
z2&WcPQtjV4OR#~;nKZJgEPxo12zkNk>ev8i-%yS$Eu{_@adYGPZ|BY54w;Fl&PrP@
zOoSE{TFlJNIUdc>9335f66^(x)utB~2Ex#(xP6}3FWm|HX|OZDf{&-i7pjeLIUQ!;
zxiynB_BL^MyRb{m;%;ondimJ|7lwr1Z_ISq9O)Z{_=4u=txYBi+eY+i!Zpv!cORjw
zQrmBQOvil!X6-uUud{-j&wK)E)Acu3I-z=6Ad^!bNoIwzdzDn;wZ_+sJ7|(gkW=@R
zn#e5aEeqBg%p4(wPOd*U^bL8NEu0ea1p9-NMjEeglANdF&)K=CK3S529I(1T~S!2#e4Xc|81eW-1lCWH(hI?
z&XcgdUw-QN!M)T!HCD6Q9FDC>cDKNciuJTNnMYkYgxu~D=v{Z3MS=nq+9`fJ>K2*#NLu*IPYOvZ+_J{ql1^
z_N8~(yY0EssO`^A;A~rcxzFi!!Di|>v!kTO2sMQe!-W27!j;+pE;HHfdi5d}-xUz=
zk|=C7yW<>5Y7AftgJ3$A(w&f8RBd_-4Q%)fj)lg1=6;B3-T-B3`EN;wXyUcbLnD|!
zGxSNh)dsWBch;-Jr3F@+>}GJf467rVJjqW-cxbUiYbkGExz;aiDx0>3|Go@G&}-ik
zwIZJtHI#f@t!ME`o;#CAA`%)pLOh0}`jR1nB&DuMA5fk{TI%TWR}Ek>JNge=^l$^%
zQg~3m265YO{4;^ne0jOEu(PAW_&PZ=(^Dvy{#~`6Y`OhhT?sk_OK`#^v#(Dauod8O
zJJb1BloA{a4H!Lhdt8BLXJ;`7@#qtrnyd6bcIX0rLEV3(@+db<85}*EwNeeFi`zw5
zi_mCzMiyGa&iPs5@cRV%-LeTrAyo2vXDr)I*VX;*)>|_C%np>04)zGe?W`Yn2_f7M
zYv?Ds&V2Z0x}&l8#5*S?xEZC|o!jVsLkvRCEHVwY;9{M06*UCRax0OzKroZ2uoY(+@mHKNO
zNRc*?+xY+mFb6WYJ6Qz$3b_fOq5CGdp{pl6lGyrQJ8U{9R9uIJTh^9SsA>XOs&tbmbjoRc6Z1-;(F^7
z@xx^Wq}q0ok+noE&>sH%p^>ZBMfI~taXcH-bsmN7TzOC4$Wp`T<%vrPOT8nGXc8^~5$F27#
zt9GARE)SC}kjVa$`@@-+$Mx*I)IGQwoLVoFeBGl!Z18}&ZVG(wou%9Dr}k(4uH7Wy
znKfSDJJq?Yw_`O~vLnT~x}c~qF*zlf-x^RL
zgXQ#kJMYxnShbhL=i77A3?CYp>zrX{viSnF;xsOx<21^lw5)I*bb61YNpG`7u~TJ5)^bdOK-?Y%W_YEz!=@GKR~UUNFOO>bD0
zgudwWIzEKkee(IY-q@pZHnM3CXc5>9-R%61Sqe6{ih3E`;f>fMltgD_Q;VZ=>i{!E
zgfp0ex?SSA#e;OpI~29v7HfmgrRej*oR{SuTIIJJ;eA{7o_@aW_!%O|@~aeX{HlwN
zDL#$@V|e4>Fn;9aF4*PceJm>a
zxkw?q5U8HPWQwt6-)aP3`5$-U5z@JzcnB8%u?;!#;1&j+(S^2)jt+5J7FBTECs(jvMh?EdSXIBc8n9#D+I#OJR7co8
z^b#5_L1(i#Sr`b^%xm_V@u6R=i;mnUr`UWaF@AkXgf}cB>pV#tiH3
zhbVFwe6r%QrA!-%QM73xCxb-d^e&%Qf|WQD%4LgNL;A&|w=(bNerQ6kX6ouZj<4@6
zR>uQl)Fh>qD2JgJvmNhvZtJ&3fM?h*l&I>
z`Q%Sq$Y%?VT2;06@tyw_%~7Gp21Je4^TJ8P7TU*Z^qaTpdcU6@3|wuWe=@yhzxQ?{
zuZ$0FQ^5w20i(#!$S*gFc=*e)CdqmvXv+2(Xi2#f?t9cuW^Fxn>XfKn}S2qKw
zf7{$iYf?I6-rC@)0E>RXcklq^=N4FtecOh*4}`#kwgKKz^wm}V;YbEAq_0*&
z3hdc*xs2@KYzA|g#ffybG!V7^_OXJ4B>{|fF*$=Ekb|_Q+aAcZmLY63t@)A>l^};2
zbxUH3_P5ayR{?@2rTdDTZynyaH*WCuE4$Y0-j(%|8)M_`e0}tn`aX({RZ&5Emfz!?
zn?}1al!(_CiJ8#4I>-JfuFJFB-MZO&CAR~R{>zKL)BY;*!~*IjSeMNSyJOhK?Jeaj
z^yfbIumygLzfm!FOV`MJp?$B=tAO8K$h-ghTe9DX{yT)};;b(-!%`vc@|){3P@x}|
zOPiTdQAHE%j4ih-oR%16@Oy?@RJ9GwlqkbV7@Dg!uXr`F^-R9P;6B#&FVtOr)>+@4
zsLmVFyui8_yit~)pLM(@Y-9seVZ}V!GW?YGFBhoo*Q0hUMT@i6M06Ics_J%%;H|1BFE8AE&%$2|7$6qxv|(B;
z);kFScC=xy&(SE@U;;i!irR1DF^)#It;-_KrXMs}+8|s7)Kgott%o9wyD>5ZT?%};
z%fyan*7#Drt$}uBNw`dB@YYjVaIM|2T2I|KD=S1MS@&?v^AQS$KA!c-u`5+N562to
zK$SR2*1;CJba(e2*ywDY0A=bQ``2J}2ZVk~b=q7U-spY3J3zSdkBT&XR1GAfh#_5o
zwz|4{vQQmh&aPD=?L~tol97NyPSGO?8!&7H8-^poABCcT4(SJ+UqFHEaHImpncN~|
z@?=D1-}Uah=ZSU9Vq_Z0T~S4|W%PQOmfmt-`{H4-ZL(2L;
z^fIs6qT#2G1q*}+~;#YINbL*ZbO!gaOkSA@!lu4Grr$bb}ss&Bpq%o
zk)-|psK!~b7@jh;WsbEuhg8{mrN2;ZpzKkuP>rq3p#H0@vT`qqYwgF@b^HO8;oz6T
z|UlZ>p1JTaiI`q
zyJx&T+XU;}@jQL@#@v%6h?^3>O9V0ypBOxi;1clqe(0~YusGanReueQqC++aho-tG
z*nX;77uR;dVL|P`+@8r?9?Hj-_+xuZ)WTPj&q{d0_a~8f{gVC?g}PLdce=X}5yt)E
zjU`ZoR7F7E%T3@K`!$2wkuR|c(8N`!?`gn2)$aQ^{e&-*9_t=h?h>orC_v8J?6|;9f{g>8vNV2|X
z)V*5yZfuAIK!#{a^*1=C1cw;yAD)FfuD2mqU$wbV*Mt=;!P*e22(bKeQ?CM*9m2{9
zyj+xOFV@&{wdjH8ufa=z|BEB{tk+%qh`71A(C7{v`NCgMmdWoh?fZXhmO1|e@MHCL
zQ)`5#YriNWvoFX>H-`{7Yaq9Gzndz5;%rQ!zJOA;h$6UkB|(W7or&^<$YyL+}24L=`FRvUjM
zP0XpF3rtZA6^p0V#AJyDO|6RZVv$d+3TtbBHsqD(PotPg1k0L8Qj&qmDh3uY1Tq!T
zSW>~VAha{m)Dub!OHwqn2{0iK?QhC00Jfow8=E6jNfvQD9{K-+MhEh5eh_b7*9j{Nc1dl97~)CH+S2}U_2F_Vzk0cn2@%F)vyOpK^B*k
zX^%}VI9C2G&&g^D_5>boZfRMHVFg@)
zX}HVerS}OJe0+SmXJQ?}6f{kBb#;$+p!<@Pgax2W?ZpNlLIVd+NT;oCG(<&3VM5QB
zRaI4;R8>}1*1Q01dKGnbWp#B4;LL?x7wCJhORv_4Tc%z+r6zzWR7({%|K7rMe@h3L
zZD`4R4E=_9_|8l#uv*Vd8`14%Vv6CXe4i91mYmmaezG}hzE_*8)E99%6&
zutk`l=9S97;5mYv6mAaqN{9c7m5r|@P*Ihba@i{F@n`GTsCK}lDnm9pw0P2iQkOAW
z!b?-Ojj__&xk0X$i;z{@+9=uP=V%X~P3KJ5U$3SYInCt1Ke?vYsgDiKHwx9vH%_9;
z&hEXTI7ZzvsHvvr0y>LG)^_=H6fxhGaWbJBeIM0a?N%f>^9;>glynVj+da7@+)hR1
z!XFBwXr)tHgh3dlQ~6RW_y1m1}dGj)B3oY>*@s>JlXBru5U}Jyweo(UT>|pJC(e
zW2G)u7NR5M#`)4{*>sk{>X8pD
zYI@zw*wU>`^KrvvMwQ#7Go0d)!F6B2%6t6euFjPP{IqHNKX_$5vh*imhnjA
zt!pFhrf2S0*TnRyHx`&iLgDCpd&6`2;P+|7o^-YyR#u;ev9(OT6b>t_{qbxnA_(xY
z_rJY9KMpGRb_FBiYjpSu0O5OYQi9k7xN&<7S&|sE`?`YQ7u&30wA8w=8N^pF*oUbY
z#1QWP+#etXzaR9^)Kg9b5lDIrXwvJ~#01&-{Y#3X;%Rdb5^6cp!b{iUA(laxHd*vJ
z__E$~WVyuW87hueT=R<>6f+Iy7~Gc-HqLq;HP5rIA-bkIu>;!fS7mWIQgJ<5=xq0S
zPT}`pz1|x&8ct&P&%QE*$TJl1ZJAtJlBUKmoUhcS*ZA|3D%(45kGEx?!dmEWc49ggv*C&P8ek9NEZ)N^`{W3v=WzxY+&yBQ+8D&;
z`kUfxM7s4W^caJd;+bKZ3U!>>^u~RzY8gzMDh61mEP1)NTk^xJ(^G-+
zB{>6|pG%h)9y>qg{*rG0G8xUy<@>0eu}~A`&N*_JL@w*+f{?Dx2%7N(6iZq53ZW&+
zMKxykAJ^9Zq;l;un!fg(76(Htn+}2_Y&B9^f=cigJT+^qudno}KY#Mo6-+f2Q|wv|
z&9vc;lUGpZsy5~;O)seDljA*(P1?#=W{E=$a)-#$~=hM@W{z9>&!a4(`
z;$W2HOoB54QviY5n41gf(AU`Fe~;Ju)$|b}jF1GWJbXY^Y(leSW+OZ*Z=Zq+_t84v@%6L7=b*&8awXeul|e
z+``t{5O+{`2HGVDp@h0U1Dx(KS)hqXCfQ+rC2
z!^FmX{I2vZXzFxM(b~`7xxVAkWk_JY(FC%G9;j_>m-dgn?OwgIfy!^|mI
zTm!vTvokX)kF5<2cb{;r&CQ#BJV)FMsJt+m{wePHUV@)c1+E32{3<<#GC<*U_P9`S8dNX%}F+9!N1*qSn%i(gyF
za{2l?Xf+FMs^5DQiHNV+hvzCqYKL~~m(#|8s>>{e-w0`6^iv`Iw8rv3IU(FZx@+~{
z#kf;BMD5oF_=|0i>;^PJhI9wIc=Io(vnT7GA1KPUN}vbFP}Kcizeb;~DX2+qrE^A`
z{=lVduwe0f^X^j-=$_g=pCXKym|B#VPC7sc(yVdEy?;OW2oSjuX>$v0Cdl*pKA-oG
zwH2rFEVc6X+!@weEx83MNN*yAI~k{rZ*wRysDGltO|Lp8m_(Q|U&T)HUv03lb8;Cx
zLYEfUzj-68>w6$C&t;2Xfuc|O|G9NIlk3*QQQvOuPOHq@8FyVnF6YMQNx;^Bz0-8P
zIPFIhksV&XeVS)8x2Q1f)IN8(&m;#(Tml$iYT!1NiDm0Bwpcn$Wy-Lt$IRWQ&-l((
zNS4>o>2}_B>mu67yacug`DByt-JWAG2|=2>Z*e=s-KftQu#T5!O$EgdPAn}A#Zk!M
z2zqnpQcum#_lINBHSK44Ei^k(9XhA=Mqsmf-B}|Mt|;&_enahBVGYM6*CWR~GhGjB
z^S&P=uJ+z0N=Omy(CQg2^swB?`^#&C`s_A8?OB|J-|h%CsS%!Hi5|}$J{4pjqARAW$IOcwhHk5sHli?Ii9<`=tgF{Y=-;W=uSgit~E@^wJv>{iU+0%
zC>}DFtsv0lYf645_6j_-8xv=9{@To+$x!ifBXNIm6rs#Lzak~x@aKdeyc8WfcV=F7
zdQM5guCu4MHp8ych#yyqT>`UH`M#L
z9pO@i`OO6n@2bF@)|6lg39nEIV%)(KO(zSxt0bBvIo)^9-f^TZudov_*t>o
zjp~oIo>vsrlcNFDT~V3>t)^pfgt^maacS|;z5@gfGD%de)@f&nnn3c*p4?Rs`Pai@
zc~(-A9#Q9hGUp)j{5Y1t?^Gg9>CVz5u_y;fE|Zu@s0u|fE&*qf7^-ZNpy|50x+Jj@
zDiJR${7p$Jk-zCGyyCPBB(RD=#GI7;M4Ci~B}dvb1%%76rce?PN}%I&{2(_ADVTdo
zN}(zKdwz&HS#*pvx?Ff*An0_}fEUnhEq;?ViBYnMi^W;p*D|*$B}cO;C~J*!mlZ?P
zojOD)aSn8^$s9YQ1Wl4<*1?9vfyqd7yF8{+iMB-WSdu!WD8n+!x@%Omx>xIhx50t*
zS;jf8{X=oHtHSKdVy!dc5K?=_8EN_%QCbXfX$mRO7sKkSo~}V~a8pcS5ud!aRj4Gl
zm=20mkumV!!oYyi0N^QhCD%-n%F~Y6>e#dMN=iz|C~j|WXEG{wS00n3dn}p5RoACv
z<%|S4qHftUtO^fxoWxuiqtSGwtr>d@as>mHk=y%)74a}CI&YdID9pZxLN@}>vI#&^
zOiN2k+FUgNlF~4;P%Db=T3xguB$jqI=+fI^cZB2|!vJ!nW7eZXD%`u7cq4lP?xYgTMlc77SrbM35AG)pBJ50;kcT6mrN
zm_45*WUf7@^7t%`ogH1jIJipCVe^m(C8G-+A3y0`jbvQ$+1%ZyKDT$=llU%Ej~q)1
zQ^93NncG7{#(%MKci)Adt~@`ysx;2V&P^X^B9dl;XJ+$6l9DD%tn4h4{yhYHo3Z?;sey`P}OpTrG_EQhRk04-s!i32(^Xn+n%>v-v5PrW_JWhFRk
zEC#i9#8T|aFxp#(0$*mU9_i2dZSuoPQAbaj_IbBqCTSc3+xVwEqv@A}XR~P~Hd*nB
z0}Jc@8N2tmR8nNY>K|C&$L^;Kcf
z!*;;9|%w@o~qY`%3#|W
za7s=zr|;eBG^~6OuFd&YWqRdyUG`gGo7cVL#=noee0+yTM_ZdA#Czd%mA`@F=<3R`
zvUv~B_iT%eC#C6mR7XARzX930F&QsdSs+L8A!<(
z1Cta@RGv}_`j!7_!e_;AT-Vy`77EXjuDE!ica-Zr8W7thw|@b8?$&xfx2iy+vH5z8
zk7qYQd7<6Mi{|!sM@RPCn{SrK9`2mbJ%1ETnMG;&W>@X_?jconZfRj!a0AwmCG8>e
ztOXC|JMr?V^GA$ovVJdS
zS(QO|gmx%JBIbbBNKoL=qx(}FaA^YGzJ+BYRo;zYqd_@L^@6YD9&NP@)qvp^VMH!qt|lvv0V
zh4eb$A>(a0!V&25`LMlEWMLSbMIpwlLF3z0xKW!8i#SI|zbmSfYHH?-%W2IlyX3g3
zjcOMiT1F(LVZ|c0uX`@Nl$&%(b0?V@$G^aJhSmkGkQ%zOH5-3`%m>dNlaS=Y^@B@Y
ziAdNDsCMsSVcp>heYn41BXx!d?69yBycl%7eb}^*F=qz~qpoxK?falGF|i(J=nkd^
z*wjmMB?@v>BmQ#^V?^ZC6oPE(kDWI+?3D3g4biSGo-MeU89$5-GcFHlC>czH`y?#R
zPYY{1u%{Qy;cC`kafhc*q6@35s~f*m7B~w4baptUi<{f@?5yf1%GyQmFE{l5lW5Fs
zEVJho?3|q9`ufDDr>FmklG)i+@TQjw1R2-&wEcId8j@Q-SALrdeuNiFV$uGe)n`O8`)^!igY~{9kt?kjz_C?91{*T)9mquL6kO+7_%mh#(ylwH*4X7
z00z%eD%@gkZ|{2`y9>wd%S*=f!%2sC7}M+Ze)G%JaMMjNhxL-%2mOhlaf|KJh{~dz
zn)ni2woZ+o6A2KjF)cZDQJ6|xJ}uTLuc0BAWWCNG5?l`YC=3j-iYf_pp()azQDk~F
zz21Gik9*Fqayp)1iJyDcuL=N&%w+2g#X?F7RyN+D7dUMzZ@-cLm4zZLO;NUkbAoGl
zTcEy`bx8vMwL}9?cPJ*_iP|96gF=+`M^RO6D*SkRWKG*`lYn4X7;KJv%4D^Lnr=(*
z-qFWTjKr@DggS1Wx3c%kF@d1ppW$53JYvz`Zb5ISfy9?9!6EiuMeg3KNbRq79h-J<
zcU2E#Vfv=GrRf?z&5H3HT-lqCQ3{S-^X**{LQlAY&x=f#!}^(hW!id%`F@`|$U7Fx$upqI5Zecn`MofVYZyqLDZT`)y
z2eii+*cp)n$9c2(-R3A2OBS_jsHQN<1D8QeB2Y{8Bm|4`3d5*8MX2iTyAdmq&9%
zLsBv_b^_7mH>R`S*!5qwuz3#i(cuAwC?|?|&
zjZQxzy4$H$*?#2NetCO-G1&18L-g<}pwsw7tLJ^I>YYQq=7632vL$ka)Ua_+m6{E+
zoRG<;z!No}wH{hb73=6QbZ@iOs{hO{^u7r3*oqBFtzNo#e$DV23o36rCr#7xO35^X
zs!_XXpQ{#0^0H3hP_Nt~e%~X0c)85pX6yIMVDi3odbylLl$G@e6Mq5!BKkG<$4
zujq63yg`ayU>^4gC)vlmhJoEW{CcT~nB9w}%Mej;Je-a#6V@>T5K~91tarDrnKpr5
zegC=B*5#6YvrW?qThl5qOoUA2_5s58?H{pjf?{$##^Bd4k;TdV$0Qhcs8JHI!Jija
z8R=bNTp`4E)I%qqWVKBHXqnlMa7$6e0YfPPYzjh&$OLW##E%2-!(r>sSom4%;r)pu
zsj{e1j~6fukqUR)4q{~U~Gvf@TVD+>9V=TC2r%WS?xB$c4MIm^*Qag{zP|)+5%>`}eOCqnFPkP`^@!
ziBEm`%~%-XsGQDIW?>G`>&
zxES!L`jyG&rlh7OE+YdkCnpyf6=lGhDt)UpJpGbHrt0J4Bawf~;M3rICQFH~tE*er
z*vQ7r{9Vh|qjU=&a-2CuzApDi%fI}+)ukJe%YJ26T|X+9+73>$wDfApiqHLOut-rg
z)6gMHgTC|O0W>bqm<7+&oN@}|#*ALQ5tVY;6yndm7>G#0Dy;U$u+aq#R^ejnZolaz
zY4)VJgd}M=c3>QR_A6}ai6W_t8fLCiI9w~H*#LwDS6``DHabI*M(lsJ0APBlGnB~j
zg_Nu`5+aBZJoth_*%+P{mm_Lq?RZ<#5?$dl^__PTH1@uG$lsC~w
z-FXMEa#+Jach=x>Y;rUybcMjnM_ur*PmZh*JIZic^PPNl40zdF1(vFjJc_sx*+|2B
z*==WD)Gz*$AQ5VePk`$P06?S>J&meya=ybVV(%muuo4(#6K#zZ*N!929+Z|UMvEau&1=CSs^1Z2ZHmQ0!II2G
z0ydNk`{E%-nHh?9)m*JbY2RuMCigYgG)xOzz&lj+F$Zq^7d0{1E{F3w5;y
zf-s7Gvkt%(=RvgEf2N@g(%?Bge$pk(>AX|j+BhvY6DHd
z5EtI(Fy4ehk-7B=mIk-AI|x*mLbn$)?T|~#bs37?*eybRK!L~cbzGG}f>H=#(kI6r
z*K>N6SHcsRA4q2QeFxzVmy59o`T7RIHknv+il^>Fm^q%0nsD6j37>L)Pu^%o<)_xRI>*r&-gSx@JqJLL6|$8OwlbQI-O
zV-80qOX>id0JE*ir95VrfWzU{j_JpAEz`u(iinw=!1CSSp`c`){^(5AhrdW&g4l3X
zlC-~pMiZDkI6X@UMMM%5Tfly(68D|@8_5n;TqIhg_@7qYCT~3gA}%RXIWkfb5EyL}
z)KG%!EziVQgqXdq7jE3U-RGtY${-;K-@XnG>z|U$6=x;gx`%OSZ3Ei4fK(nBI%OWe
zXn|!aq$}hx0WB1XlI-Lp!_pmUhI{0ac5&C&l
zgC00FluBetLK?xK5eoKUYGmPWWMqo_PPNxUy&1Z|>SuRCqLuA7e*68zljV-Yw=m%?
zEj$RNS%46?u|blTmzOeX3QXwH2z?iR^#AG!{d9gp-EoSU;-M0US
zw6E~0vfI9X5u^pBLAo3129fSY4jqSX1O+JxLAtx7y9Mc#jzfoZgLJoioA=)P`v<-=
z)G-)x;CY_2_u6aCHP@U!v4bU+a2|9rwD`EVBmjL1M6x`bj*$^19bMhs!^0jZM|?th
zTH3F@3oK-W$~oJ-AHR5|@|Oq}Q!>2w)(xLN+SiS%fv@@OFaBuCs1fPEkEYIv^v}1-
zoxp0$Fgwe)yI;+?10RATGTs&ip5oZ-Xh&%3&+#`4!NLc>pa=O)6_1{LFW>K4)XBmEP_r}sQ|9k@XY@7v;~@${q;v(A
z8(buY)bHft`CTkYHRDgZv3{B13RA^u(wyq}de+I%ukrpFTC;Lyz}1Y4Qhx?QqhD#q
z0!2tNG0ygwBq7*86D}^ARCvK0yu8xoQFNlZZwGfIOjNQ^
zdKuZ|urxCsbrAA)YKF{1HYSDmxg#^ClVdGV1fLD<@pFX8QFtIrrqD#=jByCGe#!LA
z`bKRo+XJ19li^{B!Jti^36U|0X?PyKV2jX4o@XJ8=Kk)LV2xz>cV74pDrtkSlBwa%P6QZaE8p
z9Wplu0n>;zH8r7ar_Wy@WKFVBgYYJo2h@+C9E5eTsQGa!rl91cVYRF)Ei>PEAansjz_(g+-i?CR&RV#~eQ?J)MduB3hH1
zekAt2rrHSsp(NCpN7{);Tq^Nfx431>*fK2vdIGJ2ys)B#Di`r1-s=eS8c65rn}4dA
zu~89JC4>DER#luZ7+BQOGO0x0Q&UoZ3uV|SRbpm&879?-dy0crgIvW&C~GVt8r1t*
zV)~Ss*v~Vop3gXhs$jiPEvA$f>xFy2d6=Oy+<10KHhv!-o(!!7wW_%K2ZZ}qSWfGn
z49JST$1@1iXTv>h3Z~WS
z4|}+Ys%>o{!BtL_DEJSi!f79So;O#!vl&FDfA1BWjHW)6!@jx+4r~T3lg=!@RU?Gd
z?hv!zVarE!8DX!!A)W+!BCJad7?ESq5`-Alj;x#^$aYIS8zEQIqa-+f8GiGv`$fUq
zP_vZXT`Qr(e@>F%@C}ragBJYwnMYa-*giI;y9vqh5&zn|T6JlvY!c>cfm`rJ
z&M?ABWcx<#z$OVlJF!d$W|o0cRRPuCuHmuQin=_<51`zZ!oV>
z*LrYP9~yNmqxl{eZ$(3l1+S2T#d|UnN=1sztqgAbv+=EhB1?g9-40aI3ek@F$&tgV
zVFfR{D2Pc#*)=W3?JTU#5x478ZH1)!UNbjPHnx!NV_+&JMjE}5rOYzoX>#=NlgNH{
z67ZIqh>if`RR}`xucbSej-p^$+Fr~V5k&=sQ81@v=S4!IpMH*kG3r2MGH%jil9}b;
z_ANhxM=GCIhKU0&H6A>Srw06m^59fT1@Gy}e%Iy>PHFV5m!sH)sc9KmP`Nh2qX@*Je=*@)`
zFf~T??@%ZFH_=^=IuFR8>o&?xW8sN4E#-m7!~qr*DM3)$Pa1u4!B%S_GJNUOMg26N
zI+}}fLa=V;o>gh20eS>W9{muE!iq6V0$s_1Elt
zatU#$OYP*a!Hg@8Bpi9Pj0!yt2ynS-3><_xbZQ*QT;;B`;v$)Jc)>X`0*xu+3MBzl
z>|6gZyeDTI_@^&1GSkX+dvl``iq|oIANAyaqZ|nX@Goj_txmj!jROPB^D(XUI$ypE;H2METME
zA!Q70M`x+B7B)mFFJPiWQ?lJxOmyNHprQ6f{3Rw09~WAck>9(I8EFO*-}3ux_^bbz
z95qT1=m+O8$!e$?K^?zrXSgTS+RU6by>{qcf04Z-NnKm{zt}d&GYKP^(d!?C+2~9&;-09HAI@?*9?xpnek5@+A^X^+kVEnjlzG1Jt
zY3}bW29eHder;V@MRk&{*qr(Y5z1gbeSP7$M3P_jAIGOA2bo~@og$m$1jk0T;S;0U
z!xJ!}k+PplLyMo5ho@NtcXmn1iCz)xkgdLz{gU$QF)cezfovqs?e_h-4
z%QpT8oBLjvPrKryJKFrEgXw_K@K%9=MWHo8$6T8jH$4NY;j!KC082(9`y8Na-{SAOmtk^u>80_WcS7`y-yjJ&PQ=>9bI1BLw+B*_
z;2jSP2)60Eg0fP4yOE1a+~wuR-vYncby-|4F2*@W4T}e@4-Pks^j~;&iBpd=^w810
zNmg+A_z{FN2~$%l01f4FwJa?y+e186kG7o0be$>{EO-zU@D`S$7kUX_Ix3tTtD1|m(&c)^A4b9rjHJBbqWry
z9NdzRHSy6ewEN`vIn;c^G~TLL7ZyiknMC;jpVmpW&{GsnI
z_xuYB>7X-1s7_;InCtoY31hMM^@l0G-a%Klg&uY}`EAn^@0$;`o^@%rmoZW*#n|VeB(@aq&sKLp4evTG=3b3>omZQwUGBEGpWFbGQ%Ct*G~xhw&#C
zObg3g`1$~Q_J4R6U9k6NDteEuCZ-k#pX2{cFidx4UH-d-S-%paImuJ|
z3R@!0fGk=Dor18SsxCy=p*i7oMPpbvOju5H*uE!U`sDez+k;i{pFi%_52k6iC1fXL
z7HOR`Z5QH)t=p<~2eZAV%AzCEkAK;226#na6(a(PQzhj_2PyK`BQqjBqCO`R_s2if
z>mU1T(O+OXui^Vh&5zh);UR_N-T@d?z2V|8i2w0)@Oq4a?!)g-J|j$#cIM6t3e<#V
zGp#KPj%SMZD{+~Q;5T;9ZR>aDm6UI;4VLHUwICUe?r?9t2z0z@MlcQ4x_Nv-30coE
zrNIsYsn2H*k0P7GUi@QDJ`ROXK4c`qivX|-r0ZpfC>+=Afp{=@N#7-)D|
z0ajy6OF9T6Apa>WDaom=#cf(t($#$pl<&YMU3G2%S`(Wq9sW;(3yqBeV8>VKl;v$T
zb#-+;ZDK$Vla@vTB_Rkh3E2knUS*)0{3K72ljC1k#{)`4`N4$v_$r5G5u(?x*^?E{
z&(Fc=9~{WSc6N4*oSkEQec|dHmLs}WjiAr~@RpAUzs)4ht!=DqZF9j70o?Z?b50OH
zz%NkK)g8C037_0Onw@428Y)N2~S8Bz3!Q!#A$6QeIm;2A9u>4JV
zFTYBw?`=Z*!p*4Nz4_FQt$>P><40fWs3ebVndvc#!6ZJW6a~f{%0C<_DYQBHs#D#v
zKQnmL(x9eTMV6E?86wZLBWM-*1uRL>pd?xeVHy&#p`r8f_-x}GedFVZ#H=h8-z=?D
zy2u#_9vP)zHCTKsVl(5;a?{#Unu%~)w{PNDyj!^lr}2#6#(wDWp5jVLaGUwZ#tMtg
zTtbbIP*&gXt=CE805TzoD%1DE2CNMh-@w8)!b+}9nZ5z$)Je9EshEfx3Xf0^Qjrm-wpg1WjeD{~12@Y>Z94>;Kfx2>(_durKp89wi7S63?-82EWa
zyD*}BkTi*=H>gPb>P|nz`Z8D^XG{BkAdMNx{`&M(V$JRievy!4R75Kx&w*R;vVpU3
z#Zloe`}ADT?T@Wz-A7fMMRw=BKRNhErEd;f(k^2stO^~>On^SSt8i+a{d(i_V&82d
zPv!0Hl*EY_=xOeF_&D0!j~m3Bz2%Il1{q>}>2;r0IMjJF*PS
z%}c@L5~-)LGA~DXydQD~t-Q-HA9wh|%{;Eh@mmM~*c=&q%!z=FG?aY2rMuUzv8Q?YKHO>7`JovZH=BsmKCiV{;2psk)ZEq~}s
zAL&m?DNO20&4#zR|QUkBw;
zet!PW-X2qj77)r99v-F^eZFAN3*c|?
zzSA3_Z2Gl}&pje+BYm#WMr=x0J2lvuWLOB~&
z?g!oeHY666+Zx;c3Y;hGAd`JV;yh||P+(D-&hSChe*T|?G4sIRgS(as-Ft!=s~6RY
z4JV=wE2UHT)w^%`y;-EGeURJYyrkDdbHua^V)_Sq>c1)^Xh_kNAaCHpX|iV%t4Y0`
z!rtg+c4xOy*s1~h>9yD&<*_P5dMbe|*|S3DlQ-vux0G*K;G!!Dia3@gG~AsU%w7p<
z8sN=EVYX>i4<0^qvri4LWoLE=A|R`M8DUKX~xpAX!v@_=Kj^mgvST@kvs!z~_vM
z$R@?o)@Ci5j&$4C)#n#B@;YX3QeC6_)=gr=#;J{^{a(*{#Is)_-TjSi!ik-g$zpb#J;AOYay4+Mjp
zni_1`n4R6-tj5MhgwSXigpw&a5QN0V#SxxKO&rq9>OP%2=@A$Z$Vk)i_@^(-lBU~x
z9{fiO%g#M)BTvi0`AqRs_2rW5!p}?NX_0y`Tz9mQAiB`GcvZGq)q7~xHGz3LMCG#*
zeP_S!>*283ie$eX2@`6^{i)y8-PRN`V~w$vXofY%Z(=?DO^p~Hx=CZ&+^>K^krVqK
z3kM1($q+S;`fU!OIKzl1or(=l#!NCGt+M{bgK%Ie&9N%}#BB(o%q|Ls|1c#qp1jbA
z`4a+^WqAurqTk_qKfGe9tD=_6n$~t-yr0G1kVO&}c7huYJ5Q=AO%So}Lqm^8Q5c+QP4-DfZV}EY}LDwg@24Cmp7F&ORzk
z(T*CJE!5I6EY(4$Ydumpd}6o9yoOUqXz1YQ^2mg;Xz2Vw_wH$x%_l-k;d=!9`%7mn
zeJ|k)77{oASIr$Sqh$izm;;tgdwJ|S1vvwwj*VQyj{9OUKb)0asd<0@I)B(4n)&x0
zN5{k3?Q>VoK2t?bV_oP7DYma=lzfFiVi0LlP)eYA0F-#!h3R!hYx*{?Q15h$$1(Lm
zm}1yzmk)np#-h24!rb`>cgcvTaBv;(;Q3laK!*y@OjLxzW*(Q`P465dQ{}J5aAr(d
zn;98>3Cx%BgcG%Iiv-Q-KdGrZhetUzZHX!Qh&?P5pqDSuC;-mXF7ujb1=`?lle`S$
zkZjPZ1W7ghMJGB4cMsnA1qDD^F1Mf{sHlj67(=@My3@P{9Q1N6)rg3Q1Y~5rCRI-r
zx}6;h=y3z=8-rBnTR)UCSpncy9pA@lnA4T8!=-jXo^ET4-n1CeZDI^AEF*&y6bp`g
z#9@(<6LWL@Bk6*&d1`#=BWmX?nXvV<8xSnA0KD+~w+@#gljJCfDIoUL%qal25{Nxv
z5fNDEh|8`Mp}2jYeg2e@%R{s-ou_Z4C8{ItbBsM@Efth?XaD|Yt!r*fx6?J;j!*n~
z`e*B)xzY)nt))45=IU_e!fT$MZCUo9!;4EJLAAvPf78Rj0=7i5Up_nBF-=rQy3hsO
zug{ZvUpW(Q-0zzV509n3dVEhVudcBM>B8{VieRThr5_OT6H#VNd^?6cgd&Mr