Performing a Side-by-Side Upgrade to MOM 2005

  • Article

In a large enterprise environment, it can take a substantial period of time to upgrade all of your MOM 2000 SP1 components and agents to MOM 2005. When upgrading to MOM 2005 in such an environment, you might want to consider using a side-by-side upgrade. In this scenario, you deploy a new MOM 2005 management group along side your MOM 2000 SP1 configuration. You can then use multihomed MOM 2005 agents that belong to both MOM 2000 SP1 configuration groups and MOM 2005 management groups. This allows you to gradually deploy MOM 2005 agents to managed computers, while continuing to monitor those computers with a DCAM in the MOM 2000 SP1 configuration group.

You might also consider using a side-by-side upgrade if you have specialized MOM 2000 SP1 configuration groups that are set up to automatically install agents on and to manage specific types of computers, such as all Domain Controllers, to collect security audit events.

MOM 2005 supports a MOM 2005 agent simultaneously belonging to MOM 2000 SP1 configuration groups and MOM 2005 management groups. The following sections describe how to configure multihomed agents for a side-by-side upgrade. These sections also describe how to remove a MOM 2000 SP1 configuration group from a multihomed MOM 2005 agent.

Important

When you are doing a side-by-side upgrade, it is important that you do not install a MOM 2005 agent on any MOM 2000 SP1 DCAM. Ensure that you do not inadvertently include any computer that hosts a MOM 2000 SP1 DCAM in a MOM 2005 Computer Discovery rule.

There are two scenarios in which a MOM 2005 agent can be multihomed to MOM 2000 SP1 configuration groups and to MOM 2005 management groups. Both scenarios use the MOM 2005 Transition Management Pack. The MOM 2005 Transition Management Pack enables MOM 2000 SP1 configuration groups to process alerts, events, and performance data that a multihomed MOM 2005 agent sends.

Upgrading an Existing MOM 2000 SP1 Multihomed Agent

In this scenario, you have an existing MOM 2000 SP1 agent that is multihomed to two MOM 2000 SP1 configuration groups. In this scenario, it is assumed that your intent is to eventually remove the other MOM 2000 SP1 configuration group, not to upgrade it. You then upgrade one of the MOM 2000 SP1 configuration groups and the multihomed agent to MOM 2005.

If you intend to upgrade the other MOM 2000 SP1 configuration group that the multihomed agent belongs to, see the "Upgrading MOM 2000 SP1 Configuration Groups with Multihomed Agents" section later in this chapter.

To install a multihomed agent by upgrading a MOM 2000 SP1 configuration group and agent

  1. Upgrade one of the MOM 2000 SP1 configuration groups.

  2. In the other MOM 2000 SP1 configuration group, import the MOM 2005 Transition Management Pack from the UpgradeTools directory on the product CD.

  3. Upgrade the MOM 2000 SP1 multihomed agent to MOM 2005.

Installing a New MOM 2005 Management Group and Creating Multihomed Agent

In this scenario, you have an existing MOM 2000 SP1 configuration group, and you install a new MOM 2005 management group and deploy a MOM 2005 agent. You then add the existing MOM 2000 SP1 configuration group to the MOM 2005 agent to make it a multihomed agent.

To install a new MOM 2005 management group and create a multihomed agent

  1. Install a new MOM 2005 management group and deploy a MOM 2005 agent.

  2. In the MOM 2000 SP1 configuration group that you want to add to the multihomed agent to, import the MOM 2005 Transition Management Pack from the UpgradeTools directory on the product CD.

  3. Open the MOM Administrator console for the MOM 2000 SP1 configuration group, and add the computer on which the MOM 2005 agent is installed to the Managed Computer rules. Alternately, you can add the computer to the ManualMC.txt file on the DCAM.

  4. Perform a managed computer scan.

Removing a MOM 2000 SP1 Configuration Group from a MOM 2005 Multihomed Agent

In a side-by-side upgrade scenario, you eventually must remove the MOM 2000 SP1 configuration group from the MOM 2005 multihomed agent.

To remove a MOM 2000 SP1 configuration group from a MOM 2005 multihomed agent

  1. Open the MOM Administrator console for the MOM 2000 SP1 configuration group, and remove the managed computer on which the agent is installed from the Managed Computer rules. Alternately, you can remove the computer from the ManualMC.txt file on the DCAM.

  2. Perform a managed computer scan.

  3. Log on to a DCAM in the MOM 2000 SP1 configuration group by using an account that has administrative credentials on the managed computer with the multihomed agent.

  4. Locate the RemoveConfigGroup.exe tool in the SupportTools directory on the MOM 2005 product CD.

  5. Open a command-line window and run the following command: < CD drive >:\SupportTools\RemoveConfigGroup.exe <RemoteAgentName> <ConfigGroupToRemove>

Where <CD drive> is the letter of the CD drive, <RemoteAgentName> is the name of the managed computer with the agent, and <ConfigGroupToRemove> is the name of the MOM 2000 SP1 configuration group to be removed from the agent.

Acknowledgments

Authors: Py Bateman (S&T Onsite), John Hallows, James R. Morey, Dan Wesley

Program Managers: Vlad Joanovic, Lorenzo Rizzi, Travis Wright

Applies To:   Microsoft Operations Manager 2005

Primary Reviewers: Barry Webberley, Starr Parker, Selma Tanaka

Secondary Reviewers: Alexandre Coelho, Kerry Minietta, Omar Kouatly, Ian Jirka

Managing Editor: Sandra Faucett