Microsoft KB Archive/171338

= SMS: Preparing for a Systems Management Server Upgrade =

Article ID: 171338

Article Last Modified on 10/27/2006

-

APPLIES TO


 * Microsoft Systems Management Server 1.1 Standard Edition
 * Microsoft Systems Management Server 1.2 Standard Edition

-



This article was previously published under Q171338





SUMMARY
Upgrading a site that is not in a functioning, healthy state may cause serious problems, and may require a reinstallation. This article outlines recommended procedures for upgrading a Systems Management Server site from version 1.1 to 1.2 or for applying a service pack. Following these procedures should prevent problems from occurring.



MORE INFORMATION
The following steps should be performed before all Systems Management Server upgrades (including the application of service packs) are performed:

 Read the Readme.txt files, release notes, and all .txt files that accompany the service pack or the upgrade CD. Read chapter 8, "Upgrading," of the Systems Management Server 1.2 Installation and Configuration Guide. Ensure that the Systems Management Server service account is working, has Domain Admin, Domain Users, Administrator, and the Logon As A Service advanced user rights in all domains participating in the site. Check the Windows NT Application Event log (on the parent site and any children) for connectivity or hierarchy related errors. Back up the following:  The Systems Management Server registry key and subkeys found in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\

-and-

</li> The site control file ...\Sms\Site.srv\Sitecfg.box\Sitectrl.ct0.

-and-

</li> The ...Sms\System.map on the primary site and child secondary sites (if any exist).</li></ul>

</li> Back up the site with a full database dump and directory backup.</li> Use Network Monitor to check the network usage and bandwidth, and do the upgrade during non-busy hours.</li> VERY IMPORTANT: Perform a site reset at every primary site (from within Systems Management Server Setup) and stop and restart the Site Configuration Manager service on the all child Secondary sites (if any).</li> Ensure that SQL Server is configured properly. For more information on SQL Server configuration, refer to the following article in the Microsoft Knowledge Base:

166244 SMS: SQL Server Tuning Parameters for Systems Management Server

</li> Ensure that the transaction log and the Systems Management Server database is not full. If necessary, increase the log size, database size, tempdb, or device size before upgrading.</li></ol>

If there are child secondary sites, also do the following:


 * 1) Ensure connectivity from the parent to the child and visa versa with Net View, and so on.
 * 2) Check that ALL secondary sites are active by looking at the status screen in the site properties in the Systems Management Server Administrator program. The Hman.log file should show all sites active (status 1). This is very important because if one secondary site is not active, the upgrade will be delayed or may fail.

Additional Notes
<ul> Systems Management Server 1.2 Service Pack 2 introduced a switch to delay the automatic upgrade of child secondary sites. For more information, please refer to the service pack's Readme.txt file.</li> For more information on secondary site installation and upgrades, visit the following Web site:

http://www.microsoft.com/smsmgmt/

When you are on the Web site, click "Deployment & Support" and then click "Technical Papers".</li> It may be necessary to reinstall the SQL Server service pack after applying the Systems Management Server service pack. Systems Management Server 1.2 Service Pack 2 overwrites some SQL Server service pack files.</li></ul>

Additional query words: prodsms SP1 SP2 SP

Keywords: kbhowto kbinfo kbnetwork kbsetup KB171338

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.