![Novell ZENWORKS 10 CONFIGURATION MANAGEMENT SP3 - COMMAND LINE UTILITIES REFERENCE 10.3 30-03-2010 Reference Manual Download Page 111](http://html.mh-extra.com/html/novell/zenworks-10-configuration-management-sp3-command-line-utilities-reference-10-3-30-03-2010/zenworks-10-configuration-management-sp3-command-line-utilities-reference-10-3-30-03-2010_reference-manual_1711928111.webp)
License Allocation Concepts
12
111
no
vd
ocx
(e
n)
7 Ja
nua
ry 201
0
12
License Allocation Concepts
Allocating licenses to devices, departments, sites, and cost centers lets you track and maintain
license ownership within your organization.
The following sections introduce the concepts you should understand to effectively use Asset
Management to allocate licenses:
Section 12.1, “Allocation vs. Compliance,” on page 111
Section 12.2, “Device Allocations and Demographic Allocations,” on page 111
12.1 Allocation vs. Compliance
License allocation
is an accounting tool; it assigns licenses to devices, departments, sites, or cost
centers to track license distribution and ownership.
License compliance
is an evaluation tool; it
compares a product’s license quantities against its installation quantities to determine a compliance
status.
With the exception that both are based on licensed products, license allocation and license
compliance are independent of one another. Allocating licenses does not affect the number of
purchased licenses or installations for a product, and therefore does not affect the license compliance
status for the product.
For example, assume that DepartmentQ purchased 30 licenses of ProductA. However, DepartmentQ
has 35 installations of the product, which means that the license compliance status for ProductA is
undercompliant (too few licenses for the number of installations). You decide to allocate 35 licenses
to DepartmentQ, which you can do even though you only have 30 purchased licenses. The
compliance status remains undercompliant because the purchased licenses, not the allocated
licenses, are used when calculating compliance.
In some instances, license allocations might help you resolve compliance problems. For example,
you notice that Product A is undercompliant by four licenses. You check the license allocation
information for Product A and see that 14 licenses are allocated to DepartmentQ and 14 devices
associated with DepartmentQ have Product A installed. At the same time, you see that 12 licenses
are allocated to DepartmentZ but 16 devices associated with DepartmentZ have Product A installed.
You know that you need to work with DepartmentZ to resolve the compliance problem.
12.2 Device Allocations and Demographic
Allocations
You can allocate licenses to devices and to demographics (sites, departments, or cost centers).
A
device allocation
is the assignment of a license to a specific device. The device can have the
product installed or not installed. For example, you purchase 10 licenses of ProductA. You can
allocate the licenses to the target devices before ProductA is even installed on the devices.
A
demographic allocation
is the assignment of one or more licenses to a site, department, or cost
center. Any device that is assigned the demographic and has the product installed shows up as an
installation associated with the allocation. For example, you purchase 15 licenses of ProductA and
Summary of Contents for ZENWORKS 10 CONFIGURATION MANAGEMENT SP3 - COMMAND LINE UTILITIES REFERENCE 10.3 30-03-2010
Page 4: ...4 ZENworks 10 Asset Management Reference novdocx en 7 January 2010 ...
Page 12: ...12 ZENworks 10 Asset Management Reference novdocx en 7 January 2010 ...
Page 14: ...14 ZENworks 10 Asset Management Reference novdocx en 7 January 2010 ...
Page 38: ...38 ZENworks 10 Asset Management Reference novdocx en 7 January 2010 ...
Page 40: ...40 ZENworks 10 Asset Management Reference novdocx en 7 January 2010 ...
Page 68: ...68 ZENworks 10 Asset Management Reference novdocx en 7 January 2010 ...
Page 110: ...110 ZENworks 10 Asset Management Reference novdocx en 7 January 2010 ...
Page 124: ...124 ZENworks 10 Asset Management Reference novdocx en 7 January 2010 ...
Page 128: ...128 ZENworks 10 Asset Management Reference novdocx en 7 January 2010 ...
Page 130: ...130 ZENworks 10 Asset Management Reference novdocx en 7 January 2010 ...
Page 134: ...134 ZENworks 10 Asset Management Reference novdocx en 7 January 2010 ...
Page 136: ...136 ZENworks 10 Asset Management Reference novdocx en 7 January 2010 ...
Page 140: ...140 ZENworks 10 Asset Management Reference novdocx en 7 January 2010 ...
Page 142: ...142 ZENworks 10 Asset Management Reference novdocx en 7 January 2010 ...
Page 144: ...144 ZENworks 10 Asset Management Reference novdocx en 7 January 2010 ...
Page 154: ...154 ZENworks 10 Asset Management Reference novdocx en 7 January 2010 ...
Page 162: ...162 ZENworks 10 Asset Management Reference novdocx en 7 January 2010 ...
Page 164: ...164 ZENworks 10 Asset Management Reference novdocx en 7 January 2010 ...
Page 166: ...166 ZENworks 10 Asset Management Reference novdocx en 7 January 2010 ...
Page 170: ...170 ZENworks 10 Asset Management Reference novdocx en 7 January 2010 ...
Page 172: ...172 ZENworks 10 Asset Management Reference novdocx en 7 January 2010 ...
Page 180: ...180 ZENworks 10 Asset Management Reference novdocx en 7 January 2010 ...
Page 182: ...182 ZENworks 10 Asset Management Reference novdocx en 7 January 2010 ...
Page 186: ...186 ZENworks 10 Asset Management Reference novdocx en 7 January 2010 ...
Page 196: ...196 ZENworks 10 Asset Management Reference novdocx en 7 January 2010 ...
Page 200: ...200 ZENworks 10 Asset Management Reference novdocx en 7 January 2010 ...