I copied this from TechNet. It's kinda long, but I wanted to make sure you got the necessary info.
The whole article is extremely long, so here is the url.
Upgrade Client Computers on a Network
For most organizations, the best way to deploy Office 2000 SR-1 is to create an updated image of the product on an administrative installation point. Users can then connect to the local server and install the SR-1 update on their computers.
In many cases, you need to maintain two administrative installation points during your upgrade process:
An Office 2000 SR-1 share from which clients upgrade to Office 2000 SR-1 through the recache and reinstallation process.
An original Office 2000 share to serve as a source for clients who have not yet upgraded. Until they upgrade, these clients need access to the original share for install on demand, automatic feature repair, and so on.
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.
Your strategy for upgrading an administrative installation point may depend upon whether your server runs under Windows NT 4.0 or Windows 2000. This article focuses on Windows NT 4.0. The information also applies to Windows 2000 servers that support non-Windows 2000-based client computers.
For more information about working with Windows 2000, see "Install Windows 2000 and Office SR-1 at the Same Time," later in this article.
Upgrade the administrative installation point
There are two ways in which you can create an upgraded administrative installation point for Office 2000 SR-1:
Create a new administrative share with the full Office 2000 SR-1 product by running Setup with the appropriate command-line options.
Run the administrative version of the SR-1 update, which is designed to upgrade Office 2000 administrative installation points.
The administrative update for SR-1 produces the same upgraded version of Office that the standard update produces. The difference between the two is that the administrative update contains complete updated files, rather than binary patches for the original files. The complete files allow the administrative update to correctly replace files on the server that have been modified with Microsoft QFE updates.
Note The standard version of the SR-1 update does not correctly upgrade an administrative share, so be sure to obtain either the administrative version of the update or the full Office 2000 SR-1 product before proceeding. You can reuse your existing transform (MST file) on an updated administrative image to reproduce the same customizations for new client installations.
Create a new administrative share with the full Office 2000 SR-1 product
In some cases, the simplest solution may be to obtain a full copy of Office 2000 SR-1 and create a new administrative installation point for the upgraded product. A new installation created from the full Office 2000 SR-1 product is nearly identical to an upgraded version created with the administrative update.
If you modified files in your original Office 2000 administrative installation point such as Setup.ini or Offcln9.opc, you must make the same modifications to these files in your new image. Note that the SR-1 copies of these files are not identical to the original versions. You must add your modifications to the new files rather than copying the old files to the new image.
Update an existing Office installation point
To install the administrative update, you run the Windows Installer from a command line with the appropriate file references and options. (The administrative update does not provide an installation interface like the standard update.) On the command line, you specify the path to the Office 2000 MSI file and the name of the Office SR-1 MSP file.
The MSI file is the Windows Installer package file (Data1.msi) in your original administrative image.
The MSP file is the Windows Installer administrative update file that contains information on the changes in the SR-1 upgrade. The update instructs the Windows Installer to add, update, or remove files in the administrative image.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.