The cmdlets themselves have descriptive names such as Test-Mailflow, Test-MAPIConnectivity, Test-ActiveSyncConnectivity, and so on. You can see the full list by using Get-Command in the Exchange Management Shell.
[PS] C:\>Get-Command -Verb Test | Where Module -match $env:computername
Tip: You could also just run “Get-Command –Verb Test”. The point of filtering the output by Module is to keep some other Test-* cmdlets that aren’t part of the Exchange module from appearing in the results.
As you can see there are quite a lot of test cmdlets available for administrators to use. In reality some of the test cmdlets are more commonly used than others, and a few are primarily used by services such as System Center Operations Manager (SCOM) rather than by the administrators.
Though it is not practical to explore every test cmdlet in depth let’s take a closer look at some of the test cmdlets that you may find yourself using more frequently than others.
- Creating the Test Mailbox User
- Using Test-ReplicationHealth to Test DAG Members
- Using Test-MAPIConnectivity to Test Mailbox Databases
- Using Test-ServiceHealth to Verify Required Services are Running
- Using Test-Mailflow to Verify End to End Mail Delivery
- Using Test-ActiveSyncConnectivity to Verify Exchange ActiveSync
- Using Test-OutlookWebServices to Verify Web Services Functionality
- Using Test-MRSHealth to Verify the Mailbox Replication Service
- Using Test-PowerShellConnectivity to Verify PowerShell Remoting