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

Novell®
www.novell.com
novdocx (en) 16 April 2010
AUTHORIZED DOCUMENTATION
ZENworks 10 Configuration Management Software Distribution Reference
ZENworks ® 10 Configuration Management SP3
10.3
March 30, 2010
Software Distribution Reference

novdocx (en) 16 April 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.
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) 16 April 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 Configuration Management Software Distribution Reference
novdocx (en) 16 April 2010

Contents 5
Contents
novdocx (en) 16 April 2010
About This Guide 9
1 Basic Concepts 11
1.1 Bundles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.2 Assigning Bundles to Devices vs. Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
1.3 Packaging Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
1.4 Dependency Bundles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.4.1 Primary Applications vs. Dependent Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.4.2 Bundle Chains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
1.4.3 Distributing, Installing, and Launching a Bundle That Has Dependencies . . . . . . . . 15
1.5 Content. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
1.5.1 Content Replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
1.5.2 Content Delivery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2 Creating Bundles 19
2.1 Creating Directive Bundles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
2.2 Creating File Bundles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2.3 Creating Imaging Bundles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
2.4 Creating Windows Bundles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
2.5 Creating Bundles by Using the zman Command Line Utility . . . . . . . . . . . . . . . . . . . . . . . . . . 39
2.5.1 Creating a Bundle without Content or Dependency on Another Bundle . . . . . . . . . . 39
2.5.2 Creating a Bundle with Content and Dependency on Another Bundle . . . . . . . . . . . 40
2.5.3 Understanding the zman Bundle XML File Format . . . . . . . . . . . . . . . . . . . . . . . . . . 42
3 Managing Bundles 45
3.1 Creating Bundles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
3.2 Assigning Existing Bundles to Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
3.3 Assigning Existing Bundles to Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
3.4 Adding a Bundle to a Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
3.5 Renaming, Copying, or Moving Bundles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
3.6 Adding System Requirements for a Bundle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
3.6.1 Filter Conditions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
3.6.2 Filter Logic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
3.7 Copying a Bundle’s System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
3.8 Managing Bundle Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
3.9 Managing Bundle Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
3.10 Deleting a Bundle. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
3.11 Incrementing a Bundle’s Version Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
3.11.1 Using the Action menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
3.11.2 Editing the Bundle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
3.12 Installing a Bundle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
3.13 Launching a Bundle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
3.14 Copying a Bundle to a Content Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
3.15 Preventing a Bundle from Being Deployed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
3.16 Enabling a Bundle to Be Deployed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
3.17 Enabling a Bundle to Be Uninstalled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

