Export (0) Print
Expand All

Deployment Tools Supported Platforms

Published: October 22, 2009

Updated: November 29, 2011

Applies To: Windows 7

noteNote
This content applies to Windows 7. For Windows 8 content, see Windows Deployment with the Windows ADK.

This topic describes the supported platforms for Windows® deployment tools. All the tools mentioned are related to deploying a platform (x86-based, 64-bit version, or Itanium-based) from the corresponding deployment platforms. For a technical description of each tool, see Deployment Tools Technical Reference.

noteNote
Side-by-side installation of multiple versions of the Windows OEM Preinstallation Kit (Windows OPK) or Windows Automated Installation Kit (Windows AIK) on the same computer is not supported. Additionally, upgrading from one version of the Windows OPK or Windows AIK to a later version is not supported. For example, the Windows Vista® with Service Pack 1 (SP1) OPK needs to be uninstalled on a technician computer prior to installing the Windows® 7 OPK on the same technician computer.

In This Section

Deployment Image Servicing and Management

Deployment Image Servicing and Management (DISM) works on Windows 7, Windows Vista® with Service Pack 2 (SP2), Windows Vista with SP1, Windows Server® 2008 R2 and Windows Server® 2008 images. However, the full functionality is available only when you are servicing a Windows 7 or Windows Server 2008 R2 image. This is because the files and resources required to service any Windows image are located in the image. DISM will detect and use the resources available in the target image to update the image.

If you are servicing an image that contains Windows Vista with SP1 or SP2, or Windows Server 2008, DISM will translate the DISM command to the equivalent Package Manager command so that the image can be updated. This is why you do not get the additional functionality available in DISM when you are servicing Windows Vista with SP1 or SP2, or Windows Server 2008. However, you will not lose any functionality. DISM provides functional parity to Package Manager.

When you use DISM to service a Windows Vista with SP2, Windows Vista with SP1 or Windows Server 2008 image, note the following limitations:

  • Only offline scenarios are supported.

  • The Windows image that you are updating must be Windows Vista with SP2, Windows Vista with SP1 or Windows Server 2008.

  • Only Package Manager features are available. The new functionality in DISM, such as adding and removing drivers without an answer file, or enumerating packages and drivers, will not translate to package manager syntax.

  • You must run DISM from a full operating system or from Windows PE.

The following table provides additional information about supported platforms. The deployment platform is the operating system where DISM runs. The target platform is the image that is being serviced.

noteNote
Before servicing a Windows 7 image, or running Windows 7 setup from Windows PE 1.2, Windows XP RTM, or Windows Server 2003, you must first copy the MSXML6 binaries into your \%WINDIR%\system32 directory. MSXML6 is available on the Windows AIK and the Windows OPK media.

 

Deployment environment Target x86 platform Target x64 platform Target Itanium platform

Windows 7 or Windows Server 2008 R2 x86

Supported

Supported: target syswow64

Supported: target syswow64

Windows 7 or Windows Server 2008 R2 x64

Supported: Host syswow64

Supported

Unsupported

Windows 7 or Windows Server 2008 R2 Itanium

Supported: Host syswow64

Unsupported

Supported

Windows Vista with SP1, Windows Vista with SP2, or Windows Server 2008 x86

Supported

Supported: target syswow64

Supported: target syswow64

Windows Vista with SP1, Windows Vista with SP2, or Windows Server 2008 x64 *

Supported: Host syswow64

Supported

Unsupported

Windows Vista with SP1 , Windows Vista with SP2,or Windows Server 2008 Itanium

Supported: Host syswow64

Unsupported

Supported

Windows Server® 2003 R2 x86

Supported

Supported: Host syswow64

Supported: target syswow64

Windows Server 2003 R2 x64 *

Supported: Host syswow64

Supported

Unsupported

Windows Server 2003 R2 Itanium

Supported: Host syswow64

Unsupported

Supported

Windows PE 3.0 x86

Supported

Supported: target syswow64

Supported: target syswow64

Windows PE 3.0 x64

Unsupported

Supported

Unsupported

Windows PE 3.0 Itanium

Unsupported

Unsupported

Supported

Windows PE 2.1 x86

Supported

Supported: target syswow64

Supported: target syswow64

Windows PE 2.1 x64

Unsupported

Supported

Unsupported

Windows PE 2.1 Itanium

Unsupported

Unsupported

Supported

Windows PE 2005 (1.6) x86

Supported

Supported: target syswow64

Supported: target syswow64

Windows PE 2005 (1.6) x64

Unsupported

Supported

Unsupported

Windows PE 2005 (1.6) Itanium

Unsupported

Unsupported

Supported

* Before using DISM with the /Add-Package, /Enable-Feature or /Disable-Feature commands from a 64-bit Windows Vista , Windows Server 2008 RTM, or Windows Server 2003 R2 host, you must install a hotfix.

