Communicator contacts not updating
Yes, this is old news and there’s about 462 blog entries (ok, that’s a made up number, but there are a lot) about how to force Communicator 2007 R2 to do an Address Book (Galcontacts.db) update.
These blog entries will talk about the July 2009 update for Communicator 2007 R2 and how it introduced a random delay of 0-60 minutes for Communicator 2007 R2 to download an updated Gal to prevent the network from getting hammered by so many clients downloading an updated Gal all at the same time.
Recently there as been many reports of Presence issues with the Lync 2013 client.
Here is a breakdown of three major known issues and what to do about them.
Option #3 is what people use to set their own photo. It will be populated by Active Directory once we’re done updating. (Turns out we had to go through a lot of back-and-forth repair attempts on this one, before it all worked out.
Add new contact photos to Active Directory users whatever way you prefer (several management tools exist). The Active Directory sync is working…just not for images? There’s a lot of parts to the Lync contact profile – and by the time we were done, we’d touched all of them.) Next post I’ll detail 3 more fixes we tried.
The most common problem was introduced in the recent September 2013 update package for the Lync 2013 client.
The issue is documented in this support KB article: Presence status isn’t updated based on Exchange calendar in Lync 2013.
That registry entry works perfectly fine on x86 systems. WOW64 has its own section within the registry called Wow6432Node.
There have been other issues reported after applying this update, but it has not been determined what exactly the combination of factors introduce the issue.
When writing a new email in Outlook and you also use Microsoft Communicator, Outlook can display the current status in real time of the people you are writing to.
This issue is being actively being investigated by the Lync team at Microsoft so stay tuned.
In the meantime uninstalling the September 2013 Update and/or rolling back to the August 2013 Lync update resolves the issue.