[Previous] [Next]

Lesson 7: Upgrading SMS 1.2 to SMS 2.0

SMS 1.2 can be upgraded to SMS 2.0, or it can interoperate with SMS 2.0. There are good reasons both to upgrade and to interoperate. This lesson examines an SMS 1.2 to SMS 2.0 upgrade performed on a single, central site server. Other upgrade and interoperability issues will be addressed throughout this guide.

After this lesson, you will be able to Estimated Completion Time: 30 minutes

Pre-Installation Planning

There are a number of pre-installation requirements before an SMS 1.2 primary site server can be upgraded to an SMS 2.0 site server. The best strategy is to upgrade the operating system and database to the latest versions supported by SMS 1.2. Then consolidate all SMS 1.2 site server functions back to the SMS primary site server. For example, the SMS Executive threads running on SMS 1.2 helper servers should be returned to the site server. Upgrading the site server operating system and SMS database and consolidating SMS services will increase the likelihood of a successful upgrade to SMS 2.0. SMS 1.2 clients can be converted to SMS 2.0 client computers. Before conversion begins, you must be aware of which clients can be upgraded to SMS 2.0 client computers.

Preparing Windows NT Server and Applications Supporting SMS

An SMS 1.2 site server is designed for Windows NT Server 3.51 running SP3 (or later) domain controllers or Windows NT Server version 4.0 domain controllers. An SMS 2.0 site server can be installed on Windows NT Server version 4.0 running SP4 (or later) or on a Windows 2000 Server. The SMS 2.0 site server does not have to be a domain controller but it must be a member of a domain (member server). However, a Windows NT/2000 Server acting as a domain controller cannot be converted into a member server. Therefore, after the upgrade process, Windows NT/2000 Server will remain a domain controller.

To run the online help system and the Microsoft Management Console, you must install IE 4.01 on the computer that will be upgraded. IE 4.01 will not disrupt the normal function of an SMS 1.2 server. However, do not install the IE 4.01 active desktop prior to an upgrade to SMS 2.0.

Preparing SQL Server

While SMS 1.2 was designed for SQL Server version 6.x, it can run on SQL Server version 7.0. Therefore, you must upgrade SQL Server to either version 6.5 running SP4 or SQL Server version 7.0 before starting the SMS 2.0 upgrade process. Since SQL Server version 6.0 is not supported on Windows NT version 4.0, upgrade SQL Server to version 6.5 running SP4 before running a Windows NT Server version 4.0 upgrade. Ideally, upgrade to SQL Server version 7.0 and Windows NT Server version 4.0 running SP4 before performing any SMS 1.2 to SMS 2.0 upgrade. Once SMS 2.0 is installed on a computer running a local copy of SQL Server, that computer cannot service any SMS site servers running SMS 1.2.

The SQL Server version 6.5 tempdb (temporary database) must be expanded to support an upgrade from SMS 1.2 to SMS 2.0. You must first determine the size of the current SMS 1.2 site database. To do this, run the sp_spaceused stored procedure through SQL Server version 6.5's iSQL utility. When you have ascertained the value, increase the size of tempdb so that it is 20 percent larger than the site database. For example, if the SMS 1.2 site database is 200 MB, then tempdb should be at least 240 MB. This procedure is only necessary on SQL Server version 6.5, since SQL Server version 7.0 will dynamically grow the tempdb database as the upgrade installation requires it.

To protect your site database, run a database backup against the site database and the master database before starting a SQL Server upgrade. Run the SMS 1.2 DBCLEAN utility to delete obsolete or unused data from the database. Further, run database consistency checks in SQL Server Enterprise Manager and set the site database transaction log to `Truncate at checkpoint' before performing the SQL Server upgrade. This last option keeps the transaction log from growing out of control during the upgrade process.

Preparing SMS 1.x

Only SMS 1.2 is designed for an upgrade to SMS 2.0. If you are running SMS 1.0 or 1.1, upgrade to SMS 1.2 before starting an upgrade to SMS 2.0. SMS 1.2 is designed to run on the x86, Alpha, or MIPS platform. Since SMS 2.0 does not include binaries (installation files) for MIPS computers, an SMS 2.0 upgrade cannot be performed on this platform.

Backup the SMS 1.2 registry keys and update the emergency repair disk and the SMS directory structure. Ideally, run a full system backup and maintain this tape until a successful SMS 1.2 to SMS 2.0 upgrade has been completed.

Preparing SMS 1.2 Clients to Become SMS 2.0 Client Computers

SMS 2.0 does not include MS-DOS 5.0 or later, Macintosh System 7.x, or IBM OS/2 2.11 clients agents while SMS 1.2 does. Therefore, if these client operating systems require systems management, SMS 1.2 site servers should be made part of the SMS 2.0 site hierarchy. SMS 1.2 and SMS 2.0 interoperability issues will be covered throughout this book. If possible, upgrade the client operating systems to support the SMS 2.0 client agents. SMS 2.0 client agent support is discussed in Chapter 1.

Upgrading SMS 1.2 to SMS 2.0

Because of the structural difference between SMS 1.2 and SMS 2.0, some data in the SMS 1.2 site database cannot be converted to the SMS 2.0 site database. The following SMS 1.2 settings are lost in the upgrade: security settings configured through the SMS Security Manager; client disk inventory; named queries; and jobs, excluding system jobs. Since the SMS 1.2 directory structure is deleted, collected files, Package Definition Files (PDF), custom management information format (MIF) files, and SMS logon scripts are deleted. It is therefore important to document all critical settings and make sure that you have performed a full system backup before performing an upgrade.

Modifications to the setup options cannot be made during the upgrade process. So installation modification must be performed after the upgrade is complete. The upgrade process should not be interrupted after a database conversion has begun. The upgrade routine will prompt you to start the database conversion. An upgrade can be cancelled before database conversion has begun.