SharePoint 2010 design and deploy


Published on

The webinar will include several demonstrations and discuss:

The pros and cons of the different approaches to installing and configuring SharePoint 2010
Configuration Best Practices for SharePoint 2010 farms
The Services Architecture; dependencies, licensing and topologies
Information Architecture guidance for sizing, multilingual support, multi-tenancy, etc.
Using tools such as SharePoint Composer & SharePoint Maestro to plan, document, install and configure a SharePoint 2010 deployment
Avoiding common pitfalls

Published in: Technology
  • Be the first to comment

SharePoint 2010 design and deploy

  1. 1. SharePoint 2010 Design & Deployment <br />Best Practices<br />Webinar Series By:<br />
  2. 2. Speakers<br />Gary Lapointe<br />SharePoint MVP <br />Sr. Architect & Lead Consultant<br />Paul Papanek Stork<br />SharePoint MVP & Author <br />Sr. Architect & Lead Consultant<br />MBA, MCT, MCSE, MCSD, MCDBA, MCITP, MCPD…<br />
  3. 3. Agenda<br />A sprinkling of demos throughout…<br />Installation and Configuration Approaches<br />New Services Architecture<br />Information Architecture Considerations<br />SharePoint Composer & SharePoint Maestro<br />Best Practices/Avoiding Common Pitfalls<br />Q&A<br />
  4. 4. Installation and Configuration<br />Point-and-Click Deployments<br />SharePoint Configuration Wizard<br />Farm Configuration Wizard<br />LOTS of Central Admin Work<br />Scripted Deployments<br />PowerShell<br />STSADM/PSConfig<br />Object Model<br />
  5. 5. SharePoint Configuration Wizard (SCW)<br />Automatically launched<br />UI for PSConfig<br />Makes some assumptions<br />Central Admin DB Name<br />Central Admin installed on first server<br />
  6. 6. Farm Configuration Wizard (FCW)<br />Default Installation Path<br />Makes assumptions similar to SCW<br />DB Names<br />Managed Service Accounts<br />Application Pools<br />Great for quick install<br />Not best for Production<br />Too many services<br />Too many assumptions<br />
  7. 7. Central Admin Configurations<br />Provides complete control<br />Very time consuming<br />Can’t be replicated<br />
  8. 8. Using Wizards and the Ribbon<br />
  9. 9. Audience Survey<br />What is your primary role in Design and Deployment of SharePoint 2010 at your organization?<br />Decision Maker, Influencer or Sponsor<br />Admin or Architect<br />Analyst or End User<br />Consultant<br />
  10. 10. PowerShell<br />Repeatable/Predictabledeployments<br />Fine grained control ofall settings<br />High level of complexity<br />Extensible<br />Lots of Community Support<br />Script Repository:<br />
  11. 11. STSADM/PSConfig<br />Deprecated but still occasionally required<br />Compared to PowerShell<br />Less complex<br />Less granular<br />May be used inside PowerShell scripts<br />Extensible<br />Lots of Community Support<br />
  12. 12. Object Model (OM)<br />Some settings only available in the OM<br />Two ways to use the OM<br />PowerShell scripts<br />Custom Applications<br />Examples in the SharePoint Developer Center:<br />
  13. 13. Using Scripts and the Object Model<br />
  14. 14. Service Applications Architecture<br />Replaces Shared Service Providers (SSP’s)<br />New deployment considerations<br />What are the advantages over SSP’s?<br />What does each Service App do?<br />Which SharePoint edition do I need?<br />Which Service Apps depend on others?<br />How big do the databases normally get?<br />Charts available after Webinar<br />Service Apps per SharePoint Edition <br />Service App Dependencies<br />Service App Database planning considerations<br />
  15. 15. Service Application Components<br />Service Applications components<br />Service Instance<br />Service Machine Instance<br />Service Application Endpoint<br />Service Application<br />Service Connection (aka Service App Proxy)<br />Consumers<br />
  16. 16. Information Architecture<br />New Information Architecture Considerations<br />Considerations Include (but not limited to):<br />Sizing (Large List Support)<br />Multilingual Sites and Variations<br />Multi-Tenancy<br />
  17. 17. Sizing Considerations<br />Determine which Service Apps you need<br />Evaluate using Remote Blob Storage in heavy ECM environments<br />Avoid Content Databases over 200GB for Collaborative sites<br />Review Case Studies similar to your environment<br />Know your service level requirements<br />Model your environment during planning<br />
  18. 18. Multilingual UI Considerations<br />MUI Provides a Simple Alternative to Variations (chrome only)<br />Can easily bolt on afterwards with minimal to no impact, unlike Variations<br />Central Admin is fully MUI aware!<br />Content that is not resource file driven will still be in the source language<br />Use Variations to support translations of non-resourced content<br />Managed Metadata Terms can have Alternate Languages<br />
  19. 19. Multi-Tenancy Considerations<br />Multi-Tenancy Supports Hosted Scenarios<br />Traditional Hosting and Charge-back Scenarios<br />Multi-Tenancy Provides Isolation<br />Data (including reporting and auditing)<br />Customizations<br />Usage (including features and charge-backs)<br />Administration<br />Site Subscriptions Associate Site Collections with Tenants<br />Share Settings, Features, and Service Data<br />Feature Packs Group Features for Tenants <br />
  20. 20. Audience Survey<br />Where is your organization on the SharePoint 2010 Design & Deployment curve?<br />Already deploying SharePoint 2010<br />In the planning and design phase<br />Will install/upgrade once SP2010 has been out awhile (e.g. after the first service pack)<br />Unsure – need more information<br />No plans to move to 2010 at this time<br />
  21. 21. SharePoint Composer<br />Visually Design 2007 & 2010 Farms<br />Import & Document existing installations<br />Validate Designs Prior to deployment<br />Great Planning Tool<br />Holistic view of SharePoint<br />Enhances collaboration<br />GreatAudit Tool<br />Auditors, consultants, etc., can audit a farm config<br />Best Practices Advice<br />
  22. 22. Using SharePoint Composer<br />
  23. 23. SharePoint Maestro<br />Build a farm using the XML created by Composer<br />Leverage the power of PowerShell without knowing PowerShell<br />Repeatable build process <br />(Dev, QA, Staging, Prod)<br />Replaces SCW, FCW, and Point-and-Click configs<br />Crawl existing 2007 farms<br />
  24. 24. Using SharePoint Maestro<br />
  25. 25. Common Pitfalls<br />Underestimating the complexity of PowerShell<br />TEST, TEST, TEST!!!<br />Problems configuring some Service Apps with PowerShell<br />User Profile Service Application<br />Managed Metadata Service Application<br />Order of execution & dependencies<br />Using the Farm Configuration Wizard for Production<br />Not all Site Templates support MUI<br />Multi-Tenancy as an afterthought will result in migration issues & data loss<br />
  26. 26. Best Practices<br />Carefully design and document your SharePoint implementation<br />Validate your design for adherence to best practices<br />Start only the Service Applications you need<br />Understand SharePoint’s boundaries and limits<br />Boundaries – Absolute values not to exceed<br />Thresholds/Limits – Configurable values <br />Use PowerShell or SharePoint Composer and Maestro for large deployments<br />Establish a performance baseline and maintain periodic performance measurements<br />
  27. 27. Audience Survey<br />What do you see as next steps?<br />Assess& Document current SharePoint environment <br />Design a SharePoint 2010 implementation<br />Learn more about SharePoint 2010<br />Deploy SharePoint 2010<br />
  28. 28. Resources and Q & A<br />Assessment, Planning & Implementation<br />Get the free community version of Composer<br />Schedule a SharePoint GamePLAN engagement<br />Contact us for guidance or assistance with SP2010<br />Learn more about SharePoint 2010<br />Next Webinar: Business Application Integration using SharePoint 2010’s Business Connectivity Services<br />Online resources<br />Gary Lapointe’s Blog:<br />Composer Site:<br />Contact<br /><br />800-445-1279 - Option 2<br />