Forum Discussion
The future of autopilot and motherboards
Hi, Would like to start a discussion regarding the autopilot cycle. Scenario 1: Imagine your device which is autopiloted and has the hardware hash uploaded to your tenant (tenant 1), suddenly b...
Just wondering... but didnt you get tpm errors /device id etc or ad account password errors when the motherboard was replaced? So wouldn't be better to remove the old device object (and intune/autopilot objects) at that time and reinstall the device? So the hash is also deleted when you remove all the object?
But again that's is how we normally do it 🙂
But again that's is how we normally do it 🙂
Rudy_Ooms_MVP Hi, of course I did. The thing is, the replaced motherboard hash is in someone else tenant which I don't have any control of. Since this replaced motherboard hardware hash is already in someone else tenant somewhere in the country I can't even upload it and re-install it. In these two cases I have had to inform the manufacturer about it and they made sure I received 2 brand new motherboards ^^
So basically this issue might get a lot bigger in the future since more and more people are starting to use Intune, and they don't remove it from their own tenant.
- Hi,
I know... normally every customer needs to have policies set to make sure devices are removed properly.. but I know... a lot of companies don't bother with it and just leave it in the tenant..
When a device is removed or something is replaced... you need to trash the old device id from your tenant..
Maybe in the near future a new option will appear to make sure when there is no azure id device attached to the hash for let's say 1 month it will be removed (or something like that)