External Edge Certificate Requirements

Could somebody help me with this issue.

First off, I just realized that I posted this in the wrong category. We are running Lync Server 2013, not 2010.

I am experiencing every imaginable issue with our Lync deployment possible. Being that I am so new to IT, I do not know a definitive answer to this seemingly elusive question.

We are running Lync Server 2013 Standard Edition single server pool with Mediation Server co-located.

The question is, is it a requirement to have the external access service FQDN as not only the CN, but as well the first SAN entry? I am finding conflicting information across the internet.

Our company would like to use only one single public cert, so I have been trying to make this single public cert work across our Lync deployment. I am wondering whether or not this could be the cause of my woes.

Currently our one public certificate SN is our domain name; contoso.com.

I have consolidated the three edge services (web, access, A/V) into one FQDN and single IP and used three different port number assignments. That FQDN is not the CN of our public cert. It is not even the first SAN entry on this cert.

Please help me.

You are much appreciated.




February 7th, 2015 3:01am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics