A few more questions on activation

- given basic plan that allows 1200 activations, is it counted per license or per event? if one user activates one software, deactivate it right away, and reactivate it again, will it be counted as 2 activations? what if the user activates the software, deactivate it, then install it on 2nd PC, activate it again, will it be counted as 2 activations?

Both of those cases only 1 activation is used. Basically, an "activation" is an "allocated activation". So, you create a product key with 1 "allowed activation" then means only 1 computer fingerprint can be tied to that 1 product key at a time.

So, the basic plan allows for 1200 allocated activation.

Does that make sense?

- or if monthly plan is based on activation per license, say basic plan, does it mean when I manage to sell 1200 copies, I have to stick with basic plan and above to make sure these 1200 license can be validated?

Yes. Our pricing model is designed so that small startups can afford high quality licensing, and let them grow into the actual costs of LimeLM.

- given one activation, which can be expired by using custom field. If I update the expiry date to "renew" it, is it still counded as one activation?

Yes, it doesn't "use it" any new activations.

- when a license is activated on PC A, without deactivating it, then user tries to activate it again on PC B, what's going to happen?

The user on PC B will get an error message something to the effect that the product key has already been used.

Thanks Sam, you guys are very responsive to give people help. 😀

It's nice to know that your pricing is based on allocated license, which makes more sense. Since my software is almost subscription based, people may subscribe this month and opt it out next month. Consider this situation, on certain month, I have 100 new subscriptions, but another 100 persons opt it out, yet the total allocated licenses remains 1000, I assume it also fits into basic plan (allowing 1200 activations), correct?

" when a license is activated on PC A, without deactivating it, then user tries to activate it again on PC B, what's going to happen?"

Sam - "The user on PC B will get an error message something to the effect that the product key has already been used."

This could happen sometimes, when user's PC is crashed or replaced without a chance to deactivate it first, then the user won't be able to install the software and activate it on 2nd PC. I guess user has to contact me to clear the status before he can reactivate it on 2nd PC, is that the right way?

Thanks,w2xl

I assume it also fits into basic plan (allowing 1200 activations), correct?

Yes.

I guess user has to contact me to clear the status before he can reactivate it on 2nd PC, is that the right way?

Yes. You can just search for their product key, then either increase the number of allowed activation for the product key, or deactivate one of the old activations on the product key.

Thanks Sam. I will be integrating my code with limeLM. 😀

Hi Sam,

This is considered as a foffow up and a feature request if possible..

" when a license is activated on PC A, without deactivating it, then user tries to activate it again on PC B, what's going to happen?"

Sam - "The user on PC B will get an error message something to the effect that the product key has already been used."

Would it be nice to have a switch on backend LCP to control if the subsequent activation could automatically invalidtae previous activation and grant license to PC B?

The feature helps a lot of cases which you proposed float licensing seems overkill, and most likely all these case don't give a chance or won't be convenient for user to deactivate license first before he leaves.

i.e. User's PC is crashed, or replaced by IT dept.VM instances boot into different hardware in citrix, amazon EC2.User works in float/moble office setup, where he drops by to get any unused PC in the office.

I have plenty of cases to deal with the above.I can't afford to have them call me every time to clear their dead activation.

The only drawback seems like the software in PC A remains licensed until next check.

Another advantage of this solution is that user don't want give his license code to anyone else,Sonce it will deactivate his OWN license.

Would it be nice to have a switch on backend LCP to control if the subsequent activation could automatically invalidtae previous activation and grant license to PC B?

No, this is unworkable. It effectively neuters the hardware-locked licensing, removing all the benefits of it.

The only drawback seems like the software in PC A remains licensed until next check.

That's a huge drawback -- it effectively would turn our well designed hardware-locked licensing into serial-only licensing (which is effectively useless).

The solution to this problem is floating licensing. TurboFloat will be out soon. It will be easy to use (for you and your customers) and it will solve this problem.