Consider the following scenario:

  • You deploy an x86 version of Microsoft Lync 2013 in a Lync Server 2013 environment.

  • You create a user (user A) in Active Directory Domain Services (AD DS). One or more of the identity attributes of user A, such as cn, displayName, givenName, name, and sn, are written by using the non-Latin characters, such as Cyrillic.

  • You rebuild the user's database.

  • A user (user B) signs in to the Lync 2013 client.

  • User B tries to search for user A by entering the non-Latin characters in a case that differs from the one in the AD DS attribute. For example, if user A's display name is "Дарья Попкова" in AD DS, user B searches for user A by inputting one of the following strings:

    • д

    • п

    • ДА

    • ПО

In this scenario, user A is missing from the search result returned by Lync 2013. However, if user B inputs the characters in the same case as the one in the AD DS attributes, for example, if user B inputs one of the following strings, user A will be in the search result.

  • Д

  • Да

  • П

  • По


To resolve this issue, install the following update:

2880474 Description of the Lync 2013 update: April 2014

Note After the update is applied, the symptom may persist until the client downloads again a full copy of the address book. To force a full download, delete the local copy of the address book files (GalContacts*.db).

More Information

The latest version of the RtcAbAttributeIndexRules.xml guarantees the users whose attributes are entered by using a non-Latin language are indexed in the Lync Server 2013 user’s database.

For more information about the indexing issue, go to the "Indexing in the Address Book does not work as expected in some language (3336047)" section in the following Microsoft website:

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Thank you for your feedback!