You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
description: Understand how Windows Autopilot deployments function when you replace the motherboard on a device.
4
+
ms.prod: windows-client
5
+
ms.technology: itpro-deploy
7
6
ms.localizationpriority: medium
8
-
ms.sitesec: library
9
-
ms.pagetype: deploy
10
-
audience: itpro
11
7
author: aczechowski
12
8
ms.author: aaroncz
13
9
ms.reviewer: jubaptis
14
10
manager: dougeby
15
-
ms.date: 10/10/2021
11
+
ms.date: 09/23/2022
16
12
ms.collection: M365-modern-desktop
17
13
ms.topic: how-to
18
14
---
@@ -24,17 +20,17 @@ ms.topic: how-to
24
20
- Windows 11
25
21
- Windows 10
26
22
27
-
This document offers guidance for Windows Autopilot device repair scenarios that Microsoft partners can use in Motherboard Replacement (MBR) situations, and other servicing scenarios.
23
+
This document offers guidance for Windows Autopilot device repair scenarios that Microsoft partners can use in motherboard replacement (MBR) situations, and other servicing scenarios.
28
24
29
25
Repairing Autopilot enrolled devices is complex, as it tries to balance OEM requirements with Windows Autopilot requirements. Specifically, OEM requirements include strict uniqueness across motherboards, MAC addresses, and so on. Windows Autopilot requires strict uniqueness at the hardware hash level for each device to enable successful registration. The hardware hash doesn't always accommodate all the OEM hardware component requirements. So these requirements are sometimes at odds, causing issues with some repair scenarios. The hardware hash is also known as the hardware ID.
30
26
31
-
**Motherboard Replacement (MBR)**
27
+
Starting in the September 2022 release of Intune (2209), if a motherboard is replaced on an Autopilot registered device, and it goes back to the same tenant without an OS reset, Autopilot will attempt to register the new hardware components. In Intune, you'll see the profile status **Fix pending**. If the OEM resets the OS, you need to re-register the device. If the new hardware components are registered, the device status goes back to the assigned profile. If it's not, you'll see the profile status **Attention required**.
32
28
33
29
If a motherboard replacement is needed on a Windows Autopilot device, the following process is recommended:
34
30
35
-
1.[Deregister the device](#deregister-the-autopilot-device-from-the-autopilot-program) from Windows Autopilot
31
+
1.If the device isn't going back to the original tenant, [deregister it from Windows Autopilot](#deregister-the-autopilot-device-from-the-autopilot-program). If it's going back to the same tenant, you don't need to deregister it.
36
32
2.[Replace the motherboard](#replace-the-motherboard)
37
-
3.[Capture a new device ID (4K HH)](#capture-a-new-autopilot-device-id-4k-hh-from-the-device)
33
+
3.If the device needs to be re-registered because of a re-image or will be used by a new tenant, [capture a new device ID (4K HH)](#capture-a-new-autopilot-device-id-4k-hh-from-the-device).
38
34
4.[Reregister the device](#reregister-the-repaired-device-using-the-new-device-id) with Windows Autopilot
39
35
5.[Reset the device](#reset-the-device)
40
36
6.[Return the device](#return-the-repaired-device-to-the-customer)
@@ -28,6 +24,14 @@ This article describes known issues that can often be resolved by configuration
28
24
29
25
## Known issues
30
26
27
+
### Autopilot deployment report shows "failure" status on a successful deployment
28
+
29
+
The Autopilot deployment report (preview) will show a failed status for any device that experiences an initial deployment failure. For subsequent deployment attempts, using the **Try again** or **Continue to desktop** options, it won't update the deployment state in the report. If the user resets the device, it will show as a new deployment row in the report with the previous attempt remaining as failed.
30
+
31
+
### Autopilot deployment report doesn't show deployed device
32
+
33
+
Autopilot deployments that take longer than one hour may display an incomplete deployment status in the deployment report. If the device successfully enrolls but doesn't complete provisioning after more than one hour, the device status may not be updated in the report.
34
+
31
35
### Autopilot profile not being applied when assigned
32
36
33
37
In Windows 10 April and some May update releases, there is an issue where the Autopilot profile may fail to apply to the device and the hardware hash may not be harvested. As a result, any settings made in the profile may not be configured for the user such as device renaming. To resolve this issue, the May (KB5015020) cumulative update needs to be applied to the device.
@@ -62,9 +66,11 @@ When you attempt an Autopilot reset, you see the following message: _Autopilot r
62
66
63
67
When a device is registered in Autopilot and no profile is assigned, it will take the default Autopilot profile. This behavior is by design. It makes sure that all devices that you register with Autopilot go through the Autopilot experience. If you don't want the device to go through an Autopilot deployment, remove the Autopilot registration.
64
68
65
-
### White screen during HAADJ deployment
69
+
### White screen during hybrid Azure AD joined deployment
70
+
71
+
There's a UI bug on Autopilot hybrid Azure AD joined deployments where the Enrollment Status page is displayed as a white screen. This issue is limited to the UI and shouldn't affect the deployment process.
66
72
67
-
There's 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 shouldn't affect the deployment process.
73
+
This issue was resolved in September 2022.
68
74
69
75
### Virtual machine failing at "Preparing your device for mobile management"
When you register an Autopilot device, it automatically creates an Azure AD object. The Autopilot deployment process needs this object to identify the device before the user signs in. If you delete this object, the device can fail to enroll through Autopilot. If the device is registered and not enrolled after 180 days, you'll need to re-register the device to complete a successful deployment.
44
+
45
+
> [!NOTE]
46
+
> Don't register to Autopilot the following types of devices:
47
+
>
48
+
> -[Azure AD registered](/azure/active-directory/devices/concept-azure-ad-register), also known as "workplace joined"
> These options are intended for users to join personally-owned devices to their organization's network.
52
+
47
53
Once a device is registered in Autopilot if a profile is not assigned, it will receive the default Autopilot profile. If you do not want a device to go through Autopilot, you must remove the Autopilot registration.
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
+
20
26
## Updates to Autopilot device targeting infrastructure
21
27
22
28
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.
## <aname="bkmk_improvements-to-the-console"></a> Improvements to the console
12
+
13
+
<!--14908615-->
14
+
15
+
When performing a search on any node in the console, the hint text in the search bar will now indicate the scope of the search.
16
+
- By default, all subfolders are searched when you perform a search in any node that contains subfolders. You can narrow down the search by selecting the “Current Node” option from the search toolbar.
17
+
- If you want to expand the search to include all nodes, then select the “All Objects” button in the ribbon.
18
+
19
+
For more information, see [Console changes and tips](../../../../servers/manage/admin-console-tips.md).
## <aname="bkmk_improvements-to-the-dark-theme"></a> Improvements to the dark theme
12
+
<!--15346075-->
13
+
Pop-ups in the Health attestation dashboard will now adhere to the dark theme.
14
+
15
+
Enable this pre-release feature to experience the dark theme. For more information, see [Dark theme for the console.](../../../../../core/servers/manage/admin-console.md#bkmk_dark)
description: Learn about new features available in the Configuration Manager technical preview branch version 2209.
5
+
ms.date: 09/23/2022
6
+
ms.prod: configuration-manager
7
+
ms.technology: configmgr-core
8
+
ms.topic: conceptual
9
+
author: Banreet
10
+
ms.author: banreetkaur
11
+
manager: apoorvseth
12
+
ms.reviewer: mstewart,aczechowski
13
+
ms.localizationpriority: medium
14
+
---
15
+
16
+
# Features in Configuration Manager technical preview version 2209
17
+
18
+
*Applies to: Configuration Manager (technical preview branch)*
19
+
20
+
This article introduces the features that are available in the technical preview for Configuration Manager, version 2209. Install this version to update and add new features to your technical preview site.<!-- baseline only statement: When you install a new technical preview site, this release is also available as a baseline version.-->
21
+
22
+
Review the [technical preview](../technical-preview.md) article before installing this update. That article familiarizes you with the general requirements and limitations for using a technical preview, how to update between versions, and how to provide feedback.
23
+
24
+
The following sections describe the new features to try out in this version:
For more information about installing or updating the technical preview branch, see [Technical preview](../technical-preview.md).
39
+
40
+
For more information about the different branches of Configuration Manager, see [Which branch of Configuration Manager should I use?](../../understand/which-branch-should-i-use.md).
0 commit comments