Lync2013 integration with Exchange2013 im to Microsoft Outlook Web App 2013 (23)

In addition to the integration with Microsoft Outlook 2013, Microsoft Lync Server 2013 can also be fully integrated with Microsoft Outlook Web App 2013, and this will give Outlook Web App Add instant Messaging and presence, and enable your unified contact list to be shared between Outlook Web App and Microsoft Lync 2013. To integrate Lync server 2013 and Outlook Web apps, you must first confirm that the unified Communications managed API 4.0 runtime is installed on a Microsoft Exchange server 2013 back-end server. You can do this by determining the existence of a * * * Book table value:

Hkey_local_machine\system\currentcontrolset\services\msexchange Owa\instantmessaging\implementationdllpath

Implementationdllpath should point to the folder location of the file Microsoft.Rtc.Internal.Ucweb.dll. If not, or if the registry value does not exist, you should download and install the UCMA Runtime Setup program from the Microsoft Download Center at http://www.microsoft.com/zh-cn/download/details.aspx?id=34992.

In fact, when we install Exchange2013, the prerequisites are to install UCMA, so the default all Exchange Role servers are installed!

650) this.width=650; "Width=" 720 "height=" 541 "title=" 002.png "style=" width:720px;height:541px; "src="/HTTP/ S3.51cto.com/wyfs02/m00/53/87/wkiom1rqc7ur4w5caask0t2hlwo318.jpg "border=" 0 "vspace=" 0 "hspace=" 0 "alt=" Wkiom1rqc7ur4w5caask0t2hlwo318.jpg "/>

Create a trusted application pool for Outlook Web App

The command is:

New-cstrustedapplicationpool-identity Mail.corp.robin.com-registrar Pool01.corp.robin.com-site GDSite- Requiresreplication $False

650) this.width=650; "Width=" 720 "height=" "title=" 004.png "style=" width:720px;height:53px; "src="/HTTP/ S3.51cto.com/wyfs02/m00/53/88/wkiom1rqemqdwgcjaac9srw_3ww560.jpg "border=" 0 "vspace=" 0 "hspace=" 0 "alt=" Wkiom1rqemqdwgcjaac9srw_3ww560.jpg "/>

In the above command,mail.corp.robin.com is the fully qualified domain name of the Outlook Web App pool , and the name must be the "subject name" and "Subject Alternative name (SAN) of the certificate that provides access to the Outlook Web App. The same name appears in the field. Similarly, pool01.corp.robin.com is the fully qualified domain name of the Lync Server 2013 pool that will host the new Trusted application pool. Also note that the specified site gdsite represents the DisplayName of the Lync Server Web site. SiteID is not necessarily the same as the site's DisplayName; You can retrieve the SiteID of a Lync Server Web site by running the following command from the Lync Server Management Shell:get-cssite

650) this.width=650; "Width=" 720 "height=" 643 "title=" 003.png "style=" width:720px;height:643px; "src="/HTTP/ S3.51cto.com/wyfs02/m02/53/85/wkiol1rqd8mj-ajuaajzpxvfs44437.jpg "border=" 0 "vspace=" 0 "hspace=" 0 "alt=" Wkiol1rqd8mj-ajuaajzpxvfs44437.jpg "/>

After you create a trusted application pool, you can configure the application identity and port for Outlook Web app by using a command similar to the following command:

New-cstrustedapplication-applicationid Outlookwebapp-trustedapplicationpoolfqdn Atl-owa-001.litwareinc.com-port 5199

650) this.width=650; "Width=" 720 "height=" 643 "title=" 006.png "style=" width:720px;height:643px; "src="/HTTP/ S3.51cto.com/wyfs02/m01/53/85/wkiol1rqexaais9taamaxhmk5nw481.jpg "border=" 0 "vspace=" 0 "hspace=" 0 "alt=" Wkiol1rqexaais9taamaxhmk5nw481.jpg "/>

In the above command, ApplicationID is just a friendly identifier used to differentiate between trusted applications. ApplicationID can be any text string that does not contain spaces or other disabled characters. (To ensure that you create valid identifiers, it is recommended that you use only letters and numbers when you specify ApplicationID.) The value assigned to the port parameter will also be handled by the administrator: it can be any available network port.

After you create a trusted application, you must run the following command to enable changes to the Lync Server topology:

Enable-cstopology

650) this.width=650; "Width=" 720 "height=" 643 "title=" 007.png "style=" width:720px;height:643px; "src="/HTTP/ S3.51cto.com/wyfs02/m01/53/88/wkiom1rqesuzkrepaam2ynzype0682.jpg "border=" 0 "vspace=" 0 "hspace=" 0 "alt=" Wkiom1rqesuzkrepaam2ynzype0682.jpg "/>

