Lync Server integration with Exchange Outlook Web Access.
Recently I have deployed Lync integration with Exchange Outlook Web Access. Whenever you accessing Outlook web access you will be able to chat you’re your buddy without Lync application. This is the main feature which is enable after above integration.
Feature: Instance Messaging enable on Outlook Web Access.
You must have:
- Microsoft Exchange Server 2010 in your organization.
- Lync Server 2010.
- Obtained a certificate that's trusted by the Lync Server 2010 server and the Client Access server and is issued by the same authority. The certificate must have the Client Access server namespace as the subject on the Subject line. The namespace may be the name of a particular Client Access server, or it may be a DNS name that's used for load balancing across multiple Client Access servers.
- Recorded the fully qualified domain name (FQDN) of the Lync Server 2010 server or the Lync Server 2010 pool that the Client Access server will connect to. The server or pool should be geographically close to the Client Access server.
- Enabled your users to use Lync Server 2010 via the Lync Server 2010 user administration tools.
1. On the Client Access server running Windows Server 2008 or a later version, download and install UCMA 2.0 from Unified Communications Managed API 2.0, Core Runtime (64-bit). It will update the UC managed API
2. On the Client Access server, download and extract the CWAOWASSPMain.msi file from Microsoft Office Communications Server 2010 R2 Web Service Provider. Version: 3.5.69.07.244. The following files are extracted to the Web Service Provider installer package location:
This will required IM and Presence feature in OWA.
Download the package and install: http://www.microsoft.com/downloads/en/details.aspx?familyid=CA107AB1-63C8-4C6A-816D-17961393D2B8&displaylang=en
3. Double-click CWAOWASSP.msi to install the Microsoft Office Lync Server 2010 R2 Web Service Provider.
4. Download and install the hotfix from OCS 2007 R2 Web Service Provider Hotfix.
Cross verify the following things before doing next steps-
- Look for the InstantMessaging key
in the registry under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchange
OWA\. The string under InstantMessaging with the name ImplementationDLLPath and
the value "
\ClientAccess\owa\bin\Microsoft.Rtc.UCWeb.dll" should have been created.
- The Microsoft.Rtc.UCWeb.dll file should be present in the directory <installation drive>\Program Files\Microsoft\Exchange Server\V14\ClientAccess\Owa\Bin.
- The files SIPEPS.dll and Microsoft.Rtc.Collaboration.dll should be present in the Microsoft .NET Framework Global Assembly Cache.
5. Verify the Certificate:
a. Open Exchange management power shell.
get-ExchangeCertificate | fl Services,Thumbprint
b. Locate the certificate you want to use, and then record its thumbprint and subject.
6. Use the Management Shell to set the Lync Server 2010 Server used by the Client Access Server and to enable integration.
Note: certificate to be used, and enables the Client Access server to use trusted Lync Server 2010 for instant messaging.
Get-OwaVirtualDirectory | Set-OwaVirtualDirectory -InstantMessagingServerName
-InstantMessagingCertificateThumbprint -InstantMessagingEnabled $true -InstantMessagingType 1
You can restart the IIS service; open the Command Prompt window and using the iisreset/noforce command to reflect the changes.
You have to create Outlook Web App pool entry on the Lync Server 2010 server.
a. Run the Get-CsSite cmdlet to get the siteID for the siteName in which you are creating the pool.
b. Run the New-CsTrustedApplicationPool cmdlet to create the trusted application pool. This also creates the external service entry in Lync Server 2010.
-Registrar -Site -RequiresReplication $false
Run the New-CsTrustedApplication cmdlet to add a trusted service port for the application.
-TrustedApplicationPoolFqdn < OwaPoolfqdn same as what is used in SN of cert> -Port
Run the Enable-CsTopology cmdlet in the Shell to enable the topology.