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.

Deploying Office 2000 Service Pack 2
 

Service Pack 2 for Office 2000 (SP-2) provides a collection of fixes and security updates designed to improve the performance and reliability of your applications. While SP-2 provides many benefits, it is an optional release and is not required to maintain the current functionality of your applications. The Microsoft Office 2000 SR-1 update continues to be the recommended minimum version.

Many of the fixes included with SP-2 were previously released as separate upgrades. This service pack combines them into one integrated package, and includes a number of other changes designed especially for corporate customers and large organizations.

Two separate versions of the SP-2 update are available —one for upgrading administrative installation points and the other for upgrading stand-alone computers. The file names are as follows:

  • Sp2admin.exe is the version for administrative installation points. This self-extracting executable contains four Windows Installer patches (MSP files) that need to be applied separately to the administrative share.
  • Sp2upd.exe is the version for stand-alone computers. This version includes an integrated Setup program that enables you to easily update computers not associated with an administrative installation point.

Office 2000 Service Pack 2 is distributed through the following channels:

  • Enterprise Agreement and Select customers receive SP-2 updates as part of the Select kit.
  • Subscribers to the Microsoft Developer's Network and Microsoft TechNet receive SP-2 through their standard subscriptions.
  • Administrators can download the SP-2 updates without charge from the Office Resource Kit Web site.

Toolbox    To download either version of the update, see Office 2000 Service Pack 2 in the Office Resource Kit Toolbox.



 Note    If you use Outlook® for Macintosh on a Microsoft Exchange Server and install Microsoft Office 2000 SP-2, you will experience a change that affects the Outlook for Macintosh Inbox Assistant rules. For information on resolving the rules compatibility issue, see topic Q280713, Unable to Define New Inbox Assistant Rules with Outlook for Macintosh, in the Microsoft Knowledge Base.


Changes and features in Service Pack 2

While SP-2 provides many updates that benefit large organizations, it is an optional release and is not required to maintain the current functionality of your applications. Accordingly, your first step may be to determine how the updates apply to your computing needs. What follows is a summary of several key components included in the SP-2 update.

Outlook 2000 SR-1 Security Update Administrative Tools

The Outlook 2000 SR-1 E-mail Security Update helps provide protection from most e-mail viruses, such as the ILOVEYOU and Melissa viruses, as well as other viruses that spread themselves through e-mail, or worm viruses that can replicate through Microsoft Outlook®. This update affects certain functionality in Outlook 2000, and you should ensure you understand the impact this update will have on your organization before deploying it. For more information, see Deploying the Outlook 98/2000 E-mail Security Update in the Office Resource Kit Journal. Details on the specific behaviors changed by the update can be found in the article Description of known interoperability issues with the Outlook E-mail Security update in the Microsoft Knowledge Base.

Excel 2000 Security Update: REGISTER.ID

The Microsoft Excel REGISTER.ID Security Update helps eliminate the vulnerability that could be exploited using the worksheet tools of Excel to do malicious acts, such as deleting and overwriting files without the user's input or verification. For more information, see Deploying the Microsoft Excel 2000 and Microsoft Excel 97 Register.ID function updates in the Office Resource Kit Journal.

Office 2000 Security Update: HTML Data

The Microsoft Office 2000 HTML Data Security Update helps eliminate a security vulnerability in Microsoft Word 2000, Excel 2000, and Microsoft PowerPoint® 2000. For more information, see Deploying the Office 2000 Html Data Security Update in the Office Resource Kit Journal.

Word 2000 Mail Merge Security Update

The Word 2000 Mail Merge Security Update helps protect you from a vulnerability in the mail merge function in Word by helping to increase the security in the connection between Word mail merge documents and Access databases. For more information, see Word Mail Merge Security Update in the Office Resource Kit Journal.

Excel/PowerPoint 2000 SR-1 Update: HTML Script Vulnerability

The Excel 2000 and PowerPoint 2000 SR-1 HTML Script Vulnerability Update helps eliminate a security vulnerability in the Excel 2000 and PowerPoint 2000 object models that could expose them to unsafe scripts when a user views a Web page or HTML e-mail message. For more information, see Deploying the Excel 2000 and PowerPoint® 2000 HTML Script Vulnerability Updates in the Office Resource Kit Journal.

