This step should not be necessary under normal circumstances.
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.
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.
Time will pass and eventually everyone will get the update. If everyone logs in around the same time every day (the start of business), then an excessive load will be placed on the environment and it will even cause performance problems. It is simply that it might be a great idea to have the random offset of 0-60 minutes, but there are some individuals where this just isn’t acceptable.
For example, if I am an administrator and I get calls saying that the Address Book search is not finding somebody, and the calls are from VIPs in the company, I really need a way to test to make sure that the names can be found.
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.
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.