TA_USER license

I set my license up with TA_USER, and while I'm able to get a different user to prompt for a key - the same key that I issued to a prior user is accepted. Here is the scenario:

Login as UserARun App - get trial license Get a key "KeyA" and set it up with 1 activationEnter key "KeyA" and activate product (product activated no problem)Logoff Verify the "KeyA" is activiated on wyday.com (key is activiated 1/1)

Login as UserBRun App - get trial license Enter key "KeyA" and activate product (product activated no problem)

I'm using current 3.3.4 release. Is there any way to prevent UserA and UserB from both using license "KeyA" with TurboActivate?

Thanks,Bill

Hey Bill,

The difference between TA_USER and TA_SYSTEM is only where the activation files are stored (user wide or system wide). In both cases TurboActivate uses hardware-locked licensing.

In other words, UserA and UserB will both be able to activate on that same computer because the "computer fingerprint" is the same (because it's the same computer). Now if the UserA and UserB are on 2 separate computers then everything will function as you expect.

Now, if you want to limit the number of instances of your app that can be run on a computer then you can do that with a floating license. TurboFloat (our floating license product) will be out soon and will accomplish that.

Does that help?

Yes - thank you - and we're keeping an eye on TurboFloat.

I have a follow-up question to this scenario - and this perhaps should be another subject but I'll post here.

After userA activates, my license on wyday.com shows 1/1 activations used. Is there any way to prevent userB from activating this already 'fully' activated license?

We are in the process of trying to chase this down. It seems to me that in a prior release this was the case, however after upgrading to 3.3.4 it allows the activation. I'm uncertain if something changed in the TurboActivate release or perhaps it is in my code.

Thanks again,i10

After userA activates, my license on wyday.com shows 1/1 activations used. Is there any way to prevent userB from activating this already 'fully' activated license?

No. LimeLM allows re-activations on the identical machine.

It seems to me that in a prior release this was the case,

No, it never was the case. LimeLM / TurboActivate has always allowed re-activation on the same computer.