I upgraded to the RTM version today, and OCS 2007 R2 is still functional.

Restarted Outlook, restarted Communicator However, Office Communicator 2007 does not process SOAP messages in code chunks.

This most commonly is an issue when you are using an internal CA that is either offline or firewalled off.

Removed the aforementioned registry hack If Communicator 2007 cannot get to the CRL distribution point for the ceritificate (Details Tab -> CRL Distribution Points on the Root CA certificate), it usually wont log in.

Uninstalled Lync 2010, installed Communicator 2007 R2.

32-bit Office 2010 w/ Lync 2010 client and this registry hack on 64-bit Win7.

Just as a recap, here’s what I had going on:

Here’s the full registry key and value that I changed to fix it: In looking at the two sub-keys, I could see “Lync” and “Communicator.” So, I took a guess and changed the value to “Communicator,” restarted Outlook, and–voila–I was in business! There’s a registry key that lets Outlook know what the default IM provider is, and this value was set to Lync on my workstation. After a bit of Googling and tinkering, though, I was able to find a solution to get things back on track. I decided that Office 2013 was more important than Lync 2010 and reverted to OCS 2007 in hopes that it would fix my woes, but it did not. I assumed this was because I was using an unsupported configuration with my 2010 Lync client connecting to an OCS 2007 server.

As noted last week, I installed the Office 2013 Preview and was generally excited about it except for the fact that I wasn’t getting any presence information for contacts from Lync.

Microsoft office communicator 2007