FlexNet Manager Suite 2019 R2 (On-Premises Edition)
For
multi-product licenses (see
Multi-Product License), you can use the
Licensed products and upgrade/downgrade rights accordion to manage
products in a license, and to set upgrade and downgrade rights on each of the linked products.
For single-product licenses, the upgrade rights and downgrade rights accordions are available
separately (see
Upgrade Rights and
Downgrade Rights).
Tip: This accordion replaces the
Upgrade rights and Downgrade rights accordions
displayed for a single-product license.
Regardless of the number of applications linked to a license, you can configure the following
settings for each product through the Configure Product Use Rights
pop-up. See Configure Product Use Rights.
This section lists the following properties of the applications and products linked to this
license:
Control |
Details |
Application |
The application's name, which may be:
- Set by the Application Recognition Library (for applications with
Source: Flexera), and not editable
- Derived from the evidence values for Product,
Version, and Edition
properties (when generated by FlexNet Manager Suite), and editable to
suit your corporate standards.
You can edit this on the General tab of the application
properties when Local is displayed in the
Source column (which means the application was
added manually by an operator).
|
Edit use rights |
Enables you to configure product use rights on the products that are linked to this
license. For more information, see Configure Product Use Rights |
Edition |
The edition of an application. These editions, for example,
Lite or Pro, describe different levels or groupings
of functionality.
Visible on the General tab of the application properties.
It is editable only for applications with a Source value of
Local.
|
Primary |
This field displays the value Yes if
this is the primary product for a multi-product license.
A multi-product license covers a group of software products that are sold together
as a bundle under a single license. Different publishers structure their bundles in
different ways. For example:
- For IBM, a bundle usually focuses around one (or sometimes more than one)
primary product, to which the license mainly applies. Provided that
the primary product is installed, you are also permitted to install one or more
supplementary products at no additional cost. (Typically, the
supplementary products are co-installed on the same inventory device as the
primary product; but some licenses allow the supplementary products to be
installed on a separate device, still covered by the same license. Check license
terms carefully.)
- For other publishers, a bundle usually collects products as equals. For example,
the Microsoft Office 365 bundle includes Microsoft Office (in itself, a suite), Microsoft Azure Active Directory, Microsoft
Exchange, and so on. The bundle license permits use of any or all of these
products, in any combination, on any one inventory device. There is no concept
of primary and supplementary products here.
To cater for all kinds of bundles, multi-product licenses in FlexNet Manager Suite supports primary and supplementary products on a multi-product license. In the case,
like the Microsoft example above, of a 'bundle of equals', all the products on the
multi-product license can be primary (it is not required to have supplementary
products). The one multi-product license covers all the products, both primary and
supplementary (where these are differentiated). By default, multi-product licenses have
a higher priority for consumption than a single-product license attached to the same
application record. This means that having a single primary product installed can be
sufficient to link an inventory device to the multi-product license, and in the absence
of other factors like exemptions, to trigger consumption from this license in the next
reconciliation (for more details, see How Does License Consumption Order Work?).
|
Product |
Product names are supplied by the Application Recognition Library and are not
editable. New product names created within your enterprise are editable in the General tab of the application
properties.
|
Publisher |
The name of the publisher of this
software, responsible for its development and
distribution.
For application records that
you create manually, Publisher is
editable in the General tab of the application properties. For applications
supplied through the Application Recognition Library, the
Publisher field
is not editable.
|
Summary of use rights |
Outlines the use rights, including the upgrade and downgrade rights configured for
this product. To edit these rights, you may either:
- Click the hyperlinked summary
- Click the edit icon under the Edit use rights column.
|
Version |
The release number (or release identifier) of an application.
Visible in the Version field in General tab of the application properties.
Editable for applications with a Source value of
Local. For applications from the Application Recognition Library, it
is not editable.
|