Upgrading to SharePoint 2010

Gary Lapointe, SharePoint MVP

About Me• SharePoint MVP• Company: ShareSquared, Inc.• Blog: http://stsadm.blogspot.com/• Email: gary@thelapointes.com• Twitter: @glapointe

14

Who, When & WhyConsiderations:

Good candidates for upgradeYou need certain 2010 featuresYou have not done significant* customizations

Get a second opinion if:You have a large deploymentYou’ve done significant customization

Timing:Start planning & install the Beta now!RTM is May 12th

14

Server PreparationSQL Server

SQL 2008 R2 or SQL 2008+SP1+CU2 (or greater)SQL 2005 w/SP3 – supported / not recommended

SharePoint ServersSharePoint 2007 SP2 + October CU (or greater)

October CU updates the preupgradecheck STSADM command64 bit requiredWindows Server 2008 Standard w/SP2 (or greater)WCF Hotfix (not part of the prerequisites installer)Minimum 8GB RAM

Pre-Upgrade CheckRun the STSADM preupgradecheck command prior to upgradeRun the Test-SPContentDatabase cmdlet prior to DB mount

Plan for sufficient disk space

14

Upgrade Approaches

In-Place Upgrade

Database Attach Upgrade

Hybrid 1: Read-Only Database Upgrade

Hybrid 2: Detach

Database Upgrade

14

In-Place UpgradeUse existing hardware – servers/farm offline during upgradeConfiguration and all content upgradedFarm-wide settings preservedCustomizations available after upgradeRecommended for small or non-production environments

14

Database Attach UpgradeNew hardwareUpgrade multiple DBs at a timeServer farm settings not upgradedCustomizations must be transferredCan consolidate multiple farms into oneRecommended if farm level configurations are minimal

14

Hybrid 1: Read-only databasesUse Database Attach upgrade to preserve existing farmExisting farm is put in read-only modeCreate a new farm and attach all content databasesServer farm settings not upgradedRecommended over Database Attach

14

Hybrid 2: Detach databasesUse in-place upgrade for farm settings to preserve configurationsDetach and upgrade content databases Alternatively, upgrade content databases in a temporary farmRecommended if farm level configurations are significant

14

CustomizationsMany assemblies will not require re-compilation

Assembly binding redirects are machine level post Beta2Use SharePoint Solution Packages (WSPs)Site Templates deprecated

Existing sites based on the template will upgradeTo create new sites using the template create a site using the template, upgrade the database, and export the site as a WSP

SharePoint 2007 Themes deprecatedConvert and redeploy using the new SharePoint 2010 Theme format

Changes to OOTB files will not upgradeDocument changes to files such as document icons and noise wordsChanges will need to be recreated

14

Customizations (cont.)Importing SharePoint 2007 WSPs not created using VSeWSS is not supported*Queries on SPList items that exceed 5000 items will fail

Increase the default query threshold or modify the queryTake Visual Upgrade into consideration

Use the SharePoint:VersionedContent or SharePoint:VersionedPlaceHolder controls to support v3 and v4 UI characteristicsUse SPWeb.UIVersion to check what UI version the site it using

Don’t forget to check 3rd party vendors for updates to installed packages!

14

DEMO: Hybrid Approach 2

14

Upgrade Best PracticesLarge content databases and site collections will take longer to upgrade

If upgrade time is critical consider splitting Content Databases and/or Site Collections into smaller units prior to upgrade

STSADM’s mergecontentdbs command can be used to move a Site Collection to a different Content Database

Archive off any Site Collections, Webs, or Lists that are no longer necessary

This will reduce upgrade time and potentially reduce upgrade issues related to customizationsArchiving of Lists will require 3rd party tools or can be done after upgrade using Central Admin or PowerShell

Plan for Visual UpgradeHow will it be utilized?How long will sites use the V3 UI?Will Site Collection administrators be able to change or will it require IT intervention?

14

Upgrade Best Practices (cont.)Migrate SharePoint 2007 to 64-bit prior to upgradePrepare Client Desktops

Update to Office 2010 for enhanced featuresPre-deploy Silverlight 3.0

Evaluate Upgrade versus MigrationProvide user training

Train end-users before and after upgradeTrain administrators and developers before you even start planning for your upgrade

Test your Disaster Recovery strategy before upgradingDon’t upgrade a broken farm

14

Thank you

Thank you