Export (0) Print
Expand All

Install and configure Windows SharePoint Services for a gradual upgrade

SharePoint 2007

Updated: March 5, 2009

Applies To: Windows SharePoint Services 3.0

 

Topic Last Modified: 2009-01-29

A gradual upgrade installs the new version side-by-side with the previous version. After you install and configure Windows SharePoint Services 3.0, you can then determine which site collections to upgrade and when to upgrade them.

NoteNote:
You must use an in-place upgrade (or database migration) if you are using Windows SharePoint Services 2.0 in stand-alone mode with Microsoft SQL Server™ 2000 Desktop Engine (Windows) (WMSDE). For more information about performing an in-place upgrade, see Install and configure Windows SharePoint Services for an in-place upgrade. For more information about choosing an upgrade approach, see Determine upgrade approach.

When upgrading a server farm, be sure to upgrade all of the servers in the server farm in the following order:

  1. Run Setup to install the new version on all servers in the server farm.

  2. Run the SharePoint Products and Technologies Configuration Wizard on the front-end Web server that contains the SharePoint Central Administration Web site.

  3. Run the SharePoint Products and Technologies Configuration Wizard on all other front-end Web servers or search servers in the farm in any order.

In this article:

Before you begin installing Windows SharePoint Services 3.0, be sure you have installed all prerequisite software. For more information, see Install all pre-requisites (Windows SharePoint Services).

Make sure that the minimum permissions for the account that you use to run Setup and the SharePoint Products and Technologies Configuration Wizard are:

  • The account is a member of the Administrators group on the Web server computer.

  • The account is granted the fixed database role db_owner to all SharePoint Products and Technologies databases.

In many IT environments, database administrators (DBAs) create and manage databases. Security policies and other policies in your organization might require that DBAs create the databases needed by Windows SharePoint Services 3.0.

