Novell ZENWORKS 10 CONFIGURATION MANAGEMENT SP3 - COMMAND LINE UTILITIES REFERENCE 10.3 30-03-2010, Справочное руководство

Страница: 23 / 200

License Compliance Concepts 23
no
vd
ocx
(e
n)
7 Ja
nua
ry 201
0
1.4 License Data
As explained in Section 1.1, “License Compliance Components,” on page 15 , the number of
purchased licenses is one of the three primary pieces of information that is required to determine the
product’s license compliance. You license data can come from two different sources:
Š
Catalog Products and Purchase Records: A catalog product identifies a software product for
which you have purchased licenses. When added to an entitlement, a catalog product’s licenses
become available for consumption by the entitlement’s installations.
A catalog product’s licenses come from purchase records for the software product. If multiple
purchase records include license purchases for the software product, all licenses are rolled up to
the catalog product.
Using catalog products and purchase records as the data source for your purchased licenses is
the recommended method. Each time you add a purchase record for the software product, the
catalog product’s available license quantity is automatically increased by the number of new
licenses.
Š Purchase Summary Records: A purchase summary record lets you directly enter a license
quantity on an entitlement. The summary record includes the product’s description, cost, and
license quantity. The disadvantage to using a purchase record summary is that it doesn’t enable
you to track the product licenses through a catalog product and a purchase record.
An entitlement can use one or both sources for its available licenses.
1.5 Suites and Software Collections
In addition to standalone products, Asset Management can maintain license compliance for suite
products such as Microsoft* Office and OpenOffice.org*. Suites are included as discovered products
in the ZENworks Knowledgebase. A suite discovered product includes information about the suite
members.
When an Inventory scan discovers a suite installed on a device (for example, through the registry
settings), the installation is counted toward the suite’s installation total rather than the suite
members’ installation totals. For example, if Microsoft Word, Microsoft Excel*, and Microsoft
PowerPoint* are installed as a Microsoft Office suite on a device, the installation is applied to the
Microsoft Office discovered product and not the Word, Excel, and PowerPoint discovered products.
However, if these applications are discovered as standalone products (no Microsoft Office
installation), the installation is applied to each individual discovered products.
Software collections are administrator-defined suites. You can use them to account for suites that are
not included in the ZENworks Knowledgebase. With a software collection, you define the member
products and specify which member products must be installed on a device to qualify as a software
collection installation. If all required member products are installed on a device, the installation
counts towards the software collection. If some required member products are missing, the member
product installations count towards the individual discovered products.
1.6 Version Upgrades
A typical license agreement for a software version upgrade stipulates that you replace installations
of the base product with the upgrade product. In other words, the license entitlement (usage,
quantity, and so forth) is transferred from the base product to the upgrade product.