Ran into an interesting failure while testing a newly deployed OCS 2007 R2 Edge server on a Windows Server 2008 R2 64-bit server that I thought was worth a blog post because what ended up fixing it seemingly had nothing to do with the error message. First off, I actually made the mistakes of selected 5061 as the port instead of 443 which was what I intended to do. The reason why I made this mistakes was:
- I did not select the auto discovery option because the ISP managed to incorrectly create the public SRV records 3 times.
- I didn’t pay attention while manually entering the settings.
Though I had selected the wrong port, I did learn something out of this and it was one of the many reasons that could possibly cause https://www.testocsconnectivity.com/ to throw the error message:
“Testing SSLCertificate for validity.”
You use https://www.testocsconnectivity.com/ to test your newly deployed OCS 2007 R2 Edge server but run into the following results:
As I noted above, this can be caused by other reasons and the following is only one of the reasons.
What I found was that the edge servers weren’t defined in the Edge Servers tab in the Office Communications Server Global properties.
Once I filled in the servers, this error from https://www.testocsconnectivity.com/ (Microsoft Office Communications Server Remote Connectivity Analyzer) went away.
I found this extremely strange because the error referenced the SSL certificate yet this didn’t seem like something that would cause such an error.