Announcing Windows 10 Insider Fast Build 16257 PC + 15237 Mobile Insider
-
That means that the tablet could not be enabled for self deployment.
This is really interesting!
What prevents it from being enabled for self-deployment? Is it the non-numeric serial number? I noticed a few of the others posted earlier are non-numeric too.
-
-
And "your highness" was OK? If you start something, be ready to see it through.
I meant every word.
So did I. Clash of characters I suppose. Happened before. So first to apologise is myself.
-
What prevents it from being enabled for self-deployment? Is it the non-numeric serial number? I noticed a few of the others posted earlier are non-numeric too.
Yes, in my case it's my Dell Service Tag#. Very definitely alpha-numeric. I blurred it out, but that's what it was.
-
What prevents it from being enabled for self-deployment? Is it the non-numeric serial number? I noticed a few of the others posted earlier are non-numeric too.
In all my tests, missing serial like "To be filled by OEM" prevents the CSV file to be accepted, Business Store giving a not too descriptive error message "We can’t add your devices."
I've failed to register any device that does not have a clear, decimal device serial.
-
-
There talking to the OEM's
Registering devices to your organization
In order to register devices, you will need to acquire their hardware ID and register it. We are actively working with various hardware vendors to enable them to provide the required information to you, or upload it on your behalf.
Roy
-
There talking to the OEM's
Registering devices to your organization
In order to register devices, you will need to acquire their hardware ID and register it. We are actively working with various hardware vendors to enable them to provide the required information to you, or upload it on your behalf.
Roy
I can't see them persuading Dell to change their system of Service Tags to be all numeric though.
They probably need something better than a CSV to load the data, as it's probably not impossible to have a comma in the Serial Number, as it seems anything goes in that field.
-
![]()
Yes, in my case it's my Dell Service Tag#. Very definitely alpha-numeric. I blurred it out, but that's what it was.
The logical thing for Microsoft to do would be to remove device serial and Windows product ID from the equation; the hardware hash already contains all information required to identify the device.
By the way, for those of you interested in how the hardware hash (so called "hardware signature") is calculated: There are 15 different hardware IDs (hashes) for any Windows 10 device, Hardware ID 0 through Hardware ID 14. The HW ID 3 is used for digital licensing, and it is calculated from 6 different values ranging from manufacturer through SKU number (exact version & edition) to MoBo details. Lowest level HW ID 14 only contains the name of the manufacturer.
Hardware IDs for Windows 10
- HardwareID-0 = Manufacturer + Family + Product Name + SKU Number + BIOS Vendor + BIOS Version + BIOS Major Release + BIOS Minor Release
- HardwareID-1 = Manufacturer + Family + Product Name + BIOS Vendor + BIOS Version + BIOS Major Release + BIOS Minor Release
- HardwareID-2 = Manufacturer + Product Name + BIOS Vendor + BIOS Version + BIOS Major Release + BIOS Minor Release
- HardwareID-3 = Manufacturer + Family + Product Name + SKU Number + Baseboard Manufacturer + Baseboard Product
- HardwareID-4 = Manufacturer + Family + Product Name + SKU Number
- HardwareID-5 = Manufacturer + Family + Product Name
- HardwareID-6 = Manufacturer + SKU Number + Baseboard Manufacturer + Baseboard Product
- HardwareID-7 = Manufacturer + SKU Number
- HardwareID-8 = Manufacturer + Product Name + Baseboard Manufacturer + Baseboard Product
- HardwareID-9 = Manufacturer + Product Name
- HardwareID-10 = Manufacturer + Family + Baseboard Manufacturer + Baseboard Product
- HardwareID-11 = Manufacturer + Family
- HardwareID-12 = Manufacturer + Enclosure Type
- HardwareID-13 = Manufacturer + Baseboard Manufacturer + Baseboard Product
- HardwareID-14 = Manufacturer
Each hardware ID string is converted into a GUID by using the SHA-1 hashing algorithm.
Read more: Specifying Hardware IDs for a Computer | Microsoft Docs
Kari
-
There talking to the OEM's
Registering devices to your organization
In order to register devices, you will need to acquire their hardware ID and register it. We are actively working with various hardware vendors to enable them to provide the required information to you, or upload it on your behalf.
Roy
Yes, that's the known and working part, as I mentioned in my original post (extract):
...
... How AutoPilot works is it registers devices to organisation using three values: device serial number, Windows product ID, and device hardware hash, same data which is base for so called hardware signature used to register W10 digital licenses. With new devices this is not an issue, organisations get this data from hardware manufacturers. When device is registered, Windows and all organisation's software can be deployed without IT department never seeing the device or even never being on same network.
The problem is used devices....
...
-
Here's our release - compiled Sat 10.0.16267.1001 (rs_prerelease.170812-2252)
-
-
Here's our release - compiled Sat 10.0.16267.1001 (rs_prerelease.170812-2252)
Let's hope so.
Quote