Configuration Manager 2007 Upgrade Checklist

Applies To: System Center Configuration Manager 2007, System Center Configuration Manager 2007 R2, System Center Configuration Manager 2007 R3, System Center Configuration Manager 2007 SP1, System Center Configuration Manager 2007 SP2

This checklist outlines the steps you should take to upgrade SMS 2003 Service Pack 2, or above, sites to Microsoft System Center Configuration Manager 2007. It is intended to provide a high-level list of items to consider when upgrading or to provide guidance for new installations of Configuration Manager 2007. For information about performing a new installation of Configuration Manager 2007, see Planning and Deploying the Server Infrastructure for Configuration Manager 2007.

Upgrading from SMS 2003 Sites to Configuration Manager 2007

The following checklist provides the recommended steps to upgrade a Microsoft Systems Management Server (SMS) 2003 Service Pack 2, or above, sites to Configuration Manager 2007:

Step Reference

Complete the necessary planning required before beginning the upgrade process. Understand your business needs and how you will use Configuration Manager features to support them. This planning process might cause you to decide to make major design changes to your existing SMS 2003 hierarchy before or during the upgrade process.

Planning to Upgrade to Configuration Manager

Ensure your computing environment meets the supported configurations required for upgrading to Configuration Manager 2007.

Configuration Manager Supported Configurations

Review the prerequisites and considerations for upgrading to Configuration Manager 2007 before beginning the upgrade process.

Considerations for Upgrading Sites

Prerequisites for Upgrading to Configuration Manager

Determine readiness for upgrading. Verify that each primary site, secondary site, Configuration Manager 2007 provider computer, and SMS 2003 Administrator Console has the necessary prerequisite software installed and configured in preparation for upgrade to Configuration Manager 2007.

Prerequisites for Installing Configuration Manager

Setup Prerequisite Checks

There are two prerequisites that are not detected by the prerequisite checker and are not listed in other prerequisite documentation. You must manually apply the following hotfixes prior to running Setup:

  • 940848

  • 941132

Microsoft Knowledge Base article 940848 (

Microsoft Knowledge Base article 941132 (

Test the database upgrade process on a copy of the most recent SMS 2003 site database back up. During the upgrade process, the site database may be modified. If the upgrade fails or is canceled for any reason, you should create a new copy of the back up to ensure a valid site database backup is available for testing.

How to Test the Site Database Upgrade Process

If you have extended your Active Directory schema for SMS 2003, it is recommended that you update the schema extensions for Configuration Manager 2007. Schema extensions are not required, but they do provide many benefits.

If you have previously extended the Active Directory schema for SMS 2003, and will be using the ConfigMgr_ad_schema.ldf file to extend the Active Directory schema for Configuration Manager, review the manual procedures necessary for successfully storing all required attributes.

You can extend the schema before or after running Configuration Manager Setup, but it is recommended that you extend the schema before running setup.

Decide If You Should Extend the Active Directory Schema

How to Extend the Active Directory Schema for Configuration Manager

How to Extend the Active Directory Schema Using an LDIF File

If you have customized the default SMS_def.mof hardware inventory reporting file, you must create a backup of this file before upgrading the site. When upgrading a site, customizations made to the existing SMS_def.mof file will be overwritten.

Modifying the Default Configuration Manager SMS_def.mof File Before Upgrading

Because Configuration Manager sites require secure key exchange by default, it is recommended that you configure SMS 2003 sites to be upgraded to also require secure key exchange before beginning the upgrade process. Secure key exchange requirements are configured for a site on the advanced tab of the site properties.

If the Active Directory schema has not been extended (either for SMS 2003 or Configuration Manager) or the site is not configured to publish site data to Active Directory, you must manually exchange public keys between sites when secure key exchange is required.

Site Properties: Advanced Tab

How to Manually Exchange Public Keys Between Sites

If the planned site server computer does not have Internet access, the Prerequisite Component Update Checker must be started on a different computer with Internet access. To start the Prerequisite Component Update Checker to download updated client installation prerequisite components, use the Setup command-line option of Setup /download <path>. When downloading prerequisite update files from a different computer, ensure that the download path specified will be accessible to planned site system computers when the Setup Wizard is run and that an alternate path is used to obtain client prerequisite component files.

Prerequisite Component Update Checker

Upgrade the hierarchy. Begin by upgrading the central site, and then upgrade from the top of the hierarchy down. After the primary sites are upgraded, begin upgrading their associated secondary sites, administrator consoles, and finally, clients.


SMS 2003 primary sites cannot be managed by a Configuration Manager console installed on a Configuration Manager primary site server. If the site to be upgraded is a parent site to one or more SMS 2003 primary sites, ensure that you have installed a remote SMS 2003 Administrator Console to manage those sites.

Configuration Manager Tasks for Upgrade and Interoperability

After upgrading each site, you must manually grant permissions to administrators who need access to the site's Configuration Manager console and site objects.

When you upgrade from SMS 2003, the user performing the upgrade receives administrator rights for all of the objects in the Configuration Manager 2007 console. However, if you had additional users configured with Configuration Manager rights, they do not receive rights to new objects.

For more information about Configuration Manager object security, see Overview of Configuration Manager Object Security and WMI.

How to Assign Rights for Objects to Users and Groups

See Also

Other Resources

Configuration Manager Upgrade and Interoperability Planning and Deployment

For additional information, see Configuration Manager 2007 Information and Support.
To contact the documentation team, email