Lync 2013 + Exchange Owa 2013 Integration

 

In this Bolg we will see how to integrate Lync 2013 with Exchange OWA 2013.

Before proceeding to the integration first we have to check if auto discover URL and the Service is Published at the Exchange end.

Open Exchange Management shell

And type

Get-ClientAccessServer | Select-Object Name, AutoDiscoverServiceInternalUri | Format-List or with the following command Get-ClientAccessServer | fl fqdn, AutodiscoverServiceInternalURI

Under Auto Discover URL you should see https://autodiscover.contoso.com/autodiscover/autodiscover.xml.

If the URL is Blank you can set the URL by this command

Get-ClientAccessServer | Set-ClientAccessServer -AutoDiscoverServiceInternalUri https://autodiscover.contoso.com/autodiscover/autodiscover.xml

Now we have to set the Autodiscover Service

The Autodiscover service does the following:

Automatically configures user profile settings for clients running Microsoft Office Outlook 2007, Outlook 2010, or Outlook 2013, as well as supported mobile phones. Phones running Windows Mobile 6.1 or a later version are supported. If your phone isn't a Windows Mobile phone, check your mobile phone documentation to see if it's supported.

Provides access to Exchange features for Outlook 2007, Outlook 2010, or Outlook 2013 clients that are connected to your Exchange messaging environment.

Uses a user's email address and password to provide profile settings to Outlook 2007, Outlook 2010, or Outlook 2013 clients and supported mobile phones. If the Outlook client is joined to a domain, the user's domain account is used.

Set-CsOAuthConfiguration -Identity global -ExchangeAutodiscoverUrl https://autodiscover.contoso.com/autodiscover/autodiscover.svc

Now we have to identify the certificate that has been assigned in IIS

Here is the command to get the certificate Thumprint Information

Get-ExchangeCertificate|fl Services,Thumbprint

Copy the certificate Thumbprint in the later stage we will be using this certificate Thumprint. 5EA8831E757FBB86808B95B69F81D01A2FC2F55A

To get the owa virtual directory . to make sure you have only single owa virtual directory configured in your environment

Get-OWAVirtualDirectory

Use the below command to assign the pool name of lync server and the certificate thumbprint to OWA virtual directory. Now this enables IM capabilities for you exchange environment.

Get-OwaVirtualDirectory | Set-OwaVirtualDirectory -InstantMessagingType OCS -InstantMessagingEnabled:$true –InstantMessagingCertificateThumbprint 5EA8831E757FBB86808B95B69F81D01A2FC2F55A -InstantMessagingServerName pool.contoso.com

Next we must add the following two lines to Outlook Web App Web.config which will be available in this path C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\Owa

In this path you see an file web.config file open the file in notepad. under <AppSettings> add the below two lines

<add key="IMCertificateThumbprint" value="5EA8831E757FBB86808B95B69F81D01A2FC2F55A "/>

<add key="IMServerName" value="pool.contoso.com"/>

Now try to perform IIS reset in the Command prompt

Iisreset

At the Lync server End Configuration

Now login to your lync front end and open the Lync Management shell

To get he SITE ID of lync enter the Below Command we will be using Lync Site id while configuring the Exchange trusted Application.

Get-CsSite

We have to create the Trusted Application pool for Excahnge OWA to create the one use the following command

New-CsTrustedApplicationPool -Identity <Certificate Subject name of client access server> -Registrar <Pool FQDN of Lync server> -Site <Lync Site Name> -RequiresReplication $False

After creating the trusted application pool, use the following command to configure an application Identity and a port for Outlook Web App

Before executing the below command check if the port is not using any other application. You can use any port but make sure to check the port is available

netstat -a | findstr 5199

New-CsTrustedApplication -ApplicationId OutlookWebAccess -TrustedApplicationPoolFqdn < Certificate Subject name of client access server> -Port 5199

Now use this command to apply the configuration changes Enable-CsTopology. This command but publishing the Lync Topology.

Enable-CsTopology.

Now it’s testing time. Try logging to OWA and click on sing to IM in OWA web page

Successfully logged in to IM using OWA

Now we will be able to IM with Lync users form OWA itself.

Trouble shooting Lync OWA Integration.

1) Make sure that our OWA Virtual Directory enabled for Instant Messaging

Get-OwaVirtualDirectory -Server <Excahnge server> | Set-OwaVirtualDirectory -InstantMessagingEnable $True -InstantMessagingType OCS

2) Make sure that in the OWA Web config file you have added these lines

<add key="IMCertificateThumbprint" value="5EA8831E757FBB86808B95B69F81D01A2FC2F55A <Your Certificate Thumbprint> "/>

<add key="IMServerName" value="pool.contosot.com"/>

3) To start the trace and to get the Log file

On the exchange server you can use OcsTracer.exe in the following path C:\Program Files\Microsoft UCMA 4.0\Runtime\Tracing

To start the trace use the command prompt and go the path enter below command

OCSTracer.exe Start /Component:Collaboration,TL_noise,tf_component,tf_diag,tf_protocol,tf_connection /Component:S4,TL_VERBOSE,tf_component,tf_protocol /LogFileMode:NewFile,20

To Stop Logging

OCSTracer Stop /Component:Collaboration /component:s4 /OutputFile:traces.txt /View

It will open the Notepad file so that you check the logs.