3 ms·
Bonus points for a non-unique UEFI UUID that is already enrolled in some random company's Microsoft Intune / Windows Autopilot instance so when you fire it up o
by kotaKat 1y ago
Bonus points for a non-unique UEFI UUID that is already enrolled in some random company's Microsoft Intune / Windows Autopilot instance so when you fire it up off a fresh Windows install it begs you to sign into $RANDOM_COMPANY_WITH_BAD_IT_CONTROLS.
Triple-points if the vendor includes a sticker telling you to complete Windows OOBE without connecting it to the Internet to avoid this.
- snickerdoodle12 1y agoI still can't believe that microsoft allows companies to essentially brick machines they don't even own like that. Seems criminal to me.
- dylan604 1y agoMore criminal than hard coding UUID for some other device?
- snickerdoodle12 1y agoYou can do whatever you want with your device. Microsoft is also doing whatever they want with your device.
- sweetjuly 1y agoIf the OEM hadn't messed up and reused UUIDs, it would be "Microsoft letting companies do whatever they want with their device", which is not unreasonable. OEMs reusing UUIDs for some ridiculous reason is breaking down the chain of "whose device is it".
- shakna 1y agoMistakes happen. It is inevitable at scale. So maybe we need softer recovery processes?
- AnthonyMouse 1y agoForget about the OEM. If you find out someone else's UUID you can spin up a VM with your UUID set to theirs and then add it to your system and brick their machine?