I have done an admin install of an MSI which has been successfully distributed to clients. I have now updated one of the source files in the admin installation point (an Access MDE file) and want the clients to get this updated file.

But whenever I run msiexec /fvomus "msiname.msi" on a client machine, the newer file I copied to the admin install point is never copied to the client PC, it's as if windows installer doesn't notice the file is newer, and just leaves the out of date file on the PC as it is. I can force the updated file down to clients by using /fvamus, but this is not ideal as it means the updated file is always downloaded to the client no matter what, which is not really what I want.

Any ideas what could be going wrong when using the /fvomus switch?

Nick
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
ORIGINAL: nburgess
Any ideas what could be going wrong when using the /fvomus switch?
Your syntax. Try

. MSIEXEC /F MSIName.MSI REINSTALLMODE=vomus REINSTALL=ALL

Also, because MDEs aren't versioned, you'd need to make sure that the MSIFileHash table was updated.
Answered 05/22/2008 by: VBScab
Red Belt

Please log in to comment
0
Thanks VBScab, it worked a treat!
Answered 05/23/2008 by: nburgess
Senior Yellow Belt

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