Test cmdlet
Exchange Server administration forum

Posts: 98
Joined: Sat Sep 26, 2009 9:57 am
Location: India

Test cmdlet

by ManU » Mon Mar 28, 2011 11:31 am

Cmdlets used for testing the proper working of your Exchange organization

Here are some important cmdlets used in Exchange 2010 (Most of them are applicable to Exchange 2007 also) to test whether the exchange organization, works as expected:

Test-ActiveSyncConnectivity is used to perform a full synchronization against a specified mailbox to test the configuration of Microsoft Exchange ActiveSync.

Test-EdgeSynchronization should be run from a Hub Transport server that has Edge subscription configured. This is used to test that the subscription is good and that everything is synchronizing properly.

Test-ExchangeSearch can be ran two ways but should be ran from a mailbox role server. It used to detect if the search index for a particular database is healthy. You can run the cmdlet against a whole database or a specific user account.

Use the Test-ImapConnectivity cmdlet to verify that the IMAP4 service is running as expected.

Use the Test-IPAllowListProvider cmdlet to test the configuration for a specific IP Allow list provider on a computer that has the Hub Transport server role or Edge Transport server role installed.

Use the Test-IPBlockListProvider cmdlet to test the configuration for a specific IP Block list provider on a computer that has the Edge Transport server role or the Hub Transport server role installed.

Use the Test-Mailflow cmdlet to diagnose whether mail can be successfully sent from and delivered to the system mailbox on a computer that has the Mailbox server role installed.

Use the Test-MapiConnectivity cmdlet to verify server functionality by logging on to the mailbox that you specify

Use the Test-OutlookWebServices cmdlet to verify the Autodiscover service settings for Microsoft Outlook on a computer running Microsoft Exchange Server 2010 that has the Client Access server role installed.

Use the Test-OwaConnectivity cmdlet to verify that Microsoft Office Outlook Web App is running as expected.

Use the Test-PopConnectivity cmdlet to verify that the POP3 service is running as expected.

Use the Test-ReplicationHealth cmdlet to check all aspects of the replication and replay status to provide a complete overview of a specific Mailbox server in a database availability group (DAG).

Test-SenderId is used to test the senderid reputation from a particular ip address and domain.

Use the Test-ServiceHealth cmdlet to test whether all the Microsoft Windows services that Exchange requires on a server have started. The Test-ServiceHealth cmdlet returns an error for any service required by a configured role when the service is set to start automatically and isn't currently running.

Test-SystemHealthUse the Test-SystemHealth cmdlet to gather data about your Microsoft Exchange system and to analyze the data according to best practices.

Use the Test-UMConnectivity cmdlet to test the operation of a computer that has the Unified Messaging (UM) server role installed.

Use the Test-WebServicesConnectivity cmdlet to perform basic operations to verify the functionality of Exchange Web Services on a server running Microsoft Exchange Server 2010 that has the Client Access server role installed.
Microsoft MVP(Exchange Server)
TechNet Forums Profile: ManU

Users browsing this forum: No registered users and 2 guests

It is currently Thu Mar 22, 2018 1:41 pm