If there is still an issue with a client's ability to connect despite that tool working, then there's an issue with the client's setup or the client's ability to connect to your server from the network it's on. It'll give you detailed feedback about any errors it encounters and will sometimes give you links to ways to fix common misconfigurations. Try RCAįor a one-time test, you can use the Exchange RCA (Microsoft Remote Connectivity Analyzer) here: to test your exchange setup from an outside perspective. See the 2007 documentation, 2010 documentation, 2013 documentation, or look for the cmdlet in newer versions of Exchange in the TechNet library. If you're using Exchange 2007+, if you have the Exchange Management Tools installed on your test system, you can use the automate the Test-ActiveSyncConnectivity cmdlet to monitor whether or not ActiveSync is working properly.

You can set up a script to keep checking this URL (and possibly log in) and see if you get a HTTP 501/505 response. You can visit http(s)://YOURFQDNHERE/Microsoft-Server-ActiveSync to see if you get an authentication prompt.

Microsoft activesync tester