We will be moving to Exch 2013, but due to our archiving requirements that is 
not sufficient.  We have to keep e-mail and conversations for 7+ years and do 
not want to keep mailboxes in exchange after employee termination.  So we have 
to use a 3rd party archive product to separate the exchange requirement and 
since the Lync tie-in to Exchange does not use the SMTP interface for 
conversation storage, the Journal rules will not capture it.

From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On 
Behalf Of Michael B. Smith
Sent: Thursday, November 6, 2014 8:34 AM
To: exchange@lists.myitforum.com
Subject: [Exchange] RE: otp: Lync 2013 compliance logging

Are you using Exchange 2013 onsite?

If so, and you have integrated Exchange and Lync, then Lync can already do this 
for you by saving IM conversations into a message folder named "Conversation 
History".

From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Senter, John
Sent: Thursday, November 6, 2014 8:24 AM
To: exchange@lists.myitforum.com<mailto:exchange@lists.myitforum.com>
Subject: [Exchange] otp: Lync 2013 compliance logging

I know this is not an Exchange issue, but feel that most groups that have 
Exchange may also have Lync.

So for people are have Lync 2013, do you have a 3rd party app to capture IM 
conversations and place in an archive system like Autonomy or Enterprise Vault. 
 I am more interested in on premise systems with perpetual licensing, as some 
have started moving to subscription licenses.  The one I know about are:
                DataParser  by 17a-4
                Vantage by Actiance
                Mindlink Compliance by Mindlink
We have to have a product that will move all conversations to a worm-type 
device and allow for both end-user and compliance searching for e-discovery.  
We already have that with our mail archive product so having a IM product that 
converts IM messages to e-mail and sending to the archive, is what we want.  We 
have that today with our OCS deployment using the now defunct Quest Policy 
Authority.

Thanks for your help.

Reply via email to