After publishing the topology, I can see the mai.corp.robin.com this partner server we added in the Lync topology

650) this.width=650; "Width=" 720 "height=" 375 "title=" 01.png "style=" width:720px;height:375px; "src="/HTTP/ S3.51cto.com/wyfs02/m00/53/88/wkiom1rqejzd3lx_aao2rl_hsay157.jpg "border=" 0 "vspace=" 0 "hspace=" 0 "alt=" Wkiom1rqejzd3lx_aao2rl_hsay157.jpg "/>

Enable Instant Messaging on Outlook Web App

After you configure Lync Server correctly, you can start configuring Outlook Web App. The first step in this process is to enable Instant messaging for all Outlook Web App virtual directories on the front-end server. (You do not need to enable Instant Messaging for virtual directories on back-end servers.) In fact, it is recommended that you do not enable Instant messaging on back-end servers. You can enable Instant Messaging on the client Access server by running the following command from the Exchange Management Shell:

Get-owavirtualdirectory | set-owavirtualdirectory-instantmessagingenabled $True-instantmessagingtype OCS

650) this.width=650; "Width=" 720 "height=" 102 "title=" 008.png "style=" width:720px;height:102px; "src="/HTTP/ S3.51cto.com/wyfs02/m02/53/85/wkiol1rqedldkekdaadxnmpxcfw600.jpg "border=" 0 "vspace=" 0 "hspace=" 0 "alt=" Wkiol1rqedldkekdaadxnmpxcfw600.jpg "/>

Note: By default, instant Messaging is enabled when you install Outlook Web App; in other words, the Instantmessagingenabled property is set to True. However, you must still run the above command to set the instant message type to OCS. By default, Instantmessagingtype is set to None.

Configure the CA that is used for Lync and Exchange Server Authentication to obtain fingerprints
Note: Reapply the front-end certificate with EMS, the user name is the front-end FQDN, export the PFX certificate file after the request is completed, and then pour it into the backend. Use EMS to obtain the thumbprint of the application certificate.

The application of the certificate here is not much to say, but remember: The user name includes the FQDN of the Exchange front-end server, my environment here is two Exchange front-end and three Exchange mailbox server roles, one of which is not open, does not affect our experiment!

The approximate steps are as follows:

On one of the Exchange Client Access servers to request a certificate, I have a good name for oAuth02, after the application of the login Certificate Server: Http://robindc01/certsrv Enter the application certificate, after the application is allocated to the client server just requested, Then export from the client server and pour it into 3 mailbox role servers

The certificate that is used for Outlook Web App must be a certificate that is trusted by Lync Server. One way to ensure that certificates are trusted by both Lync server and Exchange is to use an internal certificate authority to create a certificate on a mailbox server, ensuring that the server FQDN is used as the subject name, and that the FQDN is displayed in the Certificate Override Name field. After you create the certificate, you can import the certificate to the back-end server. The end result is that the same certificate is used for two purposes: 1) communication between Exchange Unified Messaging and Lync Server, 2) integration between Outlook Web App and Lync Server.

650) this.width=650; "Width=" 720 "height=" 389 "title=" 02.png "style=" WIDTH:720PX;HEIGHT:389PX; "src="/HTTP/ S3.51cto.com/wyfs02/m02/53/86/wkiol1rqfcqq32ryaakdrzmlggs998.jpg "border=" 0 "vspace=" 0 "hspace=" 0 "alt=" Wkiol1rqfcqq32ryaakdrzmlggs998.jpg "/>

650) this.width=650; "Width=" 720 "height=" 389 "title=" 03.png "style=" WIDTH:720PX;HEIGHT:389PX; "src="/HTTP/ S3.51cto.com/wyfs02/m02/53/88/wkiom1rqfvbxujg_aakx90hu5ki405.jpg "border=" 0 "vspace=" 0 "hspace=" 0 "alt=" Wkiom1rqfvbxujg_aakx90hu5ki405.jpg "/>

Next, you have to exchage the Outlook Web App Web. config file on the Mailbox role server (this file is typically located in the folder C:\Program Files\Microsoft\Exchange server\v15\ Clientaccess\owa), add the following two lines. These two lines should be added under the < application Settings > node in the Web. config file, and this procedure should only be performed on a back-end server that has Outlook Web App installed. Note that each mailbox role server needs to be modified

<add key= "Imcertificatethumbprint" value= "ea5a332496cc05da69b75b66111c0f78a110d22d"/>
<add key= "Imservername" value= "pool01.corp.robin.com"/>

