Exchange 2007 Management Packs do not automatically monitor Exchange servers

Exchange 2007 Management Packs do not automatically monitor Exchange servers

  • Comments 4
  • Likes

By default, the Microsoft Exchange 2007 Management Packs for Operations Manager 2007 will not automatically start monitoring of any Exchange 2007 Servers even if you have imported the Management Pack. This means that the servers won’t automatically show up in the Exchange views in the monitoring section of the console.

This behaviort enables you to start monitoring all your servers immediately, or you can proceed more slowly and enable monitoring of a few Exchange servers at a time.

This article discusses how to start monitoring Exchange 2007 Servers.

How to start monitoring of Exchange 2007 Servers

To start monitoring of Exchange 2007 Servers, you will need to enable Exchange discovery in the Management Pack (after you have imported it). You do this per server role (CAS, Mailbox, Hub, etc).

To enable Exchange 2007 Server Role Discovery

1.   Go to the Object Discoveries node located under Authoring in the Operations console.

2.   In the Look for field, type Exchange 2007 Server Role and click Enter. A list of Exchange 2007 Server Role Discoveries appears. You need to enable Server Role Discoveries of the following discoveries:

 

Discovery Name

Description

Exchange 2007 CCR Clustered Mailbox Server Role Discovery

Discovers CCR and SCC clustered Mailbox servers

Exchange 2007 CCR Node Role Discovery

Discovers CCR node servers in a CCR cluster (the physical nodes)

Exchange 2007 Standalone CCR Node Discovery

Discovers standalone CCR node roles (nodes that are participating in log shipping but are not part of an active Mailbox server) and standalone mailbox roles

Exchange 2007 CAS Role Discovery

Discovers Client Access server roles

Exchange 2007 Hub Transport Role Discovery

Discovers Hub Transport server roles

Exchange 2007 Edge Role Discovery

Discovers Edge Transport server roles

Exchange 2007 UM Role Discovery

Discovers Unified Messaging (UM) roles

For example, to enable discovery of all Hub Transport servers, right-click the Exchange 2007 Hub Transport Role Discovery and select Overrides\Enable the Object Discovery\for all objects of type Exchange 2007 Discovery Helper. If you want, you can choose to discover servers using a group (containing Exchange 2007 Discovery Helper instances) or a single instance of Exchange 2007 Discovery Helper. It is also possible to use a group containing the Windows Computer objects of the Exchange servers.

 

You can then go to the “Microsoft Exchange Server 2007\Server State” view in the OpsMgr console to see that the servers are being discovered. Even after you enable discovery, Exchange 2007 discoveries run every 24 hours by default. Ie, it may take up to 24 hours to discover the servers. To speed up the initial discovery, you can restart the OpsMgr agent on the Exchange servers. You can also change the interval of the discovery to have it run more frequently.

What if my servers still aren’t discovered or monitored?

·         First, ensure that you have installed the OpsMgr agent on all the Exchange servers. If you are monitoring Exchange clusters, you need to install the OpsMgr agent on all cluster nodes.

 

·         You should then ensure that you have enabled Agent Proxy on all agents.

To enable agent proxy on managed Exchange 2007 servers

1.   Click the Administration button in the Operations console, and then in the navigation pane, click Agent Managed.

2.   In the Agent Managed pane, right-click an Exchange server, click Properties, click the Security tab, and ensure that the Allow this agent to act as a proxy and discover managed objects on other computers check box is selected. Repeat the process for every managed Exchange 2007 server in the list.

 

·         Then, ensure that the Exchange 2007 Discovery Helper discovery has found your Exchange servers

To verify that Discovery Helper has discovered your Exchange 2007 servers

1.   Ensure that you have not scoped your views.

2.   Go to the Discovered Inventory view in the Monitoring section of the Operations console.

3.   Right-click and choose Select Target Type.

4.   In the Look for field, type Exchange 2007 Discovery Helper, select it, and then click OK. A list of Exchange 2007 servers appears with a status of “Not Monitored.”

If no Exchange 2007 servers are discovered, you might want to make the discovery run more frequently than the default. You can change the interval of the Exchange 2007 Discovery Helper Discovery in Object Discoveries located under Authoring in the Operations console.

 

 

Are you using low-privilege accounts?

The easiest way to get the Management Pack to work is by using Local System as your default agent action account. If you are using low-privilege accounts, you need to setup the appropriate RunAs profiles first to allow the Management Pack to work.

The Microsoft Exchange Server 2007 Management Pack has the following Run As rofiles:

 

Run As profile name

Runs workflows that require

Exchange 2007 Local System Account

Local System privileges on the Exchange 2007 servers. This profile is used by all the Exchange synthetic transactions. The Run As account would require Local System Windows Account privileges on the computer.

Exchange 2007 View Only Local User Account

Exchange View Only Administrator rights. Most of the discovery scripts in the management pack use this profile. The Run As account is required to be a member of the Exchange View-Only Administrators group and be the equivalent of the least-permissions account on the local computer.

 

To populate the Run As profiles, first create the appropriate accounts with the required rights and then populate the profiles. For step-by-step instructions about associating a Run As account with a Run As profile, see the How to Change the Run As Account Associated with a Run As Profile in Operations Manager 2007 topic in Operations Manager 2007 Help (http://go.microsoft.com/fwlink/?LinkId=128539).

Note

The Exchange 2007 Local System Account Run As profile must be populated if you are not using Local System as the default Agent Action Account. 

What registry entries are used by the Exchange 2007 discoveries?

If at this point discovery still does not work, you should ensure that the appropriate registry keys are present on your Exchange servers. Below is a list of the Exchange server discoveries and what registry keys they check to determine if the server is hosting that Exchange 2007 Server role.

 

These keys need to be present for the servers to be discovered correctly. In some cases the discovery logic is somewhat involved. All searches are done in the HKLM hive.

Discovery Name

What’s it do?

Requirements for discovery

Exchange 2007 Discovery Helper

Discovers Exchange servers without applying any monitoring.

Software\Microsoft\Exchange\v8.0 exists

 

Note that this key might exist on administration-only servers as well.

Exchange 2007 CCR Clustered Mailbox Server Role Discovery

Discovers CCR and SCC clustered Mailbox servers

Software\Microsoft\Exchange\v8.0\MailboxRole exists

 

AND

 

the discovery is running on the cluster virtual server  (the IsVirtualNode property on the computer object is TRUE)

 

AND

 

Software\Microsoft\Exchange\Cluster exists

 

AND

 

(Software\Microsoft\Exchange\Cluster\ServerName_MSExchangeSA1 is equal to the computer name of the cluster virtual server where we’re running the discovery

 

OR

 

Software\Microsoft\Exchange\Cluster\ServerName_MSExchangeSA2 is equal to the computer name of the cluster virtual server where we’re running the discovery)

Exchange 2007 CCR Node Role Discovery

Discovers CCR node servers in a CCR cluster (the physical nodes)

Software\Microsoft\Exchange\v8.0\MailboxRole exists

 

AND

 

the discovery is not running on the cluster virtual server  (the IsVirtualNode property on the computer object is FALSE)

 

AND

 

Software\Microsoft\Exchange\Cluster DOES exist

 

AND

 

Software\Microsoft\Exchange\Cluster\ServerName_MSExchangeSA1 is not equal to the computer name of the server where we’re running the discovery

Exchange 2007 Standalone CCR Node Discovery

Discovers standalone CCR node roles (nodes that are participating in log shipping but are not part of an active Mailbox server) and standalone mailbox roles

Software\Microsoft\Exchange\v8.0\MailboxRole exists

 

AND

 

the discovery is not running on the cluster virtual server (the IsVirtualNode property on the computer object is FALSE)

 

AND

 

Software\Microsoft\Exchange\Cluster does NOT exist

Exchange 2007 CAS Role Discovery

Discovers Client Access server roles

Software\Microsoft\Exchange\v8.0\ClientAccessRole exists

Exchange 2007 Hub Transport Role Discovery

Discovers Hub Transport server roles

Software\Microsoft\Exchange\v8.0\HubTransportRole exists

Exchange 2007 Edge Role Discovery

Discovers Edge Transport server roles

Software\Microsoft\Exchange\v8.0\EdgeTransportRole exists

Exchange 2007 UM Role Discovery

Discovers Unified Messaging (UM) roles

Software\Microsoft\Exchange\v8.0\UnifiedMessagingRole exists

 

My standalone mailbox server is STILL not discovered

Sometimes a failed clustered installation may leave behind the Software\Microsoft\Exchange\Cluster key. This means that the discovery will never recognize this as a standalone mailbox server until that key is removed.

My CCR Nodes are STILL not discovered

Standalone CRR Nodes that are not participating in a cluster and are not a log shipping target will not be discovered.

I’m running 3rd party cluster software

The Management Pack does not support this configuration
Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
  • Does it matter if the Mailbox Server in a CCR Cluster is "Monitored By" the Active Node or the Passive Node?

  • The active node will discover and monitor the clustered Mailbox server. OpsMgr will automatically determine the active node.

  • Thanks, not what is happening in my setup....I'll open a case for it.

  • Hello,

    Step 2...

    To verify that Discovery Helper has discovered your Exchange 2007 servers

    1.   Ensure that you have not scoped your views.

    2.   Go to the Discovered Inventory view in the Monitoring section of the Operations console.

    3.   Right-click and choose Select Target Type.

    4.   In the Look for field, type Exchange 2007 Discovery Helper, select it, and then click OK. A list of Exchange 2007 servers appears with a status of “Not Monitored.”

    I could not find it where it says (Right Cick on Discovered Inventory)...

    I have :

    New

    Refresh

    Open in a New Window

    Add to My Workspace

    Cut

    Copy

    Paste

    Delete

    Rename

    Personalize View

    but no target!!!

    So I managed to do the search from the Actions Pane or Actions Menu under State Actions  “Change Target Type”… strange …. Let me know if you find it where it is accordingly to the documentation

    Thanks,

    Dom