Novell ZENWORKS 7.2 LINUX MANAGEMENT - SCENARIOS 1... User manual

www.novell.com
Scenarios - 1
Novell®
ZENworks®7.2 Linux Management
March 30, 2007

p. 2
NOVELL ZENWORKS 7.2 LINUX MANAGEMENT
Novell® ZENworks® Linux Management makes it easy to embrace and extend
Linux* within your existing environment. It is the only solution that uses policy-driven
automation to deploy, manage, and maintain Linux resources. These automated and
intelligent policies allow you to provide centralized control across the lifecycle of
Linux systems for desktop lockdown, imaging, remote management, inventory
management, and software management. The result is a comprehensive Linux
management solution that eliminates IT effort by dramatically reducing the required
overhead needed to manage Linux systems.
PURPOSE OF THE SCENARIOS
The purpose of these scenarios is to familiarize you with the some of new features
included in ZENworks 7.2 Linux Management (Breakout).
With the release of ZENworks 7.2 Linux Management, Novell engineering
has compiled scenarios that represent a number of the new features and functions
of the product. These scenarios are used by our test team and are now being shared
outside of the internal teams to better facilitate testing by users. This
information also helps to provide an overview of many of the features and also can
educate users on the new capabilities of the product.
ASSUMPTIONS
We assume that you have followed:
•The instructions in Installing the ZENworks Primary Server in the ZENworks
7.2 Linux Management Installation Guide.
•The instructions for Setting Up Managed Devices in the ZENworks 7.2 Linux
Management Installation Guide.

p. 3
ZENWORKS 7.2 LINUX MANAGEMENT
SCENARIOS
Click any of the following headings to begin reviewing any of the included scenarios:
Installation Scenarios
1. Installing the ZENworks Agent on a Dell PowerEdge Server
Policy Management Scenarios
2. Configuring the SUSE Linux Enterprise Desktop
Package and Content Management Scenarios
3. Using the Push Now Option to Install a Bundle Immediately After Creation
4. Scheduling the Bundle to Deploy and Install Now (From the Device Object’s Edit
Effective Bundles List)
5. Scheduling the Bundle to Deploy and Install Now (From the Bundle Object’s Edit
Assignments List)
6. Installing a Bundle with the Persistent Bundle Option
7. Viewing the Update Icon Indicating that Software Updates are Available
8. Locking Packages on a Managed Device
9. Locking Bundles on a Managed Device
10.Distributing Files to a Managed Device using a File Bundle
11.Installing Bundles using the ZENworks Linux Management Software Installer
12.Removing Packages using the ZENworks Linux Management Software Remover
13.Updating Packages using the ZENworks Linux Management Software Updater
14.Mirroring from a YUM Server
Preboot Bundle Scenarios
15.Creating a Dell Configuration Bundle
ZENworks Management Daemon (zmd) Setting Scenarios
16.Setting zmd Settings at the Folder or Zone Level (Inheritance)
17.Overriding zmd Settings at the Device Level (Overriding Inheritance)
18.Viewing zmd Setting Changes after an Inventory Scan

p. 4
1: INSTALLING THE ZENWORKS AGENT ON A DELL
POWEREDGE SERVER
Objective:
Install the ZENworks Agent on a Dell* PowerEdge* server and obtain Dell Update
Packages (DUPs).
Steps:
1. Install the ZENworks 7.2 Linux Management server components. For detailed
information, see Installation in the ZENworks 7.2 Linux Management
Installation Guide.
2. Install the ZENworks Agent on a Dell PowerEdge server and register it in the
Management Zone. For detailed information, see Setting Up Managed
Devices in the ZENworks 7.2 Linux Management Installation Guide.
3. On the ZENworks server, download Dell Update packages by using the
ZENworks Linux Management Mirror utility. For detailed information, see
Mirroring Software in the ZENworks 7.2 Linux Management Administration
Guide. Ensure that you follow the instructions in the Enabling Dell PowerEdge
Support section.
4. In the ZENworks Control Center, perform the following steps:
a. Ensure that the Dell Update Package bundles are created. By default,
the bundles are created and updated in the zlmmirror folder.
b. Assign the bundle to the Dell PowerEdge server. For detailed
information, see Assigning Dell Update Package Bundles in the
ZENworks 7.2 Linux Management Administration Guide.
c. Click the Devices tab, select the Dell PowerEdge server, click Actions,
then click Refresh.
The Dell PowerEdge server reboots, depending on the Dell Packages installed.
Expected Results:
On the Dell PowerEdge server, execute the rug bl command. This lists the DUP
bundles available on the server. Review the list.

