Jul 13 2022 04:24 AM
Hi,
Our device are added to autopilot using the windows autopilot script since we don't have a MPC.
A device was required a board replacement. We disabled bitlocker on the device and replaced the board.
Since this is the first time an Autopilot device was required a board replacement we didn't know there is a deregister + reregister device process we were required to do.
Is there a better way to manage this without the whole process which also includes resetting the device?
Thanks in advance, Rahamim.
Jul 13 2022 12:38 PM - edited Jul 13 2022 12:39 PM
I also dive deeper into this topic but it is tricky because of the TPM to get this device to an reliable state again without a reimport of the hash and a resetup. (This is also the recommended way from microsoft)
@Rudy_Ooms_MVPwrite a very good blog post to describe this topic: https://call4cloud.nl/2021/12/married-with-systemboards-976-tpm/
Jul 13 2022 10:20 PM
Jul 13 2022 10:34 PM
Thank you @Rudy_Ooms_MVP and @Jannik_Reinhard for your reply.
In our case we have warrantied laptops and in this case (Luckily or not) the laptop that was required a board replacement was mine.
Just to understand it better If I create a "convert all targeted devices to autopilot" profile will this partially solve my issue?
Rahamim.
Jul 14 2022 07:21 AM
Jul 27 2022 11:20 PM
SolutionJul 27 2022 11:23 PM
Jul 27 2022 11:20 PM
Solution