The document discusses preparing for and performing an upgrade from Microsoft SharePoint Portal Server 2003 or Windows SharePoint Services 2.0 to Microsoft Office SharePoint Server 2007. It covers running prescan to identify issues, various upgrade methods like in-place, gradual, and content database migration. Post-upgrade considerations include customizations and configurations that need to be reapplied. Tools from partners can help with tasks like migrating customizations.

2. OFC304Microsoft Windows SharePoint Services and Microsoft SharePoint Portal Server 2003 Upgrade and Migration (Level 300)Chandima Kulathilake (Microsoft MVP - Microsoft Office SharePoint Server)http://www.chandima.net/Blog/Solutions ConsultantProvoke Solutionshttp://www.provoke.co.nz

3. Upgrade Preparation PRESCAN and Disk ConsiderationsUpgrade Methods and OptionsIn-Place, Gradual and Content DB MigrationPost-Upgrade ConsiderationsCustomizations, ContentPartner Upgrade ToolsSummaryQ & ASession Objectives and Agenda

4. Upgrade/Migration PathContent ManagementServer 2002Microsoft Office SharePoint Server 2007 SharePoint PortalServer 2003Windows SharePointServices 2.0Windows SharePointServices 3.0

5. Preparing for UpgradeScope and plan your upgrade Review Hardware End of Life, plan for upgrade capacity disk space, memory, processorTest your upgrade and estimate your upgrade durationReview customizations Keep or decommission customizationsCleanupRemove orphans, increase close quotas, remove locksService offeringRedesign, training, communication plan

6. PrerequisitesDo a backup (SQL or STSADM) Make sure you know how to recover from backupGet all SharePoint servers to Service Pack 2Use SPSiteManager from SharePoint Utility Suite v2.5 with the -analyze option to find anywhere you violate the capacity guidelineshttp://www.microsoft.com/sharepoint/downloads/components/detail.asp?a1=724Run prescan.exe early and repeat as necessaryPRESCAN IS YOUR FRIEND!

7. Running Prescan.exeSharePoint Server: prescan.exe /c preupgradescanconfig.xml /allWindows SharePoint Services: prescan.exe /allPrescan Log and Summary created in \%temp%\

8. What Will Prescan find?Sites based on site templates: Site Template Upgrade Kithttp://www.microsoft.com/downloads/details.aspx?FamilyID=a70bd8f8-a0f0-4d00-9010-8e40b7c98f68&displaylang=en Sites based on custom site definitionsUn-ghosted pagesOrphaned objectsCustom Web PartsSites that need language packs

10. PrescanExample of good Prescan results07/19/2006 17:17:01 Scan finished without failure07/19/2006 17:17:01 Number of sites skipped (already scanned): 007/19/2006 17:17:01 Number of sites scanned: 107/19/2006 17:17:01 Number of broken sites: 007/19/2006 17:17:01 Number of webs scanned: 1307/19/2006 17:17:01 Number of broken webs: 007/19/2006 17:17:01 Number of webs using custom template: 007/19/2006 17:17:01 Number of pages scanned: 007/19/2006 17:17:01 Number of unghosted pages: 63

11. Issues Found with Prescan?Site/List not scanned error at the end of the logSolution: Post-SP2 HotfixUpdateListSchemaInAllWebs() Method not foundSolution: Install SP2Virtual server is not in a ready stateSolution: Run it against v2 Virtual serverGreat resource for errors and resolutionshttp://blogs.technet.com/wbaer/archive/2006/12/22/prescan-errors-what-they-mean.aspx

12. Core Upgrade MethodsIn-Place Upgrade Gradual Upgrade: Side by Side UpgradeContent DB Migration: Upgrade Into Separate Farm

13. In Place UpgradeProsSimple and fast upgradeBest for smaller or non-production environmentsConsEnvironment offline during upgradeRiskier in large environmentsUpgrade fails if it encounters errors; -fix then rerunNot recommended for most deploymentsEven for customers whose production environment is perfect for this scenario, I still recommend gradual method. Why? Lack of flexibility and recoverability

14. Database MappingV2 Config DBV3 Config DBV3 Content DBsV2 Content DBsV2 Search and User Profiles DBsSSP DBSearch DB

15. Gradual UpgradeProsOld and new SharePoint versions run in parallelAllows upgrade with minimal downtimeOnly the site collection you are upgrading is unavailableCan roll back upgrades per site collectionConsRedirector could cause user confusionUses URL redirects which aren’t compatible with Microsoft Office and most other applicationsAdditional impact from two SharePoint versionsRequires lots of extra SQL storage space

16. Gradual Upgrade Processhttp://WSShttp://WSShttp://WSSold WSS FarmWSS 2003Web AppWSS 2007Web App SQL InstanceConfigContentContentConfigTemp

17. Gradual Upgrade URL RedirectionCurrent URL: http://portal.company.comDuring upgrade, define temporary URL http://portal.company.com:8080 or http://temp-portal.company.comAll v2 content moved to temporary URLv3 automatically redirects requests to temp URL using 302 redirectsAs each site collection is upgraded v3 content is placed at current URLv2 content still available at temp URL

18. Gradual Upgrade On existing hardware, install SP2, .NET Framework 3.0, then run PrescanPrepare URL Redirect DomainInstall Binaries and Choose Gradual Upgrade optionRun Configuration Wizard to setup a new farmInstall Language PacksDeploy Upgrade Definition, Site Definition and Feature FilesDeploy Custom Web Part Packages and any other custom code (only if in Bin directory)Upgrade steps

19. Gradual UpgradeReview log files and resolve any issuesRepeat setup and upgrade on each server in the farmStart content upgrade thru UI or stsadmReview your upgraded contentIf customized sites, reset pages to 2007 site definition versionsFix issues and reapply customizations using SharePoint DesignerIf upgrade result is undesirable, revert to 2003 siteUpgrade steps

20. Gradual UpgradeWhen upgrade result is undesirable, “revert” deletes 2007and resets redirect to 2003Confirm 2003 site still exists before reverting to itRevert to 2003 via UI or command lineUI: Select Sites for Upgrade > Revert SiteCommand line: stsadm –o upgrade –revertOnce complete, re-upgrade originalUse SharePoint Designer to merge changes from “fixed”and re-upgraded versionsRevert to 2003

21. Gradual UpgradeBusiness/Customer approvalRemoves gradual upgrade redirectorYou can remove SharePoint 2003 afterwardsYou can still upgrade using database attach methodFinalize Upgrade

22. Gradual Upgrade Works best for staging environmentEnvironments with heavy customizationsRecommended for large databases and site collectionsUpgrade a subset of site collections only Environments requiring minimal migration windowDEMO – Gradual Upgrade!Scenarios

23. Content DB Attach UpgradeProsFast upgrade methodBest option if you have 1000s of site collectionsConsYou must redeploy custom configurationInstall Web PartsDefine inclusion rulesSetup search and related componentsNote: This does still require Prescan. Required for scalable hosting mode/account creation mode, and host header mode deployments

24. – SQL CPU– SQL Disk I/OSQL Server2007 Farm2003 Farm2007Config2003Config2003Content2003Content2007ContentContent DB Migration

25. Content DB Migration StepsCreate new 2007 farm on clean hardwareInstall prerequisitesConfigure farm-level settingsCreate a new Web application for each 2007 virtual serverManually re-apply configuration settingsEnsure all inclusions re-created in 2007 (required)Deploy Upgrade Definition, Site Definition and Feature FilesDeploy custom Web Parts to GAC or BIN

26. Content DB Migration StepsRun Prescan on farm or Web application and correct any issuesBack up 2003 content database using SQLRestore backup to copy in 2007 farmAdd content DB to Web application via command lineEnsure root site included in first databasestsadm –o addcontentdbUpgrade triggers automatically, runs until it completesFor large databases, command line preferableReview log files for any issuesRepeat for all additional content and search/user profile databasesstsadm –o restoresspContinued

27. Content DB MigrationMoving to new hardware or a new architecture Customers who need to maximize upgrade throughputRequired for Scalable Hosting Mode or Active Directory Account Creation ModeRecommended for large farmsScenarios

28. Methods in a Nutshell

29. Need more methods?Content Migration UpgradeMulti Threaded Database AttachVirtual In Place UpgradeMigrate Then Upgradehttp://blogs.msdn.com/joelo/archive/2007/05/22/3-methods-to-upgrade-let-me-give-you-4-more.aspx

30. SQL InstanceDatabase Attach on SteroidsMultithreaded DB Attach2007 Farm2007 Farm2007 Farm2003 Farm2007 Farm2007 Farm..

31. Virtual UpgradeBuild V2 Virtual Server (Pre migration)

32. Build V3 Virtual Server

33. Take STSADM backups from V2 server

34. Restore to V2 Pre migration and clean up

35. Run PRESCAN!

36. Backup DB

37. Run STSADM –o attachcontentdb into V3 Pre Migration or V3 UAT

38. Take STSADM backups

39. Restore to new V3 PRD serverCustomization Considerations

40. Changes to SharePoint SearchUnchangedCustom content sourcesCrawl rulesUpgraded but should be checked for conflictsCustom crawl file typesChangedScopes are lost, must recreateOnly 1 index now, default in SharePoint Server Docicon.xml modifications must be redoneThesaurus/noise file modifications must be redoneSearch schedule lost, must recreateIf using gradual upgrade both v2 and v3 index will be running Disable v2 indexer ASAP to reduce strain on hardware

41. Other SharePoint Server-specific IssuesPortal alerts are lost during upgrade (site alerts are retained)Link listing: upgraded to a special links list called listingsContent listing: upgraded to news article pageBuckets (“c12”) are moved to real URLIf conflict, number appended starting with zerohttp://portal/c12/finance becomes http://portal/finance (retains structure)Areas are upgraded to publishing sitesAfter upgrade you can only create publishing sites as subsite can be changed http://msmvps.com/blogs/shane/archive/2007/02/08/moss-after-an-upgrade-you-can-only-create-publishing-sub-sites.aspx

42. Common IssuesLocal administrator on server no longer has full access to SharePointCan be re-granted http://msmvps.com/blogs/shane/archive/2007/01/21/become-administrator-of-the-entire-web-application.aspxNew blocked file typesASMX, REM, RESX, SOAP, ASHXE-mail enabled document libraries don’t work Look at new feature “Incoming e-mail”

43. More Common IssuesOffice Web Components not available in 2007Discussion lists are changedMultithreaded discussion upgraded to single threadSite Directory now creates sites (sub-sites)

44. FrontPage CustomizationsImportant consideration: keep customizations or move to 2007Custom pages kept by default during upgradeBe aware: customized pages do not match rest of site“Reset to Site Definition” Returns page to layout in site definition Option exists to reset all pages during Gradual upgrade Available in site settings or within SharePoint Designer

45. 60\TEMPLATE\1033\STS\default.aspxUpgrade Effects on Ghosting60\Template12\Template12\TEMPLATE\SiteTemplates\STS\default.aspx2007 Farm2003 Farm SQL InstanceContentConfig

46. Custom Web PartsMost will work post-upgradeTest in Windows SharePoint Services 2003 SP2 with ASP.NET 2.0 Must re-build custom parts if you used ASP.NET 1.1 “obfuscation” tools Must re-deploy Web Parts ifMoving to a new server farm (Content DB Migration)Web Part in the \bin (Gradual Upgrade)Deploying Web Partsstsadm –o addwppack

47. Troubleshooting TipsPrescan logs%temp%Prescan.logPrescan Report and SummaryLog files Upgrade and Server logsLogs are in\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\LogsWatch the Event Viewer

48. Partners Helping You UpgradeCorasWorksMigratorRe-ghost multiple sites at onceMigrate customizations and Web Parts to sites post upgradeHelps you add layouts, master pages, Web Parts en masseEchoHelps you quickly roll out customizations and settings and permissions across your farm with no site collection boundaries2007 version coming soonAvePointDocAveUsed to connect to 2003 and move content to 2007 without dependencies on customizations. Quickly and easily move your lists and libraries into a clean slate (out-of-box site definitions)

49. TakeawaysPrepare, plan and test your customizations!Become familiar with Prescan and upgradeConsider customization policies in the new platform, using features over site definitions

50. ReferencesMy Blog: http://www.chandima.net/Blog/Will make all resource links and slides available on blog!Migration and Upgrade Information for SharePoint Developershttp://msdn2.microsoft.com/en-us/office/aa905505.aspxMigration and Upgrade Information for SharePoint Server (IT Pros)http://technet.microsoft.com/en-us/sharepointserver/bb421259.aspxUpgrade Documentation http://technet2.microsoft.com/Office/en-us/library/396c85d9-4b86-484e-9cc5-f6c4d725c5781033.mspx?mfr=trueUpgrade Toolkit for Windows SharePoint Services Sites and Templates Guidehttp://www.microsoft.com/technet/solutionaccelerators/collaboration/default.mspxUpgrade in WSS SDK http://msdn2.microsoft.com/en-us/library/ms460185.aspxFix your Orphans HotFixesrepair content databases in Windows SharePoint Services http://support.microsoft.com/kb/918744Spsadm.exe command line tool that you can use to clean up orphaned items in the configuration database in SharePoint Portal Server 2003 http://support.microsoft.com/kb/918742/

51. ReferencesSupportability2003 Best Practices to ensure upgradeability http://msdn2.microsoft.com/en-us/library/ms916859.aspxKB Article on Site Definition Supportability in 2003 http://support.microsoft.com/Default.aspx?id=898631Supported and unsupported scenarios for working with custom site definitions and custom area definitions in Windows SharePoint Services and in SharePoint Portal Server 2003 http://support.microsoft.com/kb/898631/en-usCommunity ToolsSharePoint Configuration Analyzer http://www.microsoft.com/downloads/details.aspx?FamilyID=918f8c18-89dc-4b47-82ca-34b393ea70e1&DisplayLang=enSharePoint Utility http://www.microsoft.com/sharepoint/downloads/components/detail.asp?a1=724SPReporthttp://workspaces.gotdotnet.com/spreportsManaging SharePoint Products and Technologies Performance at Microsoft http://www.microsoft.com/technet/itshowcase/content/spsperfnote.mspx#ETKAEMicrosoft SQL Server Report Pack for Microsoft Office SharePoint Portal Server 2003 http://www.microsoft.com/downloads/details.aspx?FamilyID=49159368-544b-4b09-8eed-4844b4e33d3d&DisplayLang=enBlogsResources and Recommendations for Upgrading Site Definitions and Site Templates http://blogs.msdn.com/joelo/archive/2007/01/03/resources-and-recommendations-for-upgrading-site-definitions-and-site-templates.aspxUpgrade Content IT Pros may not have seen http://blogs.msdn.com/joelo/archive/2006/12/06/upgrade-content-it-pros-may-not-have-seen.aspxOther Upgrade Topics from Joel’s Bloghttp://blogs.msdn.com/joelo/archive/tags/Upgrade/default.aspx

52. Orphaned ObjectsWindows SharePoint Services Content DB orphans Post-SP2 Hotfix, KB 918743 and KB 918744stsadm -o databaserepair -url http://WSSSite -databasename DatabaseNamestsadm -o databaserepair -url http://WSSSite -databasename DatabaseName –deletecorruptionSharePoint Server Config DB orphansPost SP2 Hotfix, KB 918742spsadm –o repairorphans http://PortalSiteWindows SharePoint Services Config DB orphansRemove and then reattach the content databases on the virtual server

53. Effect of Upgrades: Low Customization Site (Original)

54. Effect of Upgrades:Low Customization Site (Upgraded)

55. Effect of Upgrades:Low Customization Site (Re-Ghosted)

56. Effect of Upgrades:High Customization Site (Original)

57. Effect of Upgrades:High Customization Site (Upgraded)

58. Effect of Upgrades:High Customization Site (Re-Ghosted)

59. Effect of Upgrades:Themed Site (Original)

60. Effect of Upgrades:Themed Site (Upgraded)

61. Q&APlease fill the evaluation form!Thank You

62. ResourcesTechnical Communities, Webcasts, Blogs, Chats & User Groupshttp://www.microsoft.com/communities/default.mspxMicrosoft Learning and Certificationhttp://www.microsoft.com/learning/default.mspxMicrosoft Developer Network (MSDN) & TechNet http://microsoft.com/msdnhttp://microsoft.com/technetTrial Software and Virtual Labshttp://www.microsoft.com/technet/downloads/trials/default.mspxNew Zealand Technical Communities, Webcasts, Blogs, Chats & User Groupshttp://www.mscommunities.net.nz

63. The Microsoft Office SharePoint Conference 2008March 3rd – 6th 2008 at the Washington State Convention and Trade Center, Seattle, USASign up for more information and registration notification at http://www.mssharepointconference.comAnnouncing!

64. Complete an evaluation on CommNet and enter to win!