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.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.
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.
To accommodate this scenario we simply use the Before I make any changes to demonstrate this script and the modifications we’ll make to it, let’s first see how my user is currently set in the Site Collection: And as shown in the People Picker: Note the “Name”/”Display Name”, “Work e-mail”/”E-Mail”, and “Title” fields.
Now I’ll change these values in Active Directory (make the “p” in my last name capitalized, change the title, and set the email) and then run the script (I saved the script as Sync-SPUser.ps1): (Note that lowercase “p” is the correct spelling for my name, just in case you were wondering ).
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.
Search for updating sync:
Now if we look at the user details in the Site Collection and the People Picker we should see the following: Notice that the the “Name” / “Display Name” and “Work e-mail” / “E-Mail” fields were updated but not the “Title” field.