This article discusses how to use FlexNet Manager Suite to manage subscription licenses prior to the 2016 R1 release.
We're having issues using Subscription licenses in FNMS. We upload the PO's as software for the 1st yr. of Creative Cloud contract, then software maintenance for the "true up" years. WE had to do this so that FNMS wouldn't count our licenses 3 times(one for each year we are invoiced for product). We then linked them to Licenses with the Duration field set to subscription. However, when the subscription does expire, nothing really happens - the licenses still show as Active and applications are still consuming them. This is a lot of manual effort and it seems like there must be a better way to manage subscription licenses. If we should be doing it differently, please let us know, or confirm that this is the way we should be handling them?
Unfortunately, there is no other way to handle subscription licenses. However, this license type has been added in 2016 R1.
Prior to 2016 R1 you will need to upload the PO's as software for the 1st yr. of the application's contract, then software maintenance for the "true up" years. This needs to be done so that FNMS wouldn't count the licenses multiple times(one for each year that you will be invoiced for the product). You will then need to link them to a license with the duration field set to subscription. However, when the subscription does expire, the licenses will still show as active and applications will still consume them.