Skip to content

Latest commit

 

History

History
123 lines (68 loc) · 7.9 KB

manage-operating-system-images.md

File metadata and controls

123 lines (68 loc) · 7.9 KB
Raw
title titleSuffix description ms.date ms.service ms.subservice ms.topic author ms.author manager ms.localizationpriority ms.reviewer ms.collection
Manage OS images
Configuration Manager
Learn the methods to manage OS images stored in Windows image (WIM) files.
09/18/2023
configuration-manager
osd
how-to
BalaDelli
baladell
apoorvseth
medium
mstewart,aaroncz
tier3

Manage OS images with Configuration Manager

Applies to: Configuration Manager (current branch)

OS images in Configuration Manager are stored in the Windows image (WIM) file format. These images are a compressed collection of reference files and folders use to install and configure a new OS on a computer. Many OS deployment scenarios require an OS image.

OS image types

You can use a default OS image, or build the OS image from a reference computer that you configure. When you build the reference computer, you add OS files, drivers, support files, software updates, tools, and applications to the OS. Then you capture it to create the image file.

Default image

The Windows installation files include the default OS image. This image is a basic OS image that contains a standard set of drivers. When you use the default OS image, use task sequence steps to install apps and make other configurations after the OS installs on a device. Locate the default OS image in the Windows source files: \Sources\install.wim.

Default image advantages

  • The image size is smaller than a captured image.

  • Installing apps and configurations with task sequence steps is more dynamic. For example, change the configurations and apps that install in the task sequence, without having to reimage the device.

Default image disadvantages

  • OS installation can take more time. The application installation and other configurations occur after the OS installation completes.

Captured image from a reference computer

To create a customized OS image, build a reference computer with the desired OS. Then install applications and configure settings. Capture the OS image from the reference computer to create the WIM file. Manually build the reference computer, or use a task sequence to automate some or all of the build steps. For more information, see Customize OS images.

Captured image advantages

  • The installation can be faster than using the default image. For example, applications can be preinstalled with the captured OS image. Then you don't need to install those same applications later by using task sequence steps.

Captured image disadvantages

  • The image size is potentially larger than the default image.

  • Need to create a new image when you require updates for applications and tools.

Add an OS image

Before you can use an OS image, add it to your Configuration Manager site.

  1. In the Configuration Manager console, go to the Software Library workspace, expand Operating Systems, and then select the Operating System Images node.

  2. On the Home tab of the ribbon, in the Create group, select Add Operating System Image. This action starts the Add Operating System Image Wizard.

  3. On the Data Source page, specify the following information:

    • Network Path to the OS image file. For example, \\server\share\path\image.wim.

    • Accept Eula, by checking the box

    • Extract a specific image index from the specified WIM file and then select an image index from the list. Starting in version 1902, this option automatically imports a single index rather than all image indexes in the file. Using this option results in a smaller image file, and faster offline servicing. It also supports the process to Optimize image servicing, for a smaller image file after applying software updates.

      [!Note]
      Configuration Manager doesn't modify the source image file. It creates a new image file in the same source directory.

      This extraction process can fail for extremely large image files, for example over 60 GB. The DISM error is Not enough storage is available to process this command. The command line that Configuration Manager uses is in the smsprov.log and dism.log. Manually run the same command and then import the image.

    • Starting in version 1906, if you want to pre-cache content on a client, specify the Architecture and Language of the image. For more information, see Configure pre-cache content.

  4. On the General page, specify the following information. This information is useful for identification purposes when you have more than one OS image.

    • Name: A unique name for the image. By default, the name comes from the WIM file name.

    • Version: An optional version identifier. This property doesn't need to be the OS version of the image. It's often your organization's version for the package.

    • Comment: An optional brief description.

  5. Complete the wizard.

For the PowerShell cmdlet equivalent of this console wizard, see New-CMOperatingSystemImage.

Next, distribute the OS image to distribution points.

Distribute content to distribution points

Distribute OS images to distribution points the same as other content. Before you deploy the task sequence, distribute the OS image to at least one distribution point. For more information, see Distribute content.

[!INCLUDE Apply software updates to an image]

Prepare the OS image for multicast deployments

Use multicast deployments to allow more than one computer to simultaneously download an OS image. The image is multicast to clients by the distribution point, rather than each client downloading a copy of the image from the distribution point over a separate connection. When you choose the OS deployment method to Use multicast to deploy Windows over the network, configure the OS image to support multicast. Then distribute the image to a multicast-enabled distribution point.

  1. In the Configuration Manager console, go to the Software Library workspace, expand Operating Systems, and then select the Operating System Images node.

  2. Select the OS image that you want to distribute to a multicast-enabled distribution point.

  3. On the Home tab of the ribbon, in the Properties group, select Properties.

  4. Switch to the Distribution Settings tab, and configure the following options:

    • Allow this package to be transferred via multicast (WinPE only): Select this option for Configuration Manager to simultaneously deploy OS images using multicast.

    • Encrypt multicast packages: Specify whether the site encrypts the image before it's sent to the distribution point. If the image contains sensitive information, use this option. If the image isn't encrypted, its contents are visible in clear text on the network. Then an unauthorized user could intercept and view the image contents.

    • Transfer this package only via multicast: Specify whether you want the distribution point to deploy the image only during a multicast session.

      If you select Transfer this package only via multicast, you must also specify the task sequence deployment option to Download content locally when needed by the running task sequence. For more information, see Deploy a task sequence.

  5. Select OK to save the settings and close the image properties.