Configuring Client Access Server Synthetic Transactions
Applies To: Exchange Server, Operations Manager 2007 R2
The Microsoft Exchange Server 2007 Management Pack supports a number of synthetic transactions that run on Client Access servers and perform transactions against the Client Access server itself and also the back-end Mailbox servers within the same site as the Client Access server. Examples of these transactions are to check Exchange ActiveSync, Outlook Web Access, and Web Services connectivity. The transactions are implemented using Windows PowerShell cmdlets built into the Exchange 2007 product. Documentation for the Client Access server synthetic transactions supported by the management pack can be found here:
Test-OwaConnectivity (https://go.microsoft.com/fwlink/?LinkId=137732)
Test-ActiveSyncConnectivity (https://go.microsoft.com/fwlink/?LinkId=137733)
Test-WebServicesConnectivity (https://go.microsoft.com/fwlink/?LinkId=137734)
Test-PopConnectivity (https://go.microsoft.com/fwlink/?LinkId=137735)
Test-ImapConnectivity (https://go.microsoft.com/fwlink/?LinkId=137736)
Note
By default, all Client Access server synthetic transactions are disabled.
Note
To use the Client Access server synthetic transactions, you must first perform the steps outlined in the Configuring Exchange Servers to Support Client Access Synthetic Transactions section. You must do this on each agent-managed Mailbox server that you want to use as a target server for the Client Access server synthetic transactions.