Hi!

Changes in our business forces us to change some packages (e.g. Office 2000). We have deployed these packages with the vendor MSI and our MSTs. Now we need to change that MSTs.

Actually we only see one way to solve this: uninstall and reinstall the package with the new MST.

Any other suggestions?


cu Flo

ps.: OS on these machines: W2K.
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
A repair/modify doesn't work?
Answered 10/21/2005 by: sini
Orange Senior Belt

Please log in to comment
0
We exchanged/removed/added files in some cases, I don't see how this could be done by repair/modify. If we don't switch the MST the self-healing "heals" our new files ... e.g. Office templates in the userprofile (the old packager put them into the MST...).
Answered 10/21/2005 by: flo
Senior Yellow Belt

Please log in to comment
0
What deployment method are you using?

Could you use the REINSTALL property for this?
Answered 10/21/2005 by: brenthunter2005
Fifth Degree Brown Belt

Please log in to comment
0
We deploy via Intel LDMS and package with Wise & some tools.

I don't see how the REINSTALL property could help me, because before I can reinstall a feature, I need to change the content (stored in the MSTs cab file) of the feature... We have files in our transforms we need to change.


cu Flo
Answered 10/21/2005 by: flo
Senior Yellow Belt

Please log in to comment
0
Hello flo,

The reason why I suggested the REINSTALL property (on the command-line) is because this will re-evaluate your (new) MST and install any new features/components.

I've had to do this many times before (with SMS) and find this the best method.
Answered 10/21/2005 by: brenthunter2005
Fifth Degree Brown Belt

Please log in to comment
0
Hi,

I used my Office2000 example, the new MST and tried:

1.) %msipath1%\setuppro.exe transforms=cd1_%OfficeLang%.mst /wait /qb! REINSTALL=ALL REBOOT=REALLYSUPPRESS
2.) msiexec /i %msipath1%\data1pro.msi TRANSFORMS=cd1_%OfficeLang%.mst REINSTALL=ALL REBOOT=REALLYSUPPRESS /qb!

Neither of it worked. Maybe this is because the files are not stored in a component, when added via the "Office Resource Kit". It seems to me the new MST is not accepted. I didn't used a new name.


cu Flo
Answered 10/24/2005 by: flo
Senior Yellow Belt

Please log in to comment
0
Sorry, I assumed something that was silly.

You will also need to add the following property to your command-line:

REINSTALLMODE=vomus

This re-caches the MSI package on the computer with the updated MSI/MSTs.
Answered 10/24/2005 by: brenthunter2005
Fifth Degree Brown Belt

Please log in to comment
0
Oh, and be sure to read up on the REINSTALLMODE property before you use it!

The line I have specifed above will reinstall files, which you may not want. So check it first.
Answered 10/24/2005 by: brenthunter2005
Fifth Degree Brown Belt

Please log in to comment
Answer this question or Comment on this question for clarity