Exchange and Lync IM IntegrationPresenter: Triston Wan | MVP – Exchange ServerDavid Lim | MVP – Lync Server

Event:Community {Technology} Update 2011

Date:25th June 2011

Agenda

• Introduction

• Integration screenshot

• System requirements

• Components

• Demo

• Q&A

Introduction

• Lync Server 2010 can be integrated with Exchange 2010 SP1, so that Exchange Outlook Web App can also act as a Lync web client. Once integrated, users will automatically log into Lync when they log into OWA. The OWA interface changes to include the following new features:

– Sign In and Sign Out - Users can sign in or sign out of instant messaging from OWA. Once signed in, the user will automatically sign into IM every time they sign into OWA.

– Presence - User presence information is available for Lync users, showing a colored Chiclet indicating their availability.

– Contact List - The user's Lync IM contact list is made available in the OWA folder pane. Users can be added and removed, and contact groups can be managed directly from OWA.

– Instant Messaging - Lync users can chat with other Lync users using instant messaging directly from OWA.

– Right-Click Functionality - Right-click menus and actions are updated to include new Lync features. For example, right-click an email address to chat with the user or add them to an IM contact list.

System RequirementsExchange Server 2010 / Lync Server 2010

• dotnetfx35setup.exe, if the .NET Framework 3.5 is not installed on Windows Server 2008. For Windows Server 2008 R2, install the .NET Framework 3.5.1 feature from Server Manager.

• Exchange Server 2010

• Exchange Server 2010 SP 1

• Lync Server 2010

ComponentsExchange Server 2010

• Microsoft Office Communications Server 2007 R2 Web Service Provider from http://www.microsoft.com/downloads/en/details.aspx?familyid=CA107AB1-63C8-4C6A-816D-17961393D2B8&displaylang=en on your Client Access Server.

• Next, download and save the OCS 2007 R2 Web Service Provider Hotfix KB 981256 from http://www.microsoft.com/downloads/en/details.aspx?FamilyID=45C94403-39FA-44D3-BE23-07F25A2D25C7

• Download and save the Unified Communications Managed API 2.0 Redist (64 Bit) Hotfix KB 2400399 from http://www.microsoft.com/downloads/en/details.aspx?FamilyID=1F565A42-71D2-4FBD-8AE0-4B179E8F02AB to the same C:\Web Service Provider Installer Package folder.

• If your CAS server is running Exchange 2010 SP1 on Windows Server 2008 R2, you need to download and save the UcmaRedist.msp patch in Microsoft Office Communications Server 2007 R2 Hotfix KB 968802 from http://www.microsoft.com/downloads/en/details.aspx?FamilyID=b3b02475-150c-41fa-844a-c10a517040f4. The tricky part here is that the file name (UcmaRedist.msp) is the same as the Communications Managed API 2.0 Redist (64 Bit) Hotfix KB 2400399. Just rename this file name to something like UcmaRedist-R2.msp.

Exchange Server Side

• vcredit_x64.exe

• UcmaRedist.msi

• UcmaRedist.msp

• UcmaRedist-R2.msp, if your CAS is running on Windows Server 2008 R2

• CWAOWASSP.msi

• CWAOWASSP.msp

• Note that the MSI and MSP packages have a limited GUI during setup and don't indicate that they've installed successfully.

Enable Exchange 2010 SP1 Outlook Web App and IM Integration

Exchange Server Side

• Next configure the Exchange 2010 SP1 Client Access Server for Lync Server integration. Run the following two commands from the Exchange Management Shell on the CAS:

• $cert = (Get-ExchangeCertificate | Where {$_.Services -ilike "*IIS*"}).Thumbprint

• Get-OWAVirtualDirectory | Set-OWAVirtualDirectory -InstantMessagingType OCS -InstantMessagingEnabled:$true -InstantMessagingCertificateThumbprint $cert -InstantMessagingServerName pool.domain.com

• Be sure to change the InstantMessagingServerName value in the command above to the FQDN of your Lync Server pool.

Enable Exchange 2010 SP1 Outlook Web App and IM Integration

Lync Server SideEnable Exchange 2010 SP1 Outlook Web App and IM Integration

• Lync Server Management Shell:

• Get-CsSite

• New-CsTrustedApplicationPool -Identity <Exchange CAS FQDN> -ThrottleAsServer $true -TreatAsAuthenticated $true -ComputerFQDN <Exchange CAS FQDN> -Site <Site> -Registrar <Pool FQDN in the site> -RequiresReplication $false

• Run Enable-CsTopology.

• Start “Lync Server Topology Builder.”

• Select the option to Download Topology from existing deployment.

• In the Save Topology As dialog box, select the Topology Builder file you want to use, and click Save.

• In the left pane, expand the tree until you reach Trusted application servers.

• Expand the Trusted application servers node.

• You should now see the Exchange 2010 SP1 CAS server listed as a trusted application server

Demo

Troubleshooting

• Is the certificate used on Lync, and Exchange issued by a trusted CA for both Lync and Exchange

• Does the certificate have the correct name, both for Lync and Exchange

• Did you ran Enable-CSTopology after adding Exchange as a csTrustedApplication

• check by using the cmdlet Get-CsManagementStoreReplicationStatus (should not be replicate)

Troubleshooting Lync-Exchange OWA Integration

Q & A