p. 5
2: CONFIGURING THE SUSE LINUX ENTERPRISE DESKTOP
Objective:
Configure the SUSE® Linux Enterprise Desktop by using the SUSE Linux Enterprise
Desktop policy.
Steps:
1. Install the ZENworks 7.2 Linux Management server components. For detailed
information, see Installation in the ZENworks 7.2 Linux Management
Installation Guide.
2. Install the ZENworks Agent on a SUSE Linux Enterprise Desktop 10 (SLES
10) device and register it in the Management Zone. For detailed information,
see Setting Up Managed Devices in the ZENworks 7.2 Linux Management
Installation Guide.
3. In ZENworks Control Center, create a SUSE Linux Enterprise Desktop policy.
For more information, see SUSE Linux Enterprise Desktop Policy in the
ZENworks 7.2 Linux Management Administration Guide. In the SUSE Linux
Enterprise Desktop Main menu Settings page, select the following options:
•Remove Search from Main Menu
•Remove Recent Documents from Main Menu File Area
•Favorite Applications Configuration > Configure Favorite Applications, and
delete a few applications from the list.
•Remove Application Browser from Main Menu
•System Area Configuration > Configure System Area and move a few
items to the Excluded Items list.
4. Assign the policy to a SUSE Linux Enterprise Desktop 10 device. For more
information, see Assigning Policies in the ZENworks 7.2 Linux Management
Administration Guide.
5. On the Policy Schedule page, set the schedule to Event and ensure that the
User Login option is selected.
6. Log in to the managed device.
Expected Results:
The SUSE Linux Enterprise desktop is customized according to the settings
configured in the SUSE Linux Enterprise Desktop policy.

p. 6
3: USING THE PUSH NOW OPTION TO INSTALL A BUNDLE
IMMEDIATELY AFTER CREATION
Objective:
Verify that a bundle gets deployed and installed immediately at the completion of the
Create New Bundle Wizard.
Steps:
1. Ensure that you have installed the ZENworks 7.2 Linux Management server
components and the ZENworks Agent. For detailed information, see
Installation in the ZENworks 7.2 Linux Management Installation Guide.
2. On the managed device, ensure that the following zmd preferences are set
with the values mentioned:
•bind-ip must be set to either an empty string or to a valid IP address of the
managed device
•remote-enabled must be set to True
For detailed information on how to set the zmd preferences, see the
ZENworks 7.2 Linux Management Administration Guide.
3. In the ZENworks Control Center, create a bundle and assign it to a managed
device. On the Bundle Options page, click the Deploy and install immediately
(when this wizard completes) scheduling option. For detailed information, see
Creating RPM Bundles in the ZENworks 7.2 Linux Management
Administration Guide
Expected Results:
After the completion of the Create New Bundle Wizard, bundles that have been
scheduled to deploy and install immediately at the completion of the wizard are
deployed and installed on the managed device. Verify that by going to the assigned
managed device and executing a rug bl command. This lists the deployed and
installed the bundle.

