Upgrade an application with same version
I am facing a strange problem , we have deployed Adobe 8.0 in our organization thru AD. Now we have made some changed in the adobe 8.0 package and want it to be installed again. How can i make a transform which will install the previod Adobe 8.0 and reinstall the new one. I tried entering the product code of Adobe 8.0 msi into the new transform and changing the product code, but no luck. Please help me
0 Comments
[ + ] Show comments
Answers (8)
Please log in to answer
Posted by:
mazessj
17 years ago
msi_learner,
I'm not quite sure what you have done in your environment. Can you please provide more details? Please list each package name and version, revision history, and intended goal.
If I understand what you did, you installed Adobe Reader 8.0 with whatever product code it uses, then made a revision via a transform and now want everyone to get those revisions. The problem is that Adobe Reader 8.0 is already installed for some number of users, so no matter what you do to the transform short of changing the product code, it will not reinstall. The only answer to that problem is to push an uninstall job and then push another install job, since changing the product code is a very bad idea. An alternative might be to push a patch or fix to the existing users, but that seems needlessly complicated.
So simply uninstall, then reinstall.
--Josh
I'm not quite sure what you have done in your environment. Can you please provide more details? Please list each package name and version, revision history, and intended goal.
If I understand what you did, you installed Adobe Reader 8.0 with whatever product code it uses, then made a revision via a transform and now want everyone to get those revisions. The problem is that Adobe Reader 8.0 is already installed for some number of users, so no matter what you do to the transform short of changing the product code, it will not reinstall. The only answer to that problem is to push an uninstall job and then push another install job, since changing the product code is a very bad idea. An alternative might be to push a patch or fix to the existing users, but that seems needlessly complicated.
So simply uninstall, then reinstall.
--Josh
Posted by:
nheim
17 years ago
Posted by:
msi_learner
17 years ago
Posted by:
nheim
17 years ago
Hi msi_learner,
had this question arising couple of years ago, when we started with GPO-deployment. But it is a quite logical behavior.
As long as you have your app installed by GPO, its kept there by the GPO. If you want to use an uninstall fired up by an entry from an other MSI's ugrade table, you have to remove the this app from the GPO, but not from the clients (using context menu again and choose 'Remove... from the 'All Tasks' entry and then 'Allow users to continue...'). This 'frees' the app from being controlled by the GPO and then it can be uninstalled with the method you like.
Another approach would be to let the GPO do the upgrade, by using the 'Upgrades' tab from the properties context menu of an installed app. There you can choose an app which you want to upgrade with the current one.
Hope this gives you some ideas.
Regards, Nick
had this question arising couple of years ago, when we started with GPO-deployment. But it is a quite logical behavior.
As long as you have your app installed by GPO, its kept there by the GPO. If you want to use an uninstall fired up by an entry from an other MSI's ugrade table, you have to remove the this app from the GPO, but not from the clients (using context menu again and choose 'Remove... from the 'All Tasks' entry and then 'Allow users to continue...'). This 'frees' the app from being controlled by the GPO and then it can be uninstalled with the method you like.
Another approach would be to let the GPO do the upgrade, by using the 'Upgrades' tab from the properties context menu of an installed app. There you can choose an app which you want to upgrade with the current one.
Hope this gives you some ideas.
Regards, Nick
Posted by:
N615
17 years ago
I'm having the exact same problem, except that my organization doesnt use GPOs (dont ask me why).
We deployed Adobe 8 to thousands of machines, only to find out that our locked settings of disabling the PDF in browser prohibited most from doing their job. So we've been tasked with creating a new package to push out. The problem is that a new package will not change anything since the product codes are the same. I need to create an uninstall that runs before the new 8 package takes off. I did this using a VB script. I'm having trouble getting it sequenced properly in a custom action. Also, I'd like the MSI to search for the registry key that locks the machine down to determine to install the new package or not .
Ive also tried changing the product/upgrade codes in my new package so that the existing install wouldn't try to just do a repair. No go. even with different codes, the new package wont install over the existing installation of the locked down package. Help!
We deployed Adobe 8 to thousands of machines, only to find out that our locked settings of disabling the PDF in browser prohibited most from doing their job. So we've been tasked with creating a new package to push out. The problem is that a new package will not change anything since the product codes are the same. I need to create an uninstall that runs before the new 8 package takes off. I did this using a VB script. I'm having trouble getting it sequenced properly in a custom action. Also, I'd like the MSI to search for the registry key that locks the machine down to determine to install the new package or not .
Ive also tried changing the product/upgrade codes in my new package so that the existing install wouldn't try to just do a repair. No go. even with different codes, the new package wont install over the existing installation of the locked down package. Help!
Posted by:
nheim
17 years ago
Hi N615,
are we talking about "Acrobat Reader" or the Full Acrobat here?
Which deployment system are you using?
The thing with the VBS custom action can't work at all, because its not possible to have two MSI's running their 'InstallExecuteSequence' sequence. You could try to sequence the VBS in the UISequence table and run the MSI with the /qb switch.
Please do the following: Try the upgrade procedures again, but use the property 'REMOVE_PREVIOUS="YES"' on the command line or with a transform. That should do the trick.
Regards, Nick
are we talking about "Acrobat Reader" or the Full Acrobat here?
Which deployment system are you using?
The thing with the VBS custom action can't work at all, because its not possible to have two MSI's running their 'InstallExecuteSequence' sequence. You could try to sequence the VBS in the UISequence table and run the MSI with the /qb switch.
Please do the following: Try the upgrade procedures again, but use the property 'REMOVE_PREVIOUS="YES"' on the command line or with a transform. That should do the trick.
Regards, Nick
Posted by:
mazessj
17 years ago
Posted by:
nheim
17 years ago
Hi Joshua,
are you kidding? Have you ever had any support from a vendor, regarding there installer/MSI? :-(
I agree with you, that no one shouldn't change a product code frivolously, without knowing exactly what the consequences are.
But there are situations, where this is the best of all bad solutions.
Regards, Nick
are you kidding? Have you ever had any support from a vendor, regarding there installer/MSI? :-(
I agree with you, that no one shouldn't change a product code frivolously, without knowing exactly what the consequences are.
But there are situations, where this is the best of all bad solutions.
Regards, Nick
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.