Novell ZENWORKS 10 CONFIGURATION MANAGEMENT SP3 - COMMAND LINE UTILITIES REFERENCE 10.3... User manual

Novell®
www.novell.com
novdocx (en) 7 January 2010
AUTHORIZED DOCUMENTATION
ZENworks 10 Asset Management Reference
ZENworks ® 10 Asset Management SP3
10.3
March 30, 2010
Reference

novdocx (en) 7 January 2010
Legal Notices
Novell, Inc., makes no representations or warranties with respect to the contents or use of this documentation, and
specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose.
Further, Novell, Inc., reserves the right to revise this publication and to make changes to its content, at any time,
without obligation to notify any person or entity of such revisions or changes.
Further, Novell, Inc., makes no representations or warranties with respect to any software, and specifically disclaims
any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc.,
reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to
notify any person or entity of such changes.
Any products or technical information provided under this Agreement may be subject to U.S. export controls and the
trade laws of other countries. You agree to comply with all export control regulations and to obtain any required
licenses or classification to export, re-export or import deliverables. You agree not to export or re-export to entities on
the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in the U.S. export laws.
You agree to not use deliverables for prohibited nuclear, missile, or chemical biological weaponry end uses. See the
Novell International Trade Services Web page (http://www.novell.com/info/exports/) for more information on
exporting Novell software. Novell assumes no responsibility for your failure to obtain any necessary export
approvals.
Copyright © 2007-2010 Novell, Inc. All rights reserved. No part of this publication may be reproduced, photocopied,
stored on a retrieval system, or transmitted without the express written consent of the publisher.
Novell, Inc., has intellectual property rights relating to technology embodied in the product that is described in this
document. In particular, and without limitation, these intellectual property rights may include one or more of the U.S.
patents listed on the Novell Legal Patents Web page (http://www.novell.com/company/legal/patents/) and one or
more additional patents or pending patent applications in the U.S. and in other countries.
Novell, Inc.
404 Wyman Street, Suite 500
Waltham, MA 02451
U.S.A.
www.novell.com
Online Documentation: To access the latest online documentation for this and other Novell products, see
the Novell Documentation Web page (http://www.novell.com/documentation).

novdocx (en) 7 January 2010
Novell Trademarks
For Novell trademarks, see the Novell Trademark and Service Mark list (http://www.novell.com/company/legal/
trademarks/tmlist.html).
Third-Party Materials
All third-party trademarks are the property of their respective owners.

4ZENworks 10 Asset Management Reference
novdocx (en) 7 January 2010

Contents 5
Contents
novdocx (en) 7 January 2010
About This Guide 11
Part I License Compliance 13
1 License Compliance Concepts 15
1.1 License Compliance Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
1.2 Entitlements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
1.2.1 Entitlement Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
1.2.2 License Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
1.2.3 User Sources for User-Based License Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
1.2.4 License Periods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
1.2.5 Compliance Calculations for Multiple Entitlements . . . . . . . . . . . . . . . . . . . . . . . . . . 21
1.3 Installation Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
1.4 License Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
1.5 Suites and Software Collections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
1.6 Version Upgrades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2 Setting Up License Compliance 25
2.1 Preparing Your Management Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
2.2 Setting Up Compliance for Software Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
2.3 Monitoring Compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
3 Configuring Compliance Settings 29
4 Monitoring Compliance Status 31
4.1 Home Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
4.2 Licensed Products List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
4.3 Licensed Product’s Compliance Status Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
4.3.1 License Consumption (Consumption Data Source: Inventory) . . . . . . . . . . . . . . . . . 33
4.3.2 Compliance Status (Consumption Data Source: Inventory) . . . . . . . . . . . . . . . . . . . 34
4.3.3 Unresolved Installations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
4.3.4 Compliance Status (Consumption Data Source: Manual) . . . . . . . . . . . . . . . . . . . . . 37
5 Generating Compliance Reports 39
6 Working with Licensed Products 41
6.1 Viewing the Licensed Products List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
6.2 Filtering the Licensed Products List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
6.3 Creating a Licensed Product Folder. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
6.4 Refreshing Compliance Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
6.4.1 Automatically Refreshing Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
6.4.2 Manually Triggering a Refresh. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
6.4.3 Viewing Refresh Details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
6.5 Creating a Licensed Product . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

6ZENworks 10 Asset Management Reference
novdocx (en) 7 January 2010
6.5.1 Manually Creating a Licensed Product . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
6.5.2 Creating a Licensed Product from a Discovered Product . . . . . . . . . . . . . . . . . . . . . 46
6.6 Changing a Licensed Product’s General Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
6.7 Adding Custom Fields to Licensed Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
6.8 Merging Licensed Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
6.9 Deleting a Licensed Product . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
6.10 Moving a Licensed Product . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
7 Working with Entitlements 53
7.1 Viewing a Licensed Product’s Entitlements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
7.2 Creating an Entitlement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
7.2.1 Creating an Inventory Entitlement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
7.2.2 Creating a Manual Entitlement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
7.3 Adding Catalog Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
7.3.1 Editing an Entitlement to Add Catalog Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
7.3.2 Using the Catalog Products List to Add Catalog Products . . . . . . . . . . . . . . . . . . . . 59
7.4 Adding Purchase Summary Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
7.5 Adding Discovered Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
7.5.1 Editing an Entitlement to Add Discovered Products . . . . . . . . . . . . . . . . . . . . . . . . . 61
7.5.2 Using the Discovered Products List to Add Discovered Products . . . . . . . . . . . . . . . 62
7.6 Specifying User and Device Coverage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
7.6.1 Adding Covered Devices to OEM and Machine Entitlements . . . . . . . . . . . . . . . . . . 63
7.6.2 Adding Covered Users to Per-Named User Entitlements . . . . . . . . . . . . . . . . . . . . . 64
7.6.3 Excluding Users from Per-User Entitlements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
7.7 Adding Contracts and Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
8 Working with Discovered Products 69
8.1 How Installed Software Products Become Discovered Products. . . . . . . . . . . . . . . . . . . . . . . 69
8.2 Viewing the Discovered Products List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
8.3 Filtering the Discovered Products List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
8.4 Excluding Discovered Products from Compliance Calculations. . . . . . . . . . . . . . . . . . . . . . . . 72
8.5 Adding Discovered Products to Licensed Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
8.5.1 Editing an Entitlement to Add Discovered Products . . . . . . . . . . . . . . . . . . . . . . . . . 72
8.5.2 Using the Discovered Products List to Add Discovered Products . . . . . . . . . . . . . . . 73
8.6 Adding Discovered Products to Software Collections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
8.7 Viewing a Discovered Product’s Installations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
8.8 Adjusting a Discovered Product’s Installation Count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
8.9 Assigning a Standards Category . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
8.10 Viewing the Inventory Products Included in a Discovered Product . . . . . . . . . . . . . . . . . . . . . 78
8.11 Refreshing Compliance Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
8.11.1 Automatically Refreshing Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
8.11.2 Manually Triggering a Refresh. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
8.11.3 Viewing Refresh Details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
9 Working with Purchase Records 81
9.1 Viewing the Purchase Records List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
9.2 Filtering the Purchase Records List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
9.3 Creating a Purchase Record Folder. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
9.4 Creating Purchase Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
9.4.1 Importing Purchase Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
9.4.2 Manually Creating Purchase Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Contents 7
novdocx (en) 7 January 2010
9.5 Viewing a Purchase Record’s Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
9.6 Changing a Purchase Record’s General Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
9.7 Deleting a Purchase Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
9.8 Moving a Purchase Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
9.9 Working with Import Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
9.9.1 Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
9.9.2 Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
10 Working with Catalog Products 95
10.1 Viewing the Catalog Products List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
10.2 Filtering the Catalog Products List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
10.3 Excluding Catalog Products from Compliance Calculations . . . . . . . . . . . . . . . . . . . . . . . . . . 97
10.4 Creating Catalog Products by Importing Purchase Records . . . . . . . . . . . . . . . . . . . . . . . . . . 98
10.5 Creating Catalog Products Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
10.6 Adding Purchased Licenses to a Catalog Product . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
10.7 Adding Catalog Products to a Licensed Product . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
10.7.1 Editing an Entitlement to Add Catalog Products . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
10.7.2 Using the Catalog Products List to Add Catalog Products . . . . . . . . . . . . . . . . . . . 100
10.8 Creating a Catalog Product Folder. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
10.9 Viewing a Catalog Product’s Purchases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
10.10 Changing a Catalog Product’s General Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
10.11 Deleting a Catalog Product . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
10.12 Moving a Catalog Product . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
11 Working with Software Collections 105
11.1 How Software Collection Installations are Counted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
11.2 Creating a Software Collection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
11.3 Adding Products to a Software Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
11.4 Deleting a Software Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
11.5 Creating a Software Collection Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
11.6 Moving a Software Collection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Part II License Allocation 109
12 License Allocation Concepts 111
12.1 Allocation vs. Compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
12.2 Device Allocations and Demographic Allocations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
13 Preparing Demographic Data 113
13.1 Adding Demographic Data to Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
13.2 Adding Demographic Data to Purchase Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
13.3 Adding Demographic Data to Purchase Record Import Files. . . . . . . . . . . . . . . . . . . . . . . . . 115
13.4 Making Demographic Data Consistent Between Devices and Purchase Records . . . . . . . . 116
14 Allocating Licenses 117
14.1 Initializing Allocations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
14.2 Manually Adding Demographic Allocations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
14.3 Manually Adding Device Allocations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

8ZENworks 10 Asset Management Reference
novdocx (en) 7 January 2010
15 Working with License Allocations 125
15.1 Adjusting the License Quantity for a Demographic Allocation . . . . . . . . . . . . . . . . . . . . . . . . 125
15.2 Removing Allocations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
16 Generating Allocation Reports 127
Part III Software Usage 129
17 Software Usage Concepts 131
17.1 Software That Is Tracked . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
17.2 When Usage Data Is Collected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
17.3 Basic Usage Data vs. Detailed Usage Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
18 Configuring Usage Settings 133
19 Setting Up Web Applications 135
20 Monitoring Usage 137
20.1 Discovered Products List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
20.2 Licensed Product’s Compliance Status Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
20.3 Discovered Product’s Installation/Consumption Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
21 Generating Usage Reports 141
Part IV Contracts 143
22 Creating New Contracts 145
23 Working with Existing Contracts 149
23.1 Viewing the Contracts List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
23.2 Filtering the Contracts List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
23.3 Creating a Contracts Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
23.4 Copying an Existing Contract. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
23.5 Adding Documents to Contracts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
24 Working with Date Notifications 155
24.1 Specifying an E-Mail Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
24.2 Configuring Default Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
24.3 Adding Date Notifications to a Contract . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
24.4 Viewing the Date Notifications List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
24.5 Filtering the Date Notifications List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
24.6 Creating Date Notification Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
24.7 Moving a Date Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
24.8 Deleting a Date Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

Contents 9
novdocx (en) 7 January 2010
25 Generating Contract Reports 161
Part V Documents 163
26 Uploading Documents 165
27 Working with Documents 167
27.1 Viewing the Documents List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
27.2 Filtering the Documents List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
27.3 Creating a Documents Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
27.4 Attaching Documents to Licensed Products, Contracts, and Purchase Summary Records . 169
Part VI Reports 171
28 Standard and Custom Report Descriptions 173
28.1 License Management Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
28.1.1 Standard Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
28.1.2 Sample Custom Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
28.2 Software Usage Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
28.2.1 Standard Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
28.2.2 Sample Custom Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
28.3 Contract Management Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
28.3.1 Standard Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
28.3.2 Sample Custom Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
29 Configuring Report Rights 179
30 Configuring Report Settings 181
31 Working with Standard Reports 183
31.1 Running a Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
31.2 Exporting a Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
31.3 Viewing a Report as a Graph . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
31.4 Changing the Report Period. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
31.5 Changing the Filter Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
32 Working with Custom Reports 187
32.1 Creating a Custom Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
32.2 Running a Custom Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
32.3 Scheduling a Custom Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
32.4 Viewing a Scheduled Custom Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
32.5 Editing a Custom Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
32.6 Creating a Custom Report Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
32.7 Deleting a Custom Report Folder. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
32.8 Moving a Custom Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
32.9 Deleting a Custom Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
32.10 Importing New Report Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195

10 ZENworks 10 Asset Management Reference
novdocx (en) 7 January 2010
33 Working with ZENworks Reporting Server Reports 197
33.1 Predefined Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
33.1.1 License Allocation Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
33.1.2 Purchases Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
33.1.3 Software Compliance Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
33.1.4 Suites Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
33.2 Viewing a Predefined Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199

About This Guide 11
novdocx (en) 7 January 2010
About This Guide
This Novell ZENworks 10 Asset Management Reference includes information to help you manage
the software licenses within your organization. The information in this guide is organized as
follows:
Part I, “License Compliance,” on page 13
Part II, “License Allocation,” on page 109
Part III, “Software Usage,” on page 129
Part IV, “Contracts,” on page 143
Part V, “Documents,” on page 163
Part VI, “Reports,” on page 171
Audience
This guide is intended for Novell®ZENworks®administrators.
Feedback
We want to hear your comments and suggestions about this manual and the other documentation
included with this product. Please use the User Comments feature at the bottom of each page of the
online documentation, or go to the Novell Documentation Feedback site (http://www.novell.com/
documentation/feedback.html) and enter your comments there.
Additional Documentation
ZENworks 10 Asset Management is supported by other documentation (in both PDF and HTML
formats) that you can use to learn about and implement the product. See the ZENworks 10
Configuration Management documentation (http://www.novell.com/documentation/zcm10/
index.html).
Documentation Conventions
In Novell documentation, a greater-than symbol (>) is used to separate actions within a step and
items in a cross-reference path.
A trademark symbol (®, TM, etc.) denotes a Novell trademark. An asterisk (*) denotes a third-party
trademark.

12 ZENworks 10 Asset Management Reference
novdocx (en) 7 January 2010

License Compliance
I
13
novdocx (en) 7 January 2010
I
License Compliance
Novell®ZENworks®Asset Management lets you monitor software products in your organization to
know whether or not your software deployment complies with your software licensing.
Chapter 1, “License Compliance Concepts,” on page 15
Chapter 2, “Setting Up License Compliance,” on page 25
Chapter 3, “Configuring Compliance Settings,” on page 29
Chapter 4, “Monitoring Compliance Status,” on page 31
Chapter 5, “Generating Compliance Reports,” on page 39
Chapter 6, “Working with Licensed Products,” on page 41
Chapter 7, “Working with Entitlements,” on page 53
Chapter 8, “Working with Discovered Products,” on page 69
Chapter 9, “Working with Purchase Records,” on page 81
Chapter 10, “Working with Catalog Products,” on page 95
Chapter 11, “Working with Software Collections,” on page 105

14 ZENworks 10 Asset Management Reference
novdocx (en) 7 January 2010

License Compliance Concepts
1
15
novdocx (en) 7 January 2010
1
License Compliance Concepts
Ensuring that your organization owns the licenses needed to cover the products your users have
installed is a critical component of license management. At the same time, you want to minimize
costs by purchasing only the number of licenses that you really need.
Novell®ZENworks®Asset Management helps you attain this balance by monitoring and reporting
the license compliance status (compliant, overcompliant, or undercompliant) of your software
products.
The following sections introduce the concepts you should understand to effectively use Asset
Management to manage software license compliance in your organization:
Section 1.1, “License Compliance Components,” on page 15
Section 1.2, “Entitlements,” on page 18
Section 1.3, “Installation Data,” on page 22
Section 1.4, “License Data,” on page 23
Section 1.5, “Suites and Software Collections,” on page 23
Section 1.6, “Version Upgrades,” on page 23
1.1 License Compliance Components
To know whether or not a software product’s deployment within your organization complies with
your software product license records, you must reconcile three important pieces of information
about the product:
Entitlement: The rights to the software product, including how, where, and how long the
product can be used. Can the user use the product only on the OEM machine with which it
came? Can the user install the product on multiple machines under one license? Does each
installation of the product require a license? Can the product be used forever, or does it have an
expiration date? This information is contained in the software product’s license agreement or in
a software purchase contract.
Licenses: The number of licenses of the software product that your organization has purchased.
Typically, this information comes from purchase records provided by the software vendor.
Installations: The actual number of installations of the software product in your organization.
ZENworks Asset Inventory can provide this information by scanning the devices in your
organization (as long as the devices are registered in your ZENworks Management Zone). Or,
you can manually provide this information.
The following illustration shows the components that Asset Management uses to bring your product
information together:

16 ZENworks 10 Asset Management Reference
novdocx (en) 7 January 2010
Figure 1-1 Compliance Components
Licensed Product: Alicensed product is the software product whose license compliance status you
want to monitor. The information (entitlements, installations, and purchased licenses) needed to
determine the compliance status is provided through the licensed product’s components
(entitlements, discovered products, catalog products, and purchase records).
A licensed product can be version independent (such as Product A) to cover multiple versions, or it
can be version-specific (such as Product B Version 11).
License Entitlement: More than likely, not all of your purchases of a software product fall under
the same license agreement. Some agreements might specify different license types (full, upgrade,
and so forth), some might specify different license models (per-user, per-installation, OEM, and so
forth), or some might have different license periods (perpetual or fixed-term).
Catalog Products
Product A (OEM)
• 8 Licenses
Purchase Record
Product A (OEM)
• 5 Licenses
Purchase Record
Product A (10-Pack)
• 10 Licenses
Discovered Products
Product A
• 25 Installations
Entitlement
Product A Per–User
License Type:
License Model:
Coverage:
Full
Per–User
Any Users
Available Licenses: 25
Consumed Licenses: 20
Available Licenses: 25
Consumed Licenses: 20
Entitlement
Product A OEM
License Type:
License Model:
Coverage:
Full
OEM
M1, M2, M3,
M4, M5
Licensed Product
Product A
Compliance Status: Over–Compliant
Available Licenses: 30
Licenses Consumed: 25
Catalog Products
Product A (10-Pack)
• 20 Licenses
Product A (5-Pack)
• 5 Licenses
Purchase Record
Product A (10-Pack)
• 10 Licenses
Product A (5-Pack)
• 5 Licenses
Discovered Products
Product A
• 25 Installations

License Compliance Concepts 17
novdocx (en) 7 January 2010
Each different license agreement for the software product must be represented by a unique license
entitlement. A license entitlement defines the agreement details such as the license type, license
model, and license period. In addition, a license entitlement includes the number of product
installations, the number of purchased licenses, and the users and devices whose product
installations can be covered by the entitlement. Based on the entitlement details and the available
licenses, consumed licenses (from installations), and coverage information, Asset Management
determines the licensed product’s compliance status.
In the example, Product A has two entitlements representing two license agreements with different
license models:
An OEM license agreement. The installations of the product on the covered OEM machines
(M1, M2, M3, M4, and M5) are tracked against the OEM entitlement to monitor compliance
with the OEM license agreement.
A Per-User license agreement. All other installations are tracked against the Per-User
entitlement to monitor compliance with that agreement.
More information about entitlements is included in Section 1.2, “Entitlements,” on page 18.
Catalog Products: A catalog product identifies a software product for which you’ve purchased
licenses. When added to an entitlement, a catalog product’s licenses become available for
consumption by the entitlement’s installations.
Typically, a catalog product corresponds to a specific product part number. For example, when you
purchase a single copy, a 10-pack, and a 100-pack of the same software product, each has a different
product part number. As a result, each is a separate catalog product. Likewise, if you purchase two
10-packs of the same software product, one a full license pack and the other an upgrade license
pack, each of these is a separate catalog product.
As a result, a single software product might have multiple catalog products. This allows you to
assign the appropriate catalog products to the appropriate entitlements. In the example, the catalog
products that represent non-OEM versions of Product A are associated with the Product A Per-User
entitlement, resulting in 25 available licenses. The Product A OEM catalog product is associated
with the Product A OEM entitlement, resulting in 5 available licenses.
More information about catalog products is found in Section 1.4, “License Data,” on page 23.
Purchase Records: A purchase record provides details about the number of licenses purchased for
a software product. The licenses roll up to the catalog product that represents the purchased software
product.
When you purchase a software product over time, you end up with multiple purchase records for the
same software product. In this case, the software product’s licenses (included in each purchase
record) roll up to the same catalog product. In the example, Product A (10-Pack) was purchased at
two different times; however, the licenses from both purchase records are rolled into the Product A
(10-Pack) catalog product.
If you have electronic purchase record files, you can import the purchase records. When you import
a purchase record file, Asset Management creates catalog products for the software products
included in the file. If you do not have purchase record files, you must manually enter the purchase
records and manually create the catalog products.
If you do not have purchase records that include detailed software purchase information, you can
create purchase summary records to represent the purchased licenses. To provide proof of
purchases, you can attach supporting documents to the purchase summary records.

18 ZENworks 10 Asset Management Reference
novdocx (en) 7 January 2010
More information about purchase records is found in Section 1.4, “License Data,” on page 23.
Discovered Products: A discovered product represents a software product installed in your
Management Zone. When associated with an entitlement, the discovered product’s installations are
eligible to consume the entitlement’s licenses.
If a discovered product’s installations can be covered by different entitlements (for the same
licensed product), you can assign the discovered product to each entitlement. Based on the
entitlements’ license models and coverage, the Asset Management compliance engine determines
which entitlement covers each installation.
In the example, Product A (the discovered product) is associated with both entitlements. Five of the
installations (on M1, M2, M3, M4, and M5) consume licenses in the Product A OEM entitlement.
The other 20 installations consume licenses in the Product A Per-User entitlement.
More information about discovered products is found in Section 1.3, “Installation Data,” on
page 22.
1.2 Entitlements
As explained in Section 1.1, “License Compliance Components,” on page 15, license entitlements
are one of the three pieces of information that you need to understand and manage to effectively
maintain license compliance for a software product. The following sections explain concepts that
apply to entitlements:
Section 1.2.1, “Entitlement Types,” on page 18
Section 1.2.2, “License Models,” on page 19
Section 1.2.3, “User Sources for User-Based License Models,” on page 21
Section 1.2.4, “License Periods,” on page 21
Section 1.2.5, “Compliance Calculations for Multiple Entitlements,” on page 21
1.2.1 Entitlement Types
When you create an entitlement, you specify the entitlement type. There are three different types of
entitlements:
Full License: Represents a license agreement that gives users the right to install the product
without owning a previous version.
License/Maintenance: Represents a license agreement that gives users full license rights to the
purchased version and subsequent maintenance versions.
Version Upgrade: Represents a license agreement that gives users rights to upgrade a previous
product version to the new version. A Version Upgrade entitlement references a base
entitlement to automatically adjust available licenses between itself and the base entitlement.
More information about Version Upgrade entitlements is provided in Section 1.6, “Version
Upgrades,” on page 23.

License Compliance Concepts 19
novdocx (en) 7 January 2010
1.2.2 License Models
When you create an entitlement, you specify the license model for the entitlement. The entitlement’s
license model determines 1) how license consumption is calculated and 2) which product
installations can be covered by the entitlement.
There are different license models for entitlements that use Inventory installation data and for
entitlements that use manually-entered installation data.
“License Models for Inventory Entitlements” on page 19
“License Models for Manual Entitlements” on page 20
License Models for Inventory Entitlements
The Inventory data for a discovered product includes information about the devices on which the
product is installed and the primary users associated with those devices. This installation-to-device-
to-user association supports the following device-based and user-based license models:
Table 1-1 License Models for Inventory Entitlements
License Model License Consumption Coverage Example
Per-Installation Each installation of the
entitlement’s
discovered products
consumes a license.
All devices. 20 users have the product
installed on one device each. An
additional 5 users each have the
product installed on two devices.
There are 30 total installations,
and each installation consumes a
license.
OEM A covered device
consumes a license
whether or not any of
the entitlement’s
discovered products
are installed on the
device.
Only the devices you
specify as covered
devices.
You specify 15 devices as
covered devices. The product is
installed on only 12 of the devices
because three users have
uninstalled the product. Even
though there are 12 total
installations, all 15 covered
devices consume a license.
Machine A covered device
consumes a license
only if one or more of
the entitlement’s
discovered products
are installed on the
device.
Only the devices you
specify as covered
devices.
You specify 15 devices as
covered devices. The product is
installed on only 12 of the devices.
Even though you specified 15
covered devices, there are 12
total installations, so 12 covered
devices consume a license.

20 ZENworks 10 Asset Management Reference
novdocx (en) 7 January 2010
License Models for Manual Entitlements
When you manually enter installation data (rather than use the Inventory data), no device or user
information is associated with the installations. Because of this, entitlements with manual data
source support only installation-based license models. You provide the total installation quantity,
and that quantity consumes any of the entitlement’s available licenses.
There are several predefined license models for manual entitlements. These license models are
intended to match the license models most commonly used in license agreements. If your license
model is not represented, you can define it.
Table 1-2 License Models for Manual Entitlements
Per-User Each user consumes a
single license for any
installations of the
entitlement’s
discovered products,
regardless of the
numberofinstallations.
All users. You can
exclude specific users.
The entitlement includes two
discovered products (DP1 and
DP2). Both products are installed
on User1’s device. User1
consumes one license.
Or, DP1 is installed on one of
User1’s devices and DP1 and
DP2 are installed on another of
User1’s devices, User1 still
consumes only one of the
entitlement’s licenses.
Per-Named User Each covered user
consumes a single
license for any
installations of the
entitlement’s
discovered products,
regardless of the
numberofinstallations.
Only the users you
specify as covered
users.
Same as the Per-User model.
License Model License Consumption Coverage Example
Unrestricted
Qualified Desktop
CPU
User
Named User
Server
CAL
Site
Enterprise
Each installation
consumes a license.
The specified
installation
quantity.
Example 1: 20 users have the product
installed. The license agreement specifies
a User license model. You select User as
the entitlement’s license model and enter
20 total installations to cover the product
installations. The 20 installations consume
any licenses associated with the
entitlement.
Example 2: 15 servers have a server
product installed. The license agreement
specifies a Server license model. You
select Server as the entitlement’s license
model and enter 15 total installations to
cover the product installations. The 15
installations consume any licenses
associated with the entitlement.
License Model License Consumption Coverage Example