p. 7
4. SCHEDULING THE BUNDLE TO DEPLOY AND INSTALL
NOW (FROM THE DEVICE OBJECT’S EFFECTIVE BUNDLES
LIST)
Objective:
Verify that a bundle gets deployed and installed immediately using a device’s Edit
Effective Bundles Actions menu.
Steps:
1. Create a RPM bundle. For more information, see Creating RPM Bundles in
the ZENworks 7.2 Linux Management Administration Guide.
2. On the Bundle Options page of the wizard, select a deployment and
installation schedule for the bundle to get installed at a time and date in the
future.
3. Complete the Create New Bundle Wizard.
4. Go to the managed device and run rug sch and notice that the bundle is
scheduled to be installed sometime in the future.
5. Launch the ZENworks Control Center, click the Devices tab, the select the
assigned device for the effective bundle.
6. From the Effective Bundles list, click the Advanced tab.
7. Check the effective bundle that you would like to deploy and install now.
8. Click Actions, then select Deploy and Install Now.
Expected Results:
After pressing Deploy and Install Now, the bundle is immediately installed to the
managed device. Verify that the bundle is installed by going to the assigned
managed device and executing a rug bl command. This lists the deployed and
installed bundle.

p. 8
5: SCHEDULING THE BUNDLE TO DEPLOY AND INSTALL
NOW (FROM THE BUNDLE OBJECT’S EDIT ASSIGNMENTS
LIST)
Objective:
Verify that a bundle gets deployed and installed immediately using bundle object’s
Edit Assignments, Actions menu.
Steps:
1. Create a RPM bundle. For more information, see Creating RPM Bundles in
the ZENworks 7.2 Linux Management Administration Guide.
2. On the Bundle Options page, select a deployment and installation schedule
for the bundle to get installed at a time and date in the future.
3. Complete the Create New Bundle Wizard.
4. Go to the managed device and execute rug sch and notice the bundle and
its scheduled time to be installed sometime in the future.
5. Launch the ZENworks Control Center, click the Bundles tab, then select the
bundle that was just created.
6. From the Assignments list, click Advanced.
7. Check the device object assigned to the bundle that you would like to have
deployed and installed now.
8. Click Actions, then select Deploy and Install Now.
Expected Results:
After pressing Deploy and Install Now, the bundle is immediately installed to the
managed device. Verify that by going to the assigned managed device and
executing a rug bl command. This lists the deployed and installed bundle.

p. 9
6: INSTALLING A BUNDLE WITH THE PERSISTENT BUNDLE
OPTION
Objective:
Install a bundle on a managed device; configure the bundle using the Persistent
bundle option so that the bundle cannot be uninstalled by the managed device user.
Steps:
Ensure that you have installed the ZENworks 7.2 Linux Management server
components and the ZENworks Agent. For detailed information, see Installation in
the ZENworks 7.2 Linux Management Installation Guide.
Part 1: Create, Install, and Uninstall a RPM Package Bundle by Configuring the
Persistent Option
In ZENworks Control Center, create a RPM Package bundle with default options.
For detailed information, see Creating RPM Bundles in the ZENworks 7.2 Linux
Management Administration Guide.
1. In Step 2 of the Create New Bundle Wizard, verify that the Ensure this bundle
stays installed on all assigned devices (enforce persistence) option is
selected. By default, this option is selected.
2. Assign the bundle to a managed device.
3. Set the schedule to Relative to Refresh.
4. On the managed device, perform the following:
a. Start a console session and execute the rug refresh command.
b. Ensure that the RPM package bundle created in Step 1 is installed on
the device by executing the rug bl command.
c. Remove the RPM packaged in the bundle by executing the rug rm
rpm_name command.
d. On the managed device, execute the rug refresh command.
Expected Results:
The uninstalled RPM Package is reinstalled. To view the list of bundles available on
the managed device, use the rug bl command. The list includes the RPM Package
bundle created in Step 1. Verify that the RPM is reinstalled by executing the
following command:
rpm -qa | grep rpm_name

p. 10
Part 2: Create, Install, and Uninstall a RPM Package Bundle by Not Configuring
the Persistent Option
1. In the ZENworks Control Center, create a RPM Package bundle with default
options. For detailed information, see Creating RPM Bundles in the
ZENworks 7.2 Linux Management Administration Guide.
2. In Step 2 of the Create New Bundle wizard, deselect the Ensure this bundle
stays installed on all assigned devices (enforce persistence) option. By
default, this option is selected.
3. Assign the bundle to a managed device.
4. Set the schedule to Relative to Refresh.
5. On the managed device, perform the following:
a. Start a console session and execute the rug refresh command.
b. Ensure that the RPM package bundle created in Step 1 is installed on
the device by executing the rug bl command.
c. Remove the RPM packaged in the bundle by executing the rug rm
rpm_name command.
d. On the managed device, execute the rug refresh command.
Expected Results:
The uninstalled RPM package bundle is not reinstalled. Verify that the RPM is not
installed on the managed device by executing the following command: rpm -qa |
grep rpm_name.

p. 11
7: VIEWING THE UPDATE ICON INDICATING THAT
SOFTWARE UPDATES ARE AVAILABLE
In ZENworks 6.6.xLinux Management, administrators could see whether or not a
device had any package updates by checking for the presence of an icon in the
Updates Available column of the web user interface. Similarly, in ZENworks Linux
Management - Dell Edition (or Avenger), an icon was shown in the Updates
Available column in the device list when a Dell system set, or DUP Bundle, was in
the system but was not assigned to the devices it needed to be assigned to. In the
ZENworks 7.2 Linux Management release, the Updates Available icon combines
these two concepts into a single location.
Objective:
Verify that the Updates Available column for the device list shows an icon for the
following reasons:
•There is a bundle assigned to this device, whose latest version isn't currently
deployed.
•There is a Dell system set (DUP Bundle) for this device's model in the repository,
but it is not assigned to this device.
•There is a package in the repository that is an update to a package installed on
this device, but the package:
ois contained in a bundle not assigned to this device
ois contained in a version of a bundle assigned to this device that isn't
currently deployed
ois contained in a bundle assigned to this device, but simply hasn't been
installed yet
ois not contained in any bundle
Steps:
To verify that the Updates Available icon shows properly:
Part 1: Latest version not deployed
1. From the Bundles tab of the ZENworks Control Center, create a File or RPM
bundle, and assign it to a device. For more information, see Creating File
Bundles or Creating RPM Bundles in the ZENworks 7.2 Linux Management
Administration Guide.
2. On the Devices tab, click to view the list of servers or workstations. Verify that
the device in the previous step has no updates available.

p. 12
3. Go back to the bundle created in Step 1, and change one of its properties,
such as description. This will cause a new version of the bundle to be
created. Be sure not to deploy this new version.
4. Go back to the list of devices, and check the Updates Available column.
Verify that an icon is now shown, and that clicking the icon tells you the latest
version of the assigned bundle is not deployed.
Part 2: DUP Bundle not assigned to the device
1. Use zlmmirror to import Dell DUP Bundles (Dell System Sets) into the system
from the Dell remote server. For more information, see Mirroring Dell Update
Packages to Your ZENworks Server in the ZENworks 7.2 Administration
Guide.
2. Register a device whose model number matches one of the Dell System Sets
previously imported (click the Bundles tab to see the list of available system
sets, or DUP bundles).
3. Click the Devices tab, and click to view the list of servers or workstations.
Verify that an icon is shown for the supported Dell device (Note: the device
inventory scanner needs to be run on the supported device before the system
will know the model number of the Dell system).
Part 3: Package updates
Part 3a: Package in a bundle not assigned to the device
1. Create two RPM bundles, one containing any package you choose, and the
other bundle containing an update to that package. For more information, see
Creating RPM Bundles in the ZENworks 7.2 Linux Management
Administration Guide.
2. Assign the first bundle to a device, and make sure that the bundle gets
installed and that the inventory scanner acknowledges that the package is
installed (check on the Inventory tab of the device’s Details page).
3. From the device list page, verify that an icon is shown in the Updates
Available column, and that clicking it gives the explanation that an updated
package exists in another bundle.
Part 3b: Package in a bundle version not deployed
1. Create an RPM bundle, and add any package you would like. By default this
bundle should be at version 1. For more information, see Creating RPM
Bundles in the ZENworks 7.2 Linux Management Administration Guide.
2. Add a newer version of the package to the bundle, which will automatically
bump the bundle to version 2, but do not deploy this version.