Word 2000 Update: Proofing Tools Hyphenation

The Word 2000 Proofing Tools Hyphenation Update corrects an issue with the hyphenation feature of the proofing tools so that it works properly with long documents. For more information, see Word 2000 Update: Proofing Tools Hyphenation in the Office 2000 Update: Service Pack 2 (SP-2).

Word 2000 SR-1 Update: Mail Command Security

Install the Word 2000 SR-1 Mail Command Security Update to help eliminate a security vulnerability that could allow a malicious hacker to send a virus through e-mail by using the Word 2000 Visual Basic® for Applications command EmailSend. For more information, see Deploying the Word 2000 SR-1 Mail Command Security Update in the Office Resource Kit Journal.

Other changes

A large number of other updates and improvements have also been made in areas such as security, performance, graphics, and messaging. A complete list of all changes is provided in the workbook SP2Changes.xls, included with Office 2000 Service Pack 2.

A complete list of all files affected by the SP-2 administrative update can be found in the section "Files changed by the SP-2 administrative update," later in this topic.

Planning for an SP-2 deployment

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

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

Versions of Office 2000 affected by SP-2

Because SP-2 focuses on the core Office business applications, you need only apply the update to specific versions or administrative images. For example, if you're updating the administrative installation point for Office Premium, you apply the updates to only the Disc 1 image — discs 2, 3, and 4 are not affected by SP-2. The following products are updated by SP-2:

  • Microsoft Office 2000 SR-1 Premium disc 1
  • Microsoft Office 2000 SR-1 Professional disc 1
  • Microsoft Office 2000 SR-1 Standard
  • Microsoft Office 2000 SR-1 Small Business disc 1
  • Microsoft Outlook 2000 SR-1
  • Microsoft Access 2000 SR-1
  • Microsoft Excel 2000 SR-1
  • Microsoft Word 2000 SR-1
  • Microsoft FrontPage 2000 SR-1
  • Microsoft PowerPoint 2000 SR-1
  • Microsoft Access RunTime 2000 SR-1

If you attempt to update an Office 2000 administrative share that does not contain one of the products listed above, an error message will be displayed. The message states that the expected version of the product has not been found and the installation process is terminated.

Managing a staged deployment

For most organizations, the best way to deploy SP-2 is to create an updated image of the product on an administrative installation point. Local users can then connect to this share and update the version of Office installed on their computers.

If you are staging your upgrades over a period of time, you may need to maintain two administrative installation points during the process:

  • The original share serves as a source for clients who have not yet upgraded. Until they upgrade, clients may need access to the original share for install on demand, automatic feature repair, and other services.
  • The updated share serves as the installation point for SP-2.

If you need to create administrative installation points in multiple locations, you can copy the folder hierarchy and files from one administrative installation point to additional servers.

International support

The Office 2000 SP-2 release is available in all languages currently supported by Office 2000. The following table lists the languages supported by SP-2.

Arabic French Polish
Basque German Portuguese (Brazilian)
Chinese (pan) Greek Portuguese (Portugal)
Chinese (simplified) Hebrew Romanian
Chinese (traditional) Hindi Russian
Croatian Hungarian Slovakian
Czech Italian Slovenian
Danish Japanese Spanish
Dutch Korean Swedish
English Latvian Thai
Estonian Lithuanian Turkish
Finnish Norwegian

Determining which updates to apply to your administrative share

The SP-2 administrative update includes four MSP files designed to update your Office 2000 SR-1 applications. One of the MSPs contains fixes unique to the SP-2 release, while the other three contain updates that have been previously made available from Microsoft Web sites.

File name Description
Sp2admin.msp Contains the core changes for Service Pack2.
Out2kmst.msp Contains the Outlook 2000 E-mail Security Update.
Pptmsp.msp Contains the PowerPoint 2000 HTML Script Vulnerability Update.
Excelmst.msp Contains updates specific to Excel 2000.
Readadm.doc Readme file for Office 2000 Service Pack 2

