Thank you for the posting again.
We performed further research and testing on this issue based on your
We found this behavior occurs when Office 2003 is installed but the
ENTERPRISE_IMAGE=TRUE property is not set.
To resolve this problem, re-create the image including the ENTERPRISE_IMAGE
property. To do this, follow these steps:
1. Run Setup with the /a option to create an Office 2003 administrative
NOTE: Type the 25-character Volume License Product Key that is assigned to
your organization, and not the retail product key, when you create the
2. Do one of the following:
- On a computer that has never had Office 2003 installed, click "Start",
and then click "Run". Type the name and path to Office 2003 Setup, append
NOUSERNAME=True ENTERPRISE_IMAGE=True, and then click "OK". For example,
type the following: "\\server\share\admin_install_point\setup.exe
NOUSERNAME=True ENTERPRISE_IMAGE=True" (without the quotation marks)
- If you use the Custom Installation Wizard, start the Custom Installation
Wizard, and then set the following properties on the "Modify Setup
ENTERPRISE_IMAGE=True Save the settings in the Custom Installation
Wizard. On a computer that has never had Office 2003 installed, click
"Start", and then click "Run". Type the name and path to Office Setup, and
then click "OK".
3. After Office 2003 is installed, create a disk image.
For additional information about how to create an imaged-based installation
of Microsoft Office 2003, see the following Microsoft Web site:
Hope the above information and suggestion helps and answers your question.
If anything is unclear or if there is anything further we can help you
with, please let me know.
MCSE2000, MCSA2000, MCDBA2000
Microsoft Partner Online Support
Get Secure! - www.microsoft.com/security
When responding to posts, please Reply to Group via your newsreader so
that others may learn and benefit from your issue.
This posting is provided AS IS with no warranties, and confers no rights.