How can I tell when a package isn't extracting an MSI any where besides the temp folder?

I have a InstallShield installer, and i want to be perfectly sure that there isn't any MSI being extracted any where. Any thoughts on this would be very helpful.

Thanks in advance!
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
Filemon from Sysinternals...now Microsoft http://www.microsoft.com/technet/sysinternals/default.mspx

Monitor the installation, then search for .msi. You will have collected a ton of information but if an MSI is extracted you should be able to see it.
Answered 08/16/2007 by: yarborg
Blue Belt

Please log in to comment
0
Enable the DisableMSI policy and if the setup.exe is trying to execute any MSI it will be prevented and an error message will be displayed.
HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer

DisableMSI (REG_DWORD) =
0 or a missing Value Name, enables the installer.
A 1 disables the installer for non-managed applications.
A 2 disables the installer for all applications.

You should use:
DisableMSI (REG_DWORD) = 2
Answered 08/16/2007 by: AngelD
Red Belt

Please log in to comment
0
watch the running processes for msiexec.exe
Answered 08/16/2007 by: jmcfadyen
Fifth Degree Black Belt

Please log in to comment
0
If you do look for running msiexec.exe processes, have in mind if the Windows Installer (MSIServer) service has already started due to previous MSI installation the msiexec.exe process will be visible.

You could of course enable MSI logging and look for any newly created MSIxxxx.log file in the %temp% folder during or after you've installed the application.
Answered 08/16/2007 by: AngelD
Red Belt

Please log in to comment
0
Or.. Run filemon when logged on with an admin account.. In filemon highlight *CREATE*.. :P
Answered 08/17/2007 by: neo2000
Purple Belt

Please log in to comment
0
In filemon highlight *CREATE*..
There would be a lot of CREATE API queries during an install don't you think [;)]
Answered 08/17/2007 by: AngelD
Red Belt

Please log in to comment
0
ORIGINAL: AngelD

Enable the DisableMSI policy and if the setup.exe is trying to execute any MSI it will be prevented and an error message will be displayed.
HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer

DisableMSI (REG_DWORD) =
0 or a missing Value Name, enables the installer.
A 1 disables the installer for non-managed applications.
A 2 disables the installer for all applications.

You should use:
DisableMSI (REG_DWORD) = 2


Similar to the above, I would use the policies in the following way to enable full verbose logging

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer]
"Debug"=dword:00000007
"Logging"="voicewarmup"

Then all you do is check the local temp folder (%temp%) for the creation of an MSI log file if there has been any MSI activity. This log file will also contain the commandline that was executed, thus revealing the full path to where the MSI was extracted to/called from as well as any properties that are being passed to it.

Alan
Answered 08/23/2007 by: ab2cv
Orange Senior Belt

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