External Edge Server Interface

This certificate should be issued by a public certificate authority. The specific requirements for subject names and subject alternative names for the certificate on the external interface of an Edge Server pool are outlined next. The same certificate and private key should be exported and installed on each member of the same Edge Server pool.

• Access Edge—The subject name should match the published name of the Access Edge FQDN in public DNS. If a hardware load balancer is used, this is the name clients resolve to the virtual IP address. The subject alternative name field should contain any supported SIP domains in the sip.<SIP Domain> format.

• Web Conferencing Edge—The subject name should match the published name of the Web Conferencing Edge FQDN in public DNS. If a hardware load balancer is used, this is the name clients resolve to the virtual IP address. No subject alternative names are required.

• A/V Edge—This service has no certificate associated, but it is included here to provide clarity that the A/V Edge FQDN should not be included in a certificate request.

Lync Server 2013 uses subject alternative name (SAN) certificates in many locations, including the external-facing Edge Server certificate. Organizations typically include the Access Edge, Web Conferencing Edge, and any supported SIP domains on a single certificate to reduce maintenance costs and overhead.