You should use the TA_SYSTEM flag (instead of TA_USER) for CheckAndSavePKey(), this way the activations will be system-wide instead of per-user.
Does that make sense?
Our client encoutered an issue regarding using our program with different windows account. He first use Active Directory to install our product on five machines using administrator account, but when he use our program using other accounts, the license is not considered activated. What's the solution? He specifically asked where is the license file is located, so he can move the license file manually.
You should use the TA_SYSTEM flag (instead of TA_USER) for CheckAndSavePKey(), this way the activations will be system-wide instead of per-user.
Does that make sense?
You should use the TA_SYSTEM flag (instead of TA_USER) for CheckAndSavePKey(), this way the activations will be system-wide instead of per-user.
Does that make sense?
I'm using the C# version. Don't know how to do this in C#? Do you have a C# story?
If you're using the latest TurboActivate (which is 3.2.1 when I'm writing this) then the default behavior of the TurboActivate wizard is to activate on the system level. If you're making your own activation form in C#, then when using CheckAndSavePKey() you need to pass in the "TA_SYSTEM" flag:
bool isValid = TurboActivate.CheckAndSavePKey("ABCD-EFGH-IJKL-MNOP-.....", TurboActivate.TA_Flags.TA_SYSTEM);
Thx for your help. We'll try it immediately.