Managing upgrade of setup kits without Merge Module
Sireesha
September 25th, 2009
Hi,
I try to explain the problem.
Initially I added vc++ redistributable Merge Modules like CRT,ATL,MFC,OpenMP,MFCLOC in MergeModules section in wise for windows installer 5.2 and created setup kits.
Sometime later we removed the Merge Modules from setup kit and plan to install vc++ redistributable vcredist_x86.exe as windows update.
The problem occurs when we upgrade existing setup kits without Merge Module.
It doesnt delete the previous version when we upgrade without Merge Module.
For eg: Install "setup kit with MM" having 1.0.0 version
Upgrade "setup kit without MM" having 1.0.1 version
It shows both versions in control panel.
Any idea?
Note:Merge Modules are redistributed via vcredist_x86.exe
UpgradeCode
Have you included all your past MSIs in the list of valid installs to be upgraded - ie check the upgrade table.
The reason you have two entries in ARP is that the previous version has not been removed correctly.
If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.
Merge Modules removal
I dont list the past MSI'S in the upgrade table.
It should be able to auto upgrade and downgrade depending upon Upgrade code.
My only problem is once I remove Merge modules from setup kit I am not able to do an upgrade as previous version still has Merge Modules.
Is there a way to remove Merge modules from new version and upgrade should happen automatically?
Can we create custom action to do upgrade after removal of Merge Modules?
We are using Wise for windows installer 5.21 professional edition.Is there any limitations in regarding to Merge modules removal while upgrading?
i dont have any support id ,but i need contact numbers of symantec support so i can talk to them.
Actually...
...but what you need first - STILL - is to thoroughly read up on how to use the Upgrade table. You will pay big-time to learn that using Symantec support!
Don't know why 'x' happened? Want to know why 'y' happened? Use ProcMon and it will tell you.
Think about using http://www.google.com before posting.
Upgrade
To perform an upgrade, the MSI doing the upgrading must be aware of any previous MSI files that it is supposed to upgrade. It is pointless for you to speculate that an MSI should be able to auto upgrade and downgrade depending on Upgrade code, as this is not the way that Microsoft designed it.
Look in the Microsoft Windows Installer SDK help file (which is installed by Wise) - it is called MSI.CHM
Here is an extract:
Upgrade Table
The Upgrade table contains information required during major upgrades. To fully enable the installer's upgrade capabilities, every package should have an UpgradeCode property and an Upgrade table. Each record in the Upgrade table gives a characteristic combination of upgrade code, product version, and language information used to identify a set of products affected by the upgrade. When the FindRelatedProducts action detects an affected product installed on the system, it appends the product code to a property specified in the ActionProperty column. The RemoveExistingProducts action and the MigrateFeatureStates action only remove or migrate products listed in the ActionProperty column.
Also look up "RemoveExistingProducts" and "Upgrade" - there is lots of useful information that can help you with your project.
Finally, I am frankly amazed that you are asking for contact number of Symantec support, when it is so easy to find this information on the internet.
However, you can start here:
http://www.altiris.com/Support/Contact%20Support.aspx
Give the number appropriate to your area a call and they will no doubt advise you how to make a chargeable support call, as it is possible to pay for each incident if you don't have a support contract.
If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.
Don't forget...
...that as well as populating the Upgrade table, you need to add the ActionCode properties to the SecureCustomProperties list.
Don't know why 'x' happened? Want to know why 'y' happened? Use ProcMon and it will tell you.
Think about using http://www.google.com before posting.
Can you explain more on this
Can you explain more on this
>Can you explain more on
>Can you explain more on this
Click this link ==> www.lmgtfy.com/
Don't know why 'x' happened? Want to know why 'y' happened? Use ProcMon and it will tell you.
Think about using http://www.google.com before posting.
LOL
I like this service !!
If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.
LMGTFY
One of the regulars on AppDeploy turned it up for us. It's neat, isn't it? I like the "How hard was that?" message before it goes to the Results page...
Don't know why 'x' happened? Want to know why 'y' happened? Use ProcMon and it will tell you.
Think about using http://www.google.com before posting.
Exceptionally neat
I can only think that this was designed by a support person !!
If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.
Liked that...
That was simple nice way to make people read your signature VBScab (Think about using http://www.google.com before posting).. Good one. :)
Would you like to reply?
Login or Register to post your comment.