Following on the heels of success of the Exchange Remote Connectivity Analyzer (created by Shawn McGrath and Brad Hughes), Premal Gandhi (UC Support Escalation Engineer), Matthew Fresoli (Supportability Program Manager) and Jason Stine (Senior Lead Program Manager) have been busy designing and writing a complimentary tool: The Office Communications Server Remote Connectivity Analyzer.
The tool is available at https://www.TestOcsConnectivity.com
The Office Communications Server Remote Connectivity Analyzer is a web site for IT Administrators to validate and diagnose end-to-end Office Communications Server scenarios. The site simulates multiple Office Communications Server client access scenarios from outside the customer’s infrastructure and reports whether the test was successful. If the test fails, we inform the IT Admin exactly where in the process it failed as well as provide troubleshooting tips on resolving the issue.
In this beta version, the tool provides the following end-to-end tests:
· Office Communications Server Remote Connectivity
· Office Communications Server Remote Connectivity w/AutoDiscover
We will be expanding the Office Communications Server scenarios in the next few months to include the following:
· Deeper level of diagnostic information - MSDiagnostics header
· More detailed troubleshooting information based on MSDiagnostic header
· Additional tests
If you have feedback on the tool or suggestions for additional tests or improvements, please use the feedback link provided on the site.
You need to add another field (Port used if not 443) if there are customers out there that do not use port 443 especially if they use Big IP (or F5) devices as their hardware load balancer.
Good point, and even better feedback. I've relayed this suggestion to Premal (the Escalation Engineer who coded www.testocsconnectivity.com), as well as the PM that is coordinating efforts around this project. I'll try to keep everyone as up-to-date as possible in terms of the additions that we hope to incorporate into this tool ...
I try to put my DOMAIN\username with AD credentials , but it give a authentication error, what's the exact sintax ?
I'm unsure why you're encountering an error, but this may be best addressed by Premal (who wrote this awesome tool) ...
ocsrca (at) microsoft (dot) com