| title | description | ms.service | ms.localizationpriority | author | ms.author | ms.reviewer | manager | ms.date | ms.topic | ms.collection | ms.subservice | appliesto | ||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Windows Autopilot deployment for existing devices in Intune and Configuration Manager - Step 10 of 10 - Register device for Windows Autopilot |
Windows Autopilot deployment for existing devices in Intune and Configuration Manager - Step 10 of 10 - Register device for Windows Autopilot. |
windows-client |
medium |
frankroj |
frankroj |
jubaptis |
aaroncz |
04/24/2023 |
tutorial |
|
itpro-deploy |
|
Autopilot user-driven Microsoft Entra join steps:
- Step 1: Set up a Windows Autopilot profile
- Step 2: Install required modules to obtain Autopilot profile(s) from Intune
- Step 3: Create JSON file for Autopilot profile(s)
- Step 4: Create and distribute package for JSON file in Configuration Manager
- Step 5: Create Autopilot task sequence in Configuration Manager
- Step 6: Create collection in Configuration Manager
- Step 7: Deploy Autopilot task sequence to collection in Configuration Manager
- Step 8: Speed up the deployment process (optional)
- Step 9: Run Autopilot task sequence on device
[!div class="checklist"]
- Step 10: Register device for Windows Autopilot
For an overview of the Windows Autopilot deployment for existing devices workflow, see Windows Autopilot deployment for existing devices in Intune and Configuration Manager
Running the Autopilot for existing devices task sequence and the Autopilot deployment on a device doesn't automatically register the device for Windows Autopilot. The Autopilot profile JSON makes the Autopilot deployment available to the device and allows the device to run that particular Autopilot deployment, but it doesn't register the device for Windows Autopilot. If the device ever undergoes a reset, when it runs Windows Setup and OOBE for the first time after the reset, it won't run the Autopilot deployment again even though it has previously run an Autopilot deployment.
To ensure that the device can run an Autopilot deployment after a reset, you must register the device for Windows Autopilot. You can register a device by using one of the following methods:
-
Manually register devices with Windows Autopilot: Manually registering a device includes manually registering devices into Intune as an Autopilot device via the hardware hash. The hardware hash of a device can be collected via one of the following methods:
-
In an Autopilot profile that is deployed to a device group that the device is a member of, make sure the option Convert all targeted devices to Autopilot is set to Yes. For more information on creating and assigning Autopilot profiles, see one of the following articles on creating and assigning an Autopilot profile for each of the different Autopilot scenarios:
- User-driven Microsoft Entra join: Create and assign user-driven Microsoft Entra join Autopilot profile
- User-driven Microsoft Entra hybrid join: Create and assign user-driven Microsoft Entra hybrid join Autopilot profile
- Pre-provisioning Microsoft Entra join: Create and assign a pre-provisioned Microsoft Entra join Autopilot profile
- Pre-provisioning Microsoft Entra hybrid join: Create and assign a pre-provisioned Microsoft Entra hybrid join Autopilot profile
- Self-deploying mode: Create and assign self-deploying Autopilot profile
[!INCLUDE Importing the hardware hash CSV file for devices into Intune]
For Autopilot scenarios that utilize Microsoft Entra hybrid join and run after the Windows Autopilot deployment for existing devices task sequence completes, at Step 8: Configure and assign domain join profile for the Windows Autopilot user-driven Microsoft Entra hybrid join scenario or Step 8: Configure and assign domain join profile for the Windows Autopilot for pre-provisioned deployment Microsoft Entra hybrid join scenario, make sure that the domain join profile is assigned to All devices. The domain join profile needs to be assigned to All devices because:
-
If the existing device hasn't ever joined Microsoft Entra ID or been registered in Microsoft Entra ID before the Autopilot deployment runs, then there isn't any Microsoft Entra device for the device in Intune. The Microsoft Entra device is created in Intune when the device joins or registers with Microsoft Entra ID as part of the Autopilot deployment.
-
If the existing device hasn't ever registered as an Autopilot device before the Autopilot deployment runs, then there isn't any Autopilot device for the device in Intune. Normally a device has to be an Autopilot device before the Autopilot deployment can run on it. However, for the Windows Autopilot deployment for existing devices scenario, registering the device as an Autopilot device isn't required since it uses the Autopilot profile JSON file instead. The device is instead registered as an Autopilot device after the Autopilot deployment completes via the methods in the Register device for Windows Autopilot section.
In both of the above scenarios, there's no device that can be added to a device group before the Autopilot deployment begins. Since there's no device group that contains the device, there's no device group that the domain join profile can be assigned to before the Autopilot deployment begins. Assigning the domain join profile to All devices resolves this problem and ensures that the device can pick up the domain join profile before it's either a Microsoft Entra device or Autopilot device.
For more information on registering the device for Windows Autopilot, see the following article(s):