kajJust tried activating TurboFloat Server on an old physical machine running Windows Server 2003, but got the error: "Can't activate within a virtual machine or a hypervisor".
Was the error because of the old version of Windows?
Are you using the latest version of TurboActivate? If not, start by doing that.
Next, only after updating to the latest version of TurboActivate / TurboFloatServer, make sure you're not actually on a VM. For example, having Hyper-V enabled will make your machine a VM (even the "host" is a vm inside Hyper-V because of the way it works).
kajThis is the TurboFloatServer.exe program downloaded within the last couple of weeks.
I will check the Hyper-V situation
kajHyper V is not the issue on this machine -I don't think that option was around in 2003.
We were accessing the machine using terminal services - that wouldn't cause TurboFloatServer to think it was on a virtual machine, would it?
This might be a case of false-positive VM detection that has since been fixed and will be released with TurboActivate 4.0. In the meantime you can just set that product key to allow VM activations. Then, when we release TA & TFS 4.0 you can release it to your customers and disabled activations on VMs.
We were accessing the machine using terminal services - that wouldn't cause TurboFloatServer to think it was on a virtual machine, would it?
No, it wouldn't.
kajWyatt wrote:> This might be a case of false-positive VM detection that has since been fixed and> will be released with TurboActivate 4.0. In the meantime you can just set that product> key to allow VM activations. Then, when we release TA & TFS 4.0 you can release> it to your customers and disabled activations on VMs.
That's fine it that is the case. Do you have a utility that we could run now to confirm that diagnosis?
Do you have a utility that we could run now to confirm that diagnosis?
No. You'll have to wait for TFS 4.0.
