Shulou(Shulou.com)06/03 Report--

As we all know, after exchange 2013 or 2016 and skype for business server 2015 are deployed in the production environment, by default, the client outlook has integrated some functions with skype for business, including: through outlook, you can create a new skype meeting, check the user's skype status, etc., through the skype for business client, we can also directly find someone to send email, see the outlook calendar, and so on.

However, we cannot see the status information of skype through outlook web app, because this requires manual configuration before it can be integrated.

In fact, the configuration is relatively simple, the following is the configuration process (mainly in the configuration process, there are some points to pay attention to), I hope to help you.

Prerequisites:

Before configuring, we first need to make sure that the UCMA component is installed on exchange2016

Configuration process:

The whole configuration process is divided into two parts:

Part 1: configure Skype for business server 2016

Create the Skype for Business Server trusted application pool and trusted applications associated with Outlook Web App in order to add the exchange2016\ 2013 server to the list of known servers as follows:

Open the SFB Management Shell and execute the following command to create a trusted application pool:

New-CsTrustedApplicationPool-Identity mail.contoso.com-Registrar pool.contoso.com-Site 1-RequiresReplication $False

The site in the above command is obtained by the following command:

Get-CsSite | Select-Object DisplayName, SiteID

After the application pool is created, create the application identity and port with the following command:

New-CsTrustedApplication-ApplicationId OutlookWebApp-TrustedApplicationPoolFqdn mail.contoso.com-Port 5199 enables changes to the SFB topology with the following command

Enable-CsTopology

Part 2: configure exchange 2016 or 2013

There are some differences in the configuration process between exchange2016 and 2013, which I will focus on in the following configuration process

On the CAS role server, execute the following command to set up the OWA virtual directory to activate IM

Get-OwaVirtualDirectory | Set-OwaVirtualDirectory-InstantMessagingEnabled $True-InstantMessagingType OCS

Set up IM server and certificate

If we deploy exchange 2016 in our environment, the method is as follows:

Specify the IM server and IM certificate fingerprint:

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

The certificate fingerprint can be obtained by running the following command:

Get-ExchangeCertificate

If we deploy exchange 2013 in the environment, the method is as follows:

In the installation directory of the exchange 2013 MBX server, such as: C:\ Program Files\ Microsoft\ Exchange Server\ V15\ ClientAccess\ Owa, modify the web.config file and add the following 2 lines:

As shown below:

Refresh IM settings on the Exchange server

Get-MailboxServer | Get-ExchangeDiagnosticInfo-Process Microsoft.Exchange.Directory.TopologyService-Component VariantConfiguration-Argument Refresh recycle MSExchangeOWAAppPool

Restart-WebAppPool MSExchangeOWAAppPool configures outlook web app mailbox policy to enable the IM feature

Get-MailboxServer | Get-OwaMailboxPolicy | Set-OwaMailboxPolicy-InstantMessagingEnabled

$True-InstantMessagingType "OCS" to see the effect

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.