Upgrading to SharePoint 2010

Todd Klindt & Shane Young

SharePoint911 a Rackspace company

Who is this Todd guy?

• WSS MVP since 2006

• Speaker, writer, consultant, Aquarius, President of Shane Young fan club

• Personal Blog www.toddklindt.com/blog

• Company web site www.sharepoint911.com

• E-mail todd.klindt@rackspace.com

• Twitter me! @toddklindt

• Glad Shane doesn’t sign my paychecks

Who Am I?

• Shane Young

• SharePoint911, a Rackspace Company

• Microsoft Office SharePoint Server MVP

• Consultant, Trainer, Writer, & Speaker

• Shane.Young@Rackspace.com

• Blog

• http://msmvps.com/shane

• SharePoint Consulting

• http://www.sharepoint911.com

• http://twitter.com/shanescows

• Just had my first paid holiday in almost 7 years.

2010 Upgrade Scenarios and Methods

• Content Database

• Profile Service Database

• Project Service Database

• Windows Internal Database (WID) -> SQL Express 2008 + File Stream RBS

Patches are your friends

• For both SharePoint 2007 and 2010

• Find your patch level

• http://www.toddklindt.com/sp2010builds

• Lots of the 2007 patches are to make upgrade easier

• http://technet.microsoft.com/en-us/office/sharepointserver/bb735839

• Why if you are doing 2010 wouldn’t you start patched?

• http://technet.microsoft.com/en-US/sharepoint/ff800847.aspx

• Slipstream install

• http://www.toddklindt.com/SP2010Slipstream

SP2007 - Stsadm.exe –o preupgradecheck • Available in v3 SP2 and later

• Updated in multiple v3 CUs

• Read only

• Provides key information for upgrade

• Farm configuration

• Possible issues

• Orphans

• Modified databases

• Missing customizations

• Large lists

Screenshot of report

Database Attach

• Content database

• Profile service database

• Project service database

• Configuration

• Search

Test-SPContentDatabase

• Can be used on 2007 or 2010 database

• Read only

• Safe

• Can be ran often

Database Attach Steps

• Backup 2007 Content DB

• Restore to SharePoint 2010 SQL Server, using SQL Tools

• Test-SPContentDatabase –name wss_content_2007 –webapplication http://2010webapp

• Mount-SPContentDatabase –name wss_content_2007 –webapplication http://2010webapp

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

What is “Visual Upgrade”

• Data and code upgrade happens all at once

• Site UI has two modes: this version and previous version

• Pages and components make the decision at runtime, and it’s safe by default

Logging

• 14\logs

• Upgrade log per session 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.

Correlation IDs

MSDN ULSViewer

• Allows you to scroll ULS logs in real time.

• While scrolling you can:

• Filter

• Color code

• Open multiple locations

• A must have!

• http://archive.msdn.microsoft.com/ULSViewer

PowerShell and ULS logs

• Start-Transcript

• New-SPLogFile

• Closes out current ULS log and creates new log

• Get-SPLogEvent

• Allows you to query log files for specific criteria

• Merge-SPLogFile

• Combine log files from across the farm into one log

• Don’t forget help with examples

The Fab 40

• http://technet.microsoft.com/en-us/windowsserver/sharepoint/bb407286.aspx

• Commonly referred to as the devil.

• If you have them in 2007 it is best to leave them there.

• Delete all webs that are built using these templates

• Avoid putting them on 2010 at all costs

Custom themes in 2007

• Branding is all new in SharePoint 2010 and you should plan accordingly

• Custom themes will not upgrade but if you have them in 2007 you must install them on 2010 server or you may have problems converting to v4 UI

FeatureAdmin

• http://featureadmin.codeplex.com/

• Great tool for finding missing/problem Features and removing them

• Has 2007 and 2010 version

Remove Features with PowerShell

• http://get-spscripts.com/2011/06/removing-features-from-content-database.html

• PowerShell finds all webs and/or site collections using a specific Feature. Can also forcibly deactivate the Feature.

Diagnose missing setup files

• http://get-spscripts.com/2011/06/diagnosing-missingsetupfile-issues-from.html

• This command will expose to you how to find missing setup files by looking at the SQL Database.

• Remember querying and/or editing a SharePoint database is not supported. Only use this is a test environment to find webs/site collections that need corrected.

Diagnose missing web parts

• http://get-spscripts.com/2011/08/diagnose-missingwebpart-and.html

• This script helps you to discover missing web parts by looking at the SQL database.

• Remember querying and/or editing a SharePoint database is not supported. Only use this is a test environment to find webs/site collections that need corrected.

Thanks

Please fill out your evaluations

And turn yourself around