ISX_SERIALNUM ScanSoft Paperport 11.0 Wrapper
Hey Guys
Paperport comes with a ISScript10 and Vendor Supplied MSI. I have to create a Wrapper MSI for the same. The condition in which the Serial key is supposed to be provided to Wrapper should be in the Command line and not inside the MSI.
My requirement: There are three different Serial Key to be passed at three different instances in three different geographic locations. But, I am supposed to create ONE MSI.
I tried copying ISX_SERIALNUM property in the Vendor MSI and a new property in Wrapper MSI as SERIAL KEY=ISX_SERIALNUM.
But whenever I install, IS Script gets working after which it gives an error the "Invalid Serial Key"
Please help, how to pass serial key to Vendor MSI by launching Wrapper MSI.
Thanks
Satnix
Paperport comes with a ISScript10 and Vendor Supplied MSI. I have to create a Wrapper MSI for the same. The condition in which the Serial key is supposed to be provided to Wrapper should be in the Command line and not inside the MSI.
My requirement: There are three different Serial Key to be passed at three different instances in three different geographic locations. But, I am supposed to create ONE MSI.
I tried copying ISX_SERIALNUM property in the Vendor MSI and a new property in Wrapper MSI as SERIAL KEY=ISX_SERIALNUM.
But whenever I install, IS Script gets working after which it gives an error the "Invalid Serial Key"
Please help, how to pass serial key to Vendor MSI by launching Wrapper MSI.
Thanks
Satnix
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
michaelnowell
15 years ago
Firstly, why are you trying to wrap the ISScript and your Vendor MSI into one MSI? Why wouldn't you have the ISScript MSI separated so that you can use it with other installations that also require this. Or simply just install the ISScript on all of your workstations so that you no longer get presented with situtations like this.
By installing the ISScript separately you would then be able to just pass a transform against your vendor MSI instead of having to set a ISX_SERIALNUM property (within your wrapper) to pass into the vendor MSI.
As for having to pass different Serial Key's for different locations. You could run a custom action within the Transform that determine's the location of your PC (by IP address or default gateway) and then set the ISX_SERIALNUM property based on the result.
We have 3 different locations and we run a script (runs when the PC boots) which will detect the default gateway, sets a system environment variable and this variable is then queried during our installations.
Cheers, Mike
By installing the ISScript separately you would then be able to just pass a transform against your vendor MSI instead of having to set a ISX_SERIALNUM property (within your wrapper) to pass into the vendor MSI.
As for having to pass different Serial Key's for different locations. You could run a custom action within the Transform that determine's the location of your PC (by IP address or default gateway) and then set the ISX_SERIALNUM property based on the result.
We have 3 different locations and we run a script (runs when the PC boots) which will detect the default gateway, sets a system environment variable and this variable is then queried during our installations.
Cheers, Mike
Posted by:
anonymous_9363
15 years ago
Posted by:
satnix
15 years ago
Hey Mike,
Thanks, but I had a requirement to Wrap the two MSIs. Anyways, I found a solution by myself by writing a custom action for a VBScript to Run first ISSCRIPT.MSI and then call the second MAIN.MSI with a parameter passed in the command line i.e.
msiexec /i "Main.MSI" transforms="Main.mst" /qb ISX_NUMBER="xxx-xxxxx-xxxxx"
this command was run by the vbscript and the same can be used at the time of deployment for SMS.
:) Hope that solves problems for people who might face the same.
Thanks, but I had a requirement to Wrap the two MSIs. Anyways, I found a solution by myself by writing a custom action for a VBScript to Run first ISSCRIPT.MSI and then call the second MAIN.MSI with a parameter passed in the command line i.e.
msiexec /i "Main.MSI" transforms="Main.mst" /qb ISX_NUMBER="xxx-xxxxx-xxxxx"
this command was run by the vbscript and the same can be used at the time of deployment for SMS.
:) Hope that solves problems for people who might face the same.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.