Upgrading to SharePoint 2010

Who, When & Why Considerations: Good candidates for upgrade You need certain 2010 features You have not done significant* customizations Get a second opinion if: You have a large deployment You’ve done significant customization Timing: Start planning & install the Beta now! RTM is May 12 th

Server Preparation SQL Server SQL 2008 R2 or SQL 2008+SP1+CU2 (or greater) SQL 2005 w/SP3 – supported / not recommended SharePoint Servers SharePoint 2007 SP2 + October CU (or greater) October CU updates the preupgradecheck STSADM command 64 bit required Windows Server 2008 Standard w/SP2 (or greater) WCF Hotfix (not part of the prerequisites installer) Minimum 8GB RAM Pre-Upgrade Check Run the STSADM preupgradecheck command prior to upgrade Run the Test-SPContentDatabase cmdlet prior to DB mount Plan for sufficient disk space

Upgrade Approaches In-Place Upgrade Database Attach Upgrade Hybrid 1: Read-Only Database Upgrade Hybrid 2: Detach Database Upgrade

In-Place Upgrade Use existing hardware – servers/farm offline during upgrade Configuration and all content upgraded Farm-wide settings preserved Customizations available after upgrade Recommended for small or non-production environments

Database Attach Upgrade New hardware Upgrade multiple DBs at a time Server farm settings not upgraded Customizations must be transferred Can consolidate multiple farms into one Recommended if farm level configurations are minimal

Hybrid 1: Read-only databases Use Database Attach upgrade to preserve existing farm Existing farm is put in read-only mode Create a new farm and attach all content databases Server farm settings not upgraded Recommended over Database Attach

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

Customizations Many assemblies will not require re-compilation Assembly binding redirects are machine level post Beta2 Use SharePoint Solution Packages (WSPs) Site Templates deprecated Existing sites based on the template will upgrade To 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 deprecated Convert and redeploy using the new SharePoint 2010 Theme format Changes to OOTB files will not upgrade Document changes to files such as document icons and noise words Changes will need to be recreated

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 query Take Visual Upgrade into consideration Use the SharePoint:VersionedContent or SharePoint:VersionedPlaceHolder controls to support v3 and v4 UI characteristics Use SPWeb.UIVersion to check what UI version the site it using Don’t forget to check 3 rd party vendors for updates to installed packages!

DEMO: Hybrid Approach 2

Upgrade Best Practices Large 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 customizations Archiving of Lists will require 3 rd party tools or can be done after upgrade using Central Admin or PowerShell Plan for Visual Upgrade How 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?

Upgrade Best Practices (cont.) Migrate SharePoint 2007 to 64-bit prior to upgrade Prepare Client Desktops Update to Office 2010 for enhanced features Pre-deploy Silverlight 3.0 Evaluate Upgrade versus Migration Provide user training Train end-users before and after upgrade Train administrators and developers before you even start planning for your upgrade Test your Disaster Recovery strategy before upgrading Don’t upgrade a broken farm