This session will cover how to plan for upgrading your SharePoint 2003 and 2007 server farms to SharePoint 2010. We will cover the tools available today and how you can test your existing SharePoint 2007 deployment for upgrade compatibility. We will also cover important planning steps for a successful upgrade project and how to upgrade using the available upgrade paths.

2. Chandima Kulathilake Solution Architect Knowledge Cue SharePoint Upgrade Deep Dive SESSION CODE: OFS308

3. Who am I? Chandima – aka “Chan” @chandimak on twitter Solutions Architect @ Knowledge Cue- SharePoint Consulting in New Zealand Started with SharePoint 2001... It’s been a great journey SharePoint MVP since 2007 www.chandima.net/blog chan@knowledgecue.com

4. Knowledge Cue Help with strategy and planning for SharePoint Sense making for large enterprise projects Pre RFP stage expectation setting SharePoint best practices/ “real world” balancing act Consulting and deployment support Microsoft certified SharePoint experts @knowledgecue on twitter www.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 deployment Upgrade planning and upgrade tasks What you can and can’t upgrade Recommendations for SP2010

6. Upgrade Planning Cycle

7. Upgrade Paths WSS2/SPS 2003 > SharePoint 2007 > SharePoint 2010 MCMS 2002 > SharePoint 2007 > SharePoint 2010 Project Server 2003 > Project 2007 > (SharePoint) Project 2010

8. Getting Ready – Requirements SharePoint Server 2010 and SharePoint Foundation 64-bit only 64-bit Windows Server 2008 SP2 or 64-bit Windows Server 2008 R2 64-bit SQL Server 2008 SP1 + CU2 or CU5 64-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 > 2010 Upgrade – Apply new updates and or Service Packs to SharePoint Server 2007 or upgrade to SP2010

10. Preparing the servers SQL 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 command Windows 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? Identify Document Plan Review Identify migration path to 64bit Review future requirements

12. Auditing Tools for 2007 Farms Central Administration in SharePoint SharePoint Administration Toolkit V4.0 (SPDiag) http://tinyurl.com/SPAdminKit Using STSADM and PowerShell Pre-Upgrade Check Run the STSADM –o preupgradecheckcommand prior to upgrade (many times) Run STSADM –o enumallwebs [parameters] Using SharePoint Manager from CarstenKeutmann – http://www.codeplex.com/spm

13. Demo 1 - Conducting a PREUPGRADE Audit

14. Using STSADM STSADM –o enumcontentdbs STSADM – o enumallwebs (SP 2 + Updates) STSADM – o enumsolutions STSADM – o preupgradecheck

15. Post Audit Tasks Server Administrators – prepare servers and plan SP2010 deployment architecture Developers – Re-evaluate custom code solutions and files for SP2010 compatibility Project Managers – Review upgrade project plans and estimates – user training etc.

16. VseWSS Upgrade Tool - Developers

17. Also Consider… Move only “content” to brand new farm Re-organise Standardise Clean up Decommission – 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 Versions Primarily user driven, OM operations or tools help Cleanup Templates, Features, & Web Parts Primarily user driven, OM operations or tools help Repair Data Issues stsadm -o DatabaseRepair [-deletecorruption] stsadm -o ForceDeleteList stsadm -o VariationsFixupTool

19. Upgrade Methods

20. In-Place Upgrade Farm offline during upgrade Configuration and all content upgraded No option to roll-back (only if you backup the whole farm)

21. In-Place Upgrade Install SharePoint Binaries on the Server with CA first Run the Configuration Wizard The 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 Very hard to predict – even if you test multiple times Recommended for one-off tests only Good for testing Code and extracting WSP solutions to Visual Studio ALL Databases will be GUID based My recommendation – Don’t do it for a PRODUCTION deployment!

23. DEMO 2 – In Place Upgrade

24. Database Attach Upgrade New hardware and new farm for SP 2010 Install binaries first and configure required services Re-deploy customisations (WSP files) manually Attach content databases individually

25. Upgrade Sequence – Database Attach Build new SP2010 farm Create Web Application(s) Detach content databases from SP2007 farm Attach content databases to SP2010 farm Test (repeat)

26. Database attach Content databases SSP database (Upgraded to User Profiles_

27. DEMO 3 – Database Attach Upgrade

28. Database Attach – What you Get Chance to re-organise Remove unwanted sites Phased upgrades Plan 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 databases Set content databases to read-only in SQL server

33. Upgrade – HYBRID Approaches Hybrid 2 – Detach databases Detach all content databases Run in place upgrade and update farm binaries to SP2010 Configure required Service Applications Attach each content database individually

35. Upgrade – What to do for Developers Covert your custom code to deployable solutions http://tinyurl.com/SP2010Solutions Visual Studio 2010 support for SharePoint 2010 development Follow Coding Best Practices http://tinyurl.com/CodingBPSP07 Download SP2010 SDK http://tinyurl.com/SP2010DEVSDK

36. Upgrade – What to do for Administrators Large content databases and site collections will take longer to upgrade Split 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 Gary Lapointe’s convert sub site to site collection command Archive off any Site Collections, Webs, or Lists that are no longer necessary Test your Disaster Recovery strategy before upgrading

37. Upgrade Gotchas 3rd Party vendor solutions – custom development 3rd Party products – Aggregation web parts or similar Forgotten sites with no owners

38. Migration strategies DESTINATION (64bit) FARM B SOURCE (32bit) FARM A Tier C – Phase 3 x86 (MOSSWEB1) x86 (MOSSWEB2) x64 (SPWEB1) x64 (SPWEB2) Tier B – Phase 2 Tier A – Phase 1 x86 (SQL) x64 (SQLSERVER08) x86 (MOSSAPP1) x64 (SPAPP1)

40. Web and App Servers

41. SQL Cluster is SQL 2008

42. Log Shipping of all content databases

43. SAN Level Replication

44. 6000 + users

45. 1800 My sites (Phased rollout)

46. RPO = 0 (Zero data loss)

47. F5 Load balancers

48. Availability – High

49. 8am – 8pm (Critical)Web Front End Servers (WFE) Application Servers (APP) Database Backend (Dedicated SQL cluster)

51. The Plan – Getting to 2010 Build new SP2007 disposable VM’s Get Full copies of PRD databases (Fortnightly) Once SP2007 VM’s are ready run in place upgrade to SP2010 See what breaks – get developers to work on fixes Stop all SP2007 on-going development (3 month freeze) Start using SP2010/VS2010 development Business impact mitigation via Comms plan and training

52. The Plan – Core Infrastructure Layer Upgrade the Physical SQL Cluster to SQL 2008 R2 Build new VM farms to match DEV (Multiple 2010 VMs) PPTE (Pre-Production/Test) (2 VMs) Production (3 VMs) DR (3VMs) Total data capacity 500GB for just the VM’s RAM 48GB total available required on VM cluster for upgrade VMs

53. The Plan - Architecture Run workshops for Service Application Architecture Refactor Information Architecture Content Type Hub with Managed Metadata site – Web Application All other Web apps, site collections consume meta data from Content type hub Move/Migrate or re-create managed metadata Prepare tenant architecture and hosting (Multi tenancy)

54. The Plan - Development Refactor code solutions Deploy 2010 Solutions (Upgraded WSP) Re-develop if required Test > Test and Test with upgraded Production content

55. The Plan “Migration” of Data First phase – My sites – low business impact Second phase – Applications Multiple applications 2007 and 2010 in parallel farms

56. The Plan – Final Steps Once all my sites and applications are on 2010 shut down 2007 physical farm Rebuild and configure PRD physical farm for SP2010 Point 2010 content databases to new SP2010 physical farm Get rid of the temp VM’s and reclaim the storage and VM capacity

57. Resources Upgrade Resource Centre (TechNet) http://tinyurl.com/SP2010Upgrade Upgrade planning blog post series http://tinyurl.com/SP2010Blogs

58. 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 – Wellington When : September 29th 9.00am onwards Email : sharepoint@knowledgecue.com to register your interest Cost : NONE!

59. Thank you Q and A – Meet me outside or chan@knowledgecue.com Lots of improvements – Features solutions Lots of complexity – Architecture and Planning “with great power comes greater responsibility”

60. Slide for Showing Software Code Use this layout to show software code The font is Consolas, a monospace font The slide doesn’t use bullets but levels can be indented using the “Increase List Level” icon on the Home menu To use straight quotes " instead of smart quotes ”, do this: Click on the Office Button in the upper left corner At the bottom of the menu, choose PowerPoint Options From the left pane, select Proofing Click on the AutoCorrect Options button Select the AutoFormat As You Type tab, and deselect “Straight quotes” with “smart quotes”. Then Click OK.

61. © 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.