I have seen a number of posts in different forums with questions on how to integrate Office Communications Server2007 R2 with Outlook Web App in Exchange Server 2010 Service Pack 1. There are some changes made in SP1 that will cause your current integration to break. But this can be easily fixed with a couple of configuration changes.
Changes? Why Changes??
Well, changes in this case is good. What Microsoft has done is to move the Instant Messaging settings for the OWA virtual directory from web.config to Active Directory where it should be. It’s better to have all parameters for OWA virtual directory gathered in one place, right?
Below, I will walk you through the complete configuration process. If you only want to read about the configuration related to SP1, scroll down a bit to configuration!
OCS 2007 R2 Web Service Provider found here:
Hotfix for the OCS 2007 R2 Web Service Provider:
Update Unified Communications Managed API 2.0 Redist (64 Bit) Hotfix KB 2282949:
When running Exchange2010 Sp1 on a Windows 2008 R2, include the following UCMAREDIST Update, available here:
The installation of the Web Service Provider is quite straight forward:
- Download and execute CWAOWASSPMain.msi to you Exchange Server 2010 CAS.
- In Windows Explorer, navigate to the directory where the files from CWAOWASSPMain.msi were placed. The default location is C:\Web Services Provider Installer Package\.
- Execute and install vcredist_x64.exe.
- Execute and install UcmaRedist.msi.
- Go to Start > All Programs > Accessories, right-click Command Prompt, and then click Run as Administrator.
- Go to the directory where the files from CWAOWASSPMain.msi were placed and run CWAOWASSP.msi.
- Install the other updates listed under pre-requirements above.
Done, you should now have all the required components installed on you Exchange Server 2010 CAS.
First we will configure the certificate. We start of by getting the thumbprint of the certificate by using the following command:
get-ExchangeCertificate | fl
Your thumbprint should look something like this:
To apply this to our configuration use the following command:
Set-OwaVirtualDirectory -Identity <"WebSiteIdentity"> –InstantMessagingCertificateThumbprint <CertificateThumbprint>
Set-OwaVirtualDirectory -Identity "SUNDIS-EX01\owa (Default Web Site)" -InstantMessagingCertificateThumbprint 4DC1EE3506E06E971FF82AC8DD60015EAC11B21E
Next we set the server name for the OCS server, this should be the FQDN of the OCS server. Use the following command:
Set-OwaVirtualDirectory -Identity <"WebSiteIdentity"> –InstantMessagingServerName <ServerFQDN>
Set-OwaVirtualDirectory -Identity "SUNDIS-EX01\owa (Default Web Site)" -InstantMessagingServerName sundis-ocs01.sundis.local
Set type and Enable
Next we set the type of Instant Messaging Server to OCS by using this command:
Set-OwaVirtualDirectory -Identity "SUNDIS-EX01\owa (Default Web Site)" -InstantMessagingType OCS
And last but not least we enable Instant Messaging Server by using the following command:
Set-OwaVirtualDirectory -Identity "SUNDIS-EX01\owa (Default Web Site)" -InstantMessagingEnabled $true
Finish the configuration by doing a get to se the changes we made with the following command:
Get-OwaVirtualDirectory | fl InstantMessagingCertificatethumbprint, InstantMessagingServerName, InstantMessagingType, InstantMessagingEnabled
Well I almost forgot, the last thing you should do after all these configuration changes is to restart IIS by entering the following command:
Now you should be all set!
You do however need to make one last finishing touch on the Office Communications Server. That is to add the FQDN of the certificate that you specified in the Set-OwaVirtualDirectory
command above as a trusted host in you OCS server. To do this Navigate to the pool or server in OCS, right click on your pool or server and select Properties and then Forest End Properties.
Open the Host Authorization tab and then click Add.
Enter the FQDN found on the certificate you added in the previous step and make sure that you check Throttle AS Server and Treat As Authenticated, when finished click Ok. The FQDN will most certainly include a external domain in your case. In my case it’s an internal domain for testing purposes.
Make sure that all settings are correct, when finished click Ok.
Give OSC a moment to apply the settings and then head of to OWA and enjoy!
Thanks for reading and don’t hesitate to comment if you have any further questions or thoughts about the post!