Upgrade to WSS 3.0 and SharePoint Server 2007 Joel Oleson Sr. Technical Product Manager Microsoft Corporation IW310

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

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

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

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 – l.asp?a1=724 Run prescan.exe early and repeat as necessary

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

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

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

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: what-they-mean.aspx

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

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.

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

In-Place Upgrade Steps On existing hardware, install prerequisites SP2,.NET Framework 3.0 and run prescan.exe Run setup and choose “In-Place Upgrade” –Install language packs if needed Deploy Upgrade Definition, Site Definition and Feature Files Run Configuration Wizard and Upgrade one web server Review log files and resolve any issues Review upgraded content Reset pages (or site) to Site Definitions

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

SQL Instance WSS Farm WSS 2003 Web App WSS 2003 Web App Gradual Upgrade Process Temp Config Content WSS 2007 Web App WSS 2007 Web App

Gradual Upgrade URL Redirection Current URL During upgrade define temporary URL – orhttp://portal.company.com:8080 – 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

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)

Gradual Upgrade Upgrade 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

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

Microsoft Confidential 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

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

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.

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

Microsoft Confidential 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

Microsoft Confidential 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

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

SQL Instance. Database Attach on Steroids Farm 2003 Farm

Summary In-PlaceGradualDB Attach Pros Simple Uses existing hw Provides granularity Provides revert back option Reduces user impact Uses existing hw Upgrade to new farm Existing, 2003, farm not affected Cons Entire farm offline during upgrade No revert back option Failure will stop upgrade Hardware intensive, memory and storage URL Redirects during upgrade Performance impact on 2003 farm WSS Scalable Hosting mode not supported Complex, many manual steps Requires new farm an up to double storage ScenariosDev/Test platforms Medium, Large Farms Customized environments Large databases and site collections New hardware and topology WSS Scalable Hosting modes Large databases

Customization Considerations

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.

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 – become (retains structure) Areas are upgraded to publishing sites –After upgrade you can only create publishing sites as sub site can be changed an-upgrade-you-can-only-create-publishing-sub-sites.aspx Site Directory now creates sub-sites not separate site collections

SPS Site directory changes Now creates sub sites instead of site collections like in 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 – collection-sizing.aspx Want site directory to create site collection like in 2003? – Want to move existing site directories to sub sites? – site-collections-after-upgrading-sharepoint.aspx Other improvements made to site directory to investigate.

Common issues Local administrator on server no longer has full access to SharePoint –Can be regranted administrator-of-the-entire-web-application.aspx New blocked file types –ASMX, REM, RESX, SOAP, ASHX Hard coded URLS don’t work enabled document libraries don’t work. Look at new feature “Incoming ” Office Web Components not available in 2007 –More details - to-the-office-web-components.aspx

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

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

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

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

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

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

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

Partners helping you upgrade CorasWorks Migrator –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 AvePoint DocAve –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).

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.

References Migration and Upgrade Information for SharePoint Developers – Migration and Upgrade Information for SharePoint Server (IT Pros) – –Upgrade Documentation 484e-9cc5-f6c4d725c mspx?mfr=truehttp://technet2.microsoft.com/Office/en-us/library/396c85d9-4b e-9cc5-f6c4d725c mspx?mfr=true –Upgrade Toolkit for Windows SharePoint Services Sites and Templates Guide –Upgrade in WSS SDK Fix your Orphans HotFixes –repair content databases in Windows SharePoint Services –Spsadm.exe command line tool that you can use to clean up orphaned items in the configuration database in SharePoint Portal Server

References Supportability –2003 Best Practices to ensure upgradeability us/library/ms aspxhttp://msdn2.microsoft.com/en- us/library/ms aspx –KB Article on Site Definition supportability in –Supported and unsupported scenarios for working with custom site definitions and custom area definitions in Windows SharePoint Services and in SharePoint Portal Server Community Tools –SharePoint Configuration Analyzer 34b393ea70e1&DisplayLang=en 34b393ea70e1&DisplayLang=en –SharePoint Utility –SPReport Managing SharePoint Products and Technologies Performance at Microsoft –Microsoft SQL Server Report Pack for Microsoft Office SharePoint Portal Server b4e33d3d&DisplayLang=en b4e33d3d&DisplayLang=en Blogs –Resources and Recommendations for Upgrading Site Definitions and Site Templates upgrading-site-definitions-and-site-templates.aspx upgrading-site-definitions-and-site-templates.aspx –Upgrade Content IT Pros may not have seen seen.aspx seen.aspx –Other Upgrade Topics from Joel’s Blog

Orphaned Objects WSS Content DB Orphans –Post SP2 Hotfix, KB and KB –stsadm -o databaserepair -url -databasename DatabaseName –stsadm -o databaserepair -url -databasename DatabaseName –deletecorruption SPS Config DB orphans –Post SP2 Hotfix, KB –spsadm –o repairorphans WSS Config DB orphans –Remove and then reattach the content databases on the virtual server

Effect of Upgrades: Low Customization Site (Original)

Effect of Upgrades: Low Customization Site (Upgraded)

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

Effect of Upgrades: High Customization Site (Original)

Effect of Upgrades: High Customization Site (Upgraded)

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

Effect of Upgrades: Themed Site (Original)

Effect of Upgrades: Themed Site (Upgraded)