VMs and network installs

I'm looking at your product and services to add activation to our software products. I have a couple of scenario that I would appreciate help with.

First if our program is installed/authorized on an single vm image on a single server but multiple copies of the VM with the authorized program are made, what would be a suggested LimeLM configuration to enable the program on the additional copies to check for the existing authorized install so a buy more licenses prompt could be displayed?

Second, our policy limits a network install to a single server with multiple workstations. The server portion is the application directory on a network share. No other server services are used. All processing is done on installed workstations. What would a suggested configuration to authorize the first network application directory and attached workstations but prevent authorization of copies of the original directory and workstation installs to it?

I hope this make sense. I appreciate your help and look forward to hearing from you. Thank you.

First if our program is installed/authorized on an single vm image on a single server but multiple copies of the VM with the authorized program are made, what would be a suggested LimeLM configuration to enable the program on the additional copies to check for the existing authorized install so a buy more licenses prompt could be displayed?

In this case, where you app is running on VMs (cloned or not), you should use TurboFloat (our floating license product that's a part of LimeLM). The way this works is you integrate the TurboFloat library into your application. And when your app runs it will request a license lease from the TurboFloat Server that is installed somewhere on the customer's network.

You can set how large the "license lease pool" is. Meaning you can specify just how many instances of your app can run at a time.

What would a suggested configuration to authorize the first network application directory and attached workstations but prevent authorization of copies of the original directory and workstation installs to it?

For that part of your application you'd use TurboActivate (our node-locked a.k.a. hardware-locked licensing part of LimeLM). This way you could generate a single key with 1 allowed activation and they could only use that application on that server they install it on.

Does that make sense?

Reply
Discard post