7 Tips for Managing a Successful Transition to SharePoint 2010


Published on

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

No notes for slide

7 Tips for Managing a Successful Transition to SharePoint 2010

  1. 1. 12/07/2011Successful SharePoint 7 Tips for Managing a Successful Transition to SharePoint 2010 presented by Dave Healey dhealey@chrysalisbts.com (206) 734-9414
  2. 2. Welcome Dave Healey Managing Partner, Chrysalis | BTS Dave has spent twenty years delivering Enterprise Information Management solutions to large and complex organizations and has built a number of successful technology solution companies. dhealey@chrysalisbts.com Eric Schubert Solutions Engineer, Tier 3 Eric has over 15 years of experience in the IT industry. He specializes in project planning, new environment sizing and architecture—and has scoped, architected, and performed hundreds of IT deployments on- premise and in the cloud. eric.schubert@tier3.com
  3. 3. Successful SharePointSHAREPOINT 2010INTRODUCTION 3
  4. 4. Architectural OverviewSharePoint 2010 SharePoint Server 2010 Client Applications SharePoint Service Applications Browsers Search Services Visio Services Project Web Access MS Office Clients Excel Services Access Services Web Application Managed Service Mobile Devices User Profiles Metadata Fast Search Service ISV Applications BCS PerformancePoint Third Party Services Forms Services Word Automation SharePoint Foundation Sandbox Workflow Solutions Content Collaboration 4
  5. 5. Key Elements and New Features SharePoint 2010Sites Content Communities Search Composites Insights• Collaboration • Approval • My Sites • Indexing • Access Services • PerformancePoint• Web Parts • IM Policy • People Profiles • Relevance • BCS • Analytics• Office Integration • Web Publishing • Presence • Metadata • Workflow • Excel Services• Workspace • Content • Targeting • Expertise • Forms Services • Web Rendering• Mobile Deployment • Social Search • Federation • Visio Services • Dashboards• Outlook Sync • Managed • Tags • Alerts • Sandboxed • Carts• Alerts Metadata • Ratings Solutions • Content Types • Wikis • Doc Conversion Core ServicesStorage Security Management Topology Site Model APIs• Repository • Rights/Roles • Admin UX • Configuration • Rendering • Fields/Forms• Metadata • Authentication • Delegation • Service Application • Templates • Web Services• Versioning • Rights Trimming • Provisioning Management • Navigation • Client Object• Backup • Monitoring • Feature Policy • Visual Blueprint Model • Powershell • Extranet • Features • Solutions Web Parts | Personalization | Master Pages | Provider Framework Database Services Workflow Services Operating System Services 5
  6. 6. Key Structural ElementsEnvironmental Overview• Server farm: The top-level element of a logical architecture design for SharePoint Server• Web application: An IIS Web site that is created and used by SharePoint Server 2010• Content database: Provides storage Web application content• Site collection: A set of web sites that have the same owner and share administration settings• Site: One or more related Web pages and other items (such as lists, libraries, and documents) that are hosted inside a site collection 6
  7. 7. Hardware RequirementsTip 1: Design The EnvironmentFor Web Servers, Application Servers and Single Server Installations:• Processor: 64-bit, four cores• RAM: 4 GB for developer or evaluation use• 8 GB for production use in a single server or multiple server farm• Hard disk: 80 GB for system driveFor Database Servers:• Processor: 64-bit, four cores for small deployments• 64-bit, eight cores for medium deployments• RAM: 8 GB for small deployments 16 GB for medium deployments >16 GB for large deployments• Hard disk: 80 GB for system drive Hard disk space is dependent on the size of the SharePoint content 7
  8. 8. Software RequirementsTip 1: Design The EnvironmentEnvironment Minimum RequirementDatabase server One of the following:in a Farm • The 64-bit edition of Microsoft SQL Server 2008 R2 • The 64-bit edition of Microsoft SQL Server 2008 with Service Pack 1 (SP1) and Cumulative Update 2 • The 64-bit edition of Microsoft SQL Server 2005 with Service Pack 3 (SP3)Single server with • The 64-bit edition of Windows Server 2008 Standard, Enterprise, Databuilt-in database Center, or Web Server with SP2, or the 64-bit edition of Windows Server 2008 R2 Standard, Enterprise, Data Center, or Web ServerFront-end web • The 64-bit edition of Windows Server 2008 Standard, Enterprise, Dataservers and Center, or Web Server with SP2, or the 64-bit edition of Windowsapplication Server 2008 R2 Standard, Enterprise, Data Center, or Web Serverserver in a farmClient computer • A supported browser 8
  9. 9. Deployment ScenariosTip 1: Design The EnvironmentScenario DescriptionSingle server with • A single server farmSQL Server • Evaluation, team, departmental applicationSingle server with • A single server with a built-in databasea built-in • Evaluating SharePoint Server 2010database • Small number of sites and you want to minimize overheadMultiple servers • Two front-end Web servers, an application server, and afor a three-tier database serverfarm • A foundation for more complex farmsSingle server in an • Test the features and behavior of SharePoint Server 2010isolated virtual • Minimal hardware resourcesenvironment • Isolates test system from production environmentDeploy in a virtual Configuration impacts performance / functionalityenvironment • Virtual networking • Each virtual machine • Interaction with virtualization host • Stop and restart behavior 9
  10. 10. Upgrade OptionsTip 2: Determine Upgrade ApproachApproach DescriptionIn-place upgrade • Same hardware as previous version • Upgrades the complete installation in a fixed orderDatabase attach • Move to new hardware or a new farmupgrade • All content databases are detached from existing farm and then attached to the new server farm • The upgrade process then runs and upgrades the data in placeHybrid • Enables continuous read-only access to data whileapproach 1: upgrade is in progressRead-only • Databases in original farm are set to read-only and copies ofdatabases the databases are upgraded on the new farmHybrid • In-place upgrade facilitates multiple databaseapproach 2: upgrades at the same timeDetach databases • Optionally another farm can be used to perform the upgrade and then attach the upgraded databases to the original farm • Original farm cannot serve requests during the upgrade process 10
  11. 11. Pros and ConsTip 2: Determine Upgrade ApproachApproach Pros ConsIn-place • Farm-wide settings • Servers and farms are offlineupgrade are upgraded • Enough time must be allocated • Customizations are available for all content to be upgraded in in the environment after the sequence upgradeDatabase • Faster upgrade times overall • Farm settings are not upgradedattach than an in-place upgrade • Copying databases over aupgrade • Multiple farms can be network takes time and combined into one farm bandwidth • Requires direct access to the database server 11
  12. 12. Considerations for Services UpgradeTip 2: Determine Upgrade Approach In SharePoint Server 2010, many services that stored data in the SSP database have their own databases — in some cases, several databases. When you enable new services, new databases are also created to store the data for those services. 12
  13. 13. Considerations for Specific ServicesTip 2: Determine Upgrade ApproachService DescriptionProfiles • Two services now used for user profiles and taxonomy information: User Profile service, Managed Metadata serviceMy Sites • Upgrade the My Site host at the same time that you upgrade the profile services. You do not need to upgrade the My Sites themselves at the same time. • For best results, upgrade My Sites (or at least the My Site host) at the same time as your main intranet site.Search • Search service now uses three databases • Cannot upgrade Search data by using the database attach • Must configure Search in new farm either before or after upgrading other contentForms • If using database attach export any administrator-deployed form templates (XSN files) and data connection files (UDCX files) before migrating, then import them to the new farm after migrating. 13
  14. 14. Considerations for Specific ServicesTip 2: Determine Upgrade ApproachService DescriptionExcel Services • For in-place upgrade, any configuration information stored in the SSP database for Excel Services is upgraded and moved into the configuration database. • For the database attach upgrade approach, reconfigure Excel Services in the new farmBusiness Data • In-place upgrade, data that was stored in the SSP database isCatalog moved and upgraded to a separate database • The Business Data Catalog is not upgraded when using the database attach upgrade approachSingle Sign-On • The Single Sign-On (SSO) service is being replaced with the Secure Store Service in SharePoint Server 2010. Upgrade application definitions from SSO to the Secure Store Service, use Windows PowerShell cmdlets • Passwords are not upgraded 14
  15. 15. Governance Tip 3: Managing the Tension Between Empowerment and Control A Governance Plan helps Individual and team roles and responsibilities People • reduce cost of ownership, • ensure consistency, and How to accomplish common • deliver service standards tasks such as creating a new Processsite or requesting new services by aligning people, process, technology, and policy, Leveraging technology Technology and thereby resolving ambiguity features to enforce policies and mitigating potential for conflict within the organization. Principles and practicesguiding what site stakeholders Policy should and shouldn’t do
  16. 16. Content Management PlanTip 4: A Planned Approach to Managing The Information Lifecycle Managed Find and content share lifecycle information Content Strategy Legal & Optimize compliance business requirements processes A well defined Content Plan forms the foundation of an organizations information management strategy and helps facilitate user adoption, support knowledge development and optimize and resource utilization.
  17. 17. User Adoption Plan Tip 5: Effective Change Management Communicate • Long term success depends on active engagement from key stakeholders across the organization • Engage key audiences early to build Tools People buy-in, investment and ownership Best Practice: Process • Develop Adoption Plan • Engage key audiences and users early, during Phase 0:, Discovery and throughout the projectTraining Gather Feedback 17
  18. 18. Process Optimization Tip 6: Understand and Employ SharePoint Advanced Capabilities to Enhance the BusinessPerformance Business Value Approach Maturity Rudimentary Established Effective Adaptive SharePoint Pre-Deployment Initial Deployment Broad Adoption Business Solutions Adoption Business • Inconsistent Teaming • Productivity Gains • Broaden Adoption • Insight In-Context Value • Ad-hoc Collaboration • Effective Teaming • Drive Compliance • Improved • Informal, Inefficient • Lightweight • Reduce multiple system Decision Making Processes Project Management maintenance costs • Increased Agility • Significant IP & Legal Risk • File shares • Team Collaboration • Content Management • Integration Key • Email • Document Management • Social Computing • Composite and Capabilities • USB Drive • Search • Enterprise-Class Search Industry Applications • Cloud shares • Business Intelligence 18
  19. 19. SharePoint and The CloudTip 7: Consider Your Deployment Options Technology • Elasticity Business • Flexibility • Agility • Automation • Improved cost structure • Mobility Team • Focus on innovation Considerations and creating new value • Security • Reduce time to market • Privacy • Access • Compliance 19
  21. 21. Business and IT Leaders Say Cloud Enables Agility • 80%+ associate business agility with revenue growth, cost reduction, and risk management • 63% agree cloud can have a significant impact in making business more agile and responsive • Companies with enterprise-wide cloud deployments are 3x more likely to achieve business agility that is “much better than competition” SOURCE: Global Business Agility Survey, February 2011
  22. 22. Enterprise Hybrid Cloud: Solving the IT Dilemma Internal IT Hybrid Cloud Control Agility Has full control over Respond quickly to the environment Wants Agility demands Secure Cost Needs Control Known security, Transparent andpredictable performance controllable costs Leverage ElasticityInvestment in technology, Scalable Capacity people and process
  23. 23. Application Performance Matters MARKET CHALLENGEBUSINESS CRITICALITY Delivering application performance to meet customer expectations IMPACT Right performance for each application Best Effort Priority Real-Time Proximity Higher user satisfaction >100ms <100ms < 50ms < 5ms >2000km < 2000km < 500km < 50km Increased adoption, customer loyalty, and LATENCY SENSITIVITY revenue Performance matters for end user experience
  24. 24. SharePoint Migration: Getting Started Assess your existing situation: infrastructure, licensing, staffing Consider which of your apps could leverage unique cloud capabilities Assess your security requirements to understand implications Plan migration to minimize impact/downtime—practice good change management
  25. 25. Enterprise Cloud Provider ChecklistAvailability  Five 9s SLA covering servers, network and storagePerformance  Unique virtualization tech delivering comparable to on-premise performance for apps (not 20% less)  Automated, predictive optimization and hypervisor auto-tuningSecurity  Secure, multi-tenant architecture that segregates data  SAS 70 Type II audited, HIPAA and PCI compliant, SSAE16 cert underway  Secure connection (point-to-point or client VPN, direct connection)  Strong physical security policies for data centersBusiness  Disaster recovery built-in: automated 14-day backups replicated toContinuity geographically diverse datacentersControl  Choice of API or control panel enables you to control every server instance  Immediate, automatic monitoring of all resources and predictive cost estimatesSupport  Dedicated level 3 engineers on call 24/7Flexibility/Cost  Charged for resources (CPU, memory, storage) allocated by the hour
  26. 26. Tier 3: An Enterprise Cloud InnovatorTime-tested TechnologyContinuously innovating on five yearsof unique IP in enterprise virtualizationProven Results>100 enterprises trust their missioncritical apps, sites and developmentenvironments to our cloudZone FootprintThree zones across the Americas by Q4
  27. 27. Chrysalis BTS: Delivering Impact 27
  28. 28. presented by Dave Healeydhealey@chrysalisbts.com (206) 734-9414 28