The process works perfectly fine for mailboxes on Exchange 2010, but when using the Microsoft remote connectivity analyzer it fails at “Options” It is worth noting that locally ActiveSync to this same 2003 server fails as well. I have an issue where I am not able to successfully connect via ActiveSync to a 2010 CAS/HUB with mailboxes on Exchange 2003. So next time you’re troubleshooting an ActiveSync problem give the Remote Connectivity Analyzer a go.Īll of your posts are very specific and clear, so thank you in advance. This tool has definitely saved me a lot of time and headaches in the past. The Remote Connectivity Analyzer outputs a test report that breaks down each of the steps that it performed and gives you success/error details for each one, letting you know where you need to start any troubleshooting. There is a lot that can go wrong with an ActiveSync deployment, such as DNS problems, incorrect firewall rules, misconfigured Exchange 2010 SSL certificates, and more. The real value in this tool is how it reports on the results of the test. Performing each test is as simple as filling out a web form. Exchange ActiveSync Autodiscover – tests just the Autodiscover process for automatically determining the server configuration settings.You can perform this test using both Autodiscover and using manually configured server settings. Exchange ActiveSync – simulates all of the steps that a mobile device would use to connect to Exchange and sync mailbox items.The Remove Connectivity Analyzer is a web page that lets you test multiple different connectivity types as though you were sitting outside of the network.
If you ever find yourself needing to test ActiveSync for an Exchange 2010 environment, and you either don’t have an ActiveSync-capable smart phone handy or you’re trying to determine whether the phone you do have might be the problem, you can use the Microsoft Remote Connectivity Analyzer instead. Here is a quick tip for one of the most under-utilized testing tools for Exchange Server 2010.
0 kommentar(er)
