Voted Best Answer

Feb 10, 2016 - 03:45 AM
Do you have the same question? Follow this Question
Feb 10, 2016 - 03:45 AM
Feb 08, 2016 - 10:00 PM
Feb 09, 2016 - 01:25 AM
Feb 10, 2016 - 09:03 PM
Feb 10, 2016 - 09:33 PM
Feb 29, 2016 - 09:19 AM
Hi there.
I agree with previous answers but not so much with your point of view. At least I don't understand it.
If your license is being distributed by a license server (e.g. Flexnet) only users having such license can use the installed SW. Any other one will be refused.
So here there isn't any compliance issue, you can have 100 installations and only 20 concurrent licenses.
If the issue is that the user can redirect license request to a cracked or, let say, uncontrolled license key, then of course it is a fraud, but at that point such user will not appear in your server log and only a network scanning with an agent will find this installation, or?
Your problem here is to avoid such cases maintaining both a "closed" environment where users can't install their SW or change configurations, and a scanning system to have up-to-date reports on installations. (plus removal processes and punishment I must say...)
The above is pointing to your Autodesk example, but of course any SW has it EULA or SLA chapter in the purchasing contract and the incompliance is only based on that clauses.
If nothing is said, the vendor has to explain how they determine incompliance based on contractual terms (not just a script output).
Of course all will depend on who has more negotiation power because both parties can argue on legal tricks, but from a technical/process point of view it is not really otehrwise manageable.
So, when others were asking you for more details wasn’t to know your business but because any vendor has its own way to define compliance and two similar cases can have completely different output.
I wish you will succeed in your audit!
Feb 29, 2016 - 05:38 PM
Mar 01, 2016 - 09:21 AM