Event details
Sometimes when we send a device for repair, they replace the motherboard with one that is already registered to a different Tenant. I assume it was not removed from its last tenant when it was offboarded and the OEM reused the motherboard. Is there any solution for this?
I'd like to proactively catch it but it usually shows up when the user tries to enroll in autopilot. At that point, the new hardware hash needs to be exported. A ticket needs to be opened with Microsoft to have the device removed from it's old tenant, and then the new hardware hash can be imported.
Any way to make this less painful?
- Hung_Dang
Microsoft
OEMs are told to clear the Autopilot data from motherboards after they rip them out. One way to catch this before it goes to the end user is for you to boot up the device with connectivity, and check if there's an AP profile.
Or use Autopilot Device Preparation + the upcoming Autopilot Device Association feature. :)
