TurboFloat Server serving leases after revoked license

I'm testing the TurboFloat Server and I revoked the license to test. Then I stopped the service and restarted. License Server still serving leases... I then ran the commandline with -a switch and get the revoked message but when the service restart the TurboFloat Server is still serving licenses. If I stop the service then the correct error is displayed. Everything is on windows 10, localhost.

There should be a way to programmatically have the server poll if there is a license change and not in the config XML file. I think that the config XML file would give the customer up to 90 days and 14 days of invalid licensing which trying to prevent as well. The Config XML should be polled on the license website and not deployed in my opinion.

Looks like it took a period of a number of hours to revoke the license. What is the minimum pooling time? I think I set 1 in the config file?

>> " I then ran the commandline with -a switch and get the revoked message but when the service restart the TurboFloat Server is still serving licenses."

This is fixed in 4.0, out soon.

Right now the config file, specifically the IsGenuine node, specifies when the server should recheck with the activation servers.

>> "The Config XML should be polled on the license website and not deployed in my opinion."

We might make that change in the future.

Reply
Discard post