Virtual Machine Activation - Additional RisksSolved

Hello Everyone,We're shipping an increasingly popular software with TurboActivate, and we keep running into problems with Windows customers running a virtual machine knowing. The volume of support tickets is increasing and some customers also have good reasons to use a VM or are not technically proficient to follow the steps to disable whatever is creating the VM. We now usually resort quickly to just allowing VM activation for the specific customer's key. Now as it tends to come up more often and we're striking our first international reseller deals, we're thinking about allowing VM activations at the version level.

Due to our specific customer segment we are not all too worried about the occasional customer maliciously using more installations by cloning a VM, as long as it is not a comfortable method to share the installation at a larger scale. As our product is only useful in combination with a variety of other specialized software, that kind of setup would probably be way to fragile to cause us real economical harm. By the nature of our product people also will only use it on physical machines they operate themselves, so the Cloud concerns mentioned in the FAQ doesn't really apply.

We are however worried about any unforseen consequences from allowing VM activations by default. Does it open any additional doors to circumvent the protection? I know that any software will be cracked given time and motivation, but we'd rather not lower the bar of entry, and hopefully have a couple more good months without being cracked.Is there anything else we need to consider when we make this decision?

Thanks,Steve