Ilse has a great post on how she configured the integration between Exchange 2010 SP1 OWA and Microsoft Lync Server 2010. Her lab configuration had the Exchange 2010 SP1 CAS server role co-located with HUB and MBX, but not co-located with the UM role.
If you have a slightly different configuration (like me), where the CAS and UM roles are co-located there is a small catch to following the steps Ilse outlines (in fact it is having the roles co-located on the same server and having created integration between Exchange UM and Lync Server using a SIP UM dial plan hosted by the UM server) .
The catch is that you’ll see an Error event being logged by LS Protocol Stack (event ID 14563) upon RTCSRV start, where it is basically complaining about having two entries in the known server table with different version numbers. You’ll see one entry with the role 'Application Server' and version 5 and another entry with role 'Authorized Host' and version 0. The entry with role ‘Application Server’ comes from the outcome of running New-CsTrustedApplicationPool & New-CsTrustedApplication. The entry with role ‘Authorized Host’ comes from the ExUMRouting component in Lync Server, which creates these entries for all Exchange UM Servers it finds in Active Directory hosting SIP UM dial plans.
You can safely ignore the error event, since shortly after the error event you’ll see an information event (ID 14493 from LS Protocol Stack) adding the entry with role ‘Application Server’ to the known servers table.
If you want to get rid of the error event you can remove the CsTrustedApplication representing Exchange OWA. However remember to add it back again, if you one day separate the CAS and UM role or move the SIP UM dial plan(s) to be hosted by another UM server.
I have a different setup. I have coexistence with 2007 and 2010. So I have a 2007 CAS and a 2010 CAS server in the environment. I only need the OWA integration installed on the 2010 CAS but after following Ilse's steps I get an access denied creating the Get-OWAVirtualDirectory | Set-OWAVirtualDirectory -InstantMessagingType OCS -InstantMessagingEnabled:$true -InstantMessagingCertificateThumbprint $cert -InstantMessagingServerName pool.domain.com. Any help here?
Jens: Sorry, no.
Hi, Is it a requirement to have Exchnage 2010 SP1 for this lync integration or can it be done with Exchange 2010 for OWA integration.
Jens: It can also be done with Exchange 2010.
I think I went through all the setup correctly and installed all the hotfixes and updates first but now when I open OWA I can see the little square next to the username but it always stays gray even when I am available. When you click on the name, the drop down options to change status are also grayed out. I can select "Sign In To IM" but it doesn't do anything.
Also the Contact List under the mail folders just has the green spinning circles endlessly.
I wonder if you had any ideas as to what could be missing or what needs to be added.
Jens: It seems to be a problem with the SIp communication to Lync, so I would try to trace what is happening on the Lync side using SIPStack.
Hello, is this the only way to get IM for our users without having to login to the VPN? I thought we had to deploy an edge server.
Jens> When you're using OWA IM as the client against OCS/Lync it is acting as the client on your behalf. It's therefore a question about where the CAS server(s) are located. Typically they are on the internal network and you do therefore not need a OCS/Lync Edge server or to use VPN.