/build/static/layout/Breadcrumb_cap_w.png

Office 2007 Language Pack

I added the french language pack to my english enterprise office installation. So I copied the whole CD into the office enterprise 2007 english directory.

I added the following to my setup.xml which is located in \Enterprise.WW :

<!-- Match GUI language with system language -->
<AddLanguage Id="match" ShellTransform="yes"/>
<!-- Add english US language pack -->
<AddLanguage Id="en-us" />
<!-- Add english US language pack -->
<AddLanguage Id="fr-fr" />

Those line make sure the french language pack get installed. ANd everything is working fine execpt that I get one anooying poup window when I double-click on setup.exe, even if I did an unattended installation via the OCT Tool.

Heres the screenshot:

http://img519.imageshack.us/my.php?image=o2007bi3.jpg

Any suggestions to remove the damn poup and make Office 2007 as the default install product ?

0 Comments   [ + ] Show comments

Answers (2)

Posted by: spartacus 16 years ago
Black Belt
0
You need to use the /config qualifier with setup.exe and supply the path to the setup xml file, something like

\\YourServerName\OfficeFolder\setup.exe /config \\YourServerName\OfficeFolder\Enterprise.WW\config.xml

Regards,

Spartacus
Posted by: jakeld 16 years ago
Senior Yellow Belt
0
By default setup.exe look in the enterprise.ww folder no ? The /config switch is used when the config.xml is located elsewhere.

From MS:

/config [path]


Specifies the Config.xml file that Setup uses during the installation. By default, the Config.xml file stored in the core product folder directs Setup to install that product. For example, the Config.xml file in the Pro.WW folder installs Microsoft Office Professional 2007. You can edit Config.xml to make additional customizations to the installation, including specifying one or more language versions to install.

Use /config on the Setup command line to point to the location of the default Config.xml file for a particular product or to point to a custom Config.xml file.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