MS project 2003 Standard
Hello all, I looked around but didn't find anything on packaging MS Project 2003 Standard.
It has 3 MSI's. OWC10, OWC11 and PRJSTD.
I believe I have to build a seperate MST for each one I wish to install, the OWC's appear to be the same so I figured I would go with 11 vice 10.
Has anyone done a multi MSI this way and had success?
Also to get a true silent install with Installshield tool what should be done when building the package.
It doesn't ask for the Key but I still have to click next--next--next and I wish to avoid that.
ej
It has 3 MSI's. OWC10, OWC11 and PRJSTD.
I believe I have to build a seperate MST for each one I wish to install, the OWC's appear to be the same so I figured I would go with 11 vice 10.
Has anyone done a multi MSI this way and had success?
Also to get a true silent install with Installshield tool what should be done when building the package.
It doesn't ask for the Key but I still have to click next--next--next and I wish to avoid that.
ej
0 Comments
[ + ] Show comments
Answers (4)
Please log in to answer
Posted by:
viv_bhatt1
18 years ago
Hi ,
PRJSTD is the main project MSI . OWC is used to install Office web components .
I had used Installshield Tuner to create a transform for both msi's and capture the product key , EULA and other questions in the response transform created by Tuner .
Then use Software delivery to sequence installation of PRJSTD + MST and OWC11 + MST .
You can alternatively use nested msi's functionality within your package to sequence OWC after PRJSTD . However I prefer sequencing through Software delivery as it gives you flexiblity to install either or both of msi's without any change to the package .
Cheers,
V
PRJSTD is the main project MSI . OWC is used to install Office web components .
I had used Installshield Tuner to create a transform for both msi's and capture the product key , EULA and other questions in the response transform created by Tuner .
Then use Software delivery to sequence installation of PRJSTD + MST and OWC11 + MST .
You can alternatively use nested msi's functionality within your package to sequence OWC after PRJSTD . However I prefer sequencing through Software delivery as it gives you flexiblity to install either or both of msi's without any change to the package .
Cheers,
V
Posted by:
erjones
18 years ago
How did you build the package so it does a silient install without asking for more information?
I use the editor and it asks for the Product Key and that's all.
When the msi runs to install it wants to know the name of the company, answer the EULA,
what type of installation etc...
I thought that could be taken care of in the property manager section.
ej
I use the editor and it asks for the Product Key and that's all.
When the msi runs to install it wants to know the name of the company, answer the EULA,
what type of installation etc...
I thought that could be taken care of in the property manager section.
ej
Posted by:
Lillude
18 years ago
After setting the property for Product key, Install Type etc give the command line as /qb or /qn to avoid the next--next--next clicking.
/qb is for quiet mode with basic dialog (with a progress bar only)
/qn is for quiet mode with no dialog box
hope this solves ur problem
/qb is for quiet mode with basic dialog (with a progress bar only)
/qn is for quiet mode with no dialog box
hope this solves ur problem
Posted by:
erjones
18 years ago
Actually I used msiexec /i 'nameofapp.msi' /qn but that didn't take care of the problem.
for some reason when I build the MST in the Tuner it will ask for the Product Key.
I enter that and it should move to the Name of user/company, EULA and what type of install
I want, typical, custom etc..
It doesn't do it goes straight to "tuner will now opend file"and puts me in validation mode.
After this I go to Package Validation and select "Dialogs" under "Application Configuration"
and select "Show Sequence" with "Installation Sequence" in the drop down window.
It runs through the remaining install information and I close and save.
Open the MST up again and finish configurations.
When running the MSI I find none of that information was kept and the installation is not
a silent install.
One of my co-workers is suggesting use the Enterprise version so we can do an Admin install.
I jus need to know how to fix this because I know this won't be the last app like this.
ej
for some reason when I build the MST in the Tuner it will ask for the Product Key.
I enter that and it should move to the Name of user/company, EULA and what type of install
I want, typical, custom etc..
It doesn't do it goes straight to "tuner will now opend file"and puts me in validation mode.
After this I go to Package Validation and select "Dialogs" under "Application Configuration"
and select "Show Sequence" with "Installation Sequence" in the drop down window.
It runs through the remaining install information and I close and save.
Open the MST up again and finish configurations.
When running the MSI I find none of that information was kept and the installation is not
a silent install.
One of my co-workers is suggesting use the Enterprise version so we can do an Admin install.
I jus need to know how to fix this because I know this won't be the last app like this.
ej
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.