Upgrade application
Hi all,
I got a application I need to update, the new and old version of the application has the same product and upgrade code and no upgrade table.
Im using zenworks 4.1ir7 to push out the application using a msi/mst, my problem is if I do a new application pushing out the new msi nothings happens on the worksstation, I got to uninstall the old app and then push out the new but since they got the same product code can I use the upgrade table to solve this?
If I can is Orca the tool to use to add a upgrade table? And does anybody got a easy to follow instruction for adding tables and properties to your msi files.
And my 2 question, does anybody know about a good book regarding packaging
Cheers
Lelle Johansson
I got a application I need to update, the new and old version of the application has the same product and upgrade code and no upgrade table.
Im using zenworks 4.1ir7 to push out the application using a msi/mst, my problem is if I do a new application pushing out the new msi nothings happens on the worksstation, I got to uninstall the old app and then push out the new but since they got the same product code can I use the upgrade table to solve this?
If I can is Orca the tool to use to add a upgrade table? And does anybody got a easy to follow instruction for adding tables and properties to your msi files.
And my 2 question, does anybody know about a good book regarding packaging
Cheers
Lelle Johansson
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
gmorgan618
17 years ago
There is actually more than one GUID to an MSI package...
There is the Package Code - this is a unique indentifer for the MSI package, not the application
The Product Code - this is a unique indentifier for the Application
The Upgrade Code - this is a GUID which is used to connect application families. Usually this is the same for applications with the same Major version
If two different MSI's use the same Package GUID then the installation won't run (it will see it as already installed).
Same for Product Code
Upgrade code will check the Upgrade table, compare logic for version upgrade and react accordingly(e.g. Uninstall old version)
I would suggest changing the Package code and the Product code for you new application and then adding the upgrade code with version info of the old package to the new msi upgrade table. MSI's only recognize 3 version levels so 1.1.1 is the same as 1.1.1.1
I can't imagine that a retail company would design the MSI in this way, so i'm guessing it was done in house. It is completely against standard practice to change a retail GUID but if it was an in-house created MSI it shouldn't matter.
The Product Code is found in the properties table.
<I'm not sure how to change this without using FlexNet AdminStudio... I couldn't find the Package code using ORCA>
Luckily adminstudio offers a free trial download ... Unless anyone else knows how to recreate the Package Code GUID
The Package Code is found under Summary Information - I believe listed as "Revision Number"
Hopefully this helps out...
There is the Package Code - this is a unique indentifer for the MSI package, not the application
The Product Code - this is a unique indentifier for the Application
The Upgrade Code - this is a GUID which is used to connect application families. Usually this is the same for applications with the same Major version
If two different MSI's use the same Package GUID then the installation won't run (it will see it as already installed).
Same for Product Code
Upgrade code will check the Upgrade table, compare logic for version upgrade and react accordingly(e.g. Uninstall old version)
I would suggest changing the Package code and the Product code for you new application and then adding the upgrade code with version info of the old package to the new msi upgrade table. MSI's only recognize 3 version levels so 1.1.1 is the same as 1.1.1.1
I can't imagine that a retail company would design the MSI in this way, so i'm guessing it was done in house. It is completely against standard practice to change a retail GUID but if it was an in-house created MSI it shouldn't matter.
The Product Code is found in the properties table.
<I'm not sure how to change this without using FlexNet AdminStudio... I couldn't find the Package code using ORCA>
Luckily adminstudio offers a free trial download ... Unless anyone else knows how to recreate the Package Code GUID
The Package Code is found under Summary Information - I believe listed as "Revision Number"
Hopefully this helps out...
Posted by:
AngelD
17 years ago
gmorgan618 has given you the howto ;) so export the Upgrade table from another MSI or template and then import it to the "new" msi using ORCA and follow his advice. Just make sure to remove existing entries from the table you exported if any.
Posted by:
lelle68
17 years ago
Gmorgan and AngelD
Thanks for your quick reply, Im a bit short of time so I did solve my problem with a workaround this time, I will try to do it the proper way next week using the advice you guys gave me
Cheers
Lelle
Thanks for your quick reply, Im a bit short of time so I did solve my problem with a workaround this time, I will try to do it the proper way next week using the advice you guys gave me
Cheers
Lelle
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.