Rule (for license keys)

FlexNet Manager Suite 2022 R2 (On-Premises)

This rule identifies the way that the application publisher issues license keys, and controls where and how you may record the license key for an individual installation (or user, depending on license type). A license key may be issued in any of these ways:

• For a single installation
• For a single purchase (covering all the installations authorized by that purchase)
• For a single application (covering multiple installations of that application)
• For a single license (covering all installations authorized under that license).

Tip: Tracking license keys is an administrative convenience that helps you comply with the requirements of your license. However, it does not have any effect on license consumption calculations. If your goal is to bind a particular installation or user to exactly this license, use individual allocations, available on the Consumption tab.

To change the license key rule, in the Identification tab of the license properties:

1. Scroll down to the License keys section, and click Change.
2. In the Change license key rule dialog that appears, select a new value from the License key rule drop-down list:
   • No keys prevents the use of license keys for this license.
   • One (multi-install) key per application allows you to link the key to an application listed in the Applications tab of these license properties.
   • One (multi-install) key per installation means you may link the key to the authorized installations in the Consumption tab of these license properties.
   • One (multi-install) key per license means that you link the key to this license on this Identification tab, using the field that appears when you save this rule setting.
   • One (single-install) key per installation again directs you to the Consumption tab of these license properties, where you must assign a unique key to each installation record.
3. Click Save to close the Change license key rule dialog.
4. If your choice was for one key for the entire license, record the value of the key in the License key field that appears below the Rule value.
5. Remember to click Save to store your changed license properties in the compliance database.

Not available for CAL Legacy, Concurrent User, Core Points, Evaluation, Microsoft Device CAL, Microsoft Server Processor, Microsoft User CAL, SAP Named User, SAP Package, SaaS User, Tiered Device, or any Oracle licenses.

For more information, see:

• Managing License Keys
• Assigning One Multi-Install Key to a License.