{"id":302,"date":"2023-05-15T12:48:35","date_gmt":"2023-05-15T12:48:35","guid":{"rendered":"https:\/\/endpointinsights.net\/?p=302"},"modified":"2023-05-25T11:19:27","modified_gmt":"2023-05-25T09:19:27","slug":"autopilot-setup","status":"publish","type":"post","link":"https:\/\/endpointinsights.net\/de\/autopilot-setup\/","title":{"rendered":"Autopilot setup"},"content":{"rendered":"\n

Autopilot – short notes to start from<\/h1>\n\n\n\n

Autopilot Quicklinks<\/a><\/p>\n\n\n\n

<\/a>demo:<\/h2>\n\n\n\n
\nhttps:\/\/regale.cloud\/Microsoft\/viewer\/1339\/index.html#\/0\/0\n<\/div><\/figure>\n\n\n\n

<\/a>some general usefull things around autopilot<\/h1>\n\n\n\n

<\/a>Get HWID<\/h2>\n\n\n\n

md c:\\HWID<\/p>\n\n\n\n

Set-Location c:\\HWID<\/p>\n\n\n\n

Set-ExecutionPolicy -Scope Process -ExecutionPolicy Unrestricted -Force<\/p>\n\n\n\n

Install-Script -Name Get-WindowsAutopilotInfo -Force<\/p>\n\n\n\n

$env:Path += „;C:\\Program Files\\WindowsPowerShell\\Scripts“<\/p>\n\n\n\n

Get-WindowsAutopilotInfo.ps1 -OutputFile AutopilotHWID.csv<\/p>\n\n\n\n

<\/a>OR instead of doing HWID manually you can enrole the HWID in one step<\/h2>\n\n\n\n
Start OOBE on Device:\n[Shift]+F10\nPowerShell.exe -ExecutionPolicy Bypass\nInstall-Script -name Get-WindowsAutopilotInfo -Force\nSet-ExecutionPolicy -Scope Process -ExecutionPolicy RemoteSigned\n    Get-WindowsAutopilotInfo -Online  -TenantName \"tenant-name\" -GroupTag \"AutoPilot\" -verbose\n\nOr you can use this cool GUI:\nIn OOBE: Start the Command Line by simultaneously pressing Shift + F10.\nOpen Powershell by typing in Powershell.\nSet-Executionpolicy RemoteSigned\nInstall-Script Get-WindowsAutopilotImportGUI\nGet-WindowsAutopilotImportGUI\n<\/code><\/pre>\n\n\n\n
Autopilot Import GUI \u2013 Cloud Blog (ugurkoc.de)<\/a><\/p>\n\n\n\n
<\/a>Sysprep OOBE<\/h2>\n\n\n\n
PS C:\\HWID> cd C:\\Windows\\System32\\Sysprep<\/p>\n\n\n\n
PS C:\\Windows\\System32\\Sysprep> .\\sysprep.exe \/OOBE \/Reboot<\/p>\n\n\n\n
<\/a>Create Autopilot Group:<\/h2>\n\n\n\n
(device.devicePhysicalIDs -any (_ -contains \u201c[ZTDId]\u201d))<\/p>\n\n\n\n
Script – Bulk create common AAD Groups for MSIntune – Let’s ConfigMgr! (letsconfigmgr.com)<\/a><\/p>\n\n\n\n
with (device.devicePhysicalIds -any (_ -eq „[OrderID]:Standard“)) you can filter by GroupTag<\/p>\n\n\n\n
<\/a>Company Branding:<\/h2>\n\n\n\n
Azure Active Directory > Company branding MECM<\/p>\n\n\n\n
    \n
  1. Tenant administration.<\/li>\n\n\n\n
  2. Under End user experiences, click on Customization.<\/li>\n<\/ol>\n\n\n\n
    <\/a>Enable Autopilot<\/h2>\n\n\n\n
      \n
    1. Azure Active Directory > Mobility (MDM and MAM) > Microsoft Intune.<\/li>\n\n\n\n
    2. In the MDM user scope setting, select All.<\/li>\n<\/ol>\n\n\n\n
      <\/a>Configure Autopilot<\/h1>\n\n\n\n
        \n
      1. Under Device enrollment, click on Enroll devices.<\/li>\n\n\n\n
      2. Under Windows Autopilot Deployment Program, click on Devices.<\/li>\n\n\n\n
      3. Click Import, and select the MyComputers.csv file saved from before and click Import.<\/li>\n\n\n\n
      4. On the Devices > Enroll devices pane, click Deployment Profiles > + Create profile and select Windows PC.<\/li>\n\n\n\n
      5. On the Basics step, in the Name box, type Autopilot Test Profile and click Next. Note: Leave the Convert all targeted device to Autopilot set to No.<\/li>\n\n\n\n
      6. On the Out-of-box experience (OOBE) step, in the Deployment mode dropdown, select user-driven<\/a>.<\/li>\n\n\n\n
      7. In the Join to Azure AD as dropdown, select Azure AD joined.<\/li>\n\n\n\n
      8. For the Microsoft Software License Terms option, select Hide.<\/li>\n\n\n\n
      9. For the Privacy Settings option, select Hide.<\/li>\n\n\n\n
      10. For the Hide change account options option, select Hide.<\/li>\n\n\n\n
      11. For the User account type option, select Standard and click Next.<\/li>\n\n\n\n
      12. In the Assignments step, under Included groups, click + Add groups, select the Autopilot Devices group just created and click Select and then click Next.<\/li>\n\n\n\n
      13. In the Review + create step, click Create.<\/li>\n\n\n\n
      14. Wait a few minutes for the device to show up in Assigned devices under Autopilot Test Profile.<\/li>\n\n\n\n
      15. Click on Devices > Enroll devices > Windows Autopilot devices and you should be able to see the PROFILE STATUS as Updating and then further Assigned. Wait for a few moments.<\/li>\n<\/ol>\n\n\n\n
        Start OOBE<\/a> on Client<\/p>\n\n\n\n
        <\/a>Configure PreProvisioned Autopilot:<\/h2>\n\n\n\n
        <\/a>Prerequisites:<\/h3>\n\n\n\n
          \n
        1. Windows 10, version 1903 or later, or Windows 11.<\/li>\n\n\n\n
        2. Windows Pro, Enterprise, or Education editions.<\/li>\n\n\n\n
        3. An Intune subscription.<\/li>\n\n\n\n
        4. Physical devices that support TPM 2.0 and device attestation; virtual machines are not supported<\/strong>. The pre- provisioning process leverages Windows Autopilot self-deploying capabilities, so TPM 2.0 is required. The TPM attestation process also requires access to a set of HTTPS URLs that are unique for each TPM provider. For more information, see the entry for Autopilot self-Deploying mode and Autopilot pre-provisioning in Networking requirements<\/a>. Physical devices with Ethernet connectivity are required to perform pre-provisioning. Wi-Fi connectivity isn’t supported because of the requirement to choose a language, locale, and keyboard to make that Wi-Fi connection. Enforcing this requirement in a pre-provisioning process could prevent the user from choosing their own language, locale, and keyboard when they receive the device. For more information, see Using a wireless network connection with Windows Autopilot white glove<\/a><\/li>\n<\/ol>\n\n\n\n
          <\/a>MECM:<\/h3>\n\n\n\n
          On the Basics step, in the Name box, type Autopilot preprovisioned deployment test profile and click Next.<\/p>\n\n\n\n
          <\/a>Client:<\/h3>\n\n\n\n
            \n
          1. On the cleint in the OOBE-Phase<\/a> Let\u2019s set things up for your work or school screen, press the Windows key five times to view an additional options dialog. From that screen, choose the Pre-provision with Windows Autopilot option and then click Next.<\/li>\n\n\n\n
          2. A QR code containing a unique identifier for the device, useful to look up the device in Intune to make any configuration changes (example: assigning a user, adding the device to any additional groups needed for app or policy targeting).<\/li>\n\n\n\n
          3. Validate the information displayed. If any changes are needed, make those and then Refresh to re-download the updated Autopilot profile details.<\/li>\n\n\n\n
          4. Click Reseal to shut the device down. At that point, the device can be shipped to the end user. Note: If the pre-provisioning process fails, a message that says Something went wrong will be displayed with information about the device, and a QR code that can be used to review the results. Diagnostic logs can be gathered from the device, and then it can be reset to start the process over again.<\/li>\n<\/ol>\n\n\n\n
            After that > User Flow<\/p>\n\n\n\n
            <\/a>Convert existing device to Autopilot<\/h1>\n\n\n\n
            <\/a>Intune Devices:<\/h2>\n\n\n\n
            Device enrollment > Windows enrollment > Deployment Profiles > Create Profile>Set Convert all targeted devices<\/p>\n\n\n\n
            <\/a>SCCM (Co-Management devices)<\/h2>\n\n\n\n
            First, get the devices into Intune via co-management and then to Autopilot > Set Convert all targeted devices<\/p>\n\n\n\n
            <\/a>Windows 7 Devices:<\/h2>\n\n\n\n
            Upgrade Windows 7 using Windows Autopilot in Configuration Manager – Microsoft Tech Community<\/a><\/p>\n\n\n\n
            faster: Speeding up Windows Autopilot for existing devices | Microsoft Docs<\/a><\/p>\n\n\n\n
            <\/a>Device with Windows 10 but without SCCM and no Intune<\/h2>\n\n\n\n
            I have written this script<\/a> to get the such devices to Intune Autopilot. All that is required is A User with the permission to enroll.<\/p>\n\n\n\n
            <\/a>Intune AD connector (Intune Connector for Active Directory)<\/h1>\n\n\n\n
            <\/a>Windows Autopilot Workflow \u2013 Hybrid Azure AD Join<\/h2>\n\n\n\n
            \"image\"\/<\/figure>\n\n\n\n
            Following are the Intune AD connector requirement. Make sure that you have all the needs in place before the implementation. * The Intune Connector installation requires Windows Server 2016 or later.<\/p>\n\n\n\n