![Novell ZENWORKS 10 CONFIGURATION MANAGEMENT SP3 - COMMAND LINE UTILITIES REFERENCE 10.3 30-03-2010 Reference Manual Download Page 21](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_1711928021.webp)
License Compliance Concepts
21
no
vd
ocx
(e
n)
7 Ja
nua
ry 201
0
1.2.3 User Sources for User-Based License Models
Discovered product installations are associated with devices. For example, if a discovered product is
found on two devices, both devices are recorded in the discovered product’s information. This
installation-to-device association enables the use of
device-based
license models (Per-Installation,
OEM, and Machine).
To enable
user-based
license models (Per-User and Per-Named User), Asset Management uses an
installation-to-device-to-user association. This means that each device must have a user associated
with it. There are two different user sources that can provide this association. You must choose one
or the other:
Inventory User Data:
Each device’s Inventory data includes a user field. Asset Inventory does
not automatically populate the field. There are three ways that you can populate the user
information: 1) collect the information from users through an automated Inventory Collection
Data form, 2) manually enter the user information by editing a device’s Inventory data in
ZENworks Control Center, or 3) migrate Inventory data from ZENworks 7.5 Asset
Management.
Authoritative User Source:
This is the LDAP directory (or directories) your ZENworks
Management Zone connects to for user information. By default, the ZENworks system is
configured to automatically assign users from this source as primary users on devices. If a
device has multiple users, the primary user is determined by a calculation method that you can
select (usage based, login based, or direct assignment).
Both options work equally well. The Authoritative User Source method provides greater automation
because you don’t need to manually enter user information, migrate information, or rely on users to
complete the automated collection form.
If you are using Asset Management with ZENworks 7 Desktop Management, you must use the
Inventory User Data method. The ZENworks Adaptive Agent’s User Management feature, which is
required with the Authoritative User Source method, cannot coexist on the same device with the
ZENworks 7 Desktop Management Agent. Installing the User Management feature automatically
uninstalls the Desktop Management Agent.
1.2.4 License Periods
License agreements (or contracts) might stipulate a period of time during which the product can be
used. When you create an entitlement, you specify whether the license period is perpetual (never
ending) or fixed term. With fixed term, you specify the start date and end date.
1.2.5 Compliance Calculations for Multiple Entitlements
It is common for a licensed product to have multiple entitlements that share the same discovered
product. When this happens, the Software Compliance Engine must determine how the discovered
product’s installations are allocated among the entitlements.
The Software Compliance Engine processes the entitlements with the most restrictive license
models first. The most restrictive entitlements have fewer installations that meet the restrictions. By
processing them first, the greatest number of installations can be processed against the entitlements,
increasing the likelihood that the entitlement’s licenses are consumed.
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 ...