License Reservations

Important:You can use either reservations or named license pools. Reservations and named license pools cannot coexist alongside each other. For more information, see Named License Pools vs. Reservations.For general information about named license pools, see Allocating Licenses Using Named License Pools.

If currently no license reservations are defined for a license server, review the information in Comparison of Named License Pools and Reservations to decide which approach is best for you. In general, reservations are conceptually similar to named license pools, but named license pools offer significantly more flexibility in controlling your server’s license pool.

Important:Reservations can only be used if the policy setting licensing.allowDuplicateClients is set to false (the default).

The license reservation feature available with the FlexNet Embedded license server (the local license server or a CLS instance) enables you to control the distribution of the server’s license pool within your enterprise.

With no reservations defined, the license server distributes licenses on a first-come-first-served basis to client devices requesting them. However, with the use of reservations, the server pre-allocates specific license counts to certain client devices or users to help ensure that these entities have access to the licenses they need. As the license server administrator, you can choose to pre-allocate the entire pool of licenses, a portion of the licenses, or none of the licenses. Any license not reserved remains in the shared pool of licenses and is available to any device on a first-come-first-served basis.

The following sections provide background information about reservations on the FlexNet Embedded license server:

Overview of Reservation Types
Reservation Hierarchy
Managing Reservations
Disabled Reservations
License Allocation on the Server
Processing the Capability Request When Reservations Are Used
Reservation Limitations