Install and configure Office SharePoint Server for an in-place upgrade

When you run an in-place upgrade, all content and configuration data is upgraded in-place, at one time. When you start the in-place upgrade process, the Web server and Web sites remain offline until the upgrade has been installed. When you perform an in-place upgrade, you cannot pause or roll back to the previous version.

Upgrade is a detailed and complicated operation. Even in relatively basic environments, there may be customizations that do not lend themselves to a smooth and simple upgrade. These customizations, and many other variables, are outside of the control of the upgrade process and may cause the in-place upgrade to fail.

We recommend in-place upgrade only for a stand-alone server and even then, in limited situations. In general, this means that you should consider in-place upgrade for environments that meet both of the following conditions:

Small installations

Environments that have not been customized

In practice, this means that you should only use in-place upgrade in environments where there is minimal impact when a server is down. Examples include development, test, or staging servers where you need a quick upgrade experience and can quickly roll back the entire server to an earlier configuration. For example, in a virtualized environment, if something goes wrong with the upgrade, you can discard the undo disks and, in minutes, be back to your original environment. Another option to avoid having to troubleshoot a failed upgrade is to restore your server from a backup.

If your medium or large server farm contains one or more servers that are not front-end Web servers, and you have used the Default Web Site in Internet Information Services to host a SharePoint site, upgrade may fail with a message that the Default Web Site cannot be upgraded. To work around this issue, before running upgrade, on all non-front-end Web servers, rename the Default Web Site in IIS to something else, then run upgrade, and then restore the name to Default Web Site. You do not need to rename the Web site on any front-end Web servers in the server farm.

If you are running an in-place upgrade on a server farm, stop the World Wide Web Publishing Service (W3SVC) on all front-end Web servers to disconnect all the users from the server farm. In server farms with multiple front-end Web servers, if you allow users to connect after the files and databases have been updated on one Web server, and the other Web servers have not been updated, users will not be able to browse the Web sites.

Install Office SharePoint Server 2007

Run Setup.exe.

Tip:

As an alternative to installing Office SharePoint Server 2007 and then separately deploying the available software updates, you can download an Office SharePoint Server 2007 install file that includes the available software updates. You can find the Office SharePoint Server 2007 install file that includes the available software updates on the Microsoft Download Center (http://go.microsoft.com/fwlink/?LinkID=72322&clcid=0x409).

In server farm deployments, all your Web servers must have the same software update version applied. To accomplish, 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 Deployment for Office SharePoint Server 2007.

Run the SharePoint Products and Technologies Configuration Wizard

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

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

A message appears, notifying you that Internet Information Services (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.

A message appears, notifying you that you should download and install new language template packs for the new version.

Click OK to confirm the message and continue with the wizard. Do not install the language template packs until you have completed running the configuration wizard.

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.

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

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 continuing the configuration wizard. Depending on your server farm configuration, and where you are in the process of installing and configuring Office SharePoint Server 2007, 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. When all of the other servers are at this same stage, 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 already 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.

The configuration wizard continues the upgrade process by setting up the configuration database and installing the Central Administration Web application.

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 the Upgrade Running page opens. You may be prompted to enter your user name and password before the Upgrade Running page will open. The upgrade process might take a while to complete. The Upgrade Running page refreshes every minute.

After the process has completed, click Continue.

The Central Administration home page opens.

If you stopped the World Wide Web Publishing Service (W3SVC) on all front-end Web servers before the upgrade, make the Web servers available to users by manually starting the World Wide Web Publishing Service on the front-end Web servers.

Install and configure Office SharePoint Server 2007 using the command line

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 an in-place version to version upgrade.

Review the log files and resolve any issues

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

Caution:

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.