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
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
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
Answered 04/28/2009 by: jimmyx
Purple Belt

Please log in to comment
0
try it with /qr instead of /qb
Answered 04/28/2009 by: jmcfadyen
Fifth Degree Black Belt

Please log in to comment
0
Unfortunately, we cannot use Sentinel License Administrator on a server. We do not have any control on the infrastructure used in the organization.
Answered 04/29/2009 by: mailmanju
Senior Yellow Belt

Please log in to comment
0
Jmcfadyen, no luck with /qr too. I guess I had expected it, as the switches doesn't do anything much in the package other than controlling the user interface during the installation. The problem we have currently has to be solved post installation of SPSS, by executing a batch file to run licenseactivator.exe file for each user with admin privileges.
Answered 04/29/2009 by: mailmanju
Senior Yellow Belt

Please log in to comment
0
*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.
Answered 04/29/2009 by: jmcfadyen
Fifth Degree Black Belt

Please log in to comment
0
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
Answered 05/06/2009 by: mailmanju
Senior Yellow Belt

Please log in to comment
0
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
Answered 05/06/2009 by: Inabus
Second Degree Green Belt

Please log in to comment
0
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.
Answered 05/06/2009 by: mailmanju
Senior Yellow Belt

Please log in to comment
0
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...
Answered 05/06/2009 by: VBScab
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity