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

Novell®
www.novell.com
novdocx (en) 16 April 2010
AUTHORIZED DOCUMENTATION
ZENworks 10 Configuration Management Command Line Utilities Reference
ZENworks ® 10 Configuration Management SP3
10.3
March 30, 2010
Command Line Utilities 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 Command Line Utilities Reference
novdocx (en) 16 April 2010

Contents 5
Contents
novdocx (en) 16 April 2010
About This Guide 7
1 ZENworks Command Line Utilities 9
2 Command Line Utilities for Linux Satellites 89
3 ZENworks Diagnostic Center 99
3.1 Downloading and Extracting ZDC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
3.2 Running ZDC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
4 Troubleshooting ZENworks Command Line Utilities 103
5 Guidelines for Working with Zman 105
A Documentation Updates 107
A.1 March 30, 2010: SP3 (10.3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

6ZENworks 10 Configuration Management Command Line Utilities Reference
novdocx (en) 16 April 2010

About This Guide 7
novdocx (en) 16 April 2010
About This Guide
This Novell ZENworks 10 Configuration Management Command Line Utilities Reference includes
information to help you use the following Novell®ZENworks®10 Configuration Management
utilities:
zman(1)
zeninfocollect(1)
zac(1)
The information in this guide is organized as follows:
Chapter 1, “ZENworks Command Line Utilities,” on page 9
Chapter 2, “Command Line Utilities for Linux Satellites,” on page 89
Chapter 3, “ZENworks Diagnostic Center,” on page 99
Chapter 4, “Troubleshooting ZENworks Command Line Utilities,” on page 103
Chapter 5, “Guidelines for Working with Zman,” on page 105
Appendix A, “Documentation Updates,” on page 107
Audience
This guide is intended for 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 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 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.
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.

8ZENworks 10 Configuration Management Command Line Utilities Reference
novdocx (en) 16 April 2010

ZENworks Command Line Utilities
1
9
novdocx (en) 16 April 2010
1
ZENworks Command Line Utilities
The following sections give information on the Novell®ZENworks®10 Configuration Management
command line utilities:
“zman(1)” on page 10
“zeninfocollect(1)” on page 78
“zac(1)” on page 80

10 ZENworks 10 Configuration Management Command Line Utilities Reference
novdocx (en) 16 April 2010
zman(1)
Name
zman - The command line interface to Novell ZENworks 10 Configuration Management, which
provides comprehensive server, workstation, and user management, and to Novell 10 Asset
Management, which provides software and hardware inventory of servers and workstations,
software usage tracking, and software license compliance.
Description
The zman command line interface provides you a full-featured utility that can simplify many
operations by using scripting and can provide quick access to operations. It can be used effectively
in automation of tasks.
The following sections provide information about all of the commands provided for ZENworks 10
Configuration Management and ZENworks 10 Asset Management. Some of the commands apply to
both products, and some apply to only one or the other.
The following commands apply only to ZENworks 10 Configuration Management. If Configuration
Management is not installed or active, the commands have no effect:
Bundle commands
Imaging commands
Policy commands
The following commands apply only to ZENworks 10 Asset Management. If Asset Management is
not installed or active, the commands have no effect:
Asset Management commands
Syntax
zman <command> [-options] [arguments]
In general, zman commands have both a short form and a long form. The long form is assembled in
the form category-action. For example, the command
registration-list lists all registrations in
a registration folder. There are many commands, but most of them are easy to remember because
they are grouped under categories (workstation, server, bundle, policy, administrator, registration,
etc) and most actions (list, create, modify, delete) to perform on them are common.
The abbreviated form of each command uses one letter from each word in the long form. In this
manner,
admin-list is shortened to al . There are some exceptions to this rule to maintain the
uniqueness of the short names. For example,
bc is the short form of bundle-create , and bcp is the
short form of
bundle-copy .
A command takes options and arguments. Options can be specified anywhere in the command.
Arguments are dependent on position.

ZENworks Command Line Utilities 11
novdocx (en) 16 April 2010
Options
Options are of two types: switches and flagged options. Both have a short and long form. The short
form is preceded by a single hyphen and the long form is preceded by two hypens. For example, -n
and --namefilter are the short and long forms of a flagged option used to filter the display of results
by name for the bundle-list command.
Switch: A parameter that does not take any value. Its presence alone conveys the meaning. For
example, specifying the –recursive switch in
bundle-list indicates that the contents of the
subfolders should also be displayed.
Flagged Option: This parameter is used to set a value for an option. The value is given followed by
a space or equals sign after the short or long flag of the option.
Example:
zman bundle-list -namefilter "bundle*" -r
Arguments
Arguments for a command are usually ordered in the same way as the command itself. For example,
for
server-add-bundle , the server is named first and the bundle second.
Guide to Usage
This section contains a guide to general command formatting and conventions.
Administrators
Every action in zman is governed by the access limitations of the administrator. The initial
Administrator account created during the initial installation has rights to all objects. Additional
administrator accounts you create are granted read-only rights by default. These accounts must
be explicitly granted rights to any objects they are to manage.
Help
The zman command line interface provides help at several levels. Pipeline the help through the
operating system's native
more command for scrollable output.
At the highest level, lists all the categories of commands available in zman and the global
options for the commands.
Example:
zman
At the all category level, lists all the commands available in zman organized by categories
(workstation, server, bundle, policy, etc.).
Example:
zman -h
For each category, lists the commands available specific to that category.
Example:
zman policy /?
At each command level, gives usage, detailed help, and examples for a particular
command.
Example:
zman policy-list-help
 -h,--help,?,-?, and /? are the various help options available.

12 ZENworks 10 Configuration Management Command Line Utilities Reference
novdocx (en) 16 April 2010
Folders
If no folder is specified for commands that take a folder argument, the command targets the
root folder. To specify a folder path, list each folder from the root separated by a forward slash
(/). For example, if you have a folder named folder1 in the root, containing a subfolder
named
subfolder1 , you would reference this folder as folder1/subfolder1 . Each specified
folder must already exist.
Mandatory and Optional arguments
Arguments enclosed inside parentheses ( ) are mandatory and those enclosed by square
brackets [ ] are optional.
Ellipsis (...)
An ellipsis indicates that a command accepts multiple entries of the last argument type. The
arguments must be separated by space or commas, depending on the command. For example:
zman server-add-bundle [options] (server) (bundle) [...]
The ellipsis indicates that server-add-bundle can accept multiple bundles. In the command
level help, the multiple entry argument help is given as
[(bundle) (bundle) ...
(bundle)]
for more clarity.
All commands that have multiple entries of the last argument also have the -
f|--folder
option. This option is convenient if all the entries of the argument are under the same folder.
The path of the entries are calculated relative to this folder path. For example:
zman server-add-bundle server1 bundlefolder/bundle1 bundlefolder/bundle2
can also be given as:
zman server-add-bundle server bundle1 bundle2 --folder bundlefolder
Path of the ZENworks Objects
If the argument required is the path of a ZENworks object, the path must be specified relative to
the root folder of that object separated by a forward slash (/), unless it is specified in the
command help to enter the absolute path. For example:
zman server-add-bundle serverfolder/server bundlefolder/bundle1
where the absolute paths of the arguments are:
/devices/servers/serverfolder/server and /bundles/bundlefolder/bundle1
Exporting Objects to a File
You can use the zman commands such as
bundle-export-to-file , policy-export-to-
file
, and settings-export-to-file to export bundles, policies, and settings definitions
respectively to a specified file in the XML format. The file is created with the specified name
and file extension. If the file extension is not specified, the
.xml extension is added by default.
You can use these files to create bundles, policies, and settings.
Asset Management Commands
These commands are used to load purchase record files and refresh the compliance engine. They
apply only to ZENworks 10 Asset Management.

ZENworks Command Line Utilities 13
novdocx (en) 16 April 2010
asset-management-load-purchase-record (amlpr)
Loads a purchase record file. The Purchase Record Loader looks for the purchase record file to
load on the primary server in the folder
ZENWORKS_HOME/temp/PurchaseRecordImport/
uploaded
. If you have not yet used the Purchase Record Loader from ZENworks Control
Center, you need to create this folder.
This command is asynchronous, which means
zman returns immediately and does not wait for
the command to complete. This is because the command may run for a long time. You can
check the status of this process from ZENworks Control Center.
asset-management-refresh-compliance-data (amrcd)
Runs the software compliance engine to refresh the software license compliance data.
This command is asynchronous, which means zman returns immediately and does not wait for
the command to complete. This is because the command may run for a long time. You can
check the status of this process from ZENworks Control Center.
Administrator Commands
These commands are used to create and manage administrator accounts. Administrator commands
begin with
admin- in the long form or the letter a in the short form.
All of the commands below accept the option flags listed in the Global Options section. In addition,
they accept individual options as listed with each command.
admin-clear-credential (acc)
Clears the ZENworks username and password stored by using the
admin-store-credential
command. It is always safer and is a good practice to delete the stored credentials after you are
finished executing the commands.
admin-create (ac) [options] (administrator or user)
Creates a ZENworks administrator account.
(administrator or user) - Name of the administrator or full path of a user in a user source.
Accepts the following options:
-f, --fullname=[full name] - Full name of the ZENworks administrator.
-a, --assign-same-rights - Gives the new administrator the same rights as the administrator who
executes this command.
The command prompts for the password of the administrator, to avoid entering the password in
clear text. If the administrator account is based on a user, it uses the same credentials defined in
the user source so the command does not prompt for the password.
admin-delete (ad) (ZENworks administrator name) [...]
Deletes a ZENworks administrator account.
(ZENworks administrator name) [...] - Name of the ZENworks administrator. The wildcard *
can be used in the object names if it is enclosed in quotation marks. Exercise caution while
using wildcards for deleting objects.
admin-list (al) [options]
Lists all ZENworks administrator accounts.
Accepts the following options:

14 ZENworks 10 Configuration Management Command Line Utilities Reference
novdocx (en) 16 April 2010
-n, --namefilter=[filter string] - Displays results matching the specified name. The wildcards *
and ? can be used if they are enclosed in quotation marks.
-s, --scrollsize=[scrollsize] - Number of results to be displayed at a time.
admin-list-roles (alr) [options] (ZENworks administrator name)
Lists roles assigned to a ZENworks administrator account.
Accepts the following option:
-l, --longnames - Displays names for the rights. By default, the abbreviated form of the rights
name is displayed.
admin-rename (ar) (ZENworks administrator name) (new name)
Renames a ZENworks administrator account.
admin-rights-delete (ard) [options] (ZENworks administrator name) [object
path]
Deletes rights assigned to a ZENworks administrator account.
[object path] [...] - Full path of the ZENworks object, starting with a forward slash (/).
Accepts the following option:
-c, --category=[rights category] - Name of the category within which the rights are grouped. To
see the list of categories, run
zman admin-rights-set --Help | more .
admin-rights-info (ari) [options] (ZENworks administrator name) [object path]
Displays rights assigned to a ZENworks administrator account.
[object path] [...] - Full path of the ZENworks object, starting with a forward slash (/).
Accepts the following options:
-c, --category=[rights category] - Name of the category within which the rights are grouped. To
see the list of categories, run
zman admin-rights-set --Help | more .
-e, --effective - Displays the effective rights of the administrator. Effective rights include rights
inherited from roles assigned to the administrator. If this option is not specified, rights
assigned directly to the administrator are displayed.
-l, --longnames - Displays names for the rights. By default, the abbreviated form of the rights
name is displayed.
admin-rights-set (ars) [options] [ZENworks administrator name] [rights
category] [object path] [...]
Allows or denies rights for a ZENworks administrator account.
[rights category] - Name of the category under which the rights are grouped. To see the list of
categories, run
zman admin-rights-set --Help | more .
[object path] [...] - Full path of the ZENworks object, starting with forward slash (/), on which
the rights should be enforced. To view the root folders of the allowed object types for which
rights can be assigned within each rights category, run
zman admin-rights-modify --Help
| more
.
Accepts the following options:

ZENworks Command Line Utilities 15
novdocx (en) 16 April 2010
-a, --allow=[right ][...] - A comma-separated list of long or short names of the rights to be
allowed. To view the rights for each category, run
zman admin-rights-set --Help |
more
.
-A, --allow-all - Allows all rights of the Rights category.
-d, --deny=[right ][...] - A comma-separated list of long or short names of the rights to be
denied. To view the rights of each category, run
zman admin-rights-set --Help |
more
.
-D, --deny-all - Denies all rights of the Rights category.
-f, --folder=[folder name] - Full path of a folder. If specified, the path of the objects is
determined relative to this folder. This can be used to specify multiple objects under the same
folder.
-H, --Help - Displays detailed help about the categories of rights available, and the long and
short form of rights names within each category. If a category name is specified, help is
provided for that category.
admin-store-credential (asc) (ZENworks administrator name)
Stores the ZENworks username and password for use with every command so credentials need
not be entered for every command. The credentials are stored on the home directory of the
logged-in user and are used only for that logged-in user. In Linux, ensure that the user has a
home directory. If you share the same machine login with other ZENworks administrators, you
must clear your credentials by using the
admin-clear-credential command after you are
finished executing commands.
Batch Command
The batch command is a utility command used to execute a list of zman commands from a text file.
The commands are executed faster because logging into ZENworks is done only once and not for
every command. Batch commands begin with
batch- in the long form, or with the letter b in the
short form.
This command accepts the option flags listed in the Global Options section. In addition, it accepts
individual options as listed with the command.
batch-execute (bex) [options] (file path) [...]
Executes zman commands from text files in a batch (not to be confused with Windows batch
files).
(file path) [...] - The path of the text files containing zman commands to be executed. Lines
starting with
# , rem , REM , ; and // are considered as comments, and are not processed. For a
sample file, refer to
BatchExecuteCommands.txt located in /opt/novell/zenworks/
share/zman/samples/batch
on a Linux server or
Installation_path:\Novell\Zenworks\share\zman\samples\batch on a Windows
server.
Accepts the following option:
-e, --exit-on-failure - Stops executing the commands and exits if a command fails partially or
totally. A command is said to partially fail for commands that take multiple arguments when
the processing of one or more of the arguments was not successful. For example, for
bundle-delete , the command is said to partially fail if one of the arguments could not be
found or deleted. By default, the commands in the file are executed continuously without
checking for failure.

16 ZENworks 10 Configuration Management Command Line Utilities Reference
novdocx (en) 16 April 2010
Bundle Commands
These commands are used to create, modify and manage bundles. Bundle commands begin with
bundle- in the long form, or with the letter b in the short form.
All of the commands below accept the option flags listed in the Global Options section. In addition,
they accept individual options as listed with each command. These commands apply only to
ZENworks 10 Configuration Management.
bundle-add-actions (baa) [options] (bundle path) (action XML file) [...]
Adds actions to a bundle.
(action XML file) [...] - The XML files that contain information for actions to be added. The
actions are grouped under one of these action sets: Install, Launch, Verify, Uninstall, Terminate,
Preboot. The XML file contains an
ActionSet element that contains information of actions to
be added for an action set. Multiple XML files can be given as input to add actions to different
action sets of the bundle. The XML files can be created by exporting actions of an existing
bundle using the
bundle-export-actions command.
Accepts the following option:
-a, --actioninfo=[content and dependency for actions] - XML file containing content and
bundle dependency information for actions that have file content or dependency on another
bundle. For example, for Install MSI Action , the MSI file to be installed is the file
content.
Install Bundle Action takes another bundle as dependency so this data also
needs to be specified for proper functioning of these actions. For the XML format template,
refer to
ActionInfo.xml located in /opt/novell/zenworks/share/zman/samples/
bundles
on a Linux server or
Installation_directory:\Novell\Zenworks\share\zman\samples\
bundles
on a Windows server.
bundle-assign (ba) [options] (device or user type) (bundle or bundle group)
(device or user object path) [...]
Assigns a bundle or bundle group to one or more device or user objects.
(device or user type) - Valid values are device , server , workstation , and user .
(device or user object path) [...] - The path of the device or user objects relative to the root
folder of the device or user type specified.
Accepts the following options:
-f, --folder=[bundle folder] - The path of a bundle folder relative to
/Bundles . If this option is
specified, the path of the bundle objects is determined relative to this folder. This can be used
to specify multiple bundle objects under the same folder.
-I, --icon-location=[application location XML file] - XML file that contains the locations to
place the icon for the bundle application. For the XML file format, refer to
IconLocation.xml located in /opt/novell/zenworks/share/zman/samples/bundles
on a Linux server or
Installation_directory:\Novell\Zenworks\share\zman\samples\
bundles
on a Windows server.
-d, --distribution-schedule=[distribution schedule XML file] - XML file that contains the
distribution schedule.
-l, --launch-schedule=[launch schedule XML file] - XML file that contains the launch
schedule.

ZENworks Command Line Utilities 17
novdocx (en) 16 April 2010
-a, --availability-schedule=[availability schedule XML file] - XML file that contains the
availability schedule. For the schedule XML file templates, refer to the XML files located in
/opt/novell/zenworks/share/zman/samples/schedules on a Linux server or
Installation_directory:\Novell\Zenworks\share\zman\samples\
schedules
on a Windows server.
-i, --install-immediately - Installs the bundle immediately after distribution.
To use this option, you must also specify the Distribution schedule. The Distribution schedule
can be specified by using the --distribution-schedule, --distribute-now, or --distribute-on-
device-refresh option.
-L, --launch-immediately - Launches the bundle immediately after installation.
To use this option, you must also specify the Distribution schedule. The Distribution schedule
can be specified by using the --distribution-schedule, --distribute-now, or --distribute-on-
device-refresh option.
-n, --distribute-now - Sets the distribution schedule to distribute the bundle immediately. If this
option is specified, the --distribution-schedule and --distribute-on-device-refresh options are
ignored. The --distribute-now, --distribute-on-device-refresh, and --distribution-schedule
options are mutually exclusive and are used to set the distribution schedule. The --distribute-
now option is considered first, followed by --distribute-on-device-refresh and --distribution-
schedule.
-r, --distribute-on-device-refresh - Sets the distribution schedule to distribute the bundle on
device refresh. If this option is specified, the --distribution-schedule option is ignored.
-s, --launch-on-device-refresh - Sets the launch schedule to launch the bundle on device
refresh. If this option is specified, the --launch-schedule option is ignored.
-w, --wakeup-device-on-distribution - Wakes up the device by using Wake-On-LAN if it is shut
down while distributing the bundle.
To use this option, you must also specify the Distribution schedule. The Distribution schedule
can be specified by using the --distribution-schedule, --distribute-now, or --distribute-on-
device-refresh option.
-B, --broadcast=[Broadcast address][...] - A comma-separated list of addresses used to
broadcast the Wake-On-LAN magic packets. This option is used only if you choose to wake
up the device by using Wake-On-LAN. A valid IP address is a valid value.
-S, --server=[Path of the Primary or Proxy Server objects relative to
/Devices][...] - A
comma-separated list of Primary or Proxy Server objects used to wake up the device. This
option is used only if you choose to wake up the device by using Wake-On-LAN.
-C, --retries=[Number of retries] - Number of times the Wake-On-LAN magic packets are sent
to the device(s). This option is used only if you choose to wake up the device by using
Wake-On-LAN. The value must be between 0 and 5. The default value is 1.
-T, --timeout=[Time interval between retries] - The time interval between two retries. This
option is used only if you choose to wake up the device by using Wake-On-LAN. The value
must be between 2 and 10 (in minutes). The default value is 2.
bundle-copy (bcp) [options] (bundle path) (bundle name) [parent folder]
Copies a bundle.
Accepts the following options:
-d, --desc=[description] - Description for the bundle.
-i, --icon-file=[bundle icon file] - The path of the image file containing the image that should be
used as the bundle icon. If this option is not specified, the contents of the subfolders are not
listed.

18 ZENworks 10 Configuration Management Command Line Utilities Reference
novdocx (en) 16 April 2010
bundle-create (bc) [options] (bundle name) (bundle XML file) [parent folder]
Creates a new bundle.
(bundle XML file) - XML file containing exported bundle information. Use bundle-export-
to-file (betf
) to export a existing bundle's information into an XML file. If you want to
reuse files, template XML files can be created from bundles that were created through
ZENworks Control Center. For a sample XML file, refer to
WindowsMSIBundle.xml located
in
/opt/novell/zenworks/share/zman/samples/bundles on a Linux server or
Installation_directory:\Novell\Zenworks\share\zman\samples\bundles on a
Windows server.
Accepts the following options:
-d, --desc=[description] - Description for the bundle.
-a, --actioninfo=[content and dependency for actions] - XML file containing content and
bundle dependency information for actions that have file content or dependency on another
bundle. For example, for
Install MSI Action , the MSI file to be installed is the file
content.
Install Bundle Action takes another bundle as a dependency. This data also
needs to be specified for proper functioning of these actions. For the XML format template,
refer to
ActionInfo.xml located in /opt/novell/zenworks/share/zman/samples/
bundles
on a Linux server or
Installation_directory:\Novell\Zenworks\share\zman\samples\
bundles
on a Windows server.
-i, --icon-file=[bundle icon file] - The path of the image file containing the image that should be
used as the bundle icon.
bundle-delete (bd) [options] (bundle object path) [...]
Deletes one or more bundle objects.
(bundle object path) [...] - The path of the bundle objects (bundle, bundle folder or bundle
group) relative to
/Bundles . The wildcard * can be used in the object names if it is enclosed in
quotation marks. Exercise caution while using wildcards for deleting objects.
Accepts the following options:
-r, --recursive - Deletes objects inside a folder recursively.
-f, --folder=[bundle folder] - The path of a bundle folder relative to
/Bundles . If this option is
specified, the path of the bundle objects is determined relative to this folder. This can be used
to specify multiple bundle objects under the same folder.
bundle-disable (bdl) [options] (bundle path) [...]
Disables bundles.
Accepts the following option:
-f, --folder=[bundle folder] - The path of a bundle folder relative to
/Bundles . If this option is
specified, the path of the bundle objects is determined relative to this folder. This can be used
to specify multiple bundle objects under the same folder.
bundle-enable (bel) [options] (bundle path) [...]
Enables bundles.

ZENworks Command Line Utilities 19
novdocx (en) 16 April 2010
Accepts the following option:
-f, --folder=[bundle folder] - The path of a bundle folder relative to /Bundles . If this option is
specified, the path of the bundle objects is determined relative to this folder. This can be used
to specify multiple bundle objects under the same folder.
bundle-export-actions (bea) (bundle path) (XML file path) (action set type)
[action's positions] [...]
Exports the actions added to a bundle's action set to a file. The file can be used as input to the
bundle-add-actions command.
(action set type) - The type of the action set. If this option is specified, the actions for only this
action set are listed. Valid values are
Install , Launch , Verify , Uninstall , Terminate , and
Preboot .
[action's positions] [...] - A comma-separated list of position of actions in the action set. The
first action is at position 1. Use the
bundle-list-actions command to see the position of a
particular action in an action set. This is optional, but if it is not specified, all the actions in the
specified action set are exported.
bundle-export-to-file (betf) (bundle path) (XML file path)
Exports a bundle's information (in XML format) to a file. The XML file is to be used as input
for creating bundles.
bundle-folder-create (bfc) [options] (folder name) [parent folder]
Creates a new folder for containing bundles.
Accepts the following option:
--desc=[description] - Description for the folder.
bundle-group-add (bga) [options] (bundle group path) (bundle path) [...]
Adds bundles to a bundle group.
Accepts the following option:
-f, --folder=[bundle folder] - The path of a bundle folder relative to /Bundles . If this option is
specified, the path of the bundle objects is determined relative to this folder. This can be used
to specify multiple bundle objects under the same folder.
bundle-group-create (bgc) [options] (group name) [parent folder]
Creates a bundle group and adds members to it.
Accepts the following options:
--desc=[description] - Description for the group.
-m, --members=[bundle path][...] - The path of the bundles relative to
/Bundles .
-f, --folder=[bundle folder] - The path of a bundle folder relative to
/Bundles . If this option is
specified, the path of the bundle objects is determined relative to this folder. This can be used
to specify multiple bundle objects under the same folder.
bundle-group-members (bgm) [options] (bundle group path)
Lists members of a bundle group.

20 ZENworks 10 Configuration Management Command Line Utilities Reference
novdocx (en) 16 April 2010
Accepts the following option:
-s, --scrollsize=[scrollsize] - Number of results to be displayed at a time.
bundle-group-remove (bgr) [options] (bundle group path) (bundle path) [...]
Removes bundles from a bundle group.
Accepts the following option:
-f, --folder=[bundle folder] - The path of a bundle folder relative to /Bundles . If this option is
specified, the path of the bundle objects is determined relative to this folder. This can be used
to specify multiple bundle objects under the same folder.
bundle-increment-version (biv) [options] (bundle path) [...]
Increments the version of bundles.
Accepts the following option:
-f, --folder=[bundle folder] - The path of a bundle folder relative to /Bundles . If this option is
specified, the path of the bundle objects is determined relative to this folder. This can be used
to specify multiple bundle objects under the same folder.
bundle-list (bl) [options] [folder]
Lists bundles objects.
Accepts the following options:
-r, --recursive - Lists results recursively including subfolders. If this option is not specified, the
contents of the subfolders are not listed.
-n, --namefilter=[filter string] - Displays results matching the specified name. The wildcards *
and ? can be used if they are enclosed in quotation marks.
-c, --count - Displays the count of the results.
-s, --scrollsize=[scrollsize] - Number of results to be displayed at a time.
bundle-list-actions (bla) (bundle path) [action set type]
Lists actions added to a bundle.
[action set type] - The type of the action set. If this option is specified, the actions for only this
action set are listed. Valid values are
Install , Launch , Verify , Uninstall , Terminate , and
Preboot .
bundle-list-assignments (blas) [options] (bundle or bundle group)
Lists the device and user assignments for a bundle.
Accepts the following options:
-t, --typefilter=[assignment type] - Filters on the assignment type. Valid values are
device and
user .
-s, --scrollsize=[scrollsize] - Number of results to be displayed at a time.
bundle-move (bmv) (bundle object path) [destination folder path]
Moves a bundle object to a different folder.
bundle-remove-actions (bra) (bundle path) (action set type) [action's
positions] [...]
Removes actions from a bundle.