ok, but these days how many corporate IT people have access to or want to run turbofloat server on a real machine. I have cases where users bought licenses, but their IT dept dont have a physical machine to run it. Ours users are stuck.
Currently, Turboactivate dont work on Azure/AWS/Cloud virtual machines without enabling VM, which is undesirable. Second on restart, the machine signature changes invalidating the license. But VMs on Azure/AWS/Google etc have a unique identifier
https://azure.microsoft.com/en-us/blog/accessing-and-using-azure-vm-unique-id/
If this unique id is part of the machine signature, then this can be made to work.
If this feature can be enabled, I would not be pining for licensechest.
We have no plans to use alternative proprietary ID methods for VM platforms. We can already accurately detect separate VMs. That doesn't change the nature of VMs.
Use TurboFloat on VMs for best results. Covered in many forum posts, and our help documentation.
ok, but these days how many corporate IT people have access to or want to run turbofloat server on a real machine. I have cases where users bought licenses, but their IT dept dont have a physical machine to run it. Ours users are stuck.
We're releasing hosted TFS soon. That will solve that use-case.
Yes, we know that for the past 3 years.