Software Deployment

A repair/modify doesn't work?

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...).

What deployment method are you using?

Could you use the REINSTALL property for this?

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

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.

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

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.

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.