Symptoms
Consider the following scenario:
-
You use a Microsoft Office Communicator 2007 R2 client to log on to a Lync Server 2010 environment.
-
The Public Instant Messaging (IM) Connectivity (PIC) feature is enabled in the Lync Server 2010 environment.
-
A user is using a public IM client, such as Windows Live Messenger, AOL, or Yahoo. The user types in the Session Initiation Protocol (SIP) Uniform Resource Identifier (URI) of the Office Communicator 2007 R2 users.
In this scenario, the public IM user can view the status of the Office Communicator users, and send instant messages to the users.
Cause
This issue occurs because the Office Communicator 2007 R2 client misinterprets a new container manifest setting. Therefore, the Lync Server 2010 server incorrectly treats the public IM user as a colleague or as a workgroup.
Resolution
To resolve this issue, install the following cumulative update:
2590699Description of the cumulative update package for Communicator 2007 R2: September 2011
After you apply the update, you must clean up the Public Internet Connectivity (PIC) access-control entries (ACEs) that are incorrectly assigned to the user containers from the Lync Server 2010 database. To do this, click the following article number to view the article in the Microsoft Knowledge Base:
2589546 An update is available to clean up the bad state information of a user who uses an Office Communicator client to log on to a Lync Server 2010 server
Additionally, apply the following update to the Lync Server 2010 environment:
2577957 A public IM user can send instant messages to an internal Office Communicator 2007 R2 user in a Lync Server 2010 environment
More Information
For more information about the provision PIC with Lync 2010 or Office Communications Server 2007 R2, visit the following Microsoft website:
General information about the provision PIC with Lync 2010 or Office Communications Server 2007 R2
For more information about how to enable the federation and PIC features and how to configure the routing of the incoming and outgoing SIP, visit the following Microsoft website:
How to enable the federation and PIC features and how to configure the routing of the incoming and outgoing SIP
For more information about the SIP URIs, visit the following Microsoft website:
