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

1. Leveraging out-of-the-box tools to achieve SharePoint 2010 success

3. Education: Florida State University, 2000

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

16. INFRASTRUCTURE 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 – CA/Query 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

20. Request driven workflow

21. Three day turnaround

22. No UI customizations

24. Workflow In addition to alerts Created in SharePoint Designer Request Submitted Notification of Assignment Status Change

25. The site

27. Allow external resources to access the system

28. Leverage parent news/announcement content

30. Intranet Home, Project Team Site Portal, Search Center, Supplier Portal, Records Center, and Document Center

31. 12 Site Collections

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 OperationsProduction Intranet

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

43. Content types syndicated

47. Consistent terms for the organization

49. One Term Store

50. Shared/Published Across farms (for us, Dev/Production)

51. One term store, always updated.

53. Provide visual indicators to your current location

54. Don’t clutter up the page or your users will get lost

57. Modify the Master Page to Enhance Breadcrumbs

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

64. Twitter: @StevenTisdale