SMS 2003 SP3 Upgrade Checklist
This document outlines the steps you should take to upgrade from Microsoft Systems Management Server (SMS) 2003 to Microsoft Systems Management Server 2003 Service Pack 3 (SP3). This document is intended to provide a high-level checklist of items to consider when upgrading to SMS 2003 SP3. This document is not intended to provide support for a new installation of SMS 2003 SP3 or for upgrading from SMS 2.0.
For a complete discussion about planning for an implementation or upgrade of SMS, especially if you are deploying a new installation of SMS 2003 SP3 rather than an upgrade, review the "Scenarios and Procedures for Microsoft Systems Management Server 2003: Planning and Deployment" guide, which is available for download from the Systems Management Server 2003 Product Documentation web site.
In this document:
Changes in SMS 2003 SP3
Microsoft introduced several changes with SMS 2003 SP3. These changes have been outlined in detail in the "What's New in SMS 2003 Service Pack 3" document included with the SMS 2003 SP3 source files, and can be downloaded from the Systems Management Server 2003 Product Documentation web site. It is recommended that you read that document before you upgrade your SMS 2003 site.
This section describes the changes in SMS 2003 SP3 that affect the upgrade process.
New Update.exe Upgrade Method
There are now two methods to upgrade from SMS 2003, SMS 2003 SP1, or SMS 2003 SP2 to SMS 2003 SP3. Interactive setup can be run from the installation CD, which is the same as upgrading to a previous SMS 2003 service pack, and the new Update.exe upgrade method can be run from extracted installation files or the update folder on the service pack CD.
SMS 2003 SP3 can be downloaded from the Microsoft web site as a file named SMS2003SP3.exe.To manually extract the installation files to a folder use the /X:path parameter where path is the location where you want to extract the files. Update.exe can be run with the /passive or /quiet switches to upgrade your site. The /quiet switch is completely unattended and hidden, while the /passive switch displays a progress bar during the upgrade process. These switches can also be placed on the command line for SMS2003SP3.exe, and will launch Update.exe with the appropriate switches after automatic extraction to a temporary folder has completed.
Platform Changes in SP3: Site System Operating System Support
Before upgrading your site to SMS 2003 SP3, ensure that all of your site system Operating Systems are at least Windows 2000, Service Pack 4. SMS 2003 SP3 site systems roles are only supported on systems running Windows 2000, Service Pack 4 or later.
Platform Changes in SP3: Advanced Client Support
SMS 2003 SP3 no longer supports SMS Advanced Client installation on workstations running Windows 2000, Service Pack 3 or earlier or Windows XP, Service Pack 1 or earlier. Before attempting to upgrade your SMS site, you should install Service Pack 4 for Windows 2000 systems and at least Service Pack 2 for Windows XP systems if possible.
Alternatively, if you upgrade the site to SMS 2003 SP3, the computers running unsupported operating systems will have reduced SMS functionality while in this state. Specifically, SMS 2003 clients in this state will not be able to receive SMS hotfixes, and SMS 2.0 clients will not be able to report software inventory. Clients in this state should be upgraded to a supported operating system, or service pack, and then upgraded to SMS 2003 SP3, to receive full SMS client functionality.
SMS 2003 SP3 provides support for 64-bit server platforms as SMS Advanced Clients. It also offers support for Vista clients as SMS 2003 Advanced Clients.
Platform Changes in SP3: Legacy Client Support
SMS 2003 SP3 no longer supports the SMS Legacy Client on computers that are capable of running the SMS Advanced Client, such as computers running the Windows 2000 or later operating system. If you have SMS Legacy Clients that fall into this category, you must upgrade them to the SMS Advanced Client when you upgrade their assigned site to SMS 2003 SP3. Until you upgrade those Legacy Clients to the Advanced Client, they cannot receive client agent hotfixes, although they will continue to be managed by SMS. (For example, Legacy Clients can receive a package that upgrades them to the SMS Advanced Client.) Where possible, upgrade these clients before you upgrade your SMS site, and refer to the “Upgrade Legacy Clients” section of this document for more information.
Inventory Tool for Microsoft Updates
SMS 2003 SP3 includes an updated version of the Inventory Tool for Microsoft Updates (ITMU), with hotfixes and updates to the product since its initial release. Installation of the ITMU is an optional installation choice from the setup.exe splash screen. This version of the ITMU requires no updates to the SMS environment before installation can occur. However, you must upgrade your site and clients to SMS 2003 SP3 before upgrading or installing the new version of Inventory Tool for Microsoft Updates. An upgrade using the Update.exe upgrade method would not install the Inventory Tool for Microsoft Updates automatically. To manually install the Inventory Tool for Microsoft Updates you must run Autorun.exe and choose the Inventory Tool for Microsoft Updates option from the SMS Setup splash screen or run SMSITMU.msi directly from the Scantools folder of the extracted files.
Advanced Security Implementation
During an upgrade to SMS 2003 SP3, if the site being upgraded is running in standard security, and the requirements for an advanced security implementation are met, setup will state the site will be migrated to advanced security. This migration is optional and can be cancelled during the upgrade process.
Preparing to Upgrade to SMS 2003 SP3
Plan for your upgrade to SMS 2003 SP3 as you would plan for a new installation of SMS 2003, and read the planning recommendations presented in "Scenarios and Procedures for Systems Management Server 2003: Planning and Deployment".
This section is intended to highlight some of the most significant content from that guide, which you might want to consider before you upgrade from SMS 2003 to SMS 2003 SP3.
As you plan your upgrade strategy, consider the following:
You can upgrade your SMS sites first, or you can upgrade your SMS clients first, depending on the needs of your organization—provided that both clients and sites are running SMS 2003. However, you will not be able to take advantage of the new features in SP3 until the clients and sites are upgraded.
Upgrade the SMS sites in your hierarchy, beginning with the central site, followed by the SMS sites in each subsequent level.
As discussed in the section “Platform Changes in SP3: Legacy Client Support” earlier in this document, before you upgrade your SMS site, upgrade Legacy Clients running the Windows 2000 operating system or later to Advanced Clients.
Every site and Advanced Client in the SMS site hierarchy needs to be configured to use the same HTTP port. Although SMS 2003 SP1, SP2, and SP3 allow you to change the default HTTP port, do not do this until all sites and clients in the SMS hierarchy have been successfully upgraded to SMS 2003 SP3 or, at a minimum, are running SMS 2003 SP1.
Do not reassign an Advanced Client from a site that uses client authentication and data encryption to a site that does not, because Heartbeat Discovery and inventory data will be rejected.
Upgrade each remote SMS Administrator console to the SMS 2003 SP3 version. You cannot access an SMS 2003 SP3 site by using an SMS 2003 SP2 or earlier Administrator console.
Before you can upgrade your SMS site, you must first perform the following steps:
Ensure Your Site Meets All Support Prerequisites
For detailed information about operating systems that are supported for SMS servers and clients, see "SMS 2003 Supported Configurations". This document can be downloaded from the Systems Management Server 2003 Product Documentation web site.
The SMS site server and site system roles must be installed on computers running any of the following operating systems:
Microsoft Windows® 2000 Server, Service Pack 4 or later.
Windows 2000 Advanced Server, Service Pack 4 or later.
Windows 2000 Datacenter Server, Service Pack 4 or later.
Windows Server™ 2003, Standard Edition.
Windows Server 2003, Enterprise Edition.
Windows Server 2003, Datacenter Edition.
Windows Virtual Server 2005 SP1 or later.
All SMS 2003 SP3 site system roles are only supported on systems running Windows 2000, Service Pack 4 or later.
To verify the service pack support dates, visit the Lifecycle Supported Service Packs web site. For additional information about Microsoft’s support lifecycle policy, visit the Microsoft Support Lifestyle Support Policy FAQ web site.
The SMS 2003 SP3 site database can be hosted by any of the following Microsoft SQL® Server versions:
Microsoft SQL® Server 7.0, Service Pack 4 or later.
Microsoft SQL® Server 2000, Service Pack 3a or later.
Microsoft SQL® Server 2005 or later.
Determine Readiness for SMS 2003 SP3 Upgrade
If the site being upgraded is already running SMS 2003 SP1 or SP2 you are not required to run the Deployment Readiness Wizard (DRW) to validate that the site is ready to upgrade to SP3. DRW is only required when upgrading from SMS 2003 RTM to SMS 2003 SP1 or later. The DRW has been updated to support SMS 2003 SP3, and specifically for the new client operating system requirements.
If you are upgrading a site other than SMS 2003 SP1 or SP2 using the /quiet switch, setup will fail unless you first run the DRW manually. When using the /passive switch on a site other than SMS 2003 SP1 or SP2, the DRW setup wizard page will appear during the upgrade process. You must select Run Now and continue. If you cancel the wizard at this point, setup will abort.
You can run the DRW.exe file manually from the following folder on the SMS 2003 SP3 product CD: SMSSETUP\BIN\I386\.
To run the SMS 2003 SP3 Deployment Readiness Wizard on a Primary Site
Start DRW.exe on the primary site.
On the Welcome page, click Next.
If you have child secondary sites, you will see a Site Selection page. Select a site to analyze, select Analyze this primary site, and then click Next. You must complete this step for every child secondary site you want to upgrade.
On the Tests page, select the tests that you want to run and then click Next.
On the Completing the Systems Management Server 2003 Deployment Readiness Wizard page, click Finish.
The SMS 2003 Deployment Readiness Wizard runs the selected tests. After completion, you can view the detailed test results by selecting the site and clicking Details.
To run the SMS 2003 SP3 Deployment Readiness Wizard on a Secondary Site
On the parent primary site for the secondary site, start DRW.exe.
On the Welcome page, click Next.
On the Site Selection page, select the secondary sites to analyze and then click Next.
On the Tests page, select the tests that you want to run and then click Next.
On the Completing the Systems Management Server 2003 Deployment Readiness Wizard page, click Finish .
Disable SQL Replication of the SMS Site Database If You Enabled It
You must disable SQL Server database replication before you upgrade and then reconfigure it when the upgrade is complete.
To disable SQL Server replication
In the SQL Server Enterprise Manager, select the SMS site database server (the publisher).
On the menu bar, select Tools, select Replication, and then select Disable Publishing.
On the Welcome to the Disable Publishing and Distribution Wizard page, click Next.
On the Disable Publishing page, select Yes, disable publishing and then click Next.
On the Confirm Dropping of Publications page, click Next.
On the Completing the Disable Publishing and Distribution Wizard page, click Finish. If the wizard displays a message that the database is in use, click OK and then click Cancel on the Completing the Disable Publishing and Distribution Wizard page. Refresh the SQL Server Enterprise Manager to verify that the publication has been removed.
Replication is now disabled and you can upgrade your site. After the site has successfully upgraded, you can reconfigure SQL Server database replication.
To confirm that the upgrade has completed, refer to the “Determining that SMS Setup Has Completed” section, later in this document. For detailed information about configuring SQL Server database replication for SMS management points, see the white paper, Configuring Microsoft SQL Server 2000 Replication for a System Management Server (SMS) 2003 Management Point.
You should also manually delete any subscription information from remote subscribers. For more detailed information about how to manually disable SQL Server database replication, see the Microsoft Knowledge Base article number 324401, How to manually remove a replication in SQL Server 2000 or in SQL Server 2005. In addition, refer to the information contained in your Microsoft SQL Server 2000 documentation.
Test the Database Upgrade Process
On a backup copy of the SMS site database, you should test the SMS site database upgrade, using the /testdbupgrade setup switch as in the following example:
Setup.exe /testdbupgrade SMS_<sitecode>
Or if you are going to install Asset Intelligence:
Setup.exe /testdbupgrade SMS_<sitecode>
/AI<Folder path containing desired .enc file>
After successfully running the database upgrade test, you are assured that the database portion of the upgrade process will be successful. You can review the results of the test in SMSsetup.log, which is in the root of the system drive.
After running the /testdbupgrade setup switch, your SMS site database will not be compatible with earlier versions of SMS if you do not complete the upgrade, so make sure to run this on a copy of your SMS site database rather than on the original.
Due to changes in how SMS inventories data, the SMS upgrade process needs to move significant amounts of data within the SMS site database. Depending primarily on how many computers and how much inventory data is in the SMS site database, the SQL Server data and/or log files can grow significantly.
Record the size of the SQL Server data and log files, both before and after, using setup with the /testdbupgrade switch to determine the amount of disk space required for the upgrade to succeed. Before upgrading your site, ensure that SQL Server is configured to autogrow and that sufficient disk space is available on the computer running SQL Server, for both the upgrade activity and the subsequent storage of software inventory that is reported from clients.
To test the SMS 2003 site database by using /testdbupgrade
Back up your SMS site database.
Obtain a copy of the SMS site database backup by doing one of the following:
Obtain a copy created by a recent SMS backup task.
Stop all SMS services on the SMS site server and SQL Server, disable publishing on the SMS 2003 site database, and then use SQL Server Enterprise Manager to back up the SMS site database.
Setup /testdbupgrade fails on SMS site databases that are restored from an SMS 2003 site database with SQL Server database replication enabled. When SQL Server database replication is enabled for the SMS 2003 site database, the computer running SQL Server modifies the SQL Server tables that are included in the publication. When the database is restored to another database, the setup /testdbupgrade fails on that restored SMS site database.
On another computer running the same version of SQL Server, restore the database you just backed up as follows:
Manually create a new database with the same name as the one you backed up. Default data/log file sizes of 1 MB are adequate.
Copy the database backup file from the SQL Server database to a local drive on the test computer running SQL Server.
Restore the database using SQL Server Enterprise Manager. Because the drive letters might be different on your test computer that is running SQL Server, you might need to modify the destination drive and file properties during the restore operation.
On the restored SQL Server database, type the following at the command prompt: setup.exe /testdbupgrade < database name >. If you are installing Asset Intelligence, verify that the database will be compatible with Asset Intelligence by adding the /AI setup switch as shown: Setup.exe /testdbupgrade SMS_ <sitecode> /AI <Folder path containing desired .enc file> .
Setup.exe in the command line above should be run from an upgrade CD or extracted SP3 files from the service pack download. Any problems you encounter during the test upgrade must be corrected before you upgrade your production site. You can review the results of the test in SMSsetup.log, which is in the root of the system drive.
Upgrading the SMS 2003 Site to SP3
After you have completed the planning requirements listed earlier in this document, you can upgrade your SMS 2003 site to SMS 2003 SP3. You must begin your upgrade with the central site in your SMS site hierarchy and then upgrade child sites using a top-down approach. SMS Setup does not provide an automated upgrade for secondary sites, so you must manually upgrade each secondary site. For a detailed discussion about upgrading your site and running setup, see Appendix H, “Upgrading to SMS 2003” in "Scenarios and Procedures for Systems Management Server 2003: Planning and Deployment".
Any non-SMS files or folders that are in the SMS 2003 folder structure will be deleted when SMS 2003 is upgraded or removed. To avoid removing non-SMS data when SMS is upgraded or removed, install SMS in a folder that does not contain other application or data files. Also, do not install other applications into SMS folders.
If you have previously used the automated Backup SMS Site Server database maintenance task, copies of all files in the SMS site server folder tree are included in your SMS backup.
To start the upgrade process
Run Autorun.exe from the SMS 2003 SP3 Upgrade CD. Alternatively, you can download SMS 2003 SP3 from the Microsoft Systems Management Server web site, or you can order an SMS 2003 SP3 upgrade CD from Microsoft.
If the upgrade site is not already running at least SMS 2003 SP1, setup prompts you to run the Deployment Readiness Wizard. If the Deployment Readiness Wizard completes with no errors, the upgrade continues. If there are any errors, you must first correct the errors before you can complete the upgrade.
All SMS services are uninstalled and then reinstalled on all SMS site systems.
Complete this process for every primary site in your SMS site hierarchy.
To upgrade Secondary Sites to SMS 2003 SP3
Run the SMS 2003 SP3 Setup.exe on each primary site in the hierarchy. The parent primary site must be upgraded to SMS 2003 SP3 before upgrading secondary sites that report to it.
Run the Deployment Readiness Wizard against the secondary site by starting it on the primary site server, as outlined in the section “Determine Readiness for SMS 2003 SP3 Upgrade” earlier in this document.
Upgrade the secondary site by running the SMS 2003 SP3 Autorun.exe or Update.exe on the secondary site server, or initiate the upgrade from the parent primary site of the secondary site server by using the SMS Administrator console.
Determining That SMS Setup Has Completed
After you apply SP3, wait at least 30 minutes before opening the SMS Administrator console, running a site reset, or performing any other site configuration change or operation. This waiting period allows the initial SMS configuration processes, carried out by the SMS Executive and SMS Site Component Manager services, to complete. You can verify whether these processes are completed by checking the level of CPU activity on your computer or Task Manager for running upgrade processes during the SMS service installation. When the activity level returns to normal, you can open the SMS Administrator console.
You can check the C:\SMSSetup log for the SMS Setup completed successfully entry. This entry indicates that SMS Setup.exe has completed its tasks. However, this does not always mean that other SMS processes have completed their own tasks associated with setup or site reset. In addition, you can check the following logs in SMS/logs for specific activity.
SMS Site Component Manager log (SMSSitecomp.log)
This log verifies that SMS components have been reinstalled.
Search for Processing site shutdown transaction.
In the case of a site reset, this entry represents the first occurrence of the site being shut down. Subsequent lines in the log indicate that other individual services were stopped and that status messages were generated to indicate that the service stopped.
Search for Site shutdown complete.
This entry represents the first occurrence of the site shut down having completed. This occurred when the update installation signaled SMS to perform the site reset. Subsequent lines in the log indicate that other individual services were being reinstalled. This might take several minutes to complete.
Search for Waiting for changes to the “C:\SMS\Inboxes\Sitectrl.box” or “C:\SMS\Inboxes\Sitecomp.box” directories.
This entry indicates that the Site Component Manager has completed its work for the site upgrade.
Hierarchy Manager log (Hman.log)
This log verifies that SMS site information is published in Active Directory (in an extended Active Directory schema environment).
Search for Wait for site control changes for maximum 3600 seconds.
This entry indicates that Hierarchy Manager has completed its work for the site upgrade. In the lines prior to this entry, you will see entries related to publishing SMS site data to Active Directory.
SMS Inbox Manager log (Inboxmgr.log)
This log verifies that inboxes have been successfully created on the SMS site server and the SMS client access point (CAP).
Search for Waiting for changes inbox definition, inbox rules and inbox replication files, max wait = 3600 seconds.
This entry indicates that SMS Inbox Manager has completed its work for the site upgrade. In the lines prior to this entry, you will see entries indicating that files were copied to the client access point and that some inboxes were updated. In general, the last inbox to be created on the client access point is CAP_xxx\Clicomp.box.
Upgrading Legacy Clients
SMS 2.0 clients and Legacy Clients running the Windows 2000, Windows XP, and Windows Server 2003 operating systems cannot upgrade to the SMS 2003 SP3 version of the Legacy Client.
When SMS 2.0 clients or SMS 2003 Legacy Clients running the Windows 2000, Windows XP, and Windows Server 2003 operating systems are members of an SMS 2003 SP3 site, you cannot apply client agent hotfixes to them. In addition, SMS 2.0 clients running the Windows 2000, Windows XP, and Windows Server 2003 operating systems cannot report software inventory to an SMS 2003 SP3 site server.
Consequently, you should upgrade these clients to the SMS 2003 SP3 Advanced Client as soon as possible. You can upgrade these clients before you upgrade your SMS site servers. SMS 2003 SP3 Advanced Clients will communicate successfully with an SMS 2003 site.
On supported Legacy Client platforms for SMS 2003 SP3, Legacy Clients will automatically upgrade to SMS 2003 SP3 when any of the following occur after upgrading the site to SMS 2003 SP3:
On the next Client Configuration Installation Manager (CCIM) maintenance cycle, which is every 25 hours for SMS 2003 clients, or every 23 hours for SMS 2.0 clients.
When the SMS Client Service is restarted.
When forced by clicking Update Configuration on the Sites tab on the client’s Systems Management Properties page.
The clients do not upgrade if any of the following is true:
The client’s CCIM cycle has not yet run.
The client has run cliupgrade /disable, which stops the CCIM cycle from running.
The client’s operating system is Windows 2000, Windows XP, or Windows Server 2003.
Upgrading Advanced Clients
Unlike the Legacy Client, SMS Advanced Clients do not automatically upgrade to a newer version. Consequently, you must determine how to upgrade existing SMS 2003 Advanced Clients to SMS 2003 SP3. One way is for the SMS administrator to use the Client Push Installation Wizard, by selecting the option Always install (repair or upgrade existing client) on the Client Installation Options Wizard page. The SMS Administrator can also use SMS software distribution to advertise the upgrade to clients in a collection.
Windows 2000, Service Pack 4 and Windows XP, Service Pack 2 are the earliest supported version of a Windows operating system for the SMS 2003 SP3 Advanced Client. For more information about installing and upgrading Advanced Clients, refer to Appendix 1, “Installing and Configuring SMS Clients,” in Scenarios and Procedures for Microsoft Systems Management Server 2003: Planning and Deployment.
The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication.
This white paper is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS DOCUMENT.
Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.
Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.
© 2007 Microsoft Corporation. All rights reserved. Microsoft, BackOffice, Windows, and Windows NT are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.
Other product and company names mentioned herein may be the trademarks of their respective owners.
Microsoft Corporation • One Microsoft Way • Redmond, WA 98052-6399 • USA