Published on

Presentation given for CASUG (Charlotte Area SharePoint User Group) Leveraging out-of-the-box functionality for SharePoint 2010 success.

Published in: Technology
1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Original Site Architecture
  • Sp2010success

    1. 1. Leveraging out-of-the-box tools to achieve SharePoint 2010 success<br />
    2. 2. About Me<br /><ul><li>Name: Steven Tisdale
    3. 3. Education: Florida State University, 2000
    4. 4. SharePoint Experience:</li></ul>Migrated SharePoint 2003 to Moss 2007<br />Administered MOSS 2007 since December 2007<br />Recently involved in MS BI Stack, executive dashboards<br /><ul><li>Website: http://everydaysharepoint.com
    5. 5. Twitter: @StevenTisdale</li></li></ul><li>Organization Info<br />Liberty Hardware - www.libertyhardware.com<br />Since 1942, Liberty Hardware Mfg. Corp. has built its reputation by offering high quality decorative and functional hardware products at an exceptional value. The company proudly offers its extensive line of hardware products through fine retail outlets and original equipment manufacturer (OEM) distribution channels across the country. <br />Users: 250-500<br />Frequency of Use: Daily<br />Verve Living Systems – www.vervelivingsystems.com<br />Verve Living Systems is a new brand within Masco Corporation, a leading manufacturer of consumer products for the home improvement and new home construction markets. <br />Users: 10-25<br />Frequency of Use: Daily<br />
    6. 6. Outline<br /><ul><li>Approach
    7. 7. Infrastructure
    8. 8. Security Architecture
    9. 9. Content Deployment
    10. 10. Request Ticketing System
    11. 11. Intranet Development
    12. 12. Site Architecture Redesign
    13. 13. Content Management
    14. 14. Design Elements
    15. 15. Lessons Learned</li></li></ul><li>Approach<br />Governance Is The Key<br />Identify Site/Content Owners<br />Identify Content<br />Site Champions<br />Support Path<br />80% Rally Cry<br />Out-of-the-box tools?<br />Rapid Application Development<br />Iterative Process<br />
    16. 16. INFRASTRUCTURE<br />Small Farm<br />Windows Server 2008 R2, 64 bit<br />Six-Core 2.8ghz (4 processors)<br />Installed Memory: 10gb<br />Virtualized Using VM Ware <br />Clustered SQL Server 2008<br />Two WFEs – one internal, one external<br />Two Application Servers – <br />CA/Query <br />Reporting Services, Excel Services, etc.<br />
    17. 17. Security Architecture<br />Security Centrally Managed Within IT - purpose, history, and use<br />Leverage Active Directory Groups<br />Per Site Collection Setup: <br />Admins – Site Champions and IT support<br />Owners – Contributor, Content Approval<br />Members – Contributor (same area/department)<br />Users – Contributors (from a different area/department)<br />Visitors – Restricted Read<br />
    18. 18. Content Deployment<br />Moving to Production<br />Schedule vs. Manual<br />Include security or leave it out?<br />Backup DBs<br />One way push<br />
    19. 19. Request Ticketing System<br /><ul><li>Work order system to replace paper process
    20. 20. Request driven workflow
    21. 21. Three day turnaround
    22. 22. No UI customizations
    23. 23. SharePoint Designer Workflows</li></li></ul><li>Application<br />One List – Requests<br />Multiple Views<br />Awaiting Approval<br />Awaiting Assignment<br />Completed Assignments<br />Due in next 7 Days<br />Past Due Requests<br />My Assignments<br />My Requests<br />Unassigned Requests<br />Pages<br />My Requests<br />My Assignments<br />Management Overview<br />Customized Entry Forms<br />Creative Brief<br />Request<br />Label<br />Translation<br />
    24. 24. Workflow<br />In addition to alerts<br />Created in SharePoint Designer<br />Request Submitted<br />Notification of Assignment<br />Status Change<br />
    25. 25. The site<br />
    26. 26. Intranet DEVELOPMENT<br /><ul><li>Replace the share drives
    27. 27. Allow external resources to access the system
    28. 28. Leverage parent news/announcement content
    29. 29. Ridiculously easy-to-use</li></li></ul><li>Proposed Intranet<br /><ul><li>6 Web Applications
    30. 30. Intranet Home, Project Team Site Portal, Search Center, Supplier Portal, Records Center, and Document Center
    31. 31. 12 Site Collections
    32. 32. Home, Projects, Search, Supplier, Legal, Documents, Brand, Marketing, Products, Research, Sales, and Supplier Portal</li></li></ul><li><ul><li>2 Web Applications
    33. 33. Content Type Hub (CTH), Intranet Home
    34. 34. 13 Site Collections
    35. 35. CTH, Home, Projects, Search, Supplier, Legal, Documents, Brand, Marketing, Products, Research, Sales, Engineering, and Operations</li></ul>Production Intranet<br />
    36. 36. Content Management<br /><ul><li>Every document belongs to a content type
    37. 37. Every content type has a parent type
    38. 38. Use a document template whenever possible
    39. 39. No hidden naming conventions, call it what it is
    40. 40. Each content type has 3-5 metadata fields
    41. 41. Metadata fields are required as much as possible with defaults specified for every field
    42. 42. Leverage the term store</li></li></ul><li>Content Type Hub<br /><ul><li>Central repository of content types, metadata, and document templates
    43. 43. Content types syndicated
    44. 44. 219 total content types</li></li></ul><li>Metadata<br />3-5 fields per content type<br />Required (when possible) with defaults for ease of use<br />
    45. 45. Terms<br />Term Store Management Tool:<br /><ul><li>Term - A word or phrase that can be associated with content
    46. 46. Managed Terms</li></ul>controlled term that can only be created by users that have been granted permissions<br /><ul><li>Managed Metadata</li></ul>Once terms in place use the new column type “Managed Metadata”<br /><ul><li>A step further than a site column
    47. 47. Consistent terms for the organization
    48. 48. No more reproducing lists across site collections</li></li></ul><li>Content Type Syndication<br /><ul><li>One Managed Metadata Service Application
    49. 49. One Term Store
    50. 50. Shared/Published Across farms (for us, Dev/Production)
    51. 51. One term store, always updated.
    52. 52. Steps involved:</li></ul>Create Managed Metadata service application<br />Setup Publishing for the Managed Metadata Service by establishing a trust relationship<br />Setup Application Discovery and Load Balancer Service Application permissions<br />Publish Managed Metadata Service<br />Add proxy to service connection group<br />Setup Managed Metadata Service permissions<br />Test if the Published Managed Metadata Service works in your farms.<br /><ul><li>How to setup a Managed Metadata Service and Content Syndication</li></li></ul><li>Branding & design elements<br /><ul><li>Microsoft invested in this UI, why change it?
    53. 53. Provide visual indicators to your current location
    54. 54. Don’t clutter up the page or your users will get lost
    55. 55. Even if your sites are not “connected” give the feel that they are.</li></li></ul><li>Moving Across Sites<br />
    56. 56. Breadcrumbs<br /><ul><li>Disable the “Up” button
    57. 57. Modify the Master Page to Enhance Breadcrumbs
    58. 58. Consistent breadcrumbs across any site collection</li></li></ul><li>Page Layout<br />
    59. 59. Lessons Learned<br /><ul><li>Engage your stakeholders regularly
    60. 60. Managed Metadata fields are better if you implement Office 2010
    61. 61. Centrally-managing security is more of a headache up-front, but later you might be glad you did it
    62. 62. Mass loading documents is a daunting task for end-users
    63. 63. Visual design elements and beauty photography work well outside the business walls, but not for an Intranet</li></li></ul><li>Thank You<br />Contact Steven:<br /><ul><li>Website: http://everydaysharepoint.com
    64. 64. Twitter: @StevenTisdale</li>