Building a Windows 11 24H2 Reference Image using ConfigMgr (SCCM)

Since Windows Vista, creating reference images is no longer technically required, as Microsoft's ISO files already contain deployable WIM images. When needed, reference images are primarily used to expedite deployments and enhance network efficiency. However, with modern hardware, networking, and peer-to-peer technologies, fast deployments can often be achieved without the need for them.

Today, most organizations prefer thin images, adding apps and settings during deployment. But if you still need a thick reference image that includes applications, here's how to create one using a ConfigMgr Build and Capture task sequence.

Update! We're tracking an issue with Sysprep crashing on Windows 11 24H2 devices because the ConfigMgr task sequence runs Sysprep as SYSTEM, which Sysprep does not officially support (but usually works fine on earlier Windows versions).

Note: Although the Microsoft Deployment Toolkit (MDT) does not officially support Windows 11, it still works well for creating reference images on that platform and is often the preferred choice due to its simplicity and ease of automation. If MDT is your go-to tool for generating reference images, check out this post; otherwise, continue reading…

The Definition of a Reference Image

You often hear the world reference image being used in imaging scenarios. For clarity, here is the definition of a thin vs. thick image.

• Thin Image. A thin image (or a default image) is an image that does not contain any additional applications. When deploying thin images, the applications, drivers, and additional settings are installed or injected at deployment time. Even if this image type typically contains operating system components, such as the .NET Framework, and updates from Microsoft Update, it’s still considered a thin image. In general, a thin image is more suitable in a dynamic environment.
• Thick Image. A thick image is an image that includes additional applications. The primary reason for creating this image type is deployment speed. Drivers and settings are still kept outside the image. In general, a thick image is more suitable in a static environment. Educational organizations typically use this type of image to quickly deploy labs or classrooms. This guide is about creating thick images.

Build and Capture in ConfigMgr – Overview

When building reference images with ConfigMgr, there are two native processes for doing so:

• Using a Build and Capture task sequence (recommended). This process is a fully automated installation of Windows and applications, followed by running Sysprep and saving the image to a file share. This process is the one used in this guide.
• Build first, capture later. This process is broken down into two phases. First, install Windows using a standard image task sequence, and later run Sysprep and capture using the ConfigMgr capture boot media. It can be helpful during the development phase of a reference image or when manual configurations are required in an otherwise automated process.

Preparation

Regardless of which scenario you choose, there are a few key steps you need to take to prepare your ConfigMgr environment.

• Creating a Service Account. You need a service account that is used when capturing the new WIM image to a file share. This can (and should) be a regular user account. In my lab, I named it CM_OSD.
• Creating a file share. You need a file share to which the service account has permission to create files. In my lab, I named it \\CM01\Captures.
• Creating applications. For any applications you want to add to your image, whether application model applications or legacy package applications, you need to configure them to allow installation via the task sequence. For application model apps, that's done on the application properties. For legacy packages, that's a setting on the program.
• Adding an operating system image to ConfigMgr. You need to copy your install.wim WIM file to a file share, and add it as an operating system image in the ConfigMgr console. For details on this action, see the Microsoft docs – Add an OS image.

Creating a Build and Capture task sequence

Here are the steps to create a build and capture task sequence in ConfigMgr.

• Using Configuration Manager Console, in the Software Library workspace, expand Operating Systems, right-click Task Sequences, and select Create Task Sequence.
• Use the following settings for the Create Task Sequence wizard.
  • Create a new task sequence
    • Build and capture a reference operating system image
  • Task Sequence Information
    • Task sequence name: Windows 11 Enterprise x64 24H2 Build and Capture
    • Boot image: Boot image (x64)
    • Run as high performance power plan
  • Install Windows
    • Image package: Windows 11 Enterprise x64 24H2
    • Administrator Account
      • Enable the account and specify the local administrator password
      • Password and Confirm password: P@ssw0rd

• Continue the Create Task Sequence wizard…
  • Configure the network
    • Join a workgroup
    • Workgroup: WORKGROUP
  • Install the Configuration Manager client
    • Select the Configuration Manager Client Package package (default)
    • Installation Properties: DNSSUFFIX=corp.viamonstra.com SMSMP=cm01.corp.viamonstra.com
• Note: Since you are deploying reference images into a workgroup, you must provide instructions for the client to locate the management point.

• Continue the Create Task Sequence wizard…
  • Include software updates
    • Do not install any software updates (use an updated media instead)
  • Install applications
    • Add the application you want included in your image
  • System preparation
    • Just click next.
  • Specify the image properties
    • Created by: Your Name
  • Capture image settings
    • Path: \\CM01\Captures\W11-X64-24H2-Enterprise.wim
    • Account: Add your service account with its password

Creating a Windows 11 24H2 reference image

Deploy the previously created build and capture task sequence to a collection, either the built-in All Unknown Computers collection or a custom device collection (recommended).

• Create a virtual machine with 240 GB disk, 8 GB RAM, and 4 vCPUs.
  
  Note: To prevent Windows from updating any components during installation, I recommend blocking Internet access to this virtual machine during the build and capture process. Updated components are known for breaking Sysprep.
• Before booting the new VM, take a snapshot/checkpoint
• Boot the new VM on either a ConfigMgr boot image or PXE, and then select the Windows 11 Enterprise x64 24H2 Build and Capture you just created and deployed.

The Task Sequence will now run and do the following:

• Install the Windows 11 operating system
• Install the ConfigMgr Client
• Join the machine a workgroup
• Install any selected applications
• Uninstalls the ConfigMgr client (for build and capture sequences only, it removes unique identifiers when using a capture media or capture only task sequence. This behavior can be overridden with the SMSTSUninstallCCMClient task sequence variable. See this documentation: Prepare ConfigMgr Client for Capture)
• Run Sysprep (Generalize)
• Reboot into WinPE, and capture the installation to a WIM file

After the Windows 11 Enterprise x64 24H2 Build and Capture task sequence has completed, you should now see a new WIM file in the share you configured.

Additional Resources

If you are planning to use the image created via ConfigMgr for any other deployment solution, like MDT, or a custom deployment solution, please note that you need to make some additional changes to the image, see this post by Michael Niehaus: Deploy SCCM images with something other than SCCM