Here I noticed that the certificate was a self signed certificate and didn’t contain any SANs for the other exchange server therefore the Lync Server would not trust this so was probably my issue.
Next opened MMC on the Exchange Server and checked the Certificate for the common name and Subject Alternative Names. Next i went to Exchange servers and from Exchange Management Shell checked the certificate thumbprint that was referenced in the web.config file. Under you should have the IMServerName and Certificate thumbprint to be used so i checked this out. %Exchange install drive%MicrosoftExchange ServerV15ClientAccessOwa With Exchange 2013 OWA there is a web.config file on the Exchange Server used to define the Lync Pool Name and Certificate in the following directory The net result is that the same certificate is used for two purposes:ġ) communication between Exchange unified messaging and Skype for Business Server and,Ģ) the integration between Outlook Web App and Skype for Business Server. After the certificate has been created it can then be imported to your backend servers. One way to ensure that the certificate will be trusted by both Skype for Business Server and Exchange is to use your internal certificate authority to create a certificate on the mailbox server, making sure that the server FQDN is used for the subject name and that this FQDN appears in the certificate alternate name field. The certificate that you use for Outlook Web App must be a certificate that is trusted by Skype for Business Server. The Certificate assigned for use with OWA and SfB must follow there guidelines as defined on TechNet This relates to a Certificate issue either the Skype for Business server doesn’t trust the Certificate used for OWA or the Certificate doesn’t contain the SANs of the FQDN of the Exchange Servers.Īs i was using UM i already had an internal certificate will all SANs but the certificate thumbprint was incorrect in the web.config file on the exchange servers. It referenced TLS so i immediately thought certificates would be the next place to check. UCWAuthenticatedEndpoint, MethodName: InstantMessageOCSProvider.SignInCallback, InstantMessageServiceError: SipEndpointConnectionFailure, Exception: UCWEB Failure: Code=TlsFailure, SubCode=TlsRemoteDisconnected, I had multiple Exchange 2013 servers so i had to check all on the servers log files for references to the sign and i found a lot of these %Exchange install drive%MicrosoftExchange serverV15LoggingOWAInstantMessaging I checked the logging file location on the Exchange Server for OWA Instant Messaging in the following directory Had an issue recently where OWA integration with Exchange 2013 and Skype for Business was not working and users were failing to sign into IM when using OWA.
0 kommentar(er)
