Upgrading to MOM 2005

  • Article

If you have all the Microsoft Operations Manager (MOM) 2000 SP1 components installed on a single computer, upgrading to MOM 2005 is a straightforward process. If you have the MOM 2000 SP1 components installed across multiple computers, you must follow a specific order to upgrade due to interdependencies between the MOM components.

When you upgrade MOM 2000 SP1 components to MOM 2005, the MOM 2000 SP1 components on the computer are uninstalled and the MOM 2005 versions are installed in their place, with the exception of the MOM Database and MOM Reporting.

Document Revisions

The following table summarizes the revisions that have been made to this document.

Revisions, May 2005

Section

New or Updated

Title

Description

Upgrading Multitiered MOM 2000 SP 1 Configuration Groups

Updated

Reconfiguring the MOM 2005 MOM Product Connectors

Revised procedure.

Before You Begin

Updated

Reviewing Key Documents

Added best practice note.

Note

You cannot upgrade to the MOM 2005 Evaluation from MOM 2000 SP1 or any previous release of MOM 2005. You must uninstall the previous version and install MOM 2005.

When upgrading from the MOM 2005 Evaluation edition to the Select or Retail edition, you need to upgrade only the MOM Database, Management Servers, and consoles. The agents and MOM Reporting components and the MOM Reporting Database will not need to be updated.

Upgrading from the MOM 2005 Release Candidate

Upgrading from the MOM 2005 Release Candidate to the RTM release of MOM 2005 is supported. To do the upgrade follow the upgrade instructions for the MOM 2000 SP1 upgrade except that:

  • You must backup both the MOM Database and the MOM Reporting Database.

  • You do not uninstall or install any MOM 2000 SP1 components.

  • You do not need to use the Transition Management Pack (unless there are agents that are multihomed with MOM 2000 SP1).

  • For Management Servers with the MOM Connector Framework or the MOM Product Connector, you do not have to install the RTM versions of these components. The Management Server upgrade will automatically do this.

  • Upgrading MOM Reporting and the MOM Reporting Database form the Release Candidate is not supported. You should backup this Release Candidate Reporting Database and then uninstall the MOM Reporting components and the Reporting Database and install the MOM 2005 Reporting components and Reporting Database a new installation.

In This Chapter

Before You Begin

To complete the upgrade scenarios described in this chapter, it is recommended that you review and be familiar with Chapter 3, "Deploying MOM 2005 across Multiple Computers." In addition, a working knowledge of MOM components and features is beneficial.

Terminology Changes

For MOM 2005, there have been some terminology changes that you need to be aware of when using this chapter.

Table 10.1 lists the MOM 2000 SP1 terms that have changed, the MOM 2005 equivalent, and a definition of each term.

Table 10. 1 Term Equivalents from MOM 2000 SP1 to MOM 2005

MOM 2000 SP1 Term

MOM 2005 Term

Definition

DCAM

MOM Management Server

Discovers managed computers and installs, uninstalls, and upgrades agents. Passes configuration information to managed computers based on the Management Pack rules. Controls the flow of data between the MOM agents and the MOM Database.

Configuration group

Management group

Consists of a MOM database, one or more MOM Management Servers, the MOM Administrator console and MOM Operator console, managed computers, and optionally the MOM Reporting console and MOM Web console.

Zone configuration group

Source management group

Forwards alerts in a multitiered MOM configuration.

Master configuration group

Destination management group

Receives forwarded alerts in a multitiered MOM configuration.

Reviewing Key Documents

Review the MOM 2005 release notes to identify any issues that might affect planning for your upgrade.

Review the Microsoft Operations Manager 2005 Supported Configurations data sheet to ensure that your existing MOM deployment meets the hardware and software requirements that are specified.

Review the Microsoft Operations Management 2005 Security Guide for the security requirements and implications.

Review in-house documentation to ensure that you have all the information that is required to perform the upgrade. For example, you will be prompted to provide MOM service account information during the installation.

Upgrading with Agents on Windows NT 4.0

