With Lync and Exchange 2010 or 2013, you can configure both platforms so that users can use the Exchange Outlook Web App for Instant Messaging and presence.
The first thing you need to check to make sure that you can do the integration is whether Unified Communications Managed API 4.0 Runtime is installed on your mailbox servers. To verify this, log in to your mailbox servers and look for the following registry key:
HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesMSExchange OWAInstantMessagingImplementationDLLPath
This key should point to the folder location of the Microsoft.Rtc.Internal.Ucweb.dll file. If the key does not exist or does not point to this folder, you should install the application on all of your mailbox servers.
You can also check the installed programs via the control panel of your mailbox servers.
Refer to http://www.microsoft.com/en-us/download/details.aspx?id=34992 to download and install the Unified Communications Managed API (UCMA).
To configure the Lync 2013 and Exchange 2013 OWA integration, you need to follow several steps in the same order as described in the following sections.
The next step is to create a trusted application pool on Lync for the Outlook Web App.
Note
If you already have Unified Messaging integration between Lync and Exchange and if your Exchange 2013 servers have both the Client Access and the Mailbox roles, you do not need to create the trusted application pool on Lync. Creating a trusted application pool in this scenario will break the Instant Messaging and presence integration with OWA.
To create the trusted application pool, run the following cmdlet:
New-CsTrustedApplicationPool -Identity <ExchangeServerFQDN> -Registrar lyncpool.domain.com -Site SiteName -RequiresReplication $False
The identity of the trusted application pool should be the FQDN of the Exchange Client Access server or the name that is being load balanced to reach the Client Access server (that is, owa.domain.com).
If you want to get the SiteName, run the following cmdlet:
Get-CsSite |ft displayname, siteID
The register value should be the FQDN of the Lync pool.
Once the trusted application pool is created, you need to create the trusted application by running the following Lync Management Shell cmdlet:
New-CsTrustedApplication -ApplicationId OutlookWebApp -TrustedApplicationPoolFqdn <ExchangeServerFQDN> -Port 5199
Once both are created, enable the Lync topology by running this command:
Enable-CsTopology
There are three things you need to do on Exchange to complete the Instant Messaging integration with OWA:
- Configure the OWA virtual directories for Instant Messaging.
- Edit the
web.configfile on the Client Access servers. - Configure the OWA mailbox policy to allow Instant Messaging on OWA.
You need to enable on one or more OWA virtual directories on your Exchange Client Access servers for Instant Messaging integration. If there are some Client Access servers used by some users within your organization and you don't wish these client access servers to provide the IM on the OWA functionality, then you should just enable the properties on the other servers.
To get a list of all the OWA virtual directories and the Instant Messaging current configurations, run the following Exchange Management Shell cmdlet:
Get-OwaVirtualdirectory |ft identity, instantmessagingenabled, instantmessagingtype
To enable Instant Messaging on a specific virtual directory of a specific server, run the following cmdlet:
Set-OwaVirtualDirectory –identity <OwaVDirIdentity> -instantmessagingenabled $true –instantmessagingtype OCS
To enable Instant Messaging on all of your Client Access servers, run the following cmdlet:
Get-OwaVirtualDirectory | Set-OwaVirtualDirectory -instantmessagingenabled $true –instantmessagingtype OCS
To edit the web.config file, proceed with the following steps:
- On each of your Client Access servers, edit the
web.configfile present atC:Program FilesMicrosoftExchange ServerV15ClientAccessOwa(depends on the Exchange installation path). - Before editing the file, you need to know the thumbprint of the certificate that your Client Access server uses. To get this information on the Client Access server Exchange Management Shell, run the following cmdlet:
Get-ExchangeCertificate | Fl - Make sure that you write down the certificate thumbprint. The certificate used must have the FQDN of the server on the subject name and as an alternative name.
- After getting this information, you need to open the
web.configfile and edit the following section:<add key="IMCertificateThumbprint" value="<Certificate Thumbprint>"/> <add key="IMServerName" value="lyncpool.domain.com"/>
The explaination for the preceding command can be explained as follows:
- In
IMCertificateThumbprint, you should copy and paste the thumbprint you obtained previously - In
IMServerName, you should enter the FQDN of the Lync Server pool
- In
- Finally, you need to recycle the application pool on the Client Access server by running the following cmdlet:
C:WindowsSystem32InetsrvAppcmd.exe recycle apppool /apppool.name:"MSExchangeOWAAppPool"
Each user has an Outlook Web App mailbox policy assigned, and by default, the OWA mailbox policy will not allow Instant Messaging on OWA. You can either configure the default policy to allow all users to have this feature enabled, or you can create new policies and assign them to the relevant users.
To modify the default mailbox policy to allow Instant Messaging on OWA, run the following Exchange Management Shell cmdlet:
Set-OwaMailboxPolicy -Identity "Default" -InstantMessagingEnabled $True -InstantMessagingType "OCS"
To configure all of your existing mailbox policies to allow Instant Messaging on OWA, run the following Exchange Management Shell cmdlet:
Get-OwaMailboxPolicy | Set-OwaMailboxPolicy -InstantMessagingEnabled $True -InstantMessagingType "OCS"
To get a list of all your mailbox users that have a specific mailbox policy, run the following cmdlet:
Get-CASMailbox |where-object {$_.OwaMailboxPolicy -eq "Default Policy"}