The document details Steven Tisdale's expertise in utilizing SharePoint 2010, including information on his background, organizational affiliations, and approach to SharePoint governance and infrastructure. Key points cover the architecture, content management, and deployment strategies, emphasizing automation, centralized security, and effective metadata management. Lessons learned highlight the importance of stakeholder engagement and the challenges of document management in SharePoint environments.

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

2. About MeName: Steven Tisdale

3. Education: Florida State University, 2000

4. SharePoint Experience:Migrated SharePoint 2003 to Moss 2007Administered MOSS 2007 since December 2007Recently involved in MS BI Stack, executive dashboardsWebsite: http://everydaysharepoint.com

5. Twitter: @StevenTisdaleOrganization InfoLiberty Hardware - www.libertyhardware.comSince 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-500Frequency of Use: DailyVerve Living Systems – www.vervelivingsystems.comVerve 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-25Frequency of Use: Daily

6. OutlineApproach

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 LearnedApproachGovernance Is The KeyIdentify Site/Content OwnersIdentify ContentSite ChampionsSupport Path80% Rally CryOut-of-the-box tools?Rapid Application DevelopmentIterative Process

16. INFRASTRUCTURESmall FarmWindows Server 2008 R2, 64 bitSix-Core 2.8ghz (4 processors)Installed Memory: 10gbVirtualized Using VM Ware Clustered SQL Server 2008Two WFEs – one internal, one externalTwo Application Servers – CA/Query Reporting Services, Excel Services, etc.

17. Security ArchitectureSecurity Centrally Managed Within IT - purpose, history, and useLeverage Active Directory GroupsPer Site Collection Setup: Admins – Site Champions and IT supportOwners – Contributor, Content ApprovalMembers – Contributor (same area/department)Users – Contributors (from a different area/department)Visitors – Restricted Read

18. Content DeploymentMoving to ProductionSchedule vs. ManualInclude security or leave it out?Backup DBsOne way push

19. Request Ticketing SystemWork order system to replace paper process

20. Request driven workflow

21. Three day turnaround

22. No UI customizations

23. SharePoint Designer WorkflowsApplicationOne List – RequestsMultiple ViewsAwaiting ApprovalAwaiting AssignmentCompleted AssignmentsDue in next 7 DaysPast Due RequestsMy AssignmentsMy RequestsUnassigned RequestsPagesMy RequestsMy AssignmentsManagement OverviewCustomized Entry FormsCreative BriefRequestLabelTranslation

24. WorkflowIn addition to alertsCreated in SharePoint DesignerRequest SubmittedNotification of AssignmentStatus Change

25. The site

26. Intranet DEVELOPMENTReplace the share drives

27. Allow external resources to access the system

28. Leverage parent news/announcement content

29. Ridiculously easy-to-useProposed Intranet6 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 Portal2 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 OperationsProduction Intranet

36. Content ManagementEvery 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 storeContent Type HubCentral repository of content types, metadata, and document templates

43. Content types syndicated

44. 219 total content typesMetadata3-5 fields per content typeRequired (when possible) with defaults for ease of use

45. TermsTerm Store Management Tool:Term - A word or phrase that can be associated with content

46. Managed Termscontrolled term that can only be created by users that have been granted permissionsManaged MetadataOnce 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 collectionsContent Type SyndicationOne 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 applicationSetup Publishing for the Managed Metadata Service by establishing a trust relationshipSetup Application Discovery and Load Balancer Service Application permissionsPublish Managed Metadata ServiceAdd proxy to service connection groupSetup Managed Metadata Service permissionsTest if the Published Managed Metadata Service works in your farms.How to setup a Managed Metadata Service and Content SyndicationBranding & design elementsMicrosoft 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. BreadcrumbsDisable the “Up” button

57. Modify the Master Page to Enhance Breadcrumbs

58. Consistent breadcrumbs across any site collectionPage Layout

59. Lessons LearnedEngage 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 IntranetThank YouContact Steven:Website: http://everydaysharepoint.com

64. Twitter: @StevenTisdale