Novell ZENworks 7.2 Linux Management Administration Guide
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.
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 online documentation for this and other Novell products, and to get
updates, see the Novell Documentation Web page (http://www.novell.com/documentation/index.html).
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.
novdocx (en) 11 July 2008
novdocx (en) 11 July 2008
Contents
About This Guide19
Part I Understanding ZENworks Linux Management21
1 A Quick Tutorial on Basic ZENworks Linux Management Features23
18Novell ZENworks 7.2 Linux Management Administration Guide
About This Guide
novdocx (en) 11 July 2008
This ZENworks 7.2 Linux Management Administration Guide includes conceptual and task-based
®
information to help you configure and maintain your ZENworks
system. The guide is organized as
follows:
Part I, “Understanding ZENworks Linux Management,” on page 21
Part II, “ZENworks System Management,” on page 39
Part III, “Device Registration,” on page 95
Part IV, “Policy Management,” on page 117
Part V, “Package and Content Management,” on page 201
Part VI, “Preboot Services,” on page 315
Part VII, “Hardware and Software Inventory,” on page 469
Part VIII, “Remote Management,” on page 483
Part IX, “Event Monitoring,” on page 497
Part X, “Reports,” on page 519
Part XI, “Appendixes,” on page 531
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 Novell Documentation Feedback site (http://www.novell.com/
documentation/feedback.html) and enter your comments there.
Documentation Updates
For the most recent, updated version of the ZENworks 7.2 Linux Management Administration Guide,
®
visit the Novell
ZENworks 7.2 Linux Management Edition documentation Web site (http://
www.novell.com/documentation/zlm72).
Additional Documentation
ZENworks 7.2 Linux Management is supported by other documentation (in both PDF and HTML
formats) that you can use to learn about and implement the product:
Novell ZENworks 7.2 Linux Management Installation Guide
Novell ZENworks 7.2 Linux Management Troubleshooting Guide
In addition, the other capabilities included in the ZENworks 7 suite have extensive documentation
for your use. For a full list of this documentation, see the Novell ZENworks 7 Linux Management
documentation Web site (http://www.novell.com/documentation/zlm7_dell).
About This Guide19
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* or UNIX*, should use forward slashes as required by your software.
novdocx (en) 11 July 2008
20Novell ZENworks 7.2 Linux Management Administration Guide
I
Understanding ZENworks Linux
Management
Novell® ZENworks® Linux Management is the first fully integrated Linux systems management
solution for Linux servers and workstations. ZENworks Linux Management also lets you manage
Dell PowerEdge servers by using ZENworks Linux Management capabilities combined with the
Dell OpenManage* toolkit capabilities. Whether you use SUSE
Hat* Enterprise Linux on your PowerEdge servers, you can deploy and maintain hardware,
operating systems, and applications from a single administrative console—the ZENworks Control
Center.
The following sections provide information about Novell ZENworks Linux Management:
Chapter 1, “A Quick Tutorial on Basic ZENworks Linux Management Features,” on page 23
Chapter 2, “Using ZENworks Linux Management with Dell PowerEdge Servers,” on page 35
®
Linux Enterprise Server or Red
novdocx (en) 11 July 2008
Understanding ZENworks Linux ManagementI21
novdocx (en) 11 July 2008
22Novell ZENworks 7.2 Linux Management Administration Guide
1
A Quick Tutorial on Basic
novdocx (en) 11 July 2008
ZENworks Linux Management
Features
Novell® ZENworks® Linux Management is designed to let you efficiently manage a large number
of Linux devices (servers and workstations) with as little configuration effort as possible.
To help you get started managing with ZENworks, this tutorial provides a brief overview of the
major tasks you can perform. The first three sections help you set up a management structure based
on best practices, and register devices in your system. You should review these three sections first,
in the order presented:
Section 1.1, “Organizing Devices: Folders and Groups,” on page 23
Section 1.2, “Creating Registration Keys and Rules,” on page 25
Section 1.3, “Setting Up ZENworks Administrator Accounts,” on page 26
The remaining sections provide concepts you should be familiar with to successfully manage your
devices. You can work on these sections in any order you'd like.
Section 1.4, “Delivering Software Packages,” on page 27
Section 1.5, “Delivering Content Using File Bundles,” on page 28
1
Section 1.6, “Defining and Locking Down Device Configuration Settings,” on page 29
Section 1.7, “Using Preboot Services,” on page 30
Section 1.8, “Collecting Software and Hardware Inventory,” on page 30
Section 1.9, “Managing Remote Devices,” on page 31
Section 1.10, “Monitoring Events,” on page 31
Section 1.11, “Generating Reports,” on page 33
1.1 Organizing Devices: Folders and Groups
Using the ZENworks Control Center, you can manage devices by configuring settings and
assignments directly on the device objects. However, this approach is not very efficient unless you
have only a few devices to manage. To optimize management of a large number of devices,
ZENworks lets you organize devices into folders and groups.
You can create folders and groups at any time. However, the best practice is to create the folders and
groups you need before you register devices in your ZENworks Management Zone. This is because
you can set up registration keys and rules that automatically add devices to the appropriate folders
and groups when they register (see Section 1.2, “Creating Registration Keys and Rules,” on
page 25).
The following sections explain folders and groups and how to create them:
Section 1.1.1, “Folders,” on page 24
A Quick Tutorial on Basic ZENworks Linux Management Features
23
Section 1.1.2, “Groups,” on page 24
Section 1.1.3, “Folders vs. Groups,” on page 25
1.1.1 Folders
Your ZENworks Management Zone includes two default folders for devices: Servers and
Workstations. You can create additional folders within each of these folders to further organize
devices.
Folders let you control which ZENworks system configuration settings are applied to which devices,
including how often a device refreshes its information from the ZENworks Object Store, what
information a device includes in its log files, and whether or not a device can be managed remotely.
You can define the configuration settings at the ZENworks Management Zone, on folders, or on
individual devices. Because configuration settings can be defined on folders, you can place similar
devices in the same folder and then define the configuration settings on the folder. All devices in the
folder inherit the folder configuration settings, which override any settings made at the Management
Zone level.
®
For example, assume that you have 30 SUSE
Red Hat Enterprise Linux servers. You want to apply different system configuration settings to the
two types of servers, so you create two folders (/Servers/SUSE and /Servers/RedHat) and
place the appropriate servers in each folder. Because you have more SUSE servers than Red Hat
servers, you configure the settings at the Management Zone level to accommodate the SUSE
servers. Then, you configure the settings on the /Servers/RedHat folder to accommodate the
Red Hat servers and override the settings on the Management Zone.
Linux Enterprise Servers in your environment and 10
novdocx (en) 11 July 2008
To create a folder:
1 In the ZENworks Control Center, click the Devices tab.
2 If you want to create a folder for servers, click the Servers folder.
or
If you want to create a folder for workstations, click the Workstations folder.
3 Click New > Folder to display the New Folder dialog box.
4 Type the name of the new folder, then click OK.
For more information, see Appendix C, “Naming Conventions in the ZENworks Control
Center,” on page 589.
1.1.2 Groups
A group is a collection of devices that share similar requirements. The devices might require the
same software packages, the same operating system or application configuration settings, or the
same inventory collection schedule.
For example, of the 30 SUSE and 10 Red Hat servers mentioned in the Folders section, 10 SUSE
servers and 5 Red Hat servers might be dedicated to the Accounting department. As such, they all
require the same accounting software. Because groups can be assigned software packages, you
could create an Accounting group, add the 15 servers to the group, and then assign the appropriate
accounting software packages to the group.
24Novell ZENworks 7.2 Linux Management Administration Guide
The advantage to making an assignment to a group is that all devices contained in that group receive
the assignment, yet you only need to make the assignment one time. In addition, a device can belong
to any number of unique groups, and the assignments and associations from multiple groups are
additive. For example, if you assign a device to group A and B, it inherits the software packages
assigned to both groups.
To create a group:
1 In the ZENworks Control Center, click the Devices tab.
2 If you want to create a group for servers, click the Servers folder.
or
If you want to create a group for workstations, click the Workstations folder.
3 Click New > Server Group (or New > Workstation Group for workstations) to launch the Create
New Group Wizard.
4 Follow the prompts to create the group and add devices to it. For information about what you
need to supply at each step of the wizard, click the icon.
1.1.3 Folders vs. Groups
novdocx (en) 11 July 2008
As a general rule, you should manage system configuration settings through folders, and manage
assignments (software packages, policies, etc.) through groups. This allows you to efficiently
manage devices with similar configuration settings by placing them in the same folder and defining
the configuration settings on the folder. However, all devices in the folder might not have the same
software package or policy requirements. Therefore, you can organize the devices into groups and
assign the appropriate bundles and policies to each group.
The most successful management strategy uses both folders and groups to create a hierarchy and
organization that is easy to manage. A good folder organization enables you to import devices into a
folder so they automatically inherit the correct system configuration settings. A good group
organization makes it easy to assign bundles and policies to devices.
1.2 Creating Registration Keys and Rules
You can manually add devices to folders and groups, but this can be a burdensome task if you have a
large number of devices or if you are consistently registering new devices. The best way to manage
a large number of devices is to have them automatically added to the correct folders and groups
when they register. To accomplish this, you can use registration keys, registration rules, or both.
Both registration keys and registration rules let you assign a name, folder, and group memberships to
a device. However, there are differences between keys and rules that you should be aware of before
choosing whether you want to use one or both methods for registration.
Registration Keys: A registration key is an alphanumeric string that you manually define or
randomly generate. During installation of the ZENworks Agent on a device, the registration
key must be input manually or through a response file (see “Automating Installation of the
ZENworks Agent” in the Novell ZENworks 7.2 Linux Management Installation Guide). When
A Quick Tutorial on Basic ZENworks Linux Management Features25
the device connects to a ZENworks Server for the first time, the device is given a name
according to the defined naming scheme and then added to the folder and groups defined within
the key.
You can create one or more registration keys to ensure that servers and workstations are placed
in the desired folders and groups. For example, you might want to ensure that all of the Sales
department's devices are added to the /Workstations/Sales folder but are divided into
three different groups (SalesTeam1, SalesTeam2, SalesTeam3) depending on their team
assignments. You could create three different registration keys and configure each one to add
the Sales workstations to the /Workstations/Sales folder and the appropriate team
group. As long as each device uses the correct registration key, it is added to the appropriate
folder and group.
Registration Rules: If you don’t want to enter a registration key during installation, or if you
want devices to be automatically added to different folders and groups based on predefined
criteria (for example, operating system type, CPU, or IP address), you can use registration
rules.
ZENworks includes a default registration rule for servers and another one for workstations. If a
device registers without a key, the default registration rules are applied to determine the folder
and group assignments. The two default rules cause all servers to be added to the /Servers
folder and all workstations to the /Workstations folder. The device hostname is used for
its name. You cannot delete these two default rules, but you can modify the naming scheme and
the folder and groups to which the servers and workstations are added.
The two default rules are designed to ensure that no server or workstation registration fails. You
can define additional rules that enable you to filter devices as they register and add them to
different folders and groups. If, as recommended in Section 1.1.3, “Folders vs. Groups,” on
page 25, you’ve established folders for devices with similar configuration settings and groups
for devices with similar assignments, newly registered devices automatically receive the
appropriate configuration settings and assignments.
novdocx (en) 11 July 2008
To create registration keys or rules:
1 In the ZENworks Control Center, click the Configuration tab.
2 To create a new registration key, in the Registration Keys section, click New > Registration to
start the Create New Registration Key Wizard.
or
To create a new registration rule, in the Default Registration Rules section, click New to start
the Create New Default Rule Wizard.
3 Follow the prompts to create the key or rule. For information about what you need to supply at
each step of the wizard, click the icon.
For more detailed information about registering devices, see Part III, “Device Registration,” on
page 95.
1.3 Setting Up ZENworks Administrator
Accounts
During installation, a default Administrator account is created. This account provides rights to
administer all of your ZENworks system.
26Novell ZENworks 7.2 Linux Management Administration Guide
You can create additional administrator accounts that provide full access to your ZENworks system.
You can also create accounts that limit administrative rights to specific folders (device folders,
policy folders, bundle folders, and report folders).
To limit administrator rights, you assign an account rights at the folder level. The root folders are /Bundles, /Devices, /Policies, and /Reports. Rights assigned at a root folder are
effective in all subfolders (for example, /Bundles/Workstations) unless specifically
overridden at the subfolder level.
Depending on the administrative functions you want an administrator to be able to perform, you can
give an account one of the following levels of rights:
All: Provides create, delete, and modify rights to all objects within the folder.
Modify: Provides rights to edit existing objects only.
View: Provides rights to view object information.
For example, if you want an administrator to be able to view bundles that are located in the /
Bundles folder and create, delete, or modify bundles in the /Bundles/Workstations folder, you would assign the administrator View rights to the /Bundles folder and All rights to the /
Bundles/Workstation folder.
novdocx (en) 11 July 2008
To create an administrator account:
1 In the ZENworks Control Center, click the Configuration tab.
2 In the Administrators list, click New to display the Add New Administrator dialog box.
3 Provide a username and password for the account, then click OK to add the account to the
Administrators list.
The administrator can change the password the first time he or she logs in by clicking the key
icon located next to the Logout link in the upper right corner of the ZENworks Control Center.
The newly created administrator account is granted View rights to all objects in the
Management Zone. To grant additional rights, or to limit the administrator’s rights to specific
folders only, you need to modify the rights.
4 In the Administrators list, click the administrator account to display the account details.
5 Modify the assigned rights. For information about the options on the page, click Help or see
Chapter 8, “ZENworks Administrator Accounts,” on page 79.
6 When you are finished modifying the rights, click Apply to save the changes.
1.4 Delivering Software Packages
Software packages are delivered to devices through the use of RPM bundles and catalogs.
An RPM bundle is a grouping of one or more software packages. Bundles contain one or more files
that are installed to particular locations on a device, plus information about the bundle, such as
version, description, what applications must also be present for it to be installed, and more. A
catalog is a group of bundles.
The fundamental difference between RPM bundles and catalogs is that the software in bundles is
automatically installed, but users can choose whether or not to install the software included in
catalogs. Catalogs are displayed in the ZENworks Linux Management Updater Client, which is part
of the ZENworks Agent. For more information, see Section 6.3, “Using the Software Updater,
Installer, and Remover from Users’ Managed Devices,” on page 54.
A Quick Tutorial on Basic ZENworks Linux Management Features27
You can define both the deployment schedule and the installation schedule for a bundle. The
deployment schedule determines when the bundle's software packages are copied to the device. The
installation schedule determines when the packages are installed on the device.
You can also create bundle groups. A bundle group is simply a group of bundles, similar to a
catalog. However, installation of bundles in groups is automatic, just like installation of individual
bundles.
The following sections contain additional information:
Section 1.4.1, “Bundles,” on page 28
Section 1.4.2, “Catalogs,” on page 28
1.4.1 Bundles
To create a bundle:
1 In the ZENworks Control Center, click the Bundles tab.
2 In the Bundle list, click New > Bundle to display the Create New Bundle Wizard.
3 Select RPM Package Bundle (the default option), then click Next.
4 Follow the prompts to create the bundle and assign it to devices. For information about what
you need to supply at each step of the wizard, click the icon.
When assigning the bundle to devices, you can lessen your management overhead by assigning
the bundle to groups of devices rather than to individual devices. For more information about
device groups, see Section 1.1, “Organizing Devices: Folders and Groups,” on page 23.
novdocx (en) 11 July 2008
For more detailed information about using bundles and bundle groups to deliver software to devices,
see Chapter 20, “Using RPM and File Bundles,” on page 211.
1.4.2 Catalogs
To create a catalog:
1 In the ZENworks Control Center, click the Bundles tab.
2 In the Bundle list, click New > Catalog to display the Create New Catalog Wizard.
3 Follow the prompts to create the catalog, add bundles to it, and assign it to devices. For
information about what you need to supply at each step of the wizard, click the icon.
When assigning the catalog to devices, you can lessen your management overhead by assigning
the catalog to groups of devices rather than to individual devices. For more information about
device groups, see Section 1.1, “Organizing Devices: Folders and Groups,” on page 23.
For more detailed information about delivering software to devices, see Chapter 22, “Using
Catalogs,” on page 265.
1.5 Delivering Content Using File Bundles
A File bundle lets you create a bundle and distribute compressed files of the type tar.gz and
tar.bz2. For example, you can include configuration files or data files in file bundles.
28Novell ZENworks 7.2 Linux Management Administration Guide
To create a File bundle:
1 In the ZENworks Control Center, click the Bundles tab.
2 In the Bundle list, click New > Bundle to display the Create New Bundle Wizard.
3 Select File bundle, then click Next.
4 Follow the prompts to create the File bundle and assign it to devices. For information about
what you need to supply at each step of the wizard, click the icon.
When assigning the bundle to devices, you can lessen your management overhead by assigning
the bundle to groups of devices rather than to individual devices. For more information about
device groups, see Section 1.1, “Organizing Devices: Folders and Groups,” on page 23.
For more detailed information about using bundles and bundle groups to deliver software to devices,
see Chapter 20, “Using RPM and File Bundles,” on page 211.
1.6 Defining and Locking Down Device
Configuration Settings
Through the use of policies, you can control and lock down the configuration settings for the
following applications:
novdocx (en) 11 July 2008
Epiphany Web browser
Evolution
Mozilla Firefox Web browser
GNOME*
Novell Linux Desktop
SUSE Linux Enterprise Desktop
Additionally, you can create policies that run applications on a device, or perform modifications to a
text-based configuration file using regular expressions.
You can apply individual policies to devices. You can also add policies to policy groups and apply
the policy groups to devices.
Some policies are singular, meaning that only one instance of the policy can apply to the device.
Other policies are plural, meaning that multiple instances can apply. Because a device inherits policy
assignments from any groups or folders in which it is a member, conflicting assignments can occur.
In this case, ZENworks determines the effective policies by first applying any device-assigned
policies, then any group-assigned policies, and then any folder-assigned policies.
You can define the schedule for policies. The schedule determines when a policy is applied to a
device.
To create a policy:
TM
e-mail client
1 In the ZENworks Control Center, click the Policies tab.
2 In the Policies list, click New > Policy to display the Create New Policy Wizard.
3 Follow the prompts to create the policy and assign it to devices. For information about what
you need to supply at each step of the wizard, click the icon.
A Quick Tutorial on Basic ZENworks Linux Management Features29
When assigning the policy to devices, you can lessen your management overhead by assigning
the policy to groups of devices rather than to individual devices. For more information about
device groups, see Section 1.1, “Organizing Devices: Folders and Groups,” on page 23.
For more detailed information about using policies and policy groups to control and lock down
device settings, see Part IV, “Policy Management,” on page 117.
1.7 Using Preboot Services
Preboot Services allows you to automatically or manually do any of the following to a device when
it boots up:
Configure the BIOS, BMC, RAID, and DRAC settings for Dell PowerEdge servers using a
Dell Configuration bundle.
Run scripted installations on the device, such as AutoYaST and kickstart
Run ZENworks scripts on the device
Make an image of the device's hard drives and other storage devices
Restore an image to the device
Apply an existing image to multiple devices
novdocx (en) 11 July 2008
To accomplish these tasks automatically through the ZENworks Control Center, you need to have
PXE (Preboot Execution Environment) enabled on your devices, and have prebootable tasks
configured and assigned to the devices. Then, the devices can automatically implement these tasks
when they boot. For instructions, see Part VI, “Preboot Services,” on page 315.
1.8 Collecting Software and Hardware Inventory
Hardware and software inventory is automatically collected from each device. The hardware
inventory includes details such as operating system, RAM, BIOS version, network adaptors, CDROM manufacturer, and a host of additional information. The software inventory includes a
complete list of all installed packages, as well as all ZENworks-install bundles.
To view a device's hardware and software inventory:
1 In the ZENworks Control Center, click the Devices tab.
2 Click the Servers or Workstations folder to open it.
3 Click a device to display the device's Summary page.
4 Click the Inventory tab.
You can also roll up device inventory to a ZENworks 7 inventory database. For more information
about collecting software and hardware inventory, see Part VII, “Hardware and Software Inventory,”
on page 469.
30Novell ZENworks 7.2 Linux Management Administration Guide
Loading...
+ 644 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.