Enable Disable Integration Lync in Outlook Web App 2013


Enabling Instant Messaging on Outlook Web App

With Lync Server correctly configured you can then begin to configure Outlook Web App. The first step in that process is to enable instant messaging on all your Outlook Web App virtual directories on your front end servers. (There is no need to enable instant messaging for the virtual directories on your backend servers. In fact, it is recommended that you do not enable instant messaging on your backend servers.) Instant messaging can be enabled on the client access servers by running the following command from within the Exchange Management Shell:

Get-OwaVirtualDirectory | Set-OwaVirtualDirectory 
-InstantMessagingEnabled $True -InstantMessagingType OCS
By default, instant messaging is enabled when you install Outlook Web App; that is, the InstantMessagingEnabled property is set to True. However, you must still run the preceding command in order to set the instant messaging type to OCS. By default, InstantMessagingType is set to None.

Next you must add the following two lines to Outlook Web App Web.config file (this file is typically located in the folder C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\Owa). These two lines should be added under the <AppSettings> node in the Web.config file, and this procedure should be carried out only on the backend servers where Outlook Web App has been installed:

<add key="IMCertificateThumbprint" 
<add key="IMServerName" value="atl-cs-001.litwareinc.com"/>

In the preceding example, the value for IMCertificateThumbprint must be the thumbprint for the Exchange 2013 certificate that is installed on your backend servers. You can retrieve that information by running the following command from the Exchange Management Shell:


Note, too that the value assigned to IMServerName is the fully qualified domain name of the Lync Server pool where you created the trusted application pool for Outlook Web App.

The certificate that you use for Outlook Web App must be a certificate that is trusted by Lync Server. One way to ensure that the certificate will be trusted by both Lync Server and Exchange is to use your internal certificate authority to create a certificate on the mailbox server, making sure that the server FQDN is used for the subject name and that this FQDN appears in the certificate alternate name field. After the certificate has been created it can then be imported to your backend servers. The net result is that the same certificate is used for two purposes: 1) communication between Exchange unified messaging and Lync Server; and, 2) the integration between Outlook Web App and Lync Server.

After you have updated the Web.config file you should then run the following command on the Exchange backend server in order to recycle the Outlook Web App pool:

C:\Windows\System32\Inetsrv\Appcmd.exe recycle 
apppool /apppool.name:"MSExchangeOWAAppPool"

If the recycle operation succeeds you will see the following message in the Exchange Management Shell:

"MSExchangeOWAAppPool" successfully recycled

Configuring Outlook Web App Mailbox Policies

At this point you can use the following command to configure instant messaging on the appropriate Outlook Web App mailbox policy (or policies). For example, this command, run on one of your mailbox servers, enables instant messaging on the Default policy:

Set-OwaMailboxPolicy -Identity "Default" -InstantMessagingEnabled 
$True -InstantMessagingType "OCS"

And this command enables instant messaging for all your Outlook Web App mailbox policies:

Get-OwaMailboxPolicy | Set-OwaMailboxPolicy -InstantMessagingEnabled 
$True -InstantMessagingType "OCS"

After the mailbox policy has been enabled then all users managed by that policy will have full integration between Lync Server and Outlook Web App, provided that:

  • The user has a mailbox on Exchange 2013.
  • The user has been enabled for Lync Server 2013.
  • The user has a valid SIP proxy address.

Disabling Instant Messaging in Outlook Web App

As noted previously, instant messaging is enabled by default in Outlook Web App. That means that, if you do not integrate Outlook Web App with Lync Server, users will see blank presence icons and an error message each time they log on to Outlook Web App. To prevent this problem, use the following Exchange Management Shell command to disable instant messaging in Outlook web App:

 Get-OwaVirtualDirectory | Set-OwaVirtualDirectory -InstantMessagingEnabled $False

One Response to “Enable Disable Integration Lync in Outlook Web App 2013”

  1. 1 Liu Chan

    Binfer instant messaging is secure and encrypted. You can send unlimited messages at no cost. The link is http://www.binfer.com

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: