You must have:

• Deployed Microsoft Exchange Server 2010 in your organization.
  
  
• Deployed Lync Server 2010.
  
  
• Obtained a certificate that's trusted by the Lync Server 2010 server and the Client Access server and is issued by the same authority. The certificate must have the Client Access server namespace as the subject on the Subject line. The namespace may be the name of a particular Client Access server, or it may be a DNS name that's used for load balancing across multiple Client Access servers.
  
  
• Recorded the fully qualified domain name (FQDN) of the Lync Server 2010 server or the Lync Server 2010 pool that the Client Access server will connect to. The server or pool should be geographically close to the Client Access server.
  
  
• Enabled your users to use Lync Server 2010 via the Lync Server 2010 user administration tools.
  
  

You need to be assigned permissions before you can perform this procedure. To see what permissions you need, see the "Outlook Web App virtual directories" entry in the Client Access Permissions topic.

1. On the Client Access server running Windows Server 2008 or a later version, download and install UCMA 2.0 from Unified Communications Managed API 2.0, Core Runtime (64-bit).
   
   

   Note:
   Unified Communications Managed API v. 2.0 (UCMA) must be version 6907.210 or a later version. If you've installed a previous version of UCMA, you should uninstall it before you install the later version.

2. On the Client Access server, download and extract the CWAOWASSPMain.msi file from Microsoft Office Communications Server 2010 R2 Web Service Provider. The following files are extracted to the Web Service Provider installer package location:
   
   
   • CWAOWAASSP.msi
     
     
   • Donnetfx35setup.exe
     
     
   • UcamRedist.msi
     
     
   • Vcredist_x64.exe
     
     
3. Double-click CWAOWASSP.msi to install the Microsoft Office Lync Server 2010 R2 Web Service Provider.
   
   
4. Download and install the hotfix from OCS 2007 R2 Web Service Provider Hotfix.
   
   

Use the following checklist to make sure that the installation was successful:

• Look for the InstantMessaging key in the registry under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchange OWA\. The string under InstantMessaging with the name ImplementationDLLPath and the value "<Your Exchange Install Path>\ClientAccess\owa\bin\Microsoft.Rtc.UCWeb.dll" should have been created.
  
  
• The Microsoft.Rtc.UCWeb.dll file should be present in the directory <installation drive>\Program Files\Microsoft\Exchange Server\V14\ClientAccess\Owa\Bin.
  
  
• The files SIPEPS.dll and Microsoft.Rtc.Collaboration.dll should be present in the Microsoft .NET Framework Global Assembly Cache.
  
  

You need to be assigned permissions before you can perform this procedure. To see what permissions you need, see the "Certificate management" entry in the Exchange and Shell Infrastructure Permissions topic.

Note:
If all your Client Access servers are in the same namespace, you can use a single certificate for all of them.

1. Run the following cmdlet on the Client Access server to obtain certificate information for that server:
   
   

   	Copy Code
   get-ExchangeCertificate | fl

2. Locate the certificate you want to use, and then record its thumbprint and subject.
   
   

When you configure the Lync Server 2010 host authorization list, you'll add the certificate subject as the name of an authorized host.

For detailed syntax and parameter information, see Get-ExchangeCertificate.

For information about how to obtain and configure a certificate for a Client Access server, see Obtain a Server Certificate from a Certification Authority.

You need to be assigned permissions before you can perform this procedure. To see what permissions you need, see the "Outlook Web App virtual directories" entry in the Client Access Permissions topic.

Note:
Step 3 can be performed before or after step 4, but both steps are required.

This example configures which Lync Server 2010 server or pool to connect to, the certificate to be used, and enables the Client Access server to use Lync Server 2010 for instant messaging.

	Copy Code
Get-OwaVirtualDirectory | Set-OwaVirtualDirectory -InstantMessagingServerName <name of Instant Messaging server or pool to connect to> -InstantMessagingCertificateThumbprint <certificate thumbprint> -InstantMessagingEnabled $true -InstantMessagingType 1

Note:
You may have to restart Internet Information Services (IIS). You can do this by opening a Command Prompt window and using the iisreset/noforce command.

For detailed syntax and parameter information, see Set-OwaVirtualDirectory.

Note:
Step 3 can be performed before or after step 4, but both steps are required.

This example creates an Outlook Web App pool entry on the Lync Server 2010 server. Use the Lync Server Management Shell on the Lync Server 2010 server to perform the following steps:

1. Run the Get-CsSite cmdlet to get the siteID for the siteName in which you are creating the pool.
   
   
2. Run the New-CsTrustedApplicationPool cmdlet to create the trusted application pool. This also creates the external service entry in Lync Server 2010.
   
   

   	Copy Code
   New-CsTrustedApplicationPool -Identity <OwaPoolfqdn same as what is used in SN of cert> -Registrar <OCS Pool Fqdn> -Site <siteId> -RequiresReplication $false

Note:
Running the cmdlet with these parameters will create a pool with a computer FQDN that's the same as the pool FQDN. This allows you to keep adding new Outlook Web App servers to the Exchange organization without going through this process to add each of them to the Lync server.

1. Run the New-CsTrustedApplication cmdlet to add a trusted service port for the application.
   
   

   	Copy Code
   New-CsTrustedApplication -ApplicationId <ApplicationIDForOWA> -TrustedApplicationPoolFqdn < OwaPoolfqdn same as what is used in SN of cert> -Port <some available port>

Note:
The ApplicationID for Outlook Web App can’t include spaces, but otherwise it can be any string that allows the Lync Server administrator to recognize the trusted application as Outlook Web App, for example: Outlook Web App Pool.

1. Run the Enable-CsTopology cmdlet in the Shell to enable the topology.
   
   

   	Copy Code
   Enable-CsTopology

After you enable Lync Server 2010 integration on the Client Access server, you may also want to use segmentation or Outlook Web App mailbox policies to enable or disable instant messaging for users.

• Managing Outlook Web App Mailbox Policies
  
  
• Set-CASMailbox