SPSS 17.0
Hi,
I am working on packaging SPSS 17.0 and using SMS for deployment. The problem is with the licensing. The vendor has provided me with the Authcode to be used as a public property. There is a custom action in the vendor msi which uses the property to activate the license. It works when installed manually on a machine. When deployed by SMS to the user's machines, the license doesn't get activated. We have to activate it manually by running the Licenseactivator.exe in the command line with the Authcode for each user. And the user needs to have admin privelges to run this command, which is not possible.
Has anybody packaged SPSS 17.0 and have solved this issue ? Please let me know the solution.
Regards,
manju
I am working on packaging SPSS 17.0 and using SMS for deployment. The problem is with the licensing. The vendor has provided me with the Authcode to be used as a public property. There is a custom action in the vendor msi which uses the property to activate the license. It works when installed manually on a machine. When deployed by SMS to the user's machines, the license doesn't get activated. We have to activate it manually by running the Licenseactivator.exe in the command line with the Authcode for each user. And the user needs to have admin privelges to run this command, which is not possible.
Has anybody packaged SPSS 17.0 and have solved this issue ? Please let me know the solution.
Regards,
manju
0 Comments
[ + ] Show comments
Answers (9)
Please log in to answer
Posted by:
jimmyx
15 years ago
Hmmmm the joys of SPSS!
I haven't deployed v17 as yet.
For versions 14 and 16 we use Sentinel License Administrator on a server It is fairly straightforward to setup.
Can you use this in your environmnet?
Regards
Jimmy
I haven't deployed v17 as yet.
For versions 14 and 16 we use Sentinel License Administrator on a server It is fairly straightforward to setup.
Can you use this in your environmnet?
Regards
Jimmy
Posted by:
mailmanju
14 years ago
Unfortunately, we cannot use Sentinel License Administrator on a server. We do not have any control on the infrastructure used in the organization.
Posted by:
mailmanju
14 years ago
Posted by:
jmcfadyen
14 years ago
*smirk*
yes that is correct however the issue is there is an action in your user interface that is causing the installation to successfully complete.
by running /qb /qr tell it not to run portions of those UI tables.
you could track the item that is running in the UI and move it to InstallExec tables which should fix the problem.
yes that is correct however the issue is there is an action in your user interface that is causing the installation to successfully complete.
by running /qb /qr tell it not to run portions of those UI tables.
you could track the item that is running in the UI and move it to InstallExec tables which should fix the problem.
Posted by:
mailmanju
14 years ago
Atlast found the solution. There is an unique feature in Windows XP and Vista, where in, if you rename the executable as setup.exe or make 'setup' as part of the name of the exe, it would elevate itself to run as admin even in restricted user profiles. In this case, we renamed LicenseActivator.exe as setup.exe and when executed in User, it would activate the license. We can run the executable either during startup or run it manually in a batch file, before launching the main shortcut.
Regards,
manju
Regards,
manju
Posted by:
Inabus
14 years ago
Or you could of done it the proper way, used procmon to find the files or reg keys which are written during the license activation process and then opened them up with secedit or setacl ;)
P
P
Posted by:
mailmanju
14 years ago
Inabus, I had tried using procmon, filemon and regmon. Didn't find anything at all. It actually creates a license file in the INSTALLDIR, but even after giving modify permissions to users for the INSTALLDIR, it wouldn't activate the license, as SPSS works in a complicated way in licensing.
Posted by:
anonymous_9363
14 years ago
SPSS works in a complicated way in licensing.Clearly, since it apparently uses neither the file system or the registry to record the license information. Perhaps it just magically remembers...
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.