Answered by:
Lync Contact Search not showing all users.

Question
-
Hi,
Not sure if this is the right forum, I am having an issue with the Contact Search in Lync not showing the correct users in the search results.
I currently have clients set to query the server correctly for Contact Searches (i.e., not download the addressbook to their local client).
Say for instance I have the following users;
Robert, J
Smith, Rob
Robertson, Davis
Note: The format of our AD entries are all "Lastname, FirstName".
I would expect that when I start entering "Ro" in the Lync Search box that all three would turn up, however only 1 will, the other ones I need to type in either their last name first, account name or even their whole first name?
We are only using Lync for IM and Presence right now, so I don't think any of the phone normalization rules? Or are these taken into account under the hood regardless?
Thank you.
Greg
Tuesday, May 1, 2012 1:14 PM
Answers
-
If your AD is locked down then the Addressbook service is unable to query all the user, contact & group objects in your AD.
you might need to check permissions are set correctly- Belgian Unified Communications Community : http://www.pro-lync.be -
Saturday, May 5, 2012 4:17 AM
All replies
-
Phone normalization rules are not used when searching the addressbook.
Normally all users would show up, maybe you are using separation in addressbooks?- Belgian Unified Communications Community : http://www.pro-lync.be -
Wednesday, May 2, 2012 5:32 AM -
I think my problem is with the way data is represented in our AD. If I perform a similar search in our Active Directory via Outlook I get the same "view of data" as I did with Lync. However if I change the search to be "all columns" I get the results I expect.
Looking at http://technet.microsoft.com/en-us/library/gg398300.aspx
I can modify this behaviour in Lync as well by setting my SearchPrefixFlags to search these fields.
However, I am not seeing any difference in my search results.
No, there is no separation in addressbooks.
Greg
Wednesday, May 2, 2012 12:41 PM -
Hi Greg,
The Address Book Service (ABS) along with the Address Book Web Query (ABWQ), service all client types in Lync Server 2010.
The ABS further enhances the performance of the infrastructure by contacting Active Directory (AD DS) at scheduled intervals to collect and update information stored in the ABS databases. The databases (Rtcab and Rtcab1) are stored as part of the databases deployed on either an Enterprise or Standard Edition Front End for the operation of the Front End.
And you can try to update the Lync 2010 address book first, then search contacts again.
Noya Lau
TechNet Community Support
Thursday, May 3, 2012 3:37 AM -
Um, yes I know this, please see the above post for the problem in searching through this information and in using the client policy configuration for expanding the scope of this search.Thursday, May 3, 2012 12:51 PM
-
If your AD is locked down then the Addressbook service is unable to query all the user, contact & group objects in your AD.
you might need to check permissions are set correctly- Belgian Unified Communications Community : http://www.pro-lync.be -
Saturday, May 5, 2012 4:17 AM -
Greg,
Did you find a resolution for this issue? We are currently experiencing a very similar problem where search results do not return all expected values in the Lync Client until you complete more of the name.
Thanks,
CL
Monday, May 6, 2013 9:45 PM -
By default Lync Server doesn't do reverse name ("Last Name, First Name") indexing, which impacts the web queries (ABWQ) initiated from the desktop client and from the mobile clients. More information about it and the method to resolve it can be found on Joe Calev's blog:
How to enable last name, first searches in Lync Address Book
http://blogs.msdn.com/b/jcalev/archive/2012/06/06/how-to-enable-last-name-first-searches-in-lync-address-book.aspxJoe also talks about how to see which values get indexed for the searched contact using the Debug-CsAddressBookReplication cmdlet and the AttributeValues property. Note that this cmdlet was introduced in Lync Server 2013.
Debugging address book issues with Debug-CsAddressBookReplication
http://blogs.msdn.com/b/jcalev/archive/2012/10/10/debugging-address-book-issues-with-debug-csaddressbookreplication.aspxDebug-CsAddressBookReplication
http://technet.microsoft.com/en-gb/library/jj205232.aspxSearchPrefixFlags would represent a good choice only if the expected attribute isn't searched at all. Note that the property is applied via a client policy, so that it only impacts the users to which it is applied, not the entire index.
Ultimately, check the Flags value set for the indexed attributes, but generally modifying these is not a good idea:
The use of ABSconfig with Lync Server 2010
http://www.lync-blog.nl/?p=504&lang=enAdministering the Address Book Service
http://technet.microsoft.com/en-us/library/gg429711.aspx
Robert Panduru
- Proposed as answer by Robert PanduruMicrosoft employee Friday, June 7, 2013 9:15 AM
- Edited by Robert PanduruMicrosoft employee Friday, June 7, 2013 10:13 AM
Friday, June 7, 2013 9:14 AM