Office communicator presence not updating
I have Communicator working fine on some windows PCs and the Presence server is available but on some PCs connected to the same server they report the Presence server to be not available. Same cloned Windows images and some PCs connect to the Presence server and some other doesn't connect.Same version of Communicator and certificate but different Windows OS and dot net framework. I am investigating what could be the cause, but still I don't find the reason. In my case it was the Proxy Server the one cutting off the presence events. Calendar appointments works fine - ie show up in the meeting tab, and status changes correctly.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.After updating the address book, searching for Judith produced the expected results: The Lync client handles SIP address changes fairly well.Just remember to have users update their meetings and let any federated contacts know that their SIP address has changed.This means that since your contacts aren't stored with the SIP address being the identifying field, when a user on your contact list has their SIP address changed, you don't need to remove and re-add them to your contact list again. Those contacts would need to be removed and re-added since they aren't part of our Lync environment: After changing Judith's SIP address, you can see that the Resource Id stayed the same: Once Judith changes her sign in address in the Lync client, she will be able to sign in successfully and you can see that her updated display name is shown.Also any contacts that she had on her contact list would still be there: However, for William Cooper, you can see that his client didn't pick up the changes: This is because these users will need to sign out and back in before their client will pick up the changes.
Is it just to repeat information that’s already out there? So, Communicator 2007 R2 is a 32-bit (x86) application. Well, because when you run x86 applications on a x64 based system, it utilizes a system in Windows called Windows on Windows (WOW64).With the release of the September 2013 Cumulative Update for the Lync 2013 client, there is a known issue with presence not updating based on the user's free/busy status from their Exchange calendar.You can find more information about the issue in KB2883716. In the screenshot below, William has Judith as a contact on his contact list.Judith's last name is changing and so will her SIP address: After updating the user's display name and changing their SIP address, the user will be signed out of the Lync client: If we take a look at what actually happened in the database, before making any changes, you can see that each user is assigned a unique Resource Id: These IDs are what are used by the database to keep track of your contact list.