Merge pull request #16311 from MicrosoftDocs/main

Publish main to live, Wednesday 11:00 PM IST, 10/09

Author: padmagit77

autopilot/device-preparation/whats-new.md

@@ -8,7 +8,7 @@ author: frankroj
 ms.author: frankroj
 manager: aaroncz
 ms.reviewer: jubaptis
-ms.date: 09/18/2024
+ms.date: 10/09/2024
 ms.collection:
   - M365-modern-desktop
   - tier2
@@ -31,6 +31,12 @@ appliesto:
 >
 > For more information on using RSS for notifications, see [How to use the docs](/mem/use-docs#notifications) in the Intune documentation.
 
+## Diagnostics logs automatically available in Windows Autopilot device preparation deployment status report
+
+Date added: *October 9, 2024*
+
+Admins can now download diagnostics logs for failed Autopilot device preparation deployments directly from the **Windows Autopilot device preparation deployment status** report. Logs are available for download in the **Device deployment details** when you select a failed deployment under the **Device** tab. Logs are automatically collected when an error occurs during deployment.
+
 ## Windows Autopilot Device Preparation Support in Azure China 21Vianet
 
 Date added: *September 18, 2024*

autopilot/dfci-management.md

@@ -8,7 +8,7 @@ author: frankroj
 ms.author: frankroj
 ms.reviewer: jubaptis
 manager: aaroncz
-ms.date: 09/13/2024
+ms.date: 10/09/2024
 ms.collection:
   - M365-modern-desktop
   - tier2
@@ -93,6 +93,14 @@ For more information, see [Intune devices and apps API overview](/graph/intune-c
 
 Other OEMs are pending.
 
+## Known issues
+
+### DFCI enrollment fails for Professional editions of Windows 11, version 24H2
+
+Date added: *October 9, 2024*
+
+DFCI can't currently be used on devices with Professional editions of Windows 11, version 24H2. The issue is being investigated. As a workaround, ensure the device is upgraded to the Enterprise edition of Windows 11, version 24H2 during or after OOBE onboarding. After upgrading to the Enterprise edition of Windows 11, version 24H2, sync the device. Once the device is synced, reboot it to get it enrolled in DFCI.
+
 ## Related content
 
 - [Microsoft DFCI Scenarios](https://microsoft.github.io/mu/dyn/mu_feature_dfci/DfciPkg/Docs/Scenarios/DfciScenarios/).

autopilot/known-issues.md

@@ -8,7 +8,7 @@ author: frankroj
 ms.author: frankroj
 ms.reviewer: jubaptis
 manager: aaroncz
-ms.date: 08/29/2024
+ms.date: 10/09/2024
 ms.collection:
   - M365-modern-desktop
   - highpri
@@ -41,6 +41,12 @@ This article describes known issues that can often be resolved with configuratio
 
 ## Known issues
 
+### DFCI enrollment fails for Professional editions of Windows 11, version 24H2
+
+Date added: *October 9, 2024*
+
+DFCI can't currently be used on devices with Professional editions of Windows 11, version 24H2. The issue is being investigated. As a workaround, ensure the device is upgraded to the Enterprise edition of Windows 11, version 24H2 during or after OOBE onboarding. After upgrading to the Enterprise edition of Windows 11, version 24H2, sync the device. Once the device is synced, reboot it to get it enrolled in DFCI.
+
 ### Autopilot deployment report doesn't support sorting
 
 Date added: *August 29, 2024*

autopilot/tutorial/reset/autopilot-reset-overview.md

@@ -7,7 +7,7 @@ author: frankroj
 ms.author: frankroj
 ms.reviewer: jubaptis
 manager: aaroncz
-ms.date: 06/19/2024
+ms.date: 10/08/2024
 ms.topic: tutorial
 ms.collection:
   - tier1
@@ -30,7 +30,8 @@ Windows Autopilot Reset takes the device back to a business-ready state, allowin
 
 The Windows Autopilot Reset process removes or resets the following information from the existing device:
 
-- The device's primary user is removed. The next user who signs in after the Windows Autopilot Reset will be set as the primary user.
+- The device's primary user is removed when a remote Windows Autopilot Reset is used. The next user who signs in after the Windows Autopilot Reset will be set as the primary user. Shared devices will remain shared after the remote Autopilot Reset.
+- The device's owner in Microsoft Entra is removed when a remote Windows Autopilot Reset is used. The next user who signs in after the Windows Autopilot Reset will be set as the owner.
 - Removes personal files, apps, and settings.
 - Reapplies a device's original settings.
 - Sets the region, language, and keyboard to the original values.
@@ -46,6 +47,7 @@ The Windows Autopilot Reset process automatically keeps the following informatio
 - A provisioning package present on a USB drive when the reset process is started.
 - Microsoft Entra device membership and Intune enrollment information.
 - System Center Endpoint Protection (SCEP) certificates.
+- The device's primary user and owner in Microsoft Entra aren't updated when a local Windows Autopilot Reset is used. 
 
 ## Windows Autopilot Reset requirements
 

autopilot/windows-autopilot-reset.md

@@ -8,7 +8,7 @@ author: frankroj
 ms.author: frankroj
 ms.reviewer: jubaptis
 manager: aaroncz
-ms.date: 08/22/2024
+ms.date: 10/09/2024
 ms.collection:
   - M365-modern-desktop
   - highpri
@@ -38,7 +38,7 @@ The Windows Autopilot Reset process automatically keeps information from the exi
 - Microsoft Entra device membership and mobile device management (MDM) enrollment information.
 - Simple Certificate Enrollment Protocol (SCEP) certificates.
 
-Windows Autopilot Reset blocks the user from accessing the desktop until this information is restored, including reapplying any provisioning packages. For devices enrolled in an MDM service, Windows Autopilot Reset also blocks until an MDM sync is completed. When Autopilot reset is used on a device, the device's primary user is removed. The next user who signs in after the reset will be set as the primary user.
+Windows Autopilot Reset blocks the user from accessing the desktop until this information is restored, including reapplying any provisioning packages. For devices enrolled in an MDM service, Windows Autopilot Reset also blocks until an MDM sync is completed.
 
 > [!NOTE]
 >
@@ -119,6 +119,10 @@ On the device where the local Windows Autopilot reset is being performed:
 
  Once the local Autopilot Reset is triggered, the reset process starts. Once provisioning is complete, the device is again ready for use.
 
+> [!NOTE]
+>
+> When local Autopilot Reset is used on a device, the device's primary user and the Microsoft Entra device owner aren't updated. Admins can update them manually after the Autopilot Reset completes.
+
 ## Reset devices with remote Windows Autopilot Reset
 
 An MDM service such a Microsoft Intune can be used to start the remote Windows Autopilot reset process. Resetting in this way avoids the need for IT staff to visit each machine to start the process.
@@ -135,6 +139,10 @@ To trigger a remote Windows Autopilot Reset via Intune, follow these steps:
 
 Once the reset is complete, the device is again ready for use.
 
+> [!NOTE]
+>
+> When remote Autopilot Reset is used on a device, the device's primary user and the Microsoft Entra device owner is removed. The next user who signs in after the reset will be set as the primary user and Microsoft Entra device owner. Shared devices will remain shared after the Autopilot Reset.
+
 ## Troubleshooting
 
 Windows Autopilot Reset requires that the [Windows Recovery Environment (WinRE)](/windows-hardware/manufacture/desktop/windows-recovery-environment--windows-re--technical-reference) is correctly configured and enabled on the device. Before the Windows Autopilot Reset is started, it checks if WinRE is configured and enabled. If WinRE isn't configured and enabled, then the Windows Autopilot reset fails immediately on the device and an error such as `Error code: ERROR_NOT_SUPPORTED (0x80070032)` is reported in the logs.

memdocs/configmgr/core/servers/deploy/install/release-notes.md

@@ -44,7 +44,7 @@ For information about the new features introduced with different versions, see t
 ### Clients are not able download content from CMG when branch cache is enabled
 _Applies to: version 2403_
 
-After Enabling Branch Cache on Primary Sites clients are not able to Download Apps/Packages from CMG. Clients are only downloading some part of the content like 20-30% then the downloading is getting stuck. In some clients after downloading some blocks of the packages from CMG the clients are looking for branch cache to download the rest of the content. None of the client downloads whole content from CMG so that others can get content using branch cache. The **CTM.log** on the client has entries similar to the following:
+After enabling Branch Cache on primary sites, clients are unable to download apps and packages from the CMG. They typically manage to download only 20-30% of the content before the process gets stuck. In some cases, after downloading certain blocks of packages from the CMG, clients look for Branch Cache to retrieve the remaining content. However, none of the clients are able to download the complete content from the CMG, which prevents others from using Branch Cache to access it. The **CTM.log** on the client includes entries similar to the following:
 
 ```log
 (CTM.log - CTMJob({63B4C4CE-2DC4-4062-93C7-E5019B3B6CE1}): CCTMJob::Start - State=DownloadingContentFromPeers)
@@ -53,7 +53,7 @@ CTM.log _- CTMJob({D21758B0-D895-474E-9695-1023A25A1770}): CCTMJob::_PerformDown
 To work around this issue, disable branch cache.
 
 > [!NOTE]
->Clients are able to download Content from On-Premise DP when Branch Cache is Enabled.
+> Clients are able to download content from the on-premise DP when Branch Cache is enabled.
 
 ## Endpoint Protection
 ### Security configurations removed from Intune