TurboFloat Server becomes deactivated when run on a VM (solution: don't use TFS on a VM)Answered
Hi!
My customer use Turbofloat server for a licensed product.
The activation of the license (TurboFloatServer.exe -a="XXXX-XXXX-XXXX-XXXX-XXXX-XXXX") is working.
The Product key is created with the option "Allow VM activations" (yes I know, it's not a good idea... but in my opinion it should not be related to this problem.)
The said customer has the following troubles:
1.
The license will not reactivate after 90 days.
Message: "This floating license server is activated, but it failed to verify the activation with the servers".
A subsequent new activation with a new Product key (or the same Product key after deactivation...) works seamlessly.
2.
The server is no longer activated after Windows update installation and subsequent reboot.
HW/SW Specification:
Windows - Hyper-V Farm, i.e. if a Hyper-V host reboots, patches or has a problem, the HyperV VM is migrated from one host to another host
OS: Windows Server 2012 R2
RAM: 4 GB
CPU: 4 Cores mit 2,2 Ghz
no direct internet access but only via proxy (proxy.gsi.de Port 3128)
Windows updates are managed via internal WSUS
Proxy server is set and working.
Turbofloat Version 4.4.4.0
Best regards
Vlado
modulCAD s.r.o
Windows - Hyper-V Farm, i.e. if a Hyper-V host reboots, patches or has a problem, the HyperV VM is migrated from one host to another host
We have a whole article that talks explicitly about this. Licensing from inside a virtual machine or hypervisor. From the article:
Another reason why you should disallow VM activations is that on certain "cloud VM providers" like Azure and Amazon Web Services, whenever you reboot the machine the VM instance is started on a different underlying physical machine, and thus the "computer fingerprint" changes. This means that a customer that is activated on one of these machines, reboots the machine, they suddenly become deactivated.
Short answer: don't allow TFS to be activated in a VM. We put a big red warning there for a reason.