WinDeveloper O365 Mailer FREE for 1 Year

WinDeveloper IMF Tune
WinDeveloper IMF Tune

Integrating Lync 2010 with Exchange 2010 – Part 2

Paul Roman [MVP for Exchange, MCSE, MCSA, MCST, MCITP]

Paul Roman [MVP for Exchange, MCSE, MCSA, MCST, MCITP] Photo

Paul is a Microsoft Certified System Engineer since 1999. His experience covers a large number of Microsoft Exchange implementations starting from small infrastructures and going to large hosting infrastructures for thousands of users. Starting with April 1st, 2010, Paul is MVP for Exchange.

Cast your Vote
Poor Excellent

One of the coolest features resulting from Exchange 2010 and Lync 2010 integration is to have access to presence and instant messaging in OWA. Today we continue our discussion doing just that.

In Integrating Lync 2010 with Exchange 2010 – Part 1 we started our discussion focusing on integrating the Outlook Client interface. Today we turn our attention to the Outlook Web App and see how to provide users with Lync functionality through it.

Integrating Outlook Web App with Lync server

One of the coolest features resulting from Exchange 2010 and Lync 2010 integration is to have access to presence and instant messaging in OWA. This is a straight forward setup and should work perfectly if you follow these steps:

  • On the Exchange 2010 Client Access Server do the following:

    1. Download the Microsoft Office Communications Server 2007 R2 Web Service Provider

    2. Run CWAOWASSPMain.msi and select a location where to save the files.

    3. From the location selected in the previous point, run the following programs (in this order):

      Visual C++ Redistributable (vcredist_x64.exe)

      Unified Communications Managed API (ucmaredist.msi)

      OCS Service Provider (cwaowassp.msi) - this has to be run from a command prompt with elevated rights

    4. Using Exchange Management Shell run:
      Get-ExchangeCertificate

      In this manner we find out which certificate is used for OWA. You should get a result similar to:

      OWA Certificate

      We need the one that has W as service.

    5. Using the Exchange Management Shell run:
      Get-OwaVirtualDirectory |fl InstantMessaging*

      This returns the current Lync integration settings. You should get a result like:

      OWA Instant Messaging Settings

      This means that for the moment there is no integration between your Exchange 2010 and Lync 2010 servers.

    6. Using Exchange Management Shell run:
      Set-OwaVirtualDirectory "owa (default web site)"
      -InstantMessagingServerName <LyncPoolName>
      -InstantMessagingCertificateThumbprint <Thumbprint>
      -InstantMessagingEnabled $True -InstantMessagingType OCS

      <LyncPoolName> is your current Lync pool name

      <Thumbprint> is the policy thumbprint property. This is one of the policy settings we saw in Integrating Lync 2010 with Exchange 2010 – Part 1 under Control via Lync Server 2010 in-band policies.

    7. Using Exchange Management Shell again run:
      Get-OwaVirtualDirectory |fl InstantMessaging*

      ...to verify if the current Lync integration settings are as we want them. You should get a result like:

      OWA Instant Messaging Settings

    8. From the command prompt Reset IIS server by running:
      iisreset /noforce

  • On the Lync 2010 front end server do the following tasks:

    1. Open Lync Topology Builder and create "New Trusted Application Pool"

      New Trusted Application Pool

    2. Select "Single computer pool", enter your Exchange Server name under "FQDN" and click "Next"

      Application Pool Settings

    3. Select your Lync Front End pool and click "Finish"

      Application Pool Next Hop

    4. Use Lync Topology Builder to publish the topology just created

      Publish Topology

    5. Using Lync Server Management Shell run:
      Get-CSTrustedApplicationPool

      This will help you check if the Trusted Application Pool was created correctly. You should get a result like:

      Get-CsTrustedApplicationPool

    6. From the Exchange Management Shell run:
      New-CsTrustedApplication -ApplicationId <OWAApp>
      -TrustedApplicationPoolFqdn <TAPFqdn> -Port <AppPort>

      <OWAApp> is the name that you want to give to this Application

      <TAPFqdn> is the Full Qualified Domain Name of your OWA server

      <AppPort> can be any port that is not used for any other service

      This will add Outlook Web App as a trusted application in Lync Server.

    7. Using Lync Server Management Shell run:
      Get-CsTrustedApplication

      ...to verify if we have the right settings. You should get a result like:

      Get-CsTrustedApplication

    8. Using Lync Server Management Shell run:
      Enable-CsTopology

      ...so as to apply the changes we just did at the Lync configuration

    9. Test in Outlook Web App if chat and presence is available

      OWA Presence

    10. A very important aspect is that you can disable or enable chat in OWA for certain users using Outlook Web App Mailbox Policies

      OWA Policy

Conclusion

Today we continued discussing how to integrate Lync Server 2010 with Exchange 2010. Here we saw how to enable access to presence and instant messaging in Outlook Web App OWA.

In the third and final part of this article, we will see how to also integrate the Exchange 2010 Unified Messaging Server role with Lync.

References

Integrating Lync 2010 with Exchange 2010 – Part 1

Integrating Lync 2010 with Exchange 2010 - Part 3

Lync 2010 Integration

Configure Outlook Web App and Lync Server 2010 Integration

Setting Lync 2010 policies (OCS Group Policy) with PowerShell

Lync and Exchange UM Integration

Deployment Process for Integrating On-Premises Unified Messaging and Lync Server 2010

User Comments - Page 1 of 1

Sebastian 21 Dec 2011 01:31
I think he meant the Lync Management Shell on 6.

The cmdlet is from the Lync Shell and does not exist in Exchange.
Than You ! 20 Dec 2011 01:34
Hi
very ussful blog thanks very much
but step 6
how i can write Lync cmd on exchange Shell
i tried to write it but faced this error
""The term 'New-CsTrustedApplication' is not recognized as the name of a cmdlet""

Thanks for your help :)
Copyright © 2005 - 2024 All rights reserved. ExchangeInbox.com is not affiliated with Microsoft Corporation