In that case, they should deregister the device from MPC, which also removes it from the customer IT Admin's Intune account. If the OEM or CSP partner registered the device, they likely did so via the Microsoft Partner Center (MPC). If so, they should deregister the device from Intune or Microsoft 365 admin center because devices registered in Intune don't show up in Microsoft Partner Center (MPC). If the IT Admin registered the device, they likely did so via Intune, Microsoft 365 admin center, or a legacy portal such as Microsoft Store for Business (MSfB). Deregister the Autopilot device from the Autopilot programīefore the device arrives at the repair facility, the entity that registered the device must deregister it. Reregister the device with Windows Autopilot.Įach of these steps is described in the following sections.If the device needs to be re-registered because of a reimage or will be used in a new tenant, capture a new device ID (4K HH).If it's going back to the same tenant, you don't need to deregister it. If the device isn't going back to the original tenant, deregister it from Windows Autopilot.Then the following process is recommended: A motherboard is replaced on an Autopilot registered device.The OS version is older than the ones in the above list.If the OEM resets the OS, the device needs to be re-registered. If the device can't be successfully registered, the profile status for the device shows Attention required. If the new hardware components are successfully registered, the device status goes back to the assigned Autopilot profile. In Intune, the profile status for the device shows Fix pending as Autopilot attempts to register the new hardware components. Windows 10 21H2 with KB5017383 or newer installedĪnd the device goes back to the same tenant without an OS reset, Autopilot attempts to register the new hardware components.Windows 11 21H2 with KB5015882 or newer installed. ![]() If a motherboard is replaced on an Autopilot registered device with the following versions of Windows: The hardware hash is also known as the hardware ID. ![]() These requirements are sometimes at odds, which can cause issues with some repair scenarios. The hardware hash doesn't always accommodate all the OEM hardware component requirements. Windows Autopilot requires strict uniqueness at the hardware hash level for each device to enable successful registration. Specifically, OEM requirements include strict uniqueness across motherboards, MAC addresses, etc. Repairing Autopilot enrolled devices is complex, as it tries to balance OEM requirements with Windows Autopilot requirements. This document offers guidance for Windows Autopilot device repair scenarios that Microsoft partners can use in motherboard replacement situations, and other servicing scenarios.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |