Downloaded 479 times
![Logical design of SharePointFarmWeb ApplicationService ApplicationZoneContent DBSite collectionTop-level siteList/LibrarySub siteSub site[Folder]Item / Document](https://image.slidesharecdn.com/guidingasuccessfulsharepointimplementation-110824230051-phpapp01/85/Guiding-a-Successful-SharePoint-Implementation-34-320.jpg)
![Storage Capacity PlanningContent databasesDocuments x Versions x Average Size = data size10KB x [List Items + (Docs x Versions)] = Metadata sizeDB Size = data size + metadata size + logIn general, max size should be kept under 200GBIndex space requiredSize of Content DB(s) indexed * 0.035 = Index sizeIndex size * 4 = Disk Space RequiredSpread across crawl db, property db, and file system](https://image.slidesharecdn.com/guidingasuccessfulsharepointimplementation-110824230051-phpapp01/85/Guiding-a-Successful-SharePoint-Implementation-46-320.jpg)
![Logical design of SharePointFarmWeb ApplicationService ApplicationZoneContent DBSite collectionTop-level siteList/LibrarySub siteSub site[Folder]Item / Document](https://image.slidesharecdn.com/guidingasuccessfulsharepointimplementation-110824230051-phpapp01/75/Guiding-a-Successful-SharePoint-Implementation-34-2048.jpg)
![Storage Capacity PlanningContent databasesDocuments x Versions x Average Size = data size10KB x [List Items + (Docs x Versions)] = Metadata sizeDB Size = data size + metadata size + logIn general, max size should be kept under 200GBIndex space requiredSize of Content DB(s) indexed * 0.035 = Index sizeIndex size * 4 = Disk Space RequiredSpread across crawl db, property db, and file system](https://image.slidesharecdn.com/guidingasuccessfulsharepointimplementation-110824230051-phpapp01/75/Guiding-a-Successful-SharePoint-Implementation-46-2048.jpg)
Uploaded byRandy Williams
Guiding a Successful SharePoint Implementation
The document provides a detailed agenda and overview for successfully implementing SharePoint, outlining the importance of planning, governance, and addressing user requirements. It highlights common challenges, the need for executive sponsorship, and strategies for scaling SharePoint within organizations. Additionally, it discusses training recommendations and the features of Office 365, offering insights into cost comparisons and infrastructure considerations.
More Related Content
Similar to Guiding a Successful SharePoint Implementation
More from Randy Williams
Guiding a Successful SharePoint Implementation
- 1. Guiding a successfulSharePoint implementationRandy WilliamsEnterprise Trainer & Evangelistrandy.williams@avepoint.comTwitter: @tweetraw© 2011 AvePoint, Inc. All rights reserved. No part of this may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, without the prior written consent of AvePoint, Inc.
- 2. About your speaker20years in ITdeveloper, consultant, trainer, authorAt AvePointEvangelist, ArchitectThree-time SharePoint MVPLived in Singapore in 2009-2010Currently based in San Diego, California
- 3. Today’s agendaPart 1(2:00 - 3:10)Introduction & OverviewThe Need to PlanDefining the Business SolutionGovernanceQ&A / Break / Social (3:10 - 3:30)Part 2 (3:30 - 4:40)Architecting the solutionOffice 365Addressing training requirementsClosing Remarks / Q&A / Social (4:40 - 5:00)
- 4. Challenges deploying SharePointIt’sa business solutionDelivering ROICultural changesManaging the adoption balanceIt’s a complex product!Integration into existing systemsEnhancing the productDelivering effective governance
- 5. The need toplan
- 6. Yes, you reallyneed a planIt’s still a projectSharePoint is one of the trickiest types of projectsMany stakeholdersMarriage of business and technologyNumerous dependenciesPlan and execute iterativelyBe sure to get executive sponsorship from the beginning
- 7. How can SharePointFail?Lack of growth planningLack of governance modelLack of governance boardLack of executive sponsorshipLack of operational planningLack of provisioning governanceLack of strategyLack of user analysisLack of infrastructure planningLack of information architectureLack of change management
- 8.
- 9. What are yourbusiness goals?Identify pain points and opportunitiesDo not assume SharePoint is the solutionDescribe the solution without technology“I need a database that …”“I want a web site to …”Do the goals align with strategic plan?Avoid getting too deep into the weedsPrioritize
- 10. User PersonasBecause userswon’t just “figure it out”Identify specific use cases that SharePoint can addressValidates SharePoint as a solutionUsed to “sell” SharePoint to the businessHelps calculate ROIInput into governance, testing, and training How? http://www.hceye.org/HCInsight-Nielsen.htm
- 11. Organizing all requirementsProjectRequirements
- 12. Addressing the gapWhatabout requirements that cannot be met by SharePoint?Is SharePoint the right solution?Build or buy?Rich SharePoint ISV ecosystemWorkflowBackup/RecoveryRecords management/complianceStorage optimizationImproved social featuresEnforce governance
- 13. Design and delivergovernance
- 14. Governance is theset of policies, roles, responsibilities, and processes that guides, directs, and controls how an organization's business divisions and IT teams cooperate to achieve business goals. Microsoft - http://bit.ly/nmNSbjWhat is governance?
- 15.
- 16.
- 17.
- 18.
- 19.
- 20.
- 21.
- 22.
- 23.
- 24.
- 25.
- 26. WITH GREAT POWERTHERE MUST ALSO COME - - GREAT RESPONSIBILITY!
- 28.
- 29.
- 30.
- 31. Technical governanceDefine YourRequirementsAlign Management Requirements with Controls and ScopesAlign Business Requirements with Controls, Features and ScopesOverlay Information Architecture and Manageability
- 32. Ready for abreak?Q&A
- 33.
- 34. Logical design ofSharePointFarmWeb ApplicationService ApplicationZoneContent DBSite collectionTop-level siteList/LibrarySub siteSub site[Folder]Item / Document
- 35. Server rolesWeb frontend (WFE)IIS server that receives all direct HTTP requests from usersApplication serverRuns service applications, such as Search, MMS, othersAlso based on IISUses WCF for communicationDatabase server (SQL Server)Configuration databaseContent databasesApplication service databases
- 36. Scaling web frontendVery scalable role using load balancingActive/active designCan use either NLB (built into Windows) or hardware load balancerIn general 4 WFE per database server1 WFE can support thousands of users
- 37. Scaling application serverVeryscalable using SharePointActive/active designLoad balancing is built into SharePoint – no external configuration neededPay special attention to search (query and crawl)
- 38. Scaling database serverAddmultiple database serversClustering is an active/passive design only a high availability solutionKeep database servers dedicatedVirtualization okay – but small performance hitUse high-quality SAN storage for best performanceOptimizing SQL Server for SharePoint http://slidesha.re/ialfZc
- 39. How can Idecide where/how to distribute services across my farm?Answer: Perform adequate testing to determine the right topology based on your requirements and budget
- 40. Single server farmAllroles on one machineOnly advised for development or test environmentsNo fault toleranceAlso known as a standalone farm – cannot be scaled out
- 41. Two server farmVerycommon for small to some medium-sized organizationsIn general, can support up to 2000 usersFarm can be scaled across all roles to as large as neededNo fault tolerance
- 42. Three server farmEachserver has its own roleUsually used with heavier search componentAll application services are on application server except queryNo fault tolerance
- 43. Small high-availability farmFourserver farm with all roles redundantDatabase server can either beclustered or mirrored
- 44. Medium server farmComesin many flavors and sizesScale each role as neededDelivers high availability and scalability
- 45. Large farmYes, SharePointis uber scalable
- 46. Storage Capacity PlanningContentdatabasesDocuments x Versions x Average Size = data size10KB x [List Items + (Docs x Versions)] = Metadata sizeDB Size = data size + metadata size + logIn general, max size should be kept under 200GBIndex space requiredSize of Content DB(s) indexed * 0.035 = Index sizeIndex size * 4 = Disk Space RequiredSpread across crawl db, property db, and file system
- 47. Remote BLOB Storage(RBS)Store documents outside of content databaseSave on storage costsBest in file-heavy, read-centric environmentsBest for larger files (on average >1MB)Built in RBS support with SQL Server 2008 R2 (FILESTREAM provider)Not advised for production – use third partyPerformance tests show 25% reduction in average response time *However, it does complicate recovery
- 48. AuthenticationSharePoint supports twomodesClassicSame as with SharePoint 2007Works with all forms of Windows authenticationEasiest to configureCommon with intranetsClaims based authenticationNew in SharePoint 2010Supports custom providersMust be used if you want forms-based auth (FBA)
- 49.
- 50. What’s in theBox?http://office365.microsoft.com/
- 51. Microsoft’s Promise99.9% uptimeCertifiedMultipledatacentersGeo-redundantShorter release cycleshttp://www.microsoft.com/en-us/cloud/cloudpowersolutions/productivity.aspx?fbid=yk9RvqroDcr
- 52. Data Centers$2.3B+ investment– geo redundant - environmentally sustainable
- 53. Missing Features TodayBusinessConnectivity ServicesFAST SearchPerformance Point ServicesProject ServerPower PivotSecure Store ServiceLimited device supportFull Trust Solutions
- 54. Latest Costs (peruser/per month)Professional and Small Business(less than 50 users)P$6 – Exchange, Lync, SharePoint, Office Web AppsEnterpriseE1 $10 – Exchange, Lync, SharePointE2 $16 – E1 + Office Web AppsE3$24 – E2 + Office Pro Plus, Excel/InfoPath/Visio/Access ServicesE4 $27 – E3 + voice capabilitieshttp://www.microsoft.com/en-us/office365/enterprise/subscription-plans.aspx
- 55. SharePoint 2010 EnterpriseLync2010Exchange 2010 Office 2010 ProfessionalSample Comparison100 usersOn-premisesOffice 365 E3$28,800 1st year$28,000 2nd year$28,000 3rd yearInfrastructure: Network, Servers, Administrator
- 56. Software: Windows Server2008 R2, SQL Server 2008 R2, SharePoint Server 2010, Office 2010 Professional…Cost?
- 57. To learn moreabout Office 365Webcast recorded on 2 Aug 2011Download from http://www.avepoint.com/sharepointuncensored
- 58. How to addresstraining
- 59. RecommendationsUsers will not“figure it out”Training should not be product-centricTask-oriented focus on use cases and governanceremember user personas?Identify one or two champions in each business unitTrain the trainerAlso works well for tier-1 supportPower users/site collection admins get additional training
- 60.
- 61. Register today andlearn about these exciting topics:Office 365: Does it Work in a Leap Year?
- 62. To BLOB orNot to Blob? Storage Optimization Demystified
- 63. Without Boundaries: Building SharePoint for Real Global Collaboration
- 64. Application Lifecycle Management: A Cautionary Tale
- 65. The Truth BehindSharePoint Recovery and Availability: Meeting you SLAs
- 66. Automating and ProvisioningChange ManagementOr visit www.avepoint.com for more information
- 67.
- 68.
- 69. © 2011 AvePoint,Inc. All rights reserved. No part of this may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, without the prior written consent of AvePoint, Inc.