{"id":520688,"date":"2025-06-19T15:18:00","date_gmt":"2025-06-19T22:18:00","guid":{"rendered":"https:\/\/jorgep.com\/blog\/?p=520688"},"modified":"2026-05-11T15:31:57","modified_gmt":"2026-05-11T22:31:57","slug":"windows-autopilot-moving-to-v2-device-preparation","status":"publish","type":"post","link":"https:\/\/jorgep.com\/blog\/windows-autopilot-moving-to-v2-device-preparation\/","title":{"rendered":"Windows Autopilot: Moving to v2 (Device Preparation)"},"content":{"rendered":"\n

<\/p>\n\n\n\n

Checkout my other blogs about Windows Autopilot <\/a><\/p>\n\n\n\n

<\/p>\n\n\n\n

For years, IT administrators have relied on Windows Autopilot to transform “off-the-shelf” hardware into fully managed corporate machines. However, the landscape has shifted. Microsoft has introduced a re-architected version, commonly referred to as Autopilot v2<\/strong> (officially known as Windows Autopilot Device Preparation<\/strong>), to address long-standing pain points regarding speed, reliability, and the hassle of hardware hashes.<\/p>\n\n\n\n

The Timeline: A Tale of Two Versions<\/h2>\n\n\n\n

Understanding where we are requires looking at where we started. Microsoft has maintained a steady cadence of innovation in the deployment space:<\/p>\n\n\n\n

    \n
  • Windows Autopilot (v1):<\/strong> Generally Available (GA) in late 2017<\/strong>. It revolutionized the “imaging” process by replacing it with “provisioning.”<\/li>\n\n\n\n
  • Windows Autopilot Device Preparation (v2):<\/strong> Generally Available (GA) in May 2024<\/strong>. This version was built from the ground up to utilize modern cloud-native enrollment flows.<\/li>\n<\/ul>\n\n\n\n

    Comparison: v1 vs. v2<\/h2>\n\n\n\n

    While both aim to get a user to a productive desktop, the underlying plumbing is very different.<\/p>\n\n\n\n

    Feature<\/strong><\/td>Classic Autopilot (v1)<\/strong><\/td>Device Preparation (v2)<\/strong><\/td><\/tr><\/thead>
    Registration<\/strong><\/td>Requires Hardware Hash (CSV\/OEM)<\/td>None (or Corporate Identifiers)<\/td><\/tr>
    Identity Support<\/strong><\/td>Entra ID or Hybrid Join<\/td>Entra ID Join only<\/strong><\/td><\/tr>
    OS Requirement<\/strong><\/td>Windows 10 & 11<\/td>Windows 11 only<\/strong> (22H2+)<\/td><\/tr>
    Reporting<\/strong><\/td>Basic status in Intune console<\/td>Near real-time deployment tracking<\/td><\/tr>
    Deployment Logic<\/strong><\/td>Device-based targeting<\/td>User-based targeting<\/td><\/tr>
    App Limit<\/strong><\/td>No hard limit (often slow)<\/td>Optimized for up to 25 “essential” apps<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
    \n\n\n\n

    What is the Corporate Identifier List?<\/h2>\n\n\n\n

    One of the biggest hurdles in v1 was the “Hardware Hash”\u2014a 4,000-character string unique to the motherboard. v2 eliminates the mandatory requirement for this hash.<\/p>\n\n\n\n

    To ensure security and block personal devices (BYOD) from enrolling, IT admins now use the Corporate Identifier List<\/strong>. Instead of a complex hash, you identify corporate hardware using three simple strings often found on the shipping manifest or the device box:<\/p>\n\n\n\n

      \n
    1. Manufacturer<\/strong> (e.g., Dell Inc.<\/em>)<\/li>\n\n\n\n
    2. Model<\/strong> (e.g., Latitude 7440<\/em>)<\/li>\n\n\n\n
    3. Serial Number<\/strong> (e.g., ABC1234<\/em>)<\/li>\n<\/ol>\n\n\n\n

      When a user signs in, Intune checks these three pieces of data. If they match your list, the device is flagged as “Corporate” and allowed to proceed with the v2 workflow.<\/p>\n\n\n\n

      There is a way to import a CSV file into this section of the portal: <\/p>\n\n\n\n

        \n
      • Open the Microsoft Intune admin center<\/strong>.<\/li>\n\n\n\n
      • Navigate to Devices<\/strong> > Enrollment<\/strong>.<\/li>\n\n\n\n
      • Select Corporate device identifiers<\/strong>.<\/li>\n\n\n\n
      • Click Add<\/strong> > Upload CSV file<\/strong>.<\/li>\n\n\n\n
      • Browse for your file and click Add<\/strong>.<\/li>\n<\/ul>\n\n\n\n

        SAMPLE CSV FILE: <\/p>\n\n\n\n

        Dell Inc.,Latitude 7440,ABC1234\nMicrosoft,Surface Laptop 6,0123456789\nLenovo,ThinkPad T14,XYZ5678<\/code><\/pre>\n\n\n\n
          \n
        • No Headers:<\/strong> Do not include a row for “Manufacturer” or “Model” at the top.<\/li>\n\n\n\n
        • Three Columns:<\/strong> Each line must contain exactly three values in this order: Manufacturer<\/strong>, Model<\/strong>, and Serial Number<\/strong>.<\/li>\n\n\n\n
        • Plain Text:<\/strong> Save the file as a standard .csv<\/code> (Comma Separated Values).<\/li>\n<\/ul>\n\n\n\n
          Can They Coexist?<\/h2>\n\n\n\n
          The short answer is yes<\/strong>. You do not need to switch your entire organization to v2 overnight. Many enterprises are currently running both versions simultaneously.<\/p>\n\n\n\n
          The Priority Hierarchy<\/h3>\n\n\n\n
          When a user signs into a new Windows 11 device, Intune looks for instructions in a specific order to decide which “lane” to put the device in:<\/p>\n\n\n\n
          Priority<\/strong><\/td>Scenario<\/strong><\/td>Outcome<\/strong><\/td><\/tr><\/thead>
          1<\/strong><\/td>Hardware Hash is registered in the v1 service<\/td>Classic Autopilot (v1) wins<\/strong><\/td><\/tr>
          2<\/strong><\/td>No Hash found + User is assigned a v2 Policy<\/td>Device Preparation (v2) wins<\/strong><\/td><\/tr>
          3<\/strong><\/td>No Hash + No v2 Policy<\/td>Standard MDM Enrollment<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
          <\/p>\n\n\n