本文件已封存並已停止維護。

MOM 2005 to Operations Manager 2007 Migration Overview

更新日期: 2009年7月

適用於: Operations Manager 2007 R2, Operations Manager 2007 SP1

In the migration process from Microsoft Operations Manager 2005 (MOM 2005) to Operations Manager 2007, there are two aspects that must be addressed. The first aspect is the MOM 2005 infrastructure components, including the database server and its hardware, the management servers and their hardware, and so on. The second aspect is the MOM 2005 management packs that have been deployed in your environment.

Infrastructure Components

There is no upgrade path from MOM 2005 to Operations Manager 2007. To avoid interrupting your monitoring and alerting services, you must deploy Operations Manager 2007 in your environment and support both MOM 2005 and Operations Manager 2007 while they co-exist. When you can confirm that Operations Manager 2007 is providing you with all the necessary information and services, you can then start removing your MOM 2005 implementation.

Deploying Operations Manager 2007 in a MOM 2005 environment can be accomplished in one of two ways. You can either install Operations Manager 2007 server components on the same hardware that contains the MOM 2005 server components or you can install Operations Manager 2007 on hardware that is dedicated to your Operations Manager 2007 infrastructure. For information about these methods, see the next section, "MOM 2005 to Operations Manager 2007 Infrastructure Migration."

note附註
The two products can both run on the same hardware without any conflicts, if the hardware meets the requirements of both products.

Infrastructure Migration Considerations

Before you can decide which way to deploy Operations Manager 2007 in a MOM 2005 environment, you must first re-evaluate your company's monitoring and alerting needs as they relate to the features of Operations Manager 2007. If you have deployed multiple MOM 2005 management groups for security, scalability, or redundancy reasons, you can probably consolidate those multiple groups into fewer Operations Manager 2007 management groups. For more information about Operations Manager components and the design process, see the Operations Manager 2007 Design Guide at http://go.microsoft.com/fwlink/?LinkId=96761.

Consolidation Factors

The first factor to consider is that Operations Manager 2007 implements role-based security. A role in Operations Manager 2007 consists of a profile and a scope. A profile, such as Operations Manager Administrator or Operations Manager Operator, defines what actions can be taken in the Operations console. The scope defines which objects those actions can be taken on. Operations Manager 2007 Roles provide a security boundary between users who are in different roles. For example, you can use a profile, such as Operations Manager Operator, which allows the user to monitor and respond to alerts. You can combine this profile with a scope, such as all monitored servers that are running Microsoft Exchange Server, which results in an Exchange Operators Role. Any user accounts that are assigned to this role can see and interact with operations data only from the servers that are running Exchange Server. These user accounts do not have access to data from any other servers. Because role-based security is enforced by the System Center Data Access service that is running on the root management server, it is applied to all methods of accessing data, including the Operations console, command line, script, Web access, and programmatically. Because security is role-based in Operations Manager 2007, it is no longer necessary to partition management groups for security purposes.

The second factor that influences consolidation is the introduction of the gateway server. A gateway server acts as a consolidation point for communications between agents and management servers that are on opposite sides of a Kerberos trust boundary. Agents communicate with the gateway and the gateway server communicates with the management servers.

The third factor that you should consider about server consolidation is the overall increase in scalability of all the Operations Manager 2007 components. For more information about scalability, see the Operations Manager 2007 Design guide at http://go.microsoft.com/fwlink/?LinkID=158867 .

note附註
Remember that although Operations Manager 2007 delivers better performance and scalability than MOM 2005, Operations Manager 2007 has higher minimum hardware requirements than MOM 2005. For more information, see Operations Manager 2007 Supported Configurations at http://go.microsoft.com/fwlink/?LinkId=89360.

Management Packs

Over the lifecycle of your MOM 2005 implementation, you have probably invested the most time and effort in customizing vendor-written management packs and in developing custom management packs for your company-developed applications. Because your MOM 2005 management packs currently provide information that is used daily, you probably want to use the customizations in these management packs in Operations Manager 2007.

