• Lync Server 2010
• Lync client 2010
• Outlook 2010
• Exchange 2010

I have one customer whose Lync conversations have stopped saving in her Conversation History.

She uses two separate computers, and the same thing happens on both.

I confirmed that she does not have any filters applied to her Conversation History folder in Outlook.

While I was looking at her computer, one Lync conversation said "This conversation is saved...", but it wasn't in Outlook or OWA. I searched her entire mailbox, and it wasn't there. So where did it go?

Ctrl-S does the same thing. Lync says it saved the conversation, but it's not in the Conversation History folder in Outlook or OWA.

Does anyone have any ideas what would cause this?

Update: The end user was mistaken. The Lync conversations have never appeared in her Conversation History folder 9 days later. I'm not sure why she thought they did, but... there you go. Lync conversations stopped saving to her Conversation History altogether. The problem description above has been edited to reflect

Hi,

From your description above, the issue only happen for one user.

If it is the case, Lync Client uses MAPI connection to save the chat session in the history folder and show you the presence of the users within Outlook. So please check if MAPI connection is ok by holding CTRL and right click on the Lync icon in the system tray and select "Configuration Information"

Also, on Lync 2010 client--Options--Personal--Personal information manager, make sure the option "Microsoft Exchange or Microsoft Outlook" choose.

Best Regards,
Eason Huang

HI,

please confirm that users smtp and sip address is the same.If not this kind of issue will occure,but you can disable it in cs-clientpolicy and set DisableEmailComparisonCheck to true.

Set-csclientpolicy -DisableEmailComparisonCheck $true

If this is not the case,please check EWS status by right click lync icon in notifycation area and choose configuration information.

Golden rule here is to have UPN,SMTP and sip the same.

Maybe that's the golden rule, but it's just not reality. Almost none of my users have the same address for both smtp & sip, but only one user has this problem.

After learning that the end user was mistaken about Conversation History updating after-the-fact, the factors to consider narrowed considerably.

I reset the object permissions on the user's account in AD, then deleted & recreated her Lync account. Conversation History resumed saving immediately.