{"id":3703,"date":"2024-09-21T07:35:10","date_gmt":"2024-09-21T06:35:10","guid":{"rendered":"https:\/\/rolig.dk\/?p=3703"},"modified":"2024-11-06T09:25:57","modified_gmt":"2024-11-06T08:25:57","slug":"windows-autopilot-device-preparation","status":"publish","type":"post","link":"https:\/\/rolig.dk\/?p=3703","title":{"rendered":"Windows Autopilot device preparation"},"content":{"rendered":"\n

Microsoft have added a new way of preparing Windows device for Modern Managed pc’s via Intune. The new name is “Windows Autopilot device preparation”.
Microsoft article: https:\/\/learn.microsoft.com\/en-us\/autopilot\/device-preparation\/overview<\/a><\/p>\n\n\n\n

What is going to happen during the installation:<\/strong><\/p>\n\n\n\n

During the out-of-box experience (OOBE), a user authenticates with their corporate credentials. If there’s a Windows Autopilot device preparation policy assigned to the user signing in, then that policy is delivered to the device. It then determines the configuration that needs to be applied to the device based on the settings configured in the policy. After that, device setup continues in the following order:<\/p>\n\n\n\n

    \n
  1. The device joins Microsoft Entra ID and enrolls in Intune.<\/li>\n\n\n\n
  2. The Intune management extension installs.<\/li>\n\n\n\n
  3. When the device is joined to Microsoft Entra ID during the first step, the user is automatically added to the local Administrators<\/strong> group on the device. If the user account is configured as a standard user, the setting is enforced by removing the user out of the Administrators<\/strong> group.<\/li>\n\n\n\n
  4. The deployment syncs with the mobile device management (MDM) service such as Intune and checks if line-of-business (LOB) and Microsoft 365 applications are selected in the Windows Autopilot device preparation policy. It also syncs all MDM policy at this time, but application of the policy isn’t tracked during the deployment.<\/li>\n\n\n\n
  5. If there are LOB and Microsoft 365 applications selected in the policy, then they’re installed. If a LOB or Microsoft 365 application fails to install, then the deployment fails at this point.<\/li>\n\n\n\n
  6. The deployment checks if PowerShell scripts are selected in the Windows Autopilot device preparation policy. If there are PowerShell scripts selected in the policy, then they run. If a PowerShell script fails, then the deployment fails at this point.<\/li>\n\n\n\n
  7. The deployment checks if Win32 and Microsoft Store applications are selected in the Windows Autopilot device preparation policy. If there are Win32 and Microsoft Store applications selected in the policy, then they’re installed. If a Win32 or Microsoft Store application fails to install, then the deployment fails at this point.<\/li>\n\n\n\n
  8. If all steps succeed, the Required setup complete<\/strong> page is displayed for the user.<\/li>\n\n\n\n
  9. Once the Required setup complete<\/strong> page is dismissed, the user is automatically signed in and the desktop is displayed.<\/li>\n\n\n\n
  10. At this point, another sync is triggered and all other configurations is delivered to the device. Additional configurations might include:\n