Export (0) Print
Expand All
This topic has not yet been rated - Rate this topic

Appendix: If You Use the Previously-Released, Converted Exchange Server 2007 Management Pack

Applies To: Exchange Server, Operations Manager 2007 R2

You may be using the previously released version of the Exchange Server 2007 converted management pack. It is not possible to upgrade from the previously released, converted management pack to this new, native version of the Microsoft Exchange Server 2007 Management Pack.

Migration Options

This section describes options to help you decide how to migrate from the previously released, converted management pack to the new, native management pack. The options are as follows:

  • Delete the previously released, converted management pack. Then import the native Exchange Server 2007 Management Pack.

  • Keep the previously released, converted management pack and use a second management group for the new, native management pack. In this scenario, you introduce and tune the native management pack by using a second management group and multi-homing the Exchange 2007 agents to report to both management groups. You should disable the Exchange 2007 synthetic transactions from one of the management groups because synthetic transactions consume CPU, disk IO, and memory resources on the Exchange 2007 servers. We recommend that you disable the converted management pack synthetic transactions as soon as possible because the native management pack synthetic transactions use fewer resources on the Exchange 2007 servers.

  • Keep the previously released, converted management pack, and plan a gradual introduction of the new, native management pack by enabling server role discoveries on a server-by-server basis. You can gradually introduce the new, native management pack into the existing management group. This is possible because the server role discoveries in the new management pack are disabled by default. You can enable the discoveries of the new Management Pack on a server-by-server basis (see Enable Exchange 2007 Server Role Discovery). As you enable servers to be discovered by the new management pack, you can disable the discoveries for the same servers in the converted management pack. You must run the Operations Manager 2007 remove-disabledMonitoringObject cmdlet in order to remove the converted management packs objects from the management group and avoid running synthetic transactions from both management packs at the same time.

 

Option Pros Cons

Delete the previously released, converted management pack. Then import the native Exchange Server 2007 Management Pack.

The simplest approach. You delete the converted Exchange Server 2007 Management Pack and then import the native Exchange Server 2007 Management Pack.

In this scenario, you lose all the historical data of the converted management pack, including reporting data.

Keep the previously released, converted management pack and use a second management group and multi-homing for the new, native management pack.

You keep the history from the converted management pack, including reporting data.

A more complex approach with the overhead of setting up a second management group for the native management pack and multi-homing the Exchange 2007 agents to report to both management groups. Disable the Exchange 2007 synthetic transactions from one of the management groups because synthetic transactions consume CPU, disk IO, and memory resources on the Exchange 2007 servers. Eventually, you should disable the converted management pack synthetic transactions because the native management pack synthetic transactions use fewer resources on the Exchange 2007 servers.

Keep the previously released, converted management pack and plan a gradual introduction of the new, native management pack by enabling server role discoveries on a server-by-server basis.

You keep the history from the converted management pack, including reporting data. There is less complexity because you only use one management group.

An increasingly complex end-to-end migration solution because, although you avoid using a second management group, you incur management overhead on a server-by-server basis to enable server role discoveries of the native management pack. As you enable servers to be discovered by the native management pack, you must disable the discoveries for the same servers in the converted management pack. There is additional administrative overhead to run the Operations Manager Remove-disabledMonitoringObject cmdlet to remove the converted management packs objects from the management group in order to avoid running synthetic transactions from both management packs at the same time.

If You Run Both Management Packs on the Same Server

If you are running both management packs in parallel on the same server, you should disable synthetic transactions from one of the management packs. The table provides information to help you identify and disable the duplicate set of synthetic transactions. For reference, see the information about the transaction rules in the converted Exchange Server 2007 Management Pack.

 

Synthetic Transaction Target

Execute: Test-ActiveSyncConnectivity (Internal) diagnostic cmdlet. (Report Collection)

Microsoft Exchange 2007 Client Access Servers Installation

Execute: Test-ExchangeSearch cmdlet.

Microsoft Exchange 2007 Mailbox Servers Installation

