Export (0) Print
Expand All

Checklist for in-place upgrade (SharePoint Server 2010)

 

Applies to: SharePoint Server 2010

Topic Last Modified: 2011-09-28

This article contains a checklist you can use to make sure that you followed all necessary steps as you prepare for upgrade, perform the upgrade, and perform post-upgrade steps.

In this article:

Some of the steps include notes about the amount of time the steps might take. These are rough estimates only, to give you a relative idea of the duration of the step. To find out how much time each step will take for your environment, we recommend that you perform trial upgrades in a test environment. For more information, see Estimate how long the upgrade process will take and the space that you need (SharePoint Server 2010) and Use a trial upgrade to find potential issues (SharePoint Server 2010).

Follow these steps in order before you begin an in-place upgrade:

 

Pre-upgrade steps for an in-place upgrade Notes

[ ]

Run the pre-upgrade checker

Run the pre-upgrade checker and address any issues. Use the report that is generated by the tool to fill out the Upgrade planning worksheet.

Detailed steps: Run the pre-upgrade checker (SharePoint Server 2010).

Perform this step multiple times as you clean up your environment and test your upgrade process.

Running the checker takes only a few minutes, but addressing any issues might take days or weeks.

[ ]

Clean up your environment

Before you begin the upgrade, make sure that your environment functions in a healthy state and that you clean up any content that you do not have to keep. Remove or repair any orphaned sites or data, address any large lists or large access control lists (ACLs), remove extraneous document versions, and remove any unused templates, features, or Web Parts.

Detailed steps: Clean up an environment before upgrade (SharePoint Server 2010).

Perform this step once for the whole environment.

This process might take days or weeks to complete.

[ ]

Record settings for user profile synchronization

Record the settings used for user profile synchronization in your previous environment in the upgrade worksheet. You will apply them to your new environment when you create and enable the User Profile Synchronization service. Record settings for connections, property mappings, and filters.

Perform this step once for the whole environment.

[ ]

Record blocked file types

Blocked file types are not preserved during upgrade. Copy the list of blocked file types and save the list in the upgrade worksheet so you can reapply the settings after upgrade.

Perform this step once for the whole environment.

[ ]

Back up your environment

Back up your entire environment to ensure that you can recover the existing environment in case something goes wrong during the upgrade process.

Detailed steps: Back up environment before an in-place upgrade (SharePoint Server 2010).

Perform this step once for the whole environment.

This step can take an hour, several hours, or longer, depending on your data set and your environment.

Follow these steps in order during an in-place upgrade. Steps required for in-place upgrade with detached databases are also included.

 

Perform the in-place upgrade Notes

[ ]

Run the pre-upgrade checker

Run the pre-upgrade checker again to identify any new or remaining issues before you start the upgrade.

Detailed steps: Run the pre-upgrade checker (SharePoint Server 2010).

Running the checker takes only a few minutes, but addressing any issues might take longer.

[ ]

Install prerequisites on all servers

Before you can upgrade, you must run the prerequisite installer successfully on each Web server that has Office SharePoint Server 2007 installed.

Detailed steps: Install prerequisites in the "Upgrade in place to SharePoint Server 2010" article.

Perform this step on each Web server and application server in your environment.

[ ]

Detach databases (in-place upgrade with detached databases only)

If you are performing an in-place upgrade with detached databases, detach the databases before you run Setup.

Detailed steps: Roadmap: in-place upgrade with detached databases (SharePoint Server 2010).

Perform this step for each content database and Shared Services Provider (SSP) database in your environment.

[ ]

Disconnect users

If you are upgrading a server farm, disconnect all the users from the server farm by stopping the World Wide Web Publishing Service (W3SVC) on all Web servers.

Perform this step on each Web server in your environment.

[ ]

Run Setup on all servers

Run Setup on all servers to upgrade the software.

Detailed steps: Run Setup on all servers in the "Upgrade in place to SharePoint Server 2010" article.

Perform this step on each Web server and application server in your environment.

This step might take a few minutes or more than an hour, depending on how many servers are in your environment.

[ ]

Install language packs

Install any language packs you need before you run the SharePoint Products Configuration Wizard.

Detailed steps: Install available language template packs (SharePoint Server 2010).

Perform this step on each Web server in your environment.

This step should take only a few minutes per Web server.

[ ]

Run the SharePoint Products Configuration Wizard

If you are upgrading a server farm, first run the SharePoint Products Configuration Wizard on the server that is running SharePoint Central Administration, pause and run the wizard on the other servers in the farm, and then return to the first server to complete the wizard.

importantImportant
You must upgrade SharePoint Central Administration before you attempt to upgrade any other content in the farm. Completing the wizard on the server running SharePoint Central Administration allows you to do so.

Detailed steps: Run the SharePoint Products Configuration Wizard in the "Upgrade in place to SharePoint Server 2010" article.

Perform this step on each Web server and application server in your environment.

This step might take an hour or more.

[ ]

Configure forms-based authentication for a claims-based Web application (in-place upgrade with detached databases only)

