Merge pull request #6271 from MicrosoftDocs/main

12/2/2021 AM Publish

Author: Taojunshen

memdocs/autopilot/autopilot-faq.yml

@@ -13,7 +13,7 @@ metadata:
   ms.author: greglin
   ms.reviewer: jubaptis
   manager: dougeby
-  ms.date: 11/12/2021
+  ms.date: 12/02/2021
   ms.collection:
     - M365-modern-desktop
     - highpri
@@ -149,7 +149,7 @@ sections:
           |------------------|-----------------|
           | If I wipe the machine and restart, will I still receive Windows Autopilot?|Yes, if the device is still registered for Windows Autopilot and is running a supported version of Windows 10 semi-annual channel, it will receive the Windows Autopilot experience.|
           | Can I harvest the device fingerprint on existing machines?|Yes, if the device is running a supported version of Windows 10 semi-annual channel, you can harvest device fingerprints for registration. There are no plans to backport the functionality to legacy releases and no way to harvest them on devices running unsupported versions of Windows.|
-          | Is Windows Autopilot supported on other SKUs, for example, Surface Hub, HoloLens, Windows Mobile.|No, Windows Autopilot isn't supported on other SKUs.|
+          | Is Windows Autopilot supported on other SKUs, for example, Surface Hub, HoloLens, or Windows Mobile?|For Surface Hub, Windows Mobile, and other SKUs, Windows Autopilot isn't supported. HoloLens 1 also doesn't support Windows Autopilot. Starting with Windows Holographic version 2004, HoloLens 2 supports Windows Autopilot self-deploying mode with Microsoft Intune. Third-party MDM providers aren't supported. For more information on HoloLens 2, see [Windows Autopilot for HoloLens 2](/hololens/hololens2-autopilot).|
           | Does Windows Autopilot work after MBR or image reinstallation? | Yes. For more information, see [Windows Autopilot motherboard replacement scenario guidance](autopilot-mbr.md). |
           | Can devices that have been reimaged a few times go through Autopilot? What does the error message "This user isn't authorized to enroll" mean? Error code 801c0003. |There are limits to the number of devices a particular Azure AD user can enroll in Azure AD, and the number of devices that are supported per user in Intune. These limits are configurable, but not infinite. You'll run into this error frequently if you reuse the devices, or even if you roll back to previous virtual machine snapshots.|
           | What happens if a device is registered to a malicious agent? | By design, Windows Autopilot doesn't apply a profile until the user signs in with the matching tenant for the configured profile using the Azure AD sign-in process. For example, if badguys.com registers a device owned by contoso.com, then at worst, the user will be directed to sign in to badguys.com. When the user enters their email and password, the sign-in information is redirected through Azure AD to the proper Azure AD authentication and the user is prompted to then sign into contoso.com. Since contoso.com doesn't match badguys.com as the tenant, the Windows Autopilot profile won't be applied and the regular Azure AD OOBE will occur.|

memdocs/configmgr/core/plan-design/changes/whats-new-in-version-1806.md

@@ -125,7 +125,7 @@ For more information, see [Windows LEDBAT](../hierarchy/fundamental-concepts-for
 <!--1357346-->
 Client peer cache sources can now divide content into parts. These parts minimize the network transfer to reduce WAN utilization. The management point provides more detailed tracking of the content parts. It tries to eliminate more than one download of the same content per boundary group. 
 
-For more information, see [Partial download support](../hierarchy/client-peer-cache.md#bkmk_parts). 
+For more information, see [Partial download support](../hierarchy/client-peer-cache.md#partial-download-support). 
 
 
 ### Boundary group options for peer downloads

memdocs/configmgr/core/plan-design/changes/whats-new-in-version-2111.md

@@ -319,7 +319,7 @@ Starting with this version, the following features are no longer [pre-release](.
 
 Similarly, the [Microsoft Connected Cache in Configuration Manager](../hierarchy/microsoft-connected-cache.md) is now generally available for production use.<!-- 10735017 -->
 
-<!-- For more information on changes to the Windows PowerShell cmdlets for Configuration Manager, see [version 2111 release notes](/powershell/sccm/2111-release-notes). -->
+For more information on changes to the Windows PowerShell cmdlets for Configuration Manager, see [version 2111 release notes](/powershell/sccm/2111-release-notes).
 
 <!-- Aside from new features, this release also includes other changes such as bug fixes. For more information, see [Summary of changes in Configuration Manager current branch, version 2111]. -->
 

memdocs/configmgr/core/plan-design/configs/support-for-windows-10.md

@@ -68,11 +68,13 @@ For more information on Windows lifecycle, see the [Windows lifecycle fact sheet
 
 - Support for Windows 10 semi-annual channel versions includes the following editions: Enterprise, Pro, Education, Pro Education, and Pro for Workstation.
 
-- For Windows 10, version 1909, OS deployment media shows the version as 10.0.18362.418.
+- OS deployment media shows the build number from the base version. For example, `10.0.19041`. When Windows is installed, it applies an enablement package, which updates the build number to what's in the above table. You can use the revision ID to distinguish the media:
 
-- For Windows 10, version 20H2, OS deployment media shows the version as 10.0.19041.508.
-
-- For Windows 10, version 21H1, OS deployment media shows the version as 10.0.19041.844.<!-- 9504158 -->
+  | Media version     | Windows version          |
+  |-------------------|--------------------------|
+  | `10.0.19041.1288` | Windows 10, version 21H2 |
+  | `10.0.19041.844`  | Windows 10, version 21H1 |
+  | `10.0.19041.508`  | Windows 10, version 20H2 |
 
 ## <a name="bkmk_arm64"></a> Windows 10 on ARM64