Planning the SMS 2003 Software Updates Upgrade
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
There are important areas to consider when planning for software updates before and after a site upgrade from Systems Management Server (SMS) 2003 to Configuration Manager 2007. This section provides information about what software update information is upgraded and provides information about scanning computers for software updates compliance, software updates metadata, software updates synchronization, deploying software updates, and using software updates reporting. The information in this section assumes that the inventory scan tools have been installed on the highest site server in the SMS 2003 hierarchy, most likely the central site server. It also assumes that the site server highest in the hierarchy is the first site server upgraded to Configuration Manager 2007.
For the most recent planning information, see the online version at http://go.microsoft.com/fwlink/?LinkId=92773.
For more information about upgrading from SMS 2003 to Configuration Manager 2007, as well as best practices and interoperability between the two versions, see the "System Center Configuration Manager 2007 Software Update Management Guidance - Migration from SMS 2003 Inventory Tool for Microsoft Updates" whitepaper at http://go.microsoft.com/fwlink/?LinkId=103710.
Upgraded Software Updates Metadata
The site server upgrade from SMS 2003 to Configuration Manager 2007 updates the SMS 2003 files and the Microsoft SQL Server database. The upgrade details are logged in the %systemdrive%\ConfigMgrSetup.log. For more information about the upgrading your site to Configuration Manager 2007, see Configuration Manager Upgrade and Interoperability Planning and Deployment.
During the site upgrade, the following software updates information is migrated from the SMS 2003 schema to the Configuration Manager 2007 schema:
Existing SMS 2003 software update distributions will be migrated and continue to work as expected only when the advertisement and program for the distribution is created at the site that is being upgraded. Software update installation programs created at the site being upgraded will not be migrated if the advertisement for the program was created at a child site. The programs that are not migrated will continue to work on SMS 2003 clients, but Configuration Manager client computers will not retrieve the updates deployed using these installation programs.
Information about the installed version of the Inventory Tool for Microsoft Updates. Other inventory scan tools are not compatible with Configuration Manager 2007, and information about these tools will not be migrated.
Software updates metadata, such as the name, description, applicability rules, article ID, the URL to more information about the update, the bulletin ID, the path to the software update source files, the associated product for the update, and so forth. Until the software updates are synchronized, all updates will be put in an expired state and their titles will be displayed in the Configuration Manager console with (LEGACY) appended to the end of the title.
Before upgrading, verify that you have a valid package source for each package. If the package source is not valid, you must re-download all of the content in the package source or the package source validation check will fail and the content will be invalidated.
Compliance information for the software updates, such as the number of scanned clients in which the software update is required or not required.
Client status information, such as the revision for the Microsoft Update catalog that is used by clients when scanning for software updates compliance.
Security rights for SMS 2003 objects that were migrated to Configuration Manager 2007.
After upgrading a site server, the user who ran the upgrade has access to all of the software updates objects in the Configuration Manager console but other administrators have access only to objects that existed prior to upgrade. For example, users who had full rights to all SMS 2003 software updates objects will have full rights to the same objects in Configuration Manager 2007 but will not have any rights to new object types such as deployment templates.
Scanning for Software Update Compliance After a Site Upgrade
There are several inventory scan tools in SMS 2003 that scan client computers for software update compliance. When a site is upgraded to Configuration Manager 2007, the Inventory Tool for Microsoft Updates is fully operational on all client computers, the Inventory Tool for Custom Updates is supported, but with conditions, and the other scan tools have very limited support.
Inventory Tool for Microsoft Updates
During the SMS 2003 site upgrade to Configuration Manager 2007, Setup detects whether a previous version of the Inventory Tool for Microsoft Updates is installed on the site and verifies that another installation of the tool is not installed on a site higher in the hierarchy. If both are true, Setup initiates an upgrade for the inventory tool on the site server. During the installation, you can specify whether to download the latest Microsoft Update catalog from the Internet or from a local location.
After the Inventory Tool for Microsoft Updates is upgraded on the site, the catalog will be synchronized with the latest Microsoft Updates catalog, the scan package will be updated, and client computers will upgrade the scan tool following their next machine policy cycle.
During the June 10, 2008 release of the Microsoft Update catalog, additional metadata that is associated with Microsoft Office 2003 Service Pack 1 was added to the Wsusscn2.cab file. The catalog synchronization process (UpdateWUSCatalog.exe) was not designed to handle the specific changes, and as a result, synchronization for the Inventory Tool for Microsoft Updates fails and the latest updates are not available to SMS 2003 clients. To resolve this issue, a change has been made to the UpdateWUSCatalog.exe file to accommodate the new metadata. The update must be installed on the Configuration Manager site server, and then catalog synchronization must be manually run before a client using the Inventory Tool for Microsoft Updates will successfully scan for software updates. The update is available and described in Knowledge Base article 954474 (http://go.microsoft.com/fwlink/?LinkId=123771).
The client will scan for software updates compliance using the Microsoft Update catalog. Only SMS 2003 clients should be in the target collection for the Microsoft Updates Tool advertisement. The Inventory Tool for Microsoft Updates is supported only for SMS 2003 clients in the hierarchy. Configuration Manager 2007 client computers must use the software updates feature. For more information, see Administrator Checklist: Assessing and Deploying Software Updates.
When all client computers in the hierarchy have been upgraded to Configuration Manager 2007, the Inventory Tool for Microsoft Updates should be removed from the site server.
Inventory Tool for Custom Updates
After a site upgrade, SMS 2003 clients in the hierarchy will continue to scan custom software updates for compliance using the scan package for the Inventory Tool for Custom Updates. For Configuration Manager client computers to scan for the custom software updates, the custom catalog must be republished to the update server using System Center Updates Publisher, and then the software update point must be synchronized with the published updates.
Other Inventory Scan Tools
After a site upgrade, scanning for update compliance using all other inventory scan tool catalogs is supported only for SMS 2003 client computers in the hierarchy. Configuration Manager 2007 client computers do not support the inventory tools for other scan tools.
Synchronizing Software Updates After a Site Upgrade
During a site server upgrade, all software updates are migrated into the Configuration Manager 2007 database and the Expired attribute for each update is set to Yes, putting them in an expired state. Before Configuration Manager client computers are able to scan for software update compliance and before software update deployments can be created at the site server, the updates must be put back into an active state by running software updates synchronization.
Synchronizing the Microsoft Updates Catalog
After the Inventory Tool for Microsoft Updates is upgraded, the Microsoft Updates catalog is automatically synchronized using the Microsoft Updates Tool Sync advertisement. When it is complete, the synchronized software updates from the Microsoft Updates catalog are reset to an active state.
The synchronization task for the Inventory Tool for Microsoft Updates might take longer than an hour complete.
Synchronizing the Software Update Point
After a site upgrade, the software update point site role must be created and configured and then synchronized with the Windows Server Update Services (WSUS) server. For more information about creating the software update point, see How to Add the Software Update Point Site Role to a Site System. For more information about synchronizing the software updates point, see How to Synchronize Software Updates.
Software updates from only the Microsoft Updates and custom software updates catalogs can be synchronized. All other software updates will remain in an expired state, will not be scanned for software update compliance on Configuration Manager client computers, cannot be deployed to client computers from the Configuration Manager site server, and will eventually be removed from the Configuration Manager site database.
LEGACY Appended to Migrated Software Updates Metadata
During the upgrade process, Configuration Manager 2007 Setup appends (LEGACY) to the title for each software update. This helps you identify software updates that were migrated among the new software updates metadata that is synchronized after the upgrade. Software updates with (LEGACY) in the title should not be deployed to clients and are only migrated for migrated software update distributions and for reporting purposes. You can run a script to hide these software updates in the Configuration Manager console so only deployable software updates are displayed. A sample script is available from the Microsoft Script Center Script Repository (http://go.microsoft.com/fwlink/?LinkId=102377).
Migrated software updates that are in a software update deployment that was also migrated will not be hidden until the migrated deployment is deleted or the updates are removed from the deployment.
Republishing the Custom Updates Catalog
Custom catalogs that have been published to the site server using the Custom Updates Publishing Tool must be republished to WSUS using System Center Updates Publisher after the site server has been upgraded. Until the custom catalog is republished, the custom updates will not be synchronized to the site database and the updates will remain in an expired state. For information about publishing software updates using Updates Publisher, see "Publishing Software Updates" in the Updates Publisher help file, SC_UpdatesPublisher.chm. For more information about Updates Publisher and how to access this help file, see About System Center Updates Publisher.
Deploying Software Updates to Client Computers
After the site upgrade, advertisements that were active prior to the site upgrade will continue to work on SMS 2003 client computers. These advertisements are moved to the SMS 2003 Advertisements node under Software Updates \ Deployment Management in the Configuration Manager console. After the software update point site role is created and configured, the software updates are synchronized with the upstream update server, Configuration Manager client computers are scanned for software updates compliance, and new software update deployments can be created.
In Configuration Manager 2007, the Deploy Software Updates Wizard is used to deploy software updates to both Configuration Manager and SMS 2003 client computers. Software updates only from Microsoft Update and published custom updates can be deployed to SMS 2003 clients. New deployments are not supported for software updates that are in catalogs from other inventory scan tools. For more information about deployments, see About Software Update Deployments.
Using Deployment Templates That Specify SMS 2003 Settings
When deployment templates are created with the Deploy software updates to SMS 2003 clients setting enabled, the template will be available on the Deployment Template page of the Deploy Software Updates Wizard only when all software updates can be deployed to SMS 2003 clients. For example, if the software updates that are being deployed all have a value of Yes for the Deployable to SMS2003 setting, the Deploy Software Updates Wizard will show all templates regardless of configured SMS 2003 settings. If the software updates that are being deployed have a value of No for the Deployable to SMS 2003 setting, the Deploy Software Updates Wizard will not show templates that have the SMS 2003 settings configured. For more information, see About Deployment Templates in Software Updates.
Using the Software Updates Reports
The predefined software updates reports and underlying software updates SQL Server views have been modified in Configuration Manager 2007 to work with the new software updates infrastructure. Existing views from SMS 2003 will mostly work, but you should use the Configuration Manager views when creating or modifying reports.
During a site upgrade, the SMS 2003 reports are migrated, but they are deprecated and might fail to run or retrieve the expected data. You should not use the SMS 2003 software updates reports. Several new reports have been created to support software updates in Configuration Manager and are grouped in the following categories:
Software Updates - A. Compliance
Software Updates - B. Deployment Management
Software Updates - C. Deployment States
Software Updates - D. Scan
Software Updates - E. Troubleshooting
Software Updates - F. Distribution Status
When customized reports were created on the site prior to the upgrade, it is recommended that a similar Configuration Manager report should be customized or a new report should be created to retrieve the desired data instead of using the migrated customized report. For more information about the reports for software updates in Configuration Manager 2007, see About Software Updates Reports.
About Software Update Deployments
About System Center Updates Publisher
Administrator Checklist: Assessing and Deploying Software Updates
Planning for a Software Update Deployment
Planning for the Software Update Point Installation
About Software Updates Reports
For additional information, see Configuration Manager 2007 Information and Support.
To contact the documentation team, email SMSdocs@microsoft.com.