p. 13
3. Assign the bundle to a device and make sure that the bundle gets installed
and that the inventory scanner detects that the package has been installed
successfully (check the Inventory tab of the bundle’s Details page).
4. From the device list page, verify that an icon is shown in the Updates
Available column, and that clicking it gives the explanation that an updated
package exists in a newer version of the bundle.
Part 3c: Package not installed yet
1. Create an RPM bundle and add any package you would like. For more
information, see Creating RPM Bundles in the ZENworks 7.2 Linux
Management Administration Guide.
2. Assign the bundle to a device and make sure that the schedule is set for
some time in the future. Make sure the device is refreshed and that executing
the rug sch command shows that the bundle will be installed at a future
time.
3. From the device list page, verify that an icon is shown in the Updates
Available column, and that clicking it gives the explanation that an updated
package exists in a bundle that hasn't been installed yet.
Part 3d: Package not in any bundle
1. Create two RPM bundles, one containing any package you choose, and the
other bundle containing an update to that package. For more information, see
Creating RPM Bundles in the ZENworks 7.2 Linux Management
Administration Guide.
2. Assign the first bundle to a device and make sure that the bundle gets
installed and that the inventory scanner acknowledges that the package is
installed (check on the Inventory tab of the device’s Details page).
3. Delete the second bundle so that the updated package is in the system, but it
is not contained in any bundle.
4. From the device list page, verify that an icon is shown in the Updates
Available column, and that clicking it gives the explanation that an updated
package exists in the system, but is not made available by any bundles.
Expected Results:
Verify that the Updates Available icon is shown for the following reasons:
•There is a bundle assigned to this device, whose latest version isn't currently
deployed.
•There is a Dell system set (DUP Bundle) for this device's model in the repository,
but it is not assigned to this device.

p. 14
•There is a package in the repository that is an update to a package installed on
this device, but the package:
ois contained in a bundle not assigned to this device
ois contained in a version of a bundle assigned to this device, which isn't
currently deployed
ois contained in a bundle assigned to this device, but simply hasn't been
installed yet
ois not contained in any bundle

p. 15
8: LOCKING PACKAGES ON A MANAGED DEVICE
Objective:
Prevent deletion of a package on a managed device by locking the package.
Steps:
To lock a package:
1. Ensure that you have installed the ZENworks Agent. For detailed information,
see Setting Up Managed Devices in the ZENworks 7.2 Linux Management
Installation Guide.
2. Register the managed device to a Red Carpet Enterprise (RCE) or a YUM
server by executing the rug sa URL_of_the_RCE_or_YUM_server
command.
3. On the managed device, list all packages installed by executing the rug pa
command.
4. Select a package you want to lock, and lock it by executing the rug la
package_name command.
5. On the managed device, list all the locked packages by executing the rug
ll command.
Expected Results:
On the managed device, delete the locked package by executing the rug rm
package_name command. Notice that the specified package is not deleted in this
scenario because it is locked. The following message is displayed: “package_name
is locked and cannot be removed.”
For information on how to unlock a package, see rug in the ZENworks 7.2 Linux
Management Administration Guide.

p. 16
9: LOCKING BUNDLES ON A MANAGED DEVICE
Objective:
Prevent deletion of a bundle on a managed device by locking the bundle.
Steps:
To lock a bundle:
1. Ensure that you have installed the ZENworks 7.2 Linux Management server
components and ZENworks Agent. For detailed information, see Installation
in the ZENworks 7.2 Linux Management Installation Guide.
2. In the ZENworks Control Center, create a bundle and assign it to the
managed device. For detailed information, see Creating RPM Bundles in the
ZENworks 7.2 Linux Management Administration Guide.
3. On the managed device, perform the following steps:
a. Verify that the bundle created in the previous step is installed on the
device by executing the rug bl command.
b. Lock the bundle by executing the rug bla bundle_name command.
c. Verify that the bundle is locked by executing the rug bll command.
Expected Results:
On the managed device, delete the locked bundle by executing the rug brm
bundle_name command. Notice that the specified bundle is not deleted in this
scenario because it is locked.
For information on how to unlock a bundle, see rug in the ZENworks 7.2 Linux
Management Administration Guide.