For Web applications that were configured to use forms-based authentication or Web single sign-on (Web SSO) authentication, you must perform additional steps before you attach and upgrade the databases. First, you convert the Office SharePoint Server 2007 Web applications to claims authentication. After you convert the Web applications to claims authentication, you configure your Web application zones for forms-based authentication (or Web SSO authentication, as appropriate). Then, you can migrate users and permissions to SharePoint Server 2010.

Detailed steps: Configure forms-based authentication for a claims-based Web application (SharePoint Server 2010).

Perform this step now if you are following the in-place upgrade with detached databases approach. If you are following a standard in-place upgrade approach, perform this step after upgrade is completed.

Perform this step for any Web applications that used forms-based authentication in Office SharePoint Server 2007.

[ ]

Attach databases (in-place upgrade with detached databases only)

If you are performing an in-place upgrade with detached databases, attach the databases and then upgrade the data.

Detailed steps: Roadmap: in-place upgrade with detached databases (SharePoint Server 2010).

Perform this step for each content database and SSP database in your environment.

This step might take an hour, several hours, or days, depending on your data set, whether you are upgrading multiple databases in parallel, and the hardware on the Web servers, database servers, and storage subsystem.

[ ]

Monitor upgrade progress

Use the Upgrade Status page in SharePoint Central Administration to monitor progress as your sites are upgraded.

Detailed steps: Verify upgrade and review upgraded sites (SharePoint Server 2010).

Perform this step once for the whole environment.

This step might take an hour, several hours, or days, depending on your data set.

Perform the following steps in order after you perform an in-place upgrade.

 

Post-upgrade steps for an in-place upgrade Notes

[ ]

Configure forms-based authentication for a claims-based Web application

For Web applications that were configured to use forms-based authentication or Web single sign-on (Web SSO) authentication, you must perform additional steps after upgrading. First, you convert the Office SharePoint Server 2007 Web applications to claims authentication. After you convert the Web applications to claims authentication, you configure your Web application zones for forms-based authentication (or Web SSO authentication, as appropriate). Then, you can migrate users and permissions to SharePoint Server 2010.

Detailed steps: Configure forms-based authentication for a claims-based Web application (SharePoint Server 2010).

Perform this step for any Web applications that used forms-based authentication in Office SharePoint Server 2007.

[ ]

Configure new and upgraded services after in-place upgrade

Many new services are available in SharePoint Server 2010. You can enable these new services after you perform an in-place upgrade by using the Farm Configuration Wizard or by configuring them individually.

Perform this step once for your environment.

[ ]

Upgrade profile properties to taxonomy data and update the photo store for User Profile services

Data in profile properties in Microsoft Office SharePoint Server 2007 that had multiple values was stored in the SSP database as part of the Profile Services data. For SharePoint Server 2010, this data must be converted to taxonomy data and be stored in the managed metadata database. When you upgrade, any photos that were stored as profile pictures must be updated. If you do not update the photo store data, either no photos will be displayed or some photos might appear distorted. You perform these actions from the command line by using Windows PowerShell cmdlets.

Detailed steps: Upgrade profile properties to taxonomy data and update the photo store for Profile Services

Perform this step once for each User Profile service application in your environment.

This step contains a lot of smaller steps. Depending on the complexity of your user profile data and your configuration, this might take an hour or several hours to complete.

[ ]

Create and configure the Secure Store service application and migrate SSO data to the Secure Store service

The SSO service that was available in Office SharePoint Server 2007 has been replaced with the Secure Store service in SharePoint Server 2010. There is no direct upgrade path for the data and settings from SSO to the Secure Store service, but you can migrate data from the SSO database to a new Secure Store database. Excel Services Application needs the Secure Store service account to function correctly.

Detailed steps: Create and configure the Secure Store service application and migrate SSO data to the Secure Store service

Perform this step for each Secure Store service application that needs data from a previous SSO service.

[ ]

Upgrade solutions that depend on the Business Data Catalog

If your Business Data Catalog solution depended on the Web Parts that are provided by Office SharePoint Server 2007 and SharePoint Server 2010 by default (such as the Business Data List Web Part or the Business Data Actions Web Part), you must upgrade your solution to use the upgraded application definitions (called "BDC models") in the Business Data Connectivity service, because those Web Parts have been upgraded to use the new object model provided by the new service.

Detailed steps: Upgrading solutions that depend on the Business Data Catalog and Plan to upgrade to Business Connectivity Services (SharePoint Server 2010).

Perform this step once for your entire environment.

[ ]

Verify upgrade and review upgraded sites

Review sites to be sure that they have been upgraded successfully and are ready for users to view.

Detailed steps: Verify upgrade and review upgraded sites (SharePoint Server 2010).

Perform this step for every upgraded Web application and site collection in your environment.

This step might take an hour, several hours, or days, depending on your content.

You should also have site owners review their sites and report any issues.

[ ]

Start a full crawl

After all content is upgraded and all settings are configured, you can start a full search crawl of your content. This might take several hours or several days to complete, depending on how much content exists in your environment.

Perform this step once for your entire environment.

Performing a full crawl can take several hours or days to complete, depending on the amount of content in your environment.

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft