Symptoms
Consider the following scenario:
-
User A uses 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.
-
User B is using a public IM client, such as Windows Live Messenger, AOL, or Yahoo. User B types in the Session Initiation Protocol (SIP) Uniform Resource Identifier (URI) of user A.
In this scenario, user B can view the status of user A, and send instant messages to user A.
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 user B as a colleague or as a workgroup.
Resolution
To resolve this issue, install the following cumulative update:
2571546 Description of the cumulative update for Lync Server 2010: July 2011 After you apply the update, you must clean up the bad state for these users. 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
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 inbound and outbound SIP, visit the following Microsoft website:
How to enable the federation and PIC features and how to configure the routing of the inbound and outbound SIP
For more information about the SIP URIs, visit the following Microsoft website:
