Check Managed Availability Probe Results in application log when your Exchange 2013 server has sustained high CPU

I stumbled upon this neat feature in Exchange 2013. When your Exchange 2013 (and probably later) server is experiencing sustained high CPU, an event 2 error occurs inside your Microsoft-Exchange-ActiveMonitoring\ProbeResult channel. Look for an event with ResultName of EDS/ExchangeProcessorTimeTrigger_Warning/_total. Inside the details view, there are a bunch of top N lists that will give you quick insights…

1

Script: Enable and collect ExTRA tracing across all Exchange servers

Here is a PowerShell script that can be used to kick off an ExTRA trace on every Exchange server in the org and collect the traces into a single location. I’ve highlighted in red the variables you’ll likely want to edit prior to running the script. # Description: # Initiates an ExTRA trace on all…

0

How to take an ExTRA trace of Exchange setup

This blog post is mainly for us Exchange support engineers but I like to surface things externally because it's easier to search and link to. This blog post is heavily inspired by http://blogs.technet.com/b/mikelag/archive/2008/08/22/how-to-enable-store-pfd-tracing-upon-reboot.aspx. With Exchange 2007 and onwards, debug code tracing is logged to the ETW provider GUID 79BB49E6-2A2C-46E4-9167-FA122525D540. When you install Exchange, this ETW provider…

0