p. 17
10: DISTRIBUTING FILES TO A MANAGED DEVICE USING A
FILE BUNDLE
Objective:
Use a File bundle to automatically distribute files to a managed device.
Steps:
1. Ensure that you have installed the ZENworks 7.2 Linux Management server
components and the ZENworks Agent. For detailed information, see
Installation in the ZENworks 7.2 Linux Management Installation Guide.
2. In the ZENworks Control Center, create a File bundle and assign it to a
managed device. For detailed information, see Creating File Bundles in the
ZENworks 7.2 Linux Management Administration Guide.
Expected Results:
On the managed device, execute the rug refresh command. Depending on the
bundle schedule, the files are copied to the specified destination folder on the
managed device.

p. 18
11: INSTALLING BUNDLES USING THE ZENWORKS LINUX
MANAGEMENT SOFTWARE INSTALLER
Objective:
Install a bundle on a managed device using the ZENworks Linux Management
Software Installer interface.
Steps:
1. Ensure that you have installed the ZENworks 7.2 Linux Management server
components and the ZENworks Agent. For detailed information, see
Installation in the ZENworks 7.2 Linux Management Installation Guide.
2. In the ZENworks Control Center, do the following:
a. Create a RPM bundle. For more information, see Creating RPM
Bundles in the ZENworks 7.2 Linux Management Administration
Guide.
b. Create a catalog. For more information, see Creating Catalogs in the
ZENworks 7.2 Linux Management Administration Guide.
c. Add the bundle to the catalog. For more information, see Adding Bundles
to Catalogs in the ZENworks 7.2 Linux Management Administration
Guide.
3. On the managed device, launch the ZENworks Linux Management Software
Installer by executing the zen-installer command.
4. Click Configure, then click Catalog.
5. Subscribe to the catalog created in Step 2b.
6. In the ZENworks Linux Management Software Installer window, select the
RPM bundle created in Step 2a.
7. Click Install.
Expected Results:
On the managed device, execute the rug bl command. The list includes the
bundled installed.

p. 19
12: REMOVING PACKAGES USING THE ZENWORKS LINUX
MANAGEMENT SOFTWARE REMOVER
Objective:
Uninstall an RPM package on a managed device using the ZENworks Linux Management
Software Remover interface.
Steps:
1. Use the same setup as the previous scenario.
2. On the managed device, launch ZENworks Linux Management Software
Remover by executing the zen-remover command.
3. Specify the package you want to uninstall, and click Search.
4. From the Search result, select the package you want to uninstall.
5. Click Uninstall.
Expected Results:
On the managed device, execute the rug pa command. The list does not include
the uninstalled package.

p. 20
13: UPDATING PACKAGES USING THE ZENWORKS LINUX
MANAGEMENT SOFTWARE UPDATER
Objective:
Update software packages installed on a managed device from a YUM repository
using the ZENworks Linux Management Software Updater.
Steps:
1. Install the ZENworks Agent and register it in the Management Zone. For
detailed information, see Setting Up Managed Devices in the ZENworks 7.2
Linux Management Installation Guide.
2. On the managed device, launch the ZENworks Linux Management Software
Updater by executing the zen-updater command.
3. Click Configure, then click Catalog.
4. Subscribe to the catalog available on the YUM server.
5. Click Add Service.
6. Select the YUM service type.
7. Specify the service URI of a public YUM repository you want to use to update
your packages.
8. Specify a service name.
9. Click Add.
10.In the Configuration window, click Catalog and subscribe to the catalog
provided by the service.
11.In the Software Updater window, select the packages you want to update.
12.Click Update.
Expected Results:
On the managed device, execute the rug pa command. The list includes the
updated packages.