Microsoft announced Windows Autopilot end of June. Windows Autopilot is a collection of technologies to setup and pre-configure (new) Windows 10 devices. IT is able to customize the Out of Box Experience for Windows 10 devices. The end user connects the new device to the internet, logs on with the company credentials and in a few clicks the device is automatically Azure AD joined, Intune managed and software is deployed. All without the user making any decisions on settings and without the involvement of IT.
There are some prerequisites using Windows Autopilot:
- Devices must be registered to the organization
- Devices must be running Windows 10, version 1703 or later
- Devices must have access to the internet
- Azure AD Premium (for auto Azure AD join)
- Microsoft Intune or another MDM service (to manage the device/ roll out software)
Registering the devices
We first have to collect some information from the devices, to upload to the Microsoft Partner Center (later you should be able to use the Business Store as well). We need the device serial number, Windows Product ID and Hardware Hash. This information is uploaded with a csv file to the Partner Center.
To collect the information we need, we can use this script or collect it manually.
For the Windows Product ID have a look under Windows Settings, About or run this Powershell command:
Get-ItemPropertyValue “hklm:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\DefaultProductKey2\” “ProductId”
And to get the Hardware Hash, run this query:
$wmi = Get-WMIObject -Namespace root/cimv2/mdm/dmmap -Class MDM_DevDetail_Ext01 -Filter “InstanceID=’Ext’ AND ParentID=’./DevDetail'”
$wmi.DeviceHardwareData | Out-File “$($env:COMPUTERNAME).txt”
Manage Windows Autopilot from the Partner Center
Now that we have collected the information, we need to upload it to the Microsoft Partner Center to register the device.
Open the Partner Center, find the Customer and click on Devices on the left side. We first have to setup an Auto pilot profile, click on Add new profile.
Enter a group name for the devices you are uploading.
Browse to the csv file with the collected device information and click Validate.
After the validation is finished, click Upload.
When the upload is finished, check the device, select Apply profile and choose the previously created profile to apply.
The device is ready for Windows modern deployment with Windows Autopilot.
The end user experience with Windows Autopilot
The next step, Windows will verify network connectivity. When the device is connected with an ethernet cable, Windows will perform a check to see it is a known device. When not yet connected to the internet, you`re asked to select a wifi network.
When authentication is successful, the device profile from CSP is pushed to the device, the device is Azure AD joined, MDM settings are affected and software is deployed. The end user is logged on and is ready to get some work done!
Later this year new capabilities will be added to Autopilot in the Windows 10 Fall Creators update.
Update July 20th: Add device from Business Store
Creating a profile and adding devices works exact the same way as in the CSP as described above.