Question about V9 MSI/MST File
Posted: Mon Jan 25, 2021 10:01 am
Hi Tracker Support Team,
I plan to upgrade all our machines from V7 to V9.
For V7 i used the GPO deployment with the transform file, it worked perfectly.
Now i started downloading V9 MSI and wanted to use Orca to create the MST file.
As for V7, i'm using your Knowledge Base and have already made the changes in "Feature" and now in "Property".
One thing is missing: In the KB you refer to "KEY_REG" for the license key (UNC path or string, in V7 i used the String).
I see "MsiHiddenProperties" with KEY;ORGANIZE,...... and "SecureCustomProperties" with KEYDATA;KEYFILE;.....
Do i have to write the String (or UNC Path) in one of those?
Many thanks in advance
Kind regards
Michael
PS: Maybe the "Knowledge Base" page should be adjusted regarding MSI. It not only contains the old version of "KEY_REG" but also "EDITOR_LANGUAGE" with "de-DE" instead of the new variant "ProductLanguage" with code (list of codes of supported languages would be really nice)
I plan to upgrade all our machines from V7 to V9.
For V7 i used the GPO deployment with the transform file, it worked perfectly.
Now i started downloading V9 MSI and wanted to use Orca to create the MST file.
As for V7, i'm using your Knowledge Base and have already made the changes in "Feature" and now in "Property".
One thing is missing: In the KB you refer to "KEY_REG" for the license key (UNC path or string, in V7 i used the String).
I see "MsiHiddenProperties" with KEY;ORGANIZE,...... and "SecureCustomProperties" with KEYDATA;KEYFILE;.....
Do i have to write the String (or UNC Path) in one of those?
Many thanks in advance
Kind regards
Michael
PS: Maybe the "Knowledge Base" page should be adjusted regarding MSI. It not only contains the old version of "KEY_REG" but also "EDITOR_LANGUAGE" with "de-DE" instead of the new variant "ProductLanguage" with code (list of codes of supported languages would be really nice)