Shared image

A customer purchases a product key with 10 licences. He activates 1 licence and creates a system image which he then pushes out to the other 9 PCs. He then attempts to activate the further 9 licences on these cloned PCs.

How far will he get?

How does Turbo Activate behave when this happens?

Is there a way around this without using TurboFloat?

>> "How far will he get?"

He'll be able to activate on the first machine. TurboActivate is smart enough to block all the clones (because of our properitary fingerprinting algorithm). We talk about this extensively here: http://wyday.com/limelm/features/why/#competition

>> "How does Turbo Activate behave when this happens?"

It will say the cloned computers are not activated and give the customer a chance to buy more copies of your software.

>> "Is there a way around this without using TurboFloat?"

Yes. TurboActivate by default blocks this kind of behavior.

If instead of "hard drive cloning" (which I presume this question is talking about) you're talking about VM cloning, then the way to stop this behavior is to use TurboFloat. See: http://wyday.com/limelm/help/vm-hypervisor-licensing/

Yes I was talking about hard drive cloning as you say. I was hoping that that TurboActivate would see that the hardware had changed but then phone home to see if there were available licences to activate, or match against already activated hardware characteristics.

I will have to find another solution

Thanks

If we use a cloned drive and reinstall the software afterwards, then try to activate, will it see this as reactivation due to the hardware matching?

>> "Yes I was talking about hard drive cloning as you say. I was hoping that that TurboActivate would see that the hardware had changed but then phone home to see if there were available licences to activate,"

Well, the product key will still be on the cloned HDs, so the customer will be able to click "Activate" either in your app or in the TurboActivate Wizard without having to enter the product key again. However, whether they'll be able to activate or no with that product key depends on the number of allowed activations for the product key.

>> "If we use a cloned drive and reinstall the software afterwards, then try to activate, will it see this as reactivation due to the hardware matching?"

I'm not sure what you're asking. TurboActivate looks are all of the components of the computer. If you're talking about replacing a harddrive on the same computer, then TurboActivate's proprietary fingerprinting algorithm is smart enough to detect that the machine is the same.

If you're talking about moving that harddrive to a separate computer, then TurboActivate will see the computer as being different (because it will be different).

Does that make sense?

> Well, the product key will still be on the cloned HDs, so the customer will be able> to click "Activate" either in your app or in the TurboActivate Wizard without having> to enter the product key again. However, whether they'll be able to activate or> no with that product key depends on the number of allowed activations for the product> key.

Thanks for getting back to me.

Let's say there are activations available and the wizard successfully activates. If this process is repeated and a new cloned HD is installed on this laptop it will need activating again. When the activation takes place will it reuse the old activation or will it consume a new activation.

>> "Let's say there are activations available and the wizard successfully activates. If this process is repeated and a new cloned HD is installed on this laptop it will need activating again. When the activation takes place will it reuse the old activation or will it consume a new activation."

If a customer re-activates the same machine using the same product key, then LimeLM will let it use the same activation slot.