Getting started with Windows Autopilot

Here is a small guide, on how to get started with Windows Autopilot. First thing that you need to make sure, is that you have the following prerequisites:

• Devices must be registered to the organization
• Devices have to be pre-installed with Windows 10 Professional, Enterprise or Education, of version 1703 or later
• Devices must have access to the internet
• You must have Azure AD Premium P1 or P2
• You must have Microsoft Intune or other MDM services to manage your devices

First thing you need to do, is to register the device to your organization, that you want to use with Windows Autopilot. This can be an existing computer, or a brand new one.

You will need to get the follow details from the computer:

• HardwareHash
• Windows Product ID
• Device Serialnumber

There is a small Powershell Script that allows you to automatically export these into a csv file.

Here is information about the PS Script:
https://www.powershellgallery.com/packages/Get-WindowsAutoPilotInfo/1.1/DisplayScript

Basically what you need to do, is to run these commands with Powershell:

After getting the needed information from the target computer, you need to import the CSV to Store for Business.

Browse to https://businessstore.microsoft.com and login with a Global Admin account.

• From the menu bar, select Manage and from the left menu bar, select Devices.
• Select Add Devices, and select the CSV file that you created earlier.

From the same menu, you can create a new Autopilot profile and select the basic settings such as:

• Accept EULA
• Decide what kind of user account the enrolled user will have after Autopilot

You can see your device in the Intune portal on Azure

After you have registered the device to your organization it is time to choose the users or groups to use Windows Autopilot.

Browse to Azure portal https://portal.azure.com and login.

• Open Azure Active Directory and head to Mobility (MDM and MAM)
• Select Microsoft Intune
• Select the Groups you want to add, see picture below

 

Next thing you might want to do, is to add some applications to the enrollment process with Autopilot.

Browse to Azure portal https://portal.azure.com and open Intune. Open Mobile Apps and select Apps.

From here you can for example, create a package for Office 365 with the desired configuration.

Here is my example for Office 365 ProPlus package:

 

After you are done with creating the package you want, you need to assign it to the Autopilot group that you created. If you want it to automatically install during Autopilot, remember to select the type Required.

Now you are ready with Autopilot settings and Intune settings.

If you had an existing computer, you can now Sysprep it to OOBE, but do not use the selection Generalize, as the Hardware Hash will change and it will no longer be valid with the Hash you had in the CSV file.

During next boot, connect the computer to any Internet connection and login with Company Credentials, and the computer will auto enroll to Intune, and install the selected Apps.

Microsoft has also published that certain OEM vendors can provide the information that you had in the CSV, directly to your tenant during the order process of new computers. So you can directly ship the computers to the end users, and only thing you need to do, is to assign the Autopilot profiles on Intune.

Here is the list of the current vendors that support Autopilot: