This checklist outlines the steps you should take to upgrade Microsoft System Center Configuration Manager 2007 sites to Configuration Manager 2007 Service Pack 1 (SP1). 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 SP1 if it has already been extended for Configuration Manager 2007. |
Upgrading Configuration Manager Sites to Configuration Manager 2007 SP1
The following checklist provides the recommended steps to upgrade Configuration Manager 2007 sites to Configuration Manager 2007 SP1.
| Step | Reference | ||
|---|---|---|---|
|
Ensure your computing environment meets the supported configurations required for upgrading to Configuration Manager 2007 SP1. |
|||
|
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) |
||
|
The Windows Automated Installation Kit (Windows AIK) version 1.0 must be uninstalled from the SMS Provider computer and the computer must be restarted before beginning the upgrade process.
|
Internal process that is company-specific. |
||
|
If you are using SQL Server Database Replication, disable it before upgrading. |
|||
|
Back up your sites. |
|||
|
If you have SMS 2003 clients in the site, apply hotfix 945635. |
Article 945635 (http://go.microsoft.com/fwlink/?LinkId=107344) |
||
|
If you are using the software updates feature, upgrade Windows Server Update Services (WSUS) to WSUS SP1 on your software update points. |
|||
|
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. For example, Web-based Distributed Authoring and Versioning (WebDAV) is required for Configuration Manager management points and BITS-enabled distribution points, but Windows Server 2008 operating system does not automatically install WebDAV. Site servers and branch distribution points require Remote Differential Compression (RDC) to generate package signatures and perform signature comparison. RDC is not installed by default on computers running Windows Server 2008.
|
|||
|
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. |
|||
|
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.
|
|||
|
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, administrator consoles, and clients. |
Configuration Manager Tasks for Upgrade and Interoperability |
||
|
If you are using SQL Server Database Replication, reconfigure it after upgrading. |
|||
|
Verify that the site installed. |
|||
|
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 |
ImportantEffects on Boot Images when Upgrading to Configuration Manager 2007 SP1
When a Microsoft System Center Configuration Manager 2007 site is upgraded to Configuration Manager 2007 SP1, the Windows Automated Installation Kit (Windows AIK) is not automatically upgraded from version 1.0 to version 1.1. Before upgrading the site to Configuration Manager 2007 SP1, Windows AIK 1.0 must be uninstalled from the SMS Provider computer and the computer must be restarted.
Existing default boot images named Boot image (x86) and Boot image (x64) are recreated under the Boot Images node. The boot images are based on the Windows PE that is included in the Windows AIK version 1.1. If you have customized the default boot images but kept the default names, the customizations will be lost as part of the upgrade process. The device driver additions from the Configuration Manager Drivers node will continue to be included in the recreated boot images and will not be lost.