Jabber Cached Contact Photo

[jsmcniel88]

In reference to this post DATE 2012: https://supportforums.cisco.com/document/100911/jabber-displays-cached-contact-photo

Ok so if we have a new user and gets added to contact list before his photo is added to AD he will remain a grey head unless cache is cleared. This is not feasable for 700 users. Look this was dated 2012 and a reply asking for a roadmap for dynamic update that never recieved a reply. Yet we are getting fed features and ignoring these basic request (umm spell check was released for LYNC last month). I really could care less if my home phone can ring with my jabber if I cannot even have a updated photo display correctly.

When the VP of our company updates a photo and then complains that no one can see the update then this simple issue becomes a BIG problem.

Again I ask what is the plan to resolve these basic issue we continue to see?

[Amit Kumar]

have you checked the following link for Jabber for windows 9.7;

http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/Windows/9_7/JABW_BK_CF8F083D_00_cisco-jabber-for-windows-97/JABW_BK_CF8F083D_00_cisco-jabber-for-windows-97_chapter_010.html

it clearly confirms that the following defect is resolved in this release;

https://tools.cisco.com/bugsearch/bug/CSCum12467/?reffering_site=dumpcr

CSCum12467 : New AD photos do not populate in client

You should try to check if this release helps you get the answers.

Please rate if the above information helps.

[jsmcniel88]

That only addresses when photos do not populate to client, it does not speak at all in regards to dynamic updating of contact photos for on prim deployment.

In addition, there is no mention of spell check.

http://windowspbx.blogspot.com/2013/09/microsoft-lync-finally-gets-1-requested.html

[Amit Kumar]

Here is what it should do now;

Expected:
1. After doing Right click -> View profile on the contact, new or updated photo should appear 
2. After restarting client, new and updated photos should appear for contacts

dynamic update though wont happen until you restart the client.