mOSD

mOSD copied to clipboard

Hello,

In first, Thank's for your great job !. I use an unattend.xml file to send the hardware hash (Autopilot Enrollment) With Windows 10 2004 all is good, With 20h2 is not the same, it is the end for this method ? Unattend.xml in AuditUser mode -> launch a Powershell who install Windowsautopilotintune to get the hardware Hash If I check with a query Wmi, i can take the serial number but not the Class MDM_DevDetail_Ext01 Get-WmiObject -namespace root/cimv2/mdm/dmmap -class MDM_DevDetail_Ext01 return an error. Do you Have already Tested ?

Sorry for my English...:) Best regards, Michel

I'm using the AutoPilotConfigurationFile.json as described here (https://docs.microsoft.com/en-us/mem/autopilot/existing-devices) to do AutoPilot without registerring the hardware hash... Just place the File in .\sources\$OEM$\$$\provisioning\Autopilot\AutopilotConfigurationFile.json

I'm on 20H2 and I can get the HardwareHash by using your PowerShell command... Have you tried to run the command when the device is completely installed and running? Maybe it's a problem during AuditUser ?

I'm use a AutoconfigurationFile.json file too. I have restriction to personall device, so i must have the hardware hash first to complete auto-enrollment and it's not possible with the partner for the moment. I created a ticket on Microsoft, the problem is only in AuditUser Mode, after sysprep i have the class MDM_DevDetail_Ext01.

Strange... please send feedback if you hear something from MS. I know a few customers who will also run in troubles... not many have 20H2 but this will change in the next month...

Ok, no problem, for the moment I test the script with SHIFT F10 on OOBE and launch a ps1 file to send the hardware hash and waiting the profile is assign... I send feedback a soon as possible ;)