What table/property contains the version information that shows up in the Add/Remove programs -> "Click Here for support information"?

I tried finding the wrong version in my MSI but I can't find it (I actually didn't code the MSI, that person is not here anymore).

For example:

It shows up as say version: 6.4.3
But it's really 6.4.5

I only saw one spot for 6.4.3 and I edited it, but it doesn't seem to be the right spot, as it's still showing up "wrong".
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
"Productversion" is the property.
Answered 04/14/2008 by: reds4eva
Second Degree Blue Belt

Please log in to comment
0
ProductversionORIGINAL: reds4eva

"Productversion" is the property.


ProductVersion

Remember properties are case sensitive.
Answered 04/14/2008 by: aogilmor
Ninth Degree Black Belt

Please log in to comment
0
Thanks!

I had to use ORCA to edit the property, not Admin Studio (the version of Admin studio I have only makes transforms, not actually editing the .MSI file)

Now it works.
Answered 04/15/2008 by: kjhurni
Orange Belt

Please log in to comment
0
ORIGINAL: kjhurni
the version of Admin studio I have only makes transforms, not actually editing the .MSI file)
Your copy must be unique. That's not a restriction I've come across. Even the eval version edits MSIs...

If this is a vendor MSI, you should not be editing it, but using a transform instead. If you're having problems with applying the transform, you would best be advised to ask for advice here, rather than bypassing the issue in a non-recommended way.
Answered 04/15/2008 by: VBScab
Red Belt

Please log in to comment
0
It's the ZENworks edition of Admin Studio. It doesn't let you edit MSI files, only make transforms (among several other restrictions).

Even though the transform did have the correct property in it, it would not actually populate that section of the registry properly, so I had to edit the MSI directly.

The vendor actually is the one who messed up and issued a software update and forgot to edit their own MSI to put the updated version in there.

Already been apprised that it's "not supported" but it seems to work fine so far.

Thanks!
Answered 04/15/2008 by: kjhurni
Orange Belt

Please log in to comment
0
Jumping Jehesophats! Get yourself some proper tools! :) Even a freeware tool has to be a better option than a crippleware one, no?

As for the vendor's MSI...is anyone surprised? Irrespective of that, if your solution to a perceived inability of a transform to apply a new property value is to edit the MSI, your packaging career may be short-lived. Applying sticking plaster to a broken leg isn't going to make it heal.
Answered 04/15/2008 by: VBScab
Red Belt

Please log in to comment
0
So you're volunteering to figure out why the transform applies all other properties but not that one?

:)

So far, the ZEN edition of Admin Studio has served its purpose well, and this is the first time I've had to edit the MSI file itself.
Answered 04/15/2008 by: kjhurni
Orange Belt

Please log in to comment
0
ORIGINAL: kjhurni
So you're volunteering to figure out why the transform applies all other properties but not that one? :)
The tools detailed ad neaseum here - a verbose log and ProcMon - will be all you need to do that. Have fun.
Answered 04/16/2008 by: VBScab
Red Belt

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