Somebody please help me with this, once and for all.

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 brand 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 and frustrations.

Currently our one public certificate CN 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.

• Edited by Donovan Dickinson 15 hours 57 minutes ago

I had just recently changed that port to 443 two days before posting this thread. I am confidant now to reconfigure that entry back to 5061.

I believe I have the information needed now to share with my supervisor that we need to reevaluate our public certificate requirements.

Thank you so much for your quick responses. This makes so much more sense to me now.