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)
Question about V9 MSI/MST File
Moderators: PDF-XChange Support, Daniel - PDF-XChange, Chris - PDF-XChange, Sean - PDF-XChange, Vasyl - PDF-XChange, Stefan - PDF-XChange
-
Paul - PDF-XChange
- Site Admin
- Posts: 7410
- Joined: Wed Mar 25, 2009 10:37 pm
Re: Question about V9 MSI/MST File
Hi MrBurny
thanks for the report. May I ask which KB you are referring ot as the two I am familiar with that refer to Orca do not mention "KEY_REG". You said:
So definitely to use a transform to apply a key you need to create a new row in the "Property" table called KEYDATA and it must have the full string of the key as the value. Please make sure there are no line feed or carriage return characters in the key string yo paste into Orca. When you copy the key it usually has these characters so as to format the key visually. We strip this whitespace from the key when pasted into the GUI of the software but Microsoft (both Orca and InTune) do not. The entire key sting must be one line.
https://www.pdf-xchange.com/knowle ... r-products
I hope that helps!
thanks for the report. May I ask which KB you are referring ot as the two I am familiar with that refer to Orca do not mention "KEY_REG". You said:
But I am only familiar with using KEYDATA and the key as a string in Orca. (Works the same in Intune for that matter, KEYDATA="PXP80-udgdhfjfkf....hdhugjuy=")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).
So definitely to use a transform to apply a key you need to create a new row in the "Property" table called KEYDATA and it must have the full string of the key as the value. Please make sure there are no line feed or carriage return characters in the key string yo paste into Orca. When you copy the key it usually has these characters so as to format the key visually. We strip this whitespace from the key when pasted into the GUI of the software but Microsoft (both Orca and InTune) do not. The entire key sting must be one line.
https://www.pdf-xchange.com/knowle ... r-products
I hope that helps!
Best regards
Paul O'Rorke
PDF-XChange Support
http://www.pdf-xchange.com
Paul O'Rorke
PDF-XChange Support
http://www.pdf-xchange.com
-
stevenm
- User
- Posts: 1
- Joined: Fri Mar 22, 2024 6:06 am
Re: Question about V9 MSI/MST File
How does one do it with .exe file? I am trying to make Intune Package with version 8.
-
Paul - PDF-XChange
- Site Admin
- Posts: 7410
- Joined: Wed Mar 25, 2009 10:37 pm
Re: Question about V9 MSI/MST File
Hi, stevenm
the .exe installers are not really suitable for inTune. The .msi ones will work pretty much out of the box.
I do not see a license associated with the domain @slouchmr.com so I assume you are doing an unlicensed installation. That is fine, we encourage the use of the "Free" Editor, but you would be better off using the current version. May I ask why you are using version 8? There are many fixes and improvements since then.
the .exe installers are not really suitable for inTune. The .msi ones will work pretty much out of the box.
I do not see a license associated with the domain @slouchmr.com so I assume you are doing an unlicensed installation. That is fine, we encourage the use of the "Free" Editor, but you would be better off using the current version. May I ask why you are using version 8? There are many fixes and improvements since then.
Best regards
Paul O'Rorke
PDF-XChange Support
http://www.pdf-xchange.com
Paul O'Rorke
PDF-XChange Support
http://www.pdf-xchange.com
-
bts
- User
- Posts: 2
- Joined: Thu Dec 04, 2025 10:27 pm
Re: Question about V9 MSI/MST File
This is very helpful, and the KB article is almost exactly what I needed. One issue - the "Case" part mentions needing to add a license key and user details. However, the article only addresses adding the key portion and doesn't mention anything about user details.Paul - PDF-XChange wrote: ↑Wed Jan 27, 2021 12:24 am ...
So definitely to use a transform to apply a key you need to create a new row in the "Property" table called KEYDATA and it must have the full string of the key as the value. Please make sure there are no line feed or carriage return characters in the key string yo paste into Orca. When you copy the key it usually has these characters so as to format the key visually. We strip this whitespace from the key when pasted into the GUI of the software but Microsoft (both Orca and InTune) do not. The entire key sting must be one line.
https://www.pdf-xchange.com/knowledgeba ... r-products
I hope that helps!
What happens in the case where you pass a key, but nothing about a user - is there some default info that goes in there? Or how can we pass user info?
I'm trying to deploy this via Intune, which I'm still learning a bit.
-
Paul - PDF-XChange
- Site Admin
- Posts: 7410
- Joined: Wed Mar 25, 2009 10:37 pm
Re: Question about V9 MSI/MST File
Hi, bts
the user options are passed to MSIEXEC.EXE so all your users would get the same values in your deployment, so I doubt this is actually what you want.
If you have a hybrid AD/EntraID environment you can have the Editor pull user details from AD but EntraID alone will not do it.
If you pass noting, and no AD is involved it will simply use the user name from their device:
which they can type over with their own text:
Does that help?
the user options are passed to MSIEXEC.EXE so all your users would get the same values in your deployment, so I doubt this is actually what you want.
If you have a hybrid AD/EntraID environment you can have the Editor pull user details from AD but EntraID alone will not do it.
If you pass noting, and no AD is involved it will simply use the user name from their device:
which they can type over with their own text:
Does that help?
You do not have the required permissions to view the files attached to this post.
Best regards
Paul O'Rorke
PDF-XChange Support
http://www.pdf-xchange.com
Paul O'Rorke
PDF-XChange Support
http://www.pdf-xchange.com
-
bts
- User
- Posts: 2
- Joined: Thu Dec 04, 2025 10:27 pm
Re: Question about V9 MSI/MST File
Hi Paul,
Yes, this is helpful. We fully transitioned from AD to EntraID (AAD) a few years back, so no hybrid, but this should be acceptable.
Thanks,
Brian
Yes, this is helpful. We fully transitioned from AD to EntraID (AAD) a few years back, so no hybrid, but this should be acceptable.
Thanks,
Brian
-
Sean - PDF-XChange
- Site Admin
- Posts: 485
- Joined: Wed Sep 14, 2016 5:42 pm
Re: Question about V9 MSI/MST File
Sean Godley
Technical Writer
PDF-XChange Co LTD
Sales: +1 (250) 324-1621
Fax: +1 (250) 324-1623
Technical Writer
PDF-XChange Co LTD
Sales: +1 (250) 324-1621
Fax: +1 (250) 324-1623