Merge branch 'main' of https://github.com/MicrosoftDocs/memdocs-pr into lenewsad-patch-1

Author: lenewsad

memdocs/autopilot/autopilot-faq.yml

@@ -17,8 +17,7 @@ metadata:
   ms.collection:
     - M365-modern-desktop
     - highpri
-  ms.topic: troubleshooting
-    
+  ms.topic: faq
 title: Windows Autopilot FAQ
 summary: |
   **Applies to: Windows 10/11**

memdocs/autopilot/enrollment-autopilot.md

@@ -80,7 +80,7 @@ For information about formatting and using a CSV file to manually add Windows Au
 ## Assign a user to a specific Autopilot device
 
 > [!NOTE]
-> Assigning a licensed user to a registered Autopilot device using Microsoft Endpoint Manager no longer pre-fills any user information as described below. Please see [Updates to the Windows Autopilot sign-in and deployment experience](https://techcommunity.microsoft.com/t5/intune-customer-success/updates-to-the-windows-autopilot-sign-in-and-deployment/ba-p/2848452) for details on this change. This change does not impact user assigned policies and apps which are still deployed to the device when a licensed user is assigned. See [Windows Autopilot for pre-provisioned deployment](/mem/autopilot/pre-provision#preparation) for details on this.
+> Assigning a licensed user to a registered Autopilot device using Microsoft Endpoint Manager no longer pre-fills any user information as described below. Please see [Updates to the Windows Autopilot sign-in and deployment experience](https://techcommunity.microsoft.com/t5/intune-customer-success/updates-to-the-windows-autopilot-sign-in-and-deployment/ba-p/2848452) for details on this change. This change does not impact user assigned policies and apps which are still deployed to the device when a licensed user is assigned. See [Windows Autopilot for pre-provisioned deployment](./pre-provision.md#preparation) for details on this.
 
 You can assign a licensed Intune user to a specific Autopilot device. This assignment:
 - Pre-fills a user from Azure Active Directory in the [company-branded](/azure/active-directory/fundamentals/customize-branding) sign-in page during Windows setup.
@@ -131,4 +131,4 @@ You can group Windows devices by a correlator ID when enrolling using [Autopilot
 
 After you have created a device group, you can configure and apply a Windows Autopilot deployment profile to each device in the group. Deployment profiles determine the deployment mode, and customize the OOBE for your end users. For more information, see [Configure deployment profiles](profiles.md).
 
-For more information about managing your Windows Autopilot devices, see [What is Microsoft Intune device management?](../intune/remote-actions/device-management.md)
+For more information about managing your Windows Autopilot devices, see [What is Microsoft Intune device management?](../intune/remote-actions/device-management.md)

memdocs/autopilot/known-issues.md

@@ -28,6 +28,18 @@ This article describes known issues that can often be resolved by configuration
 
 ## Known issues
 
+### White screen during HAADJ deployment
+
+There is a UI bug on Autopilot HAADJ deployments where the Enrollment Status page is displayed as a white screen. This issue is limited to the UI and should not impact the deployment process. 
+
+### Virtual machine failing at “Preparing your device for mobile management”
+
+This error can be resolved by configuring your virtual machine with a minimum of 2 processers and 4GB of memory. 
+
+### ODJConnectorSvc.exe leaks memory
+
+When using a proxy server with the ODJConnector service, the memory file can get too large when processing requests resulting in impacts to performance. The current workaround for this issue is to restart the ODJConnectSvc.exe service.
+
 ### Reset button causes pre-provisioning to fail on retry
 
 When ESP fails during the pre-provisioning flow and the user selects the reset button, TPM attestation may fail during the retry. 

memdocs/configmgr/comanage/faq.yml

@@ -8,7 +8,7 @@ metadata:
   ms.reviewer: crosorio
   manager: dougeby
   ms.date: 01/26/2022
-  ms.topic: reference
+  ms.topic: faq
   ms.prod: configuration-manager
   ms.technology: configmgr-comanage
   ms.collection: highpri

memdocs/configmgr/comanage/how-to-prepare-Win10.md

@@ -5,7 +5,7 @@ description: Learn how to prepare your Windows internet-based devices for co-man
 author: mestew
 ms.author: mstewart
 manager: dougeby
-ms.date: 10/05/2021
+ms.date: 02/16/2022
 ms.topic: how-to
 ms.prod: configuration-manager
 ms.technology: configmgr-comanage
@@ -77,26 +77,26 @@ Decide which command-line properties you require for your environment:
 
 - The following command-line properties are required in all scenarios:
 
-  - **CCMHOSTNAME**
+  - `CCMHOSTNAME`
 
-  - **SMSSITECODE**
+  - `SMSSITECODE`
 
 - If a device uses Azure AD for client authentication and also has a PKI-based client authentication certificate, specify the following properties to use Azure AD:<!-- MEMDocs#1483 -->
 
-  - **AADCLIENTAPPID**
+  - `AADCLIENTAPPID`
 
-  - **AADRESOURCEURI**
+  - `AADRESOURCEURI`
 
-- If the client roams back to the intranet, use the **SMSMP** property.
+- If the client roams back to the intranet, use the `SMSMP` property.
 
-- If you use your own PKI certificate, and your CRL isn't published to the internet, use the **/NoCRLCheck** parameter. For more information, see [About client installation properties: /NoCRLCheck](../core/clients/deploy/about-client-installation-properties.md#nocrlcheck).
+- If you use your own PKI certificate, and your CRL isn't published to the internet, use the `/NoCRLCheck` parameter. For more information, see [About client installation properties: /NoCRLCheck](../core/clients/deploy/about-client-installation-properties.md#nocrlcheck).
 
   > [!IMPORTANT]
   > Microsoft recommends publishing the CRL. For more information, see [Planning for CRLs](../core/plan-design/security/plan-for-certificates.md#pki-certificate-revocation).<!-- memdocs#1942 -->
 
-- To bootstrap a task sequence immediately after client registration, use the **PROVISIONTS** property. For more information, see [About client installation properties: PROVISIONTS](../core/clients/deploy/about-client-installation-properties.md#provisionts).
+- To bootstrap a task sequence immediately after client registration, use the `PROVISIONTS` property. For more information, see [About client installation properties: PROVISIONTS](../core/clients/deploy/about-client-installation-properties.md#provisionts).
 
-The site publishes other Azure AD information to the cloud management gateway (CMG). An Azure AD-joined client gets this information from the CMG during the ccmsetup process, using the same tenant to which it's joined. This behavior further simplifies enrolling devices to co-management in an environment with more than one Azure AD tenant. The only two required ccmsetup properties are **CCMHOSTNAME** and **SMSSITECODE**.<!--3607731-->
+The site publishes other Azure AD information to the cloud management gateway (CMG). An Azure AD-joined client gets this information from the CMG during the ccmsetup process, using the same tenant to which it's joined. This behavior further simplifies enrolling devices to co-management in an environment with more than one Azure AD tenant. The only two required ccmsetup properties are `CCMHOSTNAME` and `SMSSITECODE`.<!--3607731-->
 
 > [!NOTE]
 > If you're already deploying the Configuration Manager client from Intune, update the Intune app with a new command line and new MSI.<!-- SCCMDocs-pr issue 3084 -->

memdocs/configmgr/core/TOC.yml

@@ -285,14 +285,14 @@ items:
     items:
     - name: Technical Preview overview
       href: get-started/technical-preview.md
+    - name: 2202 features
+      href: get-started/2022/technical-preview-2202.md 
     - name: 2201 features
       href: get-started/2022/technical-preview-2201.md       
     - name: 2112 features
       href: get-started/2021/technical-preview-2112.md      
     - name: 2111 features
       href: get-started/2021/technical-preview-2111.md
-    - name: 2110 features
-      href: get-started/2021/technical-preview-2110.md
   - name: Migrate data between hierarchies
     items:
     - name: Migration overview