650) this.width=650; "Width=" 720 "height=" 217 "title=" 05.png "style=" WIDTH:720PX;HEIGHT:217PX; "src="/HTTP/ S3.51cto.com/wyfs02/m00/53/88/wkiom1rqftldspi7aajzqipahr0789.jpg "border=" 0 "vspace=" 0 "hspace=" 0 "alt=" Wkiom1rqftldspi7aajzqipahr0789.jpg "/>

Also note that the value assigned to Imservername is the fully qualified domain name of the Lync Server pool in which you created the trusted application pool for Outlook Web App.

After you update the Web. config file, you should run the following command on the Exchange back-end server to reclaim the Outlook Web App pool:

C:\Windows\System32\Inetsrv\Appcmd.exe Recycle apppool/apppool.name: "Msexchangeowaapppool"

650) this.width=650; "Width=" 720 "height=" "title=" 012.png "style=" width:720px;height:320px; "src="/http S3.51cto.com/wyfs02/m02/53/88/wkiom1rqf0sqwxboaaeti8t3mkk054.jpg "border=" 0 "vspace=" 0 "hspace=" 0 "alt=" Wkiom1rqf0sqwxboaaeti8t3mkk054.jpg "/>

If the recycle operation succeeds, the following message will be displayed in the Exchange Management Shell:

"Msexchangeowaapppool" successfully recycled

Configure Outlook Web APP mailbox Policy

At this point, you can configure Instant messaging for one or more of the corresponding Outlook Web App mailbox policies by using the following command. For example, the following command that is run on one of your mailbox servers will enable Instant messaging for the Default policy:

Set-owamailboxpolicy-identity "Default"-instantmessagingenabled $True-instantmessagingtype "OCS"

650) this.width=650; "Width=" 720 "height=" "title=" 013.png "style=" width:720px;height:320px; "src="/http S3.51cto.com/wyfs02/m01/53/88/wkiom1rqf23slwr3aaf3ye1n-vo816.jpg "border=" 0 "vspace=" 0 "hspace=" 0 "alt=" Wkiom1rqf23slwr3aaf3ye1n-vo816.jpg "/>

The following command enables instant Messaging for all of your Outlook Web App mailbox Policies:

Get-owamailboxpolicy | set-owamailboxpolicy-instantmessagingenabled $True-instantmessagingtype "OCS"

After you enable a mailbox policy, all users managed by the policy will implement full integration between Lync Server and Outlook Web App, provided that:

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

Here's how the integration works:

Open Zhang San OWA and click Log in to IM

650) this.width=650; "Width=" 720 "height=" 541 "title=" 015.png "style=" width:720px;height:541px; "src="/HTTP/ S3.51cto.com/wyfs02/m00/53/86/wkiol1rqgg7wladyaakab70z3oo484.jpg "border=" 0 "vspace=" 0 "hspace=" 0 "alt=" Wkiol1rqgg7wladyaakab70z3oo484.jpg "/>

You can see that the login is successful and you can see the online status

650) this.width=650; "Width=" 720 "height=" 541 "title=" 016.png "style=" width:720px;height:541px; "src="/HTTP/ S3.51cto.com/wyfs02/m00/53/88/wkiom1rqgzqihji-aalj4dwttly517.jpg "border=" 0 "vspace=" 0 "hspace=" 0 "alt=" Wkiom1rqgzqihji-aalj4dwttly517.jpg "/>

You can also see the online status of other contacts in OWA

650) this.width=650; "Width=" 720 "height=" 518 "title=" 017.png "style=" width:720px;height:518px; "src="/HTTP/ S3.51cto.com/wyfs02/m01/53/86/wkiol1rqgg7jv-aoaajt2lgo1c8606.jpg "border=" 0 "vspace=" 0 "hspace=" 0 "alt=" Wkiol1rqgg7jv-aoaajt2lgo1c8606.jpg "/>

Mouse to the contact avatar, click that even if the message icon to start the conversation

650) this.width=650; "Width=" 720 "height=" 541 "title=" 018.png "style=" width:720px;height:541px; "src="/HTTP/ S3.51cto.com/wyfs02/m01/53/88/wkiom1rqgzutgf65aammjh-2n6i950.jpg "border=" 0 "vspace=" 0 "hspace=" 0 "alt=" Wkiom1rqgzutgf65aammjh-2n6i950.jpg "/>

650) this.width=650; "title=" 019.png "style=" Float:none; "src=" http://s3.51cto.com/wyfs02/M02/53/86/ Wkiol1rqgg-x0a66aadw32sbjko669.jpg "alt=" Wkiol1rqgg-x0a66aadw32sbjko669.jpg "/>

After seeing the effect, does it feel good to have OWA integrated IM effect? Individual is still more pleasantly surprised!

This article from "Robin's Home" blog, reproduced please contact the author!

Lync2013 integration with Exchange2013 im to Microsoft Outlook Web App 2013 (23)