Just requesting the certificate is not enough in Exchange Server 2013, and after deploying the Public Certificate, the Exchange Server was configured to use the following address on either internal or external URLs. The Skype for Business Server 2015 is using the internal PKI for all certificates, and based on the best practices of the product, only the Edge Server and Reverse Proxy roles will require Public Certificates.Īdditional certificates will be required for the integration, and we will cover that in the upcoming articles of this series. For a simple environment, only using the first two entries will be enough from the Exchange perspective. The adfs and smtp entries were not required as they were added to the existent certificate and will be used for Active Directory Federation Services and Secure SMTP communications. The names that are in use in the Exchange Certificate are listed below: The Exchange Organization has a single domain name which is patricio.ca and that is the Primary SIP domain in Skype for Business Server topology. In order to avoid headaches, a valid certificate from Public Certification Authority is in use by Exchange Server 2013 (TOREX01), and the type of certificate is the UC/SAN, which accepts multiple names on the same certificate. Nowadays the vast majority of communication is done through certificates. The certificates play a key role in the integration and are required to establish the proper security with the clients. The current scenario (Figure 02) has a single Exchange Server 2013 (TOREX01) and a single Skype for Business Server 2015 (TORSB01), and two domain controllers (TORDC01 and TORDC02), and a server holding the PKI infrastructure (TORCA01).Īll servers and users are on the same forest (that is important when integrating Exchange and Skype for Business, because when we have more than one forest, some additional steps may be required for some tasks). If you already have an environment with both products, then you can take advantage and start applying the integration right away, if you are waiting to deploy Skype for Business Server 2015 then you can start familiarizing yourself with the integration that will be required after the initial deployment.
#PHONE INTEGRATION SKYPE FOR BUSINESS SERIES#
The current scenario…Ī new series covering the Skype for Business Server 2015 deployment process will be available here at for those that want to check all the steps performed to get to this point. The integration between Skype for Business on-premises and Office365 are going to be covered in a future article here at. The word integration nowadays can be deceiving because we can have integration between different products like Exchange/Skype for Business/SharePoint and within the same product when using Office365. The series is organized in seven (7) articles and each of them will cover one area of the integration (Figure 01). In this initial article of our series, we describe in some detail the scenario that was used to build this series, and by doing that the reader can compare the settings that we have in production with their own environment. However, the decision was to create two separate series: Skype for Business Server 2015 deployment and the current series that we are starting now which will cover only the integration between Exchange and Skype for Business Server. The original idea for this series was to cover the entire deployment and integration process in a single series, including initial planning, deployment, integration and so forth.
0 kommentar(er)
