Arguably one of the most crucial aspects of SharePoint 2010 is the ability to upgrade to it. It will no doubt be the first focus of firms heavily entrenched in SharePoint.
Sean Livingston, the upgrade program manager at Microsoft, began the SharePoint Conference 2009 session on upgrading to SharePoint 2010 by stressing that “..this is only the beginning..." for Microsoft’s plans to help companies upgrade to the new release.
This release will focus on in-place upgrades and database attached upgrades -- including content databases, profile service databases and project service databases.
Unsupported upgrades will be from earlier releases than WSS v3 SP2/MOSS 2007 SP2, direct downgrade from WSS v2/SPS 2003 or earlier, side by side installations and gradual upgrades.
Upgrade Prep Tools
WSS v2/MOSS 2007 SP2
- Pre-upgrade Checker
- Stsadm –o EnumAllWebs
- SPDiag v2
- Stsadm –o ExportIPFSAdminObjects
- Stsadm –o EnumAllWebs
- SPDiag 2010
Content Database insight
Is Your Farm Healthy?
In 2010, Microsoft realized that there weren’t enough tools available to determine if your farm was in a “healthy state” before upgrading. Because there are so many custom solutions out there, the new tools will hopefully aid in the upgrade process. An update to the SPDiag tool (TBD) will offer more to admins than was currently available in the v2 version.
The Pre-Upgrade Checker Command was introduced in SP2, and is being improved in the October 2009 CU to address some shortcomings. The tool identifies farm information and current and potential issues with the farm that you need to know before upgrading. Some of the issues the tool would be looking for are missing site definitions, data orphans and modified content databases.
Modified content databases, specifically, will more than likely cause a problem during upgrade, so you’ve got to back out of those changes before upgrading. The tool will compare the schema of your content databases to an untouched schema.
This utility makes no changes to the databases, but only compares databases for upgrade readiness. Not only does it work on O12 content databases but also O14 databases.
Windows Powershell Upgarde Cmdlets
The Upgrade-SPContentDatabase will resume an upgrade session that’s in progress or to upgrade certain components after applying a recent patch that changes the build, or B2B upgrades. It can also resume a failed content database version to version upgrade.
2010 will include a feature upgrade capability that will be able to call out to custom code.
The difficulty with upgrading is that customers do not want anything to change, especially the UI. The default mode for an upgrade is the Visual Upgrade. Because 2010 ships with all of the 2007 master pages, you can remain in the 2007 UI rather than moving to the 2010 UI.