Need help with MSI in Wise???
This morning I was tasked with the following project:
To have my Beyond Compare 2.5.3 MSI check if an older version of software particularly Beyond Compare 2.4.1 is installed, if the system has it installed then go ahead and install just the update of Beyond Compare 2.5.3.
If the system does not have 2.4.1, then install 2.4.1 first and then 2.5.3 after. We are doing it this way because of licensing. We have 2.4.1 licensed so the update will just take over the license from the older version.
The question is: Can this be done? or is there a better way to do it.
FYI: This is going to be deployed with SMS 2003, so they want the MSI to do the versioning, not SMS.
Thank you,
Casey Edwards
To have my Beyond Compare 2.5.3 MSI check if an older version of software particularly Beyond Compare 2.4.1 is installed, if the system has it installed then go ahead and install just the update of Beyond Compare 2.5.3.
If the system does not have 2.4.1, then install 2.4.1 first and then 2.5.3 after. We are doing it this way because of licensing. We have 2.4.1 licensed so the update will just take over the license from the older version.
The question is: Can this be done? or is there a better way to do it.
FYI: This is going to be deployed with SMS 2003, so they want the MSI to do the versioning, not SMS.
Thank you,
Casey Edwards
0 Comments
[ + ] Show comments
Answers (6)
Please log in to answer
Posted by:
case2k5
15 years ago
Thanks Gizsha for the response.
If I did go with a script, I would have to write it to report to SMS properly and I am unsure how to do that. Does anybody know how to do this?
Thanks
If I did go with a script, I would have to write it to report to SMS properly and I am unsure how to do that. Does anybody know how to do this?
Thanks
Posted by:
anonymous_9363
15 years ago
ORIGINAL: case2k5Eh? From what I remember, BC is licensed using a simple registry entry, viz.a value called CertKey in the key 'HKEY_CURRENT_USER\Software\Scooter Software\Beyond Compare'. Why not simply add that registry entry to your 2.5 MSI?
We are doing it this way because of licensing. We have 2.4.1 licensed so the update will just take over the license from the older version.
As for the process of upgrading, check out MSDN topics on using the Upgrade Code and Upgrade table.
Posted by:
case2k5
15 years ago
I certainly did try adding the cert key reg entry in with no success. 2.5.3 doesn't recognize the cert key from 2.4.1
Any other suggestions?
I think we might just use SMS to run 2.4.1 as a pre-req and then install 2.5.3 on top.
Any other suggestions?
I think we might just use SMS to run 2.4.1 as a pre-req and then install 2.5.3 on top.
Posted by:
anonymous_9363
15 years ago
ORIGINAL: case2k5Why not snapshot the 2.4 ==> 2.5 upgrade and see what the license change is? It can't be anything too radical, can it? If it's a different reg key or, more likely, a change to the existing value's format/length, it can be added in the way I suggested.
2.5.3 doesn't recognize the cert key from 2.4.1
Posted by:
kiptek
15 years ago
i think just running a 2.4.1 install across the board followed by the 2.5.3 as you mentioned is the way to go with the least overhead. Of course you could always use appsearch or query the registry to find out if 2.4.1 or newer is installed, & if not, then do a nested MSI install to 2.4.1 then continue with your 2.5.3 upgrade. Of course you will have to be careful with your sequencing. Just remember the inherent cons with nested MSIs....
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.