Upgrading Microsoft Office SharePoint Server 2007 to SharePoint Server 2010

Ivan Sanders

SharePoint MVP, Architect DeveloperDimension Solutions inc.

Dimension Solutions inc.

ivan@dimension-si.com

Upgrade Scenarios and Methods

Supported Scenarios

In-Place Upgrade Database Attach

Upgrade: Content Database Profile Service Database Project Service Database

Single Click Install - SQL Migration Windows Internal Database

(WID) -> SQL Express 2008 + File Stream RBS

Unsupported Scenarios

Upgrade from earlier than WSS v3 SP2/MOSS 2007 SP2

Direct upgrade from WSS v2/SPS 2003 or earlier

Side by side installation Gradual upgrade

In-Place Upgrade Next, next, finished Advancements

Restartable! Common blocking time outs removed

All sites are unavailable during upgrade Site visitors continue to use the same URLs after upgrade

Does require v3 to be 64 bit Whitepaper on moving from 32 bit to 64 bit SharePoint

○ http://technet.microsoft.com/en-us/library/dd622865.aspx

Previous version must be manually removed when upgrade is complete

In-Place Pros/Cons

Farm wide settings are preserved and upgradedCustomizations are available in the environment after the upgrade if they are v4 compatible

Pros

Servers and farms areoffline while the upgradeis in progressThe upgrade proceeds continuouslyExisting v3 farm must support (64 bit and performance

Cons

Inplace Upgrade

DEMO

Database Attach Steps Stsadm –o preupgradecheck on your 2007 farm Backup 2007 Content DB Restore to SharePoint 2010 SQL Server, using SQL Tools Test-SPContentDatabase –name wss_content_2007 –

webapplication http://Team2010WebApp Mount-SPContentDatabase –name wss_content_2007 –

webapplication http://Team2010WebApp

DB Attach Pros/Cons

Upgrade multiple content databases at the same time Combine multiple farmsinto one farmCustomizations must be transferred manually

Pros

The server and farm settings are not upgradedCustomizations must be transferred manuallyMissing customizations

Cons

Database Attach

DEMO

Hybrid Approach Detach DBs Upgrade to 2010 in-place DB Attach content DBs

Hybrid Pros/Cons

Farm wide settings preservedCustomizations alreadyin placeMultiple content databasesat the same timeNon-upgraded sites(in read-only mode) whileyou upgrade the content

Pros

Labor intensiveDirect access to the database serversx86 is a lot of workExisting hardwaremay need replacing

Cons

Hybrid Approach

DEMO

Downtime Mitigation Processes Read-only databases (v3 SP2, v4) Parallel content database upgrades

Parallel upgrade farms (v4) Single farm, multiple upgrade sessions (v4)

Content database attach with AAM redirection (v4) http://technet.microsoft.com/en-us/library/

ee720448(office.14).aspx

Database Attach with AAM Redirect User interaction model

SQL Instance

WFEv3 Farm

WFE v4 Farm

http://WSShttp://WSSold http://WSSSQL

v3Config

v4Config

SQL

v3Content

v4Content

Move DB

?302

WSS v3Web App

WSS v4Web App

What is “Visual Upgrade” A feature that separates data upgrade

from UI upgradeData and code upgrade happens all at onceSite UI has two modes: this version and

previous versionPages and components make the decision

at runtime, and it’s safe by default

Why “Visual Upgrade”? IT

Focus on the dataSchedule flexibility

DevelopersClear expectationsMore control over legacy code and controls

UsersPuts the user impact into users’ handsAccommodates big shifts (ribbon)

Visual Upgrade

DEMO

Core Upgrade Overview Improvement Upgrade improvement areas Predictability/reliability Diagnostic ability/logging End-user experience Admin experience Logging Upgrade logs per session

(saved in same place) Error log per session ( -error.log)

Separate log for just errors Shows callstacks

Upgrade logs always have same columns of data making reporting easier to automate.

Core Upgrade Improvements Logging Upgrade logs per session

(saved in same place) Error log per session ( -error.log)

Separate log for just errors Shows callstacks

Upgrade logs always have same columns of data making reporting easier to automate.

Admin experience Visual feedback Better warning Quota handling and locked site collections Upgrade status page

Upgrade points to consider V3 must be Service Pack 2 or later You cannot upgrade a Trial SKU FBA web applications now use Claims in v4 Stsadm command shipped with SP2, updated with Oct 09

CU –o preupgradecheck

Do Spring cleaning before you upgrade Stale sites Excessive document Versions Reorganize Site Collections into databases as necessary

Plan to revisit branding http://technet.microsoft.com/en-us/sharepoint/ff420396.aspx

Q & A

Who can you trust??The blogs I trust through all of the noise.

Maurice Prather http://www.bluedoglimited.com/default.aspx Andrew Connell http://www.andrewconnell.com/blog Spence Harbarhttp://www.harbar.net Jim Duncan Heather Solomon http://www.heathersolomon.com/blog Todd Klindt http://www.toddklindt.com/default.aspx Todd Baginski http://www.toddbaginski.com/blog Todd Bleeker http://bit.ly/edlSm5

Jan Tielens http://weblogs.asp.net/jan Patrick Tisseghem http://www.u2u.info/Blogs/Patrick/default.aspx Wictor Wilen http://www.wictorwilen.se Ted Patisson http://blog.tedpattison.net/default.aspx Lars Fastrup http://www.fastrup.net Carsten Keutmann http://keutmann.blogspot.com Keith Richie http://blog.krichie.com Bill Baer http://blogs.technet.com/b/wbaer

PLAN

SharePoint Solution Accelerators andSystem Center

Microsoft

System Center

SharePoint Configurator

SharePoint Asset Inventory Tool

MicrosoftSystem Center

Operations Manager

MicrosoftSystem Center Configuration

Manager

MicrosoftSystem Center

Virtual Machine Manager

SharePoint Monitoring Toolkit

MicrosoftSystem Center Virtual Machine Manager

MicrosoftSystem Center Capacity Planner

MicrosoftSystem Center Configuration Manager

SharePoint Capacity Planner