Managing Outlook Web App and Office Communications Server 2007 Integration

To enable Outlook Web App and Communications Server 2007 integration, you must complete the following steps.

You must have:

• Deployed Exchange 2010 in your organization.
• A working Communications Server 2007 R2 environment. All references to Communications Server 2007 in this topic refer to Communications Server 2007 R2.
• A certificate that's trusted by the Communications Server 2007 server and the Client Access server.
• The fully qualified domain name (FQDN) of the Communications Server 2007 or Communications Server 2007 pool.
• Enabled your users to use Communications Server 2007 via the Communications Server 2007 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, download and install CWAOWASSPMain.msi from Microsoft Office Communications Server 2007 R2 Web Service Provider.
2. Use Windows Explorer to find the directory where the files from CWAOWASSPMain.msi were placed. The default location is C:\Web Services Provider Installer Package\.
3. Double-click vcredist_x64.exe.
4. Double-click UcmaRedist.msi.
5. Go to Start > All Programs > Accessories, right-click Command Prompt, and then click Run as Administrator.
6. Go to the directory where the files from CWAOWASSPMain.msi were placed and run CWAOWASSP.msi.

You can 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 <install 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 (GAC).

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.

The Client Access server must be configured to use a certificate that's trusted by Communications Server 2007.

After the certificate is in place on the Client Access server, use the Exchange Management Shell to get the certificate information by running the following command on the Client Access server:

get-ExchangeCertificate | fl

Locate the certificate you want to use, and then record the following information:

• Issuer of the certificate
• Serial number of the certificate
• Subject of the certificate

The following is an example of the output from the get-ExchangeCertificate cmdlet:

IsSelfSigned       : False
Issuer             : CN=ca1, DC=contoso, DC=com
SerialNumber       : 60482F5D00000000003C
Services           : IMAP, POP, IIS, SMTP
Status             : Valid
Subject            : CN=e14w2k8

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

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 "Text editor" entry in the Client Access Permissions topic.

1. On the Client access server, navigate to <install drive>\Program Files\Microsoft\Exchange Server\V14\ClientAccess\Owa.
2. Use Notepad to open the web.config file and make the following changes:

   1. Search for IMPoolName. You'll see the following 3 entries:

      <add key="IMPoolName" value="" />
      <add key="IMCertificateIssuer" value="" />
      <add key="IMCertificateSerialNumber" value=""/>
      

   2. Modify the entries using the FQDN of the Communications Server 2007 server, the issuer of the certificate, and the serial number of the certificate.

      <add key="IMPoolName" value="<fully qualified domain name of the Communications Server pool>" />
      <add key="IMCertificateIssuer" value="<issuer>" />
      <add key="IMCertificateSerialNumber" value="<SerialNumber with space between each octet>" />
      

      Using the earlier example:

      <add key="IMCertificateIssuer" value=" CN=ca1, DC=contoso, DC=com " /> 
      <add key="IMCertificateSerialNumber" value="60 48 2F 5D 00 00 00 00 00 3C" />
      

      If the certificate issuer value contains double quotes (“), use single quotes (') to enclose the value. For example, do this if the certificate issuer is CN=ca1, DC="contoso", DC=com, you'd use <add key="IMCertificateIssuer" value=' CN=ca1, DC="contoso", DC=com ' />.

3. Save and close the web.config file.

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.

Use the Shell to run the following command on the Client Access server to enable the Client Access server to use Communications Server 2007 for instant messaging:

Get-OwaVirtualDirectory | Set-OwaVirtualDirectory -InstantMessagingType OCS

For information about how to configure Communications Server 2007 to work with Outlook Web App, see Administering Web Service Provider in the Communications Server 2007 documentation.

After you enable Communications Server 2007 integration on the Client Access server, you may also want to use segmentation or Outlook Web App mailbox policies to enable or disable IM for users:

• Managing Outlook Web App Mailbox Policies
• Set-CASMailbox