6ZENworks 10 Configuration Management Software Distribution Reference
novdocx (en) 16 April 2010
3.18 Uninstalling a Bundle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
3.18.1 Bundle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
3.18.2 Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
3.19 Modifying Action Set Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
3.19.1 Install Action Set Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
3.19.2 Launch Action Set Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
3.19.3 Uninstall Action Set Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
3.19.4 Terminate Action Set Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
3.20 Show Bundle Activity on the Managed Device. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
3.21 Viewing the Predefined Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
4 Managing Bundle Groups 77
4.1 Creating Bundle Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
4.2 Renaming or Moving Bundle Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
4.3 Copying a Bundle Group’s System Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
4.4 Deleting a Bundle Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
4.5 Assigning a Bundle Group to Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
4.6 Assigning a Bundle Group to Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
4.7 Adding a Bundle to a Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
4.8 Copying a Bundle Group to a Content Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
5 Managing Folders 85
5.1 Creating Folders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
5.2 Renaming or Moving Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
5.3 Deleting a Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
6 Managing Bundles by using the ZENworks Adaptive Agent 87
6.1 Bundles vs. Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
6.2 User-Assigned vs. Device-Assigned Bundles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
6.3 Accessing Bundles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
6.3.1 ZENworks Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
6.3.2 ZENworks Explorer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
6.3.3 ZENworks Icon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
6.4 Understanding Bundle Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
6.5 Launching a Bundle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
6.6 Postponing a Bundle Download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
6.7 Verifying a Bundle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
6.8 Viewing a Bundle’s Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
6.9 Uninstalling a Bundle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
A Install, Uninstall, and Repair Parameters 95
A.1 Install Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
A.1.1 Restart Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
A.1.2 Display Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
A.1.3 Install Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
A.1.4 Command Line Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
A.2 Uninstall Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
A.2.1 Restart Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
A.2.2 Display Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
A.2.3 Command Line Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Contents 7
novdocx (en) 16 April 2010
A.3 Repair Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
A.3.1 Restart Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
A.3.2 Display Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
A.3.3 Repair Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
A.3.4 Command Line Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
B Authentication Hook 103
C Novell File Upload Extension 105
C.1 Installing the Novell File Upload Extension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
C.1.1 On Mozilla Firefox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
C.1.2 On Microsoft Internet Explorer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
C.2 Reinstalling the Novell File Upload Extension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
D Bundle Schedules Types 109
D.1 Date Specific . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
D.2 Event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
D.3 Now . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
D.4 Recurring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
E Actions 115
E.1 Action - Apply Personality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
E.2 Action - Copy Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
E.3 Action - Copy Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
E.4 Action - Create/Delete Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
E.5 Action - Delay. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
E.6 Action - Display Message. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
E.7 Action - Distribute Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
E.8 Action - Edit INI File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
E.8.1 Filename . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
E.8.2 Encoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
E.8.3 Create File, If Does Not Exist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
E.8.4 INI Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
E.8.5 Advanced Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
E.9 Action - Edit Text File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
E.10 Action - End Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
E.11 Action - File Removal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
E.12 Action - Install Bundle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
E.13 Action - Install Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
E.14 Action - Install Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
E.15 Action - Install MSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
E.16 Action - Install MSP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
E.17 Action - Install Network MSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
E.18 Action - Launch Bundle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
E.19 Action - Launch Java Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
E.20 Action - Launch URL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
E.21 Action - Launch Executable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
E.21.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
E.21.2 Advanced. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
E.21.3 Launch Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

