Windows SIM enables you to create an answer file to be used during Windows Setup. You can view all of the components available in a Windows image, add component settings to your answer file, and choose when to apply a component setting by adding it to a particular configuration pass.

After component settings are added to an unattended answer file, you can view and customize the available settings for each component. For more information, see Understanding Answer Files.

Windows SIM enables you to add components, packages, or other updates to an existing answer file. You can also validate an existing answer file against a Windows image to ensure that the settings in that answer file can be applied to a specific Windows image. An answer file is typically associated with a specific Windows image. By using Windows SIM, you can open the Windows image, open an existing answer file, and then make changes to the answer file.

Windows SIM validates the component settings in the answer file against the settings available in the Windows image. For more information, see Add a Component to an Answer File.

You can add device drivers during Windows Setup by using Windows SIM. Three types of drivers are used in setup:

• In-box drivers
  
  In-box drivers are handled the same as packages.
  
  
• Out-of-box drivers
  
  You can add additional .inf-based, out-of-box device drivers during Windows Setup by using Windows SIM. Typically, these out-of-box drivers are processed during the auditSystem configuration pass. Your .inf-based, out-of-box drivers must be in a distribution share subfolder called Out-of-Box Drivers. For more information, see Add Out-of-Box Drivers to a Distribution Share.
  
  
• In-box drivers installed with a Windows Installer file.
  
  In-box drivers requiring a Windows Installer file are added by the same method as applications.
  
  

  Note:

  Using the Microsoft-Windows-PnpCustomizationsWinPE component, you must add boot-critical device drivers required for installation during the windowsPE configuration pass. For more information, see Add Device Drivers by Using Windows Setup. You can also use Deployment Image Servicing and Management (DISM.exe) to add device drivers to an offline image. For more information, see Add and Remove Drivers Offline.

You can add additional applications or drivers to be installed during Windows Setup with Windows SIM by using a distribution share. You use a distribution share to store all applications, device drivers, scripts, or other resources that you make available during Windows Setup.

You can add additional applications, scripts, and other binary files by using a data image. A data image is packaged in a way that is similar to a Windows image. By using the ImageX tool, you can capture a folder structure that contains the resources that you must add to Windows (or another partition on the computer) during Windows Setup. You can specify where the data image is applied by using the DataImage setting in the Microsoft-Windows-Setup component. For more information, see Create a Data Image.

You can also use $OEM$ folder structures to place binary files and other applications in specific locations during Windows Setup. Applications are added from distribution shares through subfolders called $OEM$ folders. You must also add a RunSynchronous setting to the answer file to launch the Windows Installer file or the .exe file that installs the application. For more information, see Add Files and Folders by Using $OEM$ Folders.

Windows SIM enables the addition of offline updates to a Windows image, including software updates, device drivers, language packs, and other packages, which Microsoft provides.

Deployment Image Servicing and Management (DISM.exe) is the tool you use, with or without an answer file, to apply packages to Windows. Any package installation, removal, or modifications in the answer file is applied to the Windows image. For more information, see Add or Remove Packages Offline.

Packages that exist in the offlineServicing configuration pass are applied to the offline Windows image. For more information, see Understanding Windows Image Files and Catalog Files.

A configuration set is a subset of files that are available in a distribution share that is explicitly called in an answer file. When you create a configuration set, any files in a distribution share that are referenced in the answer file are saved to a specific folder. Paths to these files are updated in the answer file to point to the specific folder.

Configuration sets are smaller, more portable versions of a distribution share. A configuration set is ideal for installations that cannot access a distribution share. For more information, see Understanding Distribution Shares and Configuration Sets.

Windows SIM imports packages that are not part of a Windows image (.wim) file to an optional set of folders called a distribution share. The packages can then be added to an answer file from the distribution share. To import a package to a distribution share, you must use the Windows SIM tool or the CPI APIs. For more information, see Understanding Distribution Shares and Configuration Sets.

You can also import a package directly into an answer file. The answer file includes a pointer to the path of the package.

You use Windows Setup to install Windows. Windows Setup uses a new technology called image-based setup (IBS) that provides a single, unified process with which all customers—including OEMs, corporations, and retail customers—can install Windows. IBS performs both clean and upgrade installations, and you can use it in both client and server installations.

The Sysprep tool prepares a Windows image for disk imaging, system testing, or delivery to a customer. You can use the Sysprep tool to remove system-specific data, such as the security identifier (SID), from a Windows image. After removing unique system information from an image, you can capture that Windows image and use it to deploy to multiple systems.

In addition, the Sysprep tool can:

• Configure the Windows image to boot to audit mode. Audit mode enables you to test the integrity of the system and to install additional applications and device drivers.
  
  
• Configure Windows to boot to Windows Welcome the next time the computer starts.
  
  

OEMs are required to run the sysprep command with the /oobe option before delivering a computer to an end user.

ImageX (ImageX.exe) is a command-line tool that enables OEMs and corporations to capture, modify, and apply file-based disk images for rapid deployment. The ImageX tool works with Windows image (.wim) files for copying to a network, or it can work with other technologies that use Windows images, such as Windows Setup, Windows Deployment Services, and the Systems Management Server (SMS) 2003 Operating System Deployment Feature Pack.

Windows Preinstallation Environment (Windows PE) is a minimal Win32® operating system with limited services, built on the Windows 7 kernel. It is used to prepare a computer for Windows installation, to copy disk images from a network file server, and to initiate Windows Setup.