Exchange 2013 Managed Availability Trouble Shooter (MATS)
Microsoft Exchange 2013 introduced us to Managed Availability, with the aim of providing a mechanism to “detect and recover from problems as soon as they occur and are discovered by the system”
However, as Tony Redmond explains with great clarity and insight here
“Because of the blizzard of data generated by Managed Availability and the sheer number of probes, monitors, and responders required to measure all of the interactions and processing that happen within a complex software product like Exchange, it can be confusing to understand just what data is being gathered and why”
One of the presentations at MSIgnite 2015 was a new tool called the Managed Availability Trouble Shooter (MATS). Available to download here. This tool is intended to streamline the troubleshooting of Managed Availability in Exchange 2013. We’ve been looking at this tool and we think it will go a long way towards helping decipher the vast array of logs created by Managed Availability.
In this article we’ll be looking at:
Logging into M.A.T.S.
- Download the tool from the TechNet Gallery here and run the mats.exe executable.
- Enter the FQDN of your Exchange server e.g. http://ex2013svr01.testlab.local/powershell
- Click Connect. Enter your credentials
https://shanejacksonitpro.files.wordpress.com/2015/05/mats1.png?w=297
Note: If you don’t enter the FQDN you will get an error
When one or more Exchange servers are found, click the drop down menu and select an Exchange server
https://shanejacksonitpro.files.wordpress.com/2015/05/mats2.png?w=300
You're now connected.
Performing a Health Check with M.A.T.S
For general health checking we have two options:
- Health Report
- Server Health
https://shanejacksonitpro.files.wordpress.com/2015/05/mats3.png?w=300
Health Report
Click on the Health Report button which provides the output of Get-HealthReport in a grid format.
https://shanejacksonitpro.files.wordpress.com/2015/05/mats4.png?w=300
You can quickly see in this example that the Network is reporting unhealthy
https://shanejacksonitpro.files.wordpress.com/2015/05/mats5.png?w=300
Server Health
Click on the Server Health button gives us another grid listing all the probes and their last value
https://shanejacksonitpro.files.wordpress.com/2015/05/mats6.png?w=300
https://shanejacksonitpro.files.wordpress.com/2015/05/mats7.png?w=300
Troubleshooting Exchange using M.A.T.S
Where this tool is most effective is in troubleshooting specific issues.
- Click on Critical Events
- Select a test to perform g. OWA
- Click Get Results
https://shanejacksonitpro.files.wordpress.com/2015/05/mats8.png?w=300
As you can see from the output below, you can very quickly see detailed information about any issues which may be occurring
https://shanejacksonitpro.files.wordpress.com/2015/05/mats9.png?w=300
The documentation for this tool (included in the tool download) details what each of the available tests does:
- High Availability: Would you like to check on the status of your DAGS? Just use the HA option in the Critical Events dropdown as shown below and then click on “Get Results”.
- AD: Checks the status of this server and Active Directory-related information or errors
- EWS: Checks the status of any Exchange Web Services related information or errors.
- HM: Checks the status of any Health Management related information or errors
- Monitoring: This was explained above however, this will display all events that have been “Escalated” for an administrator to review.
- OutlookMapiHttp: If this is enabled in your environment it will display any information or errors related to MAPI/HTTP.
- OutlookRPC: Will display any information or errors related to Outlook Anywhere.
- OWA: Will display information and errors related to Outlook Web Access
- Perf: Reviews system and application logs for any performance information or errors.
- Recovery: This was mentioned above as well, but to review it displays and Managed Availability Recovery Actions on the server selected.
- Store User: Displays any Store related information or errors on the selected server.
You can then go a step further and check the Probe Failures, to help determine exactly where the problem is coming from:
- Click LAM Results (LAM = Local Active Monitoring)
- Select a test (or all tests)
- Select a Working Type Item (e.g. Probes)
- Click Get Results
https://shanejacksonitpro.files.wordpress.com/2015/05/mats10.png?w=300
As you can see from the output below, very detailed information is presented in an easy to navigate, searchable format
https://shanejacksonitpro.files.wordpress.com/2015/05/mats11.png?w=300
So there you have it... a quick look at the MATS tool and how it can be used for troubleshooting and health checking Exchange 2013. Overall this a great tool and one that every Exchange admin should be using.