Here are our top considerations for a pain-free migration:
Hardware. SP2010 requires 64 bit Windows Server 2008 and 64 bit SQL2005/2008. Take this opportunity to look at your SharePoint use and plan to purchase hardware to support it. Don’t just buy new 64 bit capable servers; buy enough hardware to support your 64Bit Environment. Get used to buying more CPU, more memory, faster memory and enough disk space to accommodate expected growth.
Client Environments. Your desktops will need Office 2007 or 2010 to take full advantage of SP2010’s office integration. If your end users aren’t yet familiar with the MS Office ribbon bar they are not going to understand its use in SP2010. Lastly, IE 6 is no longer supported for updating and authoring content in SharePoint. You need to use the newer standards based browsers.
Perform a MOSS 2007 Audit. You may be familiar with the PreScan utility that comes with MOSS 2007. Don't use it. Use the new Pre-Upgrade Checker utility. It performs a read-only review of the current environment. Look for 2 outputs from the checker:
#1. An XML output listing elements that can successfully upgrade and elements that fail the upgrade test.
#2. A Web page that provides a cleaner looking report of your systems upgrade issues.
Know the Difference Between an Upgrade & a Migration. Determine what's best for your environment & plan accordingly. Due to the 64 bit server requirements we expect that most organizations will need to do a migration.
Upgrade. In-place upgrades occur in the same environment. Only perform an in-place upgrade if you have the necessary hardware and have a relatively simple/straight forward deployment.
Migration. Migrations are recommended for more complex environments that have customized aspects. The migration consists of building the new farm and attaching existing databases.
If you plan to perform an in-place upgrade you should look at Custom Features/Sites/Site Definitions, the 12 hive for custom code, and the GAC for custom assemblies. You should even take a look at the Add/Remove programs on the legacy MOSS server to see if third party vendors have been part of your MOSS system. If 3rd Party vendors are part of it, you need to contact them and ask them for their SharePoint 2010 components or their SharePoint 2010/2007 upgrade compatible feature.xml files. If you are going to upgrade, you have to be on MOSS 2007 SP2. All versions of SharePoint earlier than that will have to first be upgraded to MOSS 2007
SP2. You can then upgrade to SharePoint 2010.
Be Aware of Service Changes. Shared Service Providers are a thing of the past. After you upgrade you will see individual Service Applications for each of the following services. If an in place upgrade is performed, as opposed to a fresh setup and install, the service names will by prefixed with SharedServices1. For example SharedServices1_ExcelServices.
- Search Admin Web Service
- Search Service
- Application Registry
- Business Data Connectivity
- Excel Calculation Services
- State Service App
- User Profiles
Something New in SharePoint 2010. Failed in-place upgrades can be restarted after you correct the source of the failure. If you tried the in-place upgrade with SharePoint 2003 to MOSS 2007 well…. You shouldn’t have.