Joe Buehler wrote: > I have created a modified .msi file (vs using a transform) for 1.4.0 rc5 > and invoke msiexec like this to perform an upgrade: > > msiexec.exe /fvomus %FILES%\openafs-en_US-1-4-RC5.msi /l*v > %TEMP%\openafs.txt > > The installer runs but does not upgrade anything. Adding /qf to get the > full user interface, I see that there are no components selected (i.e. > Client, Server, etc.) so I suppose that is why nothing got upgraded. > When I select the proper components the upgrade runs properly. > > The changes I made to the .msi look straightforward enough. Is this a > bug in the openafs mis setup, in my changes, or am I invoking misexec > incorrectly or...?
/fvomus is used when you are re-installing a previously installed package. One of the corrections to RC5 was to update the Product IDs. As you had never before installed this product, there were no components to re-install. The Product ID update was required for several reasons. The addition of the installed release notes as part of the client installation altered the component definitions. There was a need to provide separate Product IDs for the different build variations. There is a need to ensure that the "stable" tree has a different Product ID from the "development" tree. When installing 1.4.0 on your systems, you will not use /fvomus. When installing incremental updates to 1.4.x, you will use /fvomus. Jeffrey Altman
smime.p7s
Description: S/MIME Cryptographic Signature
