![exchange skype for business integration port exchange skype for business integration port](https://www.moh10ly.com/wp-content/uploads/2020/06/clip_image0019_thumb.png)
- #Exchange skype for business integration port how to#
- #Exchange skype for business integration port install#
- #Exchange skype for business integration port update#
- #Exchange skype for business integration port Patch#
Get-OwaMailboxPolicy | Set-OwaMailboxPolicy -InstantMessagingEnabled $true –InstantMessagingType OCS Get-OwaVirtualDirectory | Set-OwaVirtualDirectory -InstantMessagingEnabled $true -InstantMessagingType OCS -InstantMessagingCertificateThumbprint 5FB91CB7AB7677EF45B5C809CF8CB9CFDB31D0A1 –InstantMessagingServerName So we’ve removed the -ShowBackendVirtualDirectories switch. Thanks to Varol for pointing out that Microsoft tells us that IM is “NOT” enabled on the BACK END servers. When we enable Lync IM for Exchange, we only want to target the FRONT END servers. Make sure you have a valid local certificate that’s trusted & everything should work OK.
#Exchange skype for business integration port update#
Update– I’ve implemented the FREE Kemp virtual LoadMaster for my Lync 20 update and Exchange 2013 CU9 servers, but it doesn’t change the process that much. Now that we have the thumbprint, and we know our Lync pool FQDN, let’s plug it in. Issuer : CN=cloud-CIRRUS-CA, DC=cloud, DC=local Subject : CN=, OU=Connect UC, O=IT, L=Minneapolis, S=MN, C=US PS C:\Users\administrator.COMPANY> Get-Cspool | where-object | fl subject, issuer, services, thumbprint Get-clientaccessserver | fl fqdn, autodiscoverserviceinternaluriĪlso lets take on the Lync side and get the pool FQDN: An internal CA is fine (we’re using this in our test environment), third party is even better, but the self-signed will not be able to communicate because it’s missing the necessary subject names.įirst let’s get the autodiscover service URI:
#Exchange skype for business integration port install#
As part of the installation of Lync 2013 you had to install SSL certificates to start the services, however for Exchange you’ll want to make sure you’re not using the self-signed certificates. This will be any admin’s friend in pushing out set groups of contacts ?įirst, the foundation of communication between Exchange and Lync 2013 is based on the new Office Web App “OAuth” calls for server-to-server communication. This means that you don’t have to maintain a separate set of contact from Exchange, which was somewhat frustrating and cumbersome. That was half the battle in 2010, because if you didn’t have the correct version of the patches, or didn’t install them in the right order, things would fail.Īlong with OWA integration, Lync now supports a Unified Contact Store (UCS), which was somewhat hinted to in 2010 but didn’t come to fruition until 2013.
#Exchange skype for business integration port how to#
I had previously written an article on how to integrate Exchange/Lync 2010 for IM capability via OWA, and now that Exchange/Lync 2013 have been released, Microsoft has maintained the compatibility but thankfully with an easier-to-achieve process.īecause of the Unified Communications Managed API (UCMA) 4.0 requirement on Exchange 2013 for the integrated UM role, both platforms have a similar set of prerequisite requirement. With some troubleshooting I have it working, and you’ll find updates scattered throughout this article.
![exchange skype for business integration port exchange skype for business integration port](http://www.telesail.com/uploadfile/solution/TPB5096%20IP%20PBX%20enterprise%20phone%20solution.png)