TurboFloat lease management

Is there a way to manage leases on the server remotely - the use case here is for a local admin to clear the leases so that an orphan computer isn't holding on to a license. Ideally, would be good to know the IP of the clients that are holding leases.

Also, we have the Plus account and it says we only have 5 float licenses. How many float licenses are available at the other tiers.

Thanks

>> "Also, we have the Plus account and it says we only have 5 float licenses. How many float licenses are available at the other tiers."

I don't know where you're reading that. The 5 users refers to 5 "admins" for your LimeLM account: http://wyday.com/limelm/signup/

>> "Is there a way to manage leases on the server remotely [...]"

No, not yet. It's coming. For now the recommendation is to keep sane lease-lengths (30-minutes is a good length): http://wyday.com/limelm/help/turbofloat-server/#config-lease

This way the maximum time a "zombie" lease could exists is 29 minutes and 59 seconds (that's presuming the app or machine crashes *immediately* after requesting the lease -- and thus never has time to "Drop" the lease)

And of course a customer can always start the app on the same computer to "revive" the zombie-lease, and then properly close the app.

Thanks, looking forward to the feature.

The use case we're trying to protect against is to prevent users who left the app running on their computer and went home or on vacation. In this case, we'd not be able to release the lease for others who need to use the software.

If the admin just restarted the floating license server, would all applications need to restart themselves?

>> "If the admin just restarted the floating license server, would all applications need to restart themselves?"

Nope. The apps can continue to run -- they'll request new leases.

Bump, our customers would also love the ability to manage leases from the license server, primarily to kill orphaned leases which haven't yet expired.

A TurboFloat Server Management interface and library is coming. We've put significant amounts of work into it already, but we're not quite there yet.