Office communicator meeting status not updating
Unfortunately all Lync accounts created are not synchronised with our Active Directory accounts, so the usual feature of Lync's presence being updated based on Outlook availability does not work.
I remember in a previous life being able to add keywords into a meeting such as [In a Meeting] in a calendar's topic and it would update communicator's status.
In the meantime uninstalling the September 2013 Update and/or rolling back to the August 2013 Lync update resolves the issue.
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.
Our staff members are people who drive this cause – it is because of our drive, our passion, our belief in others, and our belief in the strength of our mission that we are able to make a difference – every day.
We are looking for an administrative support persons who have good multi-tasking skills, and experience working from home or in a remote team setting. Good communication (written and verbal), typing, grammar, self-initiative and positive Currently seeking multiple Executive Administrative Assistants.
In a nutshell, the Lync 2013 Windows client maintains a local cache of the address book and they can get in a state that causes a variety of issues with the Contact List in the Lync 2013 client.
November 13, 2013 Update: the presence issues with Exchange free/busy that were introduced in the September 2013 Lync 2013 Client update have now been fixed in the November 2013 Update; see Lync 2013 November Update – A Much Anticipated Client Fix.
Recently there as been many reports of Presence issues with the Lync 2013 client.
The SIP profile folder is located here: Note – I achieved the same results just deleting the local address book files (Gal and Gal idx) but you should delete the whole folder to be safe.
As the Next Hop article points out, deleting this SIP profile folder will trigger a complete address book download at a random interval in the next hour from when the client is restarted.
Here is a sample screen shot of the associated bad Outlook contact used in the example above: In this case the domain name in the Email and IM address fields were different than the SIP address for this contact in the Lync address book.