If you are updating an administrative share, you need only apply those fixes not yet installed on the computer. For example, if you have already deployed the Outlook 2000 E-mail Security Update, you would not install Out2kmst.msp, which would attempt to duplicate the same fix.


 Note    The Out2kmst.msp, Pptmsp.msp and Excelmst.msp files update the registry, while the files on the computer are updated by Sp2admin.msp. Updated versions of all MSP files must be applied to the computer in order for the upgrade to succeed. Failure to apply all msp files will put the Office 2000 SP-2 Administrative image in an unsupported state.


The requirement for applying separate MSP files to complete the upgrade is due to a current limitation with Windows Installer. Microsoft plans to address this limitation shortly through a QFE update to Windows Installer. After the update, administrators will be able to install future Office updates through a single administrative file.

The following section describes the conditions under which you install each of the MSP files and lists the possible error conditions if you attempt to repeat an installation.

Sp2admin.msp The core update for SP-2 should be applied to all administrative shares.

Out2kmst.msp Not required if the Outlook 2000 E-mail Security Update has already been applied to the computer. If you attempt to apply this patch to a computer that already contains the Outlook update, the following error message is displayed:

Internal Error 2250: Please contact product support for assistance.

Pptmst.msp Not required if the PowerPoint 2000 HTML Script Vulnerability Update has already been applied to the computer. If you attempt to apply this patch to a computer that already contains the PowerPoint update, the following error message is displayed

Internal Error 2251: Please contact product support for assistance.

Excelmst.msp Not required if the patch for KB Q264719 (briefcase support registration) has already been applied to the computer. If you attempt to apply this patch to a computer that already contains the update, the following error message is displayed.

Internal Error 2251: Please contact product support for assistance.

Installing the SP-2 Administrative Update

The administrative update files for SP-2 are Windows Installer patches (MSP files) that you apply to your administrative share by using a command line with specific parameters. For best results, the patch files should be applied from the console of the computer containing the administrative installation point.

 Note   Before you update an administrative installation point, make sure that no clients are using the share. If a file on the share is in use during the upgrade process, a newer version of that file is not copied to the installation point.

To apply the SP-2 update to an administrative installation point

  1. Download Sp2admin.exe and double-click the file name to extract the administrative update files.
  2. Connect to the server share for the administrative installation point.

    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 SP-2 update. Use the following syntax:

    [start] msiexec /p [path\name of update MSP file] /a [path\name of MSI file] SHORTFILENAMES=TRUE /qb /L* [path\name of log file]

You will need to 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 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 SP-2 update (MSP file) from the Office Resource Kit Toolbox.
/a Enables Windows Installer to perform an administrative installation of a product on a network share.
SHORTFILENAMES=TRUE Directs Windows Installer to create all file names and folders with MS-DOS-compatible file names, as used on Office 2000 Disc 1. Required when you run Windows Installer from the command line.
/qb Sets the user interface to the basic level (simple progress and error handling).
/L* Turns on logging and sets a path for the log file. The * flag causes the switch to log all information.
[path\name of log file] Path and file name of the Windows Installer log file.

Updating client computers from an administrative installation point

After you update your administrative installation point, you must perform a recache and reinstallation on existing client computers that use the administrative image. Any new client installations from the administrative share will automatically include the updated version of Office 2000.

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 administrative image] REINSTALL=[list of features] REINSTALLMODE=vomus

You can run this command line by creating a logon script, distributing it as a batch file, deploying it via Systems Management Server, or using other means according to your practice. The options for this command line are as follows.

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 Windows Installer package (.MSI file) on the administrative installation point.
REINSTALL=ALL Specifies that you want to reinstall all applications on the administrative image.
REINSTALLMODE=vomus Triggers the recache and reinstallation on the client computer.


 Note   If you originally installed Office 2000 on a client computer from an administrative installation point, you must follow the recache and reinstallation procedure described above to update that client. If you update the client directly by using the stand-alone patch, the client and administrative images will become out-of-sync, which may cause future updates to fail.


Applying the SP-2 Update under Windows 2000

