Microsoft Office Online
Sign in to My Office Online (What's this?) | Sign in

Warning: You are viewing this page with an unsupported Web browser. This Web site works best with Microsoft Internet Explorer 6.0 or later, Firefox 1.5, or Netscape Navigator 8.0 or later. Learn more about supported browsers.

Email this linkEmail this link Printer-Friendly VersionPrinter-Friendly Version Bookmark and ShareShare
Office 2000 Server Extensions Service Pack 3 (SP3)
 

Office 2000 Server Extensions Service Pack 3 (SP3) provides the latest updates to Microsoft® Office Web Server Extensions and contains significant security enhancements as well as stability and performance improvements.

Any public updates released for Office 2000 Server Extensions after Office 2000 Server Extensions Service Pack 3 will first require the installation of Office 2000 Server Extensions Service Pack 3.


Toolbox   The full-file version of Office 2000 Server Extensions SP3 consists of one Windows Installer patch file (MSP format) packaged in a self-extracting executable (Owssp3a.exe). You can find this downloadable file on the Office 2000 Resource Kit Downloads page.

Localized versions of this service pack are listed later in this article in the section titled "Localized versions of the Server Extensions SP3 update."



Order the CD   You can obtain the Office 2000 SR1a, Office 2000 SP3, and Office 2000 Server Extensions Service Pack 3 updates free of charge on CD-ROM in North America. To order the CD online, see Order Office 2000 Service Pack 3 on CD on the Office Resource Kit Web site.


Requirements for an Office 2000 Server Extensions SP3 deployment

Before you install Office 2000 Server Extensions SP3 on either an administrative installation point or a stand-alone computer, the current installation of Office 2000 must be updated to version SR1 or SR1a. The SR1 update is a prerequisite for the fixes contained in Office 2000 Server Extensions SP3, as it provides a broad set of enhancements to the original release of Office 2000.

If you attempt to install the Office 2000 Server Extensions SP3 update on a computer without SR1, a message will be displayed advising you to install SR1 before proceeding. For more information on the SR1 update, see Deploying Office 2000 Service Release 1 in the Office Resource Kit Journal.

To ensure the integrity of your Microsoft Office installation, Windows Installer may require access to your installation media or network installation location before applying any product updates. This is a technical requirement of Windows Installer-based software patching and is not intended to be an anti-piracy measure. For more information, see Windows Installer Must Have Original Source Files When You Apply a Patch in the Microsoft Knowledge Base.

Strategies for updating your Office 2000 installations

The recommended method for distributing Office 2000 Server Extensions SP3 is first to update your administrative installation point, and then recache and reinstall Office 2000 on your users' computers to apply the changes. This is the standard update procedure presented for all previous Office 2000 updates, and it's still the most effective way to distribute software in a controlled environment. Details on using this method are covered later in this article in the section titled "Applying Office 2000 Server Extensions SP3 to an administrative installation point."

An alternative to the administrative update strategy is to apply the binary (client) version of Office 2000 Server Extensions SP3 directly to users' computers within your organization. This approach may be useful if you have experienced synchronization problems between your administrative installation points and your client computers. Details on this strategy are covered in the topic Distributing Office 2000 Client Updates to Users. The client version of Office 2000 Server Extensions SP3 is available from the Office Update Web site.

A third option is to apply the full-file updates directly to client computers. This method is an efficient way to ensure that all users have the most current version of the software when you do not know which updates users have applied. In addition, users can apply a full-file patch even if they do not have access to the administrative source. However, these client computers remain out of sync with the updated source until they reinstall Office 2000 Server Extensions SP3 from the original installation point.

Details on this strategy, and a more complete comparison of the three update methods, can be found in the article Strategies for Updating Office 2000 Installations.

Applying the Server Extensions SP3 update to an administrative installation point

The full-file administrative update file for Office 2000 Server Extensions SP3 is a Microsoft Windows Installer patch (MSP file) that you apply to your administrative share by using a command line with specific parameters. The following table lists the MSP file.

MSP file name Description
Owssp3FF.msp Updates Office 2000 Server Extensions with Service Pack 3.

 Note    For best results, the update should be applied from the computer that contains the administrative installation point. Make sure the files on the administrative installation point are not in use when you apply the update. Copy the updated administrative installation image to all installation points after you back up any custom transform, Setup.ini, or other custom files.


To apply Office 2000 Server Extensions SP3 to an administrative installation point
  1. Download Owssp3a.exe and double-click the file name to extract the MSP file.
  2. Connect to the administrative installation point.

    Note that you must have write access to the administrative installation point on the server and the appropriate privileges to carry out the task.

  3. On the Start menu, click Run and then type the command line for Windows Installer with the appropriate options for the update. Use the following syntax:
    [start] msiexec /p [path\name of update MSP file] 
    /a [path\name of MSI file]
    SHORTFILENAMES=TRUE /qb /L*v [path\name of log file]
    

You must run the command line separately for each MSP file you apply to the administrative installation point — you cannot reference multiple MSP files on the same command line. The following table describes the command-line options.

Command-line option Description
[start] Required only for Microsoft Windows® 98 systems where Msiexec is not directly in the path.
Msiexec Executable file name for Windows Installer.
/p Enables Windows Installer to apply an update to an existing installation.
[path\name of update MSP file] Path and file name of the MSP file for the update.
/a Enables Windows Installer to perform an administrative installation of a product on a network share.
[path\name of MSI file] Path and file name to updated MSI file on the administrative image. For example: \\server\share\Proplus.msi
SHORTFILENAMES=TRUE Directs Windows Installer to create all file names and folders with MS-DOS-compatible file names. Required when you run Windows Installer from the command line.
/qb Sets the user interface to the basic level (simple progress and error handling). This switch is optional on the command line.
/L*v Turns on logging and sets a path for the log file. The * flag causes the switch to log all information. This switch is optional on the command line.
[path\name of log file] Path and file name of the Windows Installer log file. Used only with the /L*v switch.

Updating client computers from an administrative installation point

After you update your administrative installation point, you must recache and reinstall Office 2000 Server Extensions SP3 on client computers that use the administrative image. Any new client installations from the administrative installation image will automatically include Office 2000 Server Extensions SP3.


 Note    If you originally installed Office 2000 on a client computer from an administrative installation point, you must follow the recache and repair procedure to update that client. If you update the client directly by using the end-user patch from the Office Update Web site, the client and administrative images become out-of-sync, which may cause future updates to fail.


To update an existing client installation from an administrative installation point, run the following command line on the client computer:

start msiexec /i [path to updated .msi file on the admin image]
REINSTALL=[list of features] 
REINSTALLMODE=vomu /qb

You can run this command line by creating a logon script, distributing it as a batch file, deploying it by using Systems Management Server, or using other software installation tools. The following table describes the command-line options.

Command-line option Description
[start] Required only for Windows 98 systems where Msiexec is not directly in the path.
Msiexec Executable file name for Windows Installer.
/i Enables Windows Installer to apply an update to an existing installation.
[path to updated .msi file on the administrative image] Path and file name of the Microsoft Installer package (MSI file) on the administrative installation point.
REINSTALL=[list of features] Specifies whether you want to reinstall specific features or reinstall all applications on the administrative image.
REINSTALLMODE=vomu Triggers the recache and reinstallation on the client computer.
/qb Suppress the End User License Agreement dialog box so administrators or end users will not be prompted by this dialog box.

For Office 2000 Server Extensions SP3, the value for [list of features] is as follows:

Complete

Optionally, you can substitute the parameter REINSTALL=ALL to reinstall all Office 2000 components on the client computer.

Applying Office 2000 Server Extensions SP3 under Windows 2000 or Windows XP

If your administrative installation point and all of your client computers are running Microsoft Windows 2000 or Windows XP, you can use IntelliMirror® technology to manage the installation of the update.


 Note    Be sure to test all software updates in a controlled setting before modifying your administrative installation point or deploying the new version throughout your organization.


To deploy a QFE fix or update under Windows 2000 or Windows XP
  1. Apply the update (MSP file) to the original Office administrative installation point.

    You will need to run the command line separately if you apply more than one MSP file to the administrative installation point — you cannot reference multiple MSP files on the same command line.

  2. Open the Software Installation snap-in within the Group Policy Object (GPO) that you are using to manage the existing Office installation.
  3. In the details pane, right-click the Office package, point to All Tasks, and then click Redeploy application.

    The next time the Group Policy is applied to the designated users or computer groups, the updated files are copied to the computers.

Note that you can redeploy a package only if it is being managed by Group Policy — that is, only if you originally installed it by using IntelliMirror software installation and maintenance, or if you brought it into a managed state under Windows 2000 or Windows XP.

Localized versions of the Server Extensions SP3 update

Localized versions of the Office 2000 Server Extensions SP3 are available in the following languages and can be downloaded from the Office XP Resource Kit Localized Tools page:

Arabic French Portuguese (Brazil)
Basque German Portuguese (Portugal)
Chinese (Pan) Greek Romanian
Chinese (Simplified) Hebrew Russian
Chinese (Trad.) Hungarian Slovak
Croatian Italian Slovenian
Czech Japanese Spanish
Danish Korean Swedish
Dutch Norwegian Thai
Finnish Polish Turkish

Files changed by Office 2000 Server Extensions SP3

The following table lists the file changed by the full-file version of Office 2000 Server Extensions SP3. If you need to confirm whether a share has been updated, you can check the related file version number.

File Version
Ows.dll 9.0.0.6228

Related links

For an overview of Office 2000 Service Pack 3, see Overview of Office 2000 Service Pack 3 in the Microsoft Knowledge Base.

For general information on applying an administrative update, see Deploying Product Updates from an Administrative Installation Point in the Office XP Resource Kit.

© 2009 Microsoft Corporation. All rights reserved.