Solve Todays Problems with 10 New SharePoint 2010 Features


Published on

Published in: Technology
1 Comment
No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Developers, Administrators, Designers, End Users2007, WSS, 2010
  • 2003 – Visionary + Leader
  • Allows you to connect to external data and manipulate that data in SharePoint.What were talking about:HR can log into SharePoint open the “Employees” list modify a record. Update someones last name and that update is immediately synchronized in source of record. (Employee database) Additionally that employee record is available inside of Outlook as a contact and can be fully read/edit in outlook as well.
  • Solve Todays Problems with 10 New SharePoint 2010 Features

    1. 1. Solving Today’s Problems with 10 New SharePoint 2010 Features<br />Cory Peters - Chief SharePoint Architect<br />Eastridge Technology, Inc.<br />MCTS, MCPD<br />blog:<br />email:<br />
    2. 2. About Me<br />Chief SharePoint Architect at Eastridge Technology, Inc.<br />Tech Geek<br />Working with SharePoint since Portal Server 2003<br />Graduated from NCSU<br />Worked with all aspects of SharePoint including<br />Architecture<br />Administration<br />Implementation<br />Development<br />Branding<br />
    3. 3. About You<br />
    4. 4. Agenda<br />How We Got Here<br />10 New Features in 2010 That Solve Todays Problems<br />What? How? Why?<br />Upgrading to 2010<br />Questions<br />
    5. 5. How We Got Here<br />
    6. 6. 10 New Features<br />
    7. 7. Unique Document IDs<br />
    8. 8. What It Does<br />Creates a Unique ID for every document within the Site Collection<br />Unique ID<br />POLICY-6-708<br />Unique URL<br />http://siteurl/_layouts/DocIdRedir.aspx?ID=POLICY-6-708<br />IDs can be inserted into documents <br />
    9. 9. How It Works - Demo<br />Activate “Document ID Service” at the Site Collection Level<br />Two Timer Jobs<br />Document ID enable/disable job<br />Document ID assignment job<br />Event Handlers<br />Handle setting the Document ID during authoring of documents<br />
    10. 10. Why We Needed It<br />Another check box to see SharePoint on it’s way to becoming a true DMS<br />Pretty close to a “Permalink” solution<br />May be able to eliminate dependency on third party solutions<br />
    11. 11. Managed Metadata Service<br />
    12. 12. What It Does<br />Global Taxonomy and Folksonomy management<br />Navigate large libraries of documents<br />Huge pain point previously to configure views or simply page through thousands of documents<br />
    13. 13. How It Works - Demo<br />New service added to Central Administration<br />Term Store Management Tool available through Central Administration, can also surface management through site collection<br />Groups – Can have managers and contributors<br />Term Sets – User suggestions, user submissions<br />Term<br />Multilingual, Custom sort order, Change management<br />
    14. 14.
    15. 15.
    16. 16.
    17. 17.
    18. 18. Why We Needed It<br />Practical support for larger lists/libraries<br />Top down AND bottom up taxonomy approach<br />Social interaction with content<br />User suggestions<br />User submissions<br />Global management of the metadata<br />
    19. 19. Metadata Navigation<br />
    20. 20. What It Does<br />Provides an interface for navigating very large document libraries.<br />
    21. 21. How It Works - Demo<br />Two Types of Navigators<br />Metadata Navigator<br />Content Type, Single-valued Choice field, Managed Metadata Field<br />Filter Navigator<br />Content Type, choice Field, Managed Metadata Field, Person or Group Field, Date and Time Field, Number Field<br />
    22. 22.
    23. 23. Why We Needed It<br />Folders are not scalable (260 character limit, does not provide searchable metadata, etc)<br />New Boundaries<br />30 Million Items per List<br />5,000 Items per View<br />Users want list based searching that doesn’t require a crawl to run<br />Need to demonstrate value of metadata to users<br />
    24. 24. Content Type Hub<br />
    25. 25. What It Does<br />Publishes content types from a source site collection to a destination site collection<br />Keeps content types in sync using SharePoint timer jobs<br />
    26. 26. How It Works<br />Connected to the Managed Metadata Service<br />Configure the Hub URL<br />Turn on Content Type consumption<br />Timer Jobs<br />Content Type Hub<br />Content Type Subscriber<br />Content Types are marked for publishing<br />
    27. 27.
    28. 28.
    29. 29.
    30. 30. Why We Needed It<br />Management of content types is tough!<br />Easy to manage with feature deployed content types<br />Very hard to manage through the user interface<br />
    31. 31. Unattached Database Recovery<br />
    32. 32. What It Does<br />Three Modes<br />Backup Site Collection<br />Export Site<br />Export List<br />Can optionally export security and version information<br />
    33. 33. How It Works - Demo<br />Restore from backup to new database<br />Browse through central administration and export list<br />Import using PowerShell<br />Import-SPWeb<br />
    34. 34. Why We Needed It<br />Recycle bin is great for 99.7% of issues but what happens when a user deletes a list or a site?<br />Remove the requirement for a restore environment<br />Restoring content was cumbersome and slow<br />
    35. 35. New Object Models<br />
    36. 36. What It Does<br />Three new object model interfaces<br />.Net CLR (Windows forms, Console apps, etc)<br />Silverlight<br />Javascript<br />
    37. 37. How It Works - Examples<br />
    38. 38. 14ISAPI<br />Microsoft.SharePoint.Client.dll<br />Microsoft.SharePoint.Client.Runtime.dll<br />
    39. 39. 14TEMPLATELAYOUTSClientBin<br />Microsoft.SharePoint.Silverlight.dll<br />Microsoft.SharePoint.Sliverlight.Runtime.dll<br />
    40. 40. 14TEMPLATELAYOUTS<br />SP.js<br />
    41. 41. Why We Needed It<br />Build less custom web services on top of SharePoint<br />Richer, quicker to develop desktop / office integrated tools for working with SharePoint<br />Rapid development<br />Developers may not need SharePoint installed locally for specific kinds of development<br />
    42. 42. Save to SharePoint<br />
    43. 43. What It Does<br />Save To SharePoint<br />SharePoint Sites<br />Workspace Integration<br />Easy way to get documents into SharePoint rather than saving locally and performing an upload.<br />
    44. 44.
    45. 45.
    46. 46.
    47. 47.
    48. 48.
    49. 49. Why We Needed It<br />1 too many steps to get documents into SharePoint<br />Avoid the middle man<br />Easier to use drag and drop functionality from windows explorer<br />
    50. 50. Search Refinements<br />
    51. 51. What It Does<br />Refinements (Facets)<br />Automated list of refinements based on results<br />FAST Search<br />Document Previews<br />“Entity Extractors” – Pull data from external systems<br />
    52. 52.
    53. 53. Why We Needed It<br />Metadata more important with refinements<br />Provides the user with a more focused query for finding their documents faster<br />FAST<br />Entity extraction allows for metadata to be pulled from the document or from systems outside of SharePoint<br />Refinements are extensible<br />
    54. 54. In Place Record Management<br />
    55. 55. What It Does<br />“In Place” Records Management<br />Declare as Record<br />Single or Bulk<br />Multi Stage Retention Policies<br />Holds and Hold Exemption<br />eDiscovery<br />
    56. 56.
    57. 57.
    58. 58.
    59. 59. Why We Needed it<br />Easier for users to declare records<br />Records can expire in-place to simplify storage requirements<br />Better support for complex retention policies<br />Incremental expiration<br />Ex: After 1 year delete previous versions, after 7 years delete record<br />
    60. 60. Business Connectivity Services<br />
    61. 61. What It Does<br />Brings Line of Business data into SharePoint<br />Create Connections with SharePoint Designer<br />Full Read / Write / Update / Delete Support<br />Looks and Feels like a SharePoint List<br />InfoPath Integration<br />Offline Support<br />
    62. 62. How It Works - Demo<br />
    63. 63.
    64. 64.
    65. 65.
    66. 66. Why We Needed It<br />SharePoint truly becomes the “Portal” to your company provided views into every other systems data<br />Applications include surfacing information from<br />Matter Management System<br />Accounting System<br />Employee Database<br />CRM System<br />etc<br />
    67. 67. Upgrading<br />
    68. 68. Server Side Requirements<br />SharePoint Servers (WFE, Index, Query, etc)<br />Windows Server 2008 R2 x64<br />Windows Server 2008 SP2 x64<br />Database Servers<br />SQL Server 2005 SP3 + KB967909 x64<br />SQL Server 2008 SP1 + KB970315 x64<br />Development Environments<br />Supports Windows 7<br />
    69. 69. Hardware Requirements<br />
    70. 70. Client Side Requirements<br />Level 1 Browsers<br />IE7, IE8 32bit<br />Firefox 3.5 on Windows<br />Level 2 Browsers<br />IE7, IE8 64bit<br />Firefox 3.5 on Unix/Linux 8.1<br />Safari 4.x and Firefox 3.5 on OS X Snow Leopard<br />IE6 Not Supported!<br />
    71. 71. Preparing to Upgrade<br />Not Supported<br />Windows Server 2003<br />SQL 2000<br />Internet Explorer 6<br />Check Hardware Readiness<br />Check Software Versions<br />Browser Chaos<br />
    72. 72. Pre-upgrade Check<br />SP2 October 2009 CU<br />Preupgradecheck<br />Server info<br />Farm info<br />Upgrade types supported<br />Site templates, features, language packs, aamurls<br />OS<br />Database schema<br />Orphans<br />Invalid settings / missing files<br />
    73. 73. Questions?<br />Our Partners<br />Software Services for Customer Success<br />Stay Connected<br /><br />!/EastridgeTechnology<br /><br />