Lync-OWA Integration

Please note that the below post relates to Exchange Server 2010 RTM and Lync Server 2010 RTM.  There have been changes made with the release of Exchange Server 2010 SP1 and SP2 to make this process easier.  This subject has been well documented and so I will not post the process again but I'll leave this on the blog for historical pusposes as it may still be relevant in certain circumstances.
--------------------------------------------------------------------

It's been a while since I last posted; however it has been a very busy year. I have just deployed Lync in to production and wanted to post on configuring up the OWA-Lync integration to allow the chat feature to work within the Outlook Web App.
Lync has introduced many new fantastic features, one of which is the Lync Web App for clients that require access to meetings but cannot download the attendee or Lync client. The Lync Web App (or Reach client) is not the same as CWA in OCS 2007 R2 due to the fact that it is aimed at meeting use rather than an IM client and so there is no provision for logging in directly to the client and using it for IM and presence. Access to the client is delivered via a meeting invite and using the simple URL, the system decides when and if you connect to the web app. Once in, you still get access to all the web conferencing features and can utilise the call back feature.
With all of this in mind, the OWA chat and LWA provide a complete solution for web based access and this is avialable across various browsers extending the solution out to MAC and Linux users.

There are a number of steps that must be completed to configure this integration as follows:

Step1:-Deploy the DLLs to the CAS ServerDownload the CWAOWASSPMain.msi file from Microsoft and run on the CAS which will extracts a number of files to a directory on the C: drive
Run the each of the executables in this directory to install the Web Service Provider files
Assuming your CAS OS is running WS2K8 R2 you will need to update the UCMARedist to the latest released version.
Check out my earlier blog about this http://viammercer.blogspot.com/2010/03/exchange-2010-and-ocs-r2-owa-chat.html
Now copy the files located in the %programFiles%\Microsoft\Exchange Server\V14\bin:
SIPEPS.dll
Microsoft.Rtc.Collaboration.dll
Microsoft.Rtc.UCWeb.dll
Paste them in to the directory %ProgramFiles%\Microsoft\Exchange Server\V14\Client Access\owa\bin


Step2:-Gather the CAS certificate detailsRun the following from the EMS
Get-ExchangeCertificate fl
This assumes only one certificate exists, otherwise it would be worth noting the thumbprint of the correct certificate and add the to the command to make it look something like...
Get-ExchangeCertificate -Thumbprint fl

Note the following details:
Issuer:CN=caTest, DC=Testlab,DC=local
SerialNumber: 7894G6T50000000003H
Subject:CN=CAS1.testlab.local

Step3:-Update the OWA Web.config fileOpen the web.config file from the directory %programFiles%\Microsoft\Exchange Server\V14\Client Access\OWA
Find the line including IMPoolName and update to read: '"IMPoolName" value="LyncPoolFQDN"'
Find the line including IMCertificateIssuer and update to read: '" IMCertificateIssuer" value="CN=caTest,DC=Testlab,DC=local"'
Find the line including IMCertificateSerialNumber and update to read: '" IMCertificateSerialNumber" value="78 94 G6 T5 00 00 00 00 00 3H"'
Note that the spaces are important and must be added
Set the instant messaging type on the OWA virtual directory to OCS using the command:
Set-OwaVirtualDirectory -Identity OwaVDIdentity -InstantMessagingType OCS
Run 'IISReset '

Step 4:-Create a Trusted Application Server within LyncIf the CAS is collocated with the UM role which is servicing Lync via a SIP dial plan then a trusted application pool must be created. If the CAS and UM roles are not collocated then an additional step must be completed to create a trusted application. I will discuss both options.
Trusted Application PoolRun 'Get-CsSite' from the Lync Management Shell
Note the siteID for the site in which you are deploying the integration
Run the command 'New-CsTrustedApplicationPool -Identity CASFQDN -ThrottleAsServer $true -TreatAsAuthenticated $true -ComputerFQDN casfqdn-site siteid-Registrar lyncpoolfqdn-RequiresReplication $false'
Trusted Application (Only needs to be run if the CAS and UM are running on separate servers)
Run the command 'New-CsTrustedApplication -ApplicationID appidstring-TrustedApplicationPoolFqdn casfqdn-Port availableport'

Run the command 'Enable-CsTopology'

This concludes the configuration and should result the ability to view presence jelly beans within OWA as well as the use of the Chat feature.

There may also be a requirement to allow the w3wp.exe process through the Windows firewall on the CAS server should this be blocked.