The following table describes the operating systems supported for Configuration Manager 2007 SP2 computer client installation. For a list of computer client hardware requirements, see Configuration Manager Supported Configurations.

Note

Microsoft provides support for the current service pack and, in some cases, the immediately preceding service pack. To find the support timelines for your product, visit the Lifecycle Supported Service Packs Web site at http://go.microsoft.com/fwlink/?LinkId=31975. For additional information about Microsoft support lifecycle policy, visit the Microsoft Support Lifecycle Support Policy FAQ Web site at http://go.microsoft.com/fwlink/?LinkId=31976.

¹Windows 2000 Datacenter Server and Windows Server 2003 Datacenter Edition are supported but not certified for Configuration Manager 2007 SP2. Hotfix support is not offered for issues specific to Windows 2000 Datacenter Server and Windows Server 2003 Datacenter Edition.

²Clients are supported on the Server Core installations and full installations of Windows Server 2008. However, desired configuration management and out of band management are supported only on full installations of Windows Server 2008. Desired configuration management is supported on Server Core installations of Windows Server 2008 R2 if the Microsoft .NET Framework 2.0 is included.

³ Configuration Manager 2007 SP2 support for x64 and Itanium-based systems is through 32-bit code running on 64-bit operating systems.

⁴Only Windows Embedded 2009 and Windows Embedded Standard 7 are supported for operating system deployment. For information about Windows Embedded support limitations, see Known Limitations in Configuration Manager Support for Windows Embedded.

The following table describes the operating systems supported for Configuration Manager 2007 SP2 mobile device client installation. For a list of mobile device hardware requirements, see Configuration Manager Supported Configurations.

