From a619cb6112c4beb11da16aba1a156f1ba650753e Mon Sep 17 00:00:00 2001 From: andreiztm Date: Tue, 11 Feb 2020 13:35:28 +0200 Subject: [PATCH] Add important note about known issue --- windows/deployment/windows-autopilot/existing-devices.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/windows/deployment/windows-autopilot/existing-devices.md b/windows/deployment/windows-autopilot/existing-devices.md index 81cc5bf9a7..afd18141f0 100644 --- a/windows/deployment/windows-autopilot/existing-devices.md +++ b/windows/deployment/windows-autopilot/existing-devices.md @@ -206,6 +206,9 @@ See the following examples. >[!IMPORTANT] >The Autopilot for existing devices task sequence will run the **Prepare Windows for capture** action which calls the System Preparation Tool (syeprep). This action will fail if the target machine is joined to a domain. + + >[!IMPORTANT] + >The System Preparation Tool (syeprep) will be executed with the /Generalize parameter which on Windows 10 1903 & Windows 10 1909 versions will delete the AutoPilot profile file and the machine will boot into OOBE phase instead of AutoPilot. Please see Michael Niehaus's blog with instructions [A challenge with Windows Autopilot for existing devices and Windows 10 1903](https://oofhours.com/2019/09/19/a-challenge-with-windows-autopilot-for-existing-devices-and-windows-10-1903/) on the solution to prevent this. 5. Click **Next** and then click **Next** again to accept the default settings on the Install Configuration Manager page. 6. On the State Migration page, enter the following details: