Hi All,
We are performing autopilot for one of the client, there is strange issue with surface laptop hardware hash CSV files.
Microsoft surface laptops serial numbers starts with "Zeros" , So once the hardware hash is generated using PowerShell cmd or csv is shared by vendor, if we or anyone open then CSV file before upload to validate, then the excel default behaviors is to auto remove the zeros from prefix.
Due to this after upload of hardware hash in Intune, zeros are missing in Intune Autopilot devices. So, if now user turn on device and start to perform the autopilot enrolment on these devices where zeros are missing in Intune Autopilot devices data bases, device will not receive and enroll with Autopilot profile created on client Intune, device will enroll with default Microsoft autopilot and OOBE.
So, every time physicals verification of hardware hash and actual serial number is not feasible.
We already instructed the team to open hardware hash file using notepad to avoid any changes in CSV file.
Also surface device has 12-digit serial number, so in case we see any device has less than 12 digits, that's an alert for us.
But still in this process there is possibility for human errors and when we have 1000's of devices are getting registered, its quite difficult to keep a tap on each one.
Due to this human error if device required rebuild, that's a huge escalation, as many users are working from home and time and effort is huge to take device remote to rebuild and rectify the mistake.
Just checking if same issues is faced by anyone and Any suggestion?
As both product is of MS (Surface device and excel), then why MS surface device serial number starts with Zeros as they know the other MS product (excel) will create issues for that zero‼
Also, Intune only accepts CSV in Autopilot devices‼
