Windows Autopilot deployment for existing devices: Run Autopilot task sequence on device
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
For an overview of the Windows Autopilot deployment for existing devices workflow, see Windows Autopilot deployment for existing devices in Intune and Configuration Manager
Run Autopilot task sequence on device
Once the Autopilot for existing devices has been created, modified as needed, and deployed, the task sequence can be run on a device by following these steps:
Start the task sequence using the desired method based on how the task sequence deployment was configured:
- Configuration Manager Software Center
- PXE enabled distribution point
- Task sequence bootable media
Allow the task sequence to complete.
Once the task sequence completes, the device either restarts or shuts down depending on the shutdown or restart behavior selected in one of the following two steps:
The behavior of the device after the task sequence completes depends on whether the device restarted or shut down:
Restart: the device restarts as soon as the task sequence completes and then immediately boot into Windows for the first time and run OOBE. When OOBE runs, the Autopilot JSON file is processed and the Autopilot deployment starts.
Shutdown: the device shuts down and power off as soon as the task sequence completes. Shutting down the device gives the option to further prepare the device and then deliver it to an end-user. OOBE and the Autopilot deployment start when the end-user turns on the device for the first time.
Important
If the following conditions are met when the device starts back up after the task sequence completes:
- Device is registered as an Autopilot device in Intune
- Device has an Autopilot profile assigned to it in Intune
then the Autopilot profile from Intune is downloaded to the device and is used instead of the Autopilot profile from the JSON file staged by the task sequence. The downloaded Autopilot profile from Intune has priority over the local Autopilot profile from the JSON file.
Next step: Register device for Windows Autopilot
More information
For more information on running the Autopilot task sequence on the device, see the following article(s):
Atsiliepimai
https://aka.ms/ContentUserFeedback.
Jau greitai: 2024 m. palaipsniui atsisakysime „GitHub“ problemų, kaip turiniui taikomo atsiliepimų mechanizmo, ir pakeisime jį nauja atsiliepimų sistema. Daugiau informacijos žr.Pateikti ir peržiūrėti atsiliepimą, skirtą