Article ID: 2672944 - View products that this article applies to.
Consider the following scenario:
This issue occurs because Lync 2010 does not merge the contact information correctly.
To fix this problem, install the following cumulative update:
2670326This update installs the following client policy:
(http://support.microsoft.com/kb/2670326/ )Description of the cumulative update for Lync 2010: February 2012
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:
General information about the New-CsClientPolicyEntry command
Article ID: 2672944 - Last Review: March 1, 2012 - Revision: 1.0