[gptalk] Re: Lost MSI
- From: Darren Mar-Elia <darren@xxxxxxxxxx>
- To: <gptalk@xxxxxxxxxxxxx>
- Date: Wed, 5 Mar 2008 12:27:55 -0600
MSIs are typically cached locally but I am not at a machine to confirm where.
They are either in per-user or per-computer Temp folder or in
c:\windows\installer
Darren
-----Original Message-----
From: "Minesh Pandya" <mpandya@xxxxxxxxx>
To: gptalk@xxxxxxxxxxxxx
Sent: 3/5/2008 12:16 PM
Subject: [gptalk] Re: Lost MSI
I think you may be right as I did try the given steps but couldn't find
anything of substance...
most probably applications which are run locally from an MSI are
stored locally, but those via policy are removed after installation, but
that doesn't answer how the application/msi is able to repair.
Yes from gpsi
______________________
Minesh Pandya
Network Analyst
Barlow Lyde & Gilbert LLP
MPandya@xxxxxxxxx
+44 207 643 7629
http://www.blg.co.uk
"Jonathan Finkbiner" <JFinkbiner@xxxxxxx>
Sent by: gptalk-bounce@xxxxxxxxxxxxx
05/03/2008 18:07
Please respond to
gptalk@xxxxxxxxxxxxx
To
<gptalk@xxxxxxxxxxxxx>
cc
Subject
[gptalk] Re: Lost MSI
I think MSI?s are packages that extracted first, then the Windows
Installer service does it?s thing. Once the files are extracted, I believe
the MSI goes away and the Windows Installer service writes information to
the registry about the extracted files which then can tell the Windows
Installer service how to rebuild the package in the event something
happens. The original source is probably kept on the computer somewhere
and you maybe able find it by tracing from the registry. Once you find the
source you would have to use Visual Studio or something to rebuild the MSI
file.
[truncated by sender]
***********************
You can unsubscribe from gptalk by sending email to
gptalk-request@xxxxxxxxxxxxx with 'unsubscribe' in the Subject field OR by
logging into the freelists.org Web interface. Archives for the list are
available at //www.freelists.org/archives/gptalk/
************************
Other related posts:
