But its still not clear.Īcrobat perpetual licenses are based on a per-device metric, rather than per user.
Adobe acrobat dc pro 2015 license key software#
I would interpret it as we are covered, as all "desktop machines that connect and access the software on the server" have a valid license. It all comes down to this interpretation or question which isn't specified.
That laptop then connects via VPN to our network, so it is a part of our network. If we have 150 licenses for our 150 users who use the software (perpetual not named), do we need to buy another 150 licenses for users to be able to access this on the RDP server? Their general EULA specifies that a license is valid for installation on an office machine and also a laptop or home machine. Customer does not need to purchase an additional Acrobat !license for the server.
Adobe acrobat dc pro 2015 license key install#
but still not clear:Īs discussed, here are the terms of use accepted when installing Acrobat 2015 on a desktop:Restrictions: You must not install the software: (c) as a component of a system or service that can be accessed by more than the licensed number of users The only tricky part I see is whether or not your users are accessing it only from the "Internal Network" or if they are outside.Īn update, handy for anyone in future who is looking for this info as I couldnt find this anywhere. Customer must purchase a license for each Network User that may have access to the Software.Ģ.1.7.2 For clarification and without limitation, Customer must not install or access (either directly or through commands, data, or instructions) the Software: (a) from or to a Computer not part of Customer’s Internal Network (b) for enabling web hosted workgroups or web hosted services available to the public (c) by any individual or entity to use, download, copy, or otherwise benefit from the functionality of the Software unless licensed to do so by Adobe (d) as a component of a system, workflow or service accessible by more than the Permitted Number of users or (e) for operations not initiated by an individual user (e.g., automated server processing). It really matters what license you are using as far as which EULA applies.īut, the Adobe Acrobat Pro 2017 EULA says the following (emphasis mine):Ģ.1.7.1 As permitted in a separate purchasing document or Documentation and subject to license restrictions stated in this agreement, Customer may install the Software on a Server only for the purpose of allowing an individual from a Compatible Computer within the same Internal Network (“Network User”) to access and use the Software. Get something comparable and probably save some money. If you can't get settled, kick Adobe to the curb and tell them to eat a 40 gallon bag of cocks. At the end of the day, you're compliant and if they try to do anything about it, the burden of proof is on them to prove that the perpetual licensing isn't good enough for users that are licensed and compliant, which they wouldn't be able to do. If you have to tell them you only have 70 users and leave it at that in order for them to get off your back, I would go that route. If there was nothing in either product's EULA that states that a specific license type is required for all users in the environment if there is a terminal server, then all that matters is that your users are licensed with an appropriate license for their use.Īll that is relevant is the 70 users. "Sorry, you need 150 licenses because we can't be certain that you have only 140 users".
That's like them questioning your user count in general. It doesn't matter that they can't monitor how many users are or aren't using the terminal server. If you have 70 users that need different licensing than you have, that's one thing, but your other 70 users are compliant. They cannot force you to purchase more licensing than you need under the EULA. If you have 140 users and all have perpetual licensing, they shouldn't even be contacting you regarding licensing unless they are auditing the user count itself. I'm curious to know why they suddenly are questioning your compliance.
0 kommentar(er)
