Changing the Host or NIC on a Virtual Machine

Would either of the following changes to a VM cause the Floating Licence service to no longer recognise the VM as the machine on which it was installed;

- Changing the Host- Changing the NIC

If so, could you please specify which one would cause this please.

One of our Clients made the above changes to their VM on which a Floating Licence was installed on and it caused it no longer to be recognised. They state that the Host will often change during maintenance work on the VMs and so want to make sure that it was the latter that caused the issue.

Hey Stephen,

>> "Floating Licence service "

Are you talking about the TurboFloat Server? If so, don't install it on a VM or "sandbox" image of any kind. Install it on a real machine. Or, if your customer doesn't have access to a real machine we'll be offering hosted versions of the TurboFloat Server for a very low price (more competitve than VM instances hosted elsewhere) very soon.

The TurboFloat Library, on the other hand, *can* be run in VMs, sandboxes, and on real machines. It was designed to handle all of those things.

So, your app, using the TurboFloat Library can run perfectly fine anywhere and can handle changing VMs, cloned VMs, real machines, and every sort of weirdness a customer can throw out at you.

The TurboFloat Server, on the other hand, *must* be installed on a real machine. We're going to make this clearer in the LimeLM interface itself (giving you an explicit warning if you set a TFS key to allow activations on VMs).

Reply
Discard post