We have three machines in this lab. A machine called Zirconia which has the role of domain controller and enterprise certifying entity. A machine called Topazio that has Exchange 2010 SP1 installed. A machine called Safira that has Lync Server installed. All machines are installed with Windows Server 2008 R2 and are part of the same Active Directory Domain. In the final configuration will have the ability to start an instant chat Lync Server using Outlook Web Access for Exchange Server, thus integrating the portal OWA Client Access Exchange with the Communicator Web Access Server Lync.

Download packages for Exchange Web

1. Since we are using Windows Server 2008 R2, you must install the UCMA 2.0. If the server already has an earlier version of the program it should be uninstalled before installing the new version. To download go to: http://go.microsoft.com/fwlink/?LinkID=198175

2. Download the Microsoft Office Communications Server 2007 R2 Web Service Provider, this is a container with four. Once unzipped you should see four files: CWAOWAASSP.msi, Donnetfx35setup.exe, UcamRedist.msi and vcredist_x64.exe. To download go to: http://go.microsoft.com/fwlink/?LinkId=199440

3. Download the OCS 2007 R2 Hotfix Web Service Provider on the link http://go.microsoft.com/fwlink/?linkid=199437

Installing packages in Web Client Access Exchange

1. First install the UCMA 2.0

2. In the folder Web Service Provider Package Installer, which was unpacked CWAOWASSPMain.msi. By default packages are extracted to the folder C:\Web Service Provider Package Installer.

Locate the file CWAOWAASSP.msi, ran the installer when he returned the following error: "The system administrator has set policies to prevent this installation"

To work around this problem I started the installer through the DOS command executed as administrator. 

Run the DOS on the server as Administrator.

Sailed up the folder where the file was run and CWAOWAASSP.msi

3. Finally install the Hotfix CWAOWASSP.msp, if the error occurs that the installer did not find any programs to upgrade will be necessary to restart the server. After restarting the server run the Hotfix.

Get information in the certificate in use by the Client Access

Open the Exchange Management Shell and run:

Get-ExchangeCertificate | fl

This command displays the following output

Locate the Thumbprint field and copy the result to a notepad.

Memorize also the Certificate Subject, when you configure the list of authorized hosts in Lync Server will have to configure the Certificate Subject to the name of the authorized host and create the Trusted Application Pool with this name.

The following commands are run in the Exchange Management Shell:

Get-OwaVirtualDirectory | Set-OwaVirtualDirectory-InstantMessagingServerName Name> Server Lync> InstantMessagingCertificateThumbprint <Thumbprint-Client Certificate Access>   $ True-InstantMessagingEnabled InstantMessagingType-1 

In the environment the syntax:

This command generates no output or warning. Run the command Get-OwaVirtualDirectory | fl * instant to see if the information is correct.

Configuring Client Access to integrate with Lync

Creating a Trusted Application Pool

1. Open Lync Sever Management Shell

2. Run the command Get-CsSite. This command returns configuration information pool Lync Server, record the information SiteID

3. Create a trusted Application Pool with the cmdlet

New-CsTrustedApplicationPool-Identity <Subject Name of Client Access Server> -ThrottleAsServer -TreatAsAuthenticated $true -ComputerFQDN <FQDN of Exchange Server> -Site <SiteID> -Register <Name of Lync server> - RequiresReplication $ false

4. Run  Enable-CsTopology  to apply the settings in the pool

Creating a Trusted Application for Exchange 2010 Client Access

1. In Lync Server Management Shell run:

New-CsTrustedApplication-ApplicationId <application name> -TrustedApplicationPoolFqdn <Certificate Subject Name of Client Access> -Port <port number>

In the case of environment: 

2. Run the  Enable-CsTopology

3. Open the Topology Builder and check in Trusted Application Server that an application was created with the settings used. Open OWA and verify that the settings were successful.



This article was originally written by: 
Fernando Lugão Veltem 
twitter:  @ flugaoveltem