Lync 2010 Integration with Outlook Web App 2010 (OWA 2010)
Email and instant messaging (IM) are both forms of communication that are frequently used in businesses around the world. As workers are becoming more mobile, IT departments are challenged with providing more ways for the mobile workforce to communicate. Now you can integrate Lync 2010 with Exchange 2010 using Outlook Web Access 2010 (OWA 2010), providing users with the ability to see each other’s presence and have Lync IM sessions. This added feature can be a real benefit to the mobile workforce as they can start Lync IM sessions with any device that has a supported browser for OWA 2010 and Internet connection.
Lync 2010 with OWA 2010: Features
The Lync integration with OWA 2010 provides some basic Lync functions and does have limitations on what capabilities are available to use while logged into OWA 2010. Browsers that only support OWA Light version will not have the Lync features available. So for those thinking they can use this to Lync chat on their iPhones – sorry, it won’t work, but there is a Lync iOS app that provides the same capabilities.
The following features are available using Lync 2010 though OWA 2010:
- Sign in/out of Lync through OWA 2010
- Presence – the users presence is displayed for all Lync users to see
- Contacts – Users Lync contact list is available, contacts can removed or added through the integrated OWA 2010
- Instant Messaging – Users can have IM sessions with other Lync users without the need to install the Lync client
The following Lync 2010 features are NOT available through OWA 2010:
- Group Chat
- Voice Calls
- Video Calls
- Desktop or Application Sharing
- Font and text formatting
Configure Exchange 2010 and Lync 2010 Integration
To get started with Lync using OWA 2010 you’ll need to make several changes on your Exchange 2010 Client Access servers (CAS) and the Lync 2010 servers. If you have an array of Exchange 2010 CAS servers you will need to make the modifications across all the servers. You will also need a certificate that is trusted by both the Lync and Exchange servers that contains the CAS namespace on the subject line. Typically you can use the same certificate that you are currently using for your existing OWA 2010 site.
Complete the following changes on the Exchange 2010 CAS Servers:
- On each of your CAS server running Windows Server 2008 or higher, download the following file: Unified Communications Managed API v. 2.0 (UCMA). (Must be version 6907.210. or later.)
- Install the file on the CAS server and reboot the server.
- Download and extract the CWAOWASSPMain.msi from the Microsoft Office Communications Server 2007 R2 Web Service Provider.
- Once the files are extracted you will need to install the CWAOWASSP.msp. file.
- Download and install the Hotfix update for CWAOWASSP.
- To verify the installation was done successfully you can check following areas:
- 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
- Look for Microsoft.Rtc.UCWeb.dll file in the directory <installation drive>\Program Files\Microsoft\Exchange Server\V14\ClientAccess\Owa\Bin
- Look for the SIPEPS.dll and Microsoft.Rtc.Collaboration.dll files in the Microsoft .NET Framework Global Assembly Cache
- Use the Exchange Management Shell to verify your certificate’s thumbprint and set the Lync pool to the OWA Virtual Directory.
- Verify your Certificate information by typing the cmdlet, take note of the name and thumbprint of the certificate. You will need this in the next step: Get-ExchangeCertificate | fl
- Next you will configure the OWA Virtual Directory to allow the Lync pool to connect and use the certificate for Lync Instant messaging.
Get-OwaVirtualDirectory | Set-OwaVirtualDirectory -InstantMessagingServerName <name of Lync Server or pool to connect to> -InstantMessagingCertificateThumbprint <certificate thumbprint> -InstantMessagingEnabled $true -InstantMessagingType 1
- Open a Command Prompt window and restart IIS using the iisreset/noforce command.
Complete the following changes on the Lync Server:
You will need to create an Outlook Web App pool entry on the Lync Server 2010 server. Using the Lync Server Management Shell complete following steps.
- Use the following cmdlet to get the Site ID of where you are creating your new Outlook Web App pool. Take note of the Site ID:
- To create the new trusted application pool use the below cmdlet:
New-CsTrustedApplicationPool -Identity <OwaPoolfqdn same as what is used in SN of cert> -Registrar <OCS Pool Fqdn> -Site <siteId> -RequiresReplication $false
- You will now add the Exchange CAS servers to the new Lync Trusted Application Pool using the Lync Management Shell
New-CsTrustedApplication -ApplicationId <ApplicationIDForOWA> -TrustedApplicationPoolFqdn < OwaPoolfqdn same as what is used in SN of cert> -Port <some available port>
- Next enable the topology by running the following:
- Login to OWA 2010 to now see the enabled Lync features
Once you’ve configured the integration between Lync 2010 and OWA 2010, the users who are already enabled for Lync will start seeing the new enabled feature the next time they login to OWA 2010. Providing these extra features to users gives them different forms of communication to utilize while on the go. Lync integrated with OWA 2010 has its limitations but it does provide basic IM functions for users.
More in Exchange Server
Microsoft Exchange Servers Hit By Stealthy IIS Backdoors
Jul 27, 2022 | Rabia Noureen
Kaspersky Discloses New 'SessionManager' Backdoor Targetting Microsoft Exchange Servers
Jul 1, 2022 | Rabia Noureen
M365 Changelog: (Updated) Safe Links Global Settings Migrated to Custom Policies
Jun 28, 2022 | Petri Staff
Microsoft Postpones the Release of Next Version of Exchange Server Until 2025
Jun 3, 2022 | Rabia Noureen
M365 Changelog: Get-AdvancedThreatProtectionDocumentReport and Get-AdvancedThreatProtectionDocumentDetail to be retired
May 24, 2022 | Petri Staff
M365 Changelog: (Updated) Microsoft Defender for Office 365: Updates to URL Protection Report
May 24, 2022 | Petri Staff
Most popular on petri