Chandima KulathilakeSolution ArchitectKnowledge Cue

SharePoint Upgrade Deep Dive

SESSION CODE: OFS308

3

Who am I?

Chandima – aka “Chan” @chandimak on twitterSolutions Architect @ Knowledge Cue- SharePoint Consulting in New ZealandStarted with SharePoint 2001... It’s been a great journey SharePoint MVP since 2007www.chandima.net/blogchan@knowledgecue.com

4

Knowledge Cue

Help with strategy and planning for SharePointSense making for large enterprise projectsPre RFP stage expectation settingSharePoint best practices/ “real world” balancing actConsulting and deployment supportMicrosoft certified SharePoint experts@knowledgecue on twitterwww.knowledgecue.co.nz

5

Agenda

Getting your existing SharePoint 2003 > 2007 farm ready for SharePoint 2010

Applying Software updates (Service Pack 2 and CU) Testing your existing deployment for SharePoint 2010 readiness

Auditing what’s in your current deploymentUpgrade planning and upgrade tasks

What you can and can’t upgradeRecommendations for SP2010

6

Upgrade Planning Cycle

Learn

Prepare

TestImplement

Validate

7

Upgrade Paths

WSS2/SPS 2003 > SharePoint 2007 > SharePoint 2010MCMS 2002 > SharePoint 2007 > SharePoint 2010Project Server 2003 > Project 2007 > (SharePoint) Project 2010

8

Getting Ready – Requirements

SharePoint Server 2010 and SharePoint Foundation 64-bit only64-bit Windows Server 2008 SP2 or 64-bit Windows Server 2008 R264-bit SQL Server 2008 SP1 + CU2 or CU564-bit SQL Server 2008 R2

Standard or Enterprise PowerPivot needs SQL 2008 R2

64-bit SQL Server 2005 + SP3 and CU3 (Supported)

http://tinyurl.com/SP2010SysReqs

9

Move, Migrate or Upgrade

Move - Use the procedures for moving a farm or components when you are changing to different hardware (more capacity, performance and x64)Migrate – From 32bit to 64bit or

SharePoint Content from 2003 to 2007 > 2010Upgrade – Apply new updates and or Service Packs to SharePoint Server 2007 or upgrade to SP2010

10

Preparing the serversSQL Server (64bit)

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

SharePoint Servers (64bit)SharePoint 2007 SP2 + October CU (or greater) – Recommend latest CU (June 2010)

October CU updates the preupgradecheck STSADM commandWindows Server 2008 Standard w/SP2 (or greater)WCF Hot fix (not part of the prerequisites installer)

Plan for sufficient disk space – Upgrades will need temp disk space (lots of)

11

Upgrade Planning

Evaluate – Where are you today?IdentifyDocumentPlanReview

Identify migration path to 64bitReview future requirements

12

Auditing Tools for 2007 Farms

Central Administration in SharePointSharePoint Administration Toolkit V4.0 (SPDiag) http://tinyurl.com/SPAdminKit Using STSADM and PowerShellPre-Upgrade Check

Run the STSADM –o preupgradecheck command prior to upgrade (many times)Run STSADM –o enumallwebs [parameters]

Using SharePoint Manager from Carsten Keutmann – http://www.codeplex.com/spm

DEMO 1 - CONDUCTING A PREUPGRADE AUDIT

14

Using STSADM

STSADM –o enumcontentdbsSTSADM – o enumallwebs (SP 2 + Updates)STSADM – o enumsolutionsSTSADM – o preupgradecheck

15

Post Audit Tasks

Server Administrators – prepare servers and plan SP2010 deployment architectureDevelopers – Re-evaluate custom code solutions and files for SP2010 compatibilityProject Managers – Review upgrade project plans and estimates – user training etc.

16

VseWSS Upgrade Tool - Developers

17

Also Consider…

Move only “content” to brand new farmRe-organiseStandardiseClean upDecommission – old hardware

18

Environment CleanupSpring cleaning for a healthy farm

Delete Stale Sites and Webs (Backup First )stsadm -o DeleteSite [-force] [-gradualdelete]stsadm -o DeleteWeb [-force]

Remove Extraneous Document VersionsPrimarily user driven, OM operations or tools help

Cleanup Templates, Features, & Web PartsPrimarily user driven, OM operations or tools help

Repair Data Issuesstsadm -o DatabaseRepair [-deletecorruption]stsadm -o ForceDeleteListstsadm -o VariationsFixupTool

19

In-Place Upgrade Database Attach Upgrade

Hybrid 1:

Read-Only Database Upgrade

Hybrid 2:

Detach Database Upgrade

Upgrade Methods

20

In-Place Upgrade

Farm offline during upgradeConfiguration and all content upgradedNo option to roll-back (only if you backup the whole farm)

21

In-Place Upgrade

Install SharePoint Binaries on the Server with CA firstRun the Configuration WizardThe SSP database is upgraded and data is copied into new user profiles and taxonomy databases. No option to roll-back (only if you backup the whole farm)

22

In-Place Upgrade

My recommendation – Don’t do it for a PRODUCTION deployment!

Very hard to predict – even if you test multiple timesRecommended for one-off tests onlyGood for testing Code and extracting WSP solutions to Visual StudioALL Databases will be GUID based

DEMO 2 – IN PLACE UPGRADE

24

Database Attach UpgradeNew hardware and new farm for SP 2010Install binaries first and configure required servicesRe-deploy customisations (WSP files) manuallyAttach content databases individually

25

Upgrade Sequence – Database Attach

Build new SP2010 farmCreate Web Application(s)Detach content databases from SP2007 farmAttach content databases to SP2010 farmTest (repeat)

26

Database attach

User requests

Database server A (content DBs)

Database server B (services DBs)

Application servers

Database server C (config DB)

Front-end Web servers

New farm http://contoso2

Content database 1-n

SSP database

Content databases

SSP database(Upgraded to User Profiles_

DEMO 3 – DATABASE ATTACH UPGRADE

28

Database Attach – What you Get

Chance to re-organiseRemove unwanted sitesPhased upgradesPlan your Service Applications properly

29

Using PowerShell

Test-SPContentDatabase -Name -WebApplication [-AssignmentCollection ] [-DatabaseCredentials ] [-ServerInstance ]

Test-SPContentDatabase -Name My_Content_DB –Webapplication http://portal.abc.com

30

Test-SpContentDatabase

31

Mount-SPContentDatabase

32

Upgrade – HYBRID Approaches

Hybrid 1 – Read only databasesSet content databases to read-only in SQL server

33

Upgrade – HYBRID Approaches

Hybrid 2 – Detach databasesDetach all content databasesRun in place upgrade and update farm binaries to SP2010Configure required Service ApplicationsAttach each content database individually

34

35

Upgrade – What to do for Developers

Covert your custom code to deployable solutionshttp://tinyurl.com/SP2010Solutions

Visual Studio 2010 support for SharePoint 2010 developmentFollow Coding Best Practices

http://tinyurl.com/CodingBPSP07Download SP2010 SDK

http://tinyurl.com/SP2010DEVSDK

36

Upgrade – What to do for AdministratorsLarge content databases and site collections will take longer to upgradeSplit Content Databases and/or Site Collections into smaller units prior to upgradeSTSADM’s mergecontentdbs command can be used to move a Site Collection to a different Content Database

Gary Lapointe’s convert sub site to site collection commandArchive off any Site Collections, Webs, or Lists that are no longer necessaryTest your Disaster Recovery strategy before upgrading

37

Upgrade Gotchas

3rd Party vendor solutions – custom development3rd Party products – Aggregation web parts or similarForgotten sites with no owners

38

Tier C – Phase 3

x86 (MOSSWEB1) x86 (MOSSWEB2) x64 (SPWEB1) x64 (SPWEB2)

Tier A – Phase 1

x64 (SQLSERVER08)x86 (SQL)

Migration strategiesSOURCE (32bit) FARM A DESTINATION (64bit) FARM B

Tier B – Phase 2

x86 (MOSSAPP1) x64 (SPAPP1)

47

Resources

Upgrade Resource Centre (TechNet)http://tinyurl.com/SP2010Upgrade

Upgrade planning blog post serieshttp://tinyurl.com/SP2010Blogs

48

Announcing – SharePoint Day

A Business Track – Hosted by Mark Orange (4 sessions)A Technical Solution Track – Hosted by Chandima Kulathilake (4 sessions)Where : Hotel Intercontinental – WellingtonWhen : September 29th 9.00am onwardsEmail : sharepoint@knowledgecue.com to register your interestCost : NONE!

49

Thank you

Q and A – Meet me outside or chan@knowledgecue.comLots of improvements – Features solutionsLots of complexity – Architecture and Planning

“with great power comes greater responsibility”

© 2008 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED

OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.