note附註
MOM 2005 management packs cannot be imported into Operations Manager 2007. They must be converted to the Operations Manager 2007 format first.

You can use the Operations Manager Migration Wizard to convert management packs from the MOM 2005 format to Operations Manager 2007 format and to extract a list of MOM 2005 agent-managed computers that you can import into the Operations Manager 2007 Discovery Wizard. Operations Manager 2007 also provides command-line utilities, which are described in Operations Manager 2007 Help.

note附註
When you install and start the Migration Wizard, you will see that it is initially called the System Center Operations Manager Migration Tool.

Before you begin converting MOM 2005 management packs to the Operations Manager 2007 format, you must inventory all of the management packs that have been deployed and document all of the modifications that have been made to them. You need to know these modifications when you modify the Operations Manager 2007 versions of those management packs in your migration testing lab. Overrides are not converted as part of the management pack conversion because they are not stored in management packs in MOM 2005.

Converted Management Packs and Operations Manager 2007 Native Management Packs

Operations Manager takes a fundamentally different approach to monitoring than MOM 2005. The basic structure of Operations Manager 2007 management packs and their components has changed. For more information, see the "Comparing MOM 2005 and Operations Manager 2007 Management Packs" section of this document. The tools and the object model that are used to produce the Operations Manager 2007 management packs are different than those of MOM 2005. A MOM 2005 management pack that has been converted to the Operations Manager 2007 format is not the same as a management pack created in Operations Manager 2007.

Microsoft-produced management packs that are converted by Microsoft are supported for a limited time. Microsoft provides Operations Manager 2007 native versions of management packs. For more information, see http://go.microsoft.com/fwlink/?LinkId=89473 for the current catalog.

There are two methods to convert MOM 2005 management packs, developed by your company, to Operations Manager. You can use the Operations Manager Migration Wizard to convert the management packs, apply your customizations, and import them into Operations Manager. This method gives you functionality that is equivalent to what you had in MOM 2005. To take advantage of the full Operations Manager 2007 object model, you should redevelop the management pack by using the Operations Manager 2007 tools. For more information, see the Operations Manager 2007 Management Pack Authoring Guide at http://go.microsoft.com/fwlink/?LinkId=158876.

Migration Order of Operations

How an organization uses MOM 2005 and integrates it into its daily process is unique to each organization. Guidance on how you have to adapt and integrate your existing process to Operations Manager 2007 is beyond the scope of this document because each company uses MOM 2005 uniquely.

However, when you are developing your MOM 2005 to Operations Manager 2007 migration plan, be sure to include the following tasks:

  1. Evaluate Operations Manager 2007, and create an infrastructure design. For more information, see the Operations Manager 2007 Design Guide.

  2. Evaluate and document your current MOM 2005 implementation and process.

  3. Implement Operations Manager 2007 in a test environment according to the design you developed in step 1. For more information, see the Operations Manager 2007 Deployment Guide.

    note附註
    Be sure to include any connectors and tiered management groups, and plan to reproduce any customized MOM 2005 Reports with Operations Manager reports.

  4. Download the Operations Manager 2007 versions of all available MOM 2005 management packs. Check for new management packs regularly. Modify these in your test environment.

  5. Convert and modify any management packs (including custom management packs) that were not covered in the previous step, by using the Operations Manager Migration Wizard, and then implement them in your test environment.

  6. Implement Operations Manager 2007 in your production environment according to your design and migration plan (using the same hardware or different hardware). For more information, see the Operations Manager 2007 Deployment Guide.

  7. Configure Operations Manager 2007 for production use. For more information, see the Operations Manager 2007 Operations Guide.

  8. Deploy the new and converted management packs. For more information, see the Operations Manager 2007 Operations Guide.

  9. Confirm all functionality in Operations Manager 2007 and test the integration of your monitoring, alerting and, reporting processes.

  10. Uninstall MOM 2005 components in the correct order. This process is described later in this guide.

顯示: