Asked by:
Lync Archiving with Skype for Business Client

-
HI
We are running production Lyn 2010 environment, with Lync archiving using Lync Clients.
We have as small test group of Office 2016 with Skype 2016 client .
We are finding that when conversations /chats are archived that have been created via the Skype Client, when exported to eml from the archive server - the conversation gets 'padded out' .
Instead of having the standard simple eml file with header and conversation in the body we are getting the same , with numerous 'untitled attachment.doc' , 'untitled attachment XXX.hmtl'.etc..
The attachment contain the same information /chat..
Lync client archiving exports did not do this. Only when using Skype for Business 2016 client.
Question
All replies
-
-
-
It could be the typical behavior of the integration. Lync 2010 is out of mainstream support anyway. You should plan for an upgrade to Skype for Business instead. Just not because of this issue, it's because the product is out of support.
http://thamaraw.com
- Proposed as answer by henghenghahi Friday, August 11, 2017 11:19 AM
-
Yes we are in the midst of upgrading , however this is a test pilot group and for Compliance issues exporting & reviewing from Lync Archive server in their current state is a very messy production.
With the Lync Chats archived via the same Lync Archive server the exports as a standard eml file with conversation history.
Now Skype for Business chats via the same Lync Archive server the exports poduce a eml file with numerous doc ot txt attachments.Is there a 'MS Proofing process' inbuilt with SFB client? Can the SFB client via csClientPolicy be reduced to plain text?
-
-
-
-
Hi DJD1977,
Are these replies helpful to you? Please remember to mark the replies as an answers if they help, this will help others who are experiencing the same issue.
Best Regards,
Molly Wu
TechNet Community Support
Please remember to mark the replies as an answers if they help and unmark them if they provide no help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.
- Edited by henghenghahi Friday, July 14, 2017 9:09 AM