ryan mcintyre, mcitp, mcpd director , portals & collaboration
DESCRIPTION
Yes, Records Management IS Possible in SharePoint 2010!. Ryan McIntyre, MCITP, MCPD Director , Portals & Collaboration. Core Lines of Business. Neudesic started its business providing best of breed consulting services on the Microsoft Platform. - PowerPoint PPT PresentationTRANSCRIPT
Ryan McIntyre, MCITP, MCPDDirector, Portals & Collaboration
Yes, Records Management IS
Possible in SharePoint 2010!
2
CORE LINES OF BUSINESS
ConsultingServices
Products Solutions
Managed Services
Neudesic started its business providing best
of breed consulting services on the
Microsoft Platform.
As clients (our partners) began to ask us to do solve
similar problems to fill the gap,
Neudesic started packaging re-usable IP to save time and
money.
As we built trusted partnerships with our customers,
we’ve extended our services to hosting
and ongoing support and administration.
PROBLEM SPACE
• Record collections grow, never shrink
• Difficult to find the right record• Do I have the CCR Green
River album?
PROBLEM SPACE
• Records Management is Scary!• Reactive Procedures• Cumbersome & Painful• Legally Required
5
LIFE IN SHAREPOINT 2007
• Sites & Libraries• Versioning & Auditing• Content Types• Information
Management Policies• Content Organizer
Records Center
2010 HORSEPOWER
• In Place vs. Records Center• Managed Metadata
• Content Type Hub• Document Sets• Document ID
• Multi-Stage Retention• Scale (Tens of millions per Record Center)• Remote Blob Storage• eDiscovery and Holds
DEMO TIME
HOW TO BE SUCCESSFUL
Identify Roles
Analyze Content
Record vs. Non-Record
Content Types /
Retention Rules
Site Structure• In-Place vs.
Records Center
Compliance & Reporting
WHAT ELSE?
• Email– Possible if email is stored in SharePoint– Requires an extra human step…we don’t trust humans
• Physical– Track physical records– Digitize physical records
• Sites– Dispose an entire site based on retention
• eDiscovery needs some help…maybe
GOTCHAS
• Content Type changes must be Published• Published changes are pushed out on a schedule• Hub location can’t be changed (without PowerShell)• Permissions (e.g. Users can modify published content types which
then get overwritten)• Workflow publishing must be done separately
