#Ms lync 2013 no certificate windows#
This really should state that a ‘trusted certificate’ is required, as a private certificate issued by an internal Enterprise Windows CA can be used and will work fine if both the Lync and Exchange servers are members of the same domain. Note that the statement “you must use a public certificate if you are using Unified Messaging with Office Communications Server” is not entirely correct. This step is a common Exchange deployment task and official instructions can be found here. Pay special attention to the Microsoft Speech Platform, UC Managed API 2.0, and UM Language Pack installations.
#Ms lync 2013 no certificate install#
Prior to deploying the Exchange Server make sure to install all of the prerequisite software for the UM role as documented in this checklist. No previous instance of Exchange had been installed so the deployment included creating a new Exchange Organization. The host used in this lab is a separate, dedicated virtual guest running Windows Server 2008 R2 with 2GB of RAM assigned to it. The best place to start would be the official Microsoft documentation. The deployment of Exchange Server 2010 SP1 is outside the scope of this article but there are many official and unofficial walkthroughs available online to help anyone unfamiliar with the Exchange Server deployment process. These steps begin right where article 3 left off so if you are following along make sure to configure the Enterprise Voice setting in Lync Server as detailed in that article.
Configure UM Dial Plan, Policy, and Auto Attendant settings.Create a new SIP Dial Plan in Exchange.Replace the self-signed certificate with one from an internal Windows Enterprise Certificate Authority and reassign all Exchange roles to it.Deploy Exchange Server 2010 SP1 in same forest as a consolidated server with Unified Messaging role included.The following steps completed in this order in a greenfield deployment should yield a working UM environment in little time. A single consolidated Exchange 2010 SP1 server was also added with all roles (CAS, Hub, Mailbox, UM). The lab environment used as examples was built using the same processes discussed in these three previous articles for Lync Server. Also note these instructions were tested various times with both RC and RTM installations of Lync Server. Although the process is basically the same as it was in Exchange 2007 and OCS 2007 R2 there are a few important changes. Thank you! Lync-Edge-Server.png Lync-Front-End-Server.This article covers the Unified Messaging (UM) integration configuration between Lync Server 2010 Release Candidate and Exchange Server 2010 SP1. (specifically, Holger's 2nd reply)Īny help is greatly appreciated.
The following articles have helped me understand this much, but I need more guidance due to my lack of knowledge of Lync servers. I've attached pictures of the current state of the certificates on both servers.
The client currently has 2 servers, an outside edge server and a front end server. My question is, what do we have to do to configure the internal CA certificate in a way that will allow us to remove the internal server name from the public cert and have Lync still accept the new public cert? We do currently have an internal CA and already have a certificate from that CA assigned to the Lync internal web services. I've found articles on blogs (I'll add the links below) that say that having an internal enterprise CA will allow us to set everything up without doing either of the things mentioned above as the internal certificate can have the internal server name. I'd prefer to avoid renaming domains or creating a split-dns zone. Since this is no longer allowed, I've been looking for the easiest way to get around this. The public certificate is expiring soon (like in 4 days) and the current public certificate has the internal server name as one of the SANs. I'm running in to an issue with a new client that has Lync 2013. I've searched EE and have found related articles but none answering the question I have.