If your administrative installation point and all of your client computers are running Windows® 2000, you can use IntelliMirror® 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 an update under Windows 2000

  1. Apply the update or patch (MSP file) to the original Office administrative installation point.
  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 (MSI file), point to All Tasks, and click Redeploy application.
  4. The next time the Group Policy is applied to the designated users or computers, the updated files are copied to their computers.

 Note   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.


Updating a stand-alone computer

The SP-2 update for stand-alone computers (Sp2upd.exe) includes a Setup program that enables you to deploy the upgrade on computers not associated with an administrative installation point.

You can also run the SP-2 update from the command line if you want to run the update in quiet mode or control other installation options. The following table lists the command-line options supported by the Setup program for Sp2upd.exe.

Command-line option Description
/Q Specifies quiet mode – no user interface or interaction.
/T:<full path> Specifies a temporary working folder in which the update files are cached during the installation.
/C When used with the /T option, extracts the files for the stand-alone update and copies them to a directory you specify.
/C:<cmd> Enables a user-defined command to override the Setup process.

To install the SP-2 update on a stand-alone computer

  1. Download the file Sp2upd.exe and copy it to a working directory on your computer. As an alternative, you can obtain a copy of the file from one of the sources mentioned earlier in this document.
  2. Close all Windows-based applications.
  3. Double-click the file name to install the update automatically.

    - or -

    To run the update with command-line options, click Run on the Start menu and type the update name with the appropriate options. For example, to run the update from the C:\Temp folder in quiet mode, type c:\temp\sp2upd.exe /q

  4. When the update starts and the license agreement dialog box is displayed, read the agreement and click Yes to continue the installation.
  5. Follow the instructions on your screen to complete the upgrade. Restart your computer after the installation is complete.

Files changed by the SP-2 administrative update

The following table lists the files changed by the SP-2 administrative update. If you need to confirm whether or not a share has been updated, you can check the related file version number to confirm.

File Name New version number
bjablr32.dll 1.0.3.27
bjlog32.dll 3.2.0.26
bjsrch32.dll 1.0.3.27
cag.exe 5.2.1.405
cdo.dll 5.5.2652.65
chapi3t1.dll 1.1.0.4130
contab32.dll 9.0.0.4506
Emablt32.dll 1.0.3.27
Emsabp32.dll 5.5.3142.0
emsmdb32.dll 5.5.3144.0
emsui32.dll 5.5.3141.0
envelope.dll 9.0.0.4201
excel.exe 9.0.0.4430
exsec32.dll 5.5.3143.0
fp4awec.dll 4.0.2.4022
fpeditax.dll 4.0.2.4426
frontpg.exe 4.0.2.4426
graph9.exe 9.1.0.4207
mimedir.dll 9.0.0.4005
msaccess.exe 9.0.0.4506
msgr2en.lex Non versioned
msmapi32.dll 5.5.3145.0
mso9.dll 9.0.0.4402
msonsext.dll 9.0.0.4105
msowc.dll 9.0.0.4309
mspst32.dll 5.5.3138.0
msqry32.exe 9.0.0.4430
oladd.fae 9.0.0.3731
olsec9.chm Non versioned
olxchng9.aw Non versioned
olxchng9.chm Non versioned
omi9.dll 5.5.3134.0
omint.dll 5.5.3134.0
outex.dll 8.30.3145.0
outlhlp9.aw Non versioned
outllib.dll 9.0.0.4527
outllibr.dll 9.0.0.4527
photoed.exe 3.0.1.1
powerpnt.exe 9.0.0.4527
ppttools.ppa Non versioned
pstprx32.dll 9.0.4525.0
rm.dll 9.0.0.4307
sendto9.dll 9.0.0.4201
utility.mda Non versioned
vbe6.dll 6.0.89.67
winword.exe 9.0.0.4527
wrd6ex32.cnv 2000.3.16.0
ww9intl.dll 9.0.0.4527

Related links

For more information about the Office 2000 SP-2 update, see the following articles in the Microsoft Knowledge Base:

© 2009 Microsoft Corporation. All rights reserved.