I’ve given the thread a good read and tried the formatting that you suggested and it didn’t seemed to work for me.
I might suspect it’s an issue for the installer itself.
I’ve noticed that in a past installation script of the application, the /v was inside of the quotes but it did seem to work correctly.
The original version we installed is 32-bit but the newest version is 64-bit.
I got to note furthermore that there was an auto-updater available for the software but one of my colleagues was getting a particular error when upgrading.
It was something like:
The file is not marked for installation.
Again, the provided instruction on their website only assumes doing it thru CMD. I might just try opening up a CMD in PSADT and installing it that way…
I gotta contact their support team before I decide doing so because this is just a big mess.
First verify if the install command works from a basic CMD prompt.
Also, Installshield exes that take those switches rather than /f1 /f2 are MSI wrappers. You could extract that MSI and install it with a transform to set the license as an alternative solution.