Hi All,

I know that repairing my installation needs the MSI file. I

thought that Windows cached a copy of it and used this for repairs,

modifications and uninstalls. Is there anything I can do to stop the

original MSI being needed? The only thing I can think of to make it

transparent to the user is to copy the MSI to %TEMPDIR%, run it from

there and then just leave it behind. Just want to know if anyone know how to Cache a copy of an MSI file so it doesn't need to repair from network sorce.
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
Windows DOES cache the MSI file itself, but not the .CAB files etc.
Answered 06/20/2005 by: brenthunter2005
Fifth Degree Brown Belt

Please log in to comment
0
Is there a way to cache the entire installation including cab files?
Answered 06/21/2005 by: UcMerrill
Senior Yellow Belt

Please log in to comment
0
You could copy it to the workstation, then launch it from there. But that's not a great idea. You end up with many, many original source files. Administrative chaos that defeats much of the purpose of MSI. Your best bet is to create Administrative Install Points on a DFS share. That provides fault tolerance and the source files can be moved transparent to the user if necessary. The Administrative Install Points can also be upgraded. I recommend setting security to read only with no directory browsing. The MSI's will know exactly where to find themselves but the users won't be able to look through directories to find them.
Answered 06/21/2005 by: VikingLoki
Second Degree Brown Belt

Please log in to comment
0
Thanks for you suggestions.
Answered 06/21/2005 by: UcMerrill
Senior Yellow Belt

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