Novell ZENWORKS LINUX MANAGEMENT Administration Guide

Novell®

www.novell.com

Administration Guide

ZENworks® Linux Management

novdocx (en) 11 July 2008

AUTHORIZED DOCUMENTATION

7.2 IR2

September 25, 2008

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.

novdocx (en) 11 July 2008

Copyright © 2007-2009 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 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 Guide 19

Part I Understanding ZENworks Linux Management 21

1 A Quick Tutorial on Basic ZENworks Linux Management Features 23

1.1 Organizing Devices: Folders and Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

1.1.1 Folders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

1.1.2 Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

1.1.3 Folders vs. Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

1.2 Creating Registration Keys and Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

1.3 Setting Up ZENworks Administrator Accounts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

1.4 Delivering Software Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

1.4.1 Bundles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

1.4.2 Catalogs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

1.5 Delivering Content Using File Bundles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

1.6 Defining and Locking Down Device Configuration Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

1.7 Using Preboot Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

1.8 Collecting Software and Hardware Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

1.9 Managing Remote Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

1.10 Monitoring Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

1.10.1 Hot List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

1.10.2 Event Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

1.10.3 System Event Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

1.10.4 Message Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

1.11 Generating Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

novdocx (en) 11 July 2008

2 Using ZENworks Linux Management with Dell PowerEdge Servers 35

2.1 Configuring PowerEdge Servers using Dell Configuration Bundles. . . . . . . . . . . . . . . . . . . . . 35

2.2 Obtaining, Configuring, and Updating PowerEdge Servers Using Dell Update Package

Bundles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

2.2.1 Obtaining Dell Update Packages from Dell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

2.2.2 Assigning Dell Update Package Bundles to Configure and Update PowerEdge

Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

2.2.3 Determining If Newer Dell Package Updates Are Available for PowerEdge Servers 37

2.2.4 Deploying a Newer Dell Update Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

2.3 Using Advanced Dell Inventory Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

2.4 Using Advanced Dell Inventory Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Part II ZENworks System Management 39

3 ZENworks Control Center 41

3.1 Where the ZENworks Control Center Is Installed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

3.2 Accessing the ZENworks Control Center. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

3.3 Accessing the ZENworks Control Center through Novell iManager. . . . . . . . . . . . . . . . . . . . . 42

3.4 Changing the Timeout Value for the ZENworks Control Center. . . . . . . . . . . . . . . . . . . . . . . . 42

Contents 5

3.5 Changing the Debug Settings of ZENworks Control Center . . . . . . . . . . . . . . . . . . . . . . . . . . 43

4 Command Line Administration Utilities 45

4.1 zlman . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

4.2 zlm-debug . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

4.3 zlmmirror . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

4.4 rug . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

4.5 zmd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

4.6 zrmservice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

5 ZENworks Server 47

5.1 ZENworks Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

5.1.1 Checking the Status of a ZENworks Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

5.1.2 Starting a ZENworks Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

5.1.3 Stopping a ZENworks Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

5.1.4 Restarting a ZENworks Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

5.2 RPM Package Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

5.2.1 Package Repository Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

5.2.2 Package Replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

5.2.3 Package Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

5.3 Uninstalling a ZENworks Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

5.3.1 Uninstalling a Primary ZENworks Server Using zlm-uninstall . . . . . . . . . . . . . . . . . . 50

5.3.2 Uninstalling a Secondary ZENworks Server Using zlm-config . . . . . . . . . . . . . . . . . 51

5.3.3 Manually Uninstalling a Primary or Secondary ZENworks Server . . . . . . . . . . . . . . . 51

5.4 Freeing Disk Space on a ZENworks Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

novdocx (en) 11 July 2008

6 ZENworks Agent 53

6.1 ZENworks Agent (zmd) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

6.1.1 ZENworks Agent (zmd) Cache Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

6.2 File System Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

6.3 Using the Software Updater, Installer, and Remover from Users’ Managed Devices . . . . . . . 54

6.3.1 Updating Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

6.3.2 Installing Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

6.3.3 Removing Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

6.3.4 Viewing System Preferences. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

6.3.5 Editing System Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

6.4 Uninstalling the ZENworks Agent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

7 Configuring Management Zone Settings 67

7.1 Configuring System Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

7.1.1 Creating System Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

7.1.2 Using Variables in ZENworks Policies: A Sample Use Case. . . . . . . . . . . . . . . . . . . 68

7.2 Configuring the Device Refresh Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

7.3 Configuring Device Inventory Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

7.4 Configuring Local Device Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

7.5 Configuring Preboot Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

7.6 Configuring Remote Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

7.7 Configuring Centralized Message Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

7.8 Configuring the Content Replication Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

7.9 Viewing Default Target Platforms and Configuring Custom Target Platforms . . . . . . . . . . . . . 73

6 Novell ZENworks 7.2 Linux Management Administration Guide

7.10 Configuring the ZENworks Management Daemon (zmd) Settings. . . . . . . . . . . . . . . . . . . . . . 74

7.11 Integrating Novell Customer Center with ZENworks Linux Management . . . . . . . . . . . . . . . . 75

7.12 Configuring the ZENworks Server Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

7.13 Understanding the StoreFileDeps Preference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

8 ZENworks Administrator Accounts 79

8.1 Creating an Administrator Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

8.2 Modifying Account Rights. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

9 ZENworks Object Store and Data Store Maintenance 83

9.1 Maintaining the ZENworks Object Store . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

9.1.1 Backing Up the ZENworks Object Store . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

9.1.2 Restoring the ZENworks Object Store. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

9.1.3 Deleting the Dangling Objects from ZENworks Object Store. . . . . . . . . . . . . . . . . . . 84

9.2 Maintaining the ZENworks Data Store on PostgreSQL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

9.2.1 Displaying the Password for the Default PostgreSQL Database . . . . . . . . . . . . . . . . 86

9.2.2 Understanding Automated Database Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . 86

9.2.3 Backing Up the ZENworks Data Store. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

9.2.4 Restoring the ZENworks Data Store . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

9.2.5 Optimizing the Server Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

9.2.6 Restarting Novell Zenworks Server Services After Restarting the Database . . . . . . 89

9.3 Maintaining the ZENworks Data Store on Oracle. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

9.3.1 Backup and Recovery Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

9.3.2 Setting Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

9.3.3 Connecting to the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

9.3.4 Starting the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

9.3.5 Backing Up the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

9.3.6 Recovering the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

9.3.7 Shutting Down the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

9.4 Synchronizing the Object Store and Data Store . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

9.5 Cleaning Up the ZENworks Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

novdocx (en) 11 July 2008

Part III Device Registration 95

10 Registration Overview 97

11 Registering Devices 99

11.1 Installing the ZENworks Agent and Registering Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

11.2 Registering a Device after Installing the ZENworks Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

11.3 Automatically Registering the Services at the Initial Startup of zmd . . . . . . . . . . . . . . . . . . . 100

12 Managing Registration Keys and Rules 101

12.1 Managing Registration Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

12.1.1 Creating Keys to Register Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

12.1.2 Editing Existing Registration Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

12.1.3 Renaming, Copying, or Moving Registration Keys . . . . . . . . . . . . . . . . . . . . . . . . . 106

12.1.4 Deleting Registration Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

12.2 Managing Registration Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

12.2.1 Creating Rules to Register Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

12.2.2 Editing Existing Registration Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Contents 7

12.2.3 Renaming or Copying Registration Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

12.2.4 Reordering Registration Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

12.2.5 Deleting Registration Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

12.3 Creating Folders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

13 Unregistering and Reregistering Devices 115

13.1 Possible Scenarios for Unregistering and Reregistering Devices . . . . . . . . . . . . . . . . . . . . . 115

13.2 Unregistering Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

13.3 Reregistering Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

Part IV Policy Management 117

14 Policy Management Overview 119

14.1 Understanding Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

14.2 Creating Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

14.3 Managing Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

novdocx (en) 11 July 2008

15 Understanding Policies 121

15.1 Types of Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

15.2 Assignments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

15.3 Schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

15.4 Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

15.5 System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

15.6 Effective Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

16 Creating Policies 127

16.1 Epiphany Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

16.2 Evolution Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

16.3 Firefox Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

16.4 Generic GNOME Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

16.5 Novell Linux Desktop Policy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

16.6 Remote Execute Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

16.7 SUSE Linux Enterprise Desktop Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

16.8 Text File Policy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

17 Managing Policies 177

17.1 Creating Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177

17.2 Creating Folders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178

17.3 Creating Policy Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

17.4 Assigning Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

17.5 Removing Policy Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

17.6 Adding Policies to Existing Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184

17.7 Editing Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184

17.7.1 Editing Epiphany, Evolution, Firefox, and NLD Policies . . . . . . . . . . . . . . . . . . . . . 184

17.7.2 Editing Generic GNOME Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

17.7.3 Editing Remote Execute Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189

17.7.4 Editing Text File Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191

17.7.5 Viewing Policy Enforcement Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194

8 Novell ZENworks 7.2 Linux Management Administration Guide

17.8 Editing System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194

17.9 Refreshing Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196

17.10 Verifying Policy Enforcement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196

17.11 Renaming, Copying, or Moving Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197

17.12 Deleting Policies, Policy Groups, and Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198

17.13 Unenforcing Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199

Part V Package and Content Management 201

18 Package and Content Management Overview 203

18.1 Understanding RPM and File Bundles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205

18.2 Understanding Catalogs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205

18.3 Understanding Dell Update Package Bundles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206

18.4 Understanding the zlman Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206

18.5 Replicating Content in the ZENworks Management Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . 206

18.6 Mirroring Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206

19 Understanding RPM Packages 207

novdocx (en) 11 July 2008

19.1 Installing the RPM Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207

19.2 Understanding the RPM Repositories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207

19.2.1 ZYPP Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207

19.2.2 YaST Online Update (YOU) Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208

19.2.3 RCE Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208

19.2.4 NU Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208

19.3 Understanding the Dependencies of RPM Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208

19.4 Loading Base Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209

19.5 Patching the Client Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209

20 Using RPM and File Bundles 211

20.1 Understanding Bundles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211

20.1.1 RPM Bundles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212

20.1.2 Preboot Bundles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212

20.1.3 File Bundles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212

20.2 Creating RPM Bundles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212

20.3 Creating File Bundles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223

20.4 Assigning Bundles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232

20.5 Editing Bundles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235

20.6 Adding Bundles to Catalogs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239

20.7 Creating Folders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239

20.8 Creating Bundle Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241

20.9 Adding Bundles to Existing Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245

20.10 Uninstalling Bundles from Devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246

20.10.1 Using the Bundles Page to Remove Bundles from Devices . . . . . . . . . . . . . . . . . . 246

20.10.2 Using the Devices Page to Remove Bundles from Devices . . . . . . . . . . . . . . . . . . 248

20.11 Deleting Bundles, Bundle Groups, and Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249

20.12 Renaming, Copying, or Moving Bundles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250

20.13 Deploying a Different Version of a Bundle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251

20.13.1 Bundle Version Deployment Behavior (ZENworks Control Center vs. the zlman

Utility). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251

20.14 Using a Remote Execute Policy to Remove Bundles and Packages from Devices. . . . . . . . 252

Contents 9

20.15 Generating Bundle Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255

20.16 Best Practices for Adding Packages to Bundles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256

21 Understanding the Package and Content Management Features Available on a

Managed Device 259

21.1 Locking and Unlocking a Package on a Managed Device . . . . . . . . . . . . . . . . . . . . . . . . . . . 259

21.2 Locking and Unlocking a Bundle on a Managed Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260

21.2.1 Locking a Bundle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260

21.2.2 Unlocking a Bundle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260

21.3 Reverting to a Previously Installed Software Configuration State . . . . . . . . . . . . . . . . . . . . . 261

21.4 Installing the Best Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262

21.4.1 Using the rug in Utility to Install the Best Package . . . . . . . . . . . . . . . . . . . . . . . . . 262

21.4.2 Using the zen-installer Utility to Install the Best Package . . . . . . . . . . . . . . . . . . . . 262

22 Using Catalogs 265

22.1 Understanding Catalogs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265

22.2 Creating Catalogs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265

22.3 Assigning Catalogs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271

22.4 Adding Bundles to Catalogs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274

22.5 Renaming or Moving Catalogs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274

22.6 Deleting Catalogs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275

22.7 Creating Folders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276

novdocx (en) 11 July 2008

23 Using Dell Update Package Bundles 279

23.1 Obtaining Dell Update Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279

23.2 Assigning Dell Update Package Bundles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279

23.3 Determining If Newer Dell Package Updates Are Available for PowerEdge Servers. . . . . . . 283

23.4 Deploying an Updated Version of a Dell Update Package Bundle . . . . . . . . . . . . . . . . . . . . 283

23.5 Modifying the Contents of a Dell Update Package Bundle . . . . . . . . . . . . . . . . . . . . . . . . . . 284

24 Replicating Content in the ZENworks Management Zone 287

24.1 Replicating the Content Immediately . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287

24.2 Configuring a Content Replication Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288

25 Mirroring Software 289

25.1 zlmmirror . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290

25.2 xzlmmirror . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290

25.3 Configuring a Software Mirror . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290

25.3.1 Creating the Configuration Files by using the Command Line Utility. . . . . . . . . . . . 291

25.3.2 Creating a Configuration File by Using the xzlmmirror Utility. . . . . . . . . . . . . . . . . . 296

25.3.3 Mirroring Patch Bundles for SLES 10 / SLED 10 / OES 2 from the NU and RCE Type

Repositories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302

25.3.4 Testing and Performing the Mirroring Operation by Using zlmmirror. . . . . . . . . . . . 303

25.3.5 Testing and Performing the Mirroring Operation by Using the xzlmmirror Utility . . . 303

25.4 Distributing Catalogs from a Public ZENworks Linux Management Server . . . . . . . . . . . . . . 304

25.4.1 Creating a Public ZENworks Linux Management Server. . . . . . . . . . . . . . . . . . . . . 304

25.4.2 Accessing a Public ZENworks Linux Management Server . . . . . . . . . . . . . . . . . . . 304

25.5 Mirroring Dell Update Packages to Your ZENworks Server. . . . . . . . . . . . . . . . . . . . . . . . . . 305

10 Novell ZENworks 7.2 Linux Management Administration Guide

25.6 Mirroring Bundles Between ZENworks 7.2 Linux Management Servers Located in Different

Management Zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309

25.7 Deploying Red Hat Network Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310

25.7.1 Providing All RPM Packages and Package Bundles through a Catalog (Pulling) . . 311

25.7.2 Delivering Specific RPM Packages (Pushing) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311

25.8 Encoding the ZENworks Server Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312

26 Creating RPM Packages From Tarballs 313

26.1 Alien Package Converter Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313

26.2 Installing Alien Package Converter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313

26.3 Example Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314

Part VI Preboot Services 315

27 Preboot Services Overview 317

27.1 Preboot Services Functionality. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317

27.2 Preboot Services Strategies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317

27.3 Preboot Bundles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318

27.4 Configuring Preboot Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318

27.5 Setting Up Devices to Use Preboot Bundles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319

novdocx (en) 11 July 2008

28 Understanding Preboot Services in ZENworks Linux Management 321

28.1 How Do You Implement Preboot Services? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321

28.2 What Is the Preboot Execution Environment (PXE)? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321

28.2.1 Understanding How Preboot Services Uses PXE . . . . . . . . . . . . . . . . . . . . . . . . . . 321

28.2.2 Understanding the ZENworks NBPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322

28.2.3 Preparing to Use PXE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323

28.3 Preboot Services Functionality. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323

28.3.1 Preboot Bundles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323

28.3.2 Preboot Services Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325

28.3.3 Image Storage Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326

28.3.4 Non-registered Device Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326

28.3.5 Preboot Work Assignment Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327

28.3.6 Preboot Referral Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328

