How to perform a chain installation of Office 2003 and Office 2003 updates

View products that this article applies to.

Expand all | Collapse all

INTRODUCTION

This article describes how to perform a chain installation of Microsoft Office 2003 and Office 2003 updates.

Consider the following scenario. You want to integrate the installation of Microsoft Office 2003 and Microsoft Office 2003 Service Pack 1 (SP1). Additionally, you want to retain the Local Installation Source (LIS) functionality. However, only Office 2003 administrative installation points and administrative updates can be used to create source files that contain service packs and updates.

To take advantage of the Office 2003 LIS functionality, the installation must be performed from a Office installation CD or from a flat folder. Currently, you cannot update the contents of an Office installation CD or a flat folder.

You can use the Ohotfix.exe file and a modified Setup.ini file to chain together the installations of Office 2003 and Office 2003 SP1 or any other update that you want. To do this, follow these steps:

Create a network share that contains a copy of the Office 2003 CD. For example, create the following network share:
\\server\off2003
Download the OHotFix (Offinst.exe) utility. Then, extract the Ohotfix.exe file, the Ohotfixr.dll file, and the Ohotfix.ini file to a subfolder in the network share. For example, extract the files to the following subfolder in the network share:
\\server\off2003\ohotfix
To obtain the OHotFix utility, visit the following Microsoft Web site:
http://www.microsoft.com/office/orkarchive/XPddl.htm (http://www.microsoft.com/office/orkarchive/XPddl.htm)
Copy the .msp files that will be applied during the Office 2003 installation to the network share that contains the OHotFix files.

Note OHotFix applies all updates in the network share by using Microsoft Windows sort order. If you want the updates to be installed in a specific order, rename the updates accordingly. For example, rename the updates as 1_update.msp, 2_update.msp, 3_update.msp, and so on.
Make a backup of the Setup.ini file that is located in the Setup subfolder of the Office 2003 flat folder. The Setup.ini file is located in the following folder:
\\server\off2003\Files\Setup\
Rename the Setup.ini file as Setup.ini.old.
Open the Setup.ini file in a text editor such as Notepad.
Copy the following text to the end of Setup.ini file:
```
[ChainedInstall_1]
TaskName=Ohotfix Chained Updates
TaskType=exe
Path=\\server\off2003\ohotfix\ohotfix.exe
IgnoreReturnValue=0
```
Note The path in the copied text must reflect the location of the shared Ohotfix.exe file.
Save the Setup.ini file.
Install Office 2003 by running the Setup.exe file that is located in the following folder:
\\server\off2003
Note Chained installations occur only if you run the Setup.exe file. If you run the Msiexec.exe file to install Office 2003, the Setup.ini file is not read.

We recommend that you enable verbose logging during the installation of Office 2003. The verbose installer log file can be used to troubleshoot any issues that may occur. To create a verbose log file, use the following command at the Setup command prompt:

/L*V %temp%\Off2003.log

The Off2003.log file is created in the computer-specific temp folder or in the user-specific temp folder.

The following is a sample command for a quiet installation of Office 2003 with verbose logging enabled:

path of Office 2003 files\setup.exe /L*V %temp%\Off2003.log /QB

For a quiet installation that uses a basic progress indicator and no Cancel button, use the /QB! switch instead of the /QB switch. For a silent installation, use the /QN switch instead of the /QB switch. For more information about how to troubleshoot an update installation by using log files in Office 2003, click the following article number to view the article in the Microsoft Knowledge Base:

884290 (http://support.microsoft.com/kb/884290/ ) How to troubleshoot an update installation by using log files in Office 2003

For more information about how to deploy Office 2003 together with other products, visit the following Microsoft Web site:

http://office.microsoft.com/en-us/assistance/HA011402051033.aspx (http://office.microsoft.com/en-us/assistance/HA011402051033.aspx)

For more information about how to install client update files by using OHotFix, visit the following Microsoft Web site:

http://office.microsoft.com/en-us/assistance/HA011364081033.aspx (http://office.microsoft.com/en-us/assistance/HA011364081033.aspx)

For more information about strategies to update Office 2003 installations, view the "Patching an administrative installation point" section of the "Strategies for Updating Office 2003 Installations" topic. To view this topic, visit the following Microsoft Web site:

http://office.microsoft.com/en-us/ork2003/HA011525741033.aspx (http://office.microsoft.com/en-us/ork2003/HA011525741033.aspx)

For more information about how to take advantage of a local installation source, visit the following Microsoft Web site:

http://office.microsoft.com/en-us/assistance/HA011402031033.aspx (http://office.microsoft.com/en-us/assistance/HA011402031033.aspx)

For more information about how to change the local installation source after you install Office 2003, visit the following Microsoft Web site:

http://office.microsoft.com/en-us/ork2003/HA011402361033.aspx (http://office.microsoft.com/en-us/ork2003/HA011402361033.aspx)

For more information about how to distribute Office 2003 product updates, view the "To use the OHotFix utility to chain client patches" section of the "Distributing Office 2003 Product Updates" topic. To view this topic, visit the following Microsoft Web site:

http://office.microsoft.com/en-us/ork2003/HA011402381033.aspx (http://office.microsoft.com/en-us/ork2003/HA011402381033.aspx)