#SPSBos
#SPSBos
#SPSBos
#SPSBos
#SPSBos
#SPSBos
#SPSBos
transferring data                                                               minimizing    re-engineering              ...
#SPSBos
#SPSBos
#SPSBos
and       Only#SPSBos
#SPSBos
#SPSBos
#SPSBos
#SPSBos
#SPSBos
#SPSBos
#SPSBos
#SPSBos
#SPSBos
#SPSBos
#SPSBos
#SPSBos
#SPSBos
#SPSBos
Office Clients#SPSBos
 YES!#SPSBos
#SPSBos
…so far, the Universe is winning.#SPSBos
#SPSBos
#SPSBos
#SPSBos
#SPSBos
#SPSBos
Whats new in upgrade   Determine upgrade approach   SharePoint Server 2010 capacity management:   Software boundaries and ...
Upcoming SlideShare
Loading in …5
×

SharePoint Saturday Boston - Pitfalls of Migrating to SharePoint 2010

2,018 views
1,970 views

Published on

Organizations of all sizes are begging their technical departments to setup SharePoint 2010 so that they're able to make use of some of the capabilities introduced within the SharePoint 2010 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, Scott and Dan will share some of their experiences and lessons learned 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 they'll share how to not 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
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
2,018
On SlideShare
0
From Embeds
0
Number of Embeds
851
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • SCOTT
  • DAN
  • SCOTTMigration versus UpgradeAre we going to do a content migration or a full up system upgrade that happens to include the entirety of the system being migrated in the process?Are we going the route of in place with Visual Upgrade or are we going the route of a database attach with a Visual Upgrade?3rd Party Tools versus OOTBDo we go buy Axceler, Metalogix, Quest, IderaWhat’s the best optionConsolidation ConsiderationsWhile we’re at it, are we going to consolidate into a single farm, a plantation, a distributed system, we’re just staying as isContent AssessmentsWait, we’re moving into a new house, shouldn’t we move things around so that it’s nice and pretty for when we’re there or are we going to be like hoardersUser Experience and TrainingThe ribbon, where’d that come from? How do I use this document set thing?Certificate plug for 77-886Authentication ChangesOh the power of claimsRealm discoveryEntropy versus Order- If we take the product of S…
  • SCOTTMigration versus UpgradeAre we going to do a content migration or a full up system upgrade that happens to include the entirety of the system being migrated in the process?Are we going the route of in place with Visual Upgrade or are we going the route of a database attach with a Visual Upgrade?Establish a baseline (common language)What is the approach? Are we upgrading? Are we migrating? Are we doing both?
  • DAN
  • DANMake mention of the other resources – Joel Oleson’s blog, Todd and Shane,Axceler Migration Toolkit, TechNet Planning Section – Capacity and sizing documentationPreUpgradeCheck – Customized / UncustomizedTest-SPContentDatabase – Features for 2007 / 2010
  • SCOTT3rd Party Tools versus OOTBDo we go buy Axceler, Metalogix, Quest, IderaWhat’s the best optionIn place?Hardware supportDowntime!Database attach?Build a new farm, plan topology and services3rd partyWhat doesn’t it migration (workflow?)What about existing data (e.g. SSP and MyLinks)
  • SCOTTIn place?Hardware supportDowntime!Database attach?Build a new farm, plan topology and services
  • SCOTTIn place?Hardware supportDowntime!Database attach?Build a new farm, plan topology and services
  • DANMore and more of the SharePoint 2010Technet articles are essentially requiring an extra farm be available for any upgrade or patching.Restore a site collection from Pre-SP1 to SP1 - http://technet.microsoft.com/en-us/library/hh344831.aspxUpdating Mission Critical Updates - http://technet.microsoft.com/en-us/library/hh495476.aspx
  • DANAuthentication ChangesOh the power of claimsRealm discoveryWhat’s this mean to me?
  • DAN
  • DAN
  • DANChanging from domain A to domain B In SharePoint 2003 and 2007 you
  • SCOTT
  • SCOTT
  • DAN
  • SCOTTContent AssessmentsWait, we’re moving into a new house, shouldn’t we move things around so that it’s nice and pretty for when we’re there or are we going to be like hoardersDANWhat about the Site Directory though?Third Party CodePlex available but it’s not the end all be all
  • DAN½SCOTT¾Consolidation ConsiderationsWhile we’re at it, are we going to consolidate into a single farm, a plantation, a distributed system, we’re just staying as isSP2010 supports no more than 5,000 site collections in a content database for upgrade. This is 45,000 less that what it was in MOSS 2007! Recommendation is 2,000.To set the warning level for the number of sites in a content database, use the Windows PowerShell cmdlet Set-SPContentDatabase with the -WarningSiteCount parameter. For more information, see Set-SPContentDatabase.
  • SCOTTContent AssessmentsWait, we’re moving into a new house, shouldn’t we move things around so that it’s nice and pretty for when we’re there or are we going to be like hoardersDANWhat about the Site Directory though?Third Party CodePlex available but it’s not the end all be all
  • SCOTTUser Experience and TrainingThe ribbon, where’d that come from? How do I use this document set thing?Certificate plug for 77-886
  • SCOTTUser Experience and TrainingThe ribbon, where’d that come from? How do I use this document set thing?Certificate plug for 77-88680/20 rule – 80% of users should be using 20% of the functionality. Don’t worry about the 20% that want to use 80%!
  • DANEntropy versus Order- If we take the dot product of S…
  • DAN
  • SCOTT
  • SharePoint Saturday Boston - Pitfalls of Migrating to SharePoint 2010

    1. 1. #SPSBos
    2. 2. #SPSBos
    3. 3. #SPSBos
    4. 4. #SPSBos
    5. 5. #SPSBos
    6. 6. #SPSBos
    7. 7. #SPSBos
    8. 8. transferring data minimizing re-engineering involve downtime replacement of a product http://en.wikipedia.org/wiki/Data_migration http://en.wikipedia.org/wiki/System_migration http://en.wikipedia.org/wiki/Upgrade#SPSBos
    9. 9. #SPSBos
    10. 10. #SPSBos
    11. 11. #SPSBos
    12. 12. and  Only#SPSBos
    13. 13. #SPSBos
    14. 14. #SPSBos
    15. 15. #SPSBos
    16. 16. #SPSBos
    17. 17. #SPSBos
    18. 18. #SPSBos
    19. 19. #SPSBos
    20. 20. #SPSBos
    21. 21. #SPSBos
    22. 22. #SPSBos
    23. 23. #SPSBos
    24. 24. #SPSBos
    25. 25. #SPSBos
    26. 26. #SPSBos
    27. 27. Office Clients#SPSBos
    28. 28.  YES!#SPSBos
    29. 29. #SPSBos
    30. 30. …so far, the Universe is winning.#SPSBos
    31. 31. #SPSBos
    32. 32. #SPSBos
    33. 33. #SPSBos
    34. 34. #SPSBos
    35. 35. #SPSBos
    36. 36. Whats 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#SPSBos

    ×