pellucHi,
We are currently evaluating LimeLM and have a few questions. First of all, we are using ClickOnce to deploy our application client-side. That means that the software will be installed independently on multiple user account. We wanted to known if its possible to activate a key by user account and not for the whole computer.
We tried calling the wizard with the userlevel argument, but it didnt work, neither did calling the TurboActivate dll with the methodCheckAndSavePKey with the flag TA_USER. I guess we are misunderstanding the concept of user level activation. Is what we are trying to achieve possible on LimeLM?
We also tried to change the generated key folder but if the customer copy the files to users folder on the same computer, the application is registred without enter the key.
Also, we were wondering where on the computer the license is saved. We looked for it in the system registry but could not find it
TurboActivate locks your software to individual computers. The only difference between TA_USER and TA_SYSTEM is where the activation data is saved. In both cases the product key (and your software) is being locked to the fingerprint of the machine (not to the user).
If you want to do per-user licensing, then you'll want to use TurboFloat.
Tell me if that helps.
pellucI try to test TurboFloat but my license insn't for TurboFloat. How I can test it ?
Forget itI found
pellucIt work but I don't want to need to install TurboFloat on customer computer. To bad because I thing your service is prety good.
Thank you I'll continue my search to find other online activation service.
Hardware-locked licensing, by definition, locks to the hardware. This means you're not going to find a properly designed online activation solution that lets you lock to individual users. That's what floating licensing is for.
So, your options are:
1. Use online activation (a.k.a. hardware-locked licensing) and you can limit the individual machines that customers can install & run your software on. (In our case use TurboActivate).
Or:
2. Use floating licensing and you can limit the individual user sessions on the same machine or separate machines that customers can install & run your software on. (In our case use TurboFloat).
Also, if you're using TurboFloat, and you don't want the customer to worry about the server, you can just automate the installation on their PC (just install it when you're installing your app). The customer never has to worry about it.
Does that make sense?
