Moving Maintenance Between Licenses
- The License and Maintenance Expiry page
- The All Licenses page.
- Choosing the quantities to move
- Choosing the destination license that received the quantity moved
- Deciding whether the source license or the destination license (or both) should allow the maintenance to expire.
- If your underlying License and Maintenance Expiry page is filtered for a future time window (visible just below the wizard as Expiring within the next), this shows the count of current maintenance coverage expiring within the chosen time window.
- If your underlying page is showing Overdue items, this maintenance coverage has already expired; but you may still move it to another license if required (so that you can, for example, correct you audit trail).
- If you selected a row in the License and Maintenance Expiry page, you have also identified the purchase that is the starting point for calculations.
- If you started from the All Licenses page, the calculations start with the purchase for which the Expiry date is closest to today.
The system then infers, for this license, a 'chain' of purchases that appear to renew the same maintenance over time, based on related quantities and dates. The chain goes no further back than a matching purchase for software with maintenance, or a software-only purchase within a day of a relevant maintenance purchase. If neither of these is found, the maintenance chain ends at the first related purchase of maintenance, and the system then finds the purchase of linked software (only) that is nearest to the start of the inferred chain of maintenance purchases. The resulting chain displays as the list of purchases initially shown in the wizard with a non-zero Transfer quantity.
To move maintenance (and possibly entitlements) from one license to another:
FlexNet Manager Suite (On-Premises)
2022 R1