Deactivate

I now have my program running on 3 computers - I deactivted my license then installed my program on another computer then activated and did the same steps and added my program to another computer and all three are running. The computers that I had my program on and deactivated are still working with no issues....... Greg

Since no answer yet I wanted to post this also, I revoked a license and I still have full access. I am testing rightnow and wanted to get the answers so I know what to expect when I deactivate and revoke a license.

Looking forward to your reply

Greg

Hey Greg,

This is a good question. We actually cover this on the product key page right below the activations:

[attachment=0]deactivating.png[/attachment]

Short answer: if the user deactivated (by your app calling the TurboActivate.Deactivate() function) then the deactivation is immediate. If you deactivate remotely using the LimeLM interface, then the user is only deactivated once your app calls IsGenuine().

Does that make sense?

Wyatt thanks for the reply, Is this something that happens automatically Program calls IsGenuine() or is this something that we need to code how often program does this? I actually had another party code the LM for me so do I need them to revisit this and add a value to when to call IsGenuine().Greg

Is this the same for Revoke a product key? I also revoked a product key but still able to use the program? I just want to make sure I have this set up correctly, If I revoke a license I want to make sure the program shuts down and what is the best way to acheive this. This would be a worst case like someone doesn't pay or one of my clients laptop or computer is stolen. I think we should have the ability to shut down our program as quickly as possible.

Thanks Greg W.

I just want to make sure I have this set up correctly, If I revoke a license I want to make sure the program shuts down and what is the best way to acheive this.

You can't have immediate shutdown because your app won't be maintaining a constant connection with LimeLM.

Calling IsGenuine() deactivates any machine that was revoked / deactivated remotely (a.k.a. via the LimeLM interface).

That' why we recommend calling the IsGenuine() function every 90 days.

So, to answer your question, yes your programmers should call IsGenuine().

Ok, I understand so the program will continue to run even it is revoked or disabled until the IIsGenuine() is called. is sounds like every 15 to 30 days should be the recommendation instead of 90 days that's three months someone could be using the program loss of income...... Just my opinion

Greg W.

sounds like every 15 to 30 days should be the recommendation instead of 90 days that's three months someone could be using the program loss of income...... Just my opinion

Right, we recommend a long time length for 3 reasons:

1. So our customers don't call IsGenuine() on every startup. (Which is a terrible user experience for the end-customer, especially if they don't have good internet access -- which is most of the world, sadly).
2. You're rarely going to need to revoke product keys (you typically only need to if you get a cargeback on the customers credit card).
3. You're rarely going to need to deactivate individual activations. You only need to do this if a user's computer is stolen or destroyed, which we've found to be a rare case. Even if a customer lies to you about this they can only get 90 days for usage on 2 computers. After that they'll only be able to use it on 1 computer. If they continue to lie to you about this it will be easy to catch it.

So choosing the correct interval to call IsGenuine() is a trade off. We still recommend 90 days. But 30 days is also doable. If you call it too often you might make legitimate users mad (especially if they have crummy internet connections).