Here's the link to the announcement: http://m3-page.info.adobe.com/nl/jsp/m.jsp?c=%40ynex7vTZ38NlZ8XkoKlpNXN91F1fSe7zJWZX0XlAGMo%3D You can also Google, "for adobe create cloud infringement" I do believe that action is required on Flexera's part to update the ARL. For example, if you look at the Adobe Systems Photoshop CC (2017) application in FNMS, you will see evidence to pull 18.1.% . According to the announcement, 18.1.17 is authorized but 18.1.6 is not. However, FNMS will recognized both of these to the Adobe Systems Photoshop CC (2017) application which, given what Adobe is saying, now needs to be broken out to two different applications. ... View more

Yes, this is a BIG issue and 100% should be a product enhancement. Not having this ability and not accounting for it manually, as you (and we) have done, leads to an overstatement of Adobe license position. For yearly subscriptions in large environments this can become very costly if you are not paying attention! Additionally, having to account for this manually, requires additional FTE operational time and oversight which o increases the total operational costs of FNMS. Given that the Adobe product use rights allow for organizations to do exactly what you stated, a commercial product like FNMS should support this ability out of the box. A BIG +1 for this enhancement request and I strongly encourage others to support this enhancement by adding to this thread. ... View more