Adobe reader upgrade from 7.1.0 to 7.1.1
Hello experts,
I would like to patch 7.1.1 Msp to existing Adobe reader 7.1.0. what I tested are (using SMS)
1) MSIEXEC /p "AdobeReader711.msp" Reinstallmode=omus Reinstall=all /qb!
it worked well but I couldn't fix shortcut problem. Existing reader's shortcut was renamed with version name by Transform. and applying MSP doesn't help even though I changed shortcut name in Msp.It might be because shortcut name is not from MSI but from MST. how can I easily rename shortcut while applying msp?
2) since I couldn't rename the shortcut, I made admin install with all the patches including 7.1.1 and renamed shortcut accordingly. In SMS envrionment, to remove previous version (7.1.0), we used to chain removal-7.1.0 and install-7.1.1. So, my package don't do anything for removal of old version but SMS does.
Question ) my boss asked me to use upgrade option in Msi. So new MSI detect old version and remove it and install new one. and its process looked simple according to manual, just add upgrade code, min/max version, Securecustomproperties etc.. but in my case, it didn't work, saying old version still exists etc. Is it becuase upgrade table only valid for major upgrade which has different product code? what might be wrong for me?
I would like to patch 7.1.1 Msp to existing Adobe reader 7.1.0. what I tested are (using SMS)
1) MSIEXEC /p "AdobeReader711.msp" Reinstallmode=omus Reinstall=all /qb!
it worked well but I couldn't fix shortcut problem. Existing reader's shortcut was renamed with version name by Transform. and applying MSP doesn't help even though I changed shortcut name in Msp.It might be because shortcut name is not from MSI but from MST. how can I easily rename shortcut while applying msp?
2) since I couldn't rename the shortcut, I made admin install with all the patches including 7.1.1 and renamed shortcut accordingly. In SMS envrionment, to remove previous version (7.1.0), we used to chain removal-7.1.0 and install-7.1.1. So, my package don't do anything for removal of old version but SMS does.
Question ) my boss asked me to use upgrade option in Msi. So new MSI detect old version and remove it and install new one. and its process looked simple according to manual, just add upgrade code, min/max version, Securecustomproperties etc.. but in my case, it didn't work, saying old version still exists etc. Is it becuase upgrade table only valid for major upgrade which has different product code? what might be wrong for me?
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
clyrigham
13 years ago
Did you try to put the exactly upgrade code of 7.1.0?
Just to be curious, Why are you upgradint to 7.1.1 and not to 9.x?
Just to be curious, Why are you upgradint to 7.1.1 and not to 9.x?
Posted by:
jcarri06
13 years ago
I think you may just have an issue where the RemoveExistingProducts action is in the wrong sequence.
On your admin created 7.1.1 msi (should actually be on an MST, but choice is yours), go into the InstallExecuteSequence table and located the RemoveExistingProducts action. Change the sequence number so that it´s between the InstallValidate and InstallInitialize actions (usually 1450). This will make your new msi uninstall 7.1 first and then install 7.1.1.
Hopefully this works for you! Good luck.
On your admin created 7.1.1 msi (should actually be on an MST, but choice is yours), go into the InstallExecuteSequence table and located the RemoveExistingProducts action. Change the sequence number so that it´s between the InstallValidate and InstallInitialize actions (usually 1450). This will make your new msi uninstall 7.1 first and then install 7.1.1.
Hopefully this works for you! Good luck.
Posted by:
faithkim
13 years ago
Thanks for the advice :)
I changed seq Nr but it doesn't work. It detects old version and abort.
Still struggling
I changed seq Nr but it doesn't work. It detects old version and abort.
Still struggling
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.