Your SlideShare is downloading. ×



Published on

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

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

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

No notes for slide
  • Original Site Architecture
  • Transcript

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