behaviour of TurboActivate restoring image from another machineAnswered

My clients often use a common image to reset machines that return from hire and would like to have an activated version of my app ready to go when restoring this common image to a similar but different machine. Obviously the fingerprints will not match, but lets assume the machine has a valid activation under the same product key.

What is the behaviour of TurboActivate in this instance - will it look for a valid activation matching the machine's fingerprint or will it fail?

If it fails, what is the best practice in code for reasserting the existing activation for this machine?

Thanks,

Dave

, edited
Answer

It will fail, but then when they reactivate it will match to the one already on the servers.