8ZENworks 10 Configuration Management Software Distribution Reference
novdocx (en) 16 April 2010
E.22 Action - Launch Windows Thin Client Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
E.22.1 ICA Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
E.22.2 RDP Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
E.23 Action - Prompt User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
E.24 Action - Reboot/Shutdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
E.25 Action - Registry Edit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
E.25.1 Registry Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
E.25.2 Advanced Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
E.26 Action - Run Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
E.26.1 Specify a File on a Managed Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
E.26.2 Define Your Own Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
E.26.3 Select From This Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
E.27 Action - Start/Stop Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
E.28 Action - Store Personality. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
E.29 Action - Terminate Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
E.30 Action - Terminate Application Prompt. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
E.31 Action - Undo Install Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
E.32 Action - Uninstall Bundle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
E.33 Action - Verify Bundle. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
E.34 Action - Verify Install Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
F Troubleshooting 177
G Best Practices 183
G.1 Changing the Look and Feel of the Start Menu on a Windows Vista Device . . . . . . . . . . . . . 183
G.2 Pinning Applications to the Start Menu on a Windows Vista Device . . . . . . . . . . . . . . . . . . . 183
G.3 Assigning Bundles to a Device or User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
G.4 ZENworks Explorer Folder Naming Convention. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
H Macros 185
H.1 Windows Macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
H.2 Login Script Macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
I Documentation Updates 189
I.1 March 30, 2010: SP3 (10.3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189

About This Guide 9
novdocx (en) 16 April 2010
About This Guide
This ZENworks 10 Configuration Management Software Distribution Reference includes conceptual
and task-based information to help you effectively manage software distribution in your Novell®
ZENworks®10 Configuration Management SP3 system. This guide is organized as follows:
Chapter 1, “Basic Concepts,” on page 11
Chapter 2, “Creating Bundles,” on page 19
Chapter 3, “Managing Bundles,” on page 45
Chapter 4, “Managing Bundle Groups,” on page 77
Chapter 5, “Managing Folders,” on page 85
Chapter 6, “Managing Bundles by using the ZENworks Adaptive Agent,” on page 87
Appendix A, “Install, Uninstall, and Repair Parameters,” on page 95
Appendix B, “Authentication Hook,” on page 103
Appendix C, “Novell File Upload Extension,” on page 105
Appendix D, “Bundle Schedules Types,” on page 109
Appendix E, “Actions,” on page 115
Appendix F, “Troubleshooting,” on page 177
Appendix G, “Best Practices,” on page 183
Appendix H, “Macros,” on page 185
Appendix I, “Documentation Updates,” on page 189
Audience
This guide is intended for ZENworks Configuration Management 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 Configuration Management is supported by other documentation (in both PDF and
HTML formats) that you can use to learn about and implement the product. For additional
documentation, see the ZENworks 10 Configuration Management SP3 documentation (http://
www.novell.com/documentation/zcm10/).
Documentation Conventions
In Novell documentation, a greater-than symbol (>) is used to separate actions within a step and
items in a cross-reference path.

10 ZENworks 10 Configuration Management Software Distribution Reference
novdocx (en) 16 April 2010
A trademark symbol (®, TM, etc.) denotes a Novell trademark. An asterisk (*) denotes a third-party
trademark.
When a single pathname can be written with a backslash for some platforms or a forward slash for
other platforms, the pathname is presented with a backslash. Users of platforms that require a
forward slash, such as Linux*, should use forward slashes as required by your software.

Basic Concepts
1
11
novdocx (en) 16 April 2010
1
Basic Concepts
Novell®ZENworks®Configuration Management provides great flexibility in distributing software.
You can distribute applications and individual files, or simply make modifications to existing files
on a device.
The following sections contain additional information that is important as you begin creating and
managing bundles:
Section 1.1, “Bundles,” on page 11
Section 1.2, “Assigning Bundles to Devices vs. Users,” on page 12
Section 1.3, “Packaging Considerations,” on page 12
Section 1.4, “Dependency Bundles,” on page 13
Section 1.5, “Content,” on page 16
1.1 Bundles
Software is distributed through the use of bundles. A bundle consists of all the files, configuration
settings, installation instructions, and so forth required to deploy and manage the application or files
on a device. There are four types of bundles you can create:
Directive Bundle: Performs one or more actions on a device. For example, you can use a
Directive bundle to edit a Windows* INI file or text file. You can run a script, start or stop a
service, or delete a file. In addition, the bundle includes creating various other actions and
personality actions such as Store Personality and Apply Personality actions.
File Bundle: Copies or installs files or directories to a device. For example, you can use a File
bundle to include configuration files or data files. A File bundle is useful to distribute files that
are not part of a Windows bundle.
Imaging Bundle: Performs operations before the operating system boots. The various Imaging
bundle types let you install images on one or more devices, or run ZENworks scripts containing
any commands that you can issue from the imaging bash prompt.
Windows Bundle: Distributes a Microsoft* Windows Installer (MSI) package, Microsoft
Windows Software Patch (MSP) package, thin-client application, or other Windows-based
applications to a Windows device.
The software included with a bundle is uploaded to the ZENworks Server repository. This enables
the ZENworks Server and ZENworks Adaptive Agent to distribute the software without requiring
access to any other network locations.
To create a software bundle, you use the Create New Bundle Wizard in ZENworks Control Center or
by using the zman command line utility. For more information on Creating Bundle using ZENworks
Control Center, see Chapter 2, “Creating Bundles,” on page 19 and for Creating Bundle using zman
command line utility, see “ZENworks Command Line Utilities” in the ZENworks 10 Configuration
Management Command Line Utilities Reference.
The sections in this guide provide conceptual and task-based information to help you effectively
manage software distribution in your ZENworks system. You can also use the online Help system
for information about creating bundles.

12 ZENworks 10 Configuration Management Software Distribution Reference
novdocx (en) 16 April 2010
1.2 Assigning Bundles to Devices vs. Users
You can assign bundles to both users and devices. There are differences between the two assignment
types that you need to be aware of. When you assign a bundle to users, the bundle is available to all
assigned users regardless of the device they log on to. When you assign a bundle to a device, the
bundle is available to all users who log on to the assigned device.
1.3 Packaging Considerations
Because of the way that ZENworks Configuration Management handles bundle packaging, be aware
of the following when you create bundles:
Time Required for Packaging: Creating large MSI and MSP bundles might take several
hours to package before they are available on ZENworks content servers (ZENworks Servers
and Content Distribution Points) in your Management Zone.
Large application files are compressed and encrypted, resulting in smaller bundles that reduce
bandwidth during transmission and provide greater security during transmission and on the
content server. The encrypted bundles cannot be removed from the content server and
inappropriately used.
Space Required for Packaging: Creating bundles that contain content temporarily requires up
to twice the amount of disk space as the original files. The bundle creation process uploads
copies of the original files from the local machine to a temporary directory on the ZENworks
content server. The process then packages those files as encrypted, compressed ZENworks
content files. After the ZENworks content files are created, the original uploaded files are
automatically deleted.
If you are using ZENworks Control Center to create the bundle, and if for some reason you do
not log out correctly (you close your browser before completing the Create New Bundle
Wizard, you browse to somewhere else, or your machine crashes), the temporary directory
mentioned above is automatically cleared after the session time-out is reached (30 minutes, by
default).
In some circumstances (the ZENworks Server goes down during processing, for example), the
bundle creation process is unable to delete these temporary files. You can manually delete these
temporary files, as needed.
Depending on the operating system and the utility used to create the bundle, the temporary files
are located in the following directories:
Table 1-1 Location of Temporary Files for Windows
Utility Used to Create Bundle Location of Temporary Files
ZENworks Control Center zenworks_home\share\tomcat\temp
zman (command line utility) zenworks_home\work\content-repo\tmp
ZENworks Migration Utility zenworks_home\work\collection\datamodel

Basic Concepts 13
novdocx (en) 16 April 2010
Table 1-2 Location of Temporary Files for Linux
1.4 Dependency Bundles
When you create the following actions for a bundle, you create bundle dependencies:
Action - Install Bundle
Action - Launch Bundle
Action - Uninstall Bundle
Action - Verify Bundle
A bundle’s Dependency Bundles tree shows the chaining information of that bundle and the action
sets that each dependency is in. To view the Dependency Bundles tree in ZENworks Control Center,
click the Bundles tab, click a bundle that has dependent bundles, then on the Summary tab, click the
Display Bundle Dependencies link in the Dependency Bundles row. If the selected bundle does not
have dependent bundles, the link displays None instead of Display Bundle Dependencies.
The following sections contain additional information:
Section 1.4.1, “Primary Applications vs. Dependent Applications,” on page 13
Section 1.4.2, “Bundle Chains,” on page 14
Section 1.4.3, “Distributing, Installing, and Launching a Bundle That Has Dependencies,” on
page 15
1.4.1 Primary Applications vs. Dependent Applications
When working with bundle dependencies, the primary bundle is the bundle for which you are
establishing dependencies. The bundles that are defined as dependencies are called the dependent
bundles. The following illustration shows this relationship. Application A as the primary bundle
with Applications B, C, and D as dependent bundles.
Figure 1-1 Dependency Bundle Tree
A primary bundle can have one dependent application or, as shown in the above example, it can
have multiple dependent applications.
Utility Used to Create Bundle Location of Temporary Files
ZENworks Control Center /opt/novell/zenworks/share/tomcat/temp/
zman (command line utility) /var/opt/novell/zenworks/content-repo/tmp/
ZENworks Migration Utility /var/opt/novell/zenworks/collection/datamodel/

14 ZENworks 10 Configuration Management Software Distribution Reference
novdocx (en) 16 April 2010
In addition, a bundle can be both a primary bundle and a dependent bundle, as shown in the
following illustration. Application A as the primary bundle, with Applications B, B1, B2, C, and D
as dependent bundles.
Figure 1-2 Dependency Bundle Tree
In the above example, Application B is one of Application A's dependent bundles. At the same time,
Application B has dependencies on two bundles, Application B1 and Application B2.
1.4.2 Bundle Chains
A bundle chain is two or more bundles linked together by dependencies. In its simplest form, a
application chain consists of two levels, as shown in the following illustration.
Figure 1-3 Dependency Bundle Tree
However, when bundle dependencies are nested, a bundle chain can grow to include many levels. In
the following example, Application A has a dependency on Application B. Application B, in turn,
has dependencies on Application B1 and Application B2. As a result, all three bundles (B, B1, B2),
in addition to applications C and D, must be present in order for Application A to run.
Figure 1-4 Dependency Bundle Tree
In some cases, a bundle might belong to more than one bundle chain, as in the following example
where Application D is a dependent application for both Application A and Application E.

Basic Concepts 15
novdocx (en) 16 April 2010
1.4.3 Distributing, Installing, and Launching a Bundle That Has
Dependencies
When setting up bundle dependencies, you should be aware of the following:
Bundle Assignment: A dependent bundle does not need to be assigned to devices or users. The
primary bundle, however, must be assigned to one or more devices or users for it to function
properly.
Distribution and Installation: If dependent bundles have not already been distributed to or
installed on the user's workstation, when a user launches or installs a bundle, ZENworks Adaptive
Agent distributes and installs them. ZENworks Adaptive Agent distributes a dependent bundle only
once, unless the dependent bundle’s version is updated or the distribution or installation is
unsuccessful. If ZENworks Adaptive Agent is unable to distribute or install a dependent bundle (for
example, the user’s workstation does not meet the dependent bundle’s system requirements), the
primary bundle is not launched or installed.
Distribution Through an Add-On Image: If you distribute a bundle through an image add-on, its
dependent bundles must be included as another image add-on. Otherwise, the distribution of the
primary bundle fails.
Distribution to Disconnected Workstations: For disconnected workstations, the bundles must be
force cached to the workstation before it becomes disconnected. If changes are made to dependent
bundles after the bundles have been cached to workstations, the version number of the primary
bundle must be updated in order to force a re-cache of the bundles.
Launch: Each time a bundle is launched, ZENworks Adaptive Agent performs any launch
operations, such as other actions, defined for its dependent bundles.
Reboot/Shutdown: Ensure that the dependent bundle does not include a Reboot / Shutdown action.
Redeploying a Bundle to Refresh Its Dependencies: If you change the dependencies of a bundle
that has already been replicated to content servers, you must redeploy the bundle. This ensures that
each content server has all of the dependencies required by the bundle.
To redeploy the bundle from the Bundles tab, locate and click the bundle to display its details, then
click the Content Servers tab. In the Primary Server Replication Status list, select the check box next
to the Primary Servers, then click Include to replicate the bundle to the servers. Repeat this
procedure for Satellite devices as necessary.

16 ZENworks 10 Configuration Management Software Distribution Reference
novdocx (en) 16 April 2010
To redeploy the bundle from the Devices tab, locate and click the appropriate device to display its
details, then click the Content tab. In the Replication Settings list, select the check box next to the
bundles, then click Include to replicate the bundle.
The bundle will be redeployed according to your Content Replication settings. For more
information, see “Content Replication” in the ZENworks 10 Configuration Management System
Administration Reference.
1.5 Content
When you create bundles containing content, the content is copied to content servers (ZENworks
Servers or Content Distribution Points), replicated to other content servers, and delivered to
managed devices.
The following sections contain additional information:
Section 1.5.1, “Content Replication,” on page 16
Section 1.5.2, “Content Delivery,” on page 16
1.5.1 Content Replication
Content Replication lets you determine how often content (bundle and policy files) is updated on the
ZENworks (primary) Servers and Content Distribution Points. ZENworks Servers and Content
Distribution Points are collectively referred to as content servers when discussing them in their roles
of hosting content.
When a bundle or policy that contains content is added to the Management Zone, the ZENworks
database is updated to reflect the addition of the content. Content servers are responsible for
periodically reading the ZENworks database to discover new content. Each content server that does
not have the content then retrieves the content from a content server where it resides.
If content has been removed from the Management Zone, each content server also removes the
obsolete content during the periodic update.
For more information, see “Content Replication” in the ZENworks 10 Configuration Management
System Administration Reference.
1.5.2 Content Delivery
Content delivery, or distribution, refers to the process of transferring bundle and policy content from
a content server (ZENworks Server or Content Distribution Point) to a managed device.
There are a variety of settings you can use to determine how content is delivered to managed
devices. You can:
Set up Closest Server rules that determine from which content server a managed device
downloads its content.
Schedule times, referred to as delivery blackout dates, when content cannot be downloaded by
managed devices.
Decide how often you want managed devices to look for new content to download.

Basic Concepts 17
novdocx (en) 16 April 2010
For information about performing these tasks, see “Content Delivery” in the ZENworks 10
Configuration Management System Administration Reference.

18 ZENworks 10 Configuration Management Software Distribution Reference
novdocx (en) 16 April 2010

Creating Bundles
2
19
novdocx (en) 16 April 2010
2
Creating Bundles
A bundle consists of all the files, configuration settings, installation instructions, and so forth
required to deploy and manage the application or files on a device.
Novell®ZENworks®Configuration Management lets you create bundles by using ZENworks
Control Center or by using the zman command line utility.
The following sections contain step-by-step instructions about creating bundles by using ZENworks
Control Center:
Section 2.1, “Creating Directive Bundles,” on page 19
Section 2.2, “Creating File Bundles,” on page 23
Section 2.3, “Creating Imaging Bundles,” on page 31
Section 2.4, “Creating Windows Bundles,” on page 31
The following section explains how to create bundles by using the zman command line utility:
Section 2.5, “Creating Bundles by Using the zman Command Line Utility,” on page 39
2.1 Creating Directive Bundles
A Directive bundle lets you perform one or more actions on one or more devices, regardless of
platform. For example, you can use a Directive bundle to edit a Windows INI file or text file. You
can run a script, start or stop a service, delete a file, and more. In addition, the bundle includes
various other actions and personality actions such as Store Personality and Apply Personality.
You can use ZENworks Control Center or the zman command line utility to create bundles. The
following procedure explains how to create a bundle using ZENworks Control Center. If you prefer
the zman command line utility, see “Bundle Commands” in “ZENworks Command Line Utilities”.
To create a Directive bundle:
1In ZENworks Control Center, click the Bundles tab.
2In the Bundle list, click New, then click Bundle to display the Select Bundle Type page.

20 ZENworks 10 Configuration Management Software Distribution Reference
novdocx (en) 16 April 2010
3Select Directive Bundle, then click Next to display the Select Bundle Category page.
4Select the desired bundle category:
Empty Bundle: A bundle with no initial tasks. This bundle category is useful to quickly create
a bundle without performing all of the tasks in the Create New Bundle Wizard. After you create
the empty bundle, you can edit its details to add assignments, actions, and so forth, at a later
time.
Action Bundle: A bundle with one or more actions.
Apply Personality: A bundle that applies the personality of one or more users on the managed
device from a personality file stored on the local or network path.
Store Personality: A bundle that stores the personality of one or more users on the managed
device to a personality file on the local or network path. The personality files are not uploaded
to the ZENworks content repository.
5Click Next to display the Define Details page, then fill in the fields.
Bundle Name: Provide a name for the bundle. The bundle name must be different than the
name of any other item (bundle, group, folder, and so forth) that resides in the same folder. The
name you provide displays in ZENworks Control Center and the ZENworks Adaptive Agent
(on managed devices).