RobinPHi, Am I correct in that activating with TA_USER does not prevent a second user from activating on the same machine with the same key? That is, activating all users separately with TA_USER (but same key) has the same effect as TA_SYSTEM.This sounds ok because I believe the intention is to lock the licence to a computer rather than a user. However I have just come across the possibility of a multiseat setup, e.g. using Softxpand (http://www.miniframe.com/). Does this mean more than one user can run the software at the same time if they are both logged in to the same machine? Does LimeLM do anything to detect/prevent this?Regards,Robin
This type of software (multiple sessions on the same computer) has existed for decades. The most popular one is built right into Windows: Terminal Services a.k.a. Remote Desktop Services.
The way to charge users for individual sessions is to use TurboFloat where you can control how many instances of your app can run at a time in individual sessions. See: http://wyday.com/limelm/help/using-turbofloat/
Does that make sense?
RobinP>The way to charge users for individual sessions is to use TurboFloatYou mean for example have a local float server with just one activation. We did think of doing this but don't really want to force it on all our users. I guess we have to put this down as being a possible way for more than one user to access our software, but unlikely.Thanks,Robin
Yes, you can detect if the customer is using Terminal Services (or one of the many knockoffs), and if so not allow them to use your app unless they're using floating licensing.
