True, but if I remember correctly Microsoft does not recommend that as a long term solution and it is SQL so not hard to remove/modify entries; that is why we have to offload to an environment that safe guards that. Being in a highly regulated environment, we have to adhere to 17a-4, which requires worm storage, or a service that is certified like worm.
From: [email protected] [mailto:[email protected]] On Behalf Of Orlebeck, Geoffrey Sent: Thursday, November 6, 2014 11:02 AM To: '[email protected]' Subject: [Exchange] RE: otp: Lync 2013 compliance logging Lync has an archiving piece that allows you to offload to a separate SQL DB and you can use SSRS to report against it. That's how we do it here. Thanks, Geoff From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Senter, John Sent: Thursday, November 06, 2014 7:57 AM To: [email protected]<mailto:[email protected]> Subject: [Exchange] RE: otp: Lync 2013 compliance logging 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: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Michael B. Smith Sent: Thursday, November 6, 2014 8:34 AM To: [email protected]<mailto:[email protected]> 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: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Senter, John Sent: Thursday, November 6, 2014 8:24 AM To: [email protected]<mailto:[email protected]> 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. Confidentiality Notice: This is a transmission from Community Hospital of the Monterey Peninsula. This message and any attached documents may be confidential and contain information protected by state and federal medical privacy statutes. They are intended only for the use of the addressee. If you are not the intended recipient, any disclosure, copying, or distribution of this information is strictly prohibited. If you received this transmission in error, please accept our apologies and notify the sender. Thank you.
