The solution here is to delete your existing local Lync address book files and force the download of new ones from the server: I have seen this work many times in production deployments.
Jeff Schertz has an excellent blog entry on the process that is used to update the Lync address book and how to force the Lync clients to update – see Updating the Lync 2010 Address Book.
Results may not be current” message, you might want to force your client to download the address book.
This is a fairly simple task, and it’s quite similar to the workaround from the Lync 20 clients; all you need to do is add a registry key and you’re done.
If this is not the case or for some reason normal replication is failing then a manual process can be used to toss out the entire copy of AD information in the SQL database’s address book store and regenerate a completely new copy.
Issues usually surface as errors in the Lync client shortly after sign-in (when the address book synchronization is first attempted) and manifest as one of these two errors: Or, shortly after upgrading from the Communicator client, users will see the following error beneath the contact search text box: Some address book issues are caused by a problem with the local address book files on the client machine, and other synchronization issues are caused by lack of access to the address book folder (e.g.
Four common problems and their solutions are listed below.
1] The Persistent Message “” in the Lync Client When the Lync client is run for the first time it chooses a random time between 1 – 59 min to download the Lync address book (from the FE server).
The Lync address book process can be very vague about the locations it collects the information from and the priority it applies to conflicting information.
When information is changed in AD it can be very frustrating for administrators when it is updated and shows the new information for some but not others.