Certificate Requirements

The Director role in Lync Server 2013 is much like any other role in that it uses certificates both for communication to other servers and for client services. There are three types of certificates a Lync Server 2013 Director requires, each with slightly different naming requirements. All three purposes and required names are usually combined on a single certificate, but can be broken out separately if required. These are the three types:

• Default—The default certificate is used for MTLS communications between servers, and for securing SIP signaling in client communications. The certificate should contain the pool name in the subject field, each Director’s name as a subject alternative name, and any internally supported SIP domains as a subject alternative name in the sip.<SIP Domain> format.

• WebServicesInternal—The WebServicesInternal certificate is used to secure communication for internal clients to the web services. This certificate should contain the internal web services FQDN defined in the topology for the pool and any simple URLs such as dialin, meet, lyncdiscover, and admin. This certificate is bound to the internal web services website in IIS.

• WebServicesExternal—The WebServicesInternal certificate is used to secure communication for internal clients to the web services. This certificate should contain the external web services FQDN defined in the topology for the pool and any simple URLs such as dialin, meet, lyncdiscover, and admin. This certificate is bound to the external web services website in IIS.