ZENworks Linux Management 7.2 IR1 Hot Patch 1 Enhancements

  • 3726735
  • 10-Oct-2007
  • 30-Apr-2012

Environment

Novell ZENworks 7.2 Linux Management - ZLM7.2

Situation

Novell ZENworks 7.2 Linux Management with Interim Release 1 Hot Patch 1 contains packages that were updated for ZENworks 7.2 Linux Management after the IR1 release.

We strongly recommend that you check the readme of ZENworks 7.2 Linux Management with Interim Release 1 Hot Patch 1 for installation instructions, list of issues fixed in the release, and the issues that pertain to the release.
1.0 What's New in Interim Release 1 Hot Patch 1?
1.1 Introducing novell-zenworks-zlm-release package
1.2 Mirroring Patch Bundles for SLES 10 and SLED 10 from the NU and RCE Type Repositories
1.2.1 Mirroring of the Monolithic and Patch Bundles for SLES 10 and SLED 10
1.2.2 Mirroring of the Patch bundles for SLES 10 and SLED 10
1.2.3 Mirroring of the Monolithic Bundles for SLES 10 and SLED 10
1.3 Mirroring Based on Category of the Patch
1.4 Filtering the Bundles Based on Category in ZENworks Control Center
1.5 Filtering the Assigned bundles Based on the Bundle Type
1.6 Viewing the ZENworks Linux Management Hot Patch Version Installed on the Device
1.7 Logging ZENworks Control Center Events
1.8 Point-in-Time Rebuild of the Managed Device
2.0 Documentation Conventions
3.0 Legal Notices

Resolution

1.0 What's New in Interim Release 1 Hot Patch 1?

The following sections describe the new or enhanced features in ZENworks 7.2 Linux Management with Interim Release 1 Hot Patch 1:

1.1 Introducing novell-zenworks-zlm-release package
A new novell-zenworks-zlm-release package containing the following files has been introduced:

zenworks-release:The /etc/opt/novell/zenworks/zenworks-release file contains the ZENworks Linux Management release version along with the Hot Patch version.

zenworks-update.sh:The /opt/novell/zenworks/lib/install/zenworks-update.sh file automates the pre and post install steps that are required as part of the Hot Patch install.

1.2 Mirroring Patch Bundles for SLES 10 and SLED 10 from the NU and RCE Type Repositories
You can mirror patch bundles for SLES 10 and SLED 10 from the NU and RCE type repositories such as nu.novell.com and update.novell.com.

Review the following sections for more information:

1.2.1 Mirroring of the Monolithic and Patch Bundles for SLES 10 and SLED 10
The mirroring of updates for SLES 10 and SLED 10 platforms from NUServer and RCEServer using the zlmmirror m -c conf.xml command creates patch bundles and a monolithic bundle-bundle with all the packages in it.

1.2.2 Mirroring of the Patch bundles for SLES 10 and SLED 10
Use the -p option in the zlmmirror m -p -c mirror-conf.xml command to mirror only the patch bundles for SLES10 and SLED10 platforms from RCE type and/or NU type remote servers.

1.2.3 Mirroring of the Monolithic Bundles for SLES 10 and SLED 10
To mirror the monolithic bundle(s) without creating the patch bundles, use the tag of the mirror conf file.

For example, SLED10-Updates-bundle to mirror SLED10-Updates catalog.

The slb option displays both monolithic and patch bundles. You can download the desired bundle by using the tag. To download the specific packages in the monolithic bundle, use the tag for the monolithic bundle and tags for the specific packages.

For example, a sample section to mirror the Mozilla* packages of the monolithic bundle is as follows:


SLED10-Updates
SLED10-Updates

sled-10-i586

SLED10-Updates-bundle

Mozilla*



NOTE: The local name for the catalog should NOT be same as that reserved for the folder -patches. In other words, The tag of mirror config file should NOT use the name as -patches.

1.3 Mirroring Based on Category of the Patch
A new option --category has been added to the zlmmirror mirror command for mirroring patch bundles based on category for SLES 10 and SLED10. The --category option accepts security, recommended, and optional as the values for the category argument. For example, to mirror security patches, use the following command.

zlmmirror m -c conf.xml --category=security.

The --category option is applicable for patch bundles of SLES10 and SLED10 platforms only. If --category option is used it also means that -p option is used implicitly (i.e., mirroring of patches only).

