Description of the Office 2003 Resource Kit hotfix package: March 21, 2008

This article describes the Microsoft Office 2003 Resource Kit issue that is fixed in the Office 2003 Resource Kit hotfix package that is dated March 21, 2008.

Issues that the hotfix package fixes

You install Microsoft Office 2003 by using a custom transform that adds files. In this scenario, the installation of Office 2003 is not completed successfully.

Note This software update will not fix this issue if you are redirecting user profile folders, such as the Application Data folder, the Desktop folder, or the My Documents folder.

For more information about this issue, click the following article number to view the article in the Microsoft Knowledge Base: This hotfix is for post-deployment environments only where it is not practical to redeploy with a transform that is built with the corrected Custom Installation Wizard (Custwiz.exe). The hotfix that is described in this article is intended to resolve this issue only when the following conditions are true:

• The symptoms occurred during a test phase or during a pilot phase.
• The transform has not been widely deployed already.

We recommend that you apply the hotfix in Microsoft Knowledge Base article 835209 if you can, instead of installing the hotfix that is described in this article. After you apply the 835209 hotfix, use the corrected Custom Installation Wizard (Custwiz.exe) to update the transform.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

There are no prerequisites for installing this hotfix.

Restart information

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix is not replaced by any later hotfix.

Registry information

To use one of the hotfixes in this package, you do not have to make any changes to the registry.

Hotfix file information

This hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain all the files that you must have to fully update a product to the latest build.

The global version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Download information
Microsoft Windows Installer .msp file information
Ocwcpyf.msp file informationNote For additional information about installing this hotfix, see the Readme.txt file that is included in the hotfix package.

For more information about the terminology that Microsoft uses when correcting software after it is released, click the following article number to view the article in the Microsoft Knowledge Base: