No Hardware Hash for Windows Autopilot v2? Does it really work?

How does Windows Autopilot Device Preparation work without a hardware hash? He's the theory, followed by a demonstration of how NOT to use Corporate Device Identifiers!

[@bash-shell]

The fact that you are demoing a feature live for the first time and still post it after not succeeding shows you are truly here with community to teach and learn. Thank you for all your help and videos 🙏

[@DeanEllerbyMVP]

Thanks!

[@DoubleA-ARon]

Dean, the fact that you "do it live" makes your content the best. Thanks for keeping it real!

[@DeanEllerbyMVP]

Thanks!

[@jojoka74]

In my MS tenant the option "Manufacturer, model and serial number (Windows only)" missing. What is your tenant version?

[@IrlymMylros]

Thank you Dean for clarifying how to stop Personal devices from registering at deployment stage.

[@DeanEllerbyMVP]

You’re welcome. Now I just have to get it working 😂

[@jigsaw4770]

Thanks for doing a short series on this, definitely been curious about it 😁

[@yazza1989]

I ran into the same problem last night when testing Autopilot Device Preparation. Removing the Windows Corporate Device Identifier and re-adding it worked. It still seems a rather buggy to me.

[@DeanEllerbyMVP]

Thanks for the tip!

[@augareth]

This is saving me hours Dean. Thank you!

[@pa1089]

Seems the process does not take effect immediately but takes time as per one of the blogs but the setup looks bang ON. Thanks Dean

[@Karlmit]

This looks cool, some of our users needs to be local admin on their devices. Which meant I needed to set the Group tag on the device beforehand to get the correct profile. Which also meant that mistakes could happen where an device on the shelf never was assigned the correct group tag before being handed to a user.
This looks promising as the device can get a profile that is meant for that user :D

[@m02uih00]

I like that they are trying to move away from the hardware hash to Autopilot devices. But Microsoft need to give us a simple way to identify Corporate devices so we can make it fast and simple to implement. So far I'm not seeing any advantage over the hash. Also loving your videos and been a subscriber for a while, please keep producing this content 👍

[@Vejita]

Its an advantage when I buy corporate Devices, I need to check the order list any way when it arives and on there is the serialnumber and model.
So if I write am down I already got the list in one step. So when not byuing from a big vendor, that supports adding to intune directly its an advantage I think.

[@m02uih00]

Writing things down off of the box isn't really progress though is it, easier to make an error. Especially when I can run a command and import the hash directly into intune. Dean also made the CSV file and it didn't work so again not exactly simple and fool proof.

[@Vejita]

@@m02uih00 I´m just saying that it fits in the corporate process, that I have to do anyway. So now, that this is possible, it is much easier.
Is it optimal. No.
But at least progress. When you dealing with a media breach, like this one, then its hard to automate everything. So at least like this, I can prepare everything without taking a single device out of its box. And Corporations take sometimes a long time to ship every device. Its such a pain to unpack everything, plug it in, get the hash and repacke it, so it doesnt take up to much space.
Maybe it is different for you, but there are positives. Try to change the perspective and maybe you can see it.

[@Karlmit]

It saves time! You don't need to open up the device and run a command on it. Purchase 10 computers and just upload the CSV and the devices should be ready for hand out.

[@thepete1338]

Was it the same image in HyperV as in the last video? Quite not sure about the requirements Microsoft wrote on MS Learn about specific OS versions including certain KBs..
But again - thanks for the content. Always a pleasure!!

[@DeanEllerbyMVP]

It was the same ISO, yes. W11 23H2 May update.

[@hoptop77]

I don't see much point in this unless theres an easy way for suppliers or engineers to upload a corporate identifier. It looks kind of like a rebranded policy set.

[@ulrikboesen]

Could we not rejse the list we already have in Intune?
Do a export from the Windows enrollment. Clear the CSV and import it. 😊
I have not tried it yet. But maybe work

[@summoner2100]

Perhaps the identifier needs time to "bake" and it was a little short? Um, don't vms also regenerate serials on rese? Potentially sysprepping took the serial to being different? Good video though.

[@DeanEllerbyMVP]

You’re right - I didn’t really give it “cloud time” to set.
The serial number stayed the same, though.

[@summoner2100]

So, it worked after the video?

[@fbifido2]

@2:39 - can we still use Hash ?

[@floriandaminato]

Why did I only have IMEI and SERIAL NUMBER options ? no "Manufacturer, model and serial" :(

[@DeanEllerbyMVP]

You need to look at the CSV upload option. That includes the Tuple.

[@CtrlAltDestroy3]

@@DeanEllerbyMVP I am looking at the CSV upload option and still do not see the third identifier type option either, please advise.

[@AndyGNicholls]

Nice, Dean. But am I the only one that thinks the hardware hash is much easier than this? I get what MS are trying to do but this is such a convoluted way of achieving it, and certainly more room for error if you're manually noting serial numbers. I'd like to think vendors will have a way of ingesting this information into a tenant.

[@Karlmit]

Since all the necessary information already is available on the box. Maybe they could add a QR code sticker to the box. So that we can just scan devices into Intune.

[@epic-buffalo]

Hardware hash also helps with theft. Doesn't it?