From 55aff11d116cf0e7a345a3fcd83ee57ca50e528a Mon Sep 17 00:00:00 2001
From: VLG17 <41186174+VLG17@users.noreply.github.com>
Date: Wed, 5 Jan 2022 11:31:03 +0200
Subject: [PATCH 001/415] Update info
https://github.com/MicrosoftDocs/windows-itpro-docs/issues/10021
---
.../identity-protection/hello-for-business/hello-faq.yml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/windows/security/identity-protection/hello-for-business/hello-faq.yml b/windows/security/identity-protection/hello-for-business/hello-faq.yml
index 66e88ee1a6..b033cf57b3 100644
--- a/windows/security/identity-protection/hello-for-business/hello-faq.yml
+++ b/windows/security/identity-protection/hello-for-business/hello-faq.yml
@@ -100,7 +100,7 @@ sections:
[Windows Hello for Business forgotten PIN user experience](hello-videos.md#windows-hello-for-business-forgotten-pin-user-experience)
- For on-premises deployments, devices must be well-connected to their on-premises network (domain controllers and/or certificate authority) to reset their PINs. Hybrid customers can on-board their Azure tenant to use the Windows Hello for Business PIN reset service to reset their PINs without access to their corporate network.
+ For on-premises deployments, devices must be well-connected to their on-premises network (domain controllers and/or certificate authority) to reset their PINs. Hybrid customers can on-board their Azure tenant to use the Windows Hello for Business PIN reset service to reset their PINs. Non-destructive PIN reset works without access to corporate network. Destructive PIN reset requires access to corporate network. More details about destructive and non-destructive PIN reset can be found [here](https://docs.microsoft.com/en-us/windows/security/identity-protection/hello-for-business/hello-feature-pin-reset).
- question: What URLs do I need to allow for a hybrid deployment?
answer: |
From 6b861b7d7dc6855f8b2d91d185d1685760207799 Mon Sep 17 00:00:00 2001
From: VLG17 <41186174+VLG17@users.noreply.github.com>
Date: Thu, 6 Jan 2022 11:35:22 +0200
Subject: [PATCH 002/415] Update
windows/security/identity-protection/hello-for-business/hello-faq.yml
Co-authored-by: JohanFreelancer9 <48568725+JohanFreelancer9@users.noreply.github.com>
---
.../identity-protection/hello-for-business/hello-faq.yml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/windows/security/identity-protection/hello-for-business/hello-faq.yml b/windows/security/identity-protection/hello-for-business/hello-faq.yml
index b033cf57b3..b4dc152193 100644
--- a/windows/security/identity-protection/hello-for-business/hello-faq.yml
+++ b/windows/security/identity-protection/hello-for-business/hello-faq.yml
@@ -100,7 +100,7 @@ sections:
[Windows Hello for Business forgotten PIN user experience](hello-videos.md#windows-hello-for-business-forgotten-pin-user-experience)
- For on-premises deployments, devices must be well-connected to their on-premises network (domain controllers and/or certificate authority) to reset their PINs. Hybrid customers can on-board their Azure tenant to use the Windows Hello for Business PIN reset service to reset their PINs. Non-destructive PIN reset works without access to corporate network. Destructive PIN reset requires access to corporate network. More details about destructive and non-destructive PIN reset can be found [here](https://docs.microsoft.com/en-us/windows/security/identity-protection/hello-for-business/hello-feature-pin-reset).
+ For on-premises deployments, devices must be well-connected to their on-premises network (domain controllers and/or certificate authority) to reset their PINs. Hybrid customers can onboard their Azure tenant to use the Windows Hello for Business PIN reset service to reset their PINs. Non-destructive PIN reset works without access to the corporate network. Destructive PIN reset requires access to the corporate network. For more details about destructive and non-destructive PIN reset, see [PIN reset](/windows/security/identity-protection/hello-for-business/hello-feature-pin-reset).
- question: What URLs do I need to allow for a hybrid deployment?
answer: |
From 237bd91ea6d78183a706fc2bebfe7065f5db381a Mon Sep 17 00:00:00 2001
From: Adam Shapiro <45466550+adamoboe@users.noreply.github.com>
Date: Tue, 11 Jan 2022 18:28:29 -0800
Subject: [PATCH 003/415] Update virus-initiative-criteria.md
updated the list of third party test providers
---
.../threat-protection/intelligence/virus-initiative-criteria.md | 2 --
1 file changed, 2 deletions(-)
diff --git a/windows/security/threat-protection/intelligence/virus-initiative-criteria.md b/windows/security/threat-protection/intelligence/virus-initiative-criteria.md
index 0441e00ed4..272227666c 100644
--- a/windows/security/threat-protection/intelligence/virus-initiative-criteria.md
+++ b/windows/security/threat-protection/intelligence/virus-initiative-criteria.md
@@ -45,9 +45,7 @@ Test Provider | Lab Test Type | Minimum Level / Score
AV-Comparatives | Real-World Protection Test https://www.av-comparatives.org/testmethod/real-world-protection-tests/ |“Approved” rating from AV Comparatives
AV-Test | Must pass tests for Windows. Certifications for Mac and Linux aren't accepted https://www.av-test.org/en/about-the-institute/certification/ | Achieve "AV-TEST Certified" (for home users) or "AV-TEST Approved” (for corporate users)
ICSA Labs | Endpoint Anti-Malware Detection https://www.icsalabs.com/technology-program/anti-virus/criteria |PASS/Certified
-NSS Labs | Advanced Endpoint Protection AEP 3.0, which covers automatic threat prevention and threat event reporting capabilities https://www.nsslabs.com/tested-technologies/advanced-endpoint-protection/ |“Neutral” rating from NSS
SKD Labs | Certification Requirements Product: Anti-virus or Antimalware http://www.skdlabs.com/html/english/ http://www.skdlabs.com/cert/ |SKD Labs Star Check Certification Requirements Pass >= 98.5% with On Demand, On Access and Total Detection tests
-SE Labs | Protection A rating or Small Business EP A rating or Enterprise EP Protection A rating https://selabs.uk/en/reports/consumers |Home or Enterprise “A” rating
VB 100 | VB100 Certification Test V1.1 https://www.virusbulletin.com/testing/vb100/vb100-methodology/vb100-methodology-ver1-1/ | VB100 Certification
West Coast Labs | Checkmark Certified http://www.checkmarkcertified.com/sme/ | “A” Rating on Product Security Performance
From 274c2c840d5793b8a806f4a606d91f072ef0563f Mon Sep 17 00:00:00 2001
From: Ben Watt <13239035+wattbt@users.noreply.github.com>
Date: Thu, 13 Jan 2022 12:27:22 +0000
Subject: [PATCH 004/415] Minor rewording for clarity
Some minor rewording to make it clearer about how to turn off Config Lock, what the last section before the FAQ is about, and to better explain why the Firmware protection image is there.
Also took the opportunity to improve the image descriptions.
---
windows/client-management/mdm/config-lock.md | 16 ++++++++--------
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/windows/client-management/mdm/config-lock.md b/windows/client-management/mdm/config-lock.md
index f1bee95c6a..a13a98d8b4 100644
--- a/windows/client-management/mdm/config-lock.md
+++ b/windows/client-management/mdm/config-lock.md
@@ -48,31 +48,31 @@ The steps to turn on Config Lock using Microsoft Endpoint Manager (Microsoft Int
- **Profile type**: Templates
- **Template name**: Custom
- :::image type="content" source="images/configlock-mem-createprofile.png" alt-text="create profile":::
+ :::image type="content" source="images/configlock-mem-createprofile.png" alt-text="In Configuration profiles, the Create a profile page is showing, with the Platform set to Windows 10 and later, and a Profile Type of Templates":::
1. Name your profile.
1. When you reach the Configuration Settings step, select “Add” and add the following information:
- **OMA-URI**: ./Vendor/MSFT/DMClient/Provider/MS%20DM%20Server/ConfigLock/Lock
- **Data type**: Integer
- **Value**: 1
- To turn off Config Lock. Change value to 0.
+ To turn off Config Lock, change the value to 0.
- :::image type="content" source="images/configlock-mem-editrow.png" alt-text="edit row":::
+ :::image type="content" source="images/configlock-mem-editrow.png" alt-text="In the Configuration settings step, the Edit Row page is shown with a Name of Config Lock, a Description of Turn on Config Lock and the OMA-URI set as above, along with a Data type of Integer set to a Value of 1":::
1. Select the devices to turn on Config Lock. If you're using a test tenant, you can select “+ Add all devices”.
1. You'll not need to set any applicability rules for test purposes.
1. Review the Configuration and select “Create” if everything is correct.
1. After the device syncs with the Microsoft Intune server, you can confirm if the Config Lock was successfully enabled.
- :::image type="content" source="images/configlock-mem-dev.png" alt-text="status":::
+ :::image type="content" source="images/configlock-mem-dev.png" alt-text="The Profile assignment status dashboard when viewing the Config Lock device configuration profile, showing one device has succeeded in having this profile applied":::
- :::image type="content" source="images/configlock-mem-devstatus.png" alt-text="device status":::
+ :::image type="content" source="images/configlock-mem-devstatus.png" alt-text="The Device Status for the Config Lock Device Configuration Profile, showing one device with a Deployment Status as Succeeded and two with Pending":::
-## Disabling
+## Configuring Secured-Core PC features
-Config Lock is designed to ensure that a Secured-Core PC isn't unintentionally misconfigured. IT Admins retain the ability to change (enabled/disable) SCPC features via Group Policies and/or mobile device management (MDM) tools, such as Microsoft Intune.
+Config Lock is designed to ensure that a Secured-Core PC isn't unintentionally misconfigured. IT Admins retain the ability to change (enable/disable) SCPC features (for example Firmware protection) via Group Policies and/or mobile device management (MDM) tools, such as Microsoft Intune.
-:::image type="content" source="images/configlock-mem-firmwareprotect.png" alt-text="firmware protect":::
+:::image type="content" source="images/configlock-mem-firmwareprotect.png" alt-text="The Defender Firmware protection setting, with a description of Windows Defender System Guard protects your device from compromised firmware. The setting is set to Off":::
## FAQ
From 6e75aeb09189a4c679e6787d260e9514e87885c9 Mon Sep 17 00:00:00 2001
From: Shesh <56231259+sheshachary@users.noreply.github.com>
Date: Tue, 25 Jan 2022 19:49:04 +0530
Subject: [PATCH 005/415] sheshachary-5714481
---
windows/client-management/manage-corporate-devices.md | 6 ------
...age-windows-10-in-your-organization-modern-management.md | 2 +-
windows/client-management/mdm/alljoynmanagement-csp.md | 2 +-
.../mdm/azure-active-directory-integration-with-mdm.md | 3 ++-
.../mdm/change-history-for-mdm-documentation.md | 2 +-
windows/client-management/mdm/enterprise-app-management.md | 2 +-
.../mdm/mdm-enrollment-of-windows-devices.md | 2 +-
.../mdm/new-in-windows-mdm-enrollment-management.md | 2 +-
windows/client-management/mdm/oma-dm-protocol-support.md | 4 ++--
windows/client-management/mdm/passportforwork-csp.md | 2 +-
10 files changed, 11 insertions(+), 16 deletions(-)
diff --git a/windows/client-management/manage-corporate-devices.md b/windows/client-management/manage-corporate-devices.md
index f953bdeb3d..fb532ca4b1 100644
--- a/windows/client-management/manage-corporate-devices.md
+++ b/windows/client-management/manage-corporate-devices.md
@@ -49,14 +49,8 @@ You can use the same management tools to manage all device types running Windows
[Azure AD Join on Windows 10 (and Windows 11) devices](https://go.microsoft.com/fwlink/p/?LinkId=616791)
-[Azure AD support for Windows 10 (and Windows 11)](https://go.microsoft.com/fwlink/p/?LinkID=615765)
-
[Windows 10 (and Windows 11) and Azure Active Directory: Embracing the Cloud](https://go.microsoft.com/fwlink/p/?LinkId=615768)
-[How to manage Windows 10 (and Windows 11) devices using Intune](https://go.microsoft.com/fwlink/p/?LinkId=613620)
-
-[Using Intune alone and with Configuration Manager](https://go.microsoft.com/fwlink/p/?LinkId=613207)
-
Microsoft Virtual Academy course: [System Center 2012 R2 Configuration Manager & Windows Intune](/learn/)
diff --git a/windows/client-management/manage-windows-10-in-your-organization-modern-management.md b/windows/client-management/manage-windows-10-in-your-organization-modern-management.md
index 0e9dd8a789..55882ecb16 100644
--- a/windows/client-management/manage-windows-10-in-your-organization-modern-management.md
+++ b/windows/client-management/manage-windows-10-in-your-organization-modern-management.md
@@ -135,6 +135,6 @@ There are a variety of steps you can take to begin the process of modernizing de
## Related topics
-- [What is Intune?](//mem/intune/fundamentals/what-is-intune)
+- [What is Intune?](/mem/intune/fundamentals/what-is-intune)
- [Windows 10 Policy CSP](./mdm/policy-configuration-service-provider.md)
- [Windows 10 Configuration service Providers](./mdm/configuration-service-provider-reference.md)
diff --git a/windows/client-management/mdm/alljoynmanagement-csp.md b/windows/client-management/mdm/alljoynmanagement-csp.md
index 26bcc2dda6..b2a25f79cf 100644
--- a/windows/client-management/mdm/alljoynmanagement-csp.md
+++ b/windows/client-management/mdm/alljoynmanagement-csp.md
@@ -24,7 +24,7 @@ This CSP was added in Windows 10, version 1511.
-For the firewall settings, note that PublicProfile and PrivateProfile are mutually exclusive. The Private Profile must be set on the directly on the device itself, and the only supported operation is Get. For PublicProfile, both Add and Get are supported. This CSP is intended to be used in conjunction with the AllJoyn Device System Bridge, and an understanding of the bridge will help when determining when and how to use this CSP. For more information, see [Device System Bridge (DSB) Project](https://go.microsoft.com/fwlink/p/?LinkId=615876) and [AllJoyn Device System Bridge](https://go.microsoft.com/fwlink/p/?LinkId=615877).
+For the firewall settings, note that PublicProfile and PrivateProfile are mutually exclusive. The Private Profile must be set on the directly on the device itself, and the only supported operation is Get. For PublicProfile, both Add and Get are supported. This CSP is intended to be used in conjunction with the AllJoyn Device System Bridge, and an understanding of the bridge will help when determining when and how to use this CSP. For more information, see [AllJoyn – Wikipedia](https://wikipedia.org/wiki/AllJoyn).
The following shows the AllJoynManagement configuration service provider in tree format
diff --git a/windows/client-management/mdm/azure-active-directory-integration-with-mdm.md b/windows/client-management/mdm/azure-active-directory-integration-with-mdm.md
index 634025c4b9..e1c7c75a0f 100644
--- a/windows/client-management/mdm/azure-active-directory-integration-with-mdm.md
+++ b/windows/client-management/mdm/azure-active-directory-integration-with-mdm.md
@@ -379,9 +379,10 @@ Additional claims may be present in the Azure AD token, such as:
Access tokens issued by Azure AD are JSON web tokens (JWTs). A valid JWT token is presented by Windows at the MDM enrollment endpoint to start the enrollment process. There are a couple of options to evaluate the tokens:
-- Use the JWT Token Handler extension for WIF to validate the contents of the access token and extract claims required for use. For more information, see [JSON Web Token Handler](/previous-versions/dotnet/framework/security/json-web-token-handler).
+- Use the JWT Token Handler extension for WIF to validate the contents of the access token and extract claims required for use. For more information, see [JwtSecurityTokenHandler Class](/dotnet/api/system.identitymodel.tokens.jwt.jwtsecuritytokenhandler).
- Refer to the Azure AD authentication code samples to get a sample for working with access tokens. For an example, see [NativeClient-DotNet](https://go.microsoft.com/fwlink/p/?LinkId=613667).
+
## Device Alert 1224 for Azure AD user token
An alert is sent when the DM session starts and there's an Azure AD user logged in. The alert is sent in OMA DM pkg\#1. Here's an example:
diff --git a/windows/client-management/mdm/change-history-for-mdm-documentation.md b/windows/client-management/mdm/change-history-for-mdm-documentation.md
index 089b3868fd..7c7a59ddea 100644
--- a/windows/client-management/mdm/change-history-for-mdm-documentation.md
+++ b/windows/client-management/mdm/change-history-for-mdm-documentation.md
@@ -225,7 +225,7 @@ This article lists new and updated articles for the Mobile Device Management (MD
|New or updated article|Description|
|--- |--- |
|[WindowsDefenderApplicationGuard CSP](windowsdefenderapplicationguard-csp.md)|Added the following node in Windows 10, version 1803:
Settings/AllowVirtualGPUSettings/SaveFilesToHost|
-|[NetworkProxy CSP](\networkproxy--csp.md)|Added the following node in Windows 10, version 1803:ProxySettingsPerUser|
+|[NetworkProxy CSP](networkproxy-csp.md)|Added the following node in Windows 10, version 1803:ProxySettingsPerUser|
|[Accounts CSP](accounts-csp.md)|Added a new CSP in Windows 10, version 1803.|
|[MDM Migration Analysis Tool (MMAT)](https://aka.ms/mmat)|Updated version available. MMAT is a tool you can use to determine which Group Policies are set on a target user/computer and cross-reference them against the list of supported MDM policies.|
|[CSP DDF files download](configuration-service-provider-reference.md#csp-ddf-files-download)|Added the DDF download of Windows 10, version 1803 configuration service providers.|
diff --git a/windows/client-management/mdm/enterprise-app-management.md b/windows/client-management/mdm/enterprise-app-management.md
index 9397684167..ddd6fe4dd5 100644
--- a/windows/client-management/mdm/enterprise-app-management.md
+++ b/windows/client-management/mdm/enterprise-app-management.md
@@ -400,7 +400,7 @@ If you purchased an app from the Store for Business and the app is specified for
Here are the requirements for this scenario:
-- The location of the app can be a local files system (C:\\StagedApps\\app1.appx), a UNC path (\\\\server\\share\\app1.apx), or an HTTPS location (https://contoso.com/app1.appx\_
+- The location of the app can be a local files system (C:\\StagedApps\\app1.appx), a UNC path (\\\\server\\share\\app1.apx), or an HTTPS location (`https://contoso.com/app1.appx`).
- The user must have permission to access the content location. For HTTPs, you can use server authentication or certificate authentication using a certificate associated with the enrollment. HTTP locations are supported, but not recommended because of lack of authentication requirements.
- The device doesn't need to have connectivity to the Microsoft Store, store services, or have the Microsoft Store UI be enabled.
- The user must be logged in, but association with Azure AD identity isn't required.
diff --git a/windows/client-management/mdm/mdm-enrollment-of-windows-devices.md b/windows/client-management/mdm/mdm-enrollment-of-windows-devices.md
index e475077509..96508d3fa6 100644
--- a/windows/client-management/mdm/mdm-enrollment-of-windows-devices.md
+++ b/windows/client-management/mdm/mdm-enrollment-of-windows-devices.md
@@ -291,7 +291,7 @@ The deep link used for connecting your device to work will always use the follow
> [!NOTE]
> Deep links only work with Internet Explorer or Microsoft Edge browsers. When connecting to MDM using a deep link, the URI you should use is:
> **ms-device-enrollment:?mode=mdm**
-> **ms-device-enrollment:?mode=mdm&username=someone@example.com&servername=**
+> **ms-device-enrollment:?mode=mdm&username=someone@example.com&servername=<`https://example.server.com`>**
To connect your devices to MDM using deep links:
diff --git a/windows/client-management/mdm/new-in-windows-mdm-enrollment-management.md b/windows/client-management/mdm/new-in-windows-mdm-enrollment-management.md
index a982810497..305070c1af 100644
--- a/windows/client-management/mdm/new-in-windows-mdm-enrollment-management.md
+++ b/windows/client-management/mdm/new-in-windows-mdm-enrollment-management.md
@@ -270,7 +270,7 @@ The DM agent for [push-button reset](/windows-hardware/manufacture/desktop/push-
No. Only one MDM is allowed.
### How do I set the maximum number of Azure Active Directory joined devices per user?
-1. Login to the portal as tenant admin: https://manage.windowsazure.com.
+1. Login to the portal as tenant admin: https://portal.azure.com.
2. Click Active Directory on the left pane.
3. Choose your tenant.
4. Click **Configure**.
diff --git a/windows/client-management/mdm/oma-dm-protocol-support.md b/windows/client-management/mdm/oma-dm-protocol-support.md
index 8249c0eca9..1fdbc0a4dd 100644
--- a/windows/client-management/mdm/oma-dm-protocol-support.md
+++ b/windows/client-management/mdm/oma-dm-protocol-support.md
@@ -29,8 +29,8 @@ The following table shows the OMA DM standards that Windows uses.
|OMA DM standard objects|DevInfoDevDetailOMA DM DMS account objects (OMA DM version 1.2)|
|Security|Authenticate DM server initiation notification SMS message (not used by enterprise management)Application layer Basic and MD5 client authenticationAuthenticate server with MD5 credential at application levelData integrity and authentication with HMAC at application levelSSL level certificate-based client/server authentication, encryption, and data integrity check|
|Nodes|In the OMA DM tree, the following rules apply for the node name:
"." can be part of the node name.The node name cannot be empty.The node name cannot be only the asterisk (*) character.|
-|Provisioning Files|Provisioning XML must be well formed and follow the definition in SyncML Representation Protocol](https://go.microsoft.com/fwlink/p/?LinkId=526905).
If an XML element that is not a valid OMA DM command is under SyncBody, the status code 400 is returned for that element.**Note**
To represent a Unicode string as a URI, first encode the string as UTF-8. Then encode each of the UTF-8 bytes using URI encoding.
|
-|WBXML support|Windows supports sending and receiving SyncML in both XML format and encoded WBXML format. This is configurable by using the DEFAULTENCODING node under the w7 APPLICATION characteristic during enrollment. For more information about WBXML encoding, see section 8 of the [SyncML Representation Protocol](https://go.microsoft.com/fwlink/p/?LinkId=526905) specification.|
+|Provisioning Files|Provisioning XML must be well formed and follow the definition in [SyncML Representation Protocol](https://www.openmobilealliance.org/release/Common/V1_2_2-20090724-A/OMA-TS-SyncML-RepPro-V1_2_2-20090724-A.pdf).
If an XML element that is not a valid OMA DM command is under SyncBody, the status code 400 is returned for that element.**Note**
To represent a Unicode string as a URI, first encode the string as UTF-8. Then encode each of the UTF-8 bytes using URI encoding.
|
+|WBXML support|Windows supports sending and receiving SyncML in both XML format and encoded WBXML format. This is configurable by using the DEFAULTENCODING node under the w7 APPLICATION characteristic during enrollment. For more information about WBXML encoding, see section 8 of the [SyncML Representation Protocol](https://www.openmobilealliance.org/release/Common/V1_2_2-20090724-A/OMA-TS-SyncML-RepPro-V1_2_2-20090724-A.pdf) specification.|
|Handling of large objects|In Windows 10, version 1511, client support for uploading large objects to the server was added.|
diff --git a/windows/client-management/mdm/passportforwork-csp.md b/windows/client-management/mdm/passportforwork-csp.md
index 68bd28dd1e..5506461678 100644
--- a/windows/client-management/mdm/passportforwork-csp.md
+++ b/windows/client-management/mdm/passportforwork-csp.md
@@ -88,7 +88,7 @@ PassportForWork
Root node for PassportForWork configuration service provider.
***TenantId***
-A globally unique identifier (GUID), without curly braces ( { , } ), that is used as part of Windows Hello for Business provisioning and management. To get a GUID, use the PowerShell cmdlet [Get-AzureAccount](/powershell/module/servicemanagement/azure/get-azureaccount). For more information see [Get Windows Azure Active Directory Tenant ID in Windows PowerShell](https://devblogs.microsoft.com/scripting/get-windows-azure-active-directory-tenant-id-in-windows-powershell).
+A globally unique identifier (GUID), without curly braces ( { , } ), that is used as part of Windows Hello for Business provisioning and management. To get a GUID, use the PowerShell cmdlet [Get-AzureAccount](/powershell/module/servicemanagement/azure.service/get-azureaccount). For more information see [Get Windows Azure Active Directory Tenant ID in Windows PowerShell](https://devblogs.microsoft.com/scripting/get-windows-azure-active-directory-tenant-id-in-windows-powershell).
***TenantId*/Policies**
Node for defining the Windows Hello for Business policy settings.
From 533cf1d70244bc853ba3fe6e368c5ef678034bc5 Mon Sep 17 00:00:00 2001
From: Shesh <56231259+sheshachary@users.noreply.github.com>
Date: Tue, 1 Feb 2022 18:05:13 +0530
Subject: [PATCH 006/415] Updated the changes for the broken links
---
.../enterprise-mode-schema-version-1-guidance.md | 2 +-
.../enterprise-mode-schema-version-2-guidance.md | 2 +-
windows/client-management/mdm/alljoynmanagement-csp.md | 2 +-
.../client-management/mdm/policies-in-policy-csp-admx-backed.md | 2 +-
4 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/browsers/internet-explorer/ie11-deploy-guide/enterprise-mode-schema-version-1-guidance.md b/browsers/internet-explorer/ie11-deploy-guide/enterprise-mode-schema-version-1-guidance.md
index 8ee8fbf055..b3d946c53c 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/enterprise-mode-schema-version-1-guidance.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/enterprise-mode-schema-version-1-guidance.md
@@ -35,7 +35,7 @@ If you don't want to use the Enterprise Mode Site List Manager, you also have th
The following is an example of the Enterprise Mode schema v.1. This schema can run on devices running Windows 7 and Windows 8.1.
> [!IMPORTANT]
-> Make sure that you don't specify a protocol when adding your URLs. Using a URL like `contoso.com` automatically applies to both http://contoso.com and https://contoso.com.
+> Make sure that you don't specify a protocol when adding your URLs. Using a URL like `contoso.com` automatically applies to both `http://contoso.com` and `https://contoso.com`.
```xml
diff --git a/browsers/internet-explorer/ie11-deploy-guide/enterprise-mode-schema-version-2-guidance.md b/browsers/internet-explorer/ie11-deploy-guide/enterprise-mode-schema-version-2-guidance.md
index 825646b237..d35dd497b1 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/enterprise-mode-schema-version-2-guidance.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/enterprise-mode-schema-version-2-guidance.md
@@ -109,7 +109,7 @@ The <url> attribute, as part of the <site> element in the v.2 versio
|Attribute|Description|Supported browser|
|---------|---------|---------|
-|allow-redirect|A boolean attribute of the <open-in> element that controls the behavior for redirected sites. Setting this attribute to "true" indicates that the site will open in IE11 or Microsoft Edge even if the site is navigated to as part of a HTTP or meta refresh redirection chain. Omitting the attribute is equivalent to "false" (sites in redirect chain will not open in another browser).
**Example**<site url="contoso.com/travel">
<open-in allow-redirect="true">IE11 </open-in>
</site>
In this example, if [https://contoso.com/travel](https://contoso.com/travel) is encountered in a redirect chain in Microsoft Edge, it will be opened in Internet Explorer. | Internet Explorer 11 and Microsoft Edge|
+|allow-redirect|A boolean attribute of the <open-in> element that controls the behavior for redirected sites. Setting this attribute to "true" indicates that the site will open in IE11 or Microsoft Edge even if the site is navigated to as part of a HTTP or meta refresh redirection chain. Omitting the attribute is equivalent to "false" (sites in redirect chain will not open in another browser).
**Example**<site url="contoso.com/travel">
<open-in allow-redirect="true">IE11 </open-in>
</site>
In this example, if `https://contoso.com/travel` is encountered in a redirect chain in Microsoft Edge, it will be opened in Internet Explorer. | Internet Explorer 11 and Microsoft Edge|
|version |Specifies the version of the Enterprise Mode Site List. This attribute is supported for the <site-list> element. | Internet Explorer 11 and Microsoft Edge|
|url|Specifies the URL (and port number using standard port conventions) to which the child elements apply. The URL can be a domain, sub-domain, or any path URL.
**Note**
Make sure that you don't specify a protocol. Using <site url="contoso.com"> applies to both [https://contoso.com](https://contoso.com) and [https://contoso.com](https://contoso.com).
**Example**<site url="contoso.com:8080">
<compat-mode>IE8Enterprise</compat-mode>
<open-in>IE11</open-in>
</site>
In this example, going to [https://contoso.com:8080](https://contoso.com:8080) using Microsoft Edge, causes the site to open in IE11 and load in IE8 Enterprise Mode. | Internet Explorer 11 and Microsoft Edge|
diff --git a/windows/client-management/mdm/alljoynmanagement-csp.md b/windows/client-management/mdm/alljoynmanagement-csp.md
index b2a25f79cf..6e986105de 100644
--- a/windows/client-management/mdm/alljoynmanagement-csp.md
+++ b/windows/client-management/mdm/alljoynmanagement-csp.md
@@ -24,7 +24,7 @@ This CSP was added in Windows 10, version 1511.
-For the firewall settings, note that PublicProfile and PrivateProfile are mutually exclusive. The Private Profile must be set on the directly on the device itself, and the only supported operation is Get. For PublicProfile, both Add and Get are supported. This CSP is intended to be used in conjunction with the AllJoyn Device System Bridge, and an understanding of the bridge will help when determining when and how to use this CSP. For more information, see [AllJoyn – Wikipedia](https://wikipedia.org/wiki/AllJoyn).
+For the firewall settings, note that PublicProfile and PrivateProfile are mutually exclusive. The Private Profile must be set on the directly on the device itself, and the only supported operation is Get. For PublicProfile, both Add and Get are supported. This CSP is intended to be used in conjunction with the AllJoyn Device System Bridge, and an understanding of the bridge will help when determining when and how to use this CSP. For more information, see [Device System Bridge (DSB)](https://wikipedia.org/wiki/AllJoyn). For more information, see [AllJoyn Device System Bridge](https://wikipedia.org/wiki/AllJoyn).
The following shows the AllJoynManagement configuration service provider in tree format
diff --git a/windows/client-management/mdm/policies-in-policy-csp-admx-backed.md b/windows/client-management/mdm/policies-in-policy-csp-admx-backed.md
index 40aa9ba5d3..cb1c4ed088 100644
--- a/windows/client-management/mdm/policies-in-policy-csp-admx-backed.md
+++ b/windows/client-management/mdm/policies-in-policy-csp-admx-backed.md
@@ -980,7 +980,7 @@ ms.date: 10/08/2020
- [ADMX_sdiageng/ScriptedDiagnosticsExecutionPolicy](./policy-csp-admx-sdiageng.md#admx-sdiageng-scripteddiagnosticsexecutionpolicy)
- [ADMX_sdiageng/ScriptedDiagnosticsSecurityPolicy](./policy-csp-admx-sdiageng.md#admx-sdiageng-scripteddiagnosticssecuritypolicy)
- [ADMX_sdiagschd/ScheduledDiagnosticsExecutionPolicy](./policy-csp-admx-sdiagschd.md#admx-sdiagschd-scheduleddiagnosticsexecutionpolicy)
-- [ADMX_Securitycenter/SecurityCenter_SecurityCenterInDomain](/policy-csp-admx-securitycenter.md#admx-securitycenter-securitycenter-securitycenterindomain)
+- [ADMX_Securitycenter/SecurityCenter_SecurityCenterInDomain](./policy-csp-admx-securitycenter.md#admx-securitycenter-securitycenter-securitycenterindomain)
- [ADMX_Sensors/DisableLocationScripting_1](./policy-csp-admx-sensors.md#admx-sensors-disablelocationscripting-1)
- [ADMX_Sensors/DisableLocationScripting_2](./policy-csp-admx-sensors.md#admx-sensors-disablelocationscripting-2)
- [ADMX_Sensors/DisableLocation_1](./policy-csp-admx-sensors.md#admx-sensors-disablelocation-1)
From 50793c318e0848d68e47041591ac0abbe23ea02d Mon Sep 17 00:00:00 2001
From: Shesh <56231259+sheshachary@users.noreply.github.com>
Date: Tue, 1 Feb 2022 18:41:20 +0530
Subject: [PATCH 007/415] updated the changes
---
.../mdm/new-in-windows-mdm-enrollment-management.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/windows/client-management/mdm/new-in-windows-mdm-enrollment-management.md b/windows/client-management/mdm/new-in-windows-mdm-enrollment-management.md
index 305070c1af..ca53db2988 100644
--- a/windows/client-management/mdm/new-in-windows-mdm-enrollment-management.md
+++ b/windows/client-management/mdm/new-in-windows-mdm-enrollment-management.md
@@ -33,9 +33,9 @@ For details about Microsoft mobile device management protocols for Windows 10 a
## Breaking changes and known issues
-### Get command inside an atomic command is not supported
+### Get command inside an atomic command isn’t supported
-In Windows 10 and Windows 11, a Get command inside an atomic command is not supported.
+In Windows 10 and Windows 11, a Get command inside an atomic command isn't supported.
### Apps installed using WMI classes are not removed
From 4f66822a2f59db87b26aee9de0de419c618d4dc2 Mon Sep 17 00:00:00 2001
From: Shesh <56231259+sheshachary@users.noreply.github.com>
Date: Tue, 1 Feb 2022 18:53:33 +0530
Subject: [PATCH 008/415] updated the changes
---
.../client-management/mdm/oma-dm-protocol-support.md | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/windows/client-management/mdm/oma-dm-protocol-support.md b/windows/client-management/mdm/oma-dm-protocol-support.md
index 1fdbc0a4dd..5195faa1a4 100644
--- a/windows/client-management/mdm/oma-dm-protocol-support.md
+++ b/windows/client-management/mdm/oma-dm-protocol-support.md
@@ -25,11 +25,11 @@ The following table shows the OMA DM standards that Windows uses.
|--- |--- |
|Data transport and session|Client-initiated remote HTTPS DM session over SSL.Remote HTTPS DM session over SSL.Remote DM server initiation notification using WAP Push over Short Message Service (SMS). Not used by enterprise management.Remote bootstrap by using WAP Push over SMS. Not used by enterprise management.|
|Bootstrap XML|OMA Client Provisioning XML.|
-|DM protocol commands|The following list shows the commands that are used by the device. For more information about the OMA DM command elements, see "[OMA website](https://www.openmobilealliance.org/release/DM/V1_1_2-20031209-A/)" available from the OMA website.
Add (Implicit Add supported)Alert (DM alert): Generic alert (1226) is used by enterprise management client when the user triggers an MDM unenrollment action from the device or when a CSP finishes some asynchronous actions. Device alert (1224) is used to notify the server some device triggered event.Atomic: Performing an Add command followed by Replace on the same node within an atomic element is not supported. Nested Atomic and Get commands are not allowed and will generate error code 500.Delete: Removes a node from the DM tree, and the entire subtree beneath that node if one existsExec: Invokes an executable on the client deviceGet: Retrieves data from the client device; for interior nodes, the child node names in the Data element are returned in URI-encoded formatReplace: Overwrites data on the client deviceResult: Returns the data results of a Get command to the DM serverSequence: Specifies the order in which a group of commands must be processedStatus: Indicates the completion status (success or failure) of an operation
If an XML element that is not a valid OMA DM command is under one of the following elements, the status code 400 is returned for that element:
SyncBodyAtomicSequence
If no CmdID is provided in the DM command, the client returns blank in the status element and the status code 400.
If Atomic elements are nested, the following status codes are returned:
The nested Atomic command returns 500.The parent Atomic command returns 507.
For more information about the Atomic command, see OMA DM protocol common elements.
Performing an Add command followed by Replace on the same node within an Atomic element is not supported.
LocURI cannot start with `/`.
Meta XML tag in SyncHdr is ignored by the device.|
+|DM protocol commands|The following list shows the commands that are used by the device. For more information about the OMA DM command elements, see "[OMA website](https://www.openmobilealliance.org/release/DM/V1_1_2-20031209-A/)" available from the OMA website.
Add (Implicit Add supported)Alert (DM alert): Generic alert (1226) is used by enterprise management client when the user triggers an MDM unenrollment action from the device or when a CSP finishes some asynchronous actions. Device alert (1224) is used to notify the server some device triggered event.Atomic: Performing an Add command followed by Replace on the same node within an atomic element isn't supported. Nested Atomic and Get commands aren't allowed and will generate error code 500.Delete: Removes a node from the DM tree, and the entire subtree beneath that node if one existsExec: Invokes an executable on the client deviceGet: Retrieves data from the client device; for interior nodes, the child node names in the Data element are returned in URI-encoded formatReplace: Overwrites data on the client deviceResult: Returns the data results of a Get command to the DM serverSequence: Specifies the order in which a group of commands must be processedStatus: Indicates the completion status (success or failure) of an operation
If an XML element that isn't a valid OMA DM command is under one of the following elements, the status code 400 is returned for that element:
SyncBodyAtomicSequence
If no CmdID is provided in the DM command, the client returns blank in the status element and the status code 400.
If Atomic elements are nested, the following status codes are returned:
The nested Atomic command returns 500.The parent Atomic command returns 507.
For more information about the Atomic command, see OMA DM protocol common elements.
Performing an Add command followed by Replace on the same node within an Atomic element isn't supported.
LocURI can't start with `/`.
Meta XML tag in SyncHdr is ignored by the device.|
|OMA DM standard objects|DevInfoDevDetailOMA DM DMS account objects (OMA DM version 1.2)|
|Security|Authenticate DM server initiation notification SMS message (not used by enterprise management)Application layer Basic and MD5 client authenticationAuthenticate server with MD5 credential at application levelData integrity and authentication with HMAC at application levelSSL level certificate-based client/server authentication, encryption, and data integrity check|
|Nodes|In the OMA DM tree, the following rules apply for the node name:
"." can be part of the node name.The node name cannot be empty.The node name cannot be only the asterisk (*) character.|
-|Provisioning Files|Provisioning XML must be well formed and follow the definition in [SyncML Representation Protocol](https://www.openmobilealliance.org/release/Common/V1_2_2-20090724-A/OMA-TS-SyncML-RepPro-V1_2_2-20090724-A.pdf).
If an XML element that is not a valid OMA DM command is under SyncBody, the status code 400 is returned for that element.**Note**
To represent a Unicode string as a URI, first encode the string as UTF-8. Then encode each of the UTF-8 bytes using URI encoding.
|
+|Provisioning Files|Provisioning XML must be well formed and follow the definition in [SyncML Representation Protocol](https://www.openmobilealliance.org/release/Common/V1_2_2-20090724-A/OMA-TS-SyncML-RepPro-V1_2_2-20090724-A.pdf).
If an XML element that isn't a valid OMA DM command is under SyncBody, the status code 400 is returned for that element.**Note**
To represent a Unicode string as a URI, first encode the string as UTF-8. Then encode each of the UTF-8 bytes using URI encoding.
|
|WBXML support|Windows supports sending and receiving SyncML in both XML format and encoded WBXML format. This is configurable by using the DEFAULTENCODING node under the w7 APPLICATION characteristic during enrollment. For more information about WBXML encoding, see section 8 of the [SyncML Representation Protocol](https://www.openmobilealliance.org/release/Common/V1_2_2-20090724-A/OMA-TS-SyncML-RepPro-V1_2_2-20090724-A.pdf) specification.|
|Handling of large objects|In Windows 10, version 1511, client support for uploading large objects to the server was added.|
@@ -52,7 +52,7 @@ Common elements are used by other OMA DM element types. The following table list
|MsgID|Specifies a unique identifier for an OMA DM session message.|
|MsgRef|Specifies the ID of the corresponding request message. This element takes the value of the request message MsgID element.|
|RespURI|Specifies the URI that the recipient must use when sending a response to this message.|
-|SessionID|Specifies the identifier of the OMA DM session associated with the containing message.**Note**
If the server does not notify the device that it supports a new version (through SyncApplicationVersion node in the DMClient CSP), the client returns the SessionID in integer in decimal format. If the server supports DM session sync version 2.0, which is used in Windows 10, the device client returns 2 bytes.
|
+|SessionID|Specifies the identifier of the OMA DM session associated with the containing message.**Note**
If the server doesn't notify the device that it supports a new version (through SyncApplicationVersion node in the DMClient CSP), the client returns the SessionID in integer in decimal format. If the server supports DM session sync version 2.0, which is used in Windows 10, the device client returns 2 bytes.
|
|Source|Specifies the message source address.|
|SourceRef|Specifies the source of the corresponding request message. This element takes the value of the request message Source element and is returned in the Status or Results element.|
|Target|Specifies the address of the node, in the DM Tree, that is the target of the OMA DM command.|
@@ -125,7 +125,7 @@ Below is an alert example:
```
-The server notifies the device whether it is a user targeted or device targeted configuration by a prefix to the management node’s LocURL, with ./user for user targeted configuration, or ./device for device targeted configuration. By default, if no prefix with ./device or ./user, it is device targeted configuration.
+The server notifies the device whether it's a user targeted or device targeted configuration by a prefix to the management node’s LocURL, with ./user for user targeted configuration, or ./device for device targeted configuration. By default, if no prefix with ./device or ./user, it's device targeted configuration.
The following LocURL shows a per user CSP node configuration: **./user/vendor/MSFT/EnterpriseModernAppManagement/AppInstallation/<PackageFamilyName>/StoreInstall**
@@ -135,7 +135,7 @@ The following LocURL shows a per device CSP node configuration: **./device/vendo
## SyncML response status codes
-When using SyncML in OMA DM, there are standard response status codes that are returned. The following table lists the common SyncML response status codes you are likely to see. For more information about SyncML response status codes, see section 10 of the [SyncML Representation Protocol](https://openmobilealliance.org/release/Common/V1_2_2-20090724-A/OMA-TS-SyncML-RepPro-V1_2_2-20090724-A.pdf) specification.
+When using SyncML in OMA DM, there are standard response status codes that are returned. The following table lists the common SyncML response status codes you're likely to see. For more information about SyncML response status codes, see section 10 of the [SyncML Representation Protocol](https://openmobilealliance.org/release/Common/V1_2_2-20090724-A/OMA-TS-SyncML-RepPro-V1_2_2-20090724-A.pdf) specification.
| Status code | Description |
|---|----|
From a7014ba160a6c67f8bc329960a9e2ff41e7a3ef8 Mon Sep 17 00:00:00 2001
From: Shesh <56231259+sheshachary@users.noreply.github.com>
Date: Wed, 2 Feb 2022 12:01:13 +0530
Subject: [PATCH 009/415] updated the changes
---
windows/client-management/mdm/oma-dm-protocol-support.md | 6 +++---
windows/client-management/mdm/passportforwork-csp.md | 6 +++---
2 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/windows/client-management/mdm/oma-dm-protocol-support.md b/windows/client-management/mdm/oma-dm-protocol-support.md
index 5195faa1a4..0533507105 100644
--- a/windows/client-management/mdm/oma-dm-protocol-support.md
+++ b/windows/client-management/mdm/oma-dm-protocol-support.md
@@ -28,7 +28,7 @@ The following table shows the OMA DM standards that Windows uses.
|DM protocol commands|The following list shows the commands that are used by the device. For more information about the OMA DM command elements, see "[OMA website](https://www.openmobilealliance.org/release/DM/V1_1_2-20031209-A/)" available from the OMA website.
Add (Implicit Add supported)Alert (DM alert): Generic alert (1226) is used by enterprise management client when the user triggers an MDM unenrollment action from the device or when a CSP finishes some asynchronous actions. Device alert (1224) is used to notify the server some device triggered event.Atomic: Performing an Add command followed by Replace on the same node within an atomic element isn't supported. Nested Atomic and Get commands aren't allowed and will generate error code 500.Delete: Removes a node from the DM tree, and the entire subtree beneath that node if one existsExec: Invokes an executable on the client deviceGet: Retrieves data from the client device; for interior nodes, the child node names in the Data element are returned in URI-encoded formatReplace: Overwrites data on the client deviceResult: Returns the data results of a Get command to the DM serverSequence: Specifies the order in which a group of commands must be processedStatus: Indicates the completion status (success or failure) of an operation
If an XML element that isn't a valid OMA DM command is under one of the following elements, the status code 400 is returned for that element:
SyncBodyAtomicSequence
If no CmdID is provided in the DM command, the client returns blank in the status element and the status code 400.
If Atomic elements are nested, the following status codes are returned:
The nested Atomic command returns 500.The parent Atomic command returns 507.
For more information about the Atomic command, see OMA DM protocol common elements.
Performing an Add command followed by Replace on the same node within an Atomic element isn't supported.
LocURI can't start with `/`.
Meta XML tag in SyncHdr is ignored by the device.|
|OMA DM standard objects|DevInfoDevDetailOMA DM DMS account objects (OMA DM version 1.2)|
|Security|Authenticate DM server initiation notification SMS message (not used by enterprise management)Application layer Basic and MD5 client authenticationAuthenticate server with MD5 credential at application levelData integrity and authentication with HMAC at application levelSSL level certificate-based client/server authentication, encryption, and data integrity check|
-|Nodes|In the OMA DM tree, the following rules apply for the node name:
"." can be part of the node name.The node name cannot be empty.The node name cannot be only the asterisk (*) character.|
+|Nodes|In the OMA DM tree, the following rules apply for the node name:
"." can be part of the node name.The node name can't be empty.The node name can’t be only the asterisk (*) character.|
|Provisioning Files|Provisioning XML must be well formed and follow the definition in [SyncML Representation Protocol](https://www.openmobilealliance.org/release/Common/V1_2_2-20090724-A/OMA-TS-SyncML-RepPro-V1_2_2-20090724-A.pdf).
If an XML element that isn't a valid OMA DM command is under SyncBody, the status code 400 is returned for that element.**Note**
To represent a Unicode string as a URI, first encode the string as UTF-8. Then encode each of the UTF-8 bytes using URI encoding.
|
|WBXML support|Windows supports sending and receiving SyncML in both XML format and encoded WBXML format. This is configurable by using the DEFAULTENCODING node under the w7 APPLICATION characteristic during enrollment. For more information about WBXML encoding, see section 8 of the [SyncML Representation Protocol](https://www.openmobilealliance.org/release/Common/V1_2_2-20090724-A/OMA-TS-SyncML-RepPro-V1_2_2-20090724-A.pdf) specification.|
|Handling of large objects|In Windows 10, version 1511, client support for uploading large objects to the server was added.|
@@ -106,7 +106,7 @@ For CSPs and policies that support per user configuration, the MDM server can se
The data part of this alert could be one of following strings:
- User – the user that enrolled the device is actively logged in. The MDM server could send user-specific configuration for CSPs/policies that support per user configuration
-- Others – another user login but that user does not have an MDM account. The server can only apply device-wide configuration, for example, configuration applies to all users in the device.
+- Others – another user login but that user doesn't have an MDM account. The server can only apply device-wide configuration, for example, configuration applies to all users in the device.
- None – no active user login. The server can only apply device-wide configuration and available configuration is restricted to the device environment (no active user login).
Below is an alert example:
@@ -141,7 +141,7 @@ When using SyncML in OMA DM, there are standard response status codes that are r
|---|----|
| 200 | The SyncML command completed successfully. |
| 202 | Accepted for processing. This is usually an asynchronous operation, such as a request to run a remote execution of an application. |
-| 212 | Authentication accepted. Normally you'll only see this in response to the SyncHdr element (used for authentication in the OMA-DM standard). You may see this if you look at OMA DM logs, but CSPs do not typically generate this. |
+| 212 | Authentication accepted. Normally you'll only see this in response to the SyncHdr element (used for authentication in the OMA-DM standard). You may see this if you look at OMA DM logs, but CSPs don't typically generate this. |
| 214 | Operation canceled. The SyncML command completed successfully, but no more commands will be processed within the session. |
| 215 | Not executed. A command was not executed as a result of user interaction to cancel the command. |
| 216 | `Atomic` roll back OK. A command was inside an `Atomic` element and `Atomic` failed. This command was rolled back successfully. |
diff --git a/windows/client-management/mdm/passportforwork-csp.md b/windows/client-management/mdm/passportforwork-csp.md
index 5506461678..4155f26107 100644
--- a/windows/client-management/mdm/passportforwork-csp.md
+++ b/windows/client-management/mdm/passportforwork-csp.md
@@ -88,7 +88,7 @@ PassportForWork
Root node for PassportForWork configuration service provider.
***TenantId***
-A globally unique identifier (GUID), without curly braces ( { , } ), that is used as part of Windows Hello for Business provisioning and management. To get a GUID, use the PowerShell cmdlet [Get-AzureAccount](/powershell/module/servicemanagement/azure.service/get-azureaccount). For more information see [Get Windows Azure Active Directory Tenant ID in Windows PowerShell](https://devblogs.microsoft.com/scripting/get-windows-azure-active-directory-tenant-id-in-windows-powershell).
+A globally unique identifier (GUID), without curly braces ( { , } ), that is used as part of Windows Hello for Business provisioning and management. To get a GUID, use the PowerShell cmdlet [Get-AzureAccount](/powershell/module/servicemanagement/azure.service/get-azureaccount). For more information, see [Get Windows Azure Active Directory Tenant ID in Windows PowerShell](https://devblogs.microsoft.com/scripting/get-windows-azure-active-directory-tenant-id-in-windows-powershell).
***TenantId*/Policies**
Node for defining the Windows Hello for Business policy settings.
@@ -103,7 +103,7 @@ Supported operations are Add, Get, Delete, and Replace.
***TenantId*/Policies/RequireSecurityDevice**
Boolean value that requires a Trusted Platform Module (TPM) for Windows Hello for Business. TPM provides an additional security benefit over software so that data stored in it cannot be used on other devices.
-Default value is false. If you set this policy to true, only devices with a usable TPM can provision Windows Hello for Business. If you set this policy to false, all devices can provision Windows Hello for Business using software even if there is not a usable TPM. If you do not configure this setting, all devices can provision Windows Hello for Business using software if the TPM is non-functional or unavailable.
+Default value is false. If you set this policy to true, only devices with a usable TPM can provision Windows Hello for Business. If you set this policy to false, all devices can provision Windows Hello for Business using software even if there isn't a usable TPM. If you don’t configure this setting, all devices can provision Windows Hello for Business using software if the TPM is non-functional or unavailable.
Supported operations are Add, Get, Delete, and Replace.
@@ -126,7 +126,7 @@ This cloud service encrypts a recovery secret, which is stored locally on the cl
Default value is false. If you enable this policy setting, the PIN recovery secret will be stored on the device and the user can change their PIN if needed.
-If you disable or do not configure this policy setting, the PIN recovery secret will not be created or stored. If the user's PIN is forgotten, the only way to get a new PIN is by deleting the existing PIN and creating a new one, which will require the user to re-register with any services the old PIN provided access to.
+If you disable or don't configure this policy setting, the PIN recovery secret won't be created or stored. If the user's PIN is forgotten, the only way to get a new PIN is by deleting the existing PIN and creating a new one, which will require the user to re-register with any services the old PIN provided access to.
Supported operations are Add, Get, Delete, and Replace.
From eadacf89e824bc2664ee90534479b1dc7c720b7a Mon Sep 17 00:00:00 2001
From: greg-lindsay
Date: Thu, 3 Feb 2022 15:45:36 -0800
Subject: [PATCH 010/415] template
---
windows/deployment/do/TOC.yml | 579 ++++++++++++++++++++++++++++++++
windows/deployment/do/index.yml | 104 ++++++
2 files changed, 683 insertions(+)
create mode 100644 windows/deployment/do/TOC.yml
create mode 100644 windows/deployment/do/index.yml
diff --git a/windows/deployment/do/TOC.yml b/windows/deployment/do/TOC.yml
new file mode 100644
index 0000000000..6eb965d5b3
--- /dev/null
+++ b/windows/deployment/do/TOC.yml
@@ -0,0 +1,579 @@
+- name: Deploy and update Windows client
+ href: index.yml
+ items:
+ - name: Get started
+ items:
+ - name: What's new
+ href: deploy-whats-new.md
+ - name: Windows client deployment scenarios
+ href: windows-10-deployment-scenarios.md
+ - name: What is Windows as a service?
+ href: update/waas-quick-start.md
+ - name: Windows update fundamentals
+ href: update/waas-overview.md
+ - name: Monthly quality updates
+ href: update/quality-updates.md
+ - name: Basics of Windows updates, channels, and tools
+ href: update/get-started-updates-channels-tools.md
+ - name: Prepare servicing strategy for Windows client updates
+ href: update/waas-servicing-strategy-windows-10-updates.md
+ - name: Deployment proof of concept
+ items:
+ - name: Demonstrate Autopilot deployment on a VM
+ href: windows-autopilot/demonstrate-deployment-on-vm.md
+ - name: Deploy Windows 10 with MDT and Configuration Manager
+ items:
+ - name: 'Step by step guide: Configure a test lab to deploy Windows 10'
+ href: windows-10-poc.md
+ - name: Deploy Windows 10 in a test lab using MDT
+ href: windows-10-poc-mdt.md
+ - name: Deploy Windows 10 in a test lab using Configuration Manager
+ href: windows-10-poc-sc-config-mgr.md
+ - name: Deployment process posters
+ href: windows-10-deployment-posters.md
+
+ - name: Plan
+ items:
+ - name: Plan for Windows 11
+ href: /windows/whats-new/windows-11-plan
+ - name: Create a deployment plan
+ href: update/create-deployment-plan.md
+ - name: Define readiness criteria
+ href: update/plan-define-readiness.md
+ - name: Evaluate infrastructure and tools
+ href: update/eval-infra-tools.md
+ - name: Determine application readiness
+ href: update/plan-determine-app-readiness.md
+ - name: Define your servicing strategy
+ href: update/plan-define-strategy.md
+ - name: Delivery Optimization for Windows client updates
+ href: update/waas-delivery-optimization.md
+ items:
+ - name: Using a proxy with Delivery Optimization
+ href: update/delivery-optimization-proxy.md
+ - name: Delivery Optimization client-service communication
+ href: update/delivery-optimization-workflow.md
+ - name: Windows 10 deployment considerations
+ href: planning/windows-10-deployment-considerations.md
+ - name: Windows 10 infrastructure requirements
+ href: planning/windows-10-infrastructure-requirements.md
+ - name: Plan for volume activation
+ href: volume-activation/plan-for-volume-activation-client.md
+ - name: Features removed or planned for replacement
+ items:
+ - name: Windows client features lifecycle
+ href: planning/features-lifecycle.md
+ - name: Features we're no longer developing
+ items:
+ - name: Windows 10 deprecated features
+ href: planning/windows-10-deprecated-features.md
+ - name: Features we removed
+ items:
+ - name: Windows 10 features removed
+ href: planning/windows-10-removed-features.md
+
+ - name: Prepare
+ items:
+ - name: Prepare for Windows 11
+ href: /windows/whats-new/windows-11-prepare
+ - name: Prepare to deploy Windows client updates
+ href: update/prepare-deploy-windows.md
+ - name: Evaluate and update infrastructure
+ href: update/update-policies.md
+ - name: Update Baseline
+ href: update/update-baseline.md
+ - name: Set up Delivery Optimization for Windows client updates
+ href: update/waas-delivery-optimization-setup.md
+ - name: Configure BranchCache for Windows client updates
+ href: update/waas-branchcache.md
+ - name: Prepare your deployment tools
+ items:
+ - name: Prepare for deployment with MDT
+ href: deploy-windows-mdt/prepare-for-windows-deployment-with-mdt.md
+ - name: Prepare for deployment with Configuration Manager
+ href: deploy-windows-cm/prepare-for-zero-touch-installation-of-windows-10-with-configuration-manager.md
+ - name: Build a successful servicing strategy
+ items:
+ - name: Check release health
+ href: update/check-release-health.md
+ - name: Prepare updates using Windows Update for Business
+ href: update/waas-manage-updates-wufb.md
+ - name: Prepare updates using WSUS
+ href: update/waas-manage-updates-wsus.md
+
+ - name: Deploy
+ items:
+ - name: Deploy Windows client
+ items:
+ - name: Deploy Windows client with Autopilot
+ href: windows-autopilot/index.yml
+ - name: Deploy Windows client with Configuration Manager
+ items:
+ - name: Deploy to a new device
+ href: deploy-windows-cm/deploy-windows-10-using-pxe-and-configuration-manager.md
+ - name: Refresh a device
+ href: deploy-windows-cm/refresh-a-windows-7-client-with-windows-10-using-configuration-manager.md
+ - name: Replace a device
+ href: deploy-windows-cm/replace-a-windows-7-client-with-windows-10-using-configuration-manager.md
+ - name: In-place upgrade
+ href: deploy-windows-cm/upgrade-to-windows-10-with-configuration-manager.md
+ - name: Deploy Windows client with MDT
+ items:
+ - name: Deploy to a new device
+ href: deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md
+ - name: Refresh a device
+ href: deploy-windows-mdt/refresh-a-windows-7-computer-with-windows-10.md
+ - name: Replace a device
+ href: deploy-windows-mdt/replace-a-windows-7-computer-with-a-windows-10-computer.md
+ - name: In-place upgrade
+ href: deploy-windows-mdt/upgrade-to-windows-10-with-the-microsoft-deployment-toolkit.md
+ - name: Subscription Activation
+ items:
+ - name: Windows 10/11 Subscription Activation
+ href: windows-10-subscription-activation.md
+ - name: Windows 10/11 Enterprise E3 in CSP
+ href: windows-10-enterprise-e3-overview.md
+ - name: Configure VDA for Subscription Activation
+ href: vda-subscription-activation.md
+ - name: Deploy Windows 10/11 Enterprise licenses
+ href: deploy-enterprise-licenses.md
+ - name: Deploy Windows client updates
+ items:
+ - name: Assign devices to servicing channels
+ href: update/waas-servicing-channels-windows-10-updates.md
+ - name: Deploy updates with Configuration Manager
+ href: update/deploy-updates-configmgr.md
+ - name: Deploy updates with Intune
+ href: update/deploy-updates-intune.md
+ - name: Deploy updates with WSUS
+ href: update/waas-manage-updates-wsus.md
+ - name: Deploy updates with Group Policy
+ href: update/waas-wufb-group-policy.md
+ - name: Update Windows client media with Dynamic Update
+ href: update/media-dynamic-update.md
+ - name: Migrating and acquiring optional Windows content
+ href: update/optional-content.md
+ - name: Safeguard holds
+ href: update/safeguard-holds.md
+ - name: Manage the Windows client update experience
+ items:
+ - name: Manage device restarts after updates
+ href: update/waas-restart.md
+ - name: Manage additional Windows Update settings
+ href: update/waas-wu-settings.md
+ - name: Use Windows Update for Business
+ items:
+ - name: What is Windows Update for Business?
+ href: update/waas-manage-updates-wufb.md
+ - name: Configure Windows Update for Business
+ href: update/waas-configure-wufb.md
+ - name: Use Windows Update for Business and WSUS
+ href: update/wufb-wsus.md
+ - name: Windows Update for Business deployment service
+ href: update/deployment-service-overview.md
+ items:
+ - name: Troubleshoot the Windows Update for Business deployment service
+ href: update/deployment-service-troubleshoot.md
+ - name: Enforcing compliance deadlines for updates
+ href: update/wufb-compliancedeadlines.md
+ - name: Integrate Windows Update for Business with management solutions
+ href: update/waas-integrate-wufb.md
+ - name: 'Walkthrough: use Group Policy to configure Windows Update for Business'
+ href: update/waas-wufb-group-policy.md
+ - name: 'Walkthrough: use Intune to configure Windows Update for Business'
+ href: update/deploy-updates-intune.md
+ - name: Monitor Windows client updates
+ items:
+ - name: Monitor Delivery Optimization
+ href: update/waas-delivery-optimization-setup.md#monitor-delivery-optimization
+ - name: Monitor Windows Updates
+ items:
+ - name: Monitor Windows Updates with Update Compliance
+ href: update/update-compliance-monitor.md
+ - name: Get started
+ items:
+ - name: Get started with Update Compliance
+ href: update/update-compliance-get-started.md
+ - name: Update Compliance configuration script
+ href: update/update-compliance-configuration-script.md
+ - name: Manually configuring devices for Update Compliance
+ href: update/update-compliance-configuration-manual.md
+ - name: Configuring devices for Update Compliance in Microsoft Endpoint Manager
+ href: update/update-compliance-configuration-mem.md
+ - name: Update Compliance monitoring
+ items:
+ - name: Use Update Compliance
+ href: update/update-compliance-using.md
+ - name: Need attention report
+ href: update/update-compliance-need-attention.md
+ - name: Security update status report
+ href: update/update-compliance-security-update-status.md
+ - name: Feature update status report
+ href: update/update-compliance-feature-update-status.md
+ - name: Safeguard holds report
+ href: update/update-compliance-safeguard-holds.md
+ - name: Delivery Optimization in Update Compliance
+ href: update/update-compliance-delivery-optimization.md
+ - name: Data handling and privacy in Update Compliance
+ href: update/update-compliance-privacy.md
+ - name: Update Compliance schema reference
+ href: update/update-compliance-schema.md
+ items:
+ - name: WaaSUpdateStatus
+ href: update/update-compliance-schema-waasupdatestatus.md
+ - name: WaaSInsiderStatus
+ href: update/update-compliance-schema-waasinsiderstatus.md
+ - name: WaaSDepoymentStatus
+ href: update/update-compliance-schema-waasdeploymentstatus.md
+ - name: WUDOStatus
+ href: update/update-compliance-schema-wudostatus.md
+ - name: WUDOAggregatedStatus
+ href: update/update-compliance-schema-wudoaggregatedstatus.md
+ - name: Troubleshooting
+ items:
+ - name: Resolve upgrade errors
+ items:
+ - name: Resolve Windows client upgrade errors
+ href: upgrade/resolve-windows-10-upgrade-errors.md
+ - name: Quick fixes
+ href: upgrade/quick-fixes.md
+ - name: SetupDiag
+ href: upgrade/setupdiag.md
+ - name: Troubleshooting upgrade errors
+ href: upgrade/troubleshoot-upgrade-errors.md
+ - name: Windows error reporting
+ href: upgrade/windows-error-reporting.md
+ - name: Upgrade error codes
+ href: upgrade/upgrade-error-codes.md
+ - name: Log files
+ href: upgrade/log-files.md
+ - name: Resolution procedures
+ href: upgrade/resolution-procedures.md
+ - name: Submit Windows client upgrade errors
+ href: upgrade/submit-errors.md
+ - name: Troubleshoot Windows Update
+ items:
+ - name: How to troubleshoot Windows Update
+ href: update/windows-update-troubleshooting.md
+ - name: Opt out of safeguard holds
+ href: update/safeguard-opt-out.md
+ - name: Determine the source of Windows Updates
+ href: ./update/how-windows-update-works.md
+ - name: Common Windows Update errors
+ href: update/windows-update-errors.md
+ - name: Windows Update error code reference
+ href: update/windows-update-error-reference.md
+ - name: Troubleshoot the Windows Update for Business deployment service
+ href: update/deployment-service-troubleshoot.md
+
+ - name: Reference
+ items:
+ - name: How does Windows Update work?
+ href: update/how-windows-update-works.md
+ - name: Windows client upgrade paths
+ href: upgrade/windows-10-upgrade-paths.md
+ - name: Windows client edition upgrade
+ href: upgrade/windows-10-edition-upgrades.md
+ - name: Deploy Windows 10 with Microsoft 365
+ href: deploy-m365.md
+ - name: Understand the Unified Update Platform
+ href: update/windows-update-overview.md
+ - name: Servicing stack updates
+ href: update/servicing-stack-updates.md
+ - name: Additional Windows Update settings
+ href: update/waas-wu-settings.md
+ - name: Delivery Optimization reference
+ href: update/waas-delivery-optimization-reference.md
+ - name: Windows client in S mode
+ href: s-mode.md
+ - name: Switch to Windows client Pro or Enterprise from S mode
+ href: windows-10-pro-in-s-mode.md
+ - name: Windows client deployment tools
+ items:
+ - name: Windows client deployment scenarios and tools
+ items:
+ - name: Windows Deployment Services (WDS) boot.wim support
+ href: wds-boot-support.md
+ - name: Convert MBR partition to GPT
+ href: mbr-to-gpt.md
+ - name: Configure a PXE server to load Windows PE
+ href: configure-a-pxe-server-to-load-windows-pe.md
+ - name: Windows ADK for Windows 10 scenarios for IT Pros
+ href: windows-adk-scenarios-for-it-pros.md
+ - name: Windows To Go
+ items:
+ - name: Deploy Windows To Go in your organization
+ href: deploy-windows-to-go.md
+ - name: "Windows To Go: feature overview"
+ href: planning/windows-to-go-overview.md
+ - name: Best practice recommendations for Windows To Go
+ href: planning/best-practice-recommendations-for-windows-to-go.md
+ - name: Deployment considerations for Windows To Go
+ href: planning/deployment-considerations-for-windows-to-go.md
+ - name: Prepare your organization for Windows To Go
+ href: planning/prepare-your-organization-for-windows-to-go.md
+ - name: Security and data protection considerations for Windows To Go
+ href: planning/security-and-data-protection-considerations-for-windows-to-go.md
+ - name: "Windows To Go: frequently asked questions"
+ href: planning/windows-to-go-frequently-asked-questions.yml
+
+ - name: Volume Activation Management Tool (VAMT) technical reference
+ items:
+ - name: VAMT technical reference
+ href: volume-activation/volume-activation-management-tool.md
+ - name: Introduction to VAMT
+ href: volume-activation/introduction-vamt.md
+ - name: Active Directory-Based Activation Overview
+ href: volume-activation/active-directory-based-activation-overview.md
+ - name: Install and Configure VAMT
+ items:
+ - name: Overview
+ href: volume-activation/install-configure-vamt.md
+ - name: VAMT Requirements
+ href: volume-activation/vamt-requirements.md
+ - name: Install VAMT
+ href: volume-activation/install-vamt.md
+ - name: Configure Client Computers
+ href: volume-activation/configure-client-computers-vamt.md
+ - name: Add and Manage Products
+ items:
+ - name: Overview
+ href: volume-activation/add-manage-products-vamt.md
+ - name: Add and Remove Computers
+ href: volume-activation/add-remove-computers-vamt.md
+ - name: Update Product Status
+ href: volume-activation/update-product-status-vamt.md
+ - name: Remove Products
+ href: volume-activation/remove-products-vamt.md
+ - name: Manage Product Keys
+ items:
+ - name: Overview
+ href: volume-activation/manage-product-keys-vamt.md
+ - name: Add and Remove a Product Key
+ href: volume-activation/add-remove-product-key-vamt.md
+ - name: Install a Product Key
+ href: volume-activation/install-product-key-vamt.md
+ - name: Install a KMS Client Key
+ href: volume-activation/install-kms-client-key-vamt.md
+ - name: Manage Activations
+ items:
+ - name: Overview
+ href: volume-activation/manage-activations-vamt.md
+ - name: Run Online Activation
+ href: volume-activation/online-activation-vamt.md
+ - name: Run Proxy Activation
+ href: volume-activation/proxy-activation-vamt.md
+ - name: Run KMS Activation
+ href: volume-activation/kms-activation-vamt.md
+ - name: Run Local Reactivation
+ href: volume-activation/local-reactivation-vamt.md
+ - name: Activate an Active Directory Forest Online
+ href: volume-activation/activate-forest-vamt.md
+ - name: Activate by Proxy an Active Directory Forest
+ href: volume-activation/activate-forest-by-proxy-vamt.md
+ - name: Manage VAMT Data
+ items:
+ - name: Overview
+ href: volume-activation/manage-vamt-data.md
+ - name: Import and Export VAMT Data
+ href: volume-activation/import-export-vamt-data.md
+ - name: Use VAMT in Windows PowerShell
+ href: volume-activation/use-vamt-in-windows-powershell.md
+ - name: VAMT Step-by-Step Scenarios
+ items:
+ - name: Overview
+ href: volume-activation/vamt-step-by-step.md
+ - name: "Scenario 1: Online Activation"
+ href: volume-activation/scenario-online-activation-vamt.md
+ - name: "Scenario 2: Proxy Activation"
+ href: volume-activation/scenario-proxy-activation-vamt.md
+ - name: "Scenario 3: KMS Client Activation"
+ href: volume-activation/scenario-kms-activation-vamt.md
+ - name: VAMT Known Issues
+ href: volume-activation/vamt-known-issues.md
+
+ - name: User State Migration Tool (USMT) technical reference
+ items:
+ - name: USMT overview topics
+ items:
+ - name: USMT overview
+ href: usmt/usmt-overview.md
+ - name: Getting started with the USMT
+ href: usmt/getting-started-with-the-user-state-migration-tool.md
+ - name: Windows upgrade and migration considerations
+ href: upgrade/windows-upgrade-and-migration-considerations.md
+ - name: USMT How-to topics
+ items:
+ - name: Exclude Files and Settings
+ href: usmt/usmt-exclude-files-and-settings.md
+ - name: Extract Files from a Compressed USMT Migration Store
+ href: usmt/usmt-extract-files-from-a-compressed-migration-store.md
+ - name: Include Files and Settings
+ href: usmt/usmt-include-files-and-settings.md
+ - name: Migrate Application Settings
+ href: usmt/migrate-application-settings.md
+ - name: Migrate EFS Files and Certificates
+ href: usmt/usmt-migrate-efs-files-and-certificates.md
+ - name: Migrate User Accounts
+ href: usmt/usmt-migrate-user-accounts.md
+ - name: Reroute Files and Settings
+ href: usmt/usmt-reroute-files-and-settings.md
+ - name: Verify the Condition of a Compressed Migration Store
+ href: usmt/verify-the-condition-of-a-compressed-migration-store.md
+ - name: USMT Troubleshooting
+ href: usmt/usmt-troubleshooting.md
+ - name: Common Issues
+ href: usmt/usmt-common-issues.md
+ - name: Frequently Asked Questions
+ href: usmt/usmt-faq.yml
+ - name: Log Files
+ href: usmt/usmt-log-files.md
+ - name: Return Codes
+ href: usmt/usmt-return-codes.md
+ - name: USMT Resources
+ href: usmt/usmt-resources.md
+
+ - name: USMT Reference
+ items:
+ - name: USMT Requirements
+ href: usmt/usmt-requirements.md
+ - name: USMT Best Practices
+ href: usmt/usmt-best-practices.md
+ - name: How USMT Works
+ href: usmt/usmt-how-it-works.md
+ - name: Plan Your Migration
+ href: usmt/usmt-plan-your-migration.md
+ - name: Common Migration Scenarios
+ href: usmt/usmt-common-migration-scenarios.md
+ - name: What Does USMT Migrate?
+ href: usmt/usmt-what-does-usmt-migrate.md
+ - name: Choose a Migration Store Type
+ href: usmt/usmt-choose-migration-store-type.md
+ - name: Migration Store Types Overview
+ href: usmt/migration-store-types-overview.md
+ - name: Estimate Migration Store Size
+ href: usmt/usmt-estimate-migration-store-size.md
+ - name: Hard-Link Migration Store
+ href: usmt/usmt-hard-link-migration-store.md
+ - name: Migration Store Encryption
+ href: usmt/usmt-migration-store-encryption.md
+ - name: Determine What to Migrate
+ href: usmt/usmt-determine-what-to-migrate.md
+ - name: Identify users
+ href: usmt/usmt-identify-users.md
+ - name: Identify Applications Settings
+ href: usmt/usmt-identify-application-settings.md
+ - name: Identify Operating System Settings
+ href: usmt/usmt-identify-operating-system-settings.md
+ - name: Identify File Types, Files, and Folders
+ href: usmt/usmt-identify-file-types-files-and-folders.md
+ - name: Test Your Migration
+ href: usmt/usmt-test-your-migration.md
+ - name: USMT Command-line Syntax
+ href: usmt/usmt-command-line-syntax.md
+ - name: ScanState Syntax
+ href: usmt/usmt-scanstate-syntax.md
+ - name: LoadState Syntax
+ href: usmt/usmt-loadstate-syntax.md
+ - name: UsmtUtils Syntax
+ href: usmt/usmt-utilities.md
+ - name: USMT XML Reference
+ href: usmt/usmt-xml-reference.md
+ - name: Understanding Migration XML Files
+ href: usmt/understanding-migration-xml-files.md
+ - name: Config.xml File
+ href: usmt/usmt-configxml-file.md
+ - name: Customize USMT XML Files
+ href: usmt/usmt-customize-xml-files.md
+ - name: Custom XML Examples
+ href: usmt/usmt-custom-xml-examples.md
+ - name: Conflicts and Precedence
+ href: usmt/usmt-conflicts-and-precedence.md
+ - name: General Conventions
+ href: usmt/usmt-general-conventions.md
+ - name: XML File Requirements
+ href: usmt/xml-file-requirements.md
+ - name: Recognized Environment Variables
+ href: usmt/usmt-recognized-environment-variables.md
+ - name: XML Elements Library
+ href: usmt/usmt-xml-elements-library.md
+ - name: Offline Migration Reference
+ href: usmt/offline-migration-reference.md
+
+ - name: Application Compatibility Toolkit (ACT) Technical Reference
+ items:
+ - name: SUA User's Guide
+ items:
+ - name: Overview
+ href: planning/sua-users-guide.md
+ - name: Use the SUA Wizard
+ href: planning/using-the-sua-wizard.md
+ - name: Use the SUA Tool
+ href: planning/using-the-sua-tool.md
+ - name: Tabs on the SUA Tool Interface
+ href: planning/tabs-on-the-sua-tool-interface.md
+ - name: Show Messages Generated by the SUA Tool
+ href: planning/showing-messages-generated-by-the-sua-tool.md
+ - name: Apply Filters to Data in the SUA Tool
+ href: planning/applying-filters-to-data-in-the-sua-tool.md
+ - name: Fix apps using the SUA Tool
+ href: planning/fixing-applications-by-using-the-sua-tool.md
+ - name: Compatibility Fixes for Windows 10, Windows 8, Windows 7, and Windows Vista
+ href: planning/compatibility-fixes-for-windows-8-windows-7-and-windows-vista.md
+ - name: Compatibility Administrator User's Guide
+ items:
+ - name: Overview
+ href: planning/compatibility-administrator-users-guide.md
+ - name: Use the Compatibility Administrator Tool
+ href: planning/using-the-compatibility-administrator-tool.md
+ - name: Available Data Types and Operators in Compatibility Administrator
+ href: planning/available-data-types-and-operators-in-compatibility-administrator.md
+ - name: Search for Fixed Applications in Compatibility Administrator
+ href: planning/searching-for-fixed-applications-in-compatibility-administrator.md
+ - name: Search for Installed Compatibility Fixes with the Query Tool in Compatibility Administrator
+ href: planning/searching-for-installed-compatibility-fixes-with-the-query-tool-in-compatibility-administrator.md
+ - name: Create a Custom Compatibility Fix in Compatibility Administrator
+ href: planning/creating-a-custom-compatibility-fix-in-compatibility-administrator.md
+ - name: Create a Custom Compatibility Mode in Compatibility Administrator
+ href: planning/creating-a-custom-compatibility-mode-in-compatibility-administrator.md
+ - name: Create an AppHelp Message in Compatibility Administrator
+ href: planning/creating-an-apphelp-message-in-compatibility-administrator.md
+ - name: View the Events Screen in Compatibility Administrator
+ href: planning/viewing-the-events-screen-in-compatibility-administrator.md
+ - name: Enable and Disable Compatibility Fixes in Compatibility Administrator
+ href: planning/enabling-and-disabling-compatibility-fixes-in-compatibility-administrator.md
+ - name: Install and Uninstall Custom Compatibility Databases in Compatibility Administrator
+ href: planning/installing-and-uninstalling-custom-compatibility-databases-in-compatibility-administrator.md
+ - name: Manage Application-Compatibility Fixes and Custom Fix Databases
+ items:
+ - name: Overview
+ href: planning/managing-application-compatibility-fixes-and-custom-fix-databases.md
+ - name: Understand and Use Compatibility Fixes
+ href: planning/understanding-and-using-compatibility-fixes.md
+ - name: Compatibility Fix Database Management Strategies and Deployment
+ href: planning/compatibility-fix-database-management-strategies-and-deployment.md
+ - name: Test Your Application Mitigation Packages
+ href: planning/testing-your-application-mitigation-packages.md
+ - name: Use the Sdbinst.exe Command-Line Tool
+ href: planning/using-the-sdbinstexe-command-line-tool.md
+ - name: Volume Activation
+ items:
+ - name: Overview
+ href: volume-activation/volume-activation-windows-10.md
+ - name: Plan for volume activation
+ href: volume-activation/plan-for-volume-activation-client.md
+ - name: Activate using Key Management Service
+ href: volume-activation/activate-using-key-management-service-vamt.md
+ - name: Activate using Active Directory-based activation
+ href: volume-activation/activate-using-active-directory-based-activation-client.md
+ - name: Activate clients running Windows 10
+ href: volume-activation/activate-windows-10-clients-vamt.md
+ - name: Monitor activation
+ href: volume-activation/monitor-activation-client.md
+ - name: Use the Volume Activation Management Tool
+ href: volume-activation/use-the-volume-activation-management-tool-client.md
+ - name: "Appendix: Information sent to Microsoft during activation "
+ href: volume-activation/appendix-information-sent-to-microsoft-during-activation-client.md
+
+ - name: Install fonts in Windows client
+ href: windows-10-missing-fonts.md
diff --git a/windows/deployment/do/index.yml b/windows/deployment/do/index.yml
new file mode 100644
index 0000000000..314d9aa780
--- /dev/null
+++ b/windows/deployment/do/index.yml
@@ -0,0 +1,104 @@
+### YamlMime:Landing
+
+title: Windows client deployment resources and documentation # < 60 chars
+summary: Learn about deploying and keeping Windows client devices up to date. # < 160 chars
+
+metadata:
+ title: Windows client deployment resources and documentation # Required; page title displayed in search results. Include the brand. < 60 chars.
+ description: Learn about deploying Windows 10 and keeping it up to date in your organization. # Required; article description that is displayed in search results. < 160 chars.
+ services: windows-10
+ ms.service: windows-10 #Required; service per approved list. service slug assigned to your service by ACOM.
+ ms.subservice: subservice
+ ms.topic: landing-page # Required
+ ms.collection:
+ - windows-10
+ - highpri
+ author: greg-lindsay #Required; your GitHub user alias, with correct capitalization.
+ ms.author: greglin #Required; microsoft alias of author; optional team alias.
+ ms.date: 06/24/2021 #Required; mm/dd/yyyy format.
+ localization_priority: medium
+
+# linkListType: architecture | concept | deploy | download | get-started | how-to-guide | learn | overview | quickstart | reference | tutorial | video | whats-new
+
+landingContent:
+# Cards and links should be based on top customer tasks or top subjects
+# Start card title with a verb
+ # Card (optional)
+ - title: Plan
+ linkLists:
+ - linkListType: overview
+ links:
+ - text: Create a deployment plan
+ url: update/create-deployment-plan.md
+ - text: Define readiness criteria
+ url: update/plan-define-readiness.md
+ - text: Evaluate infrastructure and tools
+ url: update/eval-infra-tools.md
+ - text: Define your servicing strategy
+ url: update/plan-define-strategy.md
+
+ # Card (optional)
+ - title: Prepare
+ linkLists:
+ - linkListType: how-to-guide
+ links:
+ - text: Prepare to deploy Windows updates
+ url: update/prepare-deploy-windows.md
+ - text: Prepare updates using Windows Update for Business
+ url: update/waas-manage-updates-wufb.md
+ - text: Prepare for Zero Touch Installation of Windows 10 with Configuration Manager
+ url: deploy-windows-cm/prepare-for-zero-touch-installation-of-windows-10-with-configuration-manager.md
+
+ # Card (optional)
+ - title: Deploy
+ linkLists:
+ - linkListType: deploy
+ links:
+ - text: Deploy Windows 10 with Autopilot
+ url: /mem/autopilot
+ - text: Assign devices to servicing channels
+ url: update/waas-servicing-channels-windows-10-updates.md
+ - text: Deploy Windows updates with Configuration Manager
+ url: update/deploy-updates-configmgr.md
+
+ # Card
+ - title: Overview
+ linkLists:
+ - linkListType: overview
+ links:
+ - text: What's new in Windows deployment
+ url: deploy-whats-new.md
+ - text: Windows 11 overview
+ url: /windows/whats-new/windows-11
+ - text: Windows client deployment scenarios
+ url: windows-10-deployment-scenarios.md
+ - text: Basics of Windows updates, channels, and tools
+ url: update/get-started-updates-channels-tools.md
+ - text: Overview of Windows Autopilot
+ url: /mem/autopilot/windows-autopilot
+
+ # Card
+ - title: Support remote work
+ linkLists:
+ - linkListType: concept
+ links:
+ - text: Deploy Windows 10 for a remote world
+ url: https://techcommunity.microsoft.com/t5/windows-it-pro-blog/deploying-a-new-version-of-windows-10-in-a-remote-world/ba-p/1419846
+ - text: Empower remote workers with Microsoft 365
+ url: /microsoft-365/solutions/empower-people-to-work-remotely
+ - text: Top 12 tasks for security teams to support working from home
+ url: /microsoft-365/security/top-security-tasks-for-remote-work
+ - text: Support your remote workforce
+ url: /microsoftteams/faq-support-remote-workforce
+
+ # Card (optional)
+ - title: Microsoft Learn
+ linkLists:
+ - linkListType: learn
+ links:
+ - text: Plan to deploy updates for Windows 10 and Microsoft 365 Apps
+ url: /learn/modules/windows-plan
+ - text: Prepare to deploy updates for Windows 10 and Microsoft 365 Apps
+ url: /learn/modules/windows-prepare/
+ - text: Deploy updates for Windows 10 and Microsoft 365 Apps
+ url: /learn/modules/windows-deploy
\ No newline at end of file
From 9559d3dda6365a8a93ed7bdbcc2a8f3b67b8475a Mon Sep 17 00:00:00 2001
From: greg-lindsay
Date: Fri, 4 Feb 2022 12:43:55 -0800
Subject: [PATCH 011/415] cards
---
windows/deployment/do/index.yml | 26 +++++++++++++-------------
1 file changed, 13 insertions(+), 13 deletions(-)
diff --git a/windows/deployment/do/index.yml b/windows/deployment/do/index.yml
index 314d9aa780..0495ecf400 100644
--- a/windows/deployment/do/index.yml
+++ b/windows/deployment/do/index.yml
@@ -1,11 +1,11 @@
### YamlMime:Landing
-title: Windows client deployment resources and documentation # < 60 chars
-summary: Learn about deploying and keeping Windows client devices up to date. # < 160 chars
+title: Delivery Optimization for Windows client # < 60 chars
+summary: Learn about using peer to peer downloads on Windows clients along with Microsoft Connected Cache. # < 160 chars
metadata:
- title: Windows client deployment resources and documentation # Required; page title displayed in search results. Include the brand. < 60 chars.
- description: Learn about deploying Windows 10 and keeping it up to date in your organization. # Required; article description that is displayed in search results. < 160 chars.
+ title: Delivery Optimization # Required; page title displayed in search results. Include the brand. < 60 chars.
+ description: Learn about using peer to peer downloads on Windows clients along with Microsoft Connected Cache. # Required; article description that is displayed in search results. < 160 chars.
services: windows-10
ms.service: windows-10 #Required; service per approved list. service slug assigned to your service by ACOM.
ms.subservice: subservice
@@ -15,7 +15,7 @@ metadata:
- highpri
author: greg-lindsay #Required; your GitHub user alias, with correct capitalization.
ms.author: greglin #Required; microsoft alias of author; optional team alias.
- ms.date: 06/24/2021 #Required; mm/dd/yyyy format.
+ ms.date: 02/04/2022 #Required; mm/dd/yyyy format.
localization_priority: medium
# linkListType: architecture | concept | deploy | download | get-started | how-to-guide | learn | overview | quickstart | reference | tutorial | video | whats-new
@@ -24,7 +24,7 @@ landingContent:
# Cards and links should be based on top customer tasks or top subjects
# Start card title with a verb
# Card (optional)
- - title: Plan
+ - title: Overview
linkLists:
- linkListType: overview
links:
@@ -38,7 +38,7 @@ landingContent:
url: update/plan-define-strategy.md
# Card (optional)
- - title: Prepare
+ - title: Configure Delivery Optimization on Windows clients
linkLists:
- linkListType: how-to-guide
links:
@@ -50,9 +50,9 @@ landingContent:
url: deploy-windows-cm/prepare-for-zero-touch-installation-of-windows-10-with-configuration-manager.md
# Card (optional)
- - title: Deploy
+ - title: Configure Delivery Optimization on Microsoft Endpoint Manager
linkLists:
- - linkListType: deploy
+ - linkListType: how-to-guide
links:
- text: Deploy Windows 10 with Autopilot
url: /mem/autopilot
@@ -62,9 +62,9 @@ landingContent:
url: update/deploy-updates-configmgr.md
# Card
- - title: Overview
+ - title: Microsoft Connected Cache for Enterprises (Private Preview)
linkLists:
- - linkListType: overview
+ - linkListType: concept
links:
- text: What's new in Windows deployment
url: deploy-whats-new.md
@@ -78,7 +78,7 @@ landingContent:
url: /mem/autopilot/windows-autopilot
# Card
- - title: Support remote work
+ - title: Microsoft Connected Cache for ISPs (Private Preview)
linkLists:
- linkListType: concept
links:
@@ -92,7 +92,7 @@ landingContent:
url: /microsoftteams/faq-support-remote-workforce
# Card (optional)
- - title: Microsoft Learn
+ - title: Resources
linkLists:
- linkListType: learn
links:
From eb3ac65cfe4d07ac3cc17edfbd3d929dd4b834ab Mon Sep 17 00:00:00 2001
From: greg-lindsay
Date: Fri, 4 Feb 2022 13:07:44 -0800
Subject: [PATCH 012/415] toc
---
windows/deployment/do/TOC.yml | 589 ++--------------------------------
1 file changed, 26 insertions(+), 563 deletions(-)
diff --git a/windows/deployment/do/TOC.yml b/windows/deployment/do/TOC.yml
index 6eb965d5b3..67d9a9faf9 100644
--- a/windows/deployment/do/TOC.yml
+++ b/windows/deployment/do/TOC.yml
@@ -1,579 +1,42 @@
-- name: Deploy and update Windows client
+- name: Delivery Optimization for Windows client
href: index.yml
items:
- name: Get started
items:
- - name: What's new
+ - name: What is Delivery Optimization?
href: deploy-whats-new.md
- - name: Windows client deployment scenarios
+ - name: What is Microsoft Connected Cache?
href: windows-10-deployment-scenarios.md
- - name: What is Windows as a service?
+ - name: What's new?
href: update/waas-quick-start.md
- - name: Windows update fundamentals
+ - name: 4
href: update/waas-overview.md
- - name: Monthly quality updates
- href: update/quality-updates.md
- - name: Basics of Windows updates, channels, and tools
- href: update/get-started-updates-channels-tools.md
- - name: Prepare servicing strategy for Windows client updates
- href: update/waas-servicing-strategy-windows-10-updates.md
- - name: Deployment proof of concept
- items:
- - name: Demonstrate Autopilot deployment on a VM
- href: windows-autopilot/demonstrate-deployment-on-vm.md
- - name: Deploy Windows 10 with MDT and Configuration Manager
- items:
- - name: 'Step by step guide: Configure a test lab to deploy Windows 10'
- href: windows-10-poc.md
- - name: Deploy Windows 10 in a test lab using MDT
- href: windows-10-poc-mdt.md
- - name: Deploy Windows 10 in a test lab using Configuration Manager
- href: windows-10-poc-sc-config-mgr.md
- - name: Deployment process posters
- href: windows-10-deployment-posters.md
-
- - name: Plan
+
+ - name: Configure Delivery Optimization
items:
- - name: Plan for Windows 11
- href: /windows/whats-new/windows-11-plan
- - name: Create a deployment plan
- href: update/create-deployment-plan.md
- - name: Define readiness criteria
- href: update/plan-define-readiness.md
- - name: Evaluate infrastructure and tools
- href: update/eval-infra-tools.md
- - name: Determine application readiness
- href: update/plan-determine-app-readiness.md
- - name: Define your servicing strategy
- href: update/plan-define-strategy.md
- - name: Delivery Optimization for Windows client updates
- href: update/waas-delivery-optimization.md
+ - name: Configure Windows Clients
items:
- - name: Using a proxy with Delivery Optimization
- href: update/delivery-optimization-proxy.md
- - name: Delivery Optimization client-service communication
- href: update/delivery-optimization-workflow.md
- - name: Windows 10 deployment considerations
- href: planning/windows-10-deployment-considerations.md
- - name: Windows 10 infrastructure requirements
- href: planning/windows-10-infrastructure-requirements.md
- - name: Plan for volume activation
- href: volume-activation/plan-for-volume-activation-client.md
- - name: Features removed or planned for replacement
+ - name: Windows Delivery Optimization settings
+ href: /windows/whats-new/windows-11-plan
+ - name: Configure Microsoft Endpoint Manager
items:
- - name: Windows client features lifecycle
- href: planning/features-lifecycle.md
- - name: Features we're no longer developing
- items:
- - name: Windows 10 deprecated features
- href: planning/windows-10-deprecated-features.md
- - name: Features we removed
- items:
- - name: Windows 10 features removed
- href: planning/windows-10-removed-features.md
-
- - name: Prepare
- items:
- - name: Prepare for Windows 11
- href: /windows/whats-new/windows-11-prepare
- - name: Prepare to deploy Windows client updates
- href: update/prepare-deploy-windows.md
- - name: Evaluate and update infrastructure
- href: update/update-policies.md
- - name: Update Baseline
- href: update/update-baseline.md
- - name: Set up Delivery Optimization for Windows client updates
- href: update/waas-delivery-optimization-setup.md
- - name: Configure BranchCache for Windows client updates
- href: update/waas-branchcache.md
- - name: Prepare your deployment tools
+ - name: Configuration Manager settings
+ href: /windows/whats-new/windows-11-plan
+
+ - name: Microsoft Connected Cache
+ items:
+ - name: Microsoft Connected Cache for Enterprises
items:
- - name: Prepare for deployment with MDT
- href: deploy-windows-mdt/prepare-for-windows-deployment-with-mdt.md
- - name: Prepare for deployment with Configuration Manager
- href: deploy-windows-cm/prepare-for-zero-touch-installation-of-windows-10-with-configuration-manager.md
- - name: Build a successful servicing strategy
+ - name: Windows Delivery Optimization settings
+ href: /windows/whats-new/windows-11-plan
+ - name: Microsoft Connected Cache for ISPs
items:
- - name: Check release health
- href: update/check-release-health.md
- - name: Prepare updates using Windows Update for Business
- href: update/waas-manage-updates-wufb.md
- - name: Prepare updates using WSUS
- href: update/waas-manage-updates-wsus.md
-
- - name: Deploy
- items:
- - name: Deploy Windows client
- items:
- - name: Deploy Windows client with Autopilot
- href: windows-autopilot/index.yml
- - name: Deploy Windows client with Configuration Manager
- items:
- - name: Deploy to a new device
- href: deploy-windows-cm/deploy-windows-10-using-pxe-and-configuration-manager.md
- - name: Refresh a device
- href: deploy-windows-cm/refresh-a-windows-7-client-with-windows-10-using-configuration-manager.md
- - name: Replace a device
- href: deploy-windows-cm/replace-a-windows-7-client-with-windows-10-using-configuration-manager.md
- - name: In-place upgrade
- href: deploy-windows-cm/upgrade-to-windows-10-with-configuration-manager.md
- - name: Deploy Windows client with MDT
- items:
- - name: Deploy to a new device
- href: deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md
- - name: Refresh a device
- href: deploy-windows-mdt/refresh-a-windows-7-computer-with-windows-10.md
- - name: Replace a device
- href: deploy-windows-mdt/replace-a-windows-7-computer-with-a-windows-10-computer.md
- - name: In-place upgrade
- href: deploy-windows-mdt/upgrade-to-windows-10-with-the-microsoft-deployment-toolkit.md
- - name: Subscription Activation
- items:
- - name: Windows 10/11 Subscription Activation
- href: windows-10-subscription-activation.md
- - name: Windows 10/11 Enterprise E3 in CSP
- href: windows-10-enterprise-e3-overview.md
- - name: Configure VDA for Subscription Activation
- href: vda-subscription-activation.md
- - name: Deploy Windows 10/11 Enterprise licenses
- href: deploy-enterprise-licenses.md
- - name: Deploy Windows client updates
- items:
- - name: Assign devices to servicing channels
- href: update/waas-servicing-channels-windows-10-updates.md
- - name: Deploy updates with Configuration Manager
- href: update/deploy-updates-configmgr.md
- - name: Deploy updates with Intune
- href: update/deploy-updates-intune.md
- - name: Deploy updates with WSUS
- href: update/waas-manage-updates-wsus.md
- - name: Deploy updates with Group Policy
- href: update/waas-wufb-group-policy.md
- - name: Update Windows client media with Dynamic Update
- href: update/media-dynamic-update.md
- - name: Migrating and acquiring optional Windows content
- href: update/optional-content.md
- - name: Safeguard holds
- href: update/safeguard-holds.md
- - name: Manage the Windows client update experience
- items:
- - name: Manage device restarts after updates
- href: update/waas-restart.md
- - name: Manage additional Windows Update settings
- href: update/waas-wu-settings.md
- - name: Use Windows Update for Business
- items:
- - name: What is Windows Update for Business?
- href: update/waas-manage-updates-wufb.md
- - name: Configure Windows Update for Business
- href: update/waas-configure-wufb.md
- - name: Use Windows Update for Business and WSUS
- href: update/wufb-wsus.md
- - name: Windows Update for Business deployment service
- href: update/deployment-service-overview.md
- items:
- - name: Troubleshoot the Windows Update for Business deployment service
- href: update/deployment-service-troubleshoot.md
- - name: Enforcing compliance deadlines for updates
- href: update/wufb-compliancedeadlines.md
- - name: Integrate Windows Update for Business with management solutions
- href: update/waas-integrate-wufb.md
- - name: 'Walkthrough: use Group Policy to configure Windows Update for Business'
- href: update/waas-wufb-group-policy.md
- - name: 'Walkthrough: use Intune to configure Windows Update for Business'
- href: update/deploy-updates-intune.md
- - name: Monitor Windows client updates
- items:
- - name: Monitor Delivery Optimization
- href: update/waas-delivery-optimization-setup.md#monitor-delivery-optimization
- - name: Monitor Windows Updates
- items:
- - name: Monitor Windows Updates with Update Compliance
- href: update/update-compliance-monitor.md
- - name: Get started
- items:
- - name: Get started with Update Compliance
- href: update/update-compliance-get-started.md
- - name: Update Compliance configuration script
- href: update/update-compliance-configuration-script.md
- - name: Manually configuring devices for Update Compliance
- href: update/update-compliance-configuration-manual.md
- - name: Configuring devices for Update Compliance in Microsoft Endpoint Manager
- href: update/update-compliance-configuration-mem.md
- - name: Update Compliance monitoring
- items:
- - name: Use Update Compliance
- href: update/update-compliance-using.md
- - name: Need attention report
- href: update/update-compliance-need-attention.md
- - name: Security update status report
- href: update/update-compliance-security-update-status.md
- - name: Feature update status report
- href: update/update-compliance-feature-update-status.md
- - name: Safeguard holds report
- href: update/update-compliance-safeguard-holds.md
- - name: Delivery Optimization in Update Compliance
- href: update/update-compliance-delivery-optimization.md
- - name: Data handling and privacy in Update Compliance
- href: update/update-compliance-privacy.md
- - name: Update Compliance schema reference
- href: update/update-compliance-schema.md
- items:
- - name: WaaSUpdateStatus
- href: update/update-compliance-schema-waasupdatestatus.md
- - name: WaaSInsiderStatus
- href: update/update-compliance-schema-waasinsiderstatus.md
- - name: WaaSDepoymentStatus
- href: update/update-compliance-schema-waasdeploymentstatus.md
- - name: WUDOStatus
- href: update/update-compliance-schema-wudostatus.md
- - name: WUDOAggregatedStatus
- href: update/update-compliance-schema-wudoaggregatedstatus.md
- - name: Troubleshooting
- items:
- - name: Resolve upgrade errors
- items:
- - name: Resolve Windows client upgrade errors
- href: upgrade/resolve-windows-10-upgrade-errors.md
- - name: Quick fixes
- href: upgrade/quick-fixes.md
- - name: SetupDiag
- href: upgrade/setupdiag.md
- - name: Troubleshooting upgrade errors
- href: upgrade/troubleshoot-upgrade-errors.md
- - name: Windows error reporting
- href: upgrade/windows-error-reporting.md
- - name: Upgrade error codes
- href: upgrade/upgrade-error-codes.md
- - name: Log files
- href: upgrade/log-files.md
- - name: Resolution procedures
- href: upgrade/resolution-procedures.md
- - name: Submit Windows client upgrade errors
- href: upgrade/submit-errors.md
- - name: Troubleshoot Windows Update
- items:
- - name: How to troubleshoot Windows Update
- href: update/windows-update-troubleshooting.md
- - name: Opt out of safeguard holds
- href: update/safeguard-opt-out.md
- - name: Determine the source of Windows Updates
- href: ./update/how-windows-update-works.md
- - name: Common Windows Update errors
- href: update/windows-update-errors.md
- - name: Windows Update error code reference
- href: update/windows-update-error-reference.md
- - name: Troubleshoot the Windows Update for Business deployment service
- href: update/deployment-service-troubleshoot.md
+ - name: Configuration Manager settings
+ href: /windows/whats-new/windows-11-plan
- name: Reference
items:
- - name: How does Windows Update work?
- href: update/how-windows-update-works.md
- - name: Windows client upgrade paths
- href: upgrade/windows-10-upgrade-paths.md
- - name: Windows client edition upgrade
- href: upgrade/windows-10-edition-upgrades.md
- - name: Deploy Windows 10 with Microsoft 365
- href: deploy-m365.md
- - name: Understand the Unified Update Platform
- href: update/windows-update-overview.md
- - name: Servicing stack updates
- href: update/servicing-stack-updates.md
- - name: Additional Windows Update settings
- href: update/waas-wu-settings.md
- - name: Delivery Optimization reference
- href: update/waas-delivery-optimization-reference.md
- - name: Windows client in S mode
- href: s-mode.md
- - name: Switch to Windows client Pro or Enterprise from S mode
- href: windows-10-pro-in-s-mode.md
- - name: Windows client deployment tools
- items:
- - name: Windows client deployment scenarios and tools
- items:
- - name: Windows Deployment Services (WDS) boot.wim support
- href: wds-boot-support.md
- - name: Convert MBR partition to GPT
- href: mbr-to-gpt.md
- - name: Configure a PXE server to load Windows PE
- href: configure-a-pxe-server-to-load-windows-pe.md
- - name: Windows ADK for Windows 10 scenarios for IT Pros
- href: windows-adk-scenarios-for-it-pros.md
- - name: Windows To Go
- items:
- - name: Deploy Windows To Go in your organization
- href: deploy-windows-to-go.md
- - name: "Windows To Go: feature overview"
- href: planning/windows-to-go-overview.md
- - name: Best practice recommendations for Windows To Go
- href: planning/best-practice-recommendations-for-windows-to-go.md
- - name: Deployment considerations for Windows To Go
- href: planning/deployment-considerations-for-windows-to-go.md
- - name: Prepare your organization for Windows To Go
- href: planning/prepare-your-organization-for-windows-to-go.md
- - name: Security and data protection considerations for Windows To Go
- href: planning/security-and-data-protection-considerations-for-windows-to-go.md
- - name: "Windows To Go: frequently asked questions"
- href: planning/windows-to-go-frequently-asked-questions.yml
-
- - name: Volume Activation Management Tool (VAMT) technical reference
- items:
- - name: VAMT technical reference
- href: volume-activation/volume-activation-management-tool.md
- - name: Introduction to VAMT
- href: volume-activation/introduction-vamt.md
- - name: Active Directory-Based Activation Overview
- href: volume-activation/active-directory-based-activation-overview.md
- - name: Install and Configure VAMT
- items:
- - name: Overview
- href: volume-activation/install-configure-vamt.md
- - name: VAMT Requirements
- href: volume-activation/vamt-requirements.md
- - name: Install VAMT
- href: volume-activation/install-vamt.md
- - name: Configure Client Computers
- href: volume-activation/configure-client-computers-vamt.md
- - name: Add and Manage Products
- items:
- - name: Overview
- href: volume-activation/add-manage-products-vamt.md
- - name: Add and Remove Computers
- href: volume-activation/add-remove-computers-vamt.md
- - name: Update Product Status
- href: volume-activation/update-product-status-vamt.md
- - name: Remove Products
- href: volume-activation/remove-products-vamt.md
- - name: Manage Product Keys
- items:
- - name: Overview
- href: volume-activation/manage-product-keys-vamt.md
- - name: Add and Remove a Product Key
- href: volume-activation/add-remove-product-key-vamt.md
- - name: Install a Product Key
- href: volume-activation/install-product-key-vamt.md
- - name: Install a KMS Client Key
- href: volume-activation/install-kms-client-key-vamt.md
- - name: Manage Activations
- items:
- - name: Overview
- href: volume-activation/manage-activations-vamt.md
- - name: Run Online Activation
- href: volume-activation/online-activation-vamt.md
- - name: Run Proxy Activation
- href: volume-activation/proxy-activation-vamt.md
- - name: Run KMS Activation
- href: volume-activation/kms-activation-vamt.md
- - name: Run Local Reactivation
- href: volume-activation/local-reactivation-vamt.md
- - name: Activate an Active Directory Forest Online
- href: volume-activation/activate-forest-vamt.md
- - name: Activate by Proxy an Active Directory Forest
- href: volume-activation/activate-forest-by-proxy-vamt.md
- - name: Manage VAMT Data
- items:
- - name: Overview
- href: volume-activation/manage-vamt-data.md
- - name: Import and Export VAMT Data
- href: volume-activation/import-export-vamt-data.md
- - name: Use VAMT in Windows PowerShell
- href: volume-activation/use-vamt-in-windows-powershell.md
- - name: VAMT Step-by-Step Scenarios
- items:
- - name: Overview
- href: volume-activation/vamt-step-by-step.md
- - name: "Scenario 1: Online Activation"
- href: volume-activation/scenario-online-activation-vamt.md
- - name: "Scenario 2: Proxy Activation"
- href: volume-activation/scenario-proxy-activation-vamt.md
- - name: "Scenario 3: KMS Client Activation"
- href: volume-activation/scenario-kms-activation-vamt.md
- - name: VAMT Known Issues
- href: volume-activation/vamt-known-issues.md
-
- - name: User State Migration Tool (USMT) technical reference
- items:
- - name: USMT overview topics
- items:
- - name: USMT overview
- href: usmt/usmt-overview.md
- - name: Getting started with the USMT
- href: usmt/getting-started-with-the-user-state-migration-tool.md
- - name: Windows upgrade and migration considerations
- href: upgrade/windows-upgrade-and-migration-considerations.md
- - name: USMT How-to topics
- items:
- - name: Exclude Files and Settings
- href: usmt/usmt-exclude-files-and-settings.md
- - name: Extract Files from a Compressed USMT Migration Store
- href: usmt/usmt-extract-files-from-a-compressed-migration-store.md
- - name: Include Files and Settings
- href: usmt/usmt-include-files-and-settings.md
- - name: Migrate Application Settings
- href: usmt/migrate-application-settings.md
- - name: Migrate EFS Files and Certificates
- href: usmt/usmt-migrate-efs-files-and-certificates.md
- - name: Migrate User Accounts
- href: usmt/usmt-migrate-user-accounts.md
- - name: Reroute Files and Settings
- href: usmt/usmt-reroute-files-and-settings.md
- - name: Verify the Condition of a Compressed Migration Store
- href: usmt/verify-the-condition-of-a-compressed-migration-store.md
- - name: USMT Troubleshooting
- href: usmt/usmt-troubleshooting.md
- - name: Common Issues
- href: usmt/usmt-common-issues.md
- - name: Frequently Asked Questions
- href: usmt/usmt-faq.yml
- - name: Log Files
- href: usmt/usmt-log-files.md
- - name: Return Codes
- href: usmt/usmt-return-codes.md
- - name: USMT Resources
- href: usmt/usmt-resources.md
-
- - name: USMT Reference
- items:
- - name: USMT Requirements
- href: usmt/usmt-requirements.md
- - name: USMT Best Practices
- href: usmt/usmt-best-practices.md
- - name: How USMT Works
- href: usmt/usmt-how-it-works.md
- - name: Plan Your Migration
- href: usmt/usmt-plan-your-migration.md
- - name: Common Migration Scenarios
- href: usmt/usmt-common-migration-scenarios.md
- - name: What Does USMT Migrate?
- href: usmt/usmt-what-does-usmt-migrate.md
- - name: Choose a Migration Store Type
- href: usmt/usmt-choose-migration-store-type.md
- - name: Migration Store Types Overview
- href: usmt/migration-store-types-overview.md
- - name: Estimate Migration Store Size
- href: usmt/usmt-estimate-migration-store-size.md
- - name: Hard-Link Migration Store
- href: usmt/usmt-hard-link-migration-store.md
- - name: Migration Store Encryption
- href: usmt/usmt-migration-store-encryption.md
- - name: Determine What to Migrate
- href: usmt/usmt-determine-what-to-migrate.md
- - name: Identify users
- href: usmt/usmt-identify-users.md
- - name: Identify Applications Settings
- href: usmt/usmt-identify-application-settings.md
- - name: Identify Operating System Settings
- href: usmt/usmt-identify-operating-system-settings.md
- - name: Identify File Types, Files, and Folders
- href: usmt/usmt-identify-file-types-files-and-folders.md
- - name: Test Your Migration
- href: usmt/usmt-test-your-migration.md
- - name: USMT Command-line Syntax
- href: usmt/usmt-command-line-syntax.md
- - name: ScanState Syntax
- href: usmt/usmt-scanstate-syntax.md
- - name: LoadState Syntax
- href: usmt/usmt-loadstate-syntax.md
- - name: UsmtUtils Syntax
- href: usmt/usmt-utilities.md
- - name: USMT XML Reference
- href: usmt/usmt-xml-reference.md
- - name: Understanding Migration XML Files
- href: usmt/understanding-migration-xml-files.md
- - name: Config.xml File
- href: usmt/usmt-configxml-file.md
- - name: Customize USMT XML Files
- href: usmt/usmt-customize-xml-files.md
- - name: Custom XML Examples
- href: usmt/usmt-custom-xml-examples.md
- - name: Conflicts and Precedence
- href: usmt/usmt-conflicts-and-precedence.md
- - name: General Conventions
- href: usmt/usmt-general-conventions.md
- - name: XML File Requirements
- href: usmt/xml-file-requirements.md
- - name: Recognized Environment Variables
- href: usmt/usmt-recognized-environment-variables.md
- - name: XML Elements Library
- href: usmt/usmt-xml-elements-library.md
- - name: Offline Migration Reference
- href: usmt/offline-migration-reference.md
-
- - name: Application Compatibility Toolkit (ACT) Technical Reference
- items:
- - name: SUA User's Guide
- items:
- - name: Overview
- href: planning/sua-users-guide.md
- - name: Use the SUA Wizard
- href: planning/using-the-sua-wizard.md
- - name: Use the SUA Tool
- href: planning/using-the-sua-tool.md
- - name: Tabs on the SUA Tool Interface
- href: planning/tabs-on-the-sua-tool-interface.md
- - name: Show Messages Generated by the SUA Tool
- href: planning/showing-messages-generated-by-the-sua-tool.md
- - name: Apply Filters to Data in the SUA Tool
- href: planning/applying-filters-to-data-in-the-sua-tool.md
- - name: Fix apps using the SUA Tool
- href: planning/fixing-applications-by-using-the-sua-tool.md
- - name: Compatibility Fixes for Windows 10, Windows 8, Windows 7, and Windows Vista
- href: planning/compatibility-fixes-for-windows-8-windows-7-and-windows-vista.md
- - name: Compatibility Administrator User's Guide
- items:
- - name: Overview
- href: planning/compatibility-administrator-users-guide.md
- - name: Use the Compatibility Administrator Tool
- href: planning/using-the-compatibility-administrator-tool.md
- - name: Available Data Types and Operators in Compatibility Administrator
- href: planning/available-data-types-and-operators-in-compatibility-administrator.md
- - name: Search for Fixed Applications in Compatibility Administrator
- href: planning/searching-for-fixed-applications-in-compatibility-administrator.md
- - name: Search for Installed Compatibility Fixes with the Query Tool in Compatibility Administrator
- href: planning/searching-for-installed-compatibility-fixes-with-the-query-tool-in-compatibility-administrator.md
- - name: Create a Custom Compatibility Fix in Compatibility Administrator
- href: planning/creating-a-custom-compatibility-fix-in-compatibility-administrator.md
- - name: Create a Custom Compatibility Mode in Compatibility Administrator
- href: planning/creating-a-custom-compatibility-mode-in-compatibility-administrator.md
- - name: Create an AppHelp Message in Compatibility Administrator
- href: planning/creating-an-apphelp-message-in-compatibility-administrator.md
- - name: View the Events Screen in Compatibility Administrator
- href: planning/viewing-the-events-screen-in-compatibility-administrator.md
- - name: Enable and Disable Compatibility Fixes in Compatibility Administrator
- href: planning/enabling-and-disabling-compatibility-fixes-in-compatibility-administrator.md
- - name: Install and Uninstall Custom Compatibility Databases in Compatibility Administrator
- href: planning/installing-and-uninstalling-custom-compatibility-databases-in-compatibility-administrator.md
- - name: Manage Application-Compatibility Fixes and Custom Fix Databases
- items:
- - name: Overview
- href: planning/managing-application-compatibility-fixes-and-custom-fix-databases.md
- - name: Understand and Use Compatibility Fixes
- href: planning/understanding-and-using-compatibility-fixes.md
- - name: Compatibility Fix Database Management Strategies and Deployment
- href: planning/compatibility-fix-database-management-strategies-and-deployment.md
- - name: Test Your Application Mitigation Packages
- href: planning/testing-your-application-mitigation-packages.md
- - name: Use the Sdbinst.exe Command-Line Tool
- href: planning/using-the-sdbinstexe-command-line-tool.md
- - name: Volume Activation
- items:
- - name: Overview
- href: volume-activation/volume-activation-windows-10.md
- - name: Plan for volume activation
- href: volume-activation/plan-for-volume-activation-client.md
- - name: Activate using Key Management Service
- href: volume-activation/activate-using-key-management-service-vamt.md
- - name: Activate using Active Directory-based activation
- href: volume-activation/activate-using-active-directory-based-activation-client.md
- - name: Activate clients running Windows 10
- href: volume-activation/activate-windows-10-clients-vamt.md
- - name: Monitor activation
- href: volume-activation/monitor-activation-client.md
- - name: Use the Volume Activation Management Tool
- href: volume-activation/use-the-volume-activation-management-tool-client.md
- - name: "Appendix: Information sent to Microsoft during activation "
- href: volume-activation/appendix-information-sent-to-microsoft-during-activation-client.md
-
- - name: Install fonts in Windows client
- href: windows-10-missing-fonts.md
+ - name: Blog1
+ href: /windows/whats-new/windows-11-plan
+ - name: Blog2
+ href: /windows/whats-new/windows-11-plan
\ No newline at end of file
From f5e7d8fd6c8b6c3c1bca70cedf636f5dc1650f5d Mon Sep 17 00:00:00 2001
From: greg-lindsay
Date: Fri, 4 Feb 2022 13:59:58 -0800
Subject: [PATCH 013/415] draft
---
windows/deployment/do/TOC.yml | 2 +-
.../deployment/{update => do}/delivery-optimization-proxy.md | 0
.../deployment/{update => do}/delivery-optimization-workflow.md | 0
.../{update => do}/waas-delivery-optimization-reference.md | 0
.../{update => do}/waas-delivery-optimization-setup.md | 0
windows/deployment/{update => do}/waas-delivery-optimization.md | 0
.../{update => do}/waas-optimize-windows-10-updates.md | 0
7 files changed, 1 insertion(+), 1 deletion(-)
rename windows/deployment/{update => do}/delivery-optimization-proxy.md (100%)
rename windows/deployment/{update => do}/delivery-optimization-workflow.md (100%)
rename windows/deployment/{update => do}/waas-delivery-optimization-reference.md (100%)
rename windows/deployment/{update => do}/waas-delivery-optimization-setup.md (100%)
rename windows/deployment/{update => do}/waas-delivery-optimization.md (100%)
rename windows/deployment/{update => do}/waas-optimize-windows-10-updates.md (100%)
diff --git a/windows/deployment/do/TOC.yml b/windows/deployment/do/TOC.yml
index 67d9a9faf9..1037725c8f 100644
--- a/windows/deployment/do/TOC.yml
+++ b/windows/deployment/do/TOC.yml
@@ -34,7 +34,7 @@
- name: Configuration Manager settings
href: /windows/whats-new/windows-11-plan
- - name: Reference
+ - name: Resources
items:
- name: Blog1
href: /windows/whats-new/windows-11-plan
diff --git a/windows/deployment/update/delivery-optimization-proxy.md b/windows/deployment/do/delivery-optimization-proxy.md
similarity index 100%
rename from windows/deployment/update/delivery-optimization-proxy.md
rename to windows/deployment/do/delivery-optimization-proxy.md
diff --git a/windows/deployment/update/delivery-optimization-workflow.md b/windows/deployment/do/delivery-optimization-workflow.md
similarity index 100%
rename from windows/deployment/update/delivery-optimization-workflow.md
rename to windows/deployment/do/delivery-optimization-workflow.md
diff --git a/windows/deployment/update/waas-delivery-optimization-reference.md b/windows/deployment/do/waas-delivery-optimization-reference.md
similarity index 100%
rename from windows/deployment/update/waas-delivery-optimization-reference.md
rename to windows/deployment/do/waas-delivery-optimization-reference.md
diff --git a/windows/deployment/update/waas-delivery-optimization-setup.md b/windows/deployment/do/waas-delivery-optimization-setup.md
similarity index 100%
rename from windows/deployment/update/waas-delivery-optimization-setup.md
rename to windows/deployment/do/waas-delivery-optimization-setup.md
diff --git a/windows/deployment/update/waas-delivery-optimization.md b/windows/deployment/do/waas-delivery-optimization.md
similarity index 100%
rename from windows/deployment/update/waas-delivery-optimization.md
rename to windows/deployment/do/waas-delivery-optimization.md
diff --git a/windows/deployment/update/waas-optimize-windows-10-updates.md b/windows/deployment/do/waas-optimize-windows-10-updates.md
similarity index 100%
rename from windows/deployment/update/waas-optimize-windows-10-updates.md
rename to windows/deployment/do/waas-optimize-windows-10-updates.md
From 7239e0d863843bd2134ecda600e67b6f5bd5f17f Mon Sep 17 00:00:00 2001
From: Shesh <56231259+sheshachary@users.noreply.github.com>
Date: Mon, 7 Feb 2022 18:17:25 +0530
Subject: [PATCH 014/415] updated the changes
---
.../deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md b/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md
index 9d20892e07..ab01c29d1c 100644
--- a/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md
+++ b/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt.md
@@ -359,7 +359,7 @@ On **MDT01**:
- Specify Product Key: Do not specify a product key at this time
- Full Name: Contoso
- Organization: Contoso
- - Internet Explorer home page: https://www.contoso.com
+ - Internet Explorer home page: `https://www.contoso.com`
- Admin Password: Do not specify an Administrator Password at this time
### Edit the Windows 10 task sequence
From f58d62543ec279f590e6a36290dd157407e6647c Mon Sep 17 00:00:00 2001
From: greg-lindsay
Date: Mon, 7 Feb 2022 18:39:08 -0800
Subject: [PATCH 015/415] index and graphics
---
windows/deployment/do/images/imcc01.png | Bin 0 -> 126607 bytes
windows/deployment/do/images/imcc02.png | Bin 0 -> 15044 bytes
windows/deployment/do/images/imcc03.png | Bin 0 -> 22086 bytes
windows/deployment/do/images/imcc04.png | Bin 0 -> 48298 bytes
windows/deployment/do/images/imcc05.png | Bin 0 -> 135186 bytes
windows/deployment/do/images/imcc06.png | Bin 0 -> 21898 bytes
windows/deployment/do/images/imcc07.png | Bin 0 -> 19569 bytes
windows/deployment/do/images/imcc08.png | Bin 0 -> 26571 bytes
windows/deployment/do/images/imcc09.png | Bin 0 -> 29331 bytes
windows/deployment/do/images/imcc10.png | Bin 0 -> 32674 bytes
windows/deployment/do/images/imcc11.png | Bin 0 -> 40542 bytes
windows/deployment/do/images/imcc12.png | Bin 0 -> 42406 bytes
windows/deployment/do/images/imcc13.png | Bin 0 -> 14466 bytes
windows/deployment/do/images/imcc14.png | Bin 0 -> 33707 bytes
windows/deployment/do/images/imcc15.png | Bin 0 -> 14389 bytes
windows/deployment/do/images/imcc16.png | Bin 0 -> 21754 bytes
windows/deployment/do/images/imcc17.png | Bin 0 -> 35423 bytes
windows/deployment/do/images/imcc18.png | Bin 0 -> 7799 bytes
windows/deployment/do/images/imcc19.png | Bin 0 -> 332879 bytes
windows/deployment/do/images/imcc20.png | Bin 0 -> 55311 bytes
windows/deployment/do/images/imcc21.png | Bin 0 -> 150352 bytes
windows/deployment/do/images/imcc22.png | Bin 0 -> 53614 bytes
windows/deployment/do/images/imcc23.png | Bin 0 -> 48406 bytes
windows/deployment/do/images/imcc24.png | Bin 0 -> 69289 bytes
windows/deployment/do/images/imcc25.png | Bin 0 -> 137678 bytes
windows/deployment/do/images/imcc26.png | Bin 0 -> 7413 bytes
windows/deployment/do/images/imcc27.png | Bin 0 -> 211119 bytes
windows/deployment/do/images/imcc28.png | Bin 0 -> 54291 bytes
windows/deployment/do/images/imcc29.png | Bin 0 -> 320595 bytes
windows/deployment/do/images/imcc30.png | Bin 0 -> 248983 bytes
windows/deployment/do/images/imcc31.png | Bin 0 -> 96417 bytes
windows/deployment/do/images/imcc32.png | Bin 0 -> 303528 bytes
windows/deployment/do/images/imcc33.png | Bin 0 -> 248121 bytes
windows/deployment/do/images/imcc34.png | Bin 0 -> 226563 bytes
windows/deployment/do/images/imcc35.png | Bin 0 -> 162645 bytes
windows/deployment/do/images/imcc36.png | Bin 0 -> 289821 bytes
windows/deployment/do/images/imcc37.png | Bin 0 -> 193670 bytes
windows/deployment/do/images/imcc38.png | Bin 0 -> 240367 bytes
windows/deployment/do/images/imcc39.png | Bin 0 -> 49298 bytes
windows/deployment/do/images/imcc40.png | Bin 0 -> 336003 bytes
windows/deployment/do/images/imcc41.png | Bin 0 -> 417228 bytes
windows/deployment/do/images/imcc42.png | Bin 0 -> 52087 bytes
windows/deployment/do/images/imcc43.png | Bin 0 -> 162083 bytes
windows/deployment/do/images/imcc44.png | Bin 0 -> 268064 bytes
windows/deployment/do/images/imcc45.png | Bin 0 -> 202209 bytes
windows/deployment/do/images/imcc46.png | Bin 0 -> 238373 bytes
windows/deployment/do/images/imcc47.png | Bin 0 -> 344777 bytes
windows/deployment/do/images/imcc48.png | Bin 0 -> 268064 bytes
windows/deployment/do/images/imcc49.png | Bin 0 -> 268064 bytes
windows/deployment/do/images/imcc50.png | Bin 0 -> 180922 bytes
windows/deployment/do/images/imcc51.png | Bin 0 -> 167025 bytes
windows/deployment/do/images/imcc52.png | Bin 0 -> 301220 bytes
windows/deployment/do/images/imcc53.png | Bin 0 -> 270918 bytes
windows/deployment/do/index.yml | 72 +++---
windows/deployment/do/mcc-enterprise.md | 258 +++++++++++++++++++++
windows/deployment/do/mcc-isp.md | 291 ++++++++++++++++++++++++
56 files changed, 578 insertions(+), 43 deletions(-)
create mode 100644 windows/deployment/do/images/imcc01.png
create mode 100644 windows/deployment/do/images/imcc02.png
create mode 100644 windows/deployment/do/images/imcc03.png
create mode 100644 windows/deployment/do/images/imcc04.png
create mode 100644 windows/deployment/do/images/imcc05.png
create mode 100644 windows/deployment/do/images/imcc06.png
create mode 100644 windows/deployment/do/images/imcc07.png
create mode 100644 windows/deployment/do/images/imcc08.png
create mode 100644 windows/deployment/do/images/imcc09.png
create mode 100644 windows/deployment/do/images/imcc10.png
create mode 100644 windows/deployment/do/images/imcc11.png
create mode 100644 windows/deployment/do/images/imcc12.png
create mode 100644 windows/deployment/do/images/imcc13.png
create mode 100644 windows/deployment/do/images/imcc14.png
create mode 100644 windows/deployment/do/images/imcc15.png
create mode 100644 windows/deployment/do/images/imcc16.png
create mode 100644 windows/deployment/do/images/imcc17.png
create mode 100644 windows/deployment/do/images/imcc18.png
create mode 100644 windows/deployment/do/images/imcc19.png
create mode 100644 windows/deployment/do/images/imcc20.png
create mode 100644 windows/deployment/do/images/imcc21.png
create mode 100644 windows/deployment/do/images/imcc22.png
create mode 100644 windows/deployment/do/images/imcc23.png
create mode 100644 windows/deployment/do/images/imcc24.png
create mode 100644 windows/deployment/do/images/imcc25.png
create mode 100644 windows/deployment/do/images/imcc26.png
create mode 100644 windows/deployment/do/images/imcc27.png
create mode 100644 windows/deployment/do/images/imcc28.png
create mode 100644 windows/deployment/do/images/imcc29.png
create mode 100644 windows/deployment/do/images/imcc30.png
create mode 100644 windows/deployment/do/images/imcc31.png
create mode 100644 windows/deployment/do/images/imcc32.png
create mode 100644 windows/deployment/do/images/imcc33.png
create mode 100644 windows/deployment/do/images/imcc34.png
create mode 100644 windows/deployment/do/images/imcc35.png
create mode 100644 windows/deployment/do/images/imcc36.png
create mode 100644 windows/deployment/do/images/imcc37.png
create mode 100644 windows/deployment/do/images/imcc38.png
create mode 100644 windows/deployment/do/images/imcc39.png
create mode 100644 windows/deployment/do/images/imcc40.png
create mode 100644 windows/deployment/do/images/imcc41.png
create mode 100644 windows/deployment/do/images/imcc42.png
create mode 100644 windows/deployment/do/images/imcc43.png
create mode 100644 windows/deployment/do/images/imcc44.png
create mode 100644 windows/deployment/do/images/imcc45.png
create mode 100644 windows/deployment/do/images/imcc46.png
create mode 100644 windows/deployment/do/images/imcc47.png
create mode 100644 windows/deployment/do/images/imcc48.png
create mode 100644 windows/deployment/do/images/imcc49.png
create mode 100644 windows/deployment/do/images/imcc50.png
create mode 100644 windows/deployment/do/images/imcc51.png
create mode 100644 windows/deployment/do/images/imcc52.png
create mode 100644 windows/deployment/do/images/imcc53.png
create mode 100644 windows/deployment/do/mcc-enterprise.md
create mode 100644 windows/deployment/do/mcc-isp.md
diff --git a/windows/deployment/do/images/imcc01.png b/windows/deployment/do/images/imcc01.png
new file mode 100644
index 0000000000000000000000000000000000000000..2e5a915b4fb425d9dd8a14136ca43e5e00006bc6
GIT binary patch
literal 126607
zcmeFZg;$na*EcFCf}$cVBA_DOAPpiVD%}Xu(%lV;bazV%64G7L-QC^YUEkz+-)D^P
zoPXgQhkI;bZ@BMkt-0p>)xujsOz82$=MV4Px%2qbM**ojckUhCxpUVI1rfgTAujY2
z{0qTCN{H`HPWOv7_~f1ruPE=GJNbdAm+DCH`2*9BUo7t2!6CW*2jP>{o83EiZc;x9
z@XFY#Z2m%)!5W$H9LQ>p$YCHQjd`Z&{UN1!+95aJ2CMEv=1i~u4@uHztwcPmRXKEB^(fTcmLwF**?6Wx6z(HC*pm2?|=UuI<}fTaD9pL
zKYw|@Uq<}*W7ntm{{R2<|KZi(@NRE!4+{&symYjVdg*2D{=cR1qrRb`p{a?4l{J!J
z+u7FMKG}nvoqf|(8Vehnos;w8;$mcQFz=IqK}K$F%fp(srcg3*3`|Vbe~xX-s{)so
zm!zUGZ(hCnp_u>a9&ZuRV(EWM5#kPk6>UtFNQ8au@lDfPg^WClgm#KMt&YrT?6?dv5Rtk4gJ*
zW5i^4wobDpz&{{B8(#cbjl0=Ym0e+*l8cy_*o@N&!5Ixtt+LDIUQ1UjD=rpR-Y5Ur
zQyQE2#Kc4f&F0QuoVc1}zayl-e6gEv^j2^1IJ>wg{C~gLJvzGFe@++1qj|h?a>rYx
zGbKeuizPy<0$m1b@ePe=@y0nHg&xH51tHY1FPSnDA}a{s(!)Wy5GT_q7K%NY!TtADWV?*S?(1VQ2D^JoVLJVq%)h!Dlt@?Cx$JZAL|k
zIh-geDiZX?xw<^)A^#zIZXz0`r7rZg_R}}U@ALEX3oU{Cc?sMO9=symivm+@WAqQm
z2!duX1U&hig>Rdh+e=vd)b#Yz>x&)L8t1FJpU6Z`hke&q7ai^GqkT6Q36+(ck8~(-
zdt<#Z$>w)bgaUnhd?Kj7xMGw!FgG|hHZ~@{_WMT2Wox?9{i~#;Bug&4eoETC9n}7~OT^>cnRbmT@?hOJ+5Tj^Ype9Z
zg9jWO922D`E$PJuBkdg>$jHb{X`b!Gd!5lt!^6Yriv?O85p=3Ksj1jFIL$PY=|dUP
ze^`vh-8vPpb$a4OMMbq*u6A6Y#-bcYa+IOEn+raE{#;R3_JYmy4ttX8q+On0YoYnl
zXWP@MN*i`6ybb-900M>Rbo@c5?aA`f;JCQB*jQgH_h>|R_Hr`ucvG7PV&dW>Lqk&q
zTByT35vX`o)z#6DPJJaEjyLlQ3;7=?kawQ!&NW0)RG|-NCMOq|&eg+~pLh~E*IEml
zk&=>%5;BtTg9?U%6ACb`@Be1j-leVobyO0|7g96Kh(
z=ph~+-soX)aPa;6_w$V3Xz+vu2R}eV(`mmwk5B&FSa|OQoSe+K+#FAs1aYw4Z@l{%
zlZdD%;Ckk!prGLL>dNT`>3K#@&h^oVD!(Qr6;%?0s?!nnru&7n-sjKlmuCk_DSo(f
z$RhX6&EcHV(b37vkHp2jhur*!`>sxR4GA9@FSs0W3q3&r<&@2Aq
z?WvAFvO7l7va+{z$AA;jv8Ocnblzt@$+5Gkt?dDJ!@h<(15S90>!asybqCWWpFe-z
z`n|ojj8r^+b7iGP=I(xpc2^9)=M&fjG`t*@Y9A!tADsqq>PMeHe}=ZUu{~A!>({S*
z^Vxoj<<7O48lLvXA`!w>hWpsq*ugDRQ_5ezzBrJTkWj<2nXa-^;K3vnVRO0W8V+=K
zM`A&KYun)Qm`S@cuc)Ze@s)$AgAAIm&!@c9Jikyk9>g;SbIMh=dci+K9K5BN}r8W9vg7^l7B0s;bd{$1q!{Y$-Iva1k}93mdahEVs<`HDl|d8L~meKTLPB{8g1;V-|Y
zre;{%DNU$O?RSLr_4Q{>i$8wRs#Kl+NpP+&Px+sMb@d;wK$GF^p-$%rQrO(C78_ABMy
zBgXCao`cd@7Nho_o|bh!(Y$wPMDP4);D0uHq@ifbY>3m}EjF;r<8HCiU41g`03)#3
zNpx85lCMvq}E1v*ksI_7zcV
zG*^{J>_kRhUcME7GprJo7WuR-fPnL5G)x+ihY8N8N@im-fluTEwhY;E(R
zpMRGMz-JBEQxYTO;o-5iY$zvn&D6p|Q|M;L<@7O0a~iLEG}ebN
zLVnNCF)#pGFgahI>J6mT@kHm}+4tjUcvf9i71c@PxLXH!VYKgY1qxG($L{fQv&h+r
zQs-cAZ|~UH*!cMKj{O!Q7q!Rq`z|}v+=DMF?+JazGdDLM{`=+bj@IUL1AGI&iv}^#
za~kBqgfRuEx$iTC-1b;m!T|Gwr~f0QaBEUXz8K4J1|Jw84jdQR`}tBVslrIO9Uo_DbvR+KF!bB2=vo|n7%
zUkbGuoP7=R^YfvE+{B3BNC6;9U%c3;2Sr3QE0DTN%Au&gfB)XpbQi`OgDUiwlCt}G
zy8IrG${kKaPTnJQ9Ji^Gt#7`jhi^Ki%{wa;&Q*4!D{qU+PF2kn*
zMkXeKsk6sQ@v+sD&c0mG)qHVi&Q}s#W|K=zW;_DbQ=cfBBo=$Nhy5H=KYT*8ePPxLe$p;%S$fyV}
zFK_3S5`f6n|B|!SvEP6GKuP>Hnfce>-@p9z*|TSkCsQ^sEoP5JTARZtq}8$ko$7=>
z*X=h+DlnDY<)|qxEd2Sp-gK6R%e1B<8aeI7vJrnezCN2y_Y2*g5E9{+4t_-DR8(A-
zfCKVuV3c+j<`NPT@?0HaCcs0zwOAIRwpCPozVd1s0J_=bF_f8*cKk(Y5UWi1LTT?>
zTPT^Qhev_%DP0_iQO1l$FwfayC@@g%Z{PB?u22Vz$_6gwl$7w1Vq#)o1N2{0QjSA+
zT7G5Ze2HVAxzOwn15m9(oXMMB<@RY`{4W(<9lLk`{u97Hupq!Xioe#9s0r;pTqfXa
zjgF3ffbQDC&c*?B
ze}B6$?4P&oN4~YKtu8DPb9{VU)p5@q2L1h{4=;ks|Ne#7(UeearFXj*-OR$iVdRsG*nG3c$^&V7@+r$#U@igvS0r(M;Mk&qa?C)*!#PZa54
zF4sHm;#mEBTED{Z0CxI|S^#WCM_Ze^K8mKBR?@vwnh0QbVRi^ol9K35s8Q1Zr`}zk
zYJT{_(DoA`~4zTq!xBKOTeW^erouTh#F-Hh#$}2Tj0g~&?Zql)1B1O($f0&4Ng_cQ9@kY
zqn29L%MY(Vyt*4xuX`^g9L=h($dE$721&ogG1)`YW3sk5O(dET;K;|dqm7YQL9KdP
zT1X@dv+L_V`4Z?ZE;oQH>O}zH%x3i}qs*c4T=x3SXiz@lI}5@LS>D`qgr)!>;k}#M
z=iLu1GcI#`N-rrW#`+x@A+k}L2EPuE)gFaXt}Mm9(>6^@pg5UsPT)!qpxs9&O0{r4#P+kWB;
zCnu-Ddzg$He^Q-&d0!YS9P`{3r&8@C_5yi5aL_|imnC~r=vWcbs{!Jgrq|*(p
zj*Ol@sH?FF{|ZMyP%vAi`uT()oMPtu(o!DhOEx+5VYC%7L(LjNq{*o%NxV}^QeLDy
z(xbz}+rj`8&c?>}GI%XVWGC{qSN9KS?iHvK163jWqkdJri`2PMVVpnuaJK7oOdLKd
zRT94a_w!V!#W~u8MEvh?(L2+nlJvGI=@FuY@}(rRj)8urMkY#%m#?_FNH{4<=_||r
z2IM5V1tDa#c6L5OMLjq?tg_je2Hy4P@nbkjeBqSu*{-SU?l`1d2zJQbceIGwRH;fb#|7B`U{A7ox=;#Q!KSSS+
z@jr`wR8p?hf#U^;yS+V}Dw0n1NzdH<*Pi(z&g8U)kG+KgUa&hH|Mm6t{rmTCa`Nl;
zx>1lq2;Vufk&$_}b-tpZc^nXop#xolW!NSqmG}GkkpC
zY!5AV`$KYZT!Z_%TO~%f%-yzv=-@kzYq5{ud(k}h!NI}V-ASPU*lMQNRvvaPs
zjFg=eo%4lcLdqS2*8R!Ia=1s0O`W>V3<|?VwSVbLQxD}$rW+wsMHHC#Rqt4^k~g!`
z7N=KXb%JAjcTD=__O7iw*p&d`ttxM5+((5WOD?PyGFg!aiShS%0Rr%^JVzQghHx73f=r?|O{IXIFZXC@^jWoG*H
z&$3HNNuBzWQd{C~$)pL9D51GNWdmS(s}dai=JdbEdx&-WB!wC2Ic>DG2i~IPvxg$%
zT4QoENwjw>}u_FtCJfURO2xbmXVcT!NvNWmfF_RpYU2nZ~?{ry{AeFb<^t#An&`>EpcV*M2x4^+aoyO%F9hnarw8d7ox!hN^aU!Hf
zw2~)WQ!+|QSSTpk>g)M{oXg3{&D74;HF##|=@na9OgB^3cQM7~O=i(|WkWuwWmy#$x*v2u%*{iO~;LBXG{uB)mnu-`9l
z_nZHHXlYq;I~lF)QQF0}Fl(fq!oHW5jqgy*h=Az!v+}c+Z;KJ~)fHDwv=4YKnR~}U
ztAUYCMM1GORwyK{Iy2EiM#WiaP+Vd*I5e`dxO^WOS?O!F{bDORgP9pJvS(Nr*0NIC
zy}qs=jmt|*?rv_UEKdQZ;o^>5PDH^}t9S)?qVKwjabgrJd_!DLPq9aK&6ThR0)|51hP~cve*PRk^wzTwU~z`?P;H&f4^llvavW
zm6+Y0OG-;4rKL62&_L8lcf887{EvO0OLzOkQ|T^ejHSOP>&U+LO+VJ|ND1JkV$q)<
zV5reqLr3gLbto4gJAkDE)E5=?48S}HpTFKYjgR!?UKkiHq-SUO`Uch*>XMU?q$Ve0
zJbemcp5U*D+gC_lcnO5oITS5!RL&PvIuG?{sqLM8v2nAjnC%v{JyR8&JMBs)7hJw4sk)fK8tPmkgY?X6B>
zdGB_u0)vajy5=}m@}%PgY=*qNKYsrF3A%7hjH0EbrHzA)4Ce<)Ge9ZfZohvg
zC8_J{Q%<##z>oB@z9mMA{Ia4(d~!d=MNgPla;@4}4J+R)r$=3<7`SYA4@CJ*em?(3
z+b1R?BV%i83(%2*k^<@8{Rnv((}~3QA4H9e9Qj=1|NT3iYXERbPEGx71nED5jnU8B
zAKu&%NmuCGk;9F8CDigyry9S!8Zn~s*ww$>!PE@N>BvnNlP!jkkum3Md4Z}xV^dS=
z->RydYgshgSKjL}&u_lpdGM*NP^aho;sORv;fDLIujDm+E7Q{4@i)0SEy5fjq?W5`
z*L14K5$;i-RCU=z50_C^YRMsR)qMb!2$c*Yv^+8O=rx0+T703A9u^LEwLQ7~*U8b*
zG9ZV_od2;7iXH+(n2n5^2Q1T5x~96qz^xw8RdIacs`0RcY7LJsSrEV+sPkVwe_qcC
zmDc-$SGw~+eQQwK$x~L@6b+aS+wROap|4A@~S@F-oj{?RhrWJibqHz`3s}g=%9dAF@*C68&ZNf?hMLtQp)Su#I64h_Y
zt)L1mm)JK30=6^knl>wly>3Dh5==BSfRL?kE%28b#d`l<{B{Hy5Yf9A=;*vo;r}^|
zg79Q)%vMLidhF0#mDAMORfi0%i5U`Cd%s7vD^xb?ES1h@Wg}@}S9DL0nsRALRnabI
zL}g6dhD3<_2=9i3hNb}Fry|3}C8DdHDKW|=r=hCU*0cZ<1A4vnV~pFatwUZcB@osU
z&6bwv#NkFJe4Mx%7d7>=)QqOa;$nYE_~UrA65(O|VnnkevxVJ+XWv@6<%IWaP)v;d
z`XB{Ae*?65W8V~A(sk8;mNqt#L1B$E<||5A-_NGA3AH~_^h#9ZHVzQXvrROi>v?n_YYhp6+ywK
z`SqcKeRD$h6y0}#7UJ#f2-xihySsC$s^XOY+&U89rQiU72K)7ETx4VQNK^x
zH@)HSd8x;RBvnK%_p6Y_28}i+kyY#gU6~k<%k@`9#qqkjq=HPJiAnO)K#+DDJkerf
zVv?I0a=t)~@JWzUPl$}%uA+5#VDXD5&k#lF&6_u1Wi%L*xvoaco-2S>f{*WTal8ep
zD6gD)A@KL!aX=R16B9gk`){bJsTmj;KuQAB3lM2q+WmPSBG3vbC@A3TpoDm0XqvFT
zeG58h%OX4j`TAgn^pht~Ks1j+(r)aQYJFL=^%TS6;Z0xuir&WU!^oBPnjLr3=zX#I
z=d(Tz&uQ6F?W9@m5x$r5zQUKvunKT18=C^3RR7v^H8ej$r4(H~7}+%+MH|O
zjBW1Fd?X+sAWFVK;AS(MzgPJSC7BapuCu2H{HFrYLV=cGVh#)rf|aDLrltmnQeFKO
zW8N1fMA|aoyXEEOyXp#iz_Bf@tWI`jTvmHufqAA&|DiZ%F&_2I=t5flWC|Q6d6jTCZUrhn(xg7
z(Fh9i@?b2g$-nIrtTpNLYV`2(@skE&d#c#&~(4rx;`{?a^kiuO;2wf8IczkM~k2$Cf3x~_h}HYonCnFJaOHqvm}i?
zLhGj-Y5XB|r2zjY4*+cAGokF%>qP>bLCG)a;BD2DTms)2q$!^wrsS}nxxNAgPDDC>
zmGW7QzppPQI(l$usPwA}ED{nDHh$2cSRS9z^f`UkuV>nsEGGt=2YA(ln*~scf)q|9
za?6h&y@G?$15jn|hPQQeV4ga6ES7GGTy;dsPa>`^8_73~qq2-R5$kU#nohnh)RF1`
zV8j`pOg_$CC>oiq*3slWf@YKctZ;wA)*|BoBOFYWT-o7F>_Eshr6cF(9
z_YVyXMLNCtef!RgKb3bf%g0A>3$8T2(2~Z_?Tz>+P5JVbQ|z@Byf2Q|5edZw`;IEI
z{Ql-YQbA$fa%Qry2$^{Dn1`ok0Rsct(xyEb2SLCLB{_NGSbLf^I*hn~|Na46;k%#<
zgwqQ>A#?^~>c{!HeH4J&HDJMSnVG@X2amL(?W!NB?7Ss99v-*|G_PK%Yii!@z-~RE
z37sin`o!*zoHMzsH!N+**J*q@ZuD6Ny^`dVn5O15%AHAE5{m#gi#c}+)h8n-HF5;?
zB{-M3v|rhr&fn%NalQM{w>`J8;c$7n2c>1bh4~8=G>o|_rwf)6tOI>jX69n(I>m?R
zY(?*4O}+!?q*ch9?M>omI~;vOD8et?QP(BIEtzUY;mZDeem^Zgf5tI0%k@8aLb<0V{1_C8`>1ov6vo8F9+Eb@G_
zBU!RPaazuh(%BdD=Z++3kS;_j`9<<~R>KY~p`yG6OpIp;DXYEddQZt7Jn%j|w6w;5
z`U@q&SxHjzN5uB&-U4_!XRCe0B1hmQq-SRCVjjj*X63j0!ON=^
z>{Bl}>RVarDO=fRVPP=*Osf*0WuG0a!2WEO8H?E2+3D)8Lh}VC@hdLw-Wuix6oj9U
zOh42?{C#dgp%#F=EIoWmZ%Y4Xvic6??qdn|_5HZJnBG(!F|9{d!G3*x4d|rq)hl3E
zlg~f&nMo?j-7n{`*?v(iR(_xtJkuS|%}GJ=;3sqyz<3Gt>Og}YhR*pXHkG^FTmwBX
z?lu7nOnn5JO+1T{A`r1y%G)JZMpfPk?-BHxS%zu^|o{(QeQ#H=mu`q8+OayctH3y^^1`-DBLr@huf
z#Mj_JOdbpNJqQktrl6ui?OP974g=eeKX)SD)6K0BwEWQ~UF_@wB~u_jr!@ET+Ws;S+%`BstwBYC{t!@~n)a9xJL=gj)6y-5`n6|f*jM@MyabzrE6hlFrA
zofjn}sKU_QxWtLhRjqjkE+dvZ1_)!FzhOTnPgUt33WDa|2H?Kl9d&PSPlRxA7l<>A
zk5m7Oq<0@ad`SNj83_O^9;gIZ%)`H{tGNrQJ7pfFd&I`Z!cm7!&HoN!J?KtR50|JY
zDUH!g+^o$JUD%Eh~q647?1%1BFrEtiN8Dh1{!Rh
zfVg;1IFBn|3plVCnvuS
z#v#yN4T$royT3Pk)xW*H-C3j{4EC{5)2;&y`}7_#Ch6&HDLSnO(nMk2)qs?@x6s0B
zIC@7?Ck>J9ReDwy%<`G$W>PLLt~YP)xy&t6$^ET$RZD$^)E~e&H?6>9IzCDKi!|OUIzI7{M=8UtogMSDuK>UeE|;F%F~2!I)j7ne_r@>2SR@d
ztXC~s)f5x3xr=N2)?x`8tG|DsJk>XO;1;oWPZRoI`1w7u&a%YOz0Ytxuwc8t_(|t{
zD~dtW&(AN>0>~7EO*GzE-&|jrR)N;BOoVAV2+k%T7j)US6(btLLR;tT>Kt_ZKj{Vv$8
ziSOu#(1|~=adHw9{DjkCY6x0_hqua)Ax1FPAu!O*)Es1Y%Ji4{<;(A%+S=NFY$Vr1
z#%WgxtF`J87xa#S`h)1}32+)OXMdu-JbR4Ej0{7#O-4>mLq0Mjq#!?kt*_L`u9nwd
zx(fg%utT#ua=-$K?VsO{IDM7i^frQcYc9c-CiDXbI}(~zp`iVqZI3YF*9XmcXP6m
zlj|)_AjNaN5XeLOwX9YI2?WoV>65I=l38FqC)>w;X|PRNQb=!Y{dh{_TxGk5xE6E?
z=6~XNr$2GjI_FN61?;tlcMLG@RS{GA^^FZ8c5}D0KWMR(?{CFZwh-`PDYAsB$g>!3
z7f#u!I-rnMoH#!Dr-t{rtWeEI>!AZ)Bju}KwW~`y*|zOTtC>+L8kCw_BIgArV8mzSE1W5qyr7q3}zzK(cBLZUTZqz4^x(tiPZ{cEy?Qt3ZpS|9dK
zw}7}0=c)!Wo0yoO?Zv*;>)*I!0hcxe>Z*3BBN7gkH6XuTrLfLP17HP}mTUd1eJNl;
zc6FlEPeL>fjD1tFB72DPL0kmlMEum8$mFa{*lf@fAp2B)p|63CL;DrLQ`;AXQ-vS{{)U;|<%z*61
zoB2w_6%-n}aHz2bCTfy(_Q3@7@MoK#V6%OIz5rn55OPf^1Y>?P+cPyp$E}u<9+E27RN0?6{*(7ts=wXczSi2ZQ<}ly+4Dd-g39R`0TsP7
zUd?rmX#&mAfL|_-iVZqiUWEJ_8p%;nQGvO10lbFnKD2@T1&kjfgM%giI8FVyEE#e}
zh1#XJT$Ol6`ui;_t31piePokHa>5$-fqEIxoBOIf%0**YXgE15tE#^8^QSnPMOsW4EJSZ<}Axm`_Ml6
zYF}U9pw5hrj=pKVt~NepVz90fAvc5_F|r&!{Bk$tZ)OhhHlAhL3>5Qjm3kC{zRgm5
zIJd*Gm#^>6X#QOnNvdYOQsb!#`y>5jR>dJ_XJ^PAC>CmW4Q0u{@_)*g*1;e}3XX!F
zTcZX>H(KWtnm%Z)&@v9*HiCYj-5Hf{v!jB-WS(sN2)I4HID}6jTnKuuHxM}=A3o+e
zpD6u_5~E(_W_C%UbZWyFRv*L$XIfhUw?6d0{uD}Dr}?THRJUjD_ZjrfcV~Hth!R3V
zFd(z&l~q*qmNHPV4AN3*_2)mZ0XD_&-N4wg+8AzYZ)ZGkiMr##2gK
zdSP*~$l=8JvdOt4?crlKvFO~oxzQa88?!dh3qsm6eRG_@NsBfEq>Z&Ac=CKEIIk*q
zVbf{tN5U_g(VxAifZ2D$HbKXn-_Hzb*KhRQL=^4`T9Dr{8L0WE(xIKxelvq1^x0J7
z{tc_i0^@;=a#dS&TykYoKT|}Biu&g8>k4j=>VyIb_zf_GUJ8~z1j4-f(1vFyAjRpb
zq#*6u%yQ0d1na>?Sv5}IMeYY-_D0QKy8LI;9oqV299<^7T3RHVsEVymED*38BkC2(
zXq`>>XIZ79X6`(02Uq|1EZu#{m(EN-qawzJPdmLa>RMgAc5+$AqEAJEM)#J8CP$@d?o;2?YgRh(&x#KiwvD$fH3LcZOViNl1$EBHO~uV+Ds-J4
zvXPRFgR`yGQovx)dj$mm#DtiG!~%`R30QD7EI(-erpXJ3Y)`fGFeWD_O`RT~psX(c
zr%16
zZZxsX23fWRjUAkS=2u^`ynA;IOq2ZcuT`l$b};;7BO*LRLBlRW{T~4xQthsN!7xI?
ziMr`1DDZG_hJPs;K)r~45*+&3Yx^Y@*>y_Zu4F$;h#W0?a_Ha65@uw(_{@UX9Z}Ps
z^fwiD6Ve(b1sTKKxyA(tPyOqf9vKP2vO?4^KvWX6p6o1#-Q8Eev&!b!I|EXtX6S~Z
z@PDxT%`|J3u3W5)cbEY8K}1C4@-~JP8U27$*kyz+ZgNTr8Ue@R<|g&xR0zJbs_M?-
zq9tTlnseQE-hr}wU)OXoBCJw~l(5F$B|MFpYu73lY1^AYXw35L3zZ%fZt1R@UwueH
zrt#tU;qKt()rV4BN|C-_nxNxue%w4JuE1MbS_0wb_{kHi$E9QB6-J9oD;=$^iG4Fk
zH>x|jHC>cB!m>43zij)3*Ec)JchdlTkTev3}CB
z%Kj;S>QgAkbziWri@&`+wTy3dx@LwL<dDWIRCDI4cs5lC3bgr2M)%<%)C^E7N;u$3=|3#X8Fli
z;l)z7+K@0M+uqYBft-?-HwyO6{YQ3OmDt|K{7z1giLCO^rU?|1wCo|L24U?`_x<}j
zl~)|!txqPxE-9~C^fJXhp-_095|9QLuwq_@ejY!XlFEHqgRKU~w?slt&U$ZN5X{_5
zwNS5-p!oOz%ryw8RI1||?`qgSE|I_u`}Y^l`65o<#>;>P@UQ9o!TNB;bsQ4sW87
z#F}E?t}J`c%bBy(x9xnvRV=fu?K)bl(D=@G)u=i6wR}o3QJQvSkp(XAz7m25JS;OE
z{=289z~LbY1@}n`8=IR!dz|+hpPFVCbQVS-ZNirAm!stx7U+}KsE#mF_$+7R%$$&i
zAjC*d4@v328QDv#n1ZZ$T5ISyfKf6Xi2)`Qe+b?^>O5
z3$51jU;q2UdCY+NK|Ve=KCV?RMKbycs+6~{@1L}^f=^R-;c@TqHUy}|PNpo(;8G0W
zpDEp%WoEL?M`;xm9KbB->30GBL0k!hv|&)AK>Zp&)ICembKah0Kh2CTXJ@SPCeH=>x>Ax0_UBWD<#WEOmuff+p!dv}OUo*`Fp=v-e!;>z
zvHnOKJ5C5H3oe`H;P9|D6&~1&ibBrL|H8rs0V}MzY|wy-j@b2}H{0G4bUwt7cC!9h
zQ&n4Y`H~Z~TqLnm$pVGIEo1NS4ucT1x5NrhOpVNA?)(uF1-aH%`EH8~Qyti-h7+7i&zbhq>
zSJ(~KIIgX%c$PRLSI-xuT;YVt4O2|p?*&S_9XAXn`&eIi$_E}Roqhwf0`|y)99zGI
zg@t-782(6XikxN9DzdU#Mn=_uYLt{Fo;Zbm@x6UgUMs6x&kj!IlNT)Bv#|g|AO$vE
z<5F{RndN&K@$@~RM^kQp(efUNPdqj_xJBD`vO~QzlOwLEpXB6*f!aVmAIuC07*oD_
zg`nkhzWGJU++1B!@{^vPpq3VP&V{NNfgl2zFv>l@rz;N-L7s59xv+Q2p;t2gOk
zBU_0qo`}qMD4MBPmd{o!)*B#=fAWKV8uXFuujODO*n+PCJOJ9)W?2A2)?RMSwYh~w
zgP-YZR|V@L$%DIq2Oc8cy$hKv4GoP^^+ivWADZIbqMr=P<1b?S|Iv&obTphppu#
z_4HLFZS{|PbR
z#?H}$Svyu`XYpB|Qe4bun`o5ek-s0Ua)r#7FKyfJw}dXvX$nvFpT;OsTGQY-J2Ww+
zBwxMzF)?suUFV7f0$)jC;ev|JZm09rc~=ZG6}%>EDR-qsO#n3F$3*YAh>7pkBn`XV
zT-n%^Ioyu8u>E~=U{m<`v8=2N-Xq_&Z=o)D=d5e((8et>igm+AhL!m{APFP8WR=}3dV0w0*!k)6gb;ZdIaz19$y9Zg;iN?;J6(?N)|^x*F#7E3k!#lbYL4{
zhCDa@qp*0(SH6b&^>tOJRQKc-!EZ8yS-ChXi+Poj7kvTFN-D~K79!5+GZXWwO3IQ;
ziZY)B$H`}$kQ-&0{Z6;?>+#iKF>rW!$N6Hra_81%&-A&HVRQbgT62Ay+nj-mINCZo
zkzrNmy7X>^>FFp+JfNKFpgqFD!kR^v+Qk)>x`WsJ(x>T7=R`^0WQzh;{i3>5kZ1J6
znj{4BV@P4Zof3!ZOFM1tWpMn+M54ZzTb{Mhx0!h3{PZJWV3tFxhQ2OLT1=o)pyDm!)}sRtZuJq?4s?@uaH{^8ZEHR
z5NQ6WJ3FHxxdg9;7{J3Kh}nX)}yt;Em20MZ6b9`N>iBKsl?=_D{b^oajfIh~KL<0seUo
zA+X!;Da^u?BU~F`!ydlmz*S1nV><%>j~1O7eNy)Nv!s|YL)8~>hGPlQT0P{C0+!Gs5@L7+E^7~qS@lNUJ#d90>Z7+pn
zXRGRnEgWu7h|Hm`6~0Hr8nxTLConQ>70J49#i;8yU1_reb{%x)Bz1MjolW-h@z&`y
zHa7Ep9Ir+g`PVb!+TUI==$iSvs=aLUVWaP)PgTGCjM3i6P
z;jx2w1$lQ~iSjF)`SS^rn(~T@0%;be4_B4Aj-R62As_o`7^*1biT%d$78r
zbF{a>Pu!=S3i|b=iJhX#vOl^LB_Rp6I1Wx4P)+AkQ-BiK
z;o&djlM;3H7ICpaVh|D#$g7m+1n4!PhXNN_Kq=SDLWVecsaLX
z)xQ7%M!1_s!-o0Q9sgFK*1*((hdCg7)+fIXNR^N%qHU+51T?a_xjFjlF9fQzkU8MG
z47563UERyw2DIC&3F{4q+{?!kVDns^E(Gf8GGfk8)}L;Hdx46I3S|a10*_w*o9+g4
z@JONg{Ul=Sx`M9r0F!hRzz;-ETH7qy1YX(O+ecBt_2vnam7WA~XW>KYyapnO?f$tt
zT}`$KlC(xs$%TuI(mmKUIkgfs%H
z0cfV&pyW$SOGlZ)#>yN+F9Jn%(ix(K>_+3@NEgw%YzJIM%z8pV69jZ2AtAArd&$+c
z?#t^#S!^a@HoIhHv7i*|Vz!kFMiQPH_2Riw8)8_{3bV5&f^>s-3lo0a~lc*pF_wE-o)7*4^8i2V#?`1(^5T
z+}xw2m&2{CC@C76ntLN)c}2f!fRfLX1J~>$Mc5I9sudL#JDEzszJpc@J;mctA5O;l
zI?TT0Pd;2ifrJ3XDj{G|g-bFqHkJ)u57px_kO&X@c22+Jd@YSMO?WvfY
zWa+7fZOadq*U$gzMx33VL(0}P79Mkgn2Z(IL0&=OS!F{peEa5|zT2qZ^hZ6t3=fa{
z2RLRd-nu4-hlibAU6q;qw-$+p{>BCqsxTeTp{m98^EMhmvPS(b1Mu_4uEd{y5*O!z
zHbSAbgzN3irP$v^OvBAh%oOStcQdP^$y{9g1)vlK#nI!N`R(4?s>Bp1jLml=zy%8a
zhacJ!tE;O+IVfKTsMg)$1Mu&*CiJ{qfWbvbD#`C)hniomUkM)K5&DSvWf9g{A)dPo
z!yp5?Bg@RJixwDKM6!?i5E1b%?9R?)b%$GNptvI+ALqZkhf3c7r@^h9T{M(gydm`9
zkeKzAotxD?&29{LcTX}BvXjIfP!OS~zrF6^ak{#s_iCq8`sa8`SMzOU(Nt$6v3F#o
zG(TUjCHG$Nf8Vh#VccEt2%tOiv6^s(!IhTBkNvG(a$h9?&Y(%mOdDorv(AdY8|WY*
zVQHy5?L=y;`oJD89XdK*f`=)dm4%Civp@PVE2Sdsem!_NKj5nkJdtnd4Tk^11#iBb
zZ4UOmMH8!9lN-1Zo&aIpj)_G8^*tLhjHG5AF
zcle&j@4mysL+W^T{Sz4E7UPF&kUR#ifOmhcv~Z>KY`=q!v&F=OgJXSlHL2Au3k%{JY#CVeHkCn$RG>3D=cWWC0f&J
zg==Wr_|r8RlW(zoYw%LTS``Zmf*NqW6M}_LubWd|X9pzDYZO(@{Rkx$|EH~qiHRQ@
z5g+go%z2bYmSxV|^yFSTA#%tIrJ6UV#P44H(1Gx%hQ@q+wZpBh4ni=ur3HVA+n3j!
zhtZLd*}s&Lt=0p){3d}n<>#AmP7`e_)*KxjgoZ|fPNaTP!;+Gk$_&G=m^;WF6*r#U
z!b90l4zv#=n8h(Gw_W10@=|c7{!XWyq~so)v`y3hJdmKCR&iHh?~&r0QY>Z64cbu%
z{S;QFyblTqc@2h>p@!5~srrRi*-xUPVq(Vs^ScGQV%%`)p1Y`|m*nIS)UY?6Zk_Vn
zh=_ff!y8fwj!dWljrsQeJ{9>lZLK{&K{c~H2`=v~4Aa}Z`pxLx0^&kxhMpb}CxaH3
zRLI(`oG3)$qLe;Y-<<#gUQu3Nyd!jb|NH9d3WytLjsZEG#7Cod17EPuZ){A+?i^vW
z7#bN_Sz2=3@bfN~HpWt9W&YbISIa+_C0t5`Twqj+;W~QwV6VK)QwY-jV57)NFIxDe
zr%{0U}Y&JjY#6;e#%|iaH^26}^
zujQK4i;IP_jvm}}mq;5O=(X_N^^PQ!Ot6#F?>`BK&+*@o=zKJ$s9>BeJ)WK`wsPHN
zL3s;flp8G0kl4r;v%nJMw<3H}`!Ht(CW3Wjm=Nl^4Q<^`fa|RvRIt9n#lcSf^M@G!
zH8E3Rdf77?6yq8iS_<9=U18GFN*B#sTnJaOHEMMrRVp1`XMzE>`kIOOUS>NJF*RfJ
zJe^~pof88hsyp^+=9j@;ecIonqvQ1^He1sKn3z9#!@TnW%)kz_mzSUZsOkJ#hIBgQ
z)80B8*7ldYTj3IJ)Uo5cQ@BYpkVdU1@wP_7@F@j*-yI}FbsT=qs
z4q@EM>FIZ`U)N7e;4=Z$
z6y}gcn4Fxd@&*#tdn8tg$4p3%jx4)EN
zwJ%swk}DUU
zDIb1WI^E)DW!-D=1cD#Pr&5im-d-gbwbb7!*Hp#S%$PH?mY&Dvw`dRTg{&;OI%!a!P{?dO$Ckky$RGi=aannZhb-X&avQ~XF{+{Zx
zq@V!9f9E#(YHKSaUue?7ADhb*>oj^Mz!$T8Up|L?>GAYk6`a?JLa}%M1;U
zJ9tW$e)HLWx~ue{!c{G{>@F8VaAV@Zf`ebX*NmH
zfnS`{=m<~%pAda+b~ev^sU3PTRaW}@<|sR$Ki6o2`@8pA_qy+ErTXmPztz*#*n+98;#!zi?b5~7$QrdYp-Y>-hm#Wh
zMH=&S^8x+=v(b=dZG-9i0Fk-d^BRAK5hfu^BGm(IIH{herIgz~_iDMrvD+}=Quh1g
zS8ZWvr|IvPRN|U`e!8W)wmG{4z8Fx2j-a52{xK>prlq1Y;by&qtvGmKI#HS6%*q>x
zjQFpG3iPPdF7yhL>L0xE`Myvn73=xS<5~JOw??IAMig-gnJUgjP#&%QrhFO1WvWIH
z5oY>BI0+>P^&7-+$EV7k-RsGb0jV!@QqRr==6i!e?P#4^tJ_#QwQYC;nHU&cD-s{*
z>!+osGc9OqXl#MXVjC{}`6`N>j12q&F&-)^-Qc_}Ktp5*%==KbT^nUa0sFITOyoBecFfNF{TpSUR8g@HU#=^Wv_FRGlz15>?;kRc
zr+weob-)Y-jX(T^8=>B+U3l5htm^A~0xhfL@q;S3z=j4U-tg2IIt;pVbK4^|(mjZ6
zvv6LDYd^m-Z(OG0id^B!_Rn+Ky&-4(%q;ePQxhb>G8$?VpQT=Yx_YFQPfy#*-8u3b
z?SCDv>VR{arpZK0EZt?WW_ZM#=f1>4Vgb2e>Z&RcrL1f_nyc>8h91RGL-Fhj}0+=bQ_so)6_Iqm({)e_KAF@!Ecqg+%FLoxtyB|
z4s?aD1MSVCFQ#G8bsKJRzk}5e#RaX$s)CiAf6hWt=ZLA3157W5Z&adUykt>Bzoj1T
z@A0YE&N<4q`gt$$>}!1XIE}j7+h6rB^VM>>NWh3C6&DoE$pk;$p{_$XPJAJ&iA<38FGkgFFwz5i)T42b3X=H@!St#X4238_!mhK>HkOUQXuFBp$ep>@$QpSY
z&(i{IZdkYkfra9XJGdwfl%X_#Mu94Y377DQu`?}{pzDudRGO(Ah+5!c-MJVVi~jb!
z{FS>>N|gKi_uGcb%F5QI45+i!&n4?D%;HhSx03PF26LRT{g?D)tdS-U@jrj?0k3-k
z+g;lM=j%$%(Gp45HT&h-<4yyHi^r*(kR
ztutij;P~LCpSGy*EHj=U7?s377N@PC=|uzLLiWceS_El*SW5HL@!7!p>8Fq;ukt;(
zH9rOl1N=eItJn-?fl{Pj=PkImIta6``jgR$l&e@ep&tKwno&s*h=%c_wiTCHdH*4x
zxc~}FD&5})p+_;=hiJAj&eKgS5dUrIQipGV9M6YK97Vv
zS@j-!YD0&BKkj&B0@C2NZyE$yWe{KBqOH|#U@fF^d-SL?j!6vq?U1wN
zvilU!I!)TXcwt^`>WlR-b_z$s4N$k&Cly!p0;`I1!~xYRoP^h)g6Mn4Fn$s|jR{)%
zmZsCo_*3CbCP0X4uQhKYp~rg+PcH+E1L5M$ZAjrao_kK!SC?vIp8{aDD?x?JAa}YR
z-XjO~JgrBSl@$eH{D)HzksdDy1Wcfk6@^$%QPB}x(M{iu*2i0t(ty8}_}4y~Ru*(D
zqCK1JfWi+S!r$jK>($^!MJM5(7mzYU>!NUE$5vqQq@}By5EW&25a5?570P$}=FM=&
zUJ5U8BH`ZwkH5iDo%b;O?z=5MzFNdhZ^Sn2a%2M5F*`Xkri#LUWZ2ccGBcodEO-CS
zul{>`8ln*k9tqaexK5FMWLLsep
zXtLCs4OIv_|Jl?6GLZd)&E31EsWra7(s%ATF+10d--gitiIJda`<6A9Zd20!&;j>b
z4p?M8FJu=g|1JxfFbn~2iXCJY=w6ocJJdA^xD@3$?R%lmhV&qtcIY_fFsS4*pkYu5=gA
zyxsamkeVaOrv9F`sk}U1?Txsgs@q7Hx`|ED1-YA`daBjaeERh6%hh2(f)suDkh=}mfqefj{ZL(4IF_fq-!*(&2~9)K
z@3yw^kHq&ldL25Trrw}7J#PvIk_JgRP*g}rNi95y<=MOX`gEQ?B_km*kC0-8idgQg
z?g)Jq=9kn5?iw>*E!64^P2c86nP`~s!gvt+5JoRzr;;FXP_m&m@B*3Fb!SJ~f=Nli
z>Sho5Cy=x`iu?fduon{@BP=AG_OEMW6DfCwEr;N33eszyh@8}ZSN28*d{9@&PY#$w
z>&mWwV?W-2X3s~5nx_B3gR+r7D@faitl};~Q+LiUk^HvgTCfJ^C%uKQuVffWNb7~U
zVT=qvJV@Y2bBHI%v4ppdJGgh}jxA*_zNq#^HM&SqR|s8tB1E+x1Os~lOzKX&rc_*<
zlvm=7-~1l(|Gfyt{3^IesTJIe5i#*$CW3uYv_k
zB7N1`BywTuC5A|fC`|B`FJ?W%)64zV?W^-dZ_@8Q>%CKR*s0-_C&B}Nmb95;)b+KAW~p!Qd#`Dqj?uo&
zxNE(KGO{i~wOg(Rz9+w|y2TNGXYFzQvZw2y29>OB_Y|Rlb!i5HT==ZLck2Yr%`Kq0
zr9AVSKMl^!d0eEPdyrt|?9lDf9GaJB`%!ATCcFuJFd37R5L*Bc83pZPH8RY!@!I>pVUuLi2-3abp`p+ZrTI)j7XZ2A
z8aPS21n%wtjBxtA38br_q^PF7stp&G2tQyENS5G(tjdfeo_*>NAK1ieS{kb@Xu9|y
zdwOM~B;WP-;^;9SzQ%(G7j=BVh$+tcBL0AmiD_+po$TEd^bX*`26>~kwUwR+k}5n1
zVLo{XV&F!1IE}v=KBabNj!S5CGVzDTK|M@oi&a7XR%VzjgGjSF4+F53=M%oH$xrb23JLEq_gSN%dFDkb5WC_@OjQV3l)Pn(g^Ll@2my=ohyv
zRGh{m49w1#dee_;N*DlTllt50!Gnr7wCY(85m^qsgmf3ky@qWTKRqjRb>)ucy2vH)
z69Sy@*KH@J>dhC0UknYI$;M5V{4a;XopAHRhwWvkmN4Mil70vFB9XgyAGXD_$i=$}
zR5GB{R3D#!#{Bxt_S~f+{4CpibYbC#ujtYXwKsdfIZpgF&RUW~>>?5^|1?KzJ@P!H
z8S=@g4*yvby)*APO99}I8)$;zsXr*YibqJSQn#n%8g{gLr#B
z%{z)7AZ2nCf890&TUK&v>dMIW0kEA=V3abwG&(ZUlo8dZiVcK1RJ&@fMt{LS47(-f`*(a5v5llD$MOp)GF)nt1U;^Hs{u%!#a9Zhya20Dur+s5TvWyWzHWlV
z?kp0Mnek>9_ojkzxgmzs>)njsfI_>3$<^ZRLJ%<^*#am)8Wx%si%vZ%OH(Xhh3!FP
zfPnN}L6Jq#U*I$qU&U1>u7|vPQ#o|U8{ejCB|fj5?_qyCQ?q7e{VzYq$Ui&zS5Fu~
zo$_Dn0{jKW>d@xl;J3m79k;okrt<_xZATI?+9O7JH74qJV@uzp-
z94sJuXxlH%TXpP@jwQ3DjREn!RA{2LYHq
z;VUe0rI?M+DyQALj-(awt6`iNxd8TjXQS2U50qH*p~ceSaO`auD=*SCGK%$-Q;jN%
zQI8C1mcM>IA62Bza@xVR{REy<0WauBD!Mty0PbrkE6iKYjkCX8@#t$a#vtE^2HmH=2&1QL*?RXQ{-5Jz7E1T;Ux2Ws{xd6k8!-orODgL^
z5)UEIslr23FV%qeQLP0x^w8kGS-zu}gIFS?BMg3FDhTkdN=Gy+BVGGKYXaPr<~)6N
zFXV{?ZMSAh13KbCzG_)0|M$#8_Docif3u&M26`CX;n9u3>)5uCx;|&KJ{%JUBqewX
z&5U{`p#oD+6_|y9XPvc0i-&~Mv@><;-#mpFfuZY43Fft?g*{gT3bAKL@OC8T#vz!f
z8LGjv=DFqY-zU1umti)`0@Jj0GHK%w6G9|91k^yFIpyQC@C!t;lz{NpJM1DwJqMG`
z&LzxMm{hN<*lrdX3XVXA$eRRyzc83s;HOH0HY(3G_z{3}m-(r7;cs#Hwe4h<^YLRB
ze^+`Vi58$z$bk){soeL(!uU1XQv-g_T;fm7D#gP)l_Clu9BQmnB4JF;EiCQAknm;H&wRd;j)2z
zW1C8fD7s<=qj&kux=I?f7w6Wd7Yg693EHB3wq}SSMQiJq@A`CVK!coGr^>=`O7R^Bys7Y
zXYlk?pHF{nQ%%x-GK2F%SnCXf&HZo#o$%gea|fEerrBJ>o*R78L5=r-u;59!i1+7}
zq74xE?$R<6=i5K`fKvHwa&jKNQ>kW;aPs6m*S)>HapvU}=&Q+2w
zUAy!biUlyrfc9f4gilCVuCmLRQz9-2blS*+jEs!Qs#g#bBN}xC1BR$32o2z?giolF
zU6f8os?r+yB-d&JOux$*4G!E(b9i*@F|7(_tRc{P9;R&f-13Ejo_{RVUi|&{!P=>cE>hV
z)7;b_gW}=Z>hsdl!3x$w?AxIhl^HYo7Cr1XyfmrNehRK7F8J2L`|UUPXtFf2;mnmv
z*=ob!tWgjc^zXN7CdZup=#WkG&Ga~>^%kp)!4nDbksS(JEj_SLMJ7~#owNv
z{&A5PZ+iXh>({BgK;0jV!3TyJXHWK`_l^CLD-u0U!;k4+QHi<#~2ZBP`-t&nM*Jo_TwLbHI
zG)#ig*eu3zH)d`l-t@%LN^PTjW#OW(Q@=LtFXTXEzkgkM`5u^Wp{sJ9s-b0J$xMdtTZdr2-hG*(lBiO})|PwS
z7S;)XPZs_l5Kk(RNZ_#Cmw?XWK}>aNX=3fMI$|Q=k(wHSx4|&(aOXo8%x6YBcx=H8
z4VG?`@0L+jpto5q`5738=jP7NwZ(wOHa@F&E?@cRd==RiI!IZGQAR@`~sC^D_;o&6x5l{tiWXJB1gC-e+I~`v7FOl;HW%)8p8+Z{hkax@v)DkPJciGtqGIiZ&haH4N
ze_v2z{0mI!)IX((+_xzyIDEt*&Uqzq<;v9c)zvkx^)c$JS35QfA2LDyks#96&29I8
z`Rk4Kb%^9upEHHfZNujdca;;6D{4f&k`UdADJfo%?Wp)&eUJ}kAOQhQ$jQ6EO-g#e
zRP*`YdB}LO?r((;DfpaphemC^w?2K}QIG58{rbtSH~%YGS^yy+0q>_@rX$cz;Kzam
zmw>6)>Iz>vTq7_n1^VM55ei4oZNToT2n(0Di>bTPL&$#*1}lH@QRGBK^l&MGKkNOG
z;qWYUJ1|>ccTu{giAaY~`24zzuEHZ=eukxf)Yg(PIdwI%p6-hg^X4qdS;;C}=oy)~
zptasGQLn6mQ>{#W6$!qzz|Z3bNlf$%61X|*PLC@t>`wgFGB5z_Zw<&A0Rd;=P0Pwk
zvULZ!8D_p6fGNUKE4!TfqN=+3Lt)`AGf^iUGjnVv
zGXns7q77U}X%)?y;p`7nS-2M5Jr3iWM}ow`Ea|ZVg^U2L)SQW?Y_d5F$6=F-C=xwa
z^`Hwx#)q?da!@;fWLE4BYGL_h_Rq!t{ahZVQlilg9F9(c;a`wsC_GQ5LphA3bi7q?
z=Z;cF&+$@-r5=DdVR#m+8big5YKyMeAu;~Kzi#Zf{4rIAOr>~vJ|lz~TqZbl$=iE_
z-!+A@qBQG-o;~*aH7l&Dnt}@3KVQ(Q+s)RLuY13JzIT_FTmqd)IH>uDHtS&%DF#?z
zWVNTB7A^*0QkC;ur>77kiQc3E?*k}2&XZ)<3@#iyTDYt}5H^OJ6DW~*1673LLV!7q
ziH^<_BpN(P_Qm
zof*HSD1%aQl9_OBO2&3mv4B>r?$%DPX{JT3t-U=`_l|jF8jMR}mKc^9
zt>#NU)&zf_4ACl-f;d7ibUr=lVj9NAnM0wv+S=uy+`~Bckx~{U>6?B+)}B&1bgHQ#
zQ3zxd*jXZcQ(RI~euKTZxFwqQ_95_|K+J-vHBMosl2{7l1{=0!FBF?|$dZyRXkruO
z;h}$J{yGqL;DALrT-05M$RF(4Zs4kbSwHN)(XaOvNeV9W5MUwY<9eotMqaDFyV*Iynw{RrT?!xvC
zz@9L6$4E46nlNn}g3`##BQ^P&C>~w7c$H1GwquB$u6ZnPIWeRAcRn^P{6hzCh7V_v
zt(Iy^t+@5+&i%mNzo%!V(`f(mzbO~fR*vRNP`qeag*oY@js7zd6YPmn_SP%6xftqs
zf`1b3+i22`&BTmbUxgpc3KglU-*ZB-$epFj6}tVj6DrIcV7lvisEg9b@P8O;^ERjr
z(t7u!)TBR-Of}lEq<9)_yLiGiBO5$A29K-c{-DS#xMB(K?t=)MOK!V}+B_2k0v{A9
z@MJstON;{k!g8fYuMNaJV+0Kvdhv2&cEILj+$|HcRaV$=Ju3
z7}7l+o~2E5c-p}E58*Lbb>q?~B*rz1gzxwekV$2G_k7KwpbmrveDaHa`E$rF#l^y&
zfmjOI@e^Q|8ZeV>^wT0777!Cdy4v8!qai0Y9|4Tdqu`)4
z^$c-pUottR0D3P40&pjrwY-AA0%pWHoZ^w+0KfyL=S|t3Z9`SOcQ3uXlvtVXL%$cY
z(;UrFuV*>T(1v3Vigtgo`O*TQb<@{nQz|MdCSI*0!^5T@;eE$FpDtKYKxBs5qcKYvajDFGpul3J^1X&5*HlS7rM#s{-w_}|*t5BsZ@p)5}S
zA-d~KNOoNS8e?Z?SLLL{&0i$8ijwW^Gu4Ee
z1d)%H#{--A?vxi=kg=;!bdony#!qw|dPuU+ZNp9`heY>fwlv755C+!5HBON3|Bue8
zXHNrYum>Qr-Cq*?REF-$mdmcyE(4NU?A4^1{g`T4ghTYI>u(vE7dYTfKrDOv?wxCD
zqjTWthS-%zVY2xJwdNhe9^12%18$l(U9s}PE}hVVJa6!4h+;-r6?lQMJ<*VpE9lp4
zZtm?#)CTOtc|7yzM`&nE(1nYo6cSq>+nEHs7A8sKzOqVJo+eTH3eX&9_!faVdWJbGCtDpqlcM!xp0xQ2)vdU)81y
z&Lf@c59scC?T`+;^r~lMfV^++*Aw8bMeP!jSQzwoN=L-h2
z0#qQ(r3xhd@^rZ?SpWLY`2$B?7W7Lqi+eEnL@l1lw_y&ZE_bELu{=UD{#
zC2*uRoh|jG?SX*tVC4NiU~}{>tvT@rnn9+4nuw6Lv5z{%6n2$=ME2!+9ibV*x?FQ|fhXqI+jRy_E1t
z#6#f-MVyvG|6vu60fV*RaSk^nki1Ue-@x#3X~`cr>-&$Nt@G)qS
zr=Qp_i747WXhyz?{-jM&(Qd$yI05g#@yt+vL;Bq#=O|KV|A)ythN%J?l5_9Kw&acv
zQhB!OPM>Et$!W-X#tTR9Od!#S
z!mT-=xUBPDC+K6^bf=5%=5%MAMd-Kex_|-|ThZn|uHIpp@lmd?gl+FSl%>co`p`v7
zl?KK6@mjC}dPm$ny@I8Q6X(=~y&!OW#|sLB=wLd;6yIU-du&DE7l_gj?+!ti~s
zuBvj`B7<4C8|RH1_Yyezi=&`DAkjx50)!Ee0Mg%#C!0jn!t$sD*%Mp%p1Z44Z-0PP1)3g$ZbV%8yrA0}e!xpI?GotKsFwcW)`qkyCGdhv=3FH=RPVk|?
z-;|~gL;r*S&Bel+*A%Oxsv67U^c8JxY-R`t?|TbNR1n5d-F1AkTg->CRh}Ly1JZ7c
zZ{;nH+kx*mUoJbT^*pT;au_W1nm(VIa2=XSmbOTbwZXviW1qD%vt0
zwmZwMPa)9>*Qd`hL-%QH9=wvUkl>I;*q_`eF66@S@pHg?F7o3?tgeR{<^*QFg(mG+S5cf
zM5>e*zi?DS$yVuXi|f~ye*2Nif3cmNJ75HmKhhAS+n}#wgzpXz&
z>9Y^!$dHPj-W!Zw!@-JB9=mpS1d6U0@~m=IwIFPhxIK7cNek&m>@!&}_#$NSiia
z5}+<;la#WG^o+-g6AdQ-Iu=F8e908Y@ZX4g+V5dS>vJssGMEKY
zZsUpU-FCXL&S*!sZU!t~2>l_yM)P!t$Q@(tZI{Pb-kkd=@2<_qA!0Dv4|nD-m;@Y7
zY4-6M!SDNcE`882!TisW+=h%pS8}^^-sQ`v%zX1z+Vo$^h04o8DpKD{z*g}Wn;s?|
z{COQd5SL@Y8n>I0ob5ZKUvc&;s9m#te0CNbIAKjdft6)WB$UBIckhOE_?}|ezoDyg
zp`Uj>bnsNC_`ZYTv*x;X&Fz0C6V4ATEpqIQW34x+Hii}Rt1cp9Vq^r6rKYRc{c&NU
z<9_nVI-ex2KtBZ^g*FgUalsZkTGz{La7n(16QhiFDAj)0yM*
z_Jv2+85bRX+24Dh5B3Uhy|65W(jD^+3=Khi&dgu~mRALxgP;f9Pk9SpK~3ef$lcS<
zk!5To8%<{y!O<4$W$Er;mh2N3hN$Mbl<&CxG}A6=h)&7s`&M#zF`YJq1ofxV(NMVL
zYqOK6+d?OJZ+87fNYnw*CxO`jJGtN(35uM8;vaa~s%n{AHlg-4Tt?b*kU_;pYuX`_
z_Y#qwmIl{N4{+=tJnj#6vDA!XrHjbg_vz{L@4aW6FKwRRpAq|2jV_yXMUdv~KwGqa
zPe~qeTfEGuW!KEsos!GtUiSn!L-G5Y7|(e($CHn+my#^+?I4O>5#emW%6^o~}y
zDSo?#PQf_f42&ppr|ZI?{VqL+T@yIV&o_6&N{89Lan%AFOYnEq1NMsh(@vby6+K9>
zcvLO!7~X)uTguyHq0kMcDsS8^9^IYPM-z*dw|dahEFPstd-aZS^X1-D31L2&%%tgf
z$V}C^jeNp&+FW8ONqYLv!fBrv=(H>UU1+2$D@R6LEUo1kv<{ne9*nMs)C<&0d3n>@
zYHk%-KOnLP*@e7w^~zyqutO?5e3%;HXR?ee2A>S?o~0e`Vy8L7%B*pcO}|
zE~DBHX@=!?Q$HGCy4aM1!&Y6$Q)c!a{3(IS3A5)3=7J
zzXv4>dwa%W*uBBtZKimoFTevmipvbn&OrGtEMiZZi_FKmq8zx8P%xhE
z{|zN&=D)`sro3=ycmro92Qgvh-_`$q-shM^cRGfnVdnw76rNDr^!{d8TZP(0+~@zl
z1d3)|!0weMH#Z~w5?rO)@VxW6q3#`P-xM1+5(FNdq)T&;7y8^3^Xn_bB8VHXI$fCM
za3-|Rd1$V?4s3#&JDgzPA`jHBBtM+k>M-GA(OJ&Ye1z4RTRmIP6Y`|oY=_SodLs`r
zv8S9QB&2{7Bxnltar?iovU?gbP!c@74*`P2MN8}YVX`vdlxa(H7vmW5>PrT*0T<9p
z@vnG6QUPX(0fYyc>Z*_5LvR+1U2PjkV^)YG!(5@tYm2ou{j#HC=h^7c&>pk_w!;mB
zHl|q+TvSz8w~jc@|9~JB3(_*G^(6nbD~Y-UK~5I|K=4$03`Z;$UVUod&B=zO@H1Aj
zDtO>@+kO?0%G4MwV?z_|-xhNU>JrRZHo2)|IY+BqhV2fw?Ok%cf2hy+ZEL7s-HB)C
z*aS?2kVrA3tI14kY;smVue=4W?>zX-dq{PU?=)cG+b30)bz309{{^s-aAB3;
zkEQ*>PyW0>_5S>M0z!t_C-FJ35~n_dtm`w^G4ny7j1zCzj3&VL8PHLN6;TRWuy%-9
z%!&E%0xtz!wBLbSBd3d-8xCgszb;_u-CMRQw}_(qybc^M+>m+i117xp>N@!WA({Dq
zr(j9KbZjNzG*Hm97QesPI)n|C`N0x9QFFG1*q+UaDlh70WDlQk78HLlyPNn|1%0}b
z^or2+K!S!O3jG4TckA<<{n4fYfNW^ry@kavP#k^=!UYhl8ke*EWCMN{%L&31WXx
zsi*c!>Mz(**of1$K;2c;&kclQ1u$8-v1LeFyBJ=!OEC0xb>Y@QiJfdfcdUiifdf;4
z#1cWyL=e$>DMC4nFJBfq@19Xe;daF4tbw@EENMBK5F6VA3!*!^%E7(>%i!WBoV7Z0
z?uUXT(L*7I;k&_R-h<%_;-X}grZ>dzp8NZEd|?D%#S)eXX5chzb_8ij?S5kdoY1Gh
zuX@@sUi%(}-11iB`YLm09a(F5HP&68lVN#57_&biXqZrcI;&K&XW067{{0yOdoV>Q
zd*U<5*_V%Mo;A|`f+vgnYXtTO>J|KH|dOzFZANy->lB|7is
zeY9zu)uZ;ReZ0KN8&1G(ffxf=)avDKa8`PEUG9@n9p<s
zdZx}w@{Sx^6og>>eEeW*q3P4Tx;rW{#m<1aIr32&Nw6(USDVHJuBCGqw=#^W@{cMn-B`fR|te9Lv&fwPn&nb+8N
zsfWSgtV1KK%Fi1nspf9(q@)#g;H>^mdN^Tv1q?|nQ;%rL!bY9p$2AiHvp=VXon8p7
z;w?M;tG%!G>j~5vIV%bT#g&nJL_|SSq@o6
z38WZ9Dbe;5^@s(SR16Ggz6~GXo`C42d?N3
zRjn?8Xd)gUXm)m8iNrFqwR5ld?y)_<)1%c(1m%Czsvq_S{+yMK5c@{Sxu7ox1Dj(2
zB&2Op!pB(5gv_>h$>9#%OsUCj4RSK`vz$s*k|e^mSK;A1U!GH>{s8D0E9
zwqBCQ-s8an`0SAyi^+LH-65~XpdD$}Wo}H=w}T1&qF4}Iu?u@8a;)1UV=R|d#jGKT
z%jZkcpLBfk!aOB(Pl_>c^7-(y*KaehxCk$l)rs6y%m^@IwSuV~KsQ`A^FYuE`V??D
zZsQ`IrKLuYfR^vF?t6dGD~1+8kcz}b#)g$Ne|t7E3=20H(o=h~<#34JgUlu`X;r9YmwAobw;f%gfW^gT7>&~`^tBhsi!KJ+FAFfh3;yRJFxfc
zgX`>Z!Vje8sr;BKCAQqOT)ui(H--xz=4CP7_99ce{&MY~e&G?jcAg
zOhA2s2zjovY2&fO6HoO%$nz7D(QiXfMJ6P9f}6n_RS+c!`)C4Y3?dp5CZh@!`^OUy
z;3`X1y~m4Na(pcP;Y&}KoxRNw}q@6=u)W7`NiXaOXb{A#7Raj844`nQJ*!h@vU0Cl}w6e0}
z=8c@2z;or>(77c|RD=dK1*Y`7$H7DJ8K(-UN3FZ4*k+>T%V5p}{G7o$G+xDD2n+)6
zMBKU6@v68?ve@4vZVW*^XHI_p+}
zo1|RD3j)*I-oe*14leMC!h{t<=TS2lzDM16WM9lmD~-P`3g9Ix`#nG%)Bi2fTDgz!
zvPfHRnbH`Q3XfHdCPBOC>!Wy&
zbYE8QvrnAOSheYc0RWJC-U!pe@ALFP4Bgo3tti6Kd%97%F=18!hPgR0o6BJ-$fJY@
z5$3m2Z{+8L3J^T+y8Q9u*Gwn|0ehdy|1%Qgidc`$Iv<$$!1t~Lf*36Jp52^nIztnh
z$f01*JdP?Pz1iCesbuJ!JyDTF2xKk#nugnB5-!TTFLnO?)Ahxaj4=QSh-htv5P)#|
zx9a?gFRD;(#_t(&(sz&i{vC1AR4%tKLYgQSEsqn=(g-PzFF4v_T-MghMi4QD!W5pv
zNi0q{AQ)ueJRj=%>uoaimZod(eF~&Jtz`hQ3O1frXOG;d5q|ypHE?MFOJ@xArNJfG
zAq2%27^XA#GY;tVyvXo3OJ{!WGO#3XyE4xHV!<@B2;qE-L{B7*{*v+%9pc218sfDAs
zJot_BHX>?wGY<9^RGFvZ@-KLHY;xu_;iJNt1l|nX+yO%@?zsaMc3eV&zBT&EGwsmz
zS@UF2V6QxNhRw-|)2ICW86T^z3*RPXARwb}^f`0e8-%U2&jU3w|3L5q#*bi_b0NI3
z0Y7qF676on;NUSST|q&iTeL#XF1Ve}{w`-{pPfE^vDQEtroTR2&omO0<95n7Is#m*
zfc-H+aZ#?K;3Jny?PQ`CrV2X^&F=Qc_<#M)ORtDH~s0*;{Kvnvp+sH}9#M>FOx
zSXKrf$3PIErakX)h4niFwaL}m-OcUO^45q;V6v#xKQ$BT99A$mTS>^F#
zV5BUptN>JvuVZ+4A41jso3vqxU~l(?03vS9%>Vr&F2S-gCo^I&GhwGMcCq-KQ%eXX%zA6`zWha_@ey*EjT;l>_8S*EAo6#dowL
zKU_FG?`%oJkQ{EX=AqmQ;fuHLtE!T1dK|1iQ@>`UqN7s@gkk85I=lNLlprE+1>@M8
zA3kJAPij3is&hO&gj)fCDZ8;Rgg|CNle2!w`{dgOH~nNo0MqBs03NxZ(efmLL70vaKRODkl3+VRwG8sMfYVH`OQ&Z~;w-*JGnfazKW-kP>%PlN
z$%r1T-P#l2<=`nQ-5mKk#2@N|y7DlbI<$`xvjAr8KvvP%-ij8Exa988Bak5Tnh!YXf}ixWuO7Ls9=7hYrXBKbk%y@B~IvV&&jxu5CZYN1m(qyh9iPj0=fiI;93_O4T
zo^|`?YP@3c|B)oRr2s$#HR!(I}TS4YD{QKZ%nHM?em?c{FA0gw>
zBKG*Jv;XR400ky#S8!W%8~uCP)<@}k;B!8&fnt!d8kU>Wj<@fFk%)E|ePGdJyYn(_
z##Je;r)gdN7)KNvBGUsy#+7I@HW%2yEHPW3AbVVOo&vup3FG*Uw4PS*GBim?o*qhV
z5v8L=8Gu0&X;dAsp>KOn-oS40vs7^=c$D>*#>R|4d=hU
zfnm~STf^i`Hg_v=wjOo-FR35gBfX~HcOdOL;U$Mz87d(t+gZG~&=kgYxOuu!WtT4+
z)hlh+%9BA18h7%WolbH>Euv#SF1q40=Yh)ll~u6s>pg2h9Mug0QW_+IJ963i_?gV&
zlo>>(i3_ltGC1V(VCpAYt
zt}+Hxo2mE1Rxfk_E{l69B20iG^&atG1_o6QzJm#slsoRbcNx@99G|`XQ4vc7=?LD
z`*8Fqtlumq3_O?lxr`vE-G$4oxuUk!xva~`$Qb739MbaB*R{N{bWA5Ojs#K;)_Dik
z-RkR)!!i}ms>O1
z5_j^s-|K;2z!}RITAWpcP$NywcWsb?BqhxuFggS4+p};%?)=}mpu_M?*PhZhIf1|1
zY4CdFe$Nn+2yWft>_7Fy#-ds^_G0HKQV(HnL4kE|U$9vARwQ=s(G{7v5`D%0n=1LRUNmTX=cw{*F~uVMFj9r67?=P;(M{$eBc8^-%&GL}){|
zpA`DJBwaw4mzFl(06f{q;NZ@|0p#B9g@s2z)B-ppYb&dCSLm+UK)ZA^R6~9l7mH|8
zSJ8-=$)(a3E(dq$bb~t~ZfF>A@#5HNR=pobVlf#~(M<`Wy+mXr@^dfCiGb{33O7^}1D2B!y1j9RW=E7hJY`Ia>eIb=;l3WkpcY@~1B
zya5%@+{-ujp*OZNC&v_+6cC?S7hs#Y%gx2raeg-4UNPwGdT2i=_6VHG<_-?3#%~Q<
zLD7O?3D}C%*Wv=fdQ)lxR#SKA;$c?T{9zd^-12T0>%M*41RW4GlXVxu>z#;hP1xZ3
zUe`nJ#%4k01V>UW)f7YyL#~QpF=t9V$Bwlfs%^KarlRtGf_FeoJg3#?f{;Q=$GSEr
zVcb?#IM>^!9>0E*4y@>cFLGp?`@Riw8|~Fb?iKI$k3pp7+vL(Yd)C
zU;d8N>nkbgUE}?|_jhOsWsT2}q^p?<JL}_-)q6{PdZngAa_3`z#sy`{VCDEs
zBXFB+ID^&u(}W46T@vucS3}7#r!cyK0Rx1%
z)w2aH#uW=uk@3Zn!R>^%WH
zB22ijA<3ig1w$2I&LrmSR=Ckq{OMbJyvJNCaVljknv@Oxm9QECkj`r
z+sOzcjLJ&SHCdXeavazV?fGZuPskRMtm?*cijL)#w-1Y!Ulm!CKELvI$Il@V{e}o6Ky(`aaHQUL?VUvmCs$=
zJbdAAjtTJvKHML>mY*lS86D(q&f9TA@G4f3gzF;S0bq+DxGkZby^@+bStlKDAbfDY
zEQ8SvFDZw6Q&*LyGA4SPO^^M65PSN9b
z9$ubXT?n0}gjb6Ndb
zQW_6=Ow#*g9c@F>-c8v4J+Jgdim&v5_R1Bo0fc{YXAzU1Lqc0<8v+_i`gvbh=}*v-
zEYPMAh6+q)o)ERhB@WRHrd#5LIg9H8O@v^(76*(Z-k8~(nt(|l9IAfc;-+4N7ntO9
z6?U9{FE3A%##421*@nrh)be82Jw3p30?~ydOi-h3eP8WJUDK#y!{x%>_I9yzmA{r|
zgzrExUIwrL*5pS;n1Y9a-v>jE8we)I0s?%1PNbns4nWG4J3O_bCpctBTU(pq(~ZW)
zd*J<=olG-S^6;pDst3HwQmWg*X=&qt0GwZ6H$wmSb_>R49XogjR_;Xnupl6~Yo0p^
z)<0-zRYN!sOjhaXh5*EcYpwR&J_@U|LZsfK_rb1rXul|j>Q&I(r%CT$gI=x>6}r&2
z=)-X5l7h;05x$M6TB(1@Zy`PNY!=|#!QtU;(3~sA((erP#&HEME179gGv01Ku4Xse
zHmpFwYDx$t?u4q%g@Rjss@4m+xcDR|4&euzQDIVBfZLMbpO}%s%f1BD
z{Rn%nV15s+)X$&KJ_9{&i<1Q(SSSF3G<^EBb@NOW%U7G0x(vOoBfN7jh(FZ
za%Pfq9alujxX!ggT*{z;98L(lL;FPh=hA`ynAg%8m?p2m)+NyP1CJN4W{58Lq?Lo4
z8pM6r8Neo_s;t~3i*64jJGkOvYW@+jS#aiER@yo`4E6MwW&QOO727*I!Orwa;auDP
z@~&YnEPs>l4EbR7`SJIp|>@Can7LH89SMg6d0dZ}XX+O8-sU37O*Kr@Kpi-8+0C{_E(t
z2#hG^ASlL*!^E8V2NP;eitpU%0pzECj#Xb;)7>~Y_mGl)#|OQ7l?j$q-|BLem4|;>
zSP9X0MRV=I0ZAI=PB@O!G$(Dk$_T)SFH+R8Zn}l%;+EsbcZh(Og6j(o*N?}A{PE7A
zX$k!Yt@f?Wzkf6F{NP>Gf>1HUe`r-p>*^*@z#lVr?HwHC;Nkh!dGFY7Ibh}k1DnzM
zVP|7QNHR1vT>?zKueQoHkZkY@6vfdax_EJBHSNlUo$;G%%XdF?rQ;kJ8L^2*c|7kT
zWAx|`M7{6)X7#{<5?XMv)_R*pMmm1%zC)Gy5eRpf9)I1vWv9nYSv803m{$ihkBx0T
z!m#@hyd^6jb)N8kQQ%u`Elhd~I<3I|066X$A0JbX?p|)>W9V!hh2#mJpc{3$;N$w1PABK3kpuDS{{^clD~i
zC;frCvNFT!S0^-{LZ(a4ZTUTHOzocy-oGnnX2#j_Iyu>rYhzRzKk+S3)acl^rWQnz
z5)G&Jl1}m5B8%}<_AhxFFbNPX>YV94;4`lEr+}=
zsIY>!n)B64KO6BDxy3C{Z(~w2GMLxwe?r-jNe=2BHsX``w9-8wY2x)>2^F${+Bm3-
zig34(-M9HLdIrfG=x98IS=!~KlfB*4MH;^z#wK04!16e)eyYWHOz2bT+e^p|fFcvD
zk4#C9>k+}izP+eqIe}ry;}QAS7^7lYjg5_Y1e?+5E8)SSBF5a*?gF<$EhWRWztLVS+S?g@ocDk;70NSL|p2+8mw~0Z}Uk!gnQK
z(G8&)OmsTDf@5)z{6}qy%i|wEvfZD(#Uu`d(XyCh{@Zt}Vlk1P57Qrf>s@7C-X_8>
zluiA6T}$_>{v8v~C#?VhMi8x(p{#Y1%wdvl+v6`*fF^;&g;z@CxvWMsI202$*79Dz
z*6=mo8iIVeGb&|(OaL=lP&t2uhh8CuoyLO_t|Etb!CrNGdOGz6jx|CmkuABfiosib
zxTr8UcjD7cdMY`XsAJqfO6&@%d0l2vjIn5Lj}|e^m?kMD;y%
z9(nm|)nf~;5y(8N&7G#*zrV+IKBhVImsJlX5T&<=f2Bei=9Z+xeN*UK99-i0H8DWV
zAdAZb4(*V-0)R#+(*dYuP?+*yE{ENW@Q{=={_$$`$sm^#!j~Wp;y;S)WOlh4#zgwS
zyiIs5e}W~K*d78d4!=Ck4?z(uBFEcGqt^kxiHLf64c0C>yLP+6uEtwv8u}h0kVrSt
z)kToSG{FlB^gFH$?Dcv4ct`CDUZ2=776!U9$Z|_3RwVDATuQ6LlZ;pPs~2C9Xoa~h&i1+b__i^TH@m*7j4w?P@W!jCT_5jL!x}Y<-Xn7
z^z^dcLrq6Vxu3s=lap7sSiclgF`KUPoyj!YLZwHPhHpWC-nv|mA
zxSc%cWj|0t|9sHG53Oh1;|b5I=>Hbe}z^ve-xX0y%xl5{Q!N{g~de^
zPtvGIL|-&$7xJD)vS;2n%7Q)9Fywmh@RgL;QEzYF8a^Z+JZLl4^WE+33*bO_jA#Ot
zoQ5)2rH$2Ep0h{+M7uC@ChDTWi5-II`~ZVo^Y`2I_pbvSSc~%>Fav;J7?Nm`$3Rgh
zgwd2mVe=34`msZ@Kf3b=*}K7{$05ioQ#0~(kZneb
zg$?l0Upwg|)FgI#SXYRt3VbW5k3aj?*Ve&dAz^W1X~p*R`R=0v0(X(Xpz{=~+o1
zDUKSsvf8G|ow;XXA|m3&)$3X{e(~2N@5E@FlyriLX=%M11q@IHx%tSRY{>MZ
za$|NlD{I;-?wRRww7CQk>$>~f&h#IN$StU>D7V>|zrSp3XdGp24B)~QGtI*$n(S{U
zG>-cbh6V&^x7w6hH)+{tM
zUc;l=cP%?U-sg8@CoAq{1_lPrmFEH%GIyS)K`Y_+60Z@S{e5P-=CALMVgnH*Gi|!7
z#}lKjElio71H>04vKvlP`i!mRp?%$$w=1h$a{+aCFBrsUoGWa%Wdm$c4A@H=a5VsV
zgQ6oQGk)XOF>WZssF-MtnrL|DPh_z(?Exz6Ej13zIE
zIWFpOQxcLbkcQAZB{bmot)?F8AbP1czo09G=0LXLa3iMfC^wH6zujV>pQqdcok*g(
z3!6E5+^F5quT9IzF_Au;WuNOtfE+5Qk)Qv7|5owmqXtADOlT#UE>%^9R$1*N|C;pf
zoxc3K8iWt_Gz2M?OLeTbw6>~WyOu69f~H<3_~R=ZJSeQ&q3(d$^Fu~v^S>Kt_5)BO|||S9-cFRBE+_k*GVH4kdNu
zgis!kQn{IpQSbT7S0N~&R7Xsy;d+6VtAyLkjzg{x)$RE@TlR}FfP;lp&L3QBDKFm{@$=esaZKfa7eMO3jPb&*}{GbShI?-
z&>hI!B-y3Lor>RPnF6T6pJj(iBy|i=1EGXRmNYK9n>qEjgMyp=#B%Q2G5kxVC47
z`JSEHs_z9agM!7e2iGJI2db(xSpQ)nXZ)3JRD(vYv8835MKR_I5L_ySo(e2J4i*zI
z9(qE_T(^Em-}K}Rw|4G6XA$q`3FuGQ0td10CWY-P+K+-NJJO#T3)i=LzpkrN9tGEs
z0whbo^TU3B_kvBC8~lEtO?FejqZx_)CO-9fTL;z%-@ttc{5Fyw)}?7g|6t1?Dx
z0-PepcH}R$##~CXu?bs)h)xNn18V>ez^umaFV%R_!}$z%2SY?`STmQMO^*j$+nnh~
zy?lxey*hTl7BlYJLLG7$z1s4!3Vs9UUUbM&EDG3kPN+*m?5l
zsj2&22*3awBQ`
zB+B&-HpMD1Sr%tynF{O0fNSUtnJjqnfc^RHk+ldR
zi^JOLTCyA`&V;PCoZ3n4va*6qcx-}q2ROap2fHVo&$w0Y13M>6wAaQ?x+_2k2pPgn
z5>1p#Yy5CUa(L^3O{$E>bZsrgn_sMx-~(i)rCn$WVPs$WTvAd3f8F=O%cN0H0m7G;
zlRG_odh2qMa)7Qfw{5?WxQG0O2W|0_&tF~t%0xe|2*Noac}VpUUiSXdi`3CiT7kT#iLmTXjhAN?#3SZfPogA
zeoLC{$b%o282Uy?-BKbc;@FbJ^?S<4*bmKRS>scu(oh}(KOGS8&d806uPedP3MVAO>?DlOA4t9q)9^udfa`M%
zB(Ts^2D^@hF?}(LipjJ?s$*j_zPbN)6gdX?5IyN8QZI^2Je%~4T+SEX-y4qq47Fi1ny0#x;U?{v-&!k&ncZtju*UkadJ^=|}ySBGy*Y*bM)Nf0?#5W>lWVm8Z-Rqc3oqRg)NxijA*+u=9cx*K{
zH;K?_9ZUcYVI48pO`}h}6#f+j+q+yy!;DS2BLQ`&PB4SA&R@x~`A{Bw77kB%%ShOx3vO*L*Bdx{7
z!8yY9$65T;g{$~FVl=SZ#UDvBm>aAMosn6}*}nFUXj8a}I5t
z(n@5#b7vG}Drl)*dU~9PM+XH6BDy~{|6Zv&&GI*6ZyD(o-#~j$Ls+ykPmHjl0^bpP
zQKn^{>0