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
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Hi Casey,

What about using a VBscript for this one?

~Gizsha
Answered 10/23/2008 by: gizsha
Purple Belt

Please log in to comment
0
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
Answered 10/23/2008 by: case2k5
Orange Belt

Please log in to comment
0
ORIGINAL: case2k5
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.
Eh? 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?

As for the process of upgrading, check out MSDN topics on using the Upgrade Code and Upgrade table.
Answered 10/24/2008 by: VBScab
Red Belt

Please log in to comment
0
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.
Answered 10/24/2008 by: case2k5
Orange Belt

Please log in to comment
0
ORIGINAL: case2k5
2.5.3 doesn't recognize the cert key from 2.4.1
Why 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.
Answered 10/27/2008 by: VBScab
Red Belt

Please log in to comment
0
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....
Answered 10/27/2008 by: kiptek
Second Degree Green Belt

Please log in to comment
Answer this question or Comment on this question for clarity