NoteNote:
For information about how to deploy Windows SharePoint Services 3.0 in an environment in which DBAs create and manage databases, see Deploy using DBA-created databases (Windows SharePoint Services) (http://go.microsoft.com/fwlink/?LinkID=86818&clcid=0x409).

  1. Run Setup.exe.

    TipTip:
    As an alternative to installing Windows SharePoint Services 3.0 and then separately deploying the available software updates, you can download a Windows SharePoint Services 3.0 install file that includes the available software updates. You can find the Windows SharePoint Services 3.0 install file that includes the available software updates on the Microsoft Download Center.
  2. On the Read the Microsoft Software License Terms page, review the terms, select the I accept the terms of this agreement check box, and then click Continue.

  3. On the Upgrade earlier versions page, click Yes, perform a Gradual upgrade.

  4. On the Server Type tab, select Web Front End.

  5. Click Install Now.

    NoteNote:
    If you have a custom site definition or custom Web application installed on your server, you will see a Setup Warning dialog box, notifying you that there are third-party products installed that integrate with Windows SharePoint Services 2.0. If you are aware of these customizations or applications and are prepared to continue with the upgrade process (for example, if you have created upgrade definition files for any custom templates), click OK. If you want to cancel the upgrade process and investigate these products, click Cancel. For more information about upgrade definition files, see Develop new custom site definitions and create upgrade definition files (Windows SharePoint Services).
  6. Setup runs and installs Windows SharePoint Services 3.0.

  7. On the completion page, clear the Run the SharePoint Products and Technologies Configuration Wizard now check box, and then click Close.

Before you run the SharePoint Products and Technologies Configuration Wizard, you should perform the following steps:

NoteNote:
In server farm deployments, all your Web servers must have the same software update version applied. To accomplish this, you can create an installation source that contains a copy of the released software product, along with the available software updates (also known as a slipstreamed installation source). When you run Setup from this updated installation source, the Web server will have the same software update version as the rest of the Web servers in your server farm. You can also use the installation source to add a new Web server to an existing server farm. When you run Setup from this updated installation source, the new Web server will have the same software update version as the rest of the Web servers in your server farm. For more information about creating an installation source, see Create an installation source that includes software updates (Windows SharePoint Services 3.0)

If you have a server farm, follow the instructions to Install Windows SharePoint Services 3.0 on each front-end Web server in your server farm, and then Run the SharePoint Products and Technologies Configuration Wizard.

CautionCaution:
Do not add any servers to your server farm after running Setup. Running the SharePoint Products and Technologies Configuration Wizard upgrades the configuration database. This database contains the list of servers in the farm, and any servers added to the farm after the configuration wizard has been run will not be included in the database, and therefore will not appear in the Windows SharePoint Services 3.0 topology. If you need to add servers to your farm, do so either before starting the upgrade or after you have completed the upgrade process, following the steps in Add servers to an upgraded farm (Windows SharePoint Services).

  1. Click Start, point to All Programs, point to Administrative Tools, and then click SharePoint Products and Technologies Configuration Wizard.

  2. In the SharePoint Products and Technologies Configuration Wizard, on the Welcome to SharePoint Products and Technologies page, click Next.

  3. A message appears, notifying you that IIS, the SharePoint Administration Service, and the SharePoint Timer Service may need to be restarted or reset during configuration. Click Yes to continue with the wizard.

  4. A message appears, notifying you that if you have existing language template packs, you should download and install the new version of the language packs before you proceed. Click OK to continue with the wizard.

  5. On the Connect to a server farm page, select No, I want to create a new server farm, and then click Next.

  6. On the Specify Configuration Database Settings page, in the Database server box, type the name of the server running Microsoft SQL Server 2000 or SQL Server 2005.

  7. In the Database name box, leave the default (SharePoint_Config) or type a database name to use instead.

  8. In the Specify Database Access Account section, type the user name and password to use to connect to SQL Server, and then click Next.

    NoteNote:
    This account must have rights to create databases. If SQL Server is running on a server that is separate from your Web front-end server, then this account must also be a domain account. This user account must be a member of the following SQL Server security roles: Database Creator and Security Administrator.
  9. On the Configure SharePoint Central Administration Web Application page, if you want to use a specific port number for SharePoint Central Administration, select the Specify port number check box, and then type the port number to use.

  10. In the Configure Security Settings section, select either Negotiate (Kerberos) or NTLM, depending on your environment, and then click Next.

    NoteNote:
    To enable Kerberos authentication, you must perform additional configuration steps. For more information about authentication methods, see Plan authentication methods (Windows SharePoint Services).
  11. On the Completing the SharePoint Products and Technologies Configuration Wizard page, verify the settings, and then click Next.

    The configuration wizard runs and configures the configuration database and the Central Administration application for Windows SharePoint Services 3.0.

  12. A message appears notifying you that if you have a server farm with multiple servers, you must run Setup on each server to install new binary files before running the configuration wizard and starting the upgrade process. Depending on your server farm configuration, and where you are in the process of installing and configuring Windows SharePoint Services 3.0, you have three choices:

    • If this is the only server in your farm, no other actions are necessary. Click OK to continue with the wizard.

    • If you have other servers in your farm, and you have not yet run Setup and the configuration wizard on the other servers, leave this message open on this server, and then run Setup and the configuration wizard on the other servers in the farm. After you have run Setup and the configuration wizard on the other servers, you can return to the front-end Web server and click OK to continue with the SharePoint Products and Technologies Configuration Wizard.

    • If you have run Setup and the configuration wizard on all servers in your server farm, and they are all at this stage, on a front-end Web server, click OK to continue with the configuration wizard.

  13. On the Configuration Successful page, review the settings that have been configured, and then click Finish.

The SharePoint Products and Technologies Configuration Wizard closes and Central Administration opens. You may be prompted to enter your user name and password before the Central Administration site will open. If you have not already done so, you can install any language template packs you need for the new version. For more information, see Install available language template packs (Windows SharePoint Services). After installing the language packs (if any), you are ready to start upgrading specific Web applications and site collections. Continue with the process by following the steps in the Upgrade sites (Windows SharePoint Services) topic.

If you prefer, you can install and configure Windows SharePoint Services 3.0 from the command line instead. For more information, see Setup.exe command-line reference (Windows SharePoint Services), Command-line reference for the SharePoint Products and Technologies Configuration Wizard (Windows SharePoint Services), Stsadm command-line tool (Windows SharePoint Services), and Install Windows SharePoint Services 3.0 by using the command line.

NoteNote:
If you started the installation in silent mode, using the /q switch, the SharePoint Products and Technologies Configuration Wizard does not automatically start. To continue the upgrade, you need to force the upgrade by either manually starting the wizard or running the psconfig command with arguments to force a gradual upgrade.

If the upgrade fails or reports issues, you can refer to the log files for more information. The Upgrade.log file is located in %COMMONPROGRAMFILES%\Microsoft Shared\Web server extensions\12\LOGS.

CautionCaution:
In some configurations, the SharePoint Timer Service (OWStimer) account—which, by default, is the same account used by the SharePoint Central Administration v3 application pool account—is configured with credentials that do not have permission to access the LOGS folder in %COMMONPROGRAMFILES%\Microsoft Shared\Web server extensions\12\. If this is the case, part of the Upgrade.log file is stored in the temporary storage folder of the account that is running the SharePoint Timer service. To avoid the possibility of deleting the upgrade log file when you restart the server computer, copy Upgrade.log to another location.

For information about troubleshooting common issues, see Troubleshoot and resume upgrade (Windows SharePoint Services).

For information about viewing the upgrade log file, see Verify upgrade (Windows SharePoint Services).

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