Kevin Holman's System Center Blog

Posts in this blog are provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified in the Terms of UseAre you interested in having a dedicated engineer that will be your Mic

OpsMgr: MP Update: Exchange 2010 SP2 MP version 14.02.0247.005 (14.3.38.2 actual mp version) is released

OpsMgr: MP Update: Exchange 2010 SP2 MP version 14.02.0247.005 (14.3.38.2 actual mp version) is released

  • Comments 16
  • Likes

 

****Note 14.3.38.2 has been pulled.  If you implemented this already, please see

http://blogs.technet.com/b/exchange/archive/2012/06/28/mailboxes-on-a-database-are-quarantined-in-an-environment-with-system-center-operations-manager.aspx

 

 

 

 

Version 14.02.0247.005 (14.3.38.2 MP version) of the Exchange 2010 MP has been updated.  This is the SP2 compatible version of the MP that many have been expecting.

Available here:  http://www.microsoft.com/en-us/download/details.aspx?id=692

 

What’s new?  From the guide:

 

  • Resolved ObjectNotFoundExceptions in correlation engine   The SP1 version of the Correlation Engine could encounter ObjectNotFoundExceptions on a regular basis.  The number of exceptions of this type is significantly reduced in this update.
  • Reduced load on RMS/MS   A number of improvements were made to reduce the load of the Management Pack on the RMS/MS.  The following specific changes were made:
    • Reduced the number of read operations the Correlation Engine makes to the SDK to get entity and monitor states
    • Improved cache handling in Correlation Engine when Management Pack updates are applied
    • Increased correlation interval time from 1.5 minutes to 5 minutes
  • Reduced load due to discovery  The discovery interval was increased from 4 hours to 24 hours and improved handling of Domain Controller objects to decrease churn
  • Improved Database Copy Health monitoring  Replaced KHI: Database dismounted or service degraded with One Healthy Copy monitor to decrease load on RMS
  • Improved Performance monitoring  Non reporting Perf Instances are now enabled by default and some write operations were removed to decrease unnecessary writes to the database

 

Doesn’t sound like to many major changes.  Hopefully this will help the MP scale better for very larger Exchange 2010 environments and have less of an impact on the management group for all environments.

 

My experience:

 

One of the things the guide fails to tell you, is how to *upgrade* to this version of the Correlation Engine and management pack.  It is essentially the same process as installing new.  Just keep in mind if you had previously customized items or configuration, you will need to revisit those customizations.

 

I download and install the correct MSI of the Exchange pack for my OS version (64bit), by executing Exchange2010ManagementPackForOpsMgr2007-x64.msi.

As you step through the installer, you need to ensure you provide the correct locations if you had changed these previously.

image

 

The install/extraction begins…. it can hang for a long time on “Stopping Services”:

 

image

 

When complete:

 

image

 

Apparently this update is going to require a reboot of your management server where you run the Exchange correlation engine, so be prepared for that!

 

image

 

Log Name:      Application
Source:        MsiInstaller
Date:          6/18/2012 12:42:34 PM
Event ID:      1038
Task Category: None
Level:         Information
Keywords:      Classic
User:          OPSMGR\kevinhol
Computer:      OMMS2.opsmgr.net
Description:
Windows Installer requires a system restart. Product Name: Microsoft Exchange 2010 Management Pack for OpsMgr 2007. Product Version: 14.3.38.2. Product Language: 1033. Manufacturer: Microsoft Corporation. Type of System Restart: 2. Reason for Restart: 0.

So, I reboot my management server that is running the correlation engine. 

 

First thing I noticed – is that my service was reset from running as my SDK account, back to local system.  This is not documented behavior so watch out, if you were previously running your correlation engine under a defined account.

image

 

 

Next – I go looking for the updated management packs, in the default folder:

Before:

image

After:

image

 

So I import the two updated MP’s.  You can see for some reason the download version and MP version don’t match for these MP’s.

image

 

We can also see the updated version in Programs and Features:

Before:

image

After:

image

 

 

Next, I’ll have a peek at the actual correlation engine binary and config files:

 

Before:

image

After:

image

 

Open up my Microsoft.Exchange.Monitoring.CorrelationEngine.exe.config file:

 

Before:

image

After:

image

 

You can see – we have changed the interval for the CE to connect to the SDK to every 5 minutes, from 90seconds.  We apparently have also change the logging days kept from 7 to 30 days, which is kept at C:\Program Files\Microsoft\Exchange Server\v14\Logging\MonitoringLogs\Correlation

 

Overall, pretty straightforward.

Comments
  • Just a heads up for anyone using this MP, there is a very useful FP article here:

    support.microsoft.com/.../2592561

    We've had an issue on site where the data aggregation was stalling and we were getting 31552 errors in the Operationa Management log - we opened a call and were directed to the following section:

    SCOM Data warehouse: (Where applicable.)

    The Exchange 2010 MP adds some new Datasets to the SCOM DW for custom reporting.  These new datasets have their own set of aggregations that can take a bit more time to complete than normal.  Thus, you need to increase the timeout for DW processing to allow these aggregations to finish.

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Operations Manager\3.0\Data Warehouse]

    "Command Timeout Seconds "=dword:00000384 – Updates the DW processing timeout from 5 minutes to 15 minutes.

    Note: This needs to be done on every Management Server (including the RMS).

    Note:  This may require to be up to 30 minutes for the timeout depending on how much data flow there is.  (Mainly event and performance collection.)

    This has allowed the data to be aggregated correctly and the 31552 error has gone away.

    Cheers!

  • Hi Kevin,

    Any idea where this has gone? At the moment I can't find an Exchange MP to download anywhere!!!?

  • @John - the download is broken or pulled.  Checking into it.

  • The connect-hosted update to the Sharepoint MP has disappeared too! Not having a great week here!

  • social.technet.microsoft.com/.../00e8dda9-f4c7-4212-8598-8e4fc3b7434e

  • Hi Kevin,

    I just tried to download version 14.02.0247.005 (14.3.38.2 MP version), but the link near the top of this article appears to still be broken. Can you please provide the location of the management pack? Thanks!

  • New MP www.microsoft.com/.../details.aspx  .. 14.03.0038.003 :) let`s se...

  • Nice...again "We are sorry, the page you requested cannot be found"

  • Link is active now.

    www.microsoft.com/.../details.aspx

    Microsoft Exchange Server 2010 monitoring management pack

    Version: 14.03.0038.004 Date published: 8/31/2012

    Exchange2010ManagementPackForOpsMgr2007-x64.msi 6.2 MB

  • Can you quantify this statement "Just keep in mind if you had previously customized items or configuration, you will need to revisit those customizations"?  Does that mean I have to recreate all of my overrides or does that just refer to manual customization of the config file?  Thanks!

  • @DDog80 -

    Overrides persist across MP's.  I meant the configuration file.

  • Hi Kevin,

    What is the recommended sequence for this "upgrade"? We are currently running Exchange 2010 SP1 in production environment, and will be upgrading to SP2 soon and current Exchange MP in use is 14.2.71.0.  My question is should we install this latest (14.3.38.2) version only when the Exchange Server 2010 infrastructure has fully upgraded to SP2 or install this latest MP prior to SP2 upgrade? Our priority is to ensure no interruption in monitoring during this E2K10 SP2 deployment.

    Thanks.

  • I see the latest version is 14.03.0038.004.  Does this still require disabling the 4 monitors according this the Exchange Team blog workaround here for the previous releases: blogs.technet.com/.../mailboxes-on-a-database-are-quarantined-in-an-environment-with-system-center-operations-manager.aspx

    Or has that been resolved?

  • Hi Kevin,

    We are running Exchange 2010 SP1 and SCOM 2012 SP1, but I can't find an Exchange MP that's for SCOM 2012SP1. Kindly advice what Exchange MP version will run on SCOM 2012 SP1 deployment.

    Regards

  • Hi Kevin; Our SCOM 2012 R2 server running on platform Windows 2012 R2. The question; is Exchange 2010 SCOM Management Pack build 14.03.0038.004 released supported?

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
Search Blogs