Best practices for managing limited client licenses/login

Posted by MicSim on Stack Overflow See other posts from Stack Overflow or by MicSim
Published on 2010-04-20T08:37:28Z Indexed on 2010/04/20 8:43 UTC
Read the original article Hit count: 410

I have a multi-user software solution (containing different applications, i.e. EXEs) that should allow only a limited number of concurrent users. It's designed to run in an intranet. I dont have a really good, satisfactory solution to the problem of counting the client licenses yet. The key requirements are:

  • Multiple instances (starts) of the same application (= process) should count as only one client licence
  • Starting different applications of the software solution should also count as only one (the same) client licence
  • Application crash should not lead to orphaned used licences
  • The above should work also for Terminal Server environments (all clients same IP, but different install folders)

I'm looking for estabilished patterns, solutions, tips for managing used client licenses. Specific hints for the above sitaution are also welcome.

© Stack Overflow or respective owner

Related posts about licensing

Related posts about best-practices