1. Solving Today’s Problems with 10 New SharePoint 2010 Features Cory Peters - Chief SharePoint Architect Eastridge Technology, Inc. MCTS, MCPD blog: corypeters.net email: cpeters@eastridge.net

2. About Me Chief SharePoint Architect at Eastridge Technology, Inc. Tech Geek Working with SharePoint since Portal Server 2003 Graduated from NCSU Worked with all aspects of SharePoint including Architecture Administration Implementation Development Branding

3. About You

4. Agenda How We Got Here 10 New Features in 2010 That Solve Todays Problems What? How? Why? Upgrading to 2010 Questions

5. How We Got Here

6. 10 New Features

7. Unique Document IDs

8. What It Does Creates a Unique ID for every document within the Site Collection Unique ID POLICY-6-708 Unique URL http://siteurl/_layouts/DocIdRedir.aspx?ID=POLICY-6-708 IDs can be inserted into documents

9. How It Works - Demo Activate “Document ID Service” at the Site Collection Level Two Timer Jobs Document ID enable/disable job Document ID assignment job Event Handlers Handle setting the Document ID during authoring of documents

10. Why We Needed It Another check box to see SharePoint on it’s way to becoming a true DMS Pretty close to a “Permalink” solution May be able to eliminate dependency on third party solutions

11. Managed Metadata Service

12. What It Does Global Taxonomy and Folksonomy management Navigate large libraries of documents Huge pain point previously to configure views or simply page through thousands of documents

13. How It Works - Demo New service added to Central Administration Term Store Management Tool available through Central Administration, can also surface management through site collection Groups – Can have managers and contributors Term Sets – User suggestions, user submissions Term Multilingual, Custom sort order, Change management

18. Why We Needed It Practical support for larger lists/libraries Top down AND bottom up taxonomy approach Social interaction with content User suggestions User submissions Global management of the metadata

19. Metadata Navigation

20. What It Does Provides an interface for navigating very large document libraries.

21. How It Works - Demo Two Types of Navigators Metadata Navigator Content Type, Single-valued Choice field, Managed Metadata Field Filter Navigator Content Type, choice Field, Managed Metadata Field, Person or Group Field, Date and Time Field, Number Field

23. Why We Needed It Folders are not scalable (260 character limit, does not provide searchable metadata, etc) New Boundaries 30 Million Items per List 5,000 Items per View Users want list based searching that doesn’t require a crawl to run Need to demonstrate value of metadata to users

24. Content Type Hub

25. What It Does Publishes content types from a source site collection to a destination site collection Keeps content types in sync using SharePoint timer jobs

26. How It Works Connected to the Managed Metadata Service Configure the Hub URL Turn on Content Type consumption Timer Jobs Content Type Hub Content Type Subscriber Content Types are marked for publishing

30. Why We Needed It Management of content types is tough! Easy to manage with feature deployed content types Very hard to manage through the user interface

31. Unattached Database Recovery

32. What It Does Three Modes Backup Site Collection Export Site Export List Can optionally export security and version information

33. How It Works - Demo Restore from backup to new database Browse through central administration and export list Import using PowerShell Import-SPWeb

34. Why We Needed It Recycle bin is great for 99.7% of issues but what happens when a user deletes a list or a site? Remove the requirement for a restore environment Restoring content was cumbersome and slow

35. New Object Models

36. What It Does Three new object model interfaces .Net CLR (Windows forms, Console apps, etc) Silverlight Javascript

37. How It Works - Examples

38. 14SAPIbr />Microsoft.SharePoint.Client.dll Microsoft.SharePoint.Client.Runtime.dll

39. 14EMPLATEAYOUTSlientBinbr />Microsoft.SharePoint.Silverlight.dll Microsoft.SharePoint.Sliverlight.Runtime.dll

40. 14EMPLATEAYOUTSbr />SP.js

41. Why We Needed It Build less custom web services on top of SharePoint Richer, quicker to develop desktop / office integrated tools for working with SharePoint Rapid development Developers may not need SharePoint installed locally for specific kinds of development

42. Save to SharePoint

43. What It Does Save To SharePoint SharePoint Sites Workspace Integration Easy way to get documents into SharePoint rather than saving locally and performing an upload.

49. Why We Needed It 1 too many steps to get documents into SharePoint Avoid the middle man Easier to use drag and drop functionality from windows explorer

50. Search Refinements

51. What It Does Refinements (Facets) Automated list of refinements based on results FAST Search Document Previews “Entity Extractors” – Pull data from external systems

53. Why We Needed It Metadata more important with refinements Provides the user with a more focused query for finding their documents faster FAST Entity extraction allows for metadata to be pulled from the document or from systems outside of SharePoint Refinements are extensible

54. In Place Record Management

55. What It Does “In Place” Records Management Declare as Record Single or Bulk Multi Stage Retention Policies Holds and Hold Exemption eDiscovery

59. Why We Needed it Easier for users to declare records Records can expire in-place to simplify storage requirements Better support for complex retention policies Incremental expiration Ex: After 1 year delete previous versions, after 7 years delete record

60. Business Connectivity Services

61. What It Does Brings Line of Business data into SharePoint Create Connections with SharePoint Designer Full Read / Write / Update / Delete Support Looks and Feels like a SharePoint List InfoPath Integration Offline Support

62. How It Works - Demo

66. Why We Needed It SharePoint truly becomes the “Portal” to your company provided views into every other systems data Applications include surfacing information from Matter Management System Accounting System Employee Database CRM System etc

67. Upgrading

68. Server Side Requirements SharePoint Servers (WFE, Index, Query, etc) Windows Server 2008 R2 x64 Windows Server 2008 SP2 x64 Database Servers SQL Server 2005 SP3 + KB967909 x64 SQL Server 2008 SP1 + KB970315 x64 Development Environments Supports Windows 7

69. Hardware Requirements

70. Client Side Requirements Level 1 Browsers IE7, IE8 32bit Firefox 3.5 on Windows Level 2 Browsers IE7, IE8 64bit Firefox 3.5 on Unix/Linux 8.1 Safari 4.x and Firefox 3.5 on OS X Snow Leopard IE6 Not Supported!

71. Preparing to Upgrade Not Supported Windows Server 2003 SQL 2000 Internet Explorer 6 Check Hardware Readiness Check Software Versions Browser Chaos

72. Pre-upgrade Check SP2 October 2009 CU Preupgradecheck Server info Farm info Upgrade types supported Site templates, features, language packs, aamurls OS Database schema Orphans Invalid settings / missing files

73. Questions? Our Partners Software Services for Customer Success Stay Connected http://www.eastridge.net http://facebook.com/#!/EastridgeTechnology http://twitter.com/eastridgetech