If you do not specify the --category option, all the patches are mirrored. This option is applicable for NU and RCE servers only. Category-based mirroring is not supported for YOU patch bundles.

While mirroring patches the zlmmirror utility creates a monolithic bundle named -bundle. However, with the category-based mirroring enhancement, the zlmmirror utility additionally mirrors down patches into -patches folder(s). This helps to organize the patches better; and also enables the ZLM administrator to push out updates based on category.

The new zlmmirror folder structure would be as follows:

zlmmirror (or the folder name as specified in the config file)
|__catalog
|__-bundle
|__-patches
|__patch_bundle1
|__patch_bundle2


1.4 Filtering the Bundles Based on Category in ZENworks Control Center
You can now search for the bundles based on the category in ZENworks Control Center by using the Category option of the Search dialog box. The Category option provides the following filter options: Security, Recommended, and Optional.

In ZENworks Control Center, the values in the Category option are populated through the category-based mirroring feature of zlmmirror, which is also part of the Hot Patch.

1.5 Filtering the Assigned bundles Based on the Bundle Type
You can now filter the assigned bundles based on the type of the bundle by using the following command:

rug bl -t

Where -t is the type of the bundle. Valid values are package, file, and YOU patch. You can specify the value in one of the following formats:

rug bl -t file
rug bl -t=file
rug bl --type file
rug bl --type=file

1.6 Viewing the ZENworks Linux Management Hot Patch Version Installed on the Device
To view the ZENworks Linux Management Hot Patch version installed on the device, use the rug ping command. A sample output of this command is as follows:

ZMD 7.2.1, Copyright (C) 2007 Novell, Inc.

ZLM Hot Patch Level - 1

Started at 10/4/2007 1:45:08 PM (uptime: 1 days, 0 hours, 31 minutes)

RSS size: 43592

Network Connected: Yes

Running on Mono 1.2.2

OS Target: SUSE Linux Enterprise Desktop 10 (x86_64)

Module Name | Description
-------------------+-------------------------------

Image Agent Module | Novell ZENWorks Imaging Agent

Policy Manager | Manages policy enforcement on the device

Settings | Handles Settings refresh events.

TessModule | Tess Module

Inventory | Software and Hardware inventory module for Linux

NetworkManager | NetworkManager support

Package Management | Package Management module for Linux

RMModule | Remote Management module

ZENworks Server | SOAP methods used by a ZENworks server

Scheduled Actions | Scheduled Actions module for ZMD

XML-RPC interface | Export ZMD public interfaces over XML-RPC


1.7 Logging ZENworks Control Center Events
You can now find out the operations performed through ZENworks Control Center by referring to the audit-messages.log file. The following operations are logged in to the audit-messages.log file that is created in the log directory:

* Login and logout events.
* Creating, deleting, or assigning bundles or policies.
* Deleting devices.
* Creating or deleting users.

NOTE: The audit-messages.log file logs only the actions performed by the administrator through ZENworks Control Center and is not an authorized audit information.

1.8 Point-in-Time Rebuild of the Managed Device
To register a managed device with the ZENworks server by performing a point-in-time replacement of the older Agent, use the -r or the --rebuild option of the rug service-add (sa) command.

For example: rug sa -r

or

rug sa --rebuild

The point-in-time replacement of the managed device lets you replace the older device object on the ZLM Server with the current device object that is requesting the rebuild. The rebuild operation ensures that all the bundle and policy associations are retained. The replacement of the device object is based on the alias name (display name) and the primary IP address of the managed device.

2.0 Documentation Conventions
In this 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.

3.0 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.

You may not use, export, or re-export this product in violation of any applicable laws or regulations including, without limitation, U.S. export regulations or the laws of the country in which you reside.

Copyright © 2007 Novell, Inc. All rights reserved. No part of this publication may be reproduced, photocopied, stored on a retrieval system, or transmitted without the express written consent of the publisher.

Novell, Inc. has intellectual property rights relating to technology embodied in the product that is described in this document. In particular, and without limitation, these intellectual property rights may include one or more of the U.S. patents listed at https://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 is a registered trademark of Novell, Inc. in the United States and other countries.

SUSE is a registered trademark of SUSE AG, a Novell business.

All third-party trademarks are the property of their respective owners.

Feedback service temporarily unavailable. For content questions or problems, please contact Support.