This checklist outlines the steps you should take to upgrade Microsoft System Center Configuration Manager 2007 sites to Configuration Manager 2007 Service Pack 2 (SP2). It is intended to provide a high-level list of items to consider when applying the service pack. For information about performing a new installation of Configuration Manager 2007, see Planning and Deploying the Server Infrastructure for Configuration Manager 2007. For information about upgrading sites in Systems Management Server (SMS) 2003 Service Pack 2 or later to Configuration Manager 2007, see Configuration Manager 2007 Upgrade Checklist.
 Note |
|---|
| 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. |
Upgrading Configuration Manager Sites to Configuration Manager 2007 SP2
The following checklist provides the recommended steps to upgrade Configuration Manager 2007 sites to Configuration Manager 2007 SP2.
| Step | Reference | ||
|---|---|---|---|
|
Ensure your computing environment meets the supported configurations required for upgrading to Configuration Manager 2007 SP2. |
|||
|
Verify that you do not have any unresolved issues with the site by checking the site status messages. |
Using Status Messages for Configuration Manager Troubleshooting |
||
|
Install any critical Microsoft Windows updates on your site servers and site systems. |
Windows Update (http://go.microsoft.com/fwlink/?LinkId=105851) |
||
|
Install any critical Microsoft SQL Server updates on your site database servers. |
Windows Update (http://go.microsoft.com/fwlink/?LinkId=105851) |
||
|
Uninstall the Windows Automated Installation Kit (Windows AIK) version 1.1 from the SMS Provider computer and then restart the computer before beginning the upgrade process.
|
Internal process that is company-specific. |
||
|
Disable SQL Server Database Replication before upgrading your site. |
|||
|
Back up your sites. |
|||
|
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 |
||
|
Run the Setup Prerequisite Checker. |
|||
|
Verify that all site systems, including the primary site, secondary site, Configuration Manager 2007 provider computer, and Configuration Manager 2007 consoles meet any new prerequisite requirements.
|
|||
|
Test the database upgrade process on a copy of the most recent Configuration Manager 2007 site database backup. During the upgrade process, the site database might be modified. If the upgrade fails or is canceled for any reason, you should create a new copy of the backup to ensure a valid site database backup is available for testing. |
|||
|
Start the Prerequisite Component Update Checker on a site server computer that has 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.
|
|||
|
Restart the site server and site systems to ensure that there are no pending actions from installing updates or prerequisites. |
Internal process that is company-specific. |
||
|
Select Configuration Manager 2007 from the autorun screen, or start Setup.exe from the Configuration Manager installation media or from a copy of the installation media located on a network share or other storage media to start the Configuration Manager Setup Wizard. |
Configuration Manager Tasks for Upgrade and Interoperability |
||
|
After upgrading the central site, upgrade the rest of the hierarchy from the top down. After the primary sites are upgraded, begin upgrading their associated secondary sites, and administrator consoles.
|
Configuration Manager Tasks for Upgrade and Interoperability How to Manually Request Asset Intelligence Catalog Synchronization |
||
|
Reconfigure SQL Server Database Replication after upgrading. |
|||
|
Verify that the site installed successfully. |
|||
|
If you use a customized SMS_def.mof file, edit the SMS_def.mof file on the site server to add your customizations. Use your backup copy of the SMS_def.mof file as a reference. |
Modifying the Default Configuration Manager SMS_def.mof File Before Upgrading |
||
|
Upgrade the clients. Clients do not automatically update as a result of the site upgrade. Client upgrade methods include using software distribution and the supplied package definition file, the Client Push wizard, and the software update point. |
How to Upgrade Clients Using Software Distribution in Configuration Manager |
Important