Integrating Lync 2013 with Exchange 2013 OWA
In this article we'll go through integrating Lync 2013 with Exchange 2013 OWA. The contents of this article are unashamedly stolen from a colleague, but pointless re-inventing the wheel :).
Scenario
Multiple Exchange 2013 multi-role servers have the same public signed certificate being used for client access. This certificate does not contain the FQDN of the Exchange server as they can no longer be purchased from a public CA. The Subject Name of the SSL certificate matches the ExternalURL configured on the OWA virtual directories and is the DNS name assigned to the Virtual IP (VIP) on the Hardware Load Balancer (HLB).
If you only have a single Exchange Server and are not using HLB then simply use the FQDN of the Exchange Server in the following steps. You will need a certificate that contains the FQDN in the subject name field, so this will likely have to come from an internal CA. If this is the case then the issuing CA certs will have to be trusted by both the Exchange and Lync servers.
If you only have a single Exchange Server and are not using HLB then simply use the FQDN of the Exchange Server in the following steps. You will need a certificate that contains the FQDN in the subject name field, so this will likely have to come from an internal CA. If this is the case then the issuing CA certs will have to be trusted by both the Exchange and Lync servers.
Goal
Exchange 2013 client access server integrated with Lync 2013.