Operating System	Edition
Windows Mobile for Pocket PC	2003, 2003 Second Edition, Phone Edition 2003, Phone Edition 2003 Second Edition, 5.0, or Phone Edition 5.0 Note Password management on Windows Mobile for Pocket PC 5.0 and Windows Mobile for Pocket PC Phone Edition 5.0 requires the Messaging and Security Feature Pack (MSPF). For more information, see the Windows Mobile Messaging and Security Feature Pack Web page (http://go.microsoft.com/fwlink/?LinkId=80392).
Windows Mobile	Smartphone 2003, 5.0 Smartphone, 6 Standard, 6 Professional, 6 Classic, 6.1 or 6.5 Note Password management is not supported for Windows Mobile Smartphone 2003. Password management on Windows Mobile 5.0 Smartphone requires the Messaging and Security Feature Pack (MSPF). For more information, see the Windows Mobile Messaging and Security Feature Pack Web page (http://go.microsoft.com/fwlink/?LinkId=80392).
Windows CE	4.2 (ARM processor only), 5.0 (ARM and x86 processors), or 6.0 (ARM and x86 processors) Important Windows CE 6.0 is supported in Configuration Manager 2007 SP2 only after installing Hotfix 977384 on the site server computer. For information about this issue and to download this hotfix, see Article 977384 in the Microsoft Knowledge Base (http://go.microsoft.com/fwlink/?LinkId=180992). Note Windows CE 4.2 support requires the mobile device client distributed with the System Management Server (SMS) 2003 Device Management Feature Pack. This client supports hardware inventory, software inventory, file collection, and software distribution only in mixed mode. Windows CE 4.2 is not supported in native mode. For more information about the SMS 2003 Mobile Device Feature Pack, see SMS 2003 Device Management Feature Pack (http://go.microsoft.com/fwlink/?LinkId=129496).

Some Configuration Manager 2007 client features, such as operating system deployment, are not supported for the mobile device client. For more information about managing devices with Configuration Manager, see Overview of Mobile Device Management.

The following sections list the site system operating system requirements for Configuration Manager 2007 core and feature-specific site system role installations. For information about the minimum hardware requirements for Configuration Manager 2007 site systems, see Configuration Manager Supported Configurations.

Note

Microsoft provides support for the current service pack and, in some cases, the immediately preceding service pack. To find the support timelines for your product, visit the Lifecycle Supported Service Packs Web site at http://go.microsoft.com/fwlink/?LinkId=31975. For additional information about the Microsoft support lifecycle policy, visit the Microsoft Support Lifecycle Support Policy FAQ Web site at http://go.microsoft.com/fwlink/?LinkId=31976.

Feature-Specific Site System Requirements

No new site system roles have been added for Configuration Manager 2007 SP2.

The following table lists the site system operating system requirements for Configuration Manager 2007 SP2 feature-specific site system role installation.

¹Site system roles are not supported on Server Core installations of Windows Server 2008 or Windows Server 2008 Foundation. For more information about configuration requirements for hosting site system roles on Windows Server 2008, see How to Configure Windows Server 2008 for Site Systems.

²To use graphs in reports, Office Web Components (Microsoft Office 2000 with SP2, Microsoft Office XP, or Microsoft Office 2003) must be installed. However, Office Web Components is not supported on 64-bit operating systems. If you want to use graphs in reports, use 32-bit operating systems for your reporting points.

³Out of band service points are not supported on computers that are running Windows Server 2003 with SP1. Out of band service points running Windows Server 2003 with SP2 require KB 942841. More information about KB 942841 is available at http://go.microsoft.com/fwlink/?LinkId=155114.

⁴A Software update point installed on Windows Server 2003 with SP1 cannot support patching of Windows 7 or Windows Server 2008 R2 clients. Windows Server Update Services (WSUS)  3.0 SP2 is required to support computers running Windows 7 or Windows Server 2008 R2 and WSUS 3.0 SP2 is not supported on Windows Server 2003 with SP1. For information about WSUS 3.0 SP1 and SP2 installation requirements, see the Release Notes for Microsoft Windows Server Update Services 3.0 SP1 Web Page at http://go.microsoft.com/fwlink/?LinkId=196097, and the WSUS 3.0 SP2 Installation of Required Software Web site at http://go.microsoft.com/fwlink/?LinkId=196098.

Unless explicitly specified, the list of unsupported operating system platforms has not changed for Configuration Manager 2007 SP2 from those listed in Configuration Manager Supported Configurations. However, additional operating systems can be past the service pack support dates.

To find the support timelines for your product, visit the Lifecycle Supported Service Packs Web site at http://go.microsoft.com/fwlink/?LinkId=31975. For additional information about the Microsoft support lifecycle policy, visit the Microsoft Support Lifecycle Support Policy FAQ Web site at http://go.microsoft.com/fwlink/?LinkId=31976.

The following information describes changes to supported operating systems in Configuration Manager 2007 SP2 from those listed in Configuration Manager Supported Configurations.

• Windows Server 2008 Foundation operating system installations are not supported.
  
  

Configuration Manager 2007 SP2 does not introduce changes to Active Directory schema extension requirements, and it is not necessary to re-extend the Active Directory schema for Configuration Manager 2007 SP2 if it has already been extended for Configuration Manager 2007.

When installing Configuration Manager 2007 SP2, the site database can be installed on either the default instance or a named instance of a supported Microsoft SQL Server version installation. The instance that is used to host the site database can also be configured as an instance of the SQL Server failover cluster in an active/passive cluster, or multiple instance, configuration.

The following table describes the versions of SQL Server supported to host the Configuration Manager 2007 SP2 site database.

Note
Installing the site database on Itanium 64-bit platforms is not supported.

Out of band management in Configuration Manager 2007 SP2 is supported for computers that have the Intel vPro chip set and Intel Active Management Technology (Intel AMT) for the following firmware versions:

• Intel AMT version 3.2 with a minimum revision of 3.2.1
  
  
• Intel AMT version 4.0, version 4.1, and version 4.2
  
  
• Intel AMT version 5.0, and version 5.2 with a minimum revision of 5.2.10
  
  

802.1X authenticated wired networks are not supported by Configuration Manager 2007 SP2 for AMT versions before 4.0.

In-band provisioning is not supported on AMT-based computers that are running any version of Windows Server, Windows 2000, Windows XP with SP2, or Windows XP Tablet PC Edition.

The out of band management console is not supported on workstations running Windows XP on versions earlier than Service Pack 3, and on servers running Windows Server 2003 on versions earlier than Service Pack 2.

Out of band communication is not supported to an AMT-based computer that is running the Routing and Remote Access service in the client operating system. This service runs when Internet Connection Sharing is enabled, and the service might be enabled by line-of-business (LOB) applications.

For more information about out of band management in Configuration Manager 2007 SP2, see Out of Band Management in Configuration Manager 2007 SP1 and Later.

The BranchCache feature in Windows Server 2008 R2 is supported for Configuration Manager 2007 SP2 sites when BranchCache is configured for the distributed cache mode only. When all the requirements for BranchCache are met, this feature enables clients at remote locations to obtain content from local clients that have a current cache of the content.

For example, when the first BranchCache-enabled client computer requests content from a distribution point that is running Windows Server 2008 R2 and that has also been configured as a BranchCache server, the client computer will download the content and cache it. This content is then made available for clients on the same subnet that request this same content, and these clients also cache the content. In this way, subsequent clients on the same subnet do not have to download content from the distribution point, and the content is distributed across multiple clients for future transfers.

Configuration Manager 2007 SP2 supports BranchCache with Windows Server 2008 R2 and Windows 7 clients that are configured in BranchCache distributed cache mode. Support is extended to clients running Windows Vista SP1 and later, Windows Server 2008 SP1, and Windows Server 2008 SP2 by using the BITS 4.0 release. However, on these operating systems the BranchCache client functionality is not supported for software distribution that is run from the network or for SMB file transfers. The BITS 4.0 release can be installed on Configuration Manager clients by using software updates or software distribution. For more information about the BITS 4.0 release, see the Windows Management Framework (http://go.microsoft.com/fwlink/?LinkId=181979).

To support BranchCache with Configuration Manager, add the BranchCache feature to the Windows Server 2008 R2 site system server that is configured as a standard distribution point. In Configuration Manager, the distribution point must be configured with the Allow clients to transfer content from this distribution point using BITS, HTTP, and HTTPS option. To use BranchCache with software distribution and task sequences, advertisements must be configured by using the Download content from distribution point and run locally option. To use BranchCache with software updates, the software update deployment must be configured by using the Download software updates from distribution point and install option. Additionally, the clients that are capable of supporting BranchCache must be configured for BranchCache distributed mode and the operating system setting for BITS client settings must be enabled to support BranchCache.

For more information about BranchCache, see BranchCache for Windows Server 2008 R2 (http://go.microsoft.com/fwlink/?LinkId=177945).

The DirectAccess feature in Windows Server 2008 R2 is supported for Configuration Manager 2007 SP2 sites with the full intranet access model only. When all the requirements for DirectAccess are met, this feature allows native mode and mixed mode Configuration Manager clients on the Internet to communicate with their assigned site just as if they are on the intranet.

For more information about DirectAccess, see DirectAccess for Windows Server 2008 R2 (http://go.microsoft.com/fwlink/?LinkId=178017).

This section describes important upgrade considerations for Configuration Manager 2007 SP2. For additional information about upgrading to Configuration Manager 2007 SP2, see Configuration Manager 2007 SP2 Upgrade Checklist.

Windows Automated Installation Kit (Windows AIK) Requirements

Operating System Deployment in Configuration Manager 2007 SP2 requires the Windows 7 Windows Automated Installation Kit 2.0 release (version 6.1.7600).

The Windows AIK (version 1.0 for Configuration Manager 2007 or version 1.1 for Configuration Manager 2007 SP1) must be uninstalled from the SMS Provider computer and the computer must be restarted before beginning the upgrade process. When the site is upgraded to SP2, the Windows AIK 2.0 will be installed on the SMS Provider computer.

Note

The default boot images Boot image (x86) and Boot image (x64) under the Boot Images node will be replaced with new boot images based on Windows Preinstallation Environment (Windows PE) 3.0 from the Windows AIK 2.0. When the default boot images have been customized and use the default names, the customizations will be lost as part of the upgrade process. Device driver additions from the Configuration Manager Drivers node will be maintained in the new boot images. We recommend that existing boot images are backed up before upgrading to Configuration Manager 2007 SP2.

Windows AIK 2.0 supports deployment of the following operating systems:

• Windows Vista with SP1
  
  
• Windows 7
  
  
• Windows Server 2008
  
  
• Windows Server 2008 R2
  
  

Operating systems that do not require Windows AIK, including Windows 2000, Windows XP, and Windows Server 2003, can be deployed by using Configuration Manager 2007 SP2.

Important
Operating System Deployment in Configuration Manager 2007 SP2 only supports capturing or applying Windows Vista operating system images for Windows Vista with SP1 because Windows AIK 2.0 does not support Windows Vista without a service pack.