1 | SharePoint Saturday St. Louis 2015 EDISOVERY IN SHAREPOINT 2013 JODY SOCHA

2 | SharePoint Saturday St. Louis 2015 Outline 6 | SharePoint Saturday St. Louis 2015 Thanks to Our Sponsors! GoldSilverRaffle

3 | SharePoint Saturday St. Louis 2015 Housekeeping  Follow SharePoint Saturday St. Louis on and hashtag #spsstl  Play “Sponsor Bingo” to register for your chance to win one of the many great giveaways at the end of the day  Schedule and evaluate each session you attend via our mobile app that can be used across devices at: azurewebsites.net

4 | SharePoint Saturday St. Louis 2015 Session Evaluations  Schedule and evaluate each session you attend via our mobile app that can be used across devices at azurewebsites.net  You will be able to evaluate sessions added to your “My Sessions” 25 minutes before the scheduled end time  Evaluations are stored anonymously and your feedback is appreciated  The app will be the only method available to submit session evaluations for the event and we hope you find it intuitive and convenient 4 | SharePoint Saturday St. Louis 2015

5 | SharePoint Saturday St. Louis 2015  Jody Socha   Peabody Energy  Sr. Mgr., Collaboration Services  SharePoint Experience – 10 years Biography 5 | SharePoint Saturday St. Louis 2015

6 | SharePoint Saturday St. Louis 2015 Outline 6 | SharePoint Saturday St. Louis 2015 Project Overview SharePoint and eDiscovery Lessons Learned Outline

7 | SharePoint Saturday St. Louis 2015 Project Overview

8 | SharePoint Saturday St. Louis 2015 PROJECT OVERVIEW Implement 180 day Retention policy Configure system to allow exceptions Records Legal Holds Migrate to Exchange 2013 Evaluate eDiscovery platform

9 | SharePoint Saturday St. Louis 2015 JournalingIn Place s copied to a separate location s flagged in place for keeeping s preserved regardless of mailbox activity Extra care require to prevent loss Searches performed in separate system Searches performed in production Requires third party softwareAll in Exchange More expensiveLess expensive Management Options

10 | SharePoint Saturday St. Louis 2015 EDRM Model

11 | SharePoint Saturday St. Louis 2015 SharePoint and eDiscovery

12 | SharePoint Saturday St. Louis 2015 eDiscovery Architecture in SharePoint

13 | SharePoint Saturday St. Louis 2015 SourceSearch In-place Preservation Export SharePoint 2010 and SharePoint 2007 YesNoYes Exchange 2010No SharePoint 2013Yes Exchange 2013Yes File sharesYesNoYes Content from External systemsNo Sources and Capabilities

14 | SharePoint Saturday St. Louis 2015 Cases LGHLD LGHLD LGHLD Sets and Holds Jones, Smith | eDiscovery (H) Jones, Smith, Adams | SharePoint Smith, Site A | Legal (H) Queries and Exports Source 1 Sources 1 and 2 Source 1 Source New SharePoint eDiscovery Terms

15 | SharePoint Saturday St. Louis 2015 SharePoint Legal Holds

16 | SharePoint Saturday St. Louis 2015 Exchange Holds

17 | SharePoint Saturday St. Louis 2015 Implementation and Lessons Learned

18 | SharePoint Saturday St. Louis 2015 Implementation Details

19 | SharePoint Saturday St. Louis 2015 eDiscovery leverages search security trimming Users responsible for eDiscovery need to have permissions to content Grant users access at web application user policy Add users as a site collection administrator (O365) For file shares, this must be done at the file share level Use Groups instead of users Access to group(s) can be controlled easier than adding individual users Prevents search from needing to reindex items Use separate user account for discovery Access to the crawl log needed for items that could not be indexed Access Considerations

20 | SharePoint Saturday St. Louis 2015 In-Place Holds Preservation Libraries only created when content is edited – documents, pages, lists Rate of disk increase will be dependent on rate of change Interim changes not necessarily saved Search Amount of content will dictate architecture Current guidance is 500 GB disk for 10M items – 10M items per index Utilizes Exchange indexing Storage Considerations

21 | SharePoint Saturday St. Louis 2015 One eDiscovery Center for each Search Farm Application Complex queries are more taxing than simple queries Adding more sources increases the number and complexity of queries If shared with Enterprise Search, users could be impacted Be aware of Search limits on words and characters Search Considerations

22 | SharePoint Saturday St. Louis 2015 Content is downloaded individually using respective protocols (SharePoint, file shares) Search is not used during the export process In general, exports are not expected to affect a SharePoint environment Export Considerations

23 | SharePoint Saturday St. Louis 2015 Additional Considerations Work with legal to evaluate overall process Chain of custody Auditing Requirements Roles and responsibilities Education and Awareness Hybrid considerations - O365 vs On Premise Complexity of test environment Environment leverages Outlook Web Access for previews

24 | SharePoint Saturday St. Louis 2015 EDRM Model