Exchange 2010 SP1 Management Pack ships. Version 14.02.0071.0


Get it from the MS Download site:


This is a much expected and anticipated release… the updated version of the Exchange 2010 MP to support Exchange 2010 Service Pack 1.



Changes in This Update:


The Exchange 2010 SP1 version of the Exchange 2010 Management Pack includes significant improvements beyond those included in the RTM version of the Exchange 2010 Management Pack. The following list includes some of the new features and updates:

· Capacity planning and performance reports   New reports dig deep into the performance of individual servers and provide detailed information about how much capacity is used in each site.

· SMTP and remote PowerShell availability report   The management pack now includes two new availability reports for SMTP client connections and management end points.

· New Test-SMTPConnectivity synthetic transaction   In addition to the inbound mail connectivity tasks for protocols such as Outlook Web App, Outlook, IMAP, POP, and Exchange ActiveSync, the Management Pack now includes SMTP-connectivity monitoring for outbound mail from IMAP and POP clients. For information about how to enable this feature, see Optional Configurations.

· New Test-ECPConnectivity view   Views for the Exchange Control Panel test task are now included in the monitoring tree.

· Cross-premises mail flow monitoring and reporting   The Management Pack includes new mail flow monitoring and reporting capabilities for customers who use our hosted service.

· Improved Content Indexing and Mailbox Disk Space monitoring   New scripts have been created to better monitor context indexing and mailbox disk space. These new scripts enable automatic repair of indexes and more accurately report of disk space issues.

· The ability to disable Automatic Alert Resolution in environments that include OpsMgr connectors   When you disable Automatic Alert Resolution, the Correlation Engine won't automatically resolve alerts. This lets you use your support ticketing system to manage your environment. For information about how to disable this feature, see Optional Configurations.

· Several other updates and improvements were also added to this version of the Management Pack, including the following.

· Suppression of alerts when the alerts only occur occasionally was added to many monitors.

· Most of the event monitors in the Exchange 2010 Management Pack are automatically reset by the Correlation Engine. Automatic reset was added to those event monitors so that issues aren't missed the next time they occur. For a list of the event monitors that are not reset automatically, see Understanding Alert Correlation.

· Monitoring was added for processes that crash repeatedly.

· Additional performance monitoring was added for Outlook Web App.

· Monitoring of Active Directory access was improved.

· Monitoring of anonymous calendar sharing was added.

· Reliability of database offline alerts was improved.

· Monitoring for the database engine (ESE) was added.



Installation Notes:


  • When you install the MSI download – this is not like all our other MP’s.  This MSI actually installs the Exchange Correlation engine with no prompts or warnings.  Keep that in mind… so it is best to extract/install this MSI where you want the correlation engine to be installed!
  • My first attempts to install this on my RMS kept failing.  The problem was UAC…. this MSI doesn’t seem to invoke UAC…. so you get an “installation was interrupted” error when you try to install it.  When I opened a CMD prompt as an Administrator (elevated) and then called the MSI – it installed just fine. 
  • When you install the MP/Correlation engine – you may get an error that the correlation files cannot be updated, and a restart will be required.  Even if you stop the correlation engine service – you will be prompted for a reboot.  Therefore – plan for this update to require an outage/downtime of your RMS for a reboot (or wherever the server hosting the Exchange Correlation engine is located)



For some troubleshooting the Correlation Engine events, or Clustering the Exchange 2010 Correlation Engine service – see my previous post:



One of the previous issues I wrote about with the older Exchange 2010 MP was Config Churn .  I can now verify this new MP resolves all of those issues, the discoveries have been updated with NULL values for the previous properties which changed with each run of the discovery – DB Space, DB Size, Log Size, and AD Site:




As you can see from the above screenshot – new entities are being discovered with the empty values – by design.  One thing to note – for a short time you might see duplicate Mailbox Database objects until the discoveries are complete.  It appears we are actually creating new discovered mailbox objects, therefore if you had any explicit overrides in place those wont apply to these new entities… so make sure you put those back in place if needed.  If you had previously placed an override on the discoveries which were causing churn to one day – you can remove those overrides now if you so desire, as they will not be necessary.

Comments (10)

  1. martit01 says:

    Thanks Kevin,  

    How much time did it take for your Exchange servers to get discovered?  It's been about 30 minutes for me and I don't see anything discovered yet.



  2. Kevin Holman says:

    @martit01 – several hours.  Always wait 24 hours before considering troubleshooting a new MP discovery process.  Bouncing the healthservice on the agents helps speed up the process sometimes… as discoveries without a synch time set will run at agent startup.

    @Ramesh – yes – the package is still replicating.  Try also to use a different browser/machine than you used before, as caching can cause a same named package to appear to download the old one previously downloaded but still in cache.

    @Rafal – you MUST update the CE as well – there are many files in the package for the CE service, which are required to work with this new MP.  You cannot just update the MP only – this is why this MP should not be avaiable for direct import from the UI web catalog service.

  3. Awesome says:

    Looking forward to testing it

  4. Ramesh says:

    Kevin – This is still pointing to the old link and does not have the SP1 MP yet! Looks like they have just updated the quick details…Could you please verify?…/details.aspx

    Exchange Server 2010 Management Pack Guide.doc                                 1.5 MB                    Download

    Exchange2010ManagementPackForOpsMgr2007-EN-i386.msi               6.0MB                    Download

    Exchange2010ManagementPackForOpsMgr2007-EN-x64.msi                 6.0MB                    Download

    Quick Details


    Version:                                                                                                                  14.02.0071.0

    Date Published:                                                                                                    4/6/2011

    Change Language:                  English                Change

  5. Rafal says:

    Do I have to install everything from begining having Exchange 2010 MP already installed in SCOM, or I could just extract *.msi and import only managemant packs?

    Ramesh your right, still old version on the server.



  6. Ramesh says:

    Thanks Kevin

  7. Ramesh says:

    Thanks Kevin – I'm seeing lot of 4503 events with the following description.It happens for a variety of rules, not just the one below.

    A module reported an error 0x80FF001B from a callback which was running as part of rule "_C187B89E_5B8B_4F1F_A2CD_4F0DCBA0ADE6_.RaiseAlert" running for instance "" with id:"{D78C9A55-A2CE-B30A-F81F-EBF1AB564FC1}" in management group "SCOMLAB".

    Any pointers?

  8. Peter says:

    Is there a problem with the download page? I still get the old MP from the download site.

  9. Rem-8 says:

    I'm getting the same issues as Ramesh. Any idea?

  10. rupesh says:


    I'm getting the same issue as Ramesh and Rem-8, did you find a solution to this

    EVENT 4503

    A module reported an error 0x80FF001B from a callback which was running as part of rule "ManyDatabaseServices.DependsOn.DatabaseService.AvailabilityReverseRollup.RaiseAlert" running for instance "" with id:"{6513A03A-5748-A755-7251-6E1B661B9EC6}" in management group "CoreMG".



Skip to main content