Execute: Test-IMAPConnectivity diagnostic cmdlet.

Microsoft Exchange 2007 Client Access Servers Installation

Execute: Test-Mailflow (Local) diagnostic cmdlet. (Report Collection)

Microsoft Exchange 2007 Mailbox Servers Installation

Execute: Test-Mailflow (Remote) diagnostic cmdlet. (Report Collection)

Microsoft Exchange 2007 Mailbox Servers Installation

Execute: Test-MAPIConnectivity diagnostic cmdlet. (Report Collection)

Microsoft Exchange 2007 Mailbox Servers Installation

Execute: Test-OwaConnectivity (Internal) diagnostic cmdlet. (Report Collection)

Microsoft Exchange 2007 Client Access Servers Installation

Execute: Test-POPConnectivity diagnostic cmdlet.

Microsoft Exchange 2007 Client Access Servers Installation

Execute: Test-ReplicationHealth diagnostic cmdlet. (Report Collection)

Microsoft Exchange 2007 Mailbox Servers Installation

Execute: Test-ServiceHealth diagnostic cmdlet.

Microsoft Exchange 2007 All Servers Installation

Execute: Test-SystemHealth diagnostic cmdlet.

Microsoft Exchange 2007 All Servers Installation

Disabling Discoveries in the Converted Management Pack

If you are keeping the previously released, converted management pack and doing a gradual introduction of the new, native management pack, as you enable servers to be discovered by the new management pack, disable the discoveries for the same servers in the converted management pack. In this way, you can remove the converted management pack on a server-by-server basis.

 

Discovery Name

Microsoft.Exchange.2007.Microsoft_Exchange_2007_All_Servers_Installation.Discovery

Microsoft.Exchange.2007.Microsoft_Exchange_2007_Client_Access_Servers_Installation.Discovery

Microsoft.Exchange.2007.Microsoft_Exchange_2007_Edge_Transport_Servers_Installation.Discovery

Microsoft.Exchange.2007.Microsoft_Exchange_2007_Hub_Transport_and_Edge_Transport_Servers_Installation.Discovery

Microsoft.Exchange.2007.Microsoft_Exchange_2007_Hub_Transport_Servers_Installation.Discovery

Microsoft.Exchange.2007.Microsoft_Exchange_2007_Mailbox_Servers___CMS_and_Physical_Computers_Installation.Discovery

Microsoft.Exchange.2007.Microsoft_Exchange_2007_Mailbox_Servers_Installation.Discovery

Microsoft.Exchange.2007.Microsoft_Exchange_2007_Unified_Messaging_Servers_Installation.Discovery

Migrating Settings from the Converted Management Pack

This section provides information to help you migrate settings from the converted Exchange Server 2007 Management Pack.

Mapping Classes Between the Management Packs

The following table lists possible targets that you can have for overrides in the converted management pack and the corresponding targets that may be required in the native management pack. Note that in some instances, many targets are possible because the native management pack has a richer model.

 

Converted MP Class Override Target Native MP Class Override Possible Target

Microsoft.Exchange.2007.Microsoft_Exchange_2007_All_Servers_Installation, Ex. Common

Exchange 2007 Best Practice

Exchange 2007 Common Components

Exchange 2007 Extensible Storage Engine

Exchange 2007 Mailbox Database Disk

Exchange 2007 Mailbox Log Disk

Exchange 2007 Queue Disk

Microsoft Exchange 2007 Client Access Servers Installation, Ex. Client Access

Exchange 2007 Client Access Role

Microsoft Exchange 2007 Mailbox Servers Installation, Ex. Mailbox

Exchange 2007 Mailbox Role

Exchange 2007 CCR Clustered Mailbox Server Role

Exchange 2007 SCC Clustered Mailbox Server Role

Exchange 2007 Standalone Mailbox Role

Microsoft Exchange 2007 Edge Transport Servers Installation, Ex. Edge Transport

Exchange 2007 Transport Common Role

Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft. All rights reserved.