To service a Windows 7 image from the host environment, you must install hotfix KB960037 on the host computer. The hotfix is available on the Windows OPK and Windows AIK media, in the hotfix <%mediaroot%>\HotFix folder in one of the following locations:

  • For a 64-bit Windows Vista or Windows Server 2008 RTM host operating system, install the hotfix from: \HotFix\KB960037\WS08

  • For a 64-bit Windows Server 2003 R2 hosts operating system, install the hotfix from: \HotFix\KB960037\W2K3

Double-click the appropriate .exe file to install the hotfix.

Using Existing Package Manager Scripts

In Windows Vista with SP1, Windows Vista SP2, and Windows Server 2008, the Package Manager command-line tool was provided for updating Windows images. If you have scripts that use Package Manager, and you don’t need the additional functionality provided by DISM, you can continue to use your existing Package Manager scripts to update Windows 7 or Windows Server 2008 R2 images.

Because the resources that you need to update your image are provided in the image (Windows Vista Service Pack 1 and later), Windows 7 and Windows Server 2008 R2 images contain the logic to translate the Package Manager syntax in your script to the equivalent DISM command. However, note that none of the new functionality provided in DISM is available because you will be using Package Manager syntax, which does not include commands for the new functionality.

When you use an existing Package Manager script to update a Windows 7 image, note the following limitations:

  • Translating Package Manager scripts to DISM syntax works only when the target operating system is Windows 7 or Windows Server 2008 R2.

  • New features provided in DISM are not available.

  • Only Package Manager functionality is supported.

  • Scripts must be run from a full operating system or from Windows PE.

The following table outlines the support matrix for using existing Package Manager scripts.

 

Deployment environment Target Windows 7 or Windows Server 2008 R2 x86 platform Target Windows 7 or Windows Server 2008 R2 x64 platform Target Windows 7 or Windows Server 2008 R2 Itanium platform

Windows 7 or Windows Server 2008 R2 x86

Supported

Supported: target syswow64

Supported: target syswow64

Windows 7 or Windows Server 2008 R2 x64

Supported: Host syswow64

Supported

Unsupported

Windows 7 or Windows Server 2008 R2 Itanium

Supported: Host syswow64

Unsupported

Supported

Windows Vista with SP1, Windows Vista with SP2, or Windows Server 2008 x86

Supported

Supported: target syswow64

Supported: target syswow64

Windows Vista with SP1, Windows Vista with SP2, or Windows Server 2008 x64

Supported: Host syswow64

Supported

Unsupported

Windows Vista with SP1, Windows Vista with SP2, or Windows Server 2008 Itanium

Supported: Host syswow64

Unsupported

Supported

Windows Server 2003 R2 x86

Supported

Supported: target syswow64

Supported: target syswow64

Windows Server 2003 R2 x64

Supported: Host syswow64

Supported

Unsupported

Windows Server 2003 R2 Itanium

Supported: Host syswow64

Unsupported

Supported

Windows PE 3.0 x86

Supported

Supported: target syswow64

Supported: target syswow64

Windows PE 3.0 x64

Unsupported

Supported

Unsupported

Windows PE 3.0 Itanium

Unsupported

Unsupported

Supported

Windows PE 2.1 x86

Supported

Supported: target syswow64

Supported: target syswow64

Windows PE 2.1 x64

Unsupported

Supported

Unsupported

Windows PE 2.1 Itanium

Unsupported

Unsupported

Supported

Windows PE 2005 (1.6) x86

Supported

Supported: target syswow64

Supported: target syswow64

Windows PE 2005 (1.6) x64

Unsupported

Supported

Unsupported

Windows PE 2005 (1.6) Itanium

Unsupported

Unsupported

Supported

ImageX

The following table lists Windows operating systems and the supported list of architecture types that you can use to mount, view, apply, and modify images.

 

Operating system Architecture types

Windows XP with Service Pack 2 (32-bit version)

x86-based, x64-based, Itanium-based

Windows XP with Service Pack 2 (64-bit version)

x86-based, x64-based, Itanium-based

Windows Vista with Service Pack 2 (32-bit version)

x86-based, x64-based, Itanium-based

Windows Vista SP2 (64-bit version)

x86-based, x64-based, Itanium-based

Windows 7 (32-bit version)

x86-based, x64-based, Itanium-based

Windows 7 (64-bit version)

x86-based, x64-based, Itanium-based

Windows Server 2003 Service Pack 2 (32-bit version)

x86-based, x64-based, Itanium-based

Windows Server 2003 Service Pack 2 (64-bit version)

x86-based, x64-based, Itanium-based

Windows Server 2008 (32-bit version)

x86-based, x64-based, Itanium-based

Windows Server 2008 (64-bit version)

x86-based, x64-based, Itanium-based

Windows Server 2008 (Itanium-based)

x86-based, x64-based, Itanium-based

Windows Server 2008 R2 (64-bit version)

x86-based, x64-based, Itanium-based

Windows Server 2008 R2 (Itanium-based)

x86-based, x64-based, Itanium-based

Windows PE 2005 (1.6) (32-bit version)

x86-based, x64-based, Itanium-based

ImageX does not support read or mount operations from a Windows PE environment.

Windows PE 2005 (1.6) (64-bit version)

x86-based, x64-based, Itanium-based

ImageX does not support read or mount operations from a Windows PE environment.

Windows PE 2.0 (32-bit version)

x86-based, x64-based, Itanium-based

ImageX does not support read or mount operations from a Windows PE environment.

Windows PE 2.0 (64-bit version)

x86-based, x64-based, Itanium-based

ImageX does not support read or mount operations from a Windows PE environment.

Windows PE 3.0 (32-bit version)

x86-based, x64-based, Itanium-based

Windows PE 3.0 (64-bit version)

x86-based, x64-based, Itanium-based

Windows Setup

The following table lists Windows operating systems and the supported list of architecture types on which you can install Windows.

 

Operating system Architecture types

SP3 (32-bit version)

x86-based

SP3 (64-bit version)

x86-based, x64-based

Windows Vista SP1 and SP2 (32-bit version)

x86-based

Windows Vista SP1 and SP2 (64-bit version)

x86-based, x64-based

Windows 7 (32-bit version)

x86-based

Windows 7 (64-bit version)

x86-based, x64-based

Windows Server 2003 SP2 (32-bit version)

x86-based

Windows Server 2003 SP2 (64-bit version)

x86-based, x64-based

Windows Server 2008 (32-bit version)

x86-based

Windows Server 2008 (64-bit version)

x86-based, x64-based

Windows Server 2008 (Itanium-based)

Itanium-based

Windows Server 2008 R2 (64-bit version)

x86-based, x64-based

Windows Server 2008 R2 (Itanium-based)

Itanium-based

Windows PE 2005 (1.6) (32-bit version)

x86-based

Windows PE 2005 (1.6) (64-bit version)

x64-based

Windows PE 2.0 (32-bit version)

x86-based, x64-based

Windows PE 2.0 (64-bit version)

x64-based

Windows PE 3.0 (32-bit version)

x86-based

Windows PE 3.0 (64-bit version)

x64-based

   
   

Windows System Image Manager

The 32-bit version of Windows System Image Manager (Windows SIM) can create and open catalog files (.clg) for Windows images of all architecture types. The 64-bit versions of Windows SIM could create catalog files only for 64-bit Windows images. For example, the AMD64 version of SIM can create catalogs only of AMD64-based Windows images.

After the catalog file is created, Windows SIM can open catalog files for all Windows image architecture types.

Windows PE is not a supported platform for Windows SIM.

The following table lists Windows operating systems and the supported list of architecture types on which you can create catalog files for Windows images.

 

Operating system Architecture types

Windows Vista SP1 and SP2 (32-bit version)

x86-based, x64-based, Itanium-based

Windows Vista SP1 and SP2 (64-bit version)

x64-based only

Windows 7 (32-bit version)

x86-based, x64-based, Itanium-based

Windows 7 (64-bit version)

x64-based only

Windows Server 2003 SP2 (32-bit version)

x86-based, x64-based, Itanium-based

Windows Server 2003 SP2 (64-bit version)

x64-based only

Windows Server 2008 (32-bit version)

x86-based, x64-based, Itanium-based

Windows Server 2008 (64-bit version)

x64-based only

Windows Server 2008 (Itanium-based)

Itanium-based only

Windows Server 2008 R2 (64-bit version)

x64-based only

Windows Server 2008 R2 (Itanium-based)

Itanium-based only

Windows Preinstallation Environment

The following table lists the Windows Preinstallation Environment (Windows PE) release and corresponding Windows AIK version and operating system.

 

Windows PE release Windows AIK version Operating system

1.0

n/a

Windows XP RTM

1.1

n/a

Windows XP SP1

1.2

n/a

Windows XP SP1, Windows Server 2003 RTM

2004 (1.5)

n/a

Windows XP SP2

2005 (1.6)

n/a

Windows Server 2003 SP1

2.0

1.0

Windows Vista RTM

2.1

1.1

Windows Vista SP1, Windows Server 2008

2.2

n/a

Windows Vista SP2, Windows Server 2008 SP1

3.0

2.0

Windows 7 RTM

WarningWarning
Installation of Windows (64-bit version) from cross-platform media, such as Windows PE (32-bit version), to a Microsoft® Internet SCSI (iSCSI) boot disk is unsupported for Windows Vista, Windows Server 2008, and Windows Server 2008 R2. For these operating systems you must use the same architecture for Windows PE as the target deployment architecture when you deploy Windows to an iSCSI boot disk. For more information, see the following websites:

To identify the Windows PE release that you are running

  1. From a Windows PE command prompt, enter regedit.

  2. Navigate to HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\WinPE.

    The Version registry value of type REG_SZ lists the Windows PE version.

See Also

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft