/build/static/layout/Breadcrumb_cap_w.png

Use of Installer Cache Folder

I got a scenario like

I installed an app from network share and while using the connection is failed......

if any key path is missed then obviously it has to go for self heal.... right

Then 'll it again ask for source? or take the MSI from cache folder and got repaired?

I want to clarify that actually when the Installer mSI cache is used and what it contains? Is it same as the Original MSI file? Why the size of the cached msi is less compared to Original MSI


pls clear my doubt

Thanks in Advance

0 Comments   [ + ] Show comments

Answers (5)

Posted by: itolutions 12 years ago
Purple Belt
0
You need original sources if some media are left. But for repairing regsitry Windows Installer can use local cache.
Posted by: itolutions 12 years ago
Purple Belt
0
=> Local Cache = "Original MSI" minus "Media" ( files/cabinets).
Posted by: laxmikanth 12 years ago
Yellow Belt
0
thanks.......
Posted by: gummalla 11 years ago
Senior White Belt
0

Hi,

Have a issue where the msi goes for selfhealing it should pick up the msi from the installer folder but instead it keep asking me for the source from where it was installed. i install on win7 environment and push teh app through sccm . Anyhelp solving this?

Posted by: gummalla 11 years ago
Senior White Belt
0

I install an app from sccm on win7 machine. during selfheal the msi checkes for the source msi from which the app was installed ( the cache). but instead i want it to pick the msi from installer folder which deos not happen any solution?

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