MOM 2005 does not support agents on computers running Windows NT 4.0. If you have agents on these computers, you must do one of the following, depending upon the conditions:

Singlehomed

You must remove the agents from these computers before you upgrade to MOM 2005. Then you can discover these computers as Agentless managed.

Multihomed

In this case, you must do the following:

  1. You can continue to monitor these computers up until you reach the point when you must upgrade the agents.

  2. At this point you must follow the directions for removing the upgraded management group (configuration group) from the agent on the Windows NT 4.0 computer. Use the "To remove a MOM 2000 SP1 agent from a configuration group" procedure below.

  3. Then you must rediscover the Windows NT 4.0 computers from the upgraded MOM 2005 management group as Agentless managed.

  4. Repeat steps 2 and 3 for the second configuration group.

To remove a MOM 2000 SP1 agent from a configuration group

  1. Remove the agent computer from the MCR of the DCAM.

  2. Perform a scan or wait until the regularly scheduled scan.

  3. After the scan, stop and then restart the OnePoint service on the agent computer.

The registry on the agent will change as a result of the scan, but the agent will not pick up the change until you restart the OnePoint service. You can verify the change on the agent by reviewing the following registry key:

HKLM\software\mission critical software\onepoint\configurations\configuration_group\Operations\Agent\Consolidators

Backing up the MOM Database

You must back up the existing MOM 2000 SP1 database and verify that it can be restored. Because an upgrade to the MOM 2005 database creates changes in the database structures and relationships, the upgrade is irreversible and cannot be uninstalled. To restore your original MOM 2000 SP1 configuration, you must uninstall the MOM 2005 database components and delete (DROP) the MOM 2005 Database. You can then reinstall the MOM 2000 SP1 database component and restore the backup copy of the MOM 2000 SP1database.

To back up the MOM Database

  1. Open the Microsoft SQL Server Enterprise Manager.

  2. Expand Microsoft SQL Servers and its child nodes until the Management folder is displayed in the left pane.

  3. Expand Management.

  4. Right-click Backup, and then click Backup a Database.

  5. In the SQL Server Backup dialog box, click the General tab, and then click OnePoint in the Database list. The default value for Name is OnePoint backup; you can keep this name or type a different name.

  6. Click the Options tab, and then select Verify backup upon completion.

  7. Click OK to start the backup.

Backup ManualMC.txt and Other Files

Before you upgrade MOM, you should backup any ManualMC.txt files and any other files that you might have added to the Microsoft Operations Manager 2000 directory because setup will delete these files.

Review MOM 2000 SP1 and MOM 2005 Interoperability

There are varying degrees of interoperability between MOM 2000 SP1 and MOM 2005 components to support rolling upgrades in a distributed MOM environment. For information about interoperability, see the MOM 2005 Supported Configurations data sheet.

Important

    Interoperability between MOM 2000 SP1 and MOM 2005 components is intended to support rolling upgrades in a distributed MOM environment. It is recommended that you upgrade all MOM 2000 SP1 DCAMs in a configuration group as quickly as possible.

Command-Line Parameters or Switches to Avoid When Upgrading

You should not use any of the following command-line parameters or switches for the MSI installer while upgrading:

  • CONFIG_GROUP

  • ADDLOCAL

  • LOG_DIR

  • DATA_DIR

  • DB_SIZE

  • MOM_DB_SERVER

Configuring Security After Upgrading

After the upgrade process, several of the new security feature in MOM 2005 will be disabled by default. You should review these settings and enable them, depending upon your security policies. These settings are:

  • Block MOM 2000 and MOM 2000 SP1 agents from connecting to the Management Server

  • Mutual authentication required

  • Reject new manual agent installations

  • Prevent agent from proxying for other computers or network devices

  • Disable execution of custom responses on Management Servers

You should also review the permissions used for the Management Server Action Account. After the upgrade this account will be a domain administrator. You might change this to be a lower-privileged account, depending upon your security policies.

For more information about configuring security after upgrading, see the Microsoft Operations Manager 2005 Security Guide.