Last year at Microsoft Ignite 2017, we announced Windows Autopilot. This solution provides a way for organizations to ship fresh, untouched Windows 10 devices directly to the end user and define the provisioning flow the user goes through to get a secure, productive Windows 10 device. First, the OEM registers purchased devices with the Windows Autopilot service, so you can assign the necessary Windows Autopilot profile. This profile defines the Out of Box Experience (OOBE) for that device.
It is also possible to register your existing Windows 10 devices with the Windows Autopilot service so that if a device ever needs to be reset, or re-provisioned to a new user, the device will go through the same experience as new devices. ;For more information, see Adding devices to Windows Autopilot and the rest of our Windows Autopilot documentation.
In the year since we announced Windows Autopilot, we have received feedback from many customers who have Windows 7 estates running on modern hardware and want to re-provision those devices with Windows 10 using the Windows Autopilot experience. ;Unfortunately, the hardware hash necessary to pre-register an existing device with Windows Autopilot did not exist on Windows 10 prior to Windows 10, version 1703. This led to many people developing creative and often manual solutions to first reimage a device, then collect the hash to register the device with Windows Autopilot.
To address this, at Microsoft Ignite 2018, we announced Windows Autopilot for existing devices and other capabilities. Windows Autopilot for existing devices allows you to reimage and provision a Windows 7 device for Windows Autopilot user-driven mode using a single System Center Configuration Manager (current branch) task sequence.
You can test this scenario now using Configuration Manager 1806 or later and Windows 10 Insider Preview Build 17758 or later.
In this post, I will take you through the steps to:
Install-Module AzureAD Install-module WindowsAutopilotIntune
Get-AutopilotProfile | ConvertTo-AutopilotConfigurationJSON
NOTE: Multiple JSON profile files can be used, but each must be named AutopilotConfigurationFile.json when applied to Windows for OOBE to follow the Windows Autopilot experience.
cmd.exe /c xcopy AutopilotConfigurationFile.json %OSDTargetSystemDrive%\windows\provisioning\Autopilot\ /c
Note: Some customers wish to have the Windows Autopilot for existing devices task sequence refresh the PC and take the user through Windows Autopilot User-driven mode in one distinct sequence. In this scenario, the PC will reboot once imaged and re-sealed and immediately begin the OOBE.
Other customers may wish to collect hardware and refresh before delivering to a new user. In this case, you may select the Shutdown the computer after running this action to prevent OOBE from beginning immediately after the task sequence completes.
The task sequence is now ready to deploy to your Windows 7 machines, remembering to distribute the content!
We’ll continue to blog about the latest Windows Autopilot capabilities and our documentation will be soon be updated to reflect the new scenarios enabled with the release of Windows 10, version 1809.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.