28.3.7 Intel Active Management Technology (AMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329

28.4 The Preboot Services Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331

28.4.1 A Typical Preboot Services Operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331

28.4.2 Illustrating the Preboot Services Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331

28.5 Preboot Strategies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337

28.5.1 Automating Updates and Installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337

28.5.2 Creating, Installing, and Restoring Standard Images . . . . . . . . . . . . . . . . . . . . . . . 338

28.5.3 Reimaging Corrupted Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339

28.5.4 Restoring Lab Devices to a Clean State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339

28.5.5 Setting Up Devices for Future Reimaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340

28.5.6 Multicasting Device Images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340

28.5.7 Configuring Dell Linux Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342

29 Setting Up Preboot Services 345

29.1 Preparing a Preboot Services Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345

29.2 Setting Up the Preboot Services Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346

Contents 11

29.2.1 Using Preboot Services (PXE). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346

29.2.2 Preparing Imaging Boot CDs or DVDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346

29.2.3 Using the ZENworks Imaging Media Creator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348

29.2.4 Managing ZENworks Partitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354

29.3 Deploying and Managing Preboot Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356

29.3.1 Checking the Preboot Services Imaging Server Setup . . . . . . . . . . . . . . . . . . . . . . 357

29.3.2 Deploying Preboot Services In a Network Environment . . . . . . . . . . . . . . . . . . . . . 358

29.3.3 Administering Preboot Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366

29.3.4 Editing the Preboot Services Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368

29.4 Configuring Preboot Services Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371

29.4.1 Configuring Preboot Services Menu Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371

29.4.2 Configuring Image Storage Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373

29.4.3 Configuring Non-registered Device Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374

29.4.4 Configuring Preboot Work Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377

29.4.5 Configuring the Server Referral List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384

29.4.6 Configuring Intel Active Management Technology (AMT) . . . . . . . . . . . . . . . . . . . . 386

29.5 Overriding Preboot Services Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390

29.6 Enabling PXE on Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392

29.6.1 Enabling PXE on a PXE-Capable Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392

29.6.2 Verifying That PXE Is Enabled on a Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393

29.7 Setting Up Devices for Imaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393

29.7.1 Device Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394

29.7.2 Enabling a Device for Imaging Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394

29.7.3 Disabling Persistent Device Names. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395

novdocx (en) 11 July 2008

30 Using Preboot Services 397

30.1 Imaging Devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397

30.1.1 Imaging Using the ZENworks Control Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397

30.1.2 Performing Manual Imaging Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405

30.1.3 Setting Up Disconnected Imaging Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414

30.2 Multicasting Images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419

30.2.1 Multicasting in the ZENworks Control Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420

30.2.2 Multicasting Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425

30.3 Configuring AutoYaST or Kickstart Installation Script Bundles . . . . . . . . . . . . . . . . . . . . . . . 430

30.3.1 Configuring an AutoYaST Bundle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 430

30.3.2 Configuring a Kickstart Bundle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 436

30.4 Configuring ZENworks Script Bundles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 440

30.5 Using Dell Configuration Bundles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444

30.5.1 Creating Dell Configuration Scripts and Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444

30.5.2 Creating Dell Configuration Bundles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447

30.6 Assigning Unassigned Preboot Bundles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 451

30.7 Editing Preboot Services Work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 453

31 Imaging Utilities and Components 457

31.1 Starting Image Explorer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457

31.2 Determining the Image Explorer Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457

31.3 Image Explorer versus Linux Konquerer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 458

31.4 Opening an Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 458

31.5 Saving Image Changes and Exiting the Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 458

31.6 Managing Image Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 458

31.6.1 Viewing and Modifying the Properties of the Image File . . . . . . . . . . . . . . . . . . . . . 458

31.6.2 Viewing the Properties of an Image File Item . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 459

31.6.3 Changing a Partition’s Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 459

31.7 Image File Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 460

12 Novell ZENworks 7.2 Linux Management Administration Guide

31.7.1 Compressing an Image File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 460

31.7.2 Splitting an Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 461

31.7.3 Hiding and Removing Content in the Image File . . . . . . . . . . . . . . . . . . . . . . . . . . . 462

31.7.4 Configuring File Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 463

31.7.5 Extracting Content as Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464

31.7.6 Extracting Content as an Add-on Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464

31.7.7 Creating an Add-on Image. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 465

31.8 Modifying Image Content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 465

31.8.1 Adding Directories and Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 465

31.8.2 Creating a New Directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466

31.8.3 Creating a New Partition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466

31.8.4 Resizing a Partition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466

31.9 Creating a New Image File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466

31.9.1 Creating, Configuring, and Saving the New Image File. . . . . . . . . . . . . . . . . . . . . . 466

31.9.2 Selecting New Image File Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466

Part VII Hardware and Software Inventory 469

32 Inventory Overview 471

novdocx (en) 11 July 2008

33 Reviewing the Device Inventory 473

33.1 Accessing the Device Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473

33.2 Reviewing Device Inventory Summaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473

33.3 Reviewing Hardware (General) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474

33.4 Reviewing Software (General) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474

33.5 Reviewing Hardware Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474

33.6 Refreshing Device Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 478

34 Rolling Up Hardware Inventory 479

34.1 Preparing to Roll Up Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 479

34.2 Configuring the Inventory Roll-Up Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 479

34.3 Understanding the Roll-Up Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480

34.4 Understanding the Components Involved in the Inventory Roll-Up . . . . . . . . . . . . . . . . . . . . 481

34.4.1 Understanding the Sender. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 481

34.4.2 Understanding the Compressed Scan Data File . . . . . . . . . . . . . . . . . . . . . . . . . . . 482

34.5 Viewing the Inventory Data Stored in the ZENworks 7 Server Management or ZENworks 7

Desktop Management Inventory Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 482

Part VIII Remote Management 483

35 Remote Management Overview 485

35.1 Remote Management Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 485

35.2 Understanding the Remote Management Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 485

35.2.1 Understanding Remote Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 486

35.2.2 Understanding Remote View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 486

35.2.3 Understanding Remote Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 486

36 Setting Up Remote Management 487

36.1 Configuring the Remote Management Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487

Contents 13

36.1.1 Configuring Remote Management Settings at the Zone Level . . . . . . . . . . . . . . . . 487

36.1.2 Configuring Remote Management Settings at the Folder Level . . . . . . . . . . . . . . . 489

36.1.3 Configuring Remote Management Settings at the Device Level . . . . . . . . . . . . . . . 489

36.2 Configuring Remote Management Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 490

36.2.1 Setting Up the Remote Management Agent Password on the Managed Device . . 490

36.2.2 Clearing the Remote Management Agent Password. . . . . . . . . . . . . . . . . . . . . . . . 491

36.2.3 Clearing Remote Management Agent Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . 491

36.3 Starting Remote Management Operations Using the ZENworks Control Center. . . . . . . . . . 491

36.3.1 Initiating a Remote Management Session from Common Tasks. . . . . . . . . . . . . . . 491

36.3.2 Initiating a Remote Management Session from the Device Context . . . . . . . . . . . . 492

36.4 Starting Remote Management Operations Using the Native VNCViewer . . . . . . . . . . . . . . . 493

36.4.1 Starting Remote Management Operations Using the Windows VNC Viewer . . . . . 494

36.4.2 Starting Remote Management Operations Using the Linux VNC Viewer . . . . . . . . 494

36.5 Establishing SSH Tunneling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495

36.6 Improving Remote Management Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495

Part IX Event Monitoring 497

37 Event Monitoring Overview 499

novdocx (en) 11 July 2008

37.1 Event Monitoring Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 499

37.2 Monitoring Device Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 500

37.3 Monitoring Policy Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 500

37.4 Monitoring Bundle Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 500

37.5 Using the Hot List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 500

37.6 Backing Up the Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 501

38 Working with Event Logs 503

38.1 The Event Log Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 503

38.2 Working with the Log Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 505

38.2.1 Viewing an Event Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 505

38.2.2 Acknowledging an Event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 506

38.2.3 Using the Advanced Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 508

38.2.4 Clearing the Event Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 508

39 Message Logger 511

39.1 What Is Message Logger? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 511

39.2 Message Severity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 511

39.3 Message Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 511

39.4 Debugging and Logging ZMD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 512

39.5 Viewing the Debug Logs on ZENworks Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 512

40 Configuring Message Logger Settings 513

40.1 Configuring Message Logger Settings for the Primary Server. . . . . . . . . . . . . . . . . . . . . . . . 513

40.1.1 Configuring Database Maintenance Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 513

40.1.2 Configuring Centralized Log Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 514

40.1.3 Configuring SMTP Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 514

40.1.4 Configuring SNMP Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515

40.2 Configuring Message Logger Settings for a Managed Device. . . . . . . . . . . . . . . . . . . . . . . . 516

40.2.1 Configuring Local Log Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 516

40.2.2 Configuring System Log Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 517

14 Novell ZENworks 7.2 Linux Management Administration Guide

Part X Reports 519

41 Reports Overview 521

41.1 Bundle Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 521

41.2 Dell Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 521

41.3 Device Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 522

42 Generating ZENworks Reports 523

42.1 Creating a Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 523

42.2 Creating a Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 524

42.2.1 Using Templates to Create Dell Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 527

42.3 Organizing Reports and Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 527

42.3.1 Editing the Reports List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 527

42.3.2 Deleting a Report or Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 528

42.4 Modifying Report Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 528

42.5 Generating Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529

42.6 Exporting Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529

42.7 Resetting Default Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 530

novdocx (en) 11 July 2008

Part XI Appendixes 531

A Command Line Utilities 533

zmd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 534

zrmservice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 537

zlm-debug . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 538

zlmmirror . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 540

zlman . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 547

rug . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 571

B Bundle and Policy Schedules 585

B.1 No Schedule. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 585

B.2 Date Specific . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 585

B.3 Day of the Week Specific . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 586

B.4 Event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 587

B.5 Monthly. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 587

B.6 Relative to Refresh. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 588

C Naming Conventions in the ZENworks Control Center 589

D Imaging Utilities and Components 591

D.1 Image Explorer (imgexp.exe) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 591

D.1.1 Starting Image Explorer (imgexp.exe) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 592

D.1.2 Opening an Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 592

D.1.3 Adding a File or Folder to an Open Image. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 592

D.1.4 Creating a Folder in an Open Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 593

D.1.5 Excluding a File or Folder from a File Set in the Open Image . . . . . . . . . . . . . . . . . 593

D.1.6 Marking a File or Folder for Deletion in the Open Image. . . . . . . . . . . . . . . . . . . . . 593

D.1.7 Purging Files and Folders Marked for Deletion from the Open Image. . . . . . . . . . . 593

Contents 15

D.1.8 Extracting a File or Directory from the Open Image to a Folder . . . . . . . . . . . . . . . 593

D.1.9 Extracting a File or Directory from the Open Image As an Add-On Image . . . . . . . 593

D.1.10 Viewing a File from the Open Image in its Associated Application . . . . . . . . . . . . . 594

D.1.11 Saving Your Changes to the Open Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 594

D.1.12 Creating an Add-On Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 594

D.1.13 Adding a Partition to a New Add-On Image. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 594

D.1.14 Compressing an Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 594

D.1.15 Splitting an Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 595

D.1.16 Resizing a Partition in an Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 596

D.2 Novell ZENworks Linux Management Imaging Agent (novell-zislnx) . . . . . . . . . . . . . . . . . . . 596

D.3 Image-Safe Data Viewer and Editor (zisview and zisedit) . . . . . . . . . . . . . . . . . . . . . . . . . . . 597

D.3.1 Information Displayed by the Image-Safe Data Viewer . . . . . . . . . . . . . . . . . . . . . . 597

D.3.2 Using the Image-Safe Data Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 599

D.3.3 Using the Image-Safe Data Editor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 600

D.4 ZENworks Imaging Floppy Boot Disk Creator (zmediacreator.exe). . . . . . . . . . . . . . . . . . . . 601

D.5 Imaging Configuration Parameters (settings.txt) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 602

D.6 Imaging Boot Parameter for PCMCIA Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 605

D.7 Imaging Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 605

D.7.1 Initiating the Imaging Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 605

D.7.2 Viewing Information About Imaging Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 614

D.7.3 Starting a Manual Multicast Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 615

novdocx (en) 11 July 2008

E ZENworks Imaging Engine Commands 617

E.1 Help Mode (img help) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 617

E.2 Automatic Mode (img auto) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 618

E.3 Make Mode (img make) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 619

E.3.1 Make Locally (img makel) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 619

E.3.2 Make to Proxy (img makep) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 620

E.4 Restore Mode (img restore) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 621

E.4.1 Restore from Local (img restorel) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 622

E.4.2 Restore from Proxy (img restorep) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 624

E.5 Session (Multicast) Mode (img session). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 625

E.6 Partition Mode (img part) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 627

E.6.1 Using the ZENworks Imaging Engine Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 627

E.6.2 Using the Bash Prompt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 628

E.7 ZENworks Partition Mode (img zenPartition) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 628

E.8 Dump Mode (img dump) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 629

E.9 Information Mode (img info) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 630

F Updating ZENworks Imaging Resource Files 633

F.1 The Linux Distribution for Imaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 633

F.2 Understanding Device Boot Processes in a ZENworks Imaging Environment . . . . . . . . . . . 634

F.2.1 linuxrc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 634

F.2.2 zenworks.s. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 635

F.3 Understanding ZENworks Partitions and Command Line Parameters . . . . . . . . . . . . . . . . . 635

F.3.1 The ZENworks Partition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 635

F.3.2 Command Line Parameters and Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 636

F.4 Modifying ZENworks Imaging Resource Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 636

F.4.1 Adding Files to an Imaging Boot CD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 637

F.4.2 Adding Files to the Initrd or Root File Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . 638

F.4.3 Using the Driverupdate File Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 640

F.5 Adding or Updating LAN Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 642

F.5.1 Obtaining Drivers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 642

16 Novell ZENworks 7.2 Linux Management Administration Guide

F.5.2 Building Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 643

F.5.3 Loading Drivers with Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 644

F.6 Using Uname . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 644

F.7 Variables and Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 645

F.7.1 Imaging Script Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 646

F.7.2 Linuxrc Parameters Specified in Settings.txt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 646

F.7.3 Image Engine Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 647

F.8 Troubleshooting Linux Driver Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 647

F.8.1 Troubleshooting During the Boot Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 647

F.8.2 Troubleshooting at the Bash Prompt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 648

G Upgrading the Dell DTK 649

H Supported Ethernet Cards 651

I Using a Specific Network Card for Devices Running Dual NICs 653

J Establishing SSH Tunneling 655

novdocx (en) 11 July 2008

J.1 SSH Tunneling between a Linux Management Console and a Linux Managed Device . . . . 655

J.1.1 Basic Use. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 655

J.2 SSH Tunneling between a Windows Management Console and a Linux Managed Device . 656

J.3 Compression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 657

K License Agreement for libacl and libgconf 659

K.1 Library GNU Public License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 659

L Documentation Updates 665

L.1 September 25, 20 (Hot Patch 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 665

L.1.1 Package and Content Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 665

L.2 July 28, 2008 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 666

L.2.1 Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 666

L.3 June 26, 2008 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 666

L.3.1 Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 666

L.4 May 19, 2008 (Interim Release 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 666

L.4.1 ZENworks System Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 667

L.4.2 Package and Content Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 667

L.4.3 Preboot Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 667

L.4.4 Event Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 668

L.4.5 Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 668

L.5 January 11, 2008 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 668

L.5.1 Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 668

L.6 October 16, 2007 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 668

L.6.1 Package and Content Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 669

L.6.2 Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 669

L.7 September 3, 2007. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 669

L.7.1 Event Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 669

L.7.2 Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 669

L.8 August 23, 2007 (Interim Release 1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 670

L.8.1 ZENworks System Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 670

L.8.2 Package and Content Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 670

L.8.3 Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 670

Contents 17

L.9 June 11, 2007 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 671

L.9.1 Package and Content Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 671

L.9.2 Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 671

L.10 June 2, 2007 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 671

L.10.1 Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 671

L.11 May 18, 2007 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 672

L.11.1 ZENworks System Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 672

L.11.2 Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 672

L.12 April 13, 2007 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 672

L.12.1 ZENworks System Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 672

L.12.2 Device Registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 673

L.12.3 Policy Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 673

L.12.4 Package and Content Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 673

novdocx (en) 11 July 2008

18 Novell 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 Guide 19

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

20 Novell 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

22 Novell 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.

24 Novell 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 Features 25

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.

26 Novell 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 Features 27

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.

28 Novell 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 Features 29

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, CD­ROM 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.

30 Novell ZENworks 7.2 Linux Management Administration Guide

1.9 Managing Remote Devices

Sometimes you need to physically perform a task on a remote workstation or server. To do so,
ZENworks lets you remotely manage a device through the ZENworks Control Center. When
remotely managing a device, there are three modes of operation: Remote Control, Remote View, and
Remote Login.

 Remote Control: Lets you take control of the device's desktop and perform tasks as if you

were physically located at the device.

 Remote View: Lets you observe the device's desktop and activity.

 Remote Login: Lets you log in to the device, opening a new graphical session without

disturbing the user on the device. The user cannot view your Remote Login session.

To manage a remote device:

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 In the Workstation Tasks list or Servers Tasks list (located in the upper left corner of the

ZENworks Control Center), click Remote Control Workstation or Remote Control Server to
open the Remote Management dialog box.

5 Select the remote management operation you want to perform: Remote Control, Remote View,

or Remote Login, then click OK.

novdocx (en) 11 July 2008

The remote session appears. If you receive an error message stating that additional plug-ins are
required, see “Administration Workstation Requirements” in the Novell ZENworks 7.2 Linux

Management Installation Guide.

For more information about managing remote devices, see “Remote Management” on page 483.

1.10 Monitoring Events

The ZENworks system generates messages each time a management task is performed. For
example, when the ZENworks Agent enforces a policy on a device, it generates an event message.
Or, when the ZENworks Server is unable to register a new device, it generates an event message.
Depending on the severity level (normal, warning, or critical) of the event and the item type (device,
bundle, policy, etc.) for which the event was generated, the event can be displayed in various
locations in the ZENworks Control Center.

The following sections provide a brief overview of event monitoring and message logging:

 Section 1.10.1, “Hot List,” on page 32

 Section 1.10.2, “Event Log,” on page 32

 Section 1.10.3, “System Event Log,” on page 32

 Section 1.10.4, “Message Logs,” on page 32

For more information about message logs, see Part IX, “Event Monitoring,” on page 497.

A Quick Tutorial on Basic ZENworks Linux Management Features 31

1.10.1 Hot List

The Hot List displays all events that generated an error (critical or warning). An error event remains
in the list until you acknowledge it.

To access the Hot List:

1 In the ZENworks Control Center, click the Home tab.

1.10.2 Event Log

Each device, policy, and bundle has an Event Log that displays all of the event messages generated
for the item, regardless of severity level (normal, warning, or critical).

The Event Log for a device displays all events that applied to the device. For example, if a bundle or
policy is applied to the device, the Event Log displays a message for the event.

The Event Log for a bundle or policy displays all events that applied to the bundle or policy. For
example, if a bundle is individually applied to four devices, four messages are displayed in the Event
Log, one for each device.

novdocx (en) 11 July 2008

To access an Event Log:

1 In the ZENworks Control Center, click the Devices tab, Bundles tab, or Policies tab, depending

on whether you want to view events for a device, bundle, or policy.

2 Click the desired device, bundle, or policy to display its Summary page.

The Event Log is located near the bottom of the Summary page.

1.10.3 System Event Log

Each ZENworks Server has a System Event Log that displays all of the event messages generated
for tasks performed by the server, regardless of the event's severity level (normal, warning, or
critical). For example, it displays messages for all bundles that the server has applied to devices that
it manages.

To access a System Event Log:

1 In the ZENworks Control Center, click the Devices tab, then click a ZENworks Server to

display its Summary page.

The System Event Log is located near the bottom of the Summary page.

1.10.4 Message Logs

The events that are displayed in the ZENworks Control Center can also be logged to files on disk.
The ZENworks Agent can log event messages (the ones that appear in a device's Event Log) to a file
on the device's local disk; message logs for all managed devices can also be rolled up to a central log
file on the ZENworks Server.

The ZENworks Server can log messages (the ones that appear in the server's System Event Log) to a
file on the server's local disk.

For more information about message logs, see Part IX, “Event Monitoring,” on page 497.

32 Novell ZENworks 7.2 Linux Management Administration Guide

1.11 Generating Reports

You can generate reports to display bundle and device information, such as the bundle delivery
information for each device or the devices registered in the last 24 hours. The ZENworks Control
Center provides several predefined reports and lets you create new reports. You can export the
reports to XML, CVS, or HTML formats.

ZENworks Linux Managements lets you generate reports specific to your Dell PowerEdge servers.

To generate a report:

1 In the ZENworks Control Center, click the Reports tab.

The Reports list includes three default folders: Bundle Reports, Dell Reports, and Device
Reports. Each of these folders contains a set of predefined reports you can run. You can also
run all of the reports in a folder by selecting the folder.

2 Select the Device Reports folder by clicking the box in front of it.

3 Click Generate to generate the six device reports.

You can print each of the reports. You can also export them to XML, CSV, and HTML
formatted files.

novdocx (en) 11 July 2008

For more information about reports, see Part X, “Reports,” on page 519.

A Quick Tutorial on Basic ZENworks Linux Management Features 33

novdocx (en) 11 July 2008

34 Novell ZENworks 7.2 Linux Management Administration Guide

2

Using ZENworks Linux

novdocx (en) 11 July 2008

Management with Dell PowerEdge
Servers

By combining Novell® ZENworks® Linux Management capabilities with the Dell OpenManage
toolkit capabilities, you can configure and manage your Dell PowerEdge servers from out of the box
through the entire server life cycle. Whether you use SUSE
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.

ZENworks Linux Management provides the following features to help you deploy and manage Dell
PowerEdge servers in your ZENworks system:

 Section 2.1, “Configuring PowerEdge Servers using Dell Configuration Bundles,” on page 35

 Section 2.2, “Obtaining, Configuring, and Updating PowerEdge Servers Using Dell Update

Package Bundles,” on page 36

 Section 2.3, “Using Advanced Dell Inventory Information,” on page 38

 Section 2.4, “Using Advanced Dell Inventory Reports,” on page 38

2.1 Configuring PowerEdge Servers using Dell

®

Linux Enterprise Server or Red Hat

2

Configuration Bundles

Dell Configuration bundles let you configure the BIOS, BMC, RAID, and DRAC settings on Dell
PowerEdge servers and create a Dell utility partition. You can also select to run another Preboot
Services bundle after these configurations are complete. Dell Configuration bundles let you
configure a bare-metal PowerEdge server and quickly and easily put the server into production.

To create a Dell Configuration bundle:

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 Select Preboot bundle, then click Next.

4 Select Dell Configuration bundle, then click Next.

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

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 a Dell Configuration policy to configure Dell
PowerEdge servers, see Section 30.5, “Using Dell Configuration Bundles,” on page 444.

Using ZENworks Linux Management with Dell PowerEdge Servers

35

2.2 Obtaining, Configuring, and Updating PowerEdge Servers Using Dell Update Package Bundles

Dell Update Package bundles let you update and configure hardware and system settings (including
BIOS, DRAC, RAID, BMC, and FRMW configurations) on Dell PowerEdge servers. After you
obtain Dell Update Packages from Dell by using the mirroring capabilities of ZENworks Linux
Management, you can easily assign the Dell Update Package bundles that are automatically created
to PowerEdge servers in your ZENworks system. It is easy for you to determine if an updated Dell
Update Package is available for PowerEdge servers in your system and deliver the update.
ZENworks Linux Management helps you manage and update your PowerEdge servers though the
entire server lifecycle.

The following sections contain additional information:

 Section 2.2.1, “Obtaining Dell Update Packages from Dell,” on page 36

 Section 2.2.2, “Assigning Dell Update Package Bundles to Configure and Update PowerEdge

Servers,” on page 36

 Section 2.2.3, “Determining If Newer Dell Package Updates Are Available for PowerEdge

Servers,” on page 37

novdocx (en) 11 July 2008

 Section 2.2.4, “Deploying a Newer Dell Update Package,” on page 38

2.2.1 Obtaining Dell Update Packages from Dell

You can mirror Dell Update Packages from the Dell FTP site to your ZENworks server or you can
mirror the CDs you receive from Dell Support.

Dell Update Packages let you update and configure hardware and system settings (including BIOS,
DRAC, RAID, BMC, and FRMW configurations) on Dell PowerEdge servers.

To mirror Dell Update Packages from the Dell FTP site or from a CD, you create and configure an
XML configuration file and then use the zlmmirror command line utility. The first time you mirror
Dell Update Packages, all available packages are mirrored; subsequent mirror sessions obtain
upgraded packages only. After the mirroring operation is complete, the Dell Update Packages are
automatically bundled and display in the ZENworks Control Center on the Bundles page. You then
assign the Dell Update Package bundles to devices just as you would with other bundles.

For more detailed information and step-by-step instructions, see Section 25.5, “Mirroring Dell

Update Packages to Your ZENworks Server,” on page 305

2.2.2 Assigning Dell Update Package Bundles to Configure and Update PowerEdge Servers

After the mirroring operation is complete, the Dell Update Packages are automatically bundled and
display in the ZENworks Control Center on the Bundles page. To install them on PowerEdge servers
in your ZENworks system, you must assign them to devices using the Assign Bundle Wizard in the
ZENworks Control Center.

36 Novell ZENworks 7.2 Linux Management Administration Guide

To assign a Dell Update Package bundle:

1 In the ZENworks Control Center, click the Bundles tab, then click the underlined link next to

the folder containing the Dell Update Packages that was created during the mirroring process.

2 Select the desired Dell Update Package bundle by clicking the box next to its name, click

Action, then click Assign Bundle to launch the Assign Bundle Wizard.

3 Follow the prompts to create the Dell Update Package 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 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, see Section 23.2, “Assigning Dell Update Package Bundles,” on

page 279.

2.2.3 Determining If Newer Dell Package Updates Are Available for PowerEdge Servers

novdocx (en) 11 July 2008

After you run a mirror session and obtain updated Dell Update Packages, it is easy to determine if a
newer Dell Update Package is available for installation on Dell PowerEdge servers in your
ZENworks system.

To determine if there are updated Dell Update Package bundles available for the servers in your
system:

1 In the ZENworks Control Center, click the Devices tab, then click Servers.

A link in the Dell Updates column indicates whether there is a Dell Update Package bundle
available in the ZENworks package repository for each Dell PowerEdge server in the list. An
update is available in the following situations:

 If a Dell Update Package exists in the ZENworks package repository but it is not assigned

to that specific server model.

 If a specific Dell Update Package is already assigned to the device, but an updated

package has been mirrored and is available in the ZENworks package repository.

2 Click the link to view the name of the Dell Update Package bundle appropriate for the device.

3 If the appropriate Dell Update Package bundle is not yet assigned to the device, continue with

Section 23.2, “Assigning Dell Update Package Bundles,” on page 279.

or

If the appropriate Dell Update Package bundle is already assigned to the device, continue with

Section 23.4, “Deploying an Updated Version of a Dell Update Package Bundle,” on page 283.

For more information, see Section 23.3, “Determining If Newer Dell Package Updates Are

Available for PowerEdge Servers,” on page 283

Using ZENworks Linux Management with Dell PowerEdge Servers 37

2.2.4 Deploying a Newer Dell Update Package

If a specific Dell Update Package is already assigned to the device, but an updated package has been
mirrored and is available in the ZENworks package repository, you can deploy the updated version
of the package.

1 In the ZENworks Control Center, click the Bundles tab, click the underlined link next to the

folder containing the Dell Update Packages that was created during the mirroring process.

2 Click the underlined link in the Name column to display the bundle’s Summary page.

3 Click the Details page.

4 Use the Version drop-down list to select the desired version number, then click Deploy.

For more information, see Section 23.4, “Deploying an Updated Version of a Dell Update Package

Bundle,” on page 283.

2.3 Using Advanced Dell Inventory Information

Advanced Dell inventory information lets you display inventory information specific to Dell
PowerEdge servers. This advanced inventory information helps you determine when PowerEdge
configuration settings need to be updated.

novdocx (en) 11 July 2008

For more information, see Chapter 33, “Reviewing the Device Inventory,” on page 473.

2.4 Using Advanced Dell Inventory Reports

Advanced Dell reports let you run reports specific to Dell PowerEdge servers to find devices that do
not have valid Dell Update Packages installed or to show devices with Dell applications installed
(per device or per device model).

For more information, see Section 42.2.1, “Using Templates to Create Dell Reports,” on page 527.

38 Novell ZENworks 7.2 Linux Management Administration Guide

II

ZENworks System Management

The following sections provide information about general Novell® ZENworks® Linux Management
features and procedures:

 Chapter 3, “ZENworks Control Center,” on page 41

 Chapter 4, “Command Line Administration Utilities,” on page 45

 Chapter 5, “ZENworks Server,” on page 47

 Chapter 6, “ZENworks Agent,” on page 53

 Chapter 7, “Configuring Management Zone Settings,” on page 67

 Chapter 8, “ZENworks Administrator Accounts,” on page 79

 Chapter 9, “ZENworks Object Store and Data Store Maintenance,” on page 83

novdocx (en) 11 July 2008

II

ZENworks System Management

39

novdocx (en) 11 July 2008

40 Novell ZENworks 7.2 Linux Management Administration Guide

3

ZENworks Control Center

You use the Novell® ZENworks® Control Center to configure system settings and management
tasks in your ZENworks Management Zone. The following sections provide information about the
ZENworks Control Center:

 Section 3.1, “Where the ZENworks Control Center Is Installed,” on page 41

 Section 3.2, “Accessing the ZENworks Control Center,” on page 41

 Section 3.3, “Accessing the ZENworks Control Center through Novell iManager,” on page 42

 Section 3.4, “Changing the Timeout Value for the ZENworks Control Center,” on page 42

 Section 3.5, “Changing the Debug Settings of ZENworks Control Center,” on page 43

ZENworks Linux Management also includes the zlman command line utility to help you manage
your ZENworks system. The zlman utility lets you perform the same tasks you can perform in the
ZENworks Control Center, with the exception of imaging and preboot tasks. For more information,
see Section 4.1, “zlman,” on page 45.

novdocx (en) 11 July 2008

3

3.1 Where the ZENworks Control Center Is Installed

The ZENworks Control Center is installed on all ZENworks Servers in the Management Zone.

You can perform all management tasks on the primary server and most management tasks on the
secondary servers. The one management exception on secondary servers is the manipulation
(adding, deleting, modifying) of packages in a bundle. This task is not supported because the
primary server is the source server for packages, meaning that packages are replicated from the
primary server to secondary servers on a regularly scheduled basis. Manipulating a package on a
secondary server rather than on the primary server would result in the modified package being
replaced (or removed) the next time the secondary server's packages were updated from the primary
server. For more information about replication of packages, see Chapter 24, “Replicating Content in

the ZENworks Management Zone,” on page 287.

3.2 Accessing the ZENworks Control Center

1 Using a Web browser that meets the requirements listed in “Administration Workstation

Requirements” in the Novell ZENworks 7.2 Linux Management Installation Guide, enter the

following URL:

https://ZENworks_Server_Address

Replace ZENworks_Server_Address with the IP address or DNS name of the ZENworks
Server.

The ZENworks Control Center requires an https:// connection; requests to http:// are redirected
to https://.

2 When prompted for login credentials, use the Administrator user with the password you

provided during the installation.

ZENworks Control Center

41

3.3 Accessing the ZENworks Control Center through Novell iManager

ZENworks Linux Management includes a Novell plug-in module (.npm) that you can use to access
the ZENworks Control Center from Novell iManager, which is a management console used by a
number of other Novell products.

To install the ZENworks Control Center plug-in for iManager:

1 Copy the plug-in (zlm7link.npm) from the Novell ZENworks 7.2 Linux Management CD to

a location on your iManager server.

The zlm7link.npm file is located in the /ImanagerPlugin directory.

2 Follow the instructions in the Novell iManager 2.6 documentation (http://www.novell.com/

documentation/imanager26/) to install and configure the plug-in module.

3 If Tomcat did not restart during the installation and configuration process, restart Tomcat.

4 Log into iManager.

5 Click the ZENworks icon at the top of the page.

6 Enter the ZENworks Control Center URL:

https://ZENworks_Server_Address

novdocx (en) 11 July 2008

Replace ZENworks_Server_Address with the IP address or DNS name of the ZENworks
Server.

7 Click the ZENworks icon to launch the ZENworks Control Center.

3.4 Changing the Timeout Value for the ZENworks Control Center

By default, the ZENworks Control Center has a 30-minute timeout value. If you leave the
ZENworks Control Center idle on your computer for more than 30 minutes, you are prompted to log
in again before continuing. You can increase or decrease the timeout value, or you can specify that
the ZENworks Control Center never times out.

To change the timeout value:

1 Open the /var/opt/novell/zenworks/www/tomcat/base/webapps/

zenworks/WEB-INF/config.xml file in a text editor.

2 Increase or decrease the timeout value, as needed.

or

Specify -1 to specify that the ZENworks Control Center never times out.

3 Save the config.xml file.

4 Restart the service by executing the following command:

/etc/init.d/novell-zenserver restart

42 Novell ZENworks 7.2 Linux Management Administration Guide

3.5 Changing the Debug Settings of ZENworks Control Center

To change the debug settings of ZENworks Control Center:

1 Open the /var/opt/novell/zenworks/www/tomcat/base/webapps/

zenworks/WEB-INF/config.xml file in a text editor.

2 Make sure that the value of debug.enabled is set to True. (By default, the option is set to

True.)

The error messages logged by using WebLogger.debug() are written to the standard output.

3 (Optional) Set the value of debug.tags is set to any of the following values:

rpcToServer
controlTree
snapshotTimes
pageLoadTime
requestParams
viewStateManager
RemoteManagement
WebFramew ork
mirrorStatus

The error messages logged to WebLogger.debugForTag() are written to the standard output.

4 Save the config.xml file.

novdocx (en) 11 July 2008

5 Restart the service by executing the following command:

/etc/init.d/novell-zenserver restart

ZENworks Control Center 43

novdocx (en) 11 July 2008

44 Novell ZENworks 7.2 Linux Management Administration Guide

4

Command Line Administration

novdocx (en) 11 July 2008

Utilities

Novell® ZENworks® Linux Management includes several command line utilities to help you
manage your ZENworks system. The primary purpose of the command line utilities is to provide
access to the ZENworks management functionality in a scriptable environment.

The following command line utilities are available:

 Section 4.1, “zlman,” on page 45

 Section 4.2, “zlm-debug,” on page 45

 Section 4.3, “zlmmirror,” on page 46

 Section 4.4, “rug,” on page 46

 Section 4.5, “zmd,” on page 46

 Section 4.6, “zrmservice,” on page 46

4.1 zlman

The zlman utility lets you perform the same tasks you can perform in the ZENworks Control Center,
with the exception of imaging and preboot tasks. It is installed on ZENworks Servers in the
following location:

4

/opt/novell/zenworks/bin

For more information about zlman, view the zlman man page (man zlman) on the ZENworks Server
or see zlman (1) (page 547).

4.2 zlm-debug

The zlm-debug utility lets you gather information to help you troubleshoot and solve problems you
encounter using ZENworks Linux Management. By default, zlm-debug gathers cache, server, client,
configuration, hardware, and package data as well as log files. The information is packaged into a
tarball file and placed in the location you specify. It is installed on ZENworks Server and managed
devices in the following location:

/opt/novell/zenworks/bin

By default, zlm-debug creates a tarball, zlm-debug-

yearmonthdate_of_file_creation.tgz in the /tmp directory.

For more information about zlm-debug, view the zlm-debug man page (man zlm-debug) on the
ZENworks Server or see zlm-debug (1) (page 538).

Command Line Administration Utilities

45

4.3 zlmmirror

The zlmmirror utility lets you mirror RPM and Dell Update Packages packages from ZENworks 6.x
and 7 servers, Dell FTP servers, YaST Online Update (YOU) servers, Red Hat Network, and Red

®

Carpet

/opt/novell/zenworks/bin

For more information about zlmmirror, view the zlmmirror man page (man zlmmirror) on the
ZENworks Server, see zlmmirror (1) (page 540), or see Chapter 25, “Mirroring Software,” on

page 289.

Enterprise servers. It is installed on ZENworks Servers in the following location:

4.4 rug

The rug utility lets you perform software and user management through the ZENworks Agent on a
managed device. It is installed on managed devices in the following location:

/opt/novell/zenworks/bin

For SUSE LINUX Enterprise Server 10 (SLES 10) and SUSE LINUX Enterprise Desktop 10
(SLED 10) devices, the rug utility is located in the following directory:

novdocx (en) 11 July 2008

/usr/bin

For more information about rug, view the rug man page (man rug) on a managed device or see rug

(1) (page 571).

4.5 zmd

The zmd utility lets you control how the ZENworks Agent runs on a managed device. It is installed
on managed devices in the following location:

/opt/novell/zenworks/sbin

For SUSE LINUX Enterprise Server 10 (SLES 10) and SUSE LINUX Enterprise Desktop 10
(SLED 10) devices, the ZENworks Agent is located in the following directory:

/usr/sbin

For more information about zmd, view the zmd man page (man zmd) on a managed device or see

zmd (8) (page 534).

4.6 zrmservice

The zrmservice utility lets you control how the ZENworks Remote Management Agent (a
component of the ZENworks Agent) runs on a managed device. It is installed on managed devices in
the following location:

/opt/novell/zenworks/sbin

For more information about zrmservice, view the zrmservice man page (man zrmservice) on a
managed device or see zrmservice (1) (page 537).

46 Novell ZENworks 7.2 Linux Management Administration Guide

5

ZENworks Server

The Novell® ZENworks® Server is the backbone of the ZENworks system. It communicates with
the ZENworks Agent on managed devices to deliver software, enforce policies, collect inventory,
and perform other management tasks. The following sections provide information about the
ZENworks Server:

 Section 5.1, “ZENworks Services,” on page 47

 Section 5.2, “RPM Package Repository,” on page 49

 Section 5.3, “Uninstalling a ZENworks Server,” on page 50

 Section 5.4, “Freeing Disk Space on a ZENworks Server,” on page 52

5.1 ZENworks Services

The ZENworks Server includes the following services:

novdocx (en) 11 July 2008

5

Table 5-1 ZENworks Services

Service Service Name Description

eDirectory

PostgreSQL Database postgresql Used for the ZENworks Data Store; only

ZENworks Server novell-zenserver Used for communicating with the

ZENworks Loader novell-zenloader Used for loading modules not directly

ZENworks Server Management novell-zented Used for replicating RPM packages and

ZENworks Imaging Service novell-pbserv Used to provide imaging services to a

TM

ndsd Used for the ZENworks Object Store.

needed if the Data Store resides on the
ZENworks Server.

ZENworks Agent.

associated with the ZENworks Server.
This includes the Content Replication,
Inventory Rollup, and QueueRunner
modules.

Dell Update Packages from the primary
server to secondary servers.

device. This includes sending and
receiving image files, discovering
assigned Preboot bundles, acting as
session master for multicast imaging,
and so forth.

ZENworks Preboot Policy
Daemon

novell-zmgprebootpolicy Used by PXE-enabled devices to check

if there are any Preboot bundles that are
assigned to the device.

ZENworks Server

47

Service Service Name Description

Proxy DHCP Daemon novell-proxydhcp Used with a standard DHCP server to

inform PXE-enabled devices of the IP
address of the Novell TFTP server. It
also responds to PXE devices to indicate
which bootstrap program (nvlnbp.sys)
to use.

TFTP Daemon (TFTP Server) novell-tftp Used by PXE-enabled devices to

request files that are needed to perform
imaging tasks. It also provides a central
repository for these imaging files, such
as the Linux kernel and initrd. A PXE­enabled device uses this server to
download the bootstrap program
(nvlnbp.sys).

novdocx (en) 11 July 2008

ZENworks Management Daemon
(ZENworks Agent)

ZENworks Imaging Agent novell-zislnx Used to save and restore image-safe

novell-zmd Used to enable the server as a managed

device.

data on the server (as a managed
device). Only runs when launched by the
ZENworks Agent.

The services reside in the /etc/init.d directory on the ZENworks Server. Refer to the
following sections for instructions to help you control the ZENworks services:

 Section 5.1.1, “Checking the Status of a ZENworks Service,” on page 48

 Section 5.1.2, “Starting a ZENworks Service,” on page 48

 Section 5.1.3, “Stopping a ZENworks Service,” on page 49

 Section 5.1.4, “Restarting a ZENworks Service,” on page 49

5.1.1 Checking the Status of a ZENworks Service

To check the current status of a service, use the following command:

/etc/init.d/servicename status

Replace servicename with the name of the service as listed in Table 5-1 on page 47.

To check the current status of all services, use the following command:

/opt/novell/zenworks/bin/zlm-config --status

5.1.2 Starting a ZENworks Service

To start a service, use the following command:

/etc/init.d/servicename start

Replace servicename with the name of the service as listed in Table 5-1 on page 47.

To start all services, use the following command:

48 Novell ZENworks 7.2 Linux Management Administration Guide

/opt/novell/zenworks/bin/zlm-config --start

To ensure that all services start in the correct order, we recommend that you use the zlm-config

--start option to start all services rather than starting them one at a time.

5.1.3 Stopping a ZENworks Service

To stop a service, use the following command:

/etc/init.d/servicename stop

Replace servicename with the name of the service as listed in Table 5-1 on page 47.

To stop all services, use the following command:

/opt/novell/zenworks/bin/zlm-config --stop

5.1.4 Restarting a ZENworks Service

To restart a service that is already running, use the following command:

novdocx (en) 11 July 2008

/etc/init.d/servicename restart

Replace servicename with the name of the service as listed in Table 5-1 on page 47.

To restart all services, use the following command:

/opt/novell/zenworks/bin/zlm-config --restart

To ensure that all services start in the correct order, we recommend that you use the zlm-config

--restart option to restart all services rather than restarting only one service.

5.2 RPM Package Repository

The ZENworks Server contains all of the RPM packages and Dell Update Packages that are
included in bundles defined within your Management Zone.

The following sections contain more information:

 Section 5.2.1, “Package Repository Location,” on page 49

 Section 5.2.2, “Package Replication,” on page 50

 Section 5.2.3, “Package Administration,” on page 50

5.2.1 Package Repository Location

The package repository is the /var/opt/novell/zenworks/pkg-repo directory on the
ZENworks Server. When you add an RPM package to a bundle, the package is automatically
uploaded to the package repository. When you mirror Dell Update Packages, the packages are
automatically bundled and uploaded to the package repository.

ZENworks Server 49

5.2.2 Package Replication

To ensure that all ZENworks Servers have the same RPM packages and Dell Update Package
bundles to distribute, the ZENworks Primary Server can replicate all packages to any ZENworks
Secondary Servers in the Management Zone. To enable replication, you need to establish a
replication schedule (see Chapter 24, “Replicating Content in the ZENworks Management Zone,”

on page 287).

During replication of packages to a secondary server, only new packages and updates to existing
packages are sent.

5.2.3 Package Administration

Because of the way that packages are replicated from the primary server to secondary servers, you
must run the ZENworks Control Center or zlman utility from the primary server to add a package to
a bundle. Doing so causes the package to be added to the primary server's package repository and
then be replicated to all secondary servers.

If you add a package to a secondary server, the package does not exist on the primary server and is
therefore removed the next time the primary server replicates its packages to the secondary server.

novdocx (en) 11 July 2008

The same limitation applies to all package management tasks, such as modifying and deleting a
package from a bundle. These tasks must be performed on the primary server.

5.3 Uninstalling a ZENworks Server

ZENworks includes a uninstall program (zlm-uninstall) to remove the ZENworks services, Object
Store, and other files from a server. If for some reason the uninstall program cannot remove the
ZENworks server software, you can manually uninstall the software. The following sections provide
instructions for uninstalling the software with the uninstall program or manually.

If your ZENworks Linux Management system has secondary servers, you must uninstall the
secondary servers before uninstalling the primary ZENworks server. Otherwise, during
uninstallation of the secondary servers, you receive an error message concerning eDirectory that is
not applicable because eDirectory was already removed during uninstallation of the primary
ZENworks server.

The following sections contain more information:

 Section 5.3.1, “Uninstalling a Primary ZENworks Server Using zlm-uninstall,” on page 50

 Section 5.3.2, “Uninstalling a Secondary ZENworks Server Using zlm-config,” on page 51

 Section 5.3.3, “Manually Uninstalling a Primary or Secondary ZENworks Server,” on page 51

5.3.1 Uninstalling a Primary ZENworks Server Using zlm­uninstall

1 Make sure you know the password for the ZENworks Administrator account.

2 Log in to the ZENworks Server as root.

3 Run the following command:

50 Novell ZENworks 7.2 Linux Management Administration Guide

/opt/novell/zenworks/bin/zlm-uninstall

4 Follow the prompts.

5.3.2 Uninstalling a Secondary ZENworks Server Using zlm­config

1 Make sure you know the password for the ZENworks Administrator account.

2 Log in to the Primary ZENworks Server as root.

3 Run the following command:

/opt/novell/zenworks/bin/zlm-config --remove-secondary­server=secondary_server

where secondary_server is the full NDS context of the secondary server.

The server is usually in the system context. For example, if your server name is ZEN216, the
full command is:

/opt/novell/zenworks/bin/zlm-config --remove-secondary­server=zen216.system

novdocx (en) 11 July 2008

5.3.3 Manually Uninstalling a Primary or Secondary ZENworks Server

1 Stop the services on the ZENworks Server. If necessary, see Section 5.1.3, “Stopping a

ZENworks Service,” on page 49.

2 Remove the following directories:

/opt/novell/zenworks/share/keystore

/opt/novell/zenworks/datamodel/share/ldap-certs

/etc/opt/novell/zenworks/serverid

/etc/opt/novell/zenworks/serversecret

3 Edit /etc/crontab to remove the lines that contain ZENworks.

4 (Conditional) If you are removing a secondary server, remove the secondary server object from

the Object Store and Data Store. To do so:

4a Create a script file like the following one to create a CLASSPATH variable that includes

all of the paths to the ZENworks classes:

#!/bin/sh
CLASSPATH=''
for i in ‘ls /opt/novell/zenworks/java/lib/*.jar‘ ;
do CLASSPATH="$i:$CLASSPATH" ;
done ;
for i in ‘ls /opt/novell/extend/Common/WSSKD/lib/*.jar‘ ;
do CLASSPATH=$i:$CLASSPATH" ;
done ;
echo $CLASSPATH

4b Use the following command to remove the ZENworks secondary server object:

/opt/novell/zenworks/lib/java/bin/java -classpath $CLASSPATH
com.novell.zenworks.datamodel.extensions.installer.LDAPInsta
ller uninstall admin_password

ZENworks Server 51

Replace admin_password with the ZENworks Administrator account password.

5 (Conditional) If you are removing the primary server and are using a local PostgreSQL

database for the ZENworks Data Store, remove the database. To do so, use the following
commands:

/etc/init.d/postgresql start, su - postgres , dropdb zenworks ,
dropuser zenadmin , /etc/init.d/postgresql stop

6 Remove the ZENworks Object Store. To do so, use the following commands:

ndsconfig rm -F -a admin.system -w admin_passwordrm -rf /var/
nds/dibrm /etc/nds.conf

Replace admin_password with the ZENworks Administrator account password.

7 Remove the ZENworks RPM packages and the Dell Update Packages, if necessary. To do so:

7a Use the following command to list the package names:

rpm -qa | grep novell-zenworks

7b Remove each of the packages individually using the following command:

rpm -e | package_name

novdocx (en) 11 July 2008

or

Use the following simple script to remove multiple packages:

for i in ‘rpm -qa | grep novell-zenworks‘ ; do rpm -e $i ; done

Because of package dependencies, you might need to run this script multiple times to
remove all packages. You can verify that all packages have been removed by running the
command in Step 7a.

8 Remove the following directories:

rm -rf /opt/novell/zenworks/

rm -rf /etc/opt/novell/zenworks/

rm -rf /var/opt/novell/zenworks/

5.4 Freeing Disk Space on a ZENworks Server

You can clean up the ZENworks server disk space by either deleting or backing up the old log files.
For detailed information on how to back up the log files, see Section 37.6, “Backing Up the Log

Files,” on page 501.

You can also delete empty directories that might not be removed during the deletion of a package or
bundle. The directories are located at /var/opt/novell/zenworks/pkg-repo.

52 Novell ZENworks 7.2 Linux Management Administration Guide

6

ZENworks Agent

The Novell® ZENworks® Agent is installed on each managed device within your ZENworks
Management Zone. The agent communicates with the ZENworks Server to deliver software, enforce
policies, and perform other management tasks. The following sections provide information about
the ZENworks Agent:

 Section 6.1, “ZENworks Agent (zmd),” on page 53

 Section 6.2, “File System Access,” on page 54

 Section 6.3, “Using the Software Updater, Installer, and Remover from Users’ Managed

Devices,” on page 54

 Section 6.4, “Uninstalling the ZENworks Agent,” on page 66

6.1 ZENworks Agent (zmd)

novdocx (en) 11 July 2008

6

The ZENworks Agent is named zmd. It is sometimes referred to as the ZENworks Management
Daemon (zmd).

The ZENworks Agent performs software management functions on the ZENworks managed device,
including updating, installing, and removing software and performing basic queries of the device's
package management database. Typically, these management tasks are initiated through the
ZENworks Control Center or the rug utility, which means you should not need to interact directly
with the ZENworks Agent.

The ZENworks Agent is installed to the following directory:

/opt/novell/zenworks/sbin

For SUSE LINUX Enterprise Server 10 (SLES 10) and SUSE LINUX Enterprise Desktop 10
(SLED 10) devices, the ZENworks Agent is located in the following directory:

/usr/sbin

6.1.1 ZENworks Agent (zmd) Cache Settings

As the ZENworks Agent (zmd) performs its duties, it maintains a cache that stores the content of
bundles that are downloaded for installation on that managed device. You can control the age of
contents in the cache and its size by using cache settings. Cache cleanup is enforced on both client
startup and refresh.

If the process of downloading the bundle is interrupted on the managed device, the zmd starts the
download of individual packages from where it was left off.

The cleaning of cached information is always enabled. You can configure the following settings
using the rug set command in the rug utility to manage the cache. For more information about
the rug utility, see Section 4.4, “rug,” on page 46.

ZENworks Agent

53

Table 6-1 ZENworks Management Daemon Cache Settings

Setting Description

max-cache-age Defines the number of days the contents of the cache are retained, after

which the contents are deleted. The default is 30 days. If this setting
specifies 0 days, the cache content never expires.

The cache cleanup is enforced on client startup and refresh. The contents of
the cache are sorted by date (oldest to newest) and deleted by applying the
max-cache-age setting, starting with the oldest content.

To change the max-cache-age setting from the default of 30 days to 60
days, for example, you enter the following command from the managed
device:

rug set max-cache-age 60

cache-max-size-in-mb This setting is only enforced at cleanup time; not during bundle download.

The default is 300 MB. If this is set to 0, there is no limit to the size of the
cache; however, the max-cache-age setting still applies.

If the cache size exceeds the maximum size specified with this setting, the
cache contents are sorted by date and the oldest contents are deleted until
the cache size is within the specified size limit. If this size limit is exceed
while downloading bundles, the bundle contents are downloaded; however,
the next time the device restarts or refreshes, the cache is cleaned until its
size is within the specified size limit. The cache cleanup process will not
delete files downloaded within the last 24 hours to get within the specified
limit.

novdocx (en) 11 July 2008

To change the cache-max-size-in-mb setting from the default of 300 MB to
500 MB, for example, you enter the following command from the managed
device:

rug set cache-max-size-in-mb 500

6.2 File System Access

The ZENworks Agent runs as root. This provides it with the file system access required to perform
its management functions on the device.

On managed devices, do not mount the following directories over NFS: /etc, /opt, /usr, /
home, /var, and /root. The ZENworks Agent (zmd) is not designed to work with these
directories mounted over NFS, so this configuration is not supported.

6.3 Using the Software Updater, Installer, and Remover from Users’ Managed Devices

The ZENworks Linux Management Software Updater, Software Installer, and Software Remover
applets are components of the desktop that work through the ZENworks Agent.

In ZENworks Linux Management, these three easy-to-use desktop applets provide users with the
ability to update existing software, install new software, remove existing software from their
managed devices, and view and edit system preferences. These three desktop applets replace the
user interface clients used in previous versions of ZENworks Linux Management. Software Updater,

54 Novell ZENworks 7.2 Linux Management Administration Guide

Installer, and Remover provide users with a simple way to manage software, and the process is
integrated into the managed device’s desktop. If a rich user interface is required, you should use the
rug command line interface to accomplish these same tasks. For more information, see Section 4.4,

“rug,” on page 46.

novdocx (en) 11 July 2008

In previous versions of ZENworks Linux Management, these three applets were combined in one

®

user interface. In ZENworks Linux Management 6.x, the client interface was called Red Carpet

. In
ZENworks 7 Linux Management, the client interface was called the ZENworks Linux Management
Update Client. Software Updater, Installer, and Remover replace Red Carpet and the ZENworks
Linux Management Update Client.

The following sections contain information about each applet:

 Section 6.3.1, “Updating Software,” on page 55

 Section 6.3.2, “Installing Software,” on page 58

 Section 6.3.3, “Removing Software,” on page 61

 Section 6.3.4, “Viewing System Preferences,” on page 62

 Section 6.3.5, “Editing System Preferences,” on page 63

6.3.1 Updating Software

With the Software Updater, you can easily apply updates to your software with just a few clicks. At
startup, the Software Updater automatically checks for updates to your system from the sources
specified in the Software Updater configuration.

The following sections contain additional information:

 “Launching the Software Updater” on page 55

 “Configuring Package Sources” on page 56

 “Selecting Update Catalogs” on page 57

 “Selecting and Applying Updates” on page 58

Launching the Software Updater

1 Launch the Software Updater by navigating to /opt/novell/zenworks/bin and

running zen-updater with root privileges. To run it as a daemon, run zen-updater &.

The Software Updater icon appears in the notification area (GNOME) or the system tray
(KDE) of your panel as an icon depicting a globe, which changes to an orange circle with an
exclamation point in it when updates are available.

The first time you exit the Software Updater, you will be asked if you want it to load on startup.
If you choose Yes, you can access the Software Updater from the notification area or system
tray rather than by running zen-updater from the command line each time you want to
launch the applet.

The rug command-line utility also lets you perform software and user management through the
ZENworks Agent on a managed device. For background information on the underlying rug
command and its configuration options, see Section 4.4, “rug,” on page 46.

ZENworks Agent 55

Configuring Package Sources

Before you can use the use the Software Updater, you need to configure it to check package sources
for updates. Ask your system administrator for package sources that are available for your product
and for connection details.

NOTE: The Software Updater and the Software Installer use the same configurations. If you add a
service using the Software Updater configuration screen, that service will appear in the Software
Installer configuration and vice versa.

To add n e w s e rvices:

1 Right-click the Software Updater icon, then click Configure.

If the Software Updater icon is not in the system tray, you need to launch the program. See

“Launching the Software Updater” on page 55.

2 Click Add Service.

novdocx (en) 11 July 2008

3 Select the type of update repository from the drop-down list. The Software Updater supports

the following service types: YUM, ZYPP, NU, RCE, ZENworks, user-mounted sources
(Mount), Auto-detect, and Novell Customer Center Registration.

4 Add the connection details for the source type you selected (server URI and registration key),

then click Add. The service URI is the URL of the service. Registration keys are optional and
are made available by the administrator of the service. Only ZENworks and RCE services have
registration keys.

The source is listed in the Services tab and is ready to be used and checked for available update
packages.

To remove a service:

1 Right-click the Software Updater icon, then click Configure.

If the Software Updater icon is not in the system tray, you need to launch the program. See

“Launching the Software Updater” on page 55.

56 Novell ZENworks 7.2 Linux Management Administration Guide

2 Select the services you want to delete, then click Remove Service.

novdocx (en) 11 July 2008

Selecting Update Catalogs

Once you have configured one or more services, you can select a set of catalogs from those sources
to be checked. There may be, for example, a catalog containing all the software that came with the
original release of the product and another one containing all the update packages released since.

To select additional update catalogs:

1 Right-click Software Updater, then click Configure.

If the Software Updater icon is not in the system tray, you need to launch the program. See

“Launching the Software Updater” on page 55.

2 Click the Catalogs tab.

3 Select the catalogs you want or deselect those you don’t need, then click Close.

ZENworks Agent 57

Selecting and Applying Updates

When updates are available, the panel icon changes to an orange circle with an exclamation mark in
it. When you mouse over the icon, a message pops up indicating that updates are available.

To review and apply updates:

1 Click the Software Updater icon.

If the Software Updater icon is not in the system tray, you need to launch the program. See

“Launching the Software Updater” on page 55.

novdocx (en) 11 July 2008

2 Select the updates you want to apply.

Click Details for more information about the selected update.

NOTE: To poll the services for updates, right-click the Software Updater icon, and then click
Refresh.

3 (Optional) If you do not want to view the change summary information, select Do not show the

change summary screen. By default, this option is not selected.

4 Click Update.

If you chose to view the change summary information in Step 3, the software updater icon
blinks when the change summary screen is displayed.

6.3.2 Installing Software

Using ZENworks Linux Management, your administrator can create catalogs containing optional
software and assign them to users’ devices. Because software packages contained in catalogs are
usually considered optional, users can choose whether or not to install the software. If an
administrator has assigned catalogs to users’ devices, the catalogs display in the Software Installer.

 “Configuring Package Sources” on page 59

58 Novell ZENworks 7.2 Linux Management Administration Guide

 “Selecting Installation Catalogs” on page 60

 “Installing Software by Using the Software Installer” on page 60

Configuring Package Sources

Before you can use the Software Installer, you need to add package sources from which you can
install software.

NOTE: The Software Updater and the Software Installer use the same configurations. If you add a
service using the Software Updater configuration screen, that service will appear in the Software
Installer configuration and vice versa.

To add a package source:

1 Launch the Software Installer by navigating to /opt/novell/zenworks/bin and

running zen-installer with root privileges.

2 Click Configure.

novdocx (en) 11 July 2008

3 Click Add Service.

ZENworks Agent 59

4 Select the type of the service repository from the drop-down list. The Software Updater

supports the following service types: YUM, ZYPP, NU, RCE, ZENworks, and user-mounted
sources (Mount), Auto-detect, and Novell Customer Center Registration.

5 Add the connection details for the source type you selected (server URI and registration key),

then click Add. The service URI is the URL of the service. Registration keys are optional and
are made available by the administrator of the service. Only ZENworks and RCE services have
registration keys.

The source is listed in the Services tab and is ready to be used and checked for available
packages.

Selecting Installation Catalogs

You can configure the Software Installer to accept various catalogs:

1 Launch the Software Installer by navigating to /opt/novell/zenworks/bin and

running zen-installer with root privileges.

2 Click Configure.

3 Click the Catalogs tab.

novdocx (en) 11 July 2008

4 Select the catalogs you want or deselect those you don’t need, then click Close.

Installing Software by Using the Software Installer

To install software:

1 Launch the Software Installer by navigating to /opt/novell/zenworks/bin and

running zen-installer with root privileges.

60 Novell ZENworks 7.2 Linux Management Administration Guide

novdocx (en) 11 July 2008

2 Select the software that you want to install or search for software by typing a search term in the

search field, then click Search. (Click Clear to clear the search field.) Click Details for
information about the selected software. You can select all available software by clicking All.

3 (Optional) If you do not want to view the change summary information, select Do not show the

change summary screen. By default, this option is not selected.

4 Click Install.

NOTE: Even though the user has been assigned rights by the administrator for installing the
software, the installation of bundle fails.

6.3.3 Removing Software

The Software Remover lets you remove software on a managed device. The utility is in the /opt/
novell/zenworks/bin directory.

1 Launch Software Remover by navigating to /opt/novell/zenworks/bin and running

zen-remover with root privileges.

ZENworks Agent 61

novdocx (en) 11 July 2008

2 Select the software you want to remove. To filter the list, click on the type of software: All,

Product, Bundle, Pattern, or Package. You can click Details for more information about the

selected software.

3 (Optional) If you do not want to view the change summary information, select Do not show the

change summary screen. By default, this option is not selected.

4 Click Remove.

6.3.4 Viewing System Preferences

1 Right-click the Software Updater icon, then click Configure.

If the Software Updater icon is not in the system tray, you need to launch the program. See

“Launching the Software Updater” on page 55.

2 Click the Preferences tab.

62 Novell ZENworks 7.2 Linux Management Administration Guide

This window shows the system preferences.

novdocx (en) 11 July 2008

NOTE: You can also display this list from the command line using rug get. For more
information, see rug (1) (page 571).

6.3.5 Editing System Preferences

1 Right-click the Software Updater icon, then click Configure.

If the Software Updater icon is not in the system tray, you need to launch the program. See

“Launching the Software Updater” on page 55.

2 Click the Preferences tab.

3 (Optional) Select Start the software updater on login to automatically start the Software

Updater.

ZENworks Agent 63

4 (Optional) Select Show the version details to list all available package updates.

By default, the package list will not show the version details nor will it show if multiple
versions of the same package are available. Instead, it will show the “best” package available,
or the package with the best architecture and version and with the least number of install/delete
requests required.

5 In the preferences list, click the row whose value you want to change, then click the value.

6 Edit preferences as desired.

 bind-ip. For systems using more than one IP address, selects the address at which rcd will

bind. Leave empty to bind to all addresses.

 blackout-interval. Time interval for which the device is to be locked. Specify the start time

and end time time in the HH:MM format, with hours in 24-hour format.

 cache-cleanup-enabled. If True, automatically cleans up the cache. The default is True.

 cache-directory. The directory where cached data are stored. The default is /var/opt/

novell/zenworks/cache/zmd/web.

 cache-max-size-hard-limit. If True, never allow the cache to grow past the maximum size.

The default is False.

 cache-max-size-in-mb. Sets the cache size. The default is 300 mb.

 delay. How long before sending delayed actions, in seconds. The default is 900 seconds.

novdocx (en) 11 July 2008

 device-locked. If True, locks the device and zmd blocks install, removal, refresh, and

register operations for packages and bundles.

 device-shutdown-delay. Sets the delay for a device shutdown. The default is 2 seconds.

 hardware-inventory-enabled. If True, hardware inventory information will be collected

and sent to the server. The default is True.

 http-timeout. Number of seconds until HTTP requests timeout. The default is 180 seconds.

 hwinfo-options. Options to pass to the hwinfo command. By default, it is set to null on

SLES 9 and NLD devices. For SLES 10 and SLED 10 devices, the default setting for the
hwinfo preference is --nowpa. If the default setting is changed, the hwinfo command
resets the wireless configuration settings on SLES 10 and SLED 10.

 inventory-scanner-options . Options to pass to the inventory scanner. The default is “-

braille.”

 log-exception-traces. Log full traces when an exception is encountered. The default is

False.

 log-level . Sets the log level. Options are off, fatal, error, warn, info, and debug. The

default is Info.

 log-max-files-size. Maximum size (in MB) of all the zmd-messages.log files.

 log-soap-xml. Log soap messages (debug log level only). The default is False.

 max-cache-age. The maximum number of days to cache a file. The default is 30 days.

 max-database-age. Maximum number of days to refresh the database.

 max-downloads. Maximum number of concurrent downloads. The default is 5.

 max-retries. Maximum number of download retries. The default is 3.

 memory-threshold. Memory (in MB) at which zmd should restart because of excessive

memory usage.

64 Novell ZENworks 7.2 Linux Management Administration Guide

 no-verified-certs.Specify the IP addresses of the servers (separated by a comma) for which

you do not want to verify the SSL certificates. The servers are excluded only if require-
verified-certs is True.

 proxy-password. Password for the proxy, if any.

 proxy-url.URL for the proxy server.

NOTE: If you modify the system proxy, you must set the proxy-url with the system proxy
URL for the device to use the system proxy. You can set the proxy URL either by using
the rug command or through the zmd settings in the ZENworks Control Center. For more
information on how to use the rug command, see rug (1). For more information on how to
configure the zmd settings, see Section 7.10, “Configuring the ZENworks Management

Daemon (zmd) Settings,” on page 74.

 proxy-username. Username for the proxy, if any.

 proxy-excludes. Specify the IP address or the DNS name of the server that you want to

exclude from using the proxy settings. You can specify multiple IP addresses or DNS
names by separating the same with a comma. You can use the * wildcard character only in
the IP address. Ensure that there is no space in the specified IP address or the DNS name.

 refresh-interval. How long between refreshes, in seconds. The default is 7200 seconds.

 refresh-interval-hardware. How long between hardware refreshes. The default is 86400

seconds.

 refresh-interval-software. How long between software refreshes. The default is 86400

seconds.

novdocx (en) 11 July 2008

 refresh-interval-system. How long before system refreshes. The default is 86400 seconds.

 remote-enabled. Allow clients to connect to this daemon remotely. The default is True.

 remote-port. Port used for connections of remote clients. The default value is 5505.

 require-verified-certs. Verify SSL certificates from server. This should remain False

unless your ZENworks Linux Management server has a signed SSL certificate (generated
or purchased). The default is False.

 retry-delay. The number of milliseconds to delay before retrying a download. The default

is 2000 milliseconds.

 rollback. Store more detailed transaction history, enabling rollback feature. The default is

False.

 run-transaction-test. Run a dryrun before attempting to install or remove packages. The

default is True.

 security-level. Security requirements to enforce. Possible values are signature, checksum,

and none. The default is Checksum.

 service-retry-interval. The default is 300 seconds.

 sleep-interval. The number of seconds before the next Service Refresh schedule wakes up.

The default is 300 seconds.

 sleep-threshold. The default is 600 seconds.

 software-inventory-enabled. If True, software inventory information will be collected and

sent to the server. The default is True.

 syslog-level. Sets the log level. Options are off, fatal, error, warn, info, and debug. The

default is Info.

ZENworks Agent 65

NOTE: You can also edit these system preferences from the command line using rug set.
For more information, see rug (1) (page 571).

If you change the value of the bind-ip, remote-enabled, or remote-port, you must restart zmd
for the changes to take effect.

6.4 Uninstalling the ZENworks Agent

ZENworks includes a uninstall program (zlm-uninstall) to remove the ZENworks Agent from a
device. If for some reason the uninstall program is unable to remove the ZENworks Agent, you can
manually uninstall the agent. The following sections provide instructions to remove the software:

Using zlm-uninstall to Uninstall the ZENworks Agent

1 Make sure you have unregistered the device. See Chapter 13, “Unregistering and Reregistering

Devices,” on page 115.

2 Log in to the managed device as root.

3 Run the following command:

novdocx (en) 11 July 2008

/opt/novell/zenworks/bin/zlm-uninstall

4 Follow the prompts.

Manually Uninstalling the ZENworks Agent

1 Use the following command to list the ZENworks package names:

rpm -qa | grep novell-zenworks

2 Remove each of the packages individually using the following command:

rpm -e | package_name

or

Use the following simple script to remove multiple packages:

for i in ‘rpm -qa | grep novell-zenworks‘ ; do rpm -e $i ; done

Because of package dependencies, you might need to run this script multiple times to remove
all packages. You can verify that all packages have been removed by running the command in

Step 1.

3 Remove the following directories:

rm -rf /opt/novell/zenworks/

rm -rf /etc/opt/novell/zenworks/

rm -rf /var/opt/novell/zenworks/

NOTE: When you uninstall ZENworks Linux Management on SLES 10 and SLED 10 managed
devices, the core zmd packages such as zmd, rug, zen-updater, and zen-inventory are not removed
because they are also installed as a part of the distribution. Hence, when you reinstall the ZENworks
Agent on these devices, the configuration files such as zmd.conf that are associated to these
packages persist.

66 Novell ZENworks 7.2 Linux Management Administration Guide

7

Configuring Management Zone

novdocx (en) 11 July 2008

Settings

The ZENworks® Management Zone is the top level of the ZENworks management hierarchy. The
Management Zone provides an autonomous administrative unit of ZENworks Servers and managed
devices (workstations and servers). You use the ZENworks Control Center (the Web-based
administrative tool) to manage devices. The ZENworks Servers and managed devices work together
to apply the management tasks.

You can use the Configuration tab in the ZENworks Control Center to configure your Management
Zone.

The following sections contain additional information:

 Section 7.1, “Configuring System Variables,” on page 67

 Section 7.2, “Configuring the Device Refresh Schedule,” on page 70

 Section 7.3, “Configuring Device Inventory Settings,” on page 70

 Section 7.4, “Configuring Local Device Logging,” on page 71

 Section 7.5, “Configuring Preboot Services,” on page 72

 Section 7.6, “Configuring Remote Management,” on page 72

 Section 7.7, “Configuring Centralized Message Logging,” on page 72

 Section 7.8, “Configuring the Content Replication Schedule,” on page 72

7

 Section 7.9, “Viewing Default Target Platforms and Configuring Custom Target Platforms,” on

page 73

 Section 7.10, “Configuring the ZENworks Management Daemon (zmd) Settings,” on page 74

 Section 7.11, “Integrating Novell Customer Center with ZENworks Linux Management,” on

page 75

 Section 7.12, “Configuring the ZENworks Server Preferences,” on page 76

 Section 7.13, “Understanding the StoreFileDeps Preference,” on page 77

7.1 Configuring System Variables

The System Variables page lets you define variables that can be used to replace paths, names, and so
forth as you enter data in various ZENworks Control Center fields. System variables defined on this
page can be used on all objects in your ZENworks Management Zone.

System variables can be overridden at the device or folder level. If you add the same system variable
to a device or folder, but give it a different value, the new variable value overrides the inherited
system variable value. A variable on the device level overrides the same variable on the folder level,
which overrides the same variable on the system level.

The following sections provide additional information:

 Section 7.1.1, “Creating System Variables,” on page 68

 Section 7.1.2, “Using Variables in ZENworks Policies: A Sample Use Case,” on page 68

Configuring Management Zone Settings

67

7.1.1 Creating System Variables

To provide a variable at the device level:

1 In ZENworks Control Center, click the Devices tab.

2 Navigate to and click the desired device, click the Settings tab.

3 Click System Variables, then click Override settings.

4 To add a system variable, click Add, then fill in the Name and Va l ue fields.

When specifying the variable in an object's field, use the following syntax:

${VAR_NAME}

5 Click OK.

Click the icon for additional help

To provide a variable at the folder level: from the ZENworks Control Center, click the Devices tab,
click the (Details) link next to the desired folder, click the Settings tab, then click System Variables.
Click the icon for additional help.

1 In ZENworks Control Center, click the Devices tab.

2 Click the (Details) link next to the desired folder, click the Settings tab, then click System

Variables, then click Override settings.

novdocx (en) 11 July 2008

3 To add a system variable, click Add, then fill in the Name and Va l ue fields.

When specifying the variable in an object's field, use the following syntax:

${VAR_NAME}

4 Click OK.

Click the icon for additional help

To set system variables for your ZENworks system:

1 In the ZENworks Control Center, click the Configuration tab.

2 Click System Variables.

3 To add a system variable, click Add, then fill in the Name and Va l ue fields.

When specifying the variable in an object's field, use the following syntax:

${VAR_NAME}

4 Click OK.

7.1.2 Using Variables in ZENworks Policies: A Sample Use Case

In this scenario, you have a SLES 9 and a SLES 10 managed device. Both devices have a common
file, deviceid. On SLES 9, the file is located at /etc/opt/novell/zenworks/zmd, and
on SLES 10 it is located at /etc/zmd. Assume that you want to place a copy of deviceid in the
/tmp directory on both devices by using the Remote Execute policy. Instead of creating two
Remote Execute policies, one each for the SLES 9 and SLES 10 managed device, you can create one
policy by using system variables.

68 Novell ZENworks 7.2 Linux Management Administration Guide

Perform the following tasks in the order listed:

 “Creating a System Variable for the SLES 9 Managed Device” on page 69

 “Creating a System Variable for the SLES 10 Managed Device” on page 69

 “Creating the Remote Execute Policy and Assigning It to the Managed Devices” on page 69

Creating a System Variable for the SLES 9 Managed Device

1 In ZENworks Control Center, click the Devices tab.

2 Click Servers.

3 From the list of servers, click the SLES 9 managed device, then click the Settings tab.

4 Click System Variables, then click Override settings.

5 In the System Variables panel, click Add, then fill in the following details:

 Name: source_path

 Va lu e: /etc/opt/novell/zenworks/zmd

6 Click OK.

7 Click Apply, then click OK.

novdocx (en) 11 July 2008

Creating a System Variable for the SLES 10 Managed Device

1 In ZENworks Control Center, click the Devices tab.

2 Click Servers.

3 In the list of servers, click the SLES 9 managed device, then click the Settings tab.

4 Click System Variables, then click Override settings.

5 In the System Variables panel, click Add, then fill in the following details:

 Name: source_path

 Va lu e: /etc/zmd

6 Click OK.

7 Click Apply, then click OK.

Creating the Remote Execute Policy and Assigning It to the Managed Devices

1 In ZENworks Control Center, click the Policies tab.

2 In the Policies list, click New, then click Policy to display the Create New Policy page.

3 In the Policy Type list, click Remote Execute Policy, then click Next to display the Policy Name

page.

4 Fill in the Policy Name, Folder, and Description fields. For more information, see Step 4 on

page 160 in Section 16.6, “Remote Execute Policy,” on page 159.

5 Click Next.

6 In the Remote Execute Policy page, configure the following settings:

 Executable Type: Select Binary.

 Maximum waiting time: Select Wait till the program completes the execution.

Configuring Management Zone Settings 69

 Executable file name: /bin/cp.

 Executable file parameters: ${source_path}/deviceid /tmp.

7 Click Next to display the Summary page.

8 Review the information.

9 Click Next to display the Policy Assignment page, then assign the policy to SLES 9 and SLES

10 devices

10 Click Next to display the Policy Schedule page, then select the schedule to apply to the

assignments.

11 Click Next to display the Policy Groups page. For more information, see Step 12 in

Section 16.6, “Remote Execute Policy,” on page 159.

12 Click Next to display the Finish page.

13 Click Finish.

After the policy is applied on the managed devices, a copy of deviceid is created in the /tmp
directory.

novdocx (en) 11 July 2008

7.2 Configuring the Device Refresh Schedule

The Device Refresh Schedule page determines how often devices contact a ZENworks Server to
update policies, settings, and inventory scanning. By default, each refresh schedule occurs every two
hours.

These settings apply to all devices in your ZENworks Management Zone unless it is changed on a
device folder or individual device. To change refresh schedules for an individual device, click the

Devices tab, locate and click the device's name, click the Settings tab, click Device Refresh
Schedule, then click Override Settings. Click the icon for additional help.

The refresh interval is not reset until the device refresh is complete. For example, assume you set a
refresh interval of 2 hours. The device's first refresh occurs at 6:00 p.m. and takes 13 seconds to
complete. The second refresh will occur at 8:00:13 p.m. (2 hours after the refresh was completed at
6:00:13). If the second refresh takes 15 seconds to complete, the third refresh will occur at 10:00:28
p.m.

To configure the device refresh schedule for all devices in your ZENworks system:

1 In the ZENworks Control Center, click the Configuration tab.

2 Click Device Refresh Schedule.

3 Specify the Days, Hours, and Minutes between device refreshes in your ZENworks system.

4 Click OK.

7.3 Configuring Device Inventory Settings

The Device Inventory page determines the Inventory Roll-up settings.

Configure the settings on this page to roll up the hardware inventory information from a ZENworks
7 Linux Management database to a ZENworks 7 or later Server Management or Desktop
Management Inventory server:

1 In the ZENworks Control Center, click the Configuration tab.

70 Novell ZENworks 7.2 Linux Management Administration Guide

2 Click Device Inventory.

3 Configure the desired settings:

 DNS name or IP address of the destination server: Specify the DNS name or the IP

address of the ZENworks 7 or later Server Management or Desktop Management
Inventory server to which you want to roll up the hardware inventory information.

 Time interval between roll ups (in hours): Specify the time interval between two roll-

ups.

4 Click OK.

7.4 Configuring Local Device Logging

The Local Device Logging page lets you configure the logging of messages to a managed device's
local drive.

1 In the ZENworks Control Center, click the Configuration tab.

2 Click Local Device Logging.

3 Fill in the fields to specify local file settings. By default, the path of the files varies, depending

on the type of device. For SUSE Linux Enterprise Server 10 (SLES 10) and SUSE Linux
Enterprise Desktop (SLED 10) devices, the path is /var/log. For all other devices, it is /
var/opt/novell/log/zenworks.

 Log message to a local file if severity is: Specify filtering criteria based on severity.

novdocx (en) 11 July 2008

 Error: Stores messages with Error severity.

 Warning and above: Stores messages with Error severity.

 Information and above: Stores messages with a severity of Information, Warning,

and Error.

 Debug and above: Stores messages with a severity of Debug, Information, Warning,

and Error.

 Limit file size to: Specify the maximum size of the file where messages are being stored.

The message file is backed up after reaching the specified size. The default setting is 10
MB.

 Number of backup files: Specify the number of backup files to take. The maximum

number of backup files is 99. The default setting is 1.

4 Fill in the fields to store messages in the device system log file. The path to system log file is /

var/log/messages.

 Send message to local system log if severity is: Specify filtering criteria based on

severity.

 Error: Stores messages with Error severity.

 Warning and above: Stores messages with Error severity.

 Information and above: Stores messages with a severity of Information, Warning,

and Error.

5 Click OK.

Configuring Management Zone Settings 71

These settings apply to all devices in your ZENworks Management Zone unless it is changed
on a device folder or individual device. To change refresh schedules for an individual device,
click the Devices tab, locate and click the device's name, click the Settings tab, click Local
Device Logging, then click Override Settings. Click the icon for additional help

7.5 Configuring Preboot Services

The Preboot Services page lets you configure the following ZENworks Management Zone default
settings for devices that use Preboot Services:

 Preboot menu options

 Image storage security

 Non-registered device network settings

 Non-registered device preboot work assignment

 Server referral list

 Intel Active Management Technology (AMT)

For detailed information, see Section 29.4, “Configuring Preboot Services Defaults,” on page 371.

novdocx (en) 11 July 2008

7.6 Configuring Remote Management

The Remote Management Settings page lets you configure the Remote Management settings for the
management zone. This includes enable and disable options for remote management operations as
well as configurations for custom ports.

For detailed information, see Section 36.1.1, “Configuring Remote Management Settings at the

Zone Level,” on page 487

7.7 Configuring Centralized Message Logging

The Centralized Message Logging page lets you configure the following to log the messages on the
primary server:

 Central Server

 Centralized file log

 E-mail notification

 SNMP traps

For detailed information, see Section 40.1.2, “Configuring Centralized Log Settings,” on page 514.

7.8 Configuring the Content Replication Schedule

The Content Replication Schedule page lets you specify how often bundles are replicated from the
primary ZENworks Server to all secondary ZENworks Servers in the Management Zone. During
replication of a bundle, only new packages and updates to existing packages are sent.

For detailed information, see Section 24.2, “Configuring a Content Replication Schedule,” on

page 288.

72 Novell ZENworks 7.2 Linux Management Administration Guide

7.9 Viewing Default Target Platforms and Configuring Custom Target Platforms

This Target Platforms page lists the server and workstation platforms that ZENworks Linux
Management supports as managed devices. You can also define additional custom platforms by
adding an entry to the Custom Target Platforms list.

1 In the ZENworks Control Center, click the Configuration tab.

2 Click Platforms.

3 (Optional) To view the details of a default target platform, click the name of a platform.

4 (Optional) To add a custom target platform, under Custom Target Platforms, click Add to

display the Add Platform dialog box.

Figure 7-1 Add Platform dialog box.

novdocx (en) 11 July 2008

If you have custom distributions that your company has created based on one of the supported
platforms, these custom distributions can be recognized by ZENworks Linux Management by
adding them as a custom target platform.

5 Select an existing target platform whose settings you want to copy and edit, then click OK

The easiest way to create a custom target platform is to copy a default platform's settings that
are similar to your custom target and then edit those settings.

6 Fill in the fields:

 Name: Specify the name of the platform as you want it displayed in the ZENworks

Control Center.

 Vendor: Specify the name of the distribution's vendor.

 Product Name: Specify the product name of the distribution.

 Ve rs io n: Type the version number.

 Package Manager: Specify the package manager for the platform.

 Architecture: Specify the architecture.

 Device Type: Specify whether the device type for the platform is a workstation or a

server.

 OS Detection String: Modify the XML strings in the box to point to the file on the device

that would contain the release information and the string that the system must match to
determine the platform of a device.

 Enable this Platform: Select this option to enable this platform so that it will display in

menus and other areas in the ZENworks Control Center.

7 Click OK.

Configuring Management Zone Settings 73

7.10 Configuring the ZENworks Management Daemon (zmd) Settings

Use the ZENworks Management Daemon Settings page to configure the Zenworks Management
Daemon (zmd) settings for your ZENworks Management Zone. These settings apply to all devices
in your ZENworks Management Zone unless they are changed on a device folder or individual
device. Any changes to the settings on this page are applied to devices upon refresh.

The zmd daemon performs software management functions on the ZENworks managed device,
including updating, installing and removing software, and performing basic queries of the device's
package management database. Typically, these management tasks are initiated through the
ZENworks Control Center or the rug utility, which means you should not need to interact directly
with zmd.

The settings that you can configure on this page can also be set using the rug utility. For information
about each setting and its corresponding value, see rug (1) (page 571).

To configure a zmd setting:

1 In the ZENworks Control Center, click the Configuration tab.

novdocx (en) 11 July 2008

2 Click ZMD Settings.

3 Click Add to open the Configure Setting dialog box.

Figure 7-2 Configure Setting dialog box.

4 Fill in the fields:

 Setting: Select a value from the Setting drop-down list.

The drop-down list contains all available settings in ZENworks Linux Management. If not
all modules are installed on a device, settings that control that module will not be used by
the zmd daemon. For example, if you do not install the Remote Control module on a
device, all settings that configure this module will be ignored.

 Va lu e: If the selected setting requires specific values, select the desired value from the

drop-down list. If the selected setting does not require specific values, type the value in the
Value box.

After you click OK, if displays next to the Value box, the setting you typed is either too
small/large or you typed an invalid setting.

 Description: Displays the description of the selected setting.

74 Novell ZENworks 7.2 Linux Management Administration Guide

The zmd settings can be overridden at the device or folder level. If you add the same zmd
setting to a device or folder, but give it a different value, the new setting value overrides the
inherited zmd setting value. A setting on the device level overrides the same setting on the
folder level, which overrides the same setting on the system level.

To provide a setting at the device level, from the ZENworks Control Center, click the Devices
tab, navigate to and click the desired device, click the Settings tab, click ZMD Settings, then
click Override Settings. Click the Help icon for additional help.

To provide a setting at the folder level, from the ZENworks Control Center, click the Devices
tab, click the (Details) link next to the desired folder, click the Settings tab, then click ZMD
Settings, then click Override Settings. Click the Help icon for additional help.

If you add the same setting twice, the first instance of the setting is removed and the new
setting is applied to the device when it refreshes.

7.11 Integrating Novell Customer Center with ZENworks Linux Management

Novell Customer Center is an online tool that makes it easier for you to manage your business and
technical interactions with Novell. From one location, you can do the following:

novdocx (en) 11 July 2008

 Review the status of supported Novell products, subscriptions, and services

 Obtain support

 Get Linux updates and patches

For more information about Novell Customer Center, see the Novell Customer Center

documentation (http://www.novell.com/documentation/ncc/index.html).

ZENworks Linux Management helps you to register all SLES 10 and SLED 10 managed devices
into Novell Customer Center at the same time. By integrating Novell Customer Center with the
ZENworks Linux Management server, you do not need to individually register each managed device
to Novell Customer Center.

To integrate the ZENworks Linux Management Server with Novell Customer Center:

1 Install ZENworks Linux Management Agent on all the managed devices. For more

information, see Setting Up Managed Devices in the Novell ZENworks 7.2 Linux Management

Installation Guide.

2 Register the ZENworks Linux Management Server to Novell Customer Center.

 On SLES 10: Execute zlm-ncc-reg <IP_address_of_the

ZENworks_Linux_Management_server> <E­Mail_Id_of_Novell_Customer_Center_Account>
<License_key_for_ZENworks_Linux_Management_or_the_product_
that_entitles_you_to_ZENworks Linux Management>

 On Other Servers: Execute the zlm-ncc-reg command.

The ZENworks Linux Management Server acts as a Satellite server and registers all the
managed devices to Novell Customer Center.

3 Log in to the ZENworks Control Center, then click the Configuration tab.

4 In Management Zone Settings, click Novell Customer Center to display the Novell Customer

Center page.

Configuring Management Zone Settings 75

5 Configure the following settings to register the managed devices and upload their basic

hardware inventory information to Novell Customer Center:

 Select Enable link-up with Novell Customer Center.

This enables the server to periodically transmit information about itself and its managed
devices to Novell Customer Center.

 In Update Interval (Hrs), specify how often the server must send information to Novell

Customer Center. By default, the interval is 3 hours.

6 Click Apply, then click OK.

NOTE: To view the information uploaded by the ZENworks Linux Management Satellite server,
ensure that the Novell Customer Center account is created before registering the ZENworks Linux
Management Server to Novell Customer Center.

novdocx (en) 11 July 2008

7.12 Configuring the ZENworks Server Preferences

ZENworks Server preferences are used to control events triggered from managed device as well as
from ZENworks Server. These preferences are configured by default. The following preferences are
available for the ZENworks Linux Management Server:

 allow-rebuild: Enables or disables the rebuild action of the managed device during the device

registration process. The default value is False.

 compute-package-device-updates: Enables or disables both Package Updates and Device

Updates Queue actions triggered on the ZENworks Server. The default value is True.

 show-updates-icon: Enables or disables the Updates icon for devices displayed under the

Devices tab. The default value is True.

 store-file-deps: Enables or disables filtering of RPM Package dependency metadata. The

default value is True.

You can only edit the value of the preferences.

To edit the ZENworks Server preferences:

1 In the ZENworks Control Center, click the Configuration tab.

2 Click ZLM Server Preferences.

The ZENworks Server Settings page displays the preferences configured for the server.

3 Click Edit Preferences to display the Configure Server Preferences dialog box.

76 Novell ZENworks 7.2 Linux Management Administration Guide

4 Configure the following settings:

 In the Preference drop-down list, select the preference whose value you want to change.

 In the Va l u e drop-down list, select the desired value for the selected preference.

5 Click OK.

NOTE: The Apply and Reset buttons are not available for the ZENworks Server Settings page.

7.13 Understanding the StoreFileDeps Preference

StoreFileDeps is a preference on the ZENworks Linux Management server. This preference verifies
the Requires and Provides lists of the RPM packages on the server, depending on the value set for
the preference. You can set the value of this preference to True or False.

If the value is False, then the ZENworks Linux Management server verifies the Requires list and the
Provides list while adding a package to a repository. The server removes from the Provides list those
dependencies that are not in use by any other packages. It also adds those dependencies to the
Provides list that are in the Requires list of any other RPM package on the repository. By default, the
server also removes all the documents, man pages, etc. from the Provides list to reduce the size of
the metadata files that move from the server to the client. However, truncating dependencies can
create problems while resolving them on the client side. So, before setting the preference value as
False, you should import all the packages of different distributions installed on the agents to a
catalog on the ZENworks Linux Management server. Only then should you create a bundle or mirror
any updates. Importing the packages ensures that all the related packages are available on the
repository, and that the necessary dependencies are not filtered out while creating bundles.

novdocx (en) 11 July 2008

If the preference’s value is True, the dependencies list is kept as it is on the RPM metadata while
creating bundles. This ensures that the server does not add or remove unnecessary dependencies. It
also ensures that the dependency resolution does not fail on the client side if the dependent packages
are available on the media installation source that is added as a service to the ZENworks
Management Daemon. However, this increases the size of the metadata that moves to the client.

Configuring Management Zone Settings 77

novdocx (en) 11 July 2008

78 Novell ZENworks 7.2 Linux Management Administration Guide

8

ZENworks Administrator

novdocx (en) 11 July 2008

Accounts

During installation, a default Administrator account is created. This account provides rights to
administer all of your Novell

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 device folders, policy
folders, bundle folders, and report folders.

You can use the ZENworks Control Center or the zlman command line utility to create and modify
administrator accounts. The following procedures explain how to perform these tasks using the
ZENworks Control Center. If you prefer the zlman command line utility, see the Administrator
Commands section of zlman (1) (page 547).

The following sections provide information to help you create administrator accounts and manage
administrator rights:

 Section 8.1, “Creating an Administrator Account,” on page 79

 Section 8.2, “Modifying Account Rights,” on page 80

8.1 Creating an Administrator Account

®

ZENworks® system.

8

1 Log in to the ZENworks Control Center using an administrator account that has rights to create

other administrator accounts.

The default account, Administrator, has rights to create additional accounts.

2 In the ZENworks Control Center, click the Configuration tab.

The Administrators section of the Configuration page lists the current accounts.

3 In the Administrators list, click New to display the Add new Administrator dialog box.

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

ZENworks Administrator Accounts

79

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.

5 To change the administrator's rights, see the next section, Modifying Account Rights.

8.2 Modifying Account Rights

By default, newly created accounts are granted View rights to all objects in the Management Zone.
You can modify an administrator's rights so that the administrator can:

 Change the Management Zone configuration settings.

 Create or modify other administrator accounts.

 Create, modify, and delete all objects in the Management Zone or in a specific folder only.

 Modify all objects in the Management Zone or in a specific folder only.

To modify an administrator's rights:

1 Log in to the ZENworks Control Center using an administrator account that has rights to create

and modify other administrator accounts.

novdocx (en) 11 July 2008

The default account, Administrator, has rights to create and modify additional accounts.

2 In the ZENworks Control Center, click the Configuration tab.

The Administrators section of the Configuration page lists the current accounts.

3 Click the account you want to modify.

4 Set the General options as desired:

 Can create and manage other administrators: Select this option to enable the

administrator to create additional administrator accounts, or to change the settings for
existing administrator accounts.

 Can modify zone settings: Select this option to enable the administrator to change the

Management Zone settings, registration keys, registration rules, and licensing information
included on the Configuration page.

5 Set the bundle, device, policy, and report rights as desired.

You use the Assigned Rights sections to control the administrator's rights to manage bundles,
devices, policies, and reports. You can give the administrator All rights (Create, Delete,
Modify), Modify rights only, or View rights only.

You assign 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.

80 Novell ZENworks 7.2 Linux Management Administration Guide

For example, if you want the 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.

The following options are available to add folders and modify the administrator's rights to
folders:

 Add: By default, the Assigned Rights sections display only the root folders (/Bundles,

/Devices, /Policies, and /Reports). To assign rights to a folder that is not listed,

you need to add the folder to the list. To do so, click Add to display the Add Rights Folder
dialog box. In the Folders field, click to browse for and select the folder. After you
select the folder, select the desire rights assignment (All, Modify, or View), then click OK.

 Edit: To modify the administrator's rights to a folder that already appears in the list (for

example, the /Bundles folder), select the folder by clicking the box in front of its name,
then click Edit. Select the rights assignment you want (All, Modify, or View), then click
OK.

 Delete: To delete a folder from the list, select the folder by clicking the box in front of its

name, then click Delete. This deletes the administrator's directly assigned rights to the
folder. The administrator still inherits the rights assigned to the folder's parent. For
example, assume the administrator has View rights in the /Bundles folder and All rights
in the /Bundles/Workstations folder. You delete the /Bundles/

Workstations folder from the list. The administrator's rights in the /Bundles/
Workstations folder revert to the rights inherited from the /Bundles folders.
Therefore, in this example, the administrator goes from having All rights in the /
Bundles/Workstation folder to having View rights only.

novdocx (en) 11 July 2008

You cannot delete the root folders (/Bundles, /Devices, /Policies, and /
Reports).

6 When finished modifying rights, click Apply to apply the changes.

ZENworks Administrator Accounts 81

novdocx (en) 11 July 2008

82 Novell ZENworks 7.2 Linux Management Administration Guide

9

ZENworks Object Store and Data

novdocx (en) 11 July 2008

Store Maintenance

Under normal conditions, the data in the Novell® ZENworks® Object Store and Data Store is always
consistent. However, inconsistencies can occur because of database corruption, hardware failures, or
even natural disasters. Therefore, we recommend that you periodically back up and restore the
Object Store and Data Store.

ZENworks Linux Management provides tools to back up and restore the ZENworks Object Store
and the PostgreSQL Data Store If you are using Oracle for the Data Store, we recommend using a
tool like RMAN. Basic instructions for using RMAN are included in this section.

IMPORTANT: To restore a ZENworks Linux Management system after the failure of a ZENworks
Primary Server, you need backups of the Object Store, Data Store, package repository, and
zlmmirror configuration files. For more information, see “Disaster Recovery” in the Novell

ZENworks 7.2 Linux Management Troubleshooting Guide.

The following sections provide information about the maintenance tasks you can perform.

 Section 9.1, “Maintaining the ZENworks Object Store,” on page 83

 Section 9.2, “Maintaining the ZENworks Data Store on PostgreSQL,” on page 85

 Section 9.3, “Maintaining the ZENworks Data Store on Oracle,” on page 89

 Section 9.4, “Synchronizing the Object Store and Data Store,” on page 94

 Section 9.5, “Cleaning Up the ZENworks Database,” on page 94

9

9.1 Maintaining the ZENworks Object Store

The ZENworks Object Store is Novell eDirectoryTM 8.7.3. The Novell eDirectory Service /etc/
init.d/ndsd should be running to allow the backup and restore operations for ZENworks Object

Store.

The following sections provide information for backing up and restoring the Object Store:

 Section 9.1.1, “Backing Up the ZENworks Object Store,” on page 83

 Section 9.1.2, “Restoring the ZENworks Object Store,” on page 84

 Section 9.1.3, “Deleting the Dangling Objects from ZENworks Object Store,” on page 84

9.1.1 Backing Up the ZENworks Object Store

You use zlm_ndsbackup.sh, located in /opt/novell/zenworks/sbin, to back up the
Object Store.

1 Make sure you are logged in as root to the ZENworks Server.

2 Enter the following command at the command prompt:

ZENworks Object Store and Data Store Maintenance

83

# zlm_ndsbackup.sh -U admin.system

3 Enter the password to authenticate to the Object Store.

This is the password for the ZENworks Administrator account.

The backup program creates a directory in /var/opt/novell/zenworks/backup/nds/
month-yyyy/yyyy-mm-dd. The directory name is the date on which the backup is taken. The
backup file is saved in this directory. The name of the backup file has the format timestamp-backup,
and the time stamp indicates the time when the backup was taken. For example:

/var/opt/novell/zenworks/backup/nds/August-2005/2005-08-23/
10:12:23-backup

®

Backup creates a directory with the current date in /var/opt/novell/zenworks/

NDS
backup/nds. The backup file is saved in this directory.

The log information about the backup operation is saved to /var/opt/novell/log/
zenworks/ndsbackup.log.

9.1.2 Restoring the ZENworks Object Store

novdocx (en) 11 July 2008

If necessary, you can restore the ZENworks Object Store from a backup you created. You use
zlm_ndsrestore.sh, located in /opt/novell/zenworks/sbin, to restore the Object
Store from a backup.

1 Make sure you are logged in as root to the ZENworks Server.

2 Enter the following command on the command prompt:

zlm_ndsrestore.sh -U admin.system -F path_to_the_backup_file

Make sure that the -F option includes the backup file's complete path.

3 Enter the password to authenticate to the Object Store.

This is the password for the ZENworks Administrator account.

The log information about the restore operation is saved in /var/opt/novell/log/
zenworks/ndsrestore.log.

4 After the restore is complete, you need to ensure that the Data Store is synchronized with the

Object Store. For instructions, see Section 9.4, “Synchronizing the Object Store and Data

Store,” on page 94.

9.1.3 Deleting the Dangling Objects from ZENworks Object Store

The zlm-edirectory cleanup utility of ZENworks 7.2 Linux Management IR2 helps you to delete
dangling objects from ZENworks Object Store.

To run the zlm-edirectory cleanup utility on the ZENworks Server:

1 Close all ZENworks Linux Management operations, if any are running.

2 Create an XML file with the following content:

<?xml version="1.0" encoding="UTF-8"?>

84 Novell ZENworks 7.2 Linux Management Administration Guide

<ZLMedirectoryCleanup xmlns="http://www.novell.com/zenworks/edirectoryCleanup"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

<Tree>

<TreeName>
Management_Zone_Name
</TreeName>

<Password>eDirectory_password </Password>

<Principle>
Base_DN_of_the_eDirectory (usually, cn=admin,o=system) </
Principle>

<RootContext>
Root_context_to_which_LDAP_connection_is_to_be_established (usually,
o=cell) </RootContext>

<IPAddress>IP_address_of_the_ZENworks_Server</IPAddress>

<Port>
SSL_port_number_used_by_the_ZENworks_Server (usually, 10636) </
Port>

novdocx (en) 11 July 2008

<SSL>true</SSL>

<ImportCertificate> True or False </ImportCertificate>

</Tree>

</ZLMedirectoryCleanup>

The ZENworks server uses the information in the XML file to establish connection with
eDirectory.

3 At the server console prompt, go to /opt/novell/zenworks/sbin and execute the

following command:

zlm_edirCleanup complete_path_of_the_xml_file

Where complete_path_of_the_xml_file is completed path of the XML file created in Step 2.

4 (Optional) To review the status of the utility, see /var/opt/novell/log/zenworks/

edirCleanup.log.

9.2 Maintaining the ZENworks Data Store on PostgreSQL

The following sections provide instructions for backing up and restoring the PostgreSQL Data
Store:

 Section 9.2.1, “Displaying the Password for the Default PostgreSQL Database,” on page 86

 Section 9.2.2, “Understanding Automated Database Maintenance,” on page 86

 Section 9.2.3, “Backing Up the ZENworks Data Store,” on page 86

 Section 9.2.4, “Restoring the ZENworks Data Store,” on page 87

ZENworks Object Store and Data Store Maintenance 85

 Section 9.2.5, “Optimizing the Server Database,” on page 88

 Section 9.2.6, “Restarting Novell Zenworks Server Services After Restarting the Database,” on

page 89

9.2.1 Displaying the Password for the Default PostgreSQL Database

The password for the default ZENworks PostgreSQL database is stored as plaintext on your
ZENworks Primary Server. You can access the database without the password if you are logged on
as Root.

If you need the password for maintenance purposes, you can use the following command to display
the password (you must be logged in as Root):

cat /etc/opt/novell/zenworks/serversecret

9.2.2 Understanding Automated Database Maintenance

novdocx (en) 11 July 2008

If you are using a PostgreSQL database, there are some automated maintenance tasks that are
performed both daily and monthly.

Daily Maintenance: Once a day, old versions are flagged, allowing the space used by these records
to be used for new data; the statistics used by the query engine are updated to achieve the best
possible performance. This maintenance runs every day at 2:15 a.m.

Monthly Maintenance: Unlike the daily maintenance, the monthly maintenance actually frees the
space used by the old flagged records; this prevents a large disparity between the allocated disk
space for the database and the actual space used by the database. Because this is an intensive
process, it is scheduled monthly instead of daily. It runs at 3:15 a.m on the first day of each month.

9.2.3 Backing Up the ZENworks Data Store

This section applies only if you are using the PostgreSQL database for your Data Store.

You can use zlm_dbbackup.sh to make a backup of the Data Store. This backup utility is
located in /opt/novell/zenworks/sbin.

1 Make sure you are logged in as root to a ZENworks Server.

2 On the ZENworks Primary Server with the local data store, enter the following at the command

prompt:

zlm_dbbackup.sh

NOTE: Database backup operation is supported from the Secondary servers only if its PostgreSQL
database version is same as the Primary server. For example, you cannot run the backup utility from
a SLES 9 secondary server if the primary server is a SLES 10 server. This is because the SLES 9
server's pg_dump utility, which is used by the backup utility, is incompatible with the PostgreSQL
database version running on the primary server. You have to run the backup utility on the primary
server.

86 Novell ZENworks 7.2 Linux Management Administration Guide

A directory with the current date is created at /var/opt/novell/zenworks/backup/db.
The backup file, named timestamp-zenworks-backup.tar.gz, is saved in this directory.
For example, if the backup is taken on August 23, 2005 at 11:30 p.m., the following directory and
file are created:

/var/opt/novell/zenworks/backup/db/2005-08-23/23:30:00-zenworks­backup.tar.gz

Log information about the backup operation is saved in the /var/opt/novell/log/
zenworks/dbbackup.log file.

The utility does not require any user interaction. If desired, you can schedule the database backup
operation as a cron job.

9.2.4 Restoring the ZENworks Data Store

This section applies only if you are using the PostgreSQL database for your Data Store.

If necessary, you can restore the ZENworks Data Store from a backup you created. You use
zlm_dbrestore.sh, located in /opt/novell/zenworks/sbin, to restore the Data Store
from a backup.

novdocx (en) 11 July 2008

The restore operation drops the existing database and creates a new one.

To restore the ZENworks Data Store:

1 On all ZENworks Servers, stop the ZENworks Server (novell-zenserver) and the ZENworks

Loader (novell-zenloader) services by using the following commands:

/etc/init.d/novell-zenserver stop

/etc/init.d/novell-zenloader stop

Because all ZENworks Servers access the Data Store, you need to stop these services on all
ZENworks Servers on your system. You must also ensure that external connections, if any, to
the database are terminated.

2 Make sure you are logged in as root to a ZENworks Server.

3 On the ZENworks Primary Server, enter the following at the command prompt:

zlm_dbrestore.sh -F path_to_the_backup_file

NOTE: If you have taken a database backup from the Secondary server, you can restore the
database only if the PostgreSQL database version is same on both the Primary and Secondary
servers.

Make sure that the -F option includes the backup file's complete path. For example:

zlm_dbrestore.sh -F /var/opt/novell/zenworks/backup/db/2005-08-23/23:30:00­zenworks-backup.tar.gz

4 If prompted, enter Y to stop the ZENworks Server (novell-zenserver).

5 If prompted, enter Y to stop the ZENworks Loader (novell-zenloader).

6 When prompted to supply a password to drop the database, enter the password configured in /

etc/opt/novell/zenworks/hibernate.cfg.xml that is used for authenticating the
PostgreSQL database.

ZENworks Object Store and Data Store Maintenance 87

7 When prompted to supply a password to create the new database, enter the password

configured in /etc/opt/novell/zenworks/hibernate.cfg.xml that is used for
authenticating the PostgreSQL database.

The log information about the restore operation is saved in the file /var/opt/novell/
log/zenworks/dbrestore.log.

8 After the restore is complete, you need to ensure that the Data Store is synchronized with the

Object Store. For instructions, see Section 9.4, “Synchronizing the Object Store and Data

Store,” on page 94.

9 On all ZENworks Servers, start the ZENworks Server (novell-zenserver) and the ZENworks

Loader (novell-zenloader) by using the following commands:

/etc/init.d/novell-zenserver start

/etc/init.d/novell-zenloader start

9.2.5 Optimizing the Server Database

To improve the server database performance, use the zlm-pg-vacuum script, found in the /opt/
novell/zenworks/bin directory on the ZENworks Server. When you install a ZENworks

Primary Server using a local PostgreSQL database, the installation program creates a script that runs
on a daily basis.

novdocx (en) 11 July 2008

The zlm-pg-vacuum script runs the vacuumdb command, which has a significant impact on
database performance. You must log in as root before running the zlm-pg-vacuum script. For
the optimal performance, run the following vacuum scripts:

 zlm-pg-vacuum or zlm-pg-vacuum --busy-tables: Depending on the database activity, run

the script daily to weekly. Run the script once a week on a lightly loaded server and once a day
on a heavily loaded server.

 zlm-pg-vacuum --full: Run the script during a period of less activity or during downtime for

the database server. Depending on the database activity, run the script weekly or bi-weekly. It
performs a full vacuum analyze and exclusively locks tables. It is recommended that you
manually run the zlm-pg-vacuum --full script once a month by performing the
following steps:

1.Stop all the ZENworks services by executing zlm-config --stop.

2. Execute zlm-pg-vacuum --full.

3. Start all the ZENworks services by executing zlm-config --start.

Additionally, you can fine-tune the following parameters depending on your memory requirements
and scale:

 In the /etc/sysctl.conf file, configure kernel.shmmax.

 In the postgresql.conf file, configure shared_buffer, sort_mem, vacuum_mem,

wal_buffers, and checkpoint_segments.

For more information on how to fine-tune the parameters, see the PostgreSQL documentation (http:/

/www.postgresql.org/docs/).

Following is a sample scenario that illustrates how you can fine-tune the database parameters. The
values indicated in this scenario are sample values; you must fine-tune it according to your
requirements. For more information on how to fine-tune the parameters, see the PostgreSQL

documentation (http://www.postgresql.org/docs/)

88 Novell ZENworks 7.2 Linux Management Administration Guide

An Example Scenario: In this scenario, assume that the ZENworks server is running on an IBM
x346 with two Xeon processors and 4 GB of RAM. The database is running on the same server. 2
GB of RAM is dedicated to the other ZENworks processes, 1 GB of RAM to the operating system
and non-ZENworks processes, and the remaining 1 GB of RAM is for PostgreSQL.

To optimize the server database performance:

1 In the /etc/sysctl.conf file, set the value of kernel.shmmax to 1572864000 so

that the process can have 1.5 GB of shared memory.

The shmmax kernel parameter allows PostgreSQL to consume more shared memory. By
default, the kernel only allows a process to consume 32 MB of shared memory.

NOTE: This step is not applicable if ZENworks 7.2 Linux Management is running on SLES 10
device because the value of kernel.shmmax is 4 GB by default on SLES 10.

2 In the postgresql.conf file, configure the following parameters:

 shared_buffers = 131072

 sort_mem = 10240

 vacuum_mem = 102400

 wal_buffers = 20

 checkpoint_segments = 20

novdocx (en) 11 July 2008

3 Reboot the server for the changes to take effect.

9.2.6 Restarting Novell Zenworks Server Services After Restarting the Database

After restarting the PostgresSQL database on the ZENworks Linux Management Server, the
database connections will be restored in approximately 15 minutes. During this time, the ZENworks
Control Center and zlman utility might display database-connection errors.

To restore the connections immediately, restart the novell zenworks services by running the
following command:

/opt/novell/zenworks/bin/zlm-config --restart

9.3 Maintaining the ZENworks Data Store on Oracle

The following sections provide instructions for backing up and recovering a ZENworks Data Store
using Oracle:

 Section 9.3.1, “Backup and Recovery Solutions,” on page 90

 Section 9.3.2, “Setting Environment Variables,” on page 90

 Section 9.3.3, “Connecting to the Database,” on page 91

 Section 9.3.4, “Starting the Database,” on page 91

 Section 9.3.5, “Backing Up the Database,” on page 91

ZENworks Object Store and Data Store Maintenance 89

 Section 9.3.6, “Recovering the Database,” on page 92

 Section 9.3.7, “Shutting Down the Database,” on page 94

9.3.1 Backup and Recovery Solutions

Oracle provides two methods of backup and recovery:

 Recovery Manager (RMAN)

 User-managed backup and recovery.

The RMAN utility is automatically installed with the database. It can back up an Oracle8 database
and all later versions of an Oracle* database. RMAN uses server sessions on the database to perform
backup and recovery. RMAN has its own syntax and is accessible either through a command-line
interface or through the Oracle Enterprise Manager GUI. RMAN also provide APIs to interface with
third-party media managers.

The advantage of RMAN is that it obtains and stores metadata about its operations in the control file
of the database. An independent recovery catalog can be set up, which is a schema that contains
metadata imported from the control file, in a separate recovery catalog database. RMAN performs
the necessary record keeping for backups, archived logs, and so forth using the metadata, so
restoration and recovery is greatly simplified.

novdocx (en) 11 July 2008

An alternative method of performing recovery is to use operating system commands for backups and
SQL*Plus for recovery. This method is called User-managed backup and recovery.

RMAN automates backup and recovery, but the User-managed method requires keeping track of all
database files and backups. Therefore, because of its robustness and simplified database
administration abilities, RMAN is a highly recommended tool for backup operations. The
subsequent sections of this document explain the steps for using RMAN to perform a complete
database backup and recovery.

9.3.2 Setting Environment Variables

1 Set the following environment variables to the appropriate values before using RMAN:

 ORACLE_HOME: The directory where the Oracle software is installed. For example:

ORACLE_HOME=/home/oracle/product/9ir2

 CLASSPATH: The paths to the libraries installed by Oracle. For example:

CLASSPATH=$CLASSPATH:/oracle/opt/oracle/product/9ir2/JRE:/
oracle/opt/oracle/product/9ir2/jlib:/oracle/opt/oracle/
product/9ir2/rdbms/jlib:/oracle/opt/oracle/product/9ir2/
network/jlib

 PATH: The Oracle installation’s bin directory. For example:

PATH=$PATH:/home/oracle/product/9ir2/bin

90 Novell ZENworks 7.2 Linux Management Administration Guide

9.3.3 Connecting to the Database

You can use either of the following methods to connect to the Oracle database being used for the
Data Store:

 Start RMAN at the operating system command line without connecting to a database, by

issuing the RMAN command without any connection options:

$ rman RMAN> CONNECT TARGET /

 Start the RMAN executable at the operating system command line while connecting to the

database:

$ rman TARGET /

If the database is already mounted or open, RMAN displays output similar to the following:

Recovery Manager: Release 9.2.0.0.0
connected to target database: RMAN (DBID=1237603294)

The DBID value displayed is the database identifier for the target database.

novdocx (en) 11 July 2008

If the target database is not started, RMAN shows the following message:

connected to target database (not started)
RMAN> # the RMAN prompt is displayed

9.3.4 Starting the Database

1 Start the database using the following command:

RMAN> startup mount

This command starts an Oracle instance if it is not already started, and mounts the database but
does not open it.

If the mount was successful, then the following output is displayed:

Oracle instance started
database mounted

Otherwise, appropriate error messages are displayed, indicating the causes of failure and
suitable solutions.

9.3.5 Backing Up the Database

You can back up the database to the default disk location. The default location is OS-specific. On
Linux, the default path where backup files are stored is $ORACLE_HOME/dbs.

To make a full backup of the data files, control files, and the current server parameter file to the
default device type (which is the disk), use the following backup command at the RMAN prompt:

RMAN> BACKUP DATABASE;

In the above command, the FORMAT parameter is not specified, so RMAN automatically gives
each backup piece a unique name and stores it in the OS-specific default location
($ORACLE_HOME/dbs on Linux).

To specify a filename for the backup piece, use the backup command with the FORMAT parameter:

ZENworks Object Store and Data Store Maintenance 91

RMAN> BACKUP DATABASE FORMAT’/tmp/%U’;

%U generates a unique filename.

The RMAN backup command creates a backup set, which is a logical object that contains one or
more backup pieces.

The backup command output contains the essential information about the backup, as shown in the
following example:

Starting backup at OCT 12 2001 19:09:48
using target database controlfile instead of recovery catalogal
located channel: ORA_DISK_1
channel ORA_DISK_1: sid=10 devtype=DISK
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
including current SPFILE in backupset
including current controlfile in backupset
input datafile fno=00001 name=/oracle/oradata/zenworks/system01.dbf
input datafile fno=00002 name=/oracle/oradata/zenworks/undotbs01.dbf
input datafile fno=00003 name=/oracle/oradata/zenworks/cwmlite01.dbf
input datafile fno=00004 name=/oracle/oradata/zenworks/drsys01.dbf
input datafile fno=00005 name=/oracle/oradata/zenworks/example01.dbf
input datafile fno=00006 name=/oracle/oradata/zenworks /indx01.dbf
input datafile fno=00007 name=/oracle/oradata/zenworks/tools01.dbf
input datafile fno=00008 name=/oracle/oradata/zenworks/users01.dbf
channel ORA_DISK_1: starting piece 1 at OCT 12 2001 19:09:56
channel ORA_DISK_1: finished piece 1 at OCT 12 2001 19:10:31
piece handle=/oracle/dbs/lvd6dtk1_1_1 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:39
Finished backup at OCT 12 2001 19:10:33

novdocx (en) 11 July 2008

9.3.6 Recovering the Database

You can recover a restored data file by applying archived redo logs and online redo logs; that is,
records of changes made to the database after the backup was taken. The following sections provide
instructions for two methods you can use to recover the database:

 “Complete Recovery” on page 92

 “Incomplete Recovery” on page 93

Complete Recovery

Complete recovery involves using redo data or incremental backups combined with a backup of a
database, tablespace, or data file, to update it to the most current point in time. This is called a
complete recovery because Oracle applies all of the redo changes contained in the archived and
online logs to the backup. Typically, a complete media recovery is performed after a media failure
damages data files or the control file.

1 Use the following sequence of commands to perform a complete recovery of the database:

RMAN> connect target / RMAN> run { 2> startup mount; 3> restore
database; 4> recover database; 5> alter database open; 6> }

92 Novell ZENworks 7.2 Linux Management Administration Guide

This results in all data files being restored and then recovered. RMAN applies archive logs as
necessary until the recovery is complete.

2 After the restore is complete, you need to ensure that the Data Store is synchronized with the

Object Store. For instructions, see Section 9.4, “Synchronizing the Object Store and Data

Store,” on page 94.

Incomplete Recovery

RMAN can perform recovery of the whole database to a specified non-current time, SCN, or log
sequence number. This type of recovery is called incomplete recovery because it does not
completely use all of the available redo logs. Incomplete recovery of the whole database is also
called database point-in-time recovery (DBPITR).

You should perform an incomplete recovery of the database in the following situations:

 Media failure destroys some or all of the online redo logs.

 A user error causes data loss, for example, a user inadvertently drops a table.

 You cannot perform a complete recovery because an archived redo log is missing.

novdocx (en) 11 July 2008

To perform an incomplete recovery, restore all data files from backups created prior to the time
when a recovery is needed, and then open the database with the RESETLOGS option after recovery
completes. The RESETLOGS operation creates a new instance of the database—in other words, a
database with a new stream of log sequence numbers starting with log sequence 1.

The database must be closed to perform an incomplete recovery.

To perform an incomplete recovery:

1 Set the time format environment variable:

$ NLS_DATE_FORMAT="Mon DD YYYY HH24:MI:SS"

2 Use the following sequence of steps:

$ rman target /RMAN> startup mount; RMAN> run { 2> set until
time "to_date(’Mar 16 2005 10:24:00’, ’MM DD YYYY
HH24:MI:SS’)";3> restore database; 4> recover database; 5> }

RMAN uses the last backup created before the time mentioned in the set until command to
restore the files to their default locations. Then, it uses archived redo logs (if needed) to recover
the database.

Two other parameters that can be used with the set until command are SCN and log
sequence numbers. You obtain SCNs from the alert logs. Find the SCN of an event and recover
to a prior SCN. For example:

SET UNTIL SCN 1000

3 If recovery was successful, open the database and reset the online logs:

ALTER DATABASE OPEN RESETLOGS;

4 After the restore is complete, you need to ensure that the Data Store is synchronized with the

Object Store. For instructions, see Section 9.4, “Synchronizing the Object Store and Data

Store,” on page 94.

ZENworks Object Store and Data Store Maintenance 93

We recommend that you back up the database immediately, preferably with the database mounted
(to avoid possible data loss in an open database). Because the database is a new instance, the
backups made before the RESETLOGS are not easily usable.

9.3.7 Shutting Down the Database

1 Use the following command to shut down the database:

RMAN> SHUTDOWN NORMAL;

This command dismounts the database and stops the running Oracle instance.

9.4 Synchronizing the Object Store and Data Store

If you've restored either the Object Store or the Data Store from backup, you need to make sure the
two are synchronized. The dbsync.sh utility lets you synchronize the Data Store with the Object
store by removing all devices and bundles that are found in the Data Store but not in the Object
Store.

novdocx (en) 11 July 2008

1 Make sure you are logged in as root to the ZENworks Server.

2 Enter the following command on the command prompt:

dbsync.sh [--force]

The utility has one option, --force or -f. The synchronization operation compares the list of
devices and bundles in the two databases. When you use the --force option, dbsync.sh logs the
GUIDs and names of the devices and bundles found in the Data Store but not in the Object
Store. When you use the --force option, dbsync.sh deletes all devices and bundles that are
found in the Data Store but not in the Object Store.

3 Enter the password to authenticate to the Object Store.

The GUIDs and names of the devices and bundles that are in the Data Store but not in the Object
Store are logged in the /var/opt/novell/log/zenworks/dbsync-message.log file.

9.5 Cleaning Up the ZENworks Database

The ZENworks Database Clean-Up utility of ZENworks 7.2 Linux Management IR2 helps you to
delete inconsistent data from your ZENworks database running on PostgreSQL or Oracle. You can
use the utility to clean up the database installed on a server that has ZENworks 7.2 Linux
Management newly installed, but not on a server that has been upgraded from earlier versions of
ZENworks to ZENworks 7.2 Linux Management.

To clean up the ZENworks database, enter the following command at the server console prompt:

zlm_db_cleanup.sh

To troubleshoot any errors encountered while running the database clean-up command, refer to the /
var/opt/novell/log/zenworks/dbcleanup.log.

94 Novell ZENworks 7.2 Linux Management Administration Guide

III

Device Registration

The following sections provide information about Novell® ZENworks® Linux Management device
registration:

 Chapter 10, “Registration Overview,” on page 97

 Chapter 11, “Registering Devices,” on page 99

 Chapter 12, “Managing Registration Keys and Rules,” on page 101

 Chapter 13, “Unregistering and Reregistering Devices,” on page 115

novdocx (en) 11 July 2008

III

Device Registration

95

novdocx (en) 11 July 2008

96 Novell ZENworks 7.2 Linux Management Administration Guide

10

Registration Overview

Novell® ZENworks® Linux Management provides simplified, hands-off management of devices
(servers and workstations). Before you can configure application settings through the use of
policies, install packages using bundles or catalogs, use preboot services to image devices, collect
hardware and software inventory, remotely manage devices, and report on events, you need to install
the ZENworks Linux Management Agent on devices and register them against a ZENworks Server.

The ZENworks Management Zone is the top level of the ZENworks management hierarchy. The
Management Zone provides an autonomous administrative unit of ZENworks Servers and managed
devices (workstations and servers). You use the ZENworks Control Center (the Web-based
administrative tool) to manage devices. The ZENworks Servers and managed devices work together
to apply the management tasks.

Any device that you want to manage must be registered in the Management Zone. Registering the
device adds the device to the ZENworks Object Store and allows you to manage it through the
ZENworks Control Center.

novdocx (en) 11 July 2008

10

For Novell ZENworks to manage a device, you must install the ZENworks Agent software on the
device. During installation of the ZENworks Agent software, the device is automatically registered
as long as you (or whoever is installing the software) supplies the DNS name or IP address of a
ZENworks Server in your Management Zone. You can also register devices at a later time. For more
information, see Chapter 11, “Registering Devices,” on page 99.

You can also create registration keys or registration rules to register devices in the Management
Zone.

Using registration keys lets you define the keys that are used to register devices in the Management
Zone. A registration key specifies a set of assignments that are applied to devices that register using
that key. The key must be applied during installation of the ZENworks Agent on a device, either
manually or by using a script. For more information, see Section 12.1, “Managing Registration

Keys,” on page 102

If you do not want to use registration keys, you can create registration rules to determine a device's
assignments when it registers without using a key. The major difference between using the default
registration rules versus using a registration key is that the default registration rules use a filter to
determine which set of device assignments to apply, but a key corresponds directly to a specific set
of assignments to apply. For more information, see Section 12.2, “Managing Registration Rules,” on

page 107.

NOTE: You can register devices against only one ZENworks 7.2 Linux Management Server.
However, you can register devices against one ZENworks 7.2 Server and multiple ZENworks 6.6.x
Linux Management Servers. Registering devices against multiple Servers is useful, for example,
during the transitional period while you deploy ZENworks 7.2.

Registration Overview

97

novdocx (en) 11 July 2008

98 Novell ZENworks 7.2 Linux Management Administration Guide

11

Registering Devices

The process of registering devices includes installing the ZENworks® Agent on devices and then
registering the devices against a ZENworks Server. During installation of the ZENworks Agent
software, the device is automatically registered as long as you (or whoever is installing the software)
supplies the IP address or DNS name of a ZENworks Server in your Management Zone. You can
also register devices at a later time.

NOTE: If you plan to update Dell PowerEdge servers using Dell Update Packages, we recommend
that you mirror the packages from the Dell FTP site before installing the ZENworks Agent on the
managed PowerEdge servers. You can also mirror the packages after installing the ZENworks Agent
on the managed PowerEdge servers but before registering them in the ZENworks Management
Zone. Mirroring the Dell Update Packages prior to installing the ZENworks Agent or registering the
servers in the Management Zone ensures that all Dell model numbers are loaded into the database,
the standard reports are run as the servers register, and the Dell Update Packages exist in the
ZENworks package repository. For more information, see Chapter 23, “Using Dell Update Package

Bundles,” on page 279.

novdocx (en) 11 July 2008

11

The following sections contain additional information:

 Section 11.1, “Installing the ZENworks Agent and Registering Devices,” on page 99

 Section 11.2, “Registering a Device after Installing the ZENworks Agent,” on page 99

 Section 11.3, “Automatically Registering the Services at the Initial Startup of zmd,” on

page 100

11.1 Installing the ZENworks Agent and Registering Devices

You can register devices (servers or workstations) against a ZENworks Server during installation of
the ZENworks Agent on devices.

For more information about manually installing and registering the agent or automating installation
and registration using a script, see “Setting Up Managed Devices” in the Novell ZENworks 7.2 Linux

Management Installation Guide.

11.2 Registering a Device after Installing the ZENworks Agent

If the person who installed the ZENworks Agent on a device did not specify the Server address (IP
address or DNS name) during installation, the device can be registered at a later time by running the
following rug command from the device:

For SUSE LINUX Enterprise Server 10 (SLES 10) and SUSE LINUX Enterprise Desktop 10
(SLED 10) managed devices:

/usr/bin/rug sa https://ZEN_Server_address

For all other managed devices:

Registering Devices

99

/opt/novell/zenworks/bin/rug sa https://ZEN_Server_address

Replace ZEN_Server_address with the IP address or DNS name of the primary or secondary server.

You can also register a device by using the Software Installer or Updater. For more information, see

Section 6.3, “Using the Software Updater, Installer, and Remover from Users’ Managed Devices,”
on page 54.

11.3 Automatically Registering the Services at the Initial Startup of zmd

zmd can automatically register the services configured in the initial-configuration file.
The file is located in /etc/zmd/ on SLES 10 and SLED 10 managed devices, and in /etc/opt/
novell/zenworks/zmd/ on other managed devices.

The initial-configuration file contains the URL for the supported services that zmd
registers at initial startup. zmd uses the information in the in the initial-configuration file
to mount all the services the first time it starts. These services are not loaded during the subsequent
startups because zmd records the already mounted services in @localstatedir@/lib/zmd/
services. If you want zmd to mount the services listed in initial-configuration every
time it starts, you must delete the services file before starting zmd.

novdocx (en) 11 July 2008

To have zmd automatically register devices, you must manually create the initial­configuration file with the following contents:

[URL of the service]

type = service_type

key = service_name

In the file, you can also specify the registration_code for services that need a key for
registration.

If you want to use special characters such as $ ! & ; ‘ “ in the key value, you must enclose the value
within single quotes.

A sample initial-configuration file is as follows:

[https://10.0.0.0]

type=zenworks

[https://update.novell.com/data]

type=rce

[http://www2.ati.com/suse]

type=YUM

key=yum_service

100 Novell ZENworks 7.2 Linux Management Administration Guide