http://exchangeserverpro.com/health-check-exchange-2010-mailbox-server
How many times each day do you get asked, “Is there a problem with the Exchange server?”
If you’re like me then you get asked this question at least once per day. Of course there usually isn’t anything wrong with our Exchange servers 
but once the question has been asked then you have no choice but to investigate and confirm that everything is okay.
In this article I’m going to demonstrate how you can quickly check the health of your Exchange Server 2010mailbox servers, and share a script with you that can help to speed up this task.
Exchange Server 2010 has a series of PowerShell cmdlets that make it easy to do a health check of mailbox servers. For example, we can:
- Run Test-Servicehealth to check the required services are all running
- Run Get-MailboxDatabase to check whether the mailbox databases are mounted
- Run Test-MapiConnectivity to verify that the databases are responding to MAPI requests
- Run Test-MailFlow to confirm that email is able to pass successfully between two servers
- Run Get-MailboxDatabaseCopyStatus for DAG members to check the database copy status, queues, and content indexes
That’s quite a few cmdlets to run, especially if we’ve got more than one mailbox server in the organization. And of course each of those cmdlets needs to run and show you output that you need to interpret.
I like to make life a bit easier and use PowerShell scripts to speed up these types of tasks. So naturally I put together a script for performing all of the above tests (and a few more) on my mailbox servers and display a nice simple colour-coded output so that I can tell at a glance whether there might be a problem.
This isn’t designed to do a diagnosis of any problems, it just checks the fundamentals and gives me a simple pass/fail and a few other indicators that I can then troubleshoot further if necessary.
Download the script file here: Test-MailboxServer.ps1 (downloaded 2023 times so far)
Extract Test-MailboxServer.ps1 from the Zip file and run it in your Exchange Management Shell to see output such as this:
