Article ID: 919293 - View products that this article applies to.
By default, the Office Source Engine does not recognize system environment variables in the Office Delivery sources path when you implement a local installation source with Microsoft Office 2003. This article describes a new functionality that enables the Office Source Engine to recognize system environment variables. Additionally, this article discusses how to enable this new functionality.
How to enable the new functionalityTo enable the new functionality that enables the Office Source Engine to recognize system environment variables, install the hotfix that is described in the following Microsoft Knowledge Base article:
(http://support.microsoft.com/kb/915433/ )Description of the Office 2003 hotfix package: April 5, 2006
Usage informationAfter you enable this new functionality, you can use System Environment Variables in the Office Delivery sources path. The following is an example of a defined system environment variable in the Path registry entry.
To change the default Office Delivery sources path or to specify additional redundant source servers for fault tolerance, you can use the Custom Maintenance Wizard.
Collapse this tableExpand this table
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/913420/ )Error message when you try to repair, reinstall, or add a component to an Office 2003 program and you use a Local Installation Source: "Installation Error: File Not Found"
Scenario informationThe following scenario describes a situation in which you would need this new functionality. You used the local installation source to deploy Office 2003. However, the original source is no longer valid. The following list contains two examples of an original source:
Note The first time a system environment variable is defined, the computer typically must be restarted before the new value takes effect.
Article ID: 919293 - Last Review: May 24, 2006 - Revision: 1.9