New Exchange 2007 Management Pack and Keeping Old Management Pack Data

New Exchange 2007 Management Pack and Keeping Old Management Pack Data

  • Comments 6
  • Likes

 

One of the scenarios supported by the new Exchange 2007 MP (6.0.6623.0) is to keep the Exchange 2007 Converted MP (6.0.6461.0) installed.  This allows you to keep your historical data from the old Exchange MP, while gaining the advantages of monitoring your Exchange 2007 servers with the new Management Pack.  In order to do this you need to disable the monitoring from the old MP to avoid duplication of monitoring.    This can be done with the attached unsealed management pack.. 

The management pack, Microsoft.Exchange.2007.Disable.xml, will disable all the rules and monitors in the converted Exchange 2007 MP.  It uses enforced overrides to attempt to disable the monitoring even over any existing overrides you may have in your management group.   Using this MP should avoid duplication of alerts, one raised by the old converted MP and one raised by the new MP and also avoid running the synthetic transactions from the old converted MP.

Edit: Updated the Attached MP, the version here was incorrect as it disabled the discoveries as well.

Attachment: Microsoft.Exchange.2007.Disable.zip
Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
  • <p>Hi,</p> <p>Some addonns on your good post:</p> <p>You are only talking about keeping the historical data thats in the operations database I guess. Because the data in the DHW is not groomed until the specified limiet. Most people only use the DWH for there historical reporting.</p> <p>p.s I guess we must NOT to disbale the old converted exchange discoverys if we use your mp. Other wise the exchange targets will be groomed afterall (24h) and then also the historical data stored in the operational db.</p> <p>michel. </p>

  • <p>Hi Michel,</p> <p>You are correct the discoveries should not be disabled. &nbsp;I accidentally posted the wrong MP originally, and have updated it to not disable the discoveries so the converted MPs Exchange objects should remain along with their data.</p>

  • <p>Steven,</p> <p>Some add-on on my last post. You can disable the exchange discovery’s as long you do NOT run the “Remove-DisabledMonitoringObject” cmdlet . Be aware even if you run this cmdlet for a other discovery it will delete also the exchange targets belonging to the disabled discovery’s.</p> <p>Michel</p>

  • <p>Hi Steven.</p> <p>Is this Management pack also gonna be availible for SCOM 2007 without R2?</p> <p>I love to get rid of the converted MP for exchange 2007...</p> <p>Best Regards</p>

  • <p>our Exchange cluster mailboxes are showing up as &quot;not monitored&quot; once we went to R2. &nbsp;However I can see data for these mailbox clusters.</p>

  • <p>The best place to get answers for questions about the Exchange MP is the System Center forum in particular the management pack section (<a rel="nofollow" target="_new" href="http://social.technet.microsoft.com/Forums/en-US/operationsmanagermgmtpacks/threads">http://social.technet.microsoft.com/Forums/en-US/operationsmanagermgmtpacks/threads</a>). &nbsp;Myself, and many MVPs who work with the MP look there regularly.</p> <p>As to the cluster not monitored, this is likely normal. &nbsp;The Exchange MP monitors the Exchange Virtual Server network name, but not the other network names that are in the cluster. &nbsp;By default the network names of a cluster will not be monitored unless an MP specifically monitors them.</p>