Banner

How to Modify OWA 2013 to Support Microsoft Lync

By Brian Posey, SearchExchange.TechTarget.com

If you plan on using Lync 2013 and Exchange 2013 with unified messaging on your network, consider modifying OWA 2013 to support Lync. It adds instant messaging capabilities to OWA, as well as presence information to the OWA interface. This tip explains the initial steps necessary to make those capabilities work.

Before getting started, it's important to understand that the procedure requires that the Unified Communications Managed API 4.0 Runtime be installed on your back-end Exchange servers. If you don't already have it set up, you can download the API from Microsoft.

Create a trusted application pool

The instructions in this tip assume that you've deployed unified messaging (UM) in your Exchange Server organization. That said, the way you've deployed the UM components will have an effect on the procedure you'll use to integrate Outlook Web App 2013 with Lync.

Typically, organizations that have already deployed UM run the Microsoft Exchange Unified Messaging Service and the Microsoft Exchange Unified Messaging Call Router Service on the same server. If your UM deployment is set up thusly, you needn't create an application pool. In fact, doing so will break OWA. Therefore, if your UM components are installed on a common server, ignore the instructions in this section and skip to the next section.

If you've deployed the Microsoft Exchange Unified Messaging Service and Microsoft Exchange Unified Messaging Call Router Service on different servers, the first thing to do is create a Lync Server trusted application pool that defines OWA 2013 as a trusted application. To do so, open the Lync Server Management Shell and enter the following command:

New-CsTrustedApplicationPool -Identity <the FQDN of your OWA deployment> -Registrar <the FQDN of your OWA deployment> -Site <the SiteID defined by Lync Server> -RequiresReplication $False

There are two important things you must know about this command. First, the FQDN of your OWA deployment must match the FQDN specified in your SSL certificate's Subject Name or Subject Alternative Name field. Second, the site name isn't necessarily the name you're used to seeing within Lync. To determine the site name, run the following command:

Get-CsSite | Select-Object SiteID

 

To read the full article, go to: SearchExchange

Use Ctrl+Shift+R to “Reply all” to the selected message.
 

Poll

Will tablet and Smart phone use be a big part of your OWA 2013 deployment?