Pitfalls Of Migrating to SharePoint 2010


Published on

Organizations of all sizes are begging their technical departments to set up
SharePoint 2010 so that they're able to make use of some of the capabilities
introduced within the platform. While designing, implementing, configuring and deploying a system in and of itself has its own set of challenges, migrating into that shiny new SharePoint can be even more difficult.

In this session, you will learn tips, tricks and pointers for ensuring that you've considered the various aspects of challenges that arise during a migration effort. Further, as a bonus, you will learn how not to fall prey to some of these pitfalls, but rather be able to show that you're a well-rounded
professional that's thought things through before pressing the enter key.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Pitfalls Of Migrating to SharePoint 2010

  1. 1. ScottHoagciphertxt
  2. 2. DanUsherusher
  3. 3. introductions
  4. 4. a few ground rules…
  5. 5. http://xkcdsw.com/2502
  6. 6. transferring data minimizing re-engineering involve downtime replacement of a producthttp://en.wikipedia.org/wiki/Data_migrationhttp://en.wikipedia.org/wiki/System_migrationhttp://en.wikipedia.org/wiki/Upgrade
  7. 7. devising your way ahead
  8. 8. You’re pretty funny…you must be new here…we don’t do plans…
  9. 9. Web Front End(s) SQL Server(s)Componen Minimum Requirement Component Minimum Requirementt Hardware 64-bit, four cores (smallHardware 64-bit, four cores deployments) 64-bit, eight cores (medium deployments)Memory 8 GB Memory 8 GB (small deployments) 16 GB (medium deployments)Operation Windows Server 2008 R2 Operation Windows Server 2008 R2 withSystem with SP1 System SP1 Windows Server 2008 with Windows Server 2008 with SP2 SP2 SQL Server SQL Server 2008 R2 SQL Server 2008 with SP1 (SP1) and CU2 (or CU5 or later) SQL Server 2005 with SP3 and CU3
  10. 10. Version Migration PreparationSharePoint Portal Server 2001 Hire a consultant Consider a 3rd party migration toolWindows SharePoint Services Hire a consultant3.0 Prescan.exe / ReGhost.net / GhostHunter Web PartsOffice SharePoint Server 2007 STSADM –o preupgradecheckSharePoint Server 2010 test-spcontentdatabase cmdlet
  11. 11. and New hardware Only
  12. 12. side bar
  13. 13. > PSConfig -cmd upgrade -inplace b2b -wait -force
  14. 14. considerations
  15. 15. Classic AuthN Claims AuthN and AuthZ Integrated Windows AuthN with NTLM / Kerberos Forms Based AuthN Trusted Identity Provider (aka SAML & WS Fed)
  16. 16. $> i:0#.w|claimprovider|useraccount != i:0#.f|claimprovider|useraccount
  17. 17. Migrate a web application
  18. 18. • Lotus • Alfresco• WebSphere • Legacy HTML• Drupal • Non-OCR’d Text• DotNetNuke Documents • Orchard
  19. 19. Office Clients
  20. 20.  YES!
  21. 21. closing thought
  22. 22. …so far, the Universe is winning.
  23. 23. questions ?
  24. 24. evaluations
  25. 25. dan@spdan.com@usherwww.sharepointdan.comScott.hoag@spdelta.com@ciphertxtwww.psconfig.com
  26. 26. Whats new in upgradeDetermine upgrade approachSharePoint Server 2010 capacity management:Software boundaries and limitsVideo demos and training for SharePoint Server2010SharePoint 2010 Adoption Best Practices