Skip to content

Commit 4ec096d

Browse files
Merge pull request #8506 from DYamadaMSFT/patch-1
Update windows-autopilot-whats-new.md
2 parents d7c6a99 + 0e9bab2 commit 4ec096d

1 file changed

Lines changed: 10 additions & 4 deletions

File tree

memdocs/autopilot/windows-autopilot-whats-new.md

Lines changed: 10 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -4,11 +4,11 @@ description: News and resources about the latest updates and past versions of Wi
44
ms.prod: w10
55
ms.technology: windows
66
ms.localizationpriority: medium
7-
author: aczechowski
8-
ms.author: aaroncz
9-
manager: dougeby
7+
author: frankroj
8+
ms.author: frankroj
9+
manager: aczechowski
1010
ms.reviewer: jubaptis
11-
ms.date: 08/02/2022
11+
ms.date: 09/22/2022
1212
ms.collection:
1313
- M365-modern-desktop
1414
- highpri
@@ -17,6 +17,12 @@ ms.topic: article
1717

1818
# Windows Autopilot: What's new
1919

20+
## Autopilot automatic device diagnostics collection
21+
<!--1895390-->
22+
Starting with Intune 2209, Intune will automatically capture diagnostics when devices experience a failure during the Autopilot process on Windows 10 version 1909 or later and with Windows 11. When logs are finished processing on a failed device, they will be automatically captured and uploaded to Intune. Diagnostics and logs may include user identifiable information such as user name or device name. If the logs are not available in Intune, check if the device is powered-on and has access to the internet. Diagnostics are available for 28 days before they are removed.
23+
24+
For more information, see [Collect diagnostics from a Windows device](../intune/remote-actions/collect-diagnostics.md).
25+
2026
## Updates to Autopilot device targeting infrastructure
2127

2228
With Intune 2208 we are updating the Autopilot infrastructure to ensure that the profiles and applications assigned are consistently ready when the devices are deployed. This change reduces the amount of data that needs to be synchronized per-Autopilot device and leverages device lifecycle change events to reduce the amount of time that it takes to recover from device resets for Azure AD and Hybrid Azure AD joined devices. No action is needed to enable this change, it will be rolling out to all clients starting August 2022.

0 commit comments

Comments
 (0)