<p>Old news: SharePoint 2010 Records Management doesn't perform well in the e-discovery space. For some (most!) organizations, this isn't a detriment.</p><p>Most likely, IT pulls whatever objects are necessary to meet counsels' expectations according to its own standard operating procedure (SOP), which usually includes a third party software. Information Technology has performed e-discovery far longer and more regularly than Records Management has been allowed to implement electronic retention. Automation is Beautiful</p><p>But SharePoint 2010 Records Management services do automate records declaration beautifully. I was overjoyed the first time I architected them successfully. Of course, I mapped the records retention schedule against SharePoint 2010 RM.</p><p>Then I leveraged the records series content types holistically across site collections, attached information policies, and recalculated the indexing services to run at certain intervals. I can't tell you how excited I was when that first object moved to the matching folder the first time. I'm pretty sure I sound[ed] my barbaric yawp across the roofs of the world. Hazards Ahead</p><p><a href="http://www.cmswire.com/cms/information-management/the-problem-with-leveraging-sharepoint-records-management-services-in-office-365-022354.php">Keep reading...</a></p>