Updating source control status
To rebuild Lync’s copy of the AD data simply use the cmdlet.
Assume that 120 seconds have passed since the initial fetch and the browser has initiated a new request for the same resource.Check the platform documentation and confirm your settings.When the server returns a response, it also emits a collection of HTTP headers, describing its content-type, length, caching directives, validation token, and more.At this point, the browser could dispatch a new request and fetch the new full response.However, that’s inefficient because if the resource hasn't changed, then there's no reason to download the same information that's already in cache!Because Step #1 in the process happens by default every minute then any recent changes in AD should already be imported into the SQL database.
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.
Take note that the there is another difference here between the Lync and Communicator clients.
For standard 32-bit operating systems the registry path below is the same regardless of the client versions (OC 2007 R2 with July 2009 update or Lync 2010 RC) but previously 64-bit operating systems running the 32-bit only OC 2007 R2 client had to have the setting created under the Wow6432Node policies key.
Fetching something over the network is both slow and expensive.
Large responses require many roundtrips between the client and server, which delays when they are available and when the browser can process them, and also incurs data costs for the visitor.
As a result, the ability to cache and reuse previously fetched resources is a critical aspect of optimizing for performance.