Best Practices for SharePoint 2010 UpgradeJoel Oleson

Sr. Architect

Quest Software

@joeloleson

10 Years of SharePoint

SharePoint Product Architect, Evangelist & Strategy @ Quest

Who is SharePoint Joel?

SharePointJoel.com

Upgrade

Learn

Prepare

TestImplement

Validate

BeforeDuring & After

Pre Upgrade

SharePoint 2010 Requirements

• SharePoint 2007 SP2 Update (Recent CU or at least October highly recommended)

• 64 bit operating system for application servers– Windows Server 2008 or 2008 R2 + SP & Hotfixes

included in PreReq Installer

• 64 bit SQL Server– 2008 R2+, 2008 SP1 CU5 or later, 2005 SP3 CU5 or

later***

• Virtualization is supported and very common

*** Upgrade or Installation will fail w/o proper CU

Running PreUpgradeCheck (in SP2007 Sp2)

PreUpgradeCheck Failed Report (snippets)

Test-SPContentDatabase

Upgrade

Insight on Upgrade

• Binary Upgrade– In Place - New Timeout, Resume on failures– Database Attach - New Parallel, Progress

Indicator

• Visual Upgrade– Separate process– Delegation by default

Binary Upgrade

Visual Upgrade

In-Place Upgrade

• All-at-once upgrade– Must upgrade the whole farm at one time– No SP 2007 and SP2010 in same farm– Schedule downtime

• Simplest approach, but *most risky*!– No going back

• Resume Upgrade if problems occur• Recommendations

– Run Test-SPContentDatabase from SP 2010 farm against databases

– Do a full farm backup before you start!

Pre Requisite Installer

In Place Upgrade - Install

In Place - Binary Approach to Upgrade

Pre-Upgrade

Check 2007 farm

Fix Issues

Upgrade Binaries with In place

(Setup)

Fix Issues Visual Upgrade Verify

Caution: Not recommended for most deployments…

Why I don’t recommend In-Place Alone

Database Attach Upgrade• Safer, Requires more planning (A good thing)• Upgrade is done on a separate 2010 farm

– Done database-by-database – Can be used with 2nd step visual upgrade

• Use Test-SPContentDatabase (PowerShell cmdlet) to test database first

• To attach– Mount-SPContentDatabase (PowerShell)– STSADM –o Addcontentdb operation

• Parallel database upgrades are possible

DEMO

• Test-SpContentDatabase• Mount-SpContentDatabase• Upgrade Status

Attaching Database to SP2010 Farm

Central Admin Upgrade Status

No Brainer - Read-Only Database Strategy

DB Attach - Binary Approach to Upgrade

PreUpgradeCheck

on SP2007

farm

Fix issues

Create Destination farmUpgrade Services(consider in-place)

Test-SPContentDataba

ses

Add solutions

/Fix issues

Set ReadonlyDatabase

Attach Content

Databases

Visual Upgrade

Recommended for most deployments…

Visual Upgrade

• Stay in 2007 (default) or move to 2010 UI– 2010 ships 2007 Master pages and CSS– UI Preview capability

• Farm admin or site admin controlled– Web level setting

• Some items not 2007 UI compatible– My site host– PWA site collection– Report Server web parts

Post Binary Upgraded Site: Preview Visuals

Visual Upgrade Options

What about the Fabulous 40 Application Templates?

• What do you want to do?– I want to continue using them

• Install Upgraded Templates - Fab 40 on Destination farm

• Convert Templates - .STP to .WSP

– I want to remove them• Remove the .stp (Remove the template)• Export lists or use third party tools to move into

OOB Site Defs

– http://bit.ly/dhQUjd

Upgrade Strategies

PowerShell Upgrade CmdletsTest-SPContentDatabase• Discover and Document issues 2007/2010

Mount-SPContentDatabase• Initiate Content database B2B/V2V upgrade

Upgrade-SPContentDatabase• Resume Content database B2B/V2V upgrade

Upgrade-SPEnterpriseSearchServiceApplication• Search Service Application Instance

Upgrade-SPSingleSignOnDatabase• O12 SSO data to Secure Store database

Hybrid Upgrade Considerations

• Best of In Place– Configuration database– Site Definitions may be upgraded– Easier SSP -> Service App Upgrade

• Best of Database Attach– Fast with multi database parallel upgrade

Consider a Hybrid Upgrade

Make a copy of

the farm

Set databases Read-Only on Source

Upgrade Binaries/ Services with In Place

upgrade on

Secondary

Test-SPContentDatabases

Database Attach

Content Databases in Parallel

Visual Upgrade

Decisions???

• Customized?• Uptime?• New Hardware

Extra?• Hardware Ready?• Virtual/Rollback?• MSDE/SQL Express?

SSP to Service App

• Each SSP upgrades into:– A Search service app– A User Profiles service app– An Excel service app– An App Registry back-compat service app

• New Services can be activated/added

Visual Upgrade Strategies

• Upgrade the UI at the same time– psconfig.exe –cmd upgrade –

preserveolduserexperience false– Updateuserexperience parameter of the

Mount-SPContentDatabase or STSADM

• Stager Upgrade (Hide UI)– Post Upgrade: Site Settings | Site Collection

Administration | Supported User Experiences

• Delegate UI Upgrade (Default)• psconfig.exe –cmd upgrade –

preserveolduserexperience true

In Place Upgrade - Visual Upgrade Decisions…

Troubleshooting/Common Issues

• Missing server-side files or customizations, such as features or Web Parts

• Configuration issues in the server farm, Web application, or services, such as managed paths or services that are not started

• Additional issues in sites discovered on a site-by-site basis, starting with high-impact, high-profile sites

• Disk Space or CPU/Memory Constraints• Don’t forget Forms to Claims• Profile Import & FIM (CU has fixes, security

requirement)

Released to the Web

• SharePoint 2010: Best Practices for Upgrading and Migrating– Get Prescriptive guidance on

Upgrade Methods– Drill deep into assessment

tools– Compare Migration tools– Save yourself time

Why Consider third party tools?

• Getting out of customizations…• Quest Migration Manager

– 2003 to 2010 with post Migration Sync– 2007 to 2010 in beta

• Notes to SharePoint Migrations

www.quest.com

Thank you!

Learn More about SharePoint 2010

Information forIT Prosat TechNet

http://MSSharePointITPro.com

Information forDevelopers

at MSDNhttp://MSSharePointDeveloper.com

Information forEveryone

http://SharePoint.Microsoft.com