Yes, create a new version in LimeLM. Include that TurboActivate.dat file in your app and use the new version GUID. Trials will be new. As will all product keys.
New major version : resetting trial for all users
Hello,
We're about to release a new major version of our product : V2 to V3.We'd like to reset the trials for all the users : so all users, even those that previously uses the trial for V2, can still have a trial for V3.
Is it possible with LimeLM ? Without an extension ?
Thank you. Philippe
Hello Wyatt,
Thank you for the reply.However, from what I understand, all product keys are lost in the process : I can reimport them but I cannot preserve the activations (each of my customers would have to re-enter its keys to reactivate our product). Am I right ?
My use case is only about resetting the trial for all users, while preserving the license keys/activations for all my customers.Do you confirm it's not possible ?
Best. Philippe
Well, the keys are not lost, you just can't use the old version keys in the new version of your app. You'll have to send new keys to the customers if you want to give them free upgrades to your new version.
So, yes, it's a tradeoff. If you want to have previous potential customers start a new trial (and you want existing paying customers to use the new version using the same key) then the option is to use trial extensions. Namely, a potential customer that used a previous version will have to contact you for a trial extension and you send it to them.
Hello,
I found a solution. The principle is simple : using a 1-day verified-trial-extension to "mark" if an user needs its trial to be resetted. - If this extension can be used, the user is running the new version of the product for the first time : so the trial can be resetted- If the extension already have been used, nothing to do.
This extension acts as a lifetime "marker".It both covers the case of old users (wanting to try the new features of the new version) and new users (that should only have one trial, not 2).Of course, you can use some user-preferences to avoid checking if the extension was already used, at every start of your product.
I hope it would help someone.Best. Philippe