Hey Alexandre,
So I was wondering if it was possible to "lock" on given TS screens?
This is a very good question. We do plan to add this and make this dead simple "out of the box". Right now, the best way to handle customers who use Terminal Services (or one of the many competitors) is like this:
- Detect if they're running under TS.
- If so, use IPC (inter-process communication) to "talk" to the other instances on the computer and see under how many different "sessions" your app is running.
- Limit the number of TS sessions based on a number (you can use license fields for this)
An alternative is to just do step 1 (detect the TS) then if they are using TS force them to connect to a floating license server (TurboFloat).
2 - Also, the company who hosts the TS does so in a virtual machine and his big servers have many VMs for many different customers. Would an eventual "floating licence" server solve this issue?
Yes. We're releasing TurboFloat soon (we have a number of customers waiting for it). You can already detect and disallow activations on Virtual Machines, and when we release TurboFloat you'll be able to force customers on VMs to connect to a TurboFloat server running on their local network. This means you'll be able to get paid for every copy of your software.
We have an article that covers part of this topic: Licensing from inside a virtual machine or hypervisor. Right now the article just talks about blocking VMs from activation. When we release TurboFloat the article will be expanded on how to use this VM activation block in tandem with TurboFloat to get paid for customers running on VMs.
