Updating sync blinded by science in the online dating game
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.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.This step should not be necessary under normal circumstances.In the time it took to read the previous paragraph Lync Server should have synchronized and outstanding changes in Active Directory and Step #2 can be manually processed.
This is because the corresponding to the user from the hidden “User Information List” and then update the corresponding fields manually.
To rebuild Lync’s copy of the AD data simply use the cmdlet.
Be aware that is stuff is more process intensive than the automatic delta synchronization.
The entire process happens over time based on a number of intervals, and by default looks like this: value indicates the default behavior of Lync Server to search Active Directory for any changes every minute.
This interval is 1 minute by default and can be customized to any value between 1 second and 24 hours.
This “User Information List” is located at By looking at this list you can see that several key pieces of information are stored here – unfortunately, when you change this information in Active Directory the information stored here is not updated (even after running a full or incremental import via UPS).