Software Deployment

Try the upgrade table - it's there for just this situation.

Thanks,

Dunnpy

I have some problem in using the upgrade table.

while upgrading from old version to existing version, the old version is prompting for user interaction. we dont want any user interaction.

That is the reason i couldn't able to use upgrade table.

while upgrading from old version to existing version, the old version is prompting for user interaction. we dont want any user interaction.

That is the reason i couldn't able to use upgrade table.

what's the difference then with doing an uninstall manually? are you using command line parameters?

I am suppresing the prompt while uninstall. I am adding one additional property to the custom action for uninstall.

Here is the command line i have used in wise script.
msiexec /X {ProductCode} TSC_DATA_STORE=0 /qb

if u will put Upgrade code of old package into the new one, it will automatically remove the previous and install the new one.

Here is the command line i have used in wise script.
msiexec /X {ProductCode} TSC_DATA_STORE=0 /qb

if you want to make sure the parameter gets passed to the previous version, you could try changing the UninstallString for the application in the registry at HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall.

I'm not 100% sure if this will work though, since it might be this only gets used when you manually uninstall an application in the Add/Remove Programs window.

Another option is to look for the cached copy of the MSI in the Windows\Installer folder, and replacing it with a version of the MSI where the property is set to 0.

I suggest you try option 1 first since it's alot simpler. If that doesn't work we'll look into option 2 [:)]

PJ

Hi,

Since two MSI-based install processes cannot run at the same time, you can run your custom action only in InstallUISequence. It doesn't really matter after what standard action. I usually place them right before ExecuteAction so it looks like it's part of the install process.

Using "Upgrade" table is a solution, but you cannot set TSC_DATA_STORE this way.

Regards,
John

you can run your custom action only in InstallUISequence.You should never run CAs of this nature in the UI sequence, since if the installer chooses to run it silently (or it gets deployed by something like SMS/SCCM) the CA will never execute, something which you yourself allude to here!

Hi Ramu,
which part of this command line is needed to suppress the prompt?
TSC_DATA_STORE=0 OR /qb ?
Regards, Nick