• Save
Pitfalls of Migration to SharePoint 2010
Upcoming SlideShare
Loading in...5
×
 

Pitfalls of Migration to SharePoint 2010

on

  • 1,774 views

Session from SharePoint Saturday Virginia Beach 2010 #SPSVB

Session from SharePoint Saturday Virginia Beach 2010 #SPSVB

Statistics

Views

Total Views
1,774
Views on SlideShare
1,039
Embed Views
735

Actions

Likes
1
Downloads
0
Comments
0

6 Embeds 735

http://www.mylifeinaminute.com 688
http://psconfig.com 23
http://feeds.feedburner.com 19
http://www.linkedin.com 2
http://translate.googleusercontent.com 2
https://www.linkedin.com 1

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • SCOTT, then DAN
  • 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½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 10,000 less that what it was in MOSS 2007!
  • 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
  • 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
  • DAN

Pitfalls of Migration to SharePoint 2010 Pitfalls of Migration to SharePoint 2010 Presentation Transcript

  • #spsvb
  • #spsvb
  • #spsvb
  • #spsvb
  • 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#spsvb
  • #spsvb
  • #spsvb
  • #spsvb
  • and  Only#spsvb
  • #spsvb
  • #spsvb
  • #spsvb
  • #spsvb
  • #spsvb
  • #spsvb
  • #spsvb
  • #spsvb
  • #spsvb
  • #spsvb
  • #spsvb
  • Office Clients#spsvb
  •  YES!#spsvb
  • #spsvb
  • …so far, the Universe is winning.#spsvb
  • #spsvb
  • Red Star Tavern#spsvb
  • #spsvb
  • 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#spsvb