Upgrade sites (Office SharePoint Server)
Applies To: Office SharePoint Server 2007
This Office product will reach end of support on October 10, 2017. To stay supported, you will need to upgrade. For more information, see , Resources to help you upgrade your Office 2007 servers and clients.
Topic Last Modified: 2016-11-14
In this article:
Upgrade sites by using Central Administration pages
Upgrade sites by using the command line
Upgrade sites after installing a language template pack
When you perform a gradual upgrade, you can determine which sites to upgrade and when. Before you can upgrade any sites to Microsoft Office SharePoint Server 2007, you must run Setup and the SharePoint Products and Technologies Configuration wizard on all servers in your server farm. After you have completed that step and installed any language template packs you need, you can begin to upgrade sites. For more information about upgrading your servers, see one of the following topics:
Install and configure Office SharePoint Server for a gradual upgrade
Chapter overview: Perform a gradual upgrade in a shared services environment
When you are ready to upgrade your sites, you can use either the upgrade pages in the SharePoint® Central Administration Web site or the upgrade operation on the command line. Use the command line if you want to run upgrade for large batches of sites at different times, or if you have installed a language template pack after upgrading other sites in your environment.
Upgrade sites by using Central Administration pages
There are two phases in the process for upgrading sites from the Central Administration pages. First, you create a new Web application to host the upgraded versions of the sites. Then, you upgrade one or more site collections.
Important
You must upgrade the root site collection before you can upgrade any other site collections in the Web application.
Create a new Web application to host upgraded sites
In Central Administration, on the Operations tab, under Upgrade and Migration, click Site content upgrade status.
On the Site Content Upgrade Status page, next to the URL you want to upgrade, click Begin upgrade.
On the Set Target Web Application page, in the Web Application to Upgrade section, verify that the Web application you want to upgrade appears.
In the New URL for Original Content section, in the Port box, type a port number, and then in the Host Header box, type the host header to use (if needed).
In the Application Pool for New Web Application section, select Create new application pool, then in the Application pool name box, type a name, and then select either Predefined or Configurable.
If you selected Predefined, select the account to use.
If you selected Configurable, type the account name to use, and then type the password for that account.
Note
You cannot use the same application pool that you used for the previous version. You can use the same user account, but you must create a new application pool, or use an application pool that you already created for your upgraded sites.
In the Reset Internet Information Services section, select either Restart IIS Automatically or Restart IIS Manually.
If you choose Restart IIS Manually, you will need to restart IIS after the Web application is created in the final step in this procedure.
In the Security Configuration section, under Authentication Provider, select either Negotiate (Kerberos) or NTLM depending on your environment.
In the Content Databases section, select either Automatic database name selection or Manually set database names.
If you choose to manually set the database names, then on the Database Names page, you must supply names for the temporary content databases and the new version content databases.
In the SSP Database Settings section, in the SSP Database Name box, type the name for the Shared Services Provider database.
In the Search Database Name box, type the name for the Search database.
In the Index Server section, in the Index Server box, select the Index Server to use.
Click OK. If you chose to manually set the database names, the Database Names page opens. Type the names to use for the temporary content databases and the new version content databases for this Web application, and then click Save.
An Operation in Progress page appears while the new Web application is created.
Note
If you chose to restart IIS manually, you must now run iisreset /noforce on each front-end Web server in your server farm.
Upgrade site collections
On the Site Collection Upgrade page, select the check boxes next to the sites you want to upgrade, and then click Upgrade Sites.
Important
You must upgrade the root site collection before you can upgrade any other site collections in the Web application. If you are upgrading multiple site collections at one time, the root site collection must be included in the first set of sites that you upgrade.
On the Sites Selected for Upgrade page, verify the number of site collections, the storage used, the originating database, and the target database, and then click Upgrade Sites.
The Upgrade Running page opens, and upgrade runs for the selected site collections. This may take a few minutes or a few hours, depending on how many site collections you have selected and how large the site collections are. The Status page refreshes automatically every minute to provide you with an updated status. If the upgrade fails or reports issues, you can refer to the log files for more information. The Upgrade.log file and the trace log file are located at %COMMONPROGRAMFILES%\Microsoft Shared\web server extensions\12\LOGS. The trace log is named in the following format: Machine_name-YYYYMMDD-HHMM.log, where YYMMDD is the date and HHMM is the time (for example, Server1-20061105-1241.log).
After the upgrade process has completed, click Home to return to the Central Administration home page.
Upgrade sites by using the command line
To upgrade sites by using the command line, you must follow the same two-step process: create a target Web application, and then upgrade the sites.
To create the target Web applications, use the following command, including any options that apply to your environment (skip this step if you have already performed the steps under "Create a new Web application to host upgraded sites" above):
Stsadm.exe. -o upgradetargetwebapplication -url <URL to upgrade>
-relocationurl <new URL for non-upgraded content>
-apidname <new application pool name>
[-apidtype <configurableid/NetworkService>]
[-apidlogin <DOMAIN\name>]
[-apidpwd <application pool password>] [-exclusivelyusentlm]
Then, after you have created the Web application, you can upgrade individual site collections by using the following command, including any options that apply to your environment:
stsadm.exe -o upgrade [-inplace | -sidebyside] [-url <url>]
[-forceupgrade] [-quiet] [-farmuser <farm user>
-farmpassword <farm password>] [-sitelistpath <sites xml file>]
For example, to upgrade sites at a particular URL in a side-by-side (gradual) upgrade process, you would use the following command:
stsadm.exe -o upgrade -sidebyside -url <url>
-sitelistpath <path to XML file>
Note
When you use the command line to perform a gradual upgrade, you cannot upgrade sites from different content databases. If your Web application contains a large number of sites spread across multiple content databases, break the list into smaller groups of sites contained within the same content database.
To get a list of sites that need to be upgraded, you can use the enumsites operation to list all redirected sites on a Web application. Use the following syntax to generate the list:
**stsadm -o enumsites -url http://**server_name -redirectedsites
You can use the list of sites generated by this operation to generate your sitelist XML file for the upgrade operation.
The following table describes the parameters used for the upgrade operation:
| Parameter | Optional/Required | Description |
|---|---|---|
Inplace or Sidebyside |
Required, you must specify one of these options |
Inplace specifies an in-place upgrade, where the version 2.0 sites are upgraded immediately, and the version 2.0 environment is not available after the upgrade process is complete. Sidebyside specifies a gradual upgrade, where the version 2.0 sites are preserved in the version 2.0 environment. |
URL |
Optional |
The version 2.0 URL to the site collection. |
ForceUpgrade |
Optional |
Specifies whether or not to force the upgrade. |
Quiet |
Optional |
Specifies that the upgrade process is run in quiet mode. |
FarmUser |
Optional |
Specifies the user account to use in performing the upgrade. |
FarmPassword |
Optional (but required if using FarmUser) |
Specifies the password for the FarmUser account. |
Reghost |
Optional |
Specifies whether to reghost pages (reset pages to site definition) during upgrade. |
SiteListPath |
Optional |
Allows you to specify an XML file with a list of specific site collections to upgrade. The format of the XML file is:
The “Count” and “TargetDatabase” attributes are optional. Specify just the set of sites you want to upgrade from a single content database. Alternatively, use the command stsadm –o enumsites –url <V3url> -redirectedsites to produce this same XML for site collections that require upgrade. For additional information about how to perform this procedure using the Stsadm command-line tool, see Upgrade: Stsadm operation (Office SharePoint Server), Upgradetargetwebapplication: Stsadm operation (Office SharePoint Server), and Enumsites: Stsadm operation (Office SharePoint Server). |
Upgrade sites after installing a language template pack
If you performed an in-place upgrade and then installed a language template pack, you must now upgrade any sites that depend on the language in that language template pack. To perform the upgrade, perform the upgrade operation on the command line by using any options that apply to your environment.
Download this book
This topic is included in the following downloadable book for easier reading and printing:
See the full list of available books at Downloadable content for Office SharePoint Server 2007.