Consider the following scenario:
Microsoft Exchange Server is deployed in a Microsoft Lync Server 2010 environment.
You add a contact object for a user (user A) in the Contacts view in Outlook, and then you input the work telephone number of a second user (user B) in the contact object for user A. User B is in the global address list (GAL).
You sign in to Lync 2010 and perform a search for user A.
In this scenario, user A is listed in the search results together with the picture and the presence information for user B. Additionally, when you try to start a conversation with user A, the instant messages and calls are directed to user B.
This issue occurs because Lync 2010 does not merge the contact information correctly.
To fix this problem, install the following cumulative update:
2670326 Description of the cumulative update for Lync 2010: February 2012 This update installs the following client policy:
UseAlternativeContactMergeBehaviorWhen the client policy is set to true, Lync 2010 does not link an Active Directory contact to an Outlook contact that only contains telephone information. Additionally, Lync 2010 gives precedence to the Active Directory contact over the Outlook contact when Lync 2010 performs a Reverse Number Lookup (RNL) operation. This behavior does not change if the policy is set to false or if the policy is not set.
To set the policy to true, the administrator must run the following command in Lync Server Management Shell to apply a client policy:
New-CsClientPolicyEntry -Name "UseAlternativeContactMergeBehavior" –Value "True"
For more information about the New-CsClientPolicy command, visit the following Microsoft website:
General information about the New-CsClientPolicy commandFor more information about the New-CsClientPolicyEntry command, visit the following Microsoft website: