Upgrade to WSS 3.0 and SharePoint Server 2007

2. IW310 Upgrade to WSS 3.0 and SharePoint Server 2007 Joel Oleson http://blogs.msdn.com/joelo Sr. Technical Product Manager Microsoft Corporation

3. Agenda • Upgrade Preparation • Prescan and Disk considerations • Upgrade Methods and Options • In-Place, Gradual and Content DB Migration • Post Upgrade Considerations • Customizations, Content • Partner Upgrade Tools • Summary • Q & A

4. Upgrade/Migration Path Content Management Server 2002 Microsoft Office SharePoint Server 2007 (MOSS 2007) SharePoint Portal Server 2003 Windows SharePoint Services 2.0 Windows SharePoint Services 3.0

5. Preparing for Upgrade • Scope and Plan your upgrade • Review Hardware End of Life, plan for upgrade capacity; disk space, memory, processor • Test your upgrade & estimate your upgrade duration • Review customizations • Keep or Decommission customizations • Cleanup • Remove Orphans, increase close quotas, remove locks, • Service Offering • Redesign, Training, Communication plan

6. Prerequisites • Do a backup • Make sure you know how to recover from backup • Get all SharePoint Servers to Service Pack 2 • Use SPSiteManager from SPUtil v2.5 with the –analyze option to find anywhere you violate the capacity guidelines • http://www.microsoft.com/sharepoint/downloads/components/detail.asp?a1=724 • Run prescan.exe early and repeat as necessary

7. Running Prescan.exe • SPS: prescan.exe /c preupgradescanconfig.xml /all • WSS: prescan.exe /all • PreScan Log and Summary created in \%temp%\

8. What will Prescan find? • Sites based on site templates - site template upgrade kit • Sites based on custom site definitions • Unghosted pages • Orphaned objects • Custom Web Parts • Sites than need language packs

10. Prescan • Example of good PreScan results: • 07/19/2006 17:17:01 Scan finished without failure. • 07/19/2006 17:17:01 Number of sites skipped (already scanned): 0 • 07/19/2006 17:17:01 Number of sites scanned: 1 • 07/19/2006 17:17:01 Number of broken sites: 0 • 07/19/2006 17:17:01 Number of webs scanned: 13 • 07/19/2006 17:17:01 Number of broken webs: 0 • 07/19/2006 17:17:01 Number of webs using custom template: 0 • 07/19/2006 17:17:01 Number of pages scanned: 0 • 07/19/2006 17:17:01 Number of unghosted pages: 63

11. Issues found with Pre-Scan? • Site/List not scanned error at the end of the log • Solution: Post SP2 Hotfix • UpdateListSchemaInAllWebs() Method not found • Solution: Install SP2 • Various WSS OM method failure from SPRequest object with File not found error • Solution: Install custom site definitions • Virtual server is not in a ready state • Solution: Run it against v2 Virtual server • Great resource for errors and resolutions: http://blogs.technet.com/wbaer/archive/2006/12/22/prescan-errors-what-they-mean.aspx

12. Upgrade Options • In-Place Upgrade • For small non production environments, offline while it runs (Not recommended for most environments) • Gradual Upgrade: Side by Side Upgrade • Granular control, one to many site collections at a time • Side-by-side; rollback to 2003 supported • More complex & resource intensive • Content DB Migration: Upgrade Into Separate Farm • Attach 2003 content db to 2007 farm & upgrade runs • 2003 farm stays available and untouched • Content only, requires new farm, has many manual steps

13. In Place Upgrade • Pros: • Simple and fast upgrade • Best for smaller or non production environments • Cons: • Environment offline during upgrade • Riskier in large environments • Upgrade Fails if it encounters errors -fix then rerun. • Not Recommended for Most Deployments • Even customers who's production environment is perfect for this scenario I still recommend gradual method. Why? Lack of flexibility and recoverability.

14. V2 Config DB V3 Config DB V2 Content DBs V3 Content DBs V2 Search and User Profiles DBs SSP DB Search DB Database Mapping

15. Gradual Upgrade • Pros: • Old and new SharePoint versions run in parallel • Allows upgrade with minimal downtime • Only the site collection you are upgrading is unavailable • Can roll-back upgrades per site collection • Cons: • Redirector could cause user confusion • Uses URL redirects which aren’t compatible with MS Office and most other applications • Additional impact from two SharePoint versions • Requires lots of extra SQL storage space

16. Gradual Upgrade Process http://WSS http://WSS http://WSSold WSS Farm WSS 2003 Web App WSS 2007 Web App SQL Instance Config Content Content Config Temp

17. Gradual Upgrade URL Redirection • Current URL http://portal.company.com • During upgrade define temporary URL • http://portal.company.com:8080 or • http://temp_portal.company.com • All v2 content moved to temporary URL • V3 automatically redirects requests to temp URL using 302 redirects • As each site collection is upgraded v3 content is placed at current URL • V2 content still available at temp URL

18. Gradual UpgradeUpgrade Steps • On existing hardware, install SP2, .NET Framework 3.0, then run Prescan • Prepare URL Redirect Domain • Install Binaries and Choose Gradual Upgrade Option • Run Configuration Wizard to setup a new farm • Install Language Packs • Deploy Upgrade Definition, Site Definition and Feature Files • Deploy Custom Web Part Packages and any other custom code (only if in Bin directory)

19. Gradual UpgradeUpgrade Steps • Review log files & resolve any issues • Repeat setup & upgrade on each server in the farm • Start content upgrade thru UI or stsadm • Review your upgraded content • If customized sites, reset pages to 2007 site definition versions • Fix issues and reapply customizations using SharePoint Designer • If upgrade result is undesirable, revert to 2003 site

20. Gradual UpgradeContent Upgrade – SQL CPU – SQL Disk I/O SQL Server 2007 Farm 2003 Farm 2003 Config 2007 Config 2003 Content 2007 Content Temp

21. Gradual Upgrade Revert to 2003 When upgrade result is undesirable, “revert” deletes 2007& resets redirect to 2003 Confirm 2003 site still exists before reverting to it Revert to 2003 via UI or command line UI: Select Sites for Upgrade > Revert Site Command line: stsadm –o upgrade –revert Once complete, re-upgrade original Use SharePoint designer to merge changes from “fixed”& re-upgraded versions

22. Gradual Upgrade Scenarios • Works best for Staging Environment • Environments with Heavy Customizations • Recommended for Large Databases and Site Collections • Upgrade a subset of Site Collections only • Environments requiring minimal migration window

23. Content DB Attach Upgrade • Pros: • Fast upgrade method • Best option if you have 1000s of site collections • Cons: • You must redeploy custom configuration: • Install web parts • Define inclusion rules • Setup search and related components • Note: This does still require Prescan. Required for scalable hosting mode/account creation mode, and host header mode deployments.

24. Content DB Migration – SQL CPU – SQL Disk I/O SQL Server 2007 Farm 2003 Farm 2003 Config 2007 Config 2003 Content 2003 Content 2007 Content

25. Create new 2007 farm on clean hardware Install prerequisites Configure farm-level settings Create a new web application for each 2007 virtual server Manually re-apply configuration settings Ensure all inclusions re-created in 2007 (required) Deploy Upgrade Definition, Site Definition and Feature Files Deploy custom web parts to GAC or BIN Content DB Migration Steps

26. Run Prescan on Farm or Web Application and correct any issues Back up 2003 content database using SQL Restore backup to copy in 2007 farm Add content db to web application via command line Ensure root site included in first database stsadm –o addcontentdb Upgrade triggers automatically, runs until it completes For large databases, command line preferable Review log files for any issues Repeat for all additional content and search/user profile databases stsadm –o restoressp Content DB Migration Stepscontinued

27. Content DB MigrationScenarios • Moving to new hardware or a new architecture • Customers who need to maximize upgrade throughput. • Required for Scalable Hosting Mode or Active Directory Account Creation Mode. • Recommended for Large Farms

28. Database Attach on Steroids SQL Instance 2007 Farm 2007 Farm 2007 Farm 2007 Farm 2007 Farm 2003 Farm . .

29. Summary

30. Customization Considerations

31. Changes to SPS Search • Unchanged • Custom content sources • Crawl rules • Upgraded but should be checked for conflicts • Custom crawl file types • Changed • Scopes are lost, must recreate • Only 1 index now, default in MOSS • Docicon.xml modifications must be redone • Thesaurus/noise file modifications must be redone • Search schedule lost, must recreate • If using gradual upgrade both v2 and v3 index will be running. Disable v2 indexer ASAP to reduce strain on hardware.

32. Other SPS specific issues • Portal alerts are lost during upgrade (site alerts are retained) • Link listing – upgraded to a special links list called listings • Content listing – upgraded to news article page • Buckets (“c12”) are moved to real URL. If conflict number appended starting with zero • http://portal/c12/finance become http://portal/finance (retains structure) • Areas are upgraded to publishing sites • After upgrade you can only create publishing sites as sub site can be changed http://msmvps.com/blogs/shane/archive/2007/02/08/moss-after-an-upgrade-you-can-only-create-publishing-sub-sites.aspx • Site Directory now creates sub-sites not separate site collections

33. SPS Site directory changes • Now creates sub sites instead of site collections like in 2003. Why? • Because some MOSS functionality only works within the same site collection (ex: Content Query Web Part) • Be careful with this. More info on site collection sizing • http://blogs.msdn.com/joelo/archive/2007/01/31/tips-on-site-collection-sizing.aspx • Want site directory to create site collection like in 2003? • http://blogs.msdn.com/joelo/archive/2006/08/18/705157.aspx • Want to move existing site directories to sub sites? • http://msmvps.com/blogs/shane/archive/2006/11/14/consolidating-site-collections-after-upgrading-sharepoint.aspx • Other improvements made to site directory to investigate.

34. Common issues • Local administrator on server no longer has full access to SharePoint • Can be regranted http://msmvps.com/blogs/shane/archive/2007/01/21/become-administrator-of-the-entire-web-application.aspx • New blocked file types • ASMX, REM, RESX, SOAP, ASHX • Hard coded URLS don’t work • Email enabled document libraries don’t work. Look at new feature “Incoming email” • Office Web Components not available in 2007 • More details - http://blogs.msdn.com/joelo/archive/2007/01/05/what-happened-to-the-office-web-components.aspx

35. FrontPage Customizations • Important consideration: keep customizations or move to 2007 • Custom pages kept by default during upgrade • Be 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

36. Resetting to Site Definition 2007 Farm 2003 Farm 2003 Config 2007 Config 2007 Content 2003 Content

37. Upgrade Effects on Ghosting 60\Template 12\Template 60\TEMPLATE\1033\ STS\default.aspx 12\TEMPLATE\ SiteTemplates\STS\ default.aspx 2007 Farm 2003 Farm SQL Instance Content Config

38. Custom Web Parts • Most will work post-upgrade • Test in WSS 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 if • Moving to a new server farm (Content DB Migration) • Web part in the \bin (Gradual Upgrade) • Deploying web parts • stsadm –o addwppack

39. Finalize Upgrade • Business/Customer approval • Removes gradual upgrade redirector • You can remove SharePoint 2003 afterwards • You can still upgrade using database attach method

40. Lessons Learned • Communicate upgrade schedule • Determine plan or policies: • Ghosting during upgrade • Upgrade priorities – exceptions process • Upgrade roll-backs – exceptions process • Determine whether to offer site previews • Choose gradual upgrade redirection URL wisely • Review and Retain upgrade logs after each upgrade

41. Troubleshooting Tips • Prescan logs • %temp% • Prescan.log • Prescan Report and Summary • Log files • Upgrade and Server logs • Logs are in: \Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Logs • Watch the Event Viewer

42. Partners helping you upgrade • CorasWorksMigrator • Reghost multiple sites at once • Migrate Customizations and web parts to sites post upgrade • Helps you add layouts, master pages, web parts, en masse • Echo • Helps you quickly roll out customizations and settings and permissions across your farm with no site collection boundaries • 2007 version coming soon • AvePointDocAve • Used 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).

43. Takeaways • Prepare, plan and test your customizations!! • Become familiar with prescan and upgrade • Consider customization policies in the new platform, using features over site definitions.

44. References • Migration and Upgrade Information for SharePoint Developers • http://msdn2.microsoft.com/en-us/office/aa905505.aspx • Migration and Upgrade Information for SharePoint Server (IT Pros) • http://technet.microsoft.com/en-us/sharepointserver/bb421259.aspx • Upgrade Documentation • http://technet2.microsoft.com/Office/en-us/library/396c85d9-4b86-484e-9cc5-f6c4d725c5781033.mspx?mfr=true • Upgrade Toolkit for Windows SharePoint Services Sites and Templates Guide • http://www.microsoft.com/technet/solutionaccelerators/collaboration/default.mspx • Upgrade in WSS SDK • http://msdn2.microsoft.com/en-us/library/ms460185.aspx • Fix your Orphans HotFixes • repair content databases in Windows SharePoint Services http://support.microsoft.com/kb/918744 • Spsadm.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/

45. References • Supportability • 2003 Best Practices to ensure upgradeability http://msdn2.microsoft.com/en-us/library/ms916859.aspx • KB Article on Site Definition supportability in 2003 http://support.microsoft.com/Default.aspx?id=898631 • Supported 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-us • Community Tools • SharePoint Configuration Analyzer http://www.microsoft.com/downloads/details.aspx?FamilyID=918f8c18-89dc-4b47-82ca-34b393ea70e1&DisplayLang=en • SharePoint Utility http://www.microsoft.com/sharepoint/downloads/components/detail.asp?a1=724 • SPReporthttp://workspaces.gotdotnet.com/spreports • Managing SharePoint Products and Technologies Performance at Microsoft http://www.microsoft.com/technet/itshowcase/content/spsperfnote.mspx#ETKAE • Microsoft 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=en • Blogs • Resources 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.aspx • Upgrade Content IT Pros may not have seen http://blogs.msdn.com/joelo/archive/2006/12/06/upgrade-content-it-pros-may-not-have-seen.aspx • Other Upgrade Topics from Joel’s Blog http://blogs.msdn.com/joelo/archive/tags/Upgrade/default.aspx

46. Orphaned Objects • WSS Content DB Orphans • Post SP2 Hotfix, KB 918743 and KB 918744 • stsadm -o databaserepair -url http://WSSSite -databasenameDatabaseName • stsadm -o databaserepair -url http://WSSSite -databasenameDatabaseName –deletecorruption • SPS Config DB orphans • Post SP2 Hotfix, KB 918742 • spsadm –o repairorphans http://PortalSite • WSS Config DB orphans • Remove and then reattach the content databases on the virtual server

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

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

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

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