Presentation is loading. Please wait.

Presentation is loading. Please wait.

Monitoring Exchange 2010 with System Center Operations Manager Matt Goedtel, Microsoft.

Similar presentations


Presentation on theme: "Monitoring Exchange 2010 with System Center Operations Manager Matt Goedtel, Microsoft."— Presentation transcript:

1 Monitoring Exchange 2010 with System Center Operations Manager Matt Goedtel, Microsoft

2 Review Exchange Correlation Engine Understand What’s Monitored Agenda Recommended Configuration Introducing Exchange 2010 MP

3 One of the most comprehensive management packs released by Microsoft. −1423 Rules −658 Performance Collection −707 Alert Generating −854 Unit Monitors −57 Discovery Rules −412 Relationships −229 Classes New version ( ) released on 8/31 addresses several key bugs Supported on OM 2007 SP1/R2 and 2012

4 What’s Monitored All core components in an Exchange 2010 deployment: −Mailbox Server −Client Access Server −Edge Server −Hub Transport −Unified Messaging Synthetic monitoring using PowerShell scripts included with Exchange to proactively monitor (on-server not remote) such as: −Test-OWAConnectivity −Test-MAPIConnectivity −Test-OutlookConnectivity

5 Correlation Engine Fundamentally a custom connector written with the OM SDK. −On OM 2007 R2, recommended its installed on RMS −On OM 2012, recommended its installed on MS with RMS Emulator Configured to auto-resolve alerts Queries RMS every 5 minutes to minimize performance impact Disabling CE prevents alert generation Maintenance mode works as expected.

6 Correlation Factors KHI Monitors watching for specific diagnostics from Exchange (event, performance, and script), change state but do not generate an alert. There are three different Alert Classification categories - Key Health Indicators (KHI), Non- Service Impacting (NSI), and Forensic. −When NSI monitor changes health state, a corresponding alert is generated. −KHI monitors are evaluated, and "chains" of critical severity KHI monitors are isolated and the dependency/relationships evaluated to raise alert for the root cause monitor in the chain. −Forensic monitors do not generate alerts when they change state.

7 Exchange 2010 MP – The Correlation Engine

8 Monitoring Prerequisites All Exchange servers must have an agent installed. Agents must be healthy to avoid any false-positive alerts from CE. All Exchange servers in an Exchange Site must be in the same management group. OM is a object oriented monitoring tool, and understanding number of managed objects/instances is important. −Maximum number of Managed Objects: 800,000 −Maximum number of Relationships: ~1,000,000 −CE hard limit is 600,000 Relationships and a million Group Object Members

9 Optimizing Operations Manager Follow the guidance highlighted in KB Article – −On the 2007 RMS −Each MS in All MS Resource Pool

10 Optimizing Operations Manager −Only applicable for all 2007 SP1/R2 management servers:

11 Optimizing Operations Manager Update the Data Warehouse processing timeout from 5 minutes to 15, perform the following on all management servers (including RMS/RMSe): [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microso ft Operations Manager\3.0\Data Warehouse] "Command Timeout Seconds "=dword:

12 Tuning Recommendations KHI Unit Monitors do not generate alerts, the corresponding alert rules do. −Disable the monitor via override and then disable the alert rule. −If you only disable the rule, bad things can happen! Modification of alert Severity or Priority is done by overriding the corresponding alert rule. KHI Alert rules target the RMS class!

13 Tuning Recommendations Enable only the performance collection rules you need. New-TestCASConnectivityUser.ps1 may fail if there are multiple “Users” OUs defined in AD. −When running script, specify the OU as argument Disable event collection rules as they consume a lot of unnecessary DB space. Review thresholds and revise for monitors using performance counter data source. Custom Alert fields 5, 6, 7, 8, & 10 are used by the CE.

14 Tuning Recommendations May see false-positive alerts from: −KHI: HTTP Connectivity with Autodiscover - Unexpected Exception −KHI: HTTP Connectivity Against Local Server - Address Book failure (ABREF) −KHI: HTTP Connectivity Against Local Server - Address Book failure (NSPI) −KHI: HTTP Connectivity Against Local Server - RPC Client Access failure (Connect) −KHI: TCP Connectivity Against Local Server - Unexpected Exception - Outlook Connectivity (Local Server)

15 Discussion

16 References My Blog: Exchange Team Blog: Guidance and Known Issues with Exchange 2010 KB (Pre-SP1/SP2) - Download of MP: us/download/details.aspx?displaylang=en&id=692http://www.microsoft.com/en- us/download/details.aspx?displaylang=en&id=692 OpsMgr TechNet Wiki: rticles/245.system-center-operations-manager survival-guide-en-us.aspx

17 © 2009 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.


Download ppt "Monitoring Exchange 2010 with System Center Operations Manager Matt Goedtel, Microsoft."

Similar presentations


Ads by Google