Configure instant messaging integration with Outlook on the web in Exchange 2016

Exchange 2016
 

Applies to: Exchange Server 2016

Topic Last Modified: 2018-01-05

Summary: Learn how to configure IM integration with Outlook on the web in Exchange 2016.

To configure instant messaging (IM) integration between Skype for Business Server and Outlook on the web in Exchange 2016, you need to use the Exchange Management Shell. This is different than previous versions of Exchange where you needed to edit the web.config file. If you edit the web.config file instead of using the steps in this topic, the settings are ignored and Outlook on the web users receive the following error message:

There's a problem with instant messaging. Please try again later.

Also, the following health set errors are generated on the Exchange server:

  • HealthSet   OWA.Protocol.Dep

  • Subject   OWA.Protocol.Dep health set unhealthy (OwaIMinitializationFialiedMonitor/OWA.Protocol.Dep) - Owa InstantMessaging provider failed to intialize

  • Message   Owa InstantMessaging provider failed to initialize due to incorrect IM configuration on the server. Signin attempts to OWA IM will fail. Error Message: {Instant Messaging Certificate Thumbprint is null or empty on web.config).

Use the procedures in this topic to fix these errors and configure IM integration between Skype for Business Server and Exchange 2016. IM integration between Lync Server 2013 and Exchange 2016 isn't supported.

  • Estimated time to complete: 5 minutes

  • Exchange and Skype for Business integration requires server certificates that are trusted by all of the servers involved. The procedures in this topic assume that you already have the required certificates. For more information, see Plan to integrate Skype for Business Server 2015 and Exchange.

  • You can only use PowerShell to perform this procedure. To learn how to open the Exchange Management Shell in your on-premises Exchange organization, see Open the Exchange Management Shell.

  • You need to be assigned permissions before you can perform this procedure or procedures. To see what permissions you need, see the "Client Access virtual directory settings" entry in the Clients and mobile devices permissions topic.

  • For information about keyboard shortcuts that may apply to the procedures in this topic, see Keyboard shortcuts in the Exchange admin center.

tipTip:
Having problems? Ask for help in the Exchange forums. Visit the forums at: Exchange Server, Exchange Online, or Exchange Online Protection.

Use the following syntax in the Exchange Management Shell to specify the IM server and IM certificate thumbprint:

New-SettingOverride -Name "<UniqueOverrideName>" -Component OwaServer -Section IMSettings -Parameters @("IMServerName=<Skype server/pool  name>","IMCertificateThumbprint=<Certificate Thumbprint>") -Reason "<DescriptiveReason>" [-Server <ServerName>]

Notes:

  • To configure the same settings on all Exchange 2016 servers in the Active Directory forest, don't use the Server parameter.

  • To configure the settings on a specific Exchange 2016 server, use the Server parameter and the name of the server (don't use the fully qualified domain name or FQDN). This method is useful when you need to specify different settings on different Exchange servers.

This example specifies the IM server and IM certificate thumbprint on all Exchange 2016 servers in the organization.

  • Setting override name   "IM Override" (must be unique)

  • Skype for Business server name   skype01.contoso.com

  • Certificate thumbprint   CDF34A740E9D225A1A06193A9D44B2CE22775308

  • Override reason   Configure IM

New-SettingOverride -Name "IM Override"  -Component OwaServer -Section IMSettings -Parameters @("IMServerName=skype01.contoso.com","IMCertificateThumbprint=CDF34A740E9D225A1A06193A9D44B2CE22775308") -Reason "Configure IM"

This example specifies the IM server and IM certificate thumbprint, but only on the server named Mailbox01.

New-SettingOverride -Name "Mailbox01 IM Override"  -Component OwaServer -Section IMSettings -Parameters @("IMServerName=skype01.contoso.com","IMCertificateThumbprint=CDF34A740E9D225A1A06193A9D44B2CE22775308") -Reason "Configure IM" -Server Mailbox01

Use the following syntax in the Exchange Management Shell to refresh the IM settings on the server. You need to do this on every Exchange 2016 server that's used for Outlook on the web.

Get-ExchangeDiagnosticInfo -Server <ServerName> -Process Microsoft.Exchange.Directory.TopologyService -Component VariantConfiguration -Argument Refresh

This example refreshes the IM settings on the server named Mailbox01.

Get-ExchangeDiagnosticInfo -Server Mailbox01 -Process Microsoft.Exchange.Directory.TopologyService -Component VariantConfiguration -Argument Refresh

Run the following command in the Exchange Management Shell or in Windows PowerShell on the server. You need to do this on every Exchange 2016 server that's used for Outlook on the web.

Restart-WebAppPool MSExchangeOWAAppPool

You'll know that you've successfully configured IM integration with Outlook on the web when the error message goes away, and clients are able to sign in to IM.

To verify the values of the IMServerName and IMCertificateThumbprint properties on an Exchange server, replace <ServerName> with the name of the server (not the FQDN), and run the following command:

[xml]$diag=Get-ExchangeDiagnosticInfo -Server <ServerName> -Process MSExchangeMailboxAssistants -Component VariantConfiguration -Argument "Config,Component=OwaServer"; $diag.Diagnostics.Components.VariantConfiguration.Configuration.OwaServer.IMSettings

Note: In Exchange 2016 CU3 or earlier, you need to use different values for some of the parameters:

  • Process   Microsoft.Exchange.Directory.TopologyService (instead of MSExchangeMailboxAssistants).

  • Argument   Config (instead of "Config,Component=OwaServer").

 
Show: