/build/static/layout/Breadcrumb_cap_w.png

Office 2003 and ChainedInstall

Part of my organization's requirement's for Office 2003 is to install the MS
OrgChart 2.0 and Office 2007 file converters with every Office 2003
installation.

I've been attempting to utilize the [ChainedInstall_n] option within the
setup.ini and I do not see the applications installing. For simpicity, I
have copied the additional files/folders to the same network share as
the pro11.msi so I could use relative paths. For example:

[ChainedInstall_1]
TaskType=exe
Path=FileFormatConverters.exe
Cmdline= /quiet /passive

is at the end of my setup.ini and it never installs. I have also tried:
Path=\FileFormatConverters.exe
Path=.\FileFormatConverters.exe
and without the Cmdline option but all to no avail.

I've also tried the full path to the EXE but that did not work either.

The only other thing different is that I am using an MST created with the ORK.


But I do not see it installing or even attempting to install.

Am I missing something obvious?

0 Comments   [ + ] Show comments

Answers (2)

Posted by: nheim 17 years ago
10th Degree Black Belt
0
Hi Dave,
is it aloud to chain setup.exe with embedded MSI to it?
It depends on how and when it is called from the main setup.

Regards, Nick
Posted by: WisconsinPlatt 17 years ago
Senior Yellow Belt
0
Finally got this working after downloading the entsetup.exe from Microsoft and using the correct setup.ini format. The setup.exe and .ini were not correct. That's what I get for using what the last guy built and not going back to the media. :)
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