Blog list not updating
The second half of the server-side process is controlled by the Address Book Service which pulls information from the SQL database and writes the changes to the address book files.
cmdlet is run then a ‘synchronize now‘ event is marked and the update is not actually run immediately.
Number of device bytes written: 1,657 compressed to 1,248 bytes on disk.
Just as Office Communicator has done since a later R2 hotfix, Lync also will not immediately download changes to the Address Book files when first launched, but instead wait for a random interval of time between 1 and 60 minutes.
Like I was working on the file, they apparently did some heavy tweaking.
They committed theirs and I said to myself no worries my changes are minor.
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.
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.
To trigger an immediate download two steps must be taken on the client workstation.
The first step only needs to be performed once per workstation, while the second would be done each time a forced update is desired.
With that I figure theres gotta be a way to reset the file, or force it to take on the changes. I think you have some major misunderstanding of how SVN works.
Take a look in the SVN book and learn about what will happen if 2 people is modifying same file concurrently.