1 / 36

Pitfalls of Migrating to SharePoint 2010

Pitfalls of Migrating to SharePoint 2010. Scott Hoag & Dan Usher. Who are we?. Scott Hoag Recently picked up off waivers Jack of All Trades, Master of Some

terris
Download Presentation

Pitfalls of Migrating to SharePoint 2010

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Pitfalls of Migrating to SharePoint 2010 Scott Hoag & Dan Usher

  2. Who are we? • Scott Hoag • Recently picked up off waivers • Jack of All Trades, Master of Some • With over 8 years of experience, Scott has been utilizing Microsoft based content management solutions from MCMS 2002 to SharePoint 2010 today • Enjoys discussions about user adoption, search, and world peace • Recently began consuming (green) vegetables • Twitter: @ciphertxt

  3. Who are we? • Dan Usher • SharePoint Architect and Implementation Engineer, Principal Button Clicker, and Service Monkey • 7 years of experience with SharePoint going back to adventures with STS 2001 and SPS 2003 to the present… • Enjoys discussions about Claims AuthZ, SmartCardAuthN, Atomic Molecular Optics & the Walking Dead • Follows the SharePoint Credo -ADIDASAll Day IDream About SharePoint • Twitter: @usher

  4. …and what about this guy?

  5. What about you all? How much does your service monkey know about SharePoint migrations? Right now, not much… Ask me again in an hour…

  6. Warning!!! Warning!!! Warning!!!

  7. Smithers, fetch my agenda. • Migration vs. Upgrade • 3rd Party Tools vs. OOTB Methods • Consolidation Considerations • Content Assessments • User Adoption • User Experience and Training • AuthN Changes • Entropy vs. Order

  8. Migration vs. Upgrade • Data migration is the process of transferring data between storage types, formats, or computer systems. 1 • System migration involves moving a set of instructions or programsfrom one platform to another, minimizing re-engineering. 2 • Migration of systems can also involve downtime, while the old system is replaced with a new one. • The term upgrade refers to the replacement of a product with a newer version of the same product. 3 1 http://en.wikipedia.org/wiki/Data_migration 2 http://en.wikipedia.org/wiki/System_migration 3 http://en.wikipedia.org/wiki/Upgrade

  9. It’s all technical… right? • Make sure that you’ve successfully incorporated the technology components that help drive adoption • Implement a Training Plan • Implement a Communications Plan • Decide on a Content Migration Strategy • Have a User Support Plan • Provide Incentives and Rewards • Enable End-user Feedback • Align Business Objectives

  10. Lets get technical… • Hardware and Software Requirements • 64-bit hardware • Windows Server 2008 or Windows Server 2008 R2 • Microsoft SQL Server 2008 R2 / SQL Server 2008 with Service Pack 1 (SP1) and Cumulative Update 2 / SQL Server 2005 with SP3 and Cumulative Update 3 • SharePoint 2007? Service Pack 2 • Other preparation • SharePoint 2001 - Consider a Third Party Tool • SharePoint 2003 - Hire a Consultant, PreScan.exe, ReGhost.net, GhostHunterWebParts • SharePoint 2007 - Service Pack 2: STSADM.exe -o preupgradecheck • SharePoint 2010 - test-spcontentdatabasecmdlet Other Resources

  11. 3rd Party Tools vs. OOTB • Out of the Box • In-place • Database Attach • 3rd Party • AxcelerDavinci Migrator • AvePointDocAve • Metalogix Migration Manager • Idera SharePoint Migration Suite (OEM’d by Quest) • Tzunami Migration • Kapow Solutions • XavorSolutions

  12. In-Place or Database Attach • In-place • Same operating system (x64 required) • Same hardware (x64 required) • Content andsettings come along • Farm is offline while upgrading • Database Attach • New hardware • Onlycontent comes along • Content is not available while upgrading, but you get to pick the order! • Parallel upgrades of content • Combine multiple farms • Hybrid • Database attach read-only databases • In-place upgrade with detached databases

  13. In-Place or Database Attach vs.

  14. What about upgrading 2010 to Service Pack 1? Consolidating content from one 2010 farm to another? • Upgrade from Pre-SP1 to SP1 Required • Farm, Web Application or Content Database PSConfig-cmd upgrade -inplace b2b -wait -force • Site Collection Backup and Restore Upgrade your farm to SP1

  15. Authentication Changes • Classic AuthN • Integrated Windows AuthN with NTLM / Kerberos • Claims AuthN and AuthZ • Integrated Windows AuthN with NTLM / Kerberos • Forms Based Auth • Trusted Identity Provider (aka SAML & WS Fed)

  16. Considerations when choosing… • Additional setup for IWA Claims – Claims to Token for Kerberos Delegation • PerformancePoint Services, InfoPath Forms Services, Excel Services, etc. • Search Alerts, Search Crawling • SharePoint Explorer View • Secure Store comes in handy… • Forms Based AuthN – Still have a Membership Provider and Role Manager to register within web.config • When setting up a Trusted Identity Provider there’s a bit of work that must be done…

  17. More considerations… • Be prepared to figure out your AuthZ side of things • IWA leverages NT Security Token • Forms Role Manager information mapped • Group Claims information • Identities with one Claim Provider aren’t the same as with another… • c:0j.c|claimprovider|useraccount != c:0#.f|claimprovider|useraccount • Similar to Domain A and Domain B user objects in Classic • Multitenancy • Single zone… • Partitioned search… • Partitioned user profiles… • Partitioned Managed MetaData…

  18. What’s that mean to me? • Classic to Classic • Mapping “should” stay intact • Classic to Claims • Mapping update required • Classic Provider Identity to Claim Provider Identity • Migrate a web application… • http://technet.microsoft.com/en-us/library/gg251985.aspx

  19. What about Search? • Have you updated your Information Architecture? • Should be able to find information in any of 3 scenarios: • I know it exists and I know where it is • I know it exists, but I don’t know where it is • I don’t know if it exists • Talk to your users! Relevancy optimization is an ongoing process.

  20. What about Custom Solutions? • Web Templates and Site Definitions • BDC -> Application Registry Database • Custom Solutions • .Net version – recompile for appropriate framework • Farm Solutions to Sandboxed Solutions • Third Party Tools

  21. What about Workflows? • Remember to breathe… • In-place upgrades are your best bet • Third Party Tools with Full Fidelity • Axceler • AvePoint • Metalogix • … and others? • Gotchas • Not using the latest and greatest… • Workflow History Cleanup

  22. Content Assessment • How much data we have and where does it reside? • If we’re migrating, how will the transfer occur? • How long will it take? • Considerations for Search • Corpus size • Multilingual? • Does your content need to change in the new system? • Choice fields vs. Managed Metadata • Content Type authoring in a Content Hub?

  23. Consolidation Considerations • Does your existing taxonomy fit in the new system? • Do you have existing systems / applications that will also be migrated into SharePoint? • Do we need to (un)consolidate? • Single site collections that need to be broken apart into multiple collections • Sites that need to be promoted into site collections? • Do we have too many site collections in our databases? • Customizations / Farm Solutions

  24. Still more Content to assess… • Identify 3rd party tools/web parts/etc. that are installed in your current farm • Is there a 2010 version available? • Is the functionality now available OOTB in SharePoint (Ratings, Faceted Search, …) • Don’t forget your non-SharePoint data. Lotus? WebSphere? Drupal? DotNetNuke? Alfresco? Legacy HTML? Non-OCR’d Text Documents? Orchard?

  25. Other Solution Sets • What about the Fab 40? • What about the Productivity Hub? • Where’d my Site Directory go? • Where’d my SharePoint Designer Site Export go?

  26. Prepping for Migration…Disaster Recovery • Do you have plans? • Have you tested your plans? • Mirroring? Clustering? • Regression Plans

  27. What about the Users? • User Experience • Visual Upgrade (aka v3) is familiar. The ribbon is not. • Are you deploying the Office Web Applications? (Co-authoring can be fun!) • Multiple item selections. Refinement panels. Metadata navigation. Oh my! • What about your licensing? Enterprise? Standard? • Office Workspace? Groove? • Mobile? • Oh, you are upgrading your Office Clients too right?

  28. Training? Do we have to? • YES! • Training Tools • Videos • Computer based training • Formal classroom training • “Office hours” (on-going) • Productivity Hub from Microsoft • If you have have to provide extensive training to your typical user, you’ve most likely made some fundamental design mistakes!

  29. Entropy vs. Order Entropy - /ˈentrəpē/ • A thermodynamic quantity representing the unavailability of a system's thermal energy for conversion into mechanical work, often... • Lack of order or predictability; gradual decline into disorder. Order - /ˈôrdər/ • The arrangement or disposition of people or things in relation to each other according to a particular sequence, pattern, or method.

  30. Something to remember SharePoint Implementations today consist of a race between Architects, Developers and IT Pros striving to build well planned out, bigger and better idiot-proof solutions, and the Universe trying to produce requirements of entropy with bigger and better idiots. …so far, the Universe is winning.

  31. Thank your Sponsors! The umlaut symbol ü The number e e the exponential function is the derivative of itself

  32. Thanks to the real sponsors too!

  33. Do you know what this is?

  34. Everyone is invited to #SharePintImmediately following SharePoint Saturday Boston Meet at Skellig @ 240 Moody Street 2.2 miles ~ 42 minutes walking, 9 minutes driving SharePint: a gathering of SharePoint enthusiasts for fun, food, and drink.

  35. Evaluations & Questions? • Please fill out your evaluations before you leave…

  36. Reference • What's new in upgrade • Determine upgrade approach • SharePoint Server 2010 capacity management: Software boundaries and limits • Video demos and training for SharePoint Server 2010 • SharePoint 2010 Adoption Best Practices

More Related