Novell ZENWORKS LINUX MANAGEMENT 7.3 IR2 - ADMINISTRATION GUIDE 02-12-2010 Administration Manual

Table of Contents

Quick Links

Download this manual

AUTHORIZED DOCUMENTATION

Administration Guide

Novell

ZENworks

Linux Management

7.3 IR2

February 12, 2010

www.novell.com

Novell ZENworks 7.3 Linux Management Administration Guide

Table of Contents

Summary of Contents for Novell ZENWORKS LINUX MANAGEMENT 7.3 IR2 - ADMINISTRATION GUIDE 02-12-2010

Page 1 AUTHORIZED DOCUMENTATION Administration Guide Novell ® ZENworks Linux Management ® 7.3 IR2 February 12, 2010 www.novell.com Novell ZENworks 7.3 Linux Management Administration Guide...
Page 2 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.
Page 3 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.
Page 4 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 5: Table Of Contents
Accessing the ZENworks Control Center ......... 41 Accessing the ZENworks Control Center through Novell iManager..... 42 Changing the Timeout Value for the ZENworks Control Center.
Page 6 Configuring the Content Replication Schedule ........75 Viewing Default Target Platforms and Configuring Custom Target Platforms ... . . 75 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 7 Configuring the ZENworks Management Daemon (zmd) Settings..... . 76 7.11 Integrating Novell Customer Center with ZENworks Linux Management ....77 7.12 Configuring the ZENworks Server Preferences .
Page 8 Novell Linux Desktop Policy ........
Page 9 17.7.4 Editing Text File Policies ..........197 17.7.5 Viewing Policy Enforcement Status .
Page 10 Testing and Performing the Mirroring Operation by Using the xzlmmirror Utility . . . 307 25.4 Distributing Catalogs from a Public ZENworks Linux Management Server ....308 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 11 25.4.1 Creating a Public ZENworks Linux Management Server..... 308 25.4.2 Accessing a Public ZENworks Linux Management Server ....308 25.5 Mirroring Dell Update Packages to Your ZENworks Server.
Page 12 Opening an Image ............468 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 13 31.5 Saving Image Changes and Exiting the Utility ........468 31.6 Managing Image Properties .
Page 14 Configuring Database Maintenance Settings ......525 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 15 40.1.2 Configuring Centralized Log Settings ........526 40.1.3 Configuring SMTP Settings .
Page 16 Resizing a Partition in an Image ........612 Novell ZENworks Linux Management Imaging Agent (novell-zislnx) ....612 Image-Safe Data Viewer and Editor (zisview and zisedit) .
Page 17 Modifying ZENworks Imaging Resource Files ........650 F.4.1 Adding Files to an Imaging Boot CD .
Page 18 Appendix ............683 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 19: About This Guide
ZENworks 7.3 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.3 Linux Management Installation Guide Novell ZENworks 7.3 Linux Management Troubleshooting Guide In addition, the other capabilities included in the ZENworks 7 suite have extensive documentation for your use.
Page 20 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 ( , etc.) denotes a Novell trademark. An asterisk (*) denotes a third-party trademark.
Page 21: Part I Understanding Zenworks Linux Management
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...
Page 22 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 23: Quick Tutorial On Basic Zenworks Linux Management Features
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.
Page 24: Folders
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. Novell ZENworks 7.3 Linux Management Administration Guide...
Page 25: Folders Vs. Groups
“Automating Installation of the ZENworks Agent” in the Novell ZENworks 7.3 Linux Management Installation Guide). When 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.
Page 26: Setting Up Zenworks Administrator Accounts
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). Novell ZENworks 7.3 Linux Management Administration Guide...
Page 27: Delivering Software Packages
To limit administrator rights, you assign an account rights at the folder level. The root folders are , and . Rights assigned at a root folder are effective in all Bundles /Devices /Policies /Reports subfolders (for example, ) unless specifically overridden at the subfolder /Bundles/Workstations level.
Page 28: Bundles
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. Novell ZENworks 7.3 Linux Management Administration Guide...
Page 29: Defining And Locking Down Device Configuration Settings
Evolution e-mail client 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.
Page 30: Using Preboot Services
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. Novell ZENworks 7.3 Linux Management Administration Guide...
Page 31: Monitoring Events
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.3 Linux Management Installation Guide. For more information about managing remote devices, see “Remote Management” on page 493.
Page 32: System Event Log
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. Novell ZENworks 7.3 Linux Management Administration Guide...
Page 33 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. For more information about reports, see Part X, “Reports,” on page 531. A Quick Tutorial on Basic ZENworks Linux Management Features...
Page 34 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 35: Using Zenworks Linux Management With Dell Poweredge Servers
Using ZENworks Linux 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...
Page 36: Obtaining, Configuring, And Updating Poweredge Servers Using Dell Update Package
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. Novell ZENworks 7.3 Linux Management Administration Guide...
Page 37: Determining If Newer Dell Package Updates Are Available For Poweredge Servers
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.
Page 38: Deploying A Newer Dell Update Package
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 539. Novell ZENworks 7.3 Linux Management Administration Guide...
Page 39: Part Ii Zenworks System Management
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,”...
Page 40 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 41: 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,”...
Page 42: Accessing The Zenworks Control Center Through Novell Imanager
ZENworks Linux Management includes a Novell plug-in module ( ) that you can use to access .npm 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 ( ) from the Novell ZENworks 7.3 Linux Management CD to a...
Page 43: Changing The Debug Settings Of Zenworks Control Center
RemoteManagement WebFramework mirrorStatus The error messages logged to WebLogger.debugForTag() are written to the standard output. 4 Save the file. config.xml 5 Restart the service by executing the following command: /etc/init.d/novell-zenserver restart ZENworks Control Center...
Page 44 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 45: Command Line Administration Utilities
Command Line Administration 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.
Page 46: Zlmmirror
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 551). Novell ZENworks 7.3 Linux Management Administration Guide...
Page 47: Zenworks Server
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,”...
Page 48: Checking The Status Of A Zenworks Service
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)
Page 49: Stopping A Zenworks Service
/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 - option to start all services rather than starting them one at a time. -start 5.1.3 Stopping a ZENworks Service To stop a service, use the following command: /etc/init.d/servicename stop...
Page 50: Package Replication
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: Novell ZENworks 7.3 Linux Management Administration Guide...
Page 51: Uninstalling A Secondary Zenworks Server By Using Zlm-Config
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‘ ;...
Page 52: Freeing Disk Space On A Zenworks Server
-e | package_name 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.
Page 53: Zenworks Agent
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),”...
Page 54: File System Access
These three desktop applets replace the user interface clients used in previous versions of ZENworks Linux Management. Software Updater, Novell ZENworks 7.3 Linux Management Administration Guide...
Page 55: Updating Software
“Selecting and Applying Updates” on page 58 Launching the Software Updater 1 Launch the Software Updater by navigating to and running /opt/novell/zenworks/bin with root privileges. To run it as a daemon, run zen-updater 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.
Page 56 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.
Page 57 2 Select the services you want to delete, then click Remove Service. 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.
Page 58: Installing Software
If an administrator has assigned catalogs to users’ devices, the catalogs display in the Software Installer. “Configuring Package Sources” on page 59 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 59 3 Click Add Service. 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. ZENworks Agent...
Page 60 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 and running /opt/novell/zenworks/bin with privileges. zen-installer root Novell ZENworks 7.3 Linux Management Administration Guide...
Page 61: Removing Software
6.3.3 Removing Software The Software Remover lets you remove software on a managed device. The utility is in the /opt/ directory. novell/zenworks/bin 1 Launch Software Remover by navigating to and running /opt/novell/zenworks/bin zen- with root privileges.
Page 62: 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 2 Click the Preferences tab. Novell ZENworks 7.3 Linux Management Administration Guide...
Page 63: Editing System Preferences
This window shows the system preferences. NOTE: You can also display this list from the command line using For more rug get. information, see rug (1) (page 586). 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.
Page 64 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. Novell ZENworks 7.3 Linux Management Administration Guide...
Page 65 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.The available options are URL, Bypass, or an empty string. By default, it is set to an empty string, and the device uses the system proxy.
Page 66: Uninstalling The Zenworks Agent
-e | package_name 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.
Page 67 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 that are associated to these zmd.conf...
Page 68 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 69: Configuring Management Zone Settings
Section 7.9, “Viewing Default Target Platforms and Configuring Custom Target Platforms,” on page 75 Section 7.10, “Configuring the ZENworks Management Daemon (zmd) Settings,” on page 76 Section 7.11, “Integrating Novell Customer Center with ZENworks Linux Management,” on page 77 Section 7.12, “Configuring the ZENworks Server Preferences,” on page 78 Section 7.13, “Understanding the StoreFileDeps Preference,”...
Page 70: Creating System Variables
. On SLES 9, the file is located at and on SLES deviceid /etc/opt/novell/zenworks/zmd, 10 it is located at . Assume that you want to place a copy of in the /etc/zmd deviceid /tmp Novell ZENworks 7.3 Linux Management Administration Guide...
Page 71 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 Value: /etc/opt/novell/zenworks/zmd 6 Click OK. 7 Click Apply, then click OK. Creating a System Variable for the SLES 10 Managed Device 1 In ZENworks Control Center, click the Devices tab.
Page 72: Configuring The Device Refresh Schedule
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. Novell ZENworks 7.3 Linux Management Administration Guide...
Page 73: Configuring Local Device Logging
. For all other devices, it is /var/log /var/ opt/novell/log/zenworks Log message to a local file if severity is: Specify filtering criteria based on severity. By default, this option is selected if you are on ZENworks 7.3 Linux Management. For a new installation of ZENworks 7.3 Linux Management with IR1IR2, this option is deselected...
Page 74: Configuring Preboot Services
Zone Level,” on page 497 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 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 75: Configuring The Content Replication Schedule
E-mail notification SNMP traps For detailed information, see Section 40.1.2, “Configuring Centralized Log Settings,” on page 526. 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.
Page 76: Configuring The Zenworks Management Daemon (Zmd) Settings
To configure a zmd setting: 1 In the ZENworks Control Center, click the Configuration tab. 2 Click ZMD Settings. 3 Click Add to open the Configure Setting dialog box. Configure Setting dialog box. Figure 7-2 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 77: Integrating Novell Customer Center With Zenworks Linux Management
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: Review the status of supported Novell products, subscriptions, and services...
Page 78: Configuring The Zenworks Server Preferences
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. 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.
Page 79: Understanding The Storefiledeps Preference
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.
Page 80 Select one or more days of the week to run the scheduled event on and set other restrictions that might apply. 7 Click Apply. IMPORTANT: The Set the "Black Out" time ranges when execution should not occur option is nonfunctional. Novell ZENworks 7.3 Linux Management Administration Guide...
Page 81: Zenworks Administrator Accounts
Accounts During installation, a default Administrator account is created. This account provides rights to ® ® administer all of your Novell ZENworks system. 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.
Page 82: Modifying Account Rights
You assign rights at the folder level. The root folders are /Bundles /Devices /Policies . Rights assigned at a root folder are effective in all subfolders (for example, /Reports ) unless specifically overridden at the subfolder level. Bundles/Workstations Novell ZENworks 7.3 Linux Management Administration Guide...
Page 83 For example, if you want the administrator to be able to view bundles that are located in the folder and create, delete, or modify bundles in the folder, Bundles /Bundles/Workstations you would assign the administrator View rights to the folder and All rights to the /Bundles folder.
Page 84 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 85: Zenworks Object Store And Data Store Maintenance
ZENworks Object Store and Data 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.
Page 86: Restoring The Zenworks Object Store
5 After the restore operation 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 The log information about the restore operation is saved to /var/opt/novell/log/zenworks/ ndsrestore.log Novell ZENworks 7.3 Linux Management Administration Guide...
Page 87: Deleting The 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"?> <ZLMedirectoryCleanup xmlns="http://www.novell.com/zenworks/ edirectoryCleanup" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <Tree> <ZoneName> Management_Zone_Name </ZoneName>...
Page 88: Maintaining The Zenworks Data Store On Postgresql
Section 9.2.4, “Restoring the ZENworks Data Store,” on page 89 Section 9.2.5, “Optimizing the Server Database,” on page 90 Section 9.2.6, “Restarting Novell Zenworks Server Services After Restarting the Database,” on page 92 9.2.1 Displaying the Password for the Default PostgreSQL...
Page 89: Restoring The Zenworks Data Store
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...
Page 90: Optimizing The Server Database
Object Store. For instructions, see Section 9.4, “Synchronizing the Object Store and Data Store,” on page 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...
Page 91 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 script once a month by performing the following zlm-pg-vacuum --full...
Page 92: Restarting Novell Zenworks Server Services After Restarting The Database
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...
Page 93: Setting Environment Variables
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.
Page 94: Starting The Database
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: Novell ZENworks 7.3 Linux Management Administration Guide...
Page 95: Recovering The Database
Starting backup at JULY 12 2009 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...
Page 96 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: Novell ZENworks 7.3 Linux Management Administration Guide...
Page 97: Shutting Down The Database
ZENworks database objects schema by running the export utilities as follows as an Oracle database user: exp zenadmin/novell@ORCL FILE=NOVELL-ZENWORKS-ORAZLM.DMP LOG=NOVELL- ZENWORKS-ORAZLM.LOG OWNER=ZENADMIN where ORCL is the default Oracle system identifier, and novell is the default password for the zenadmin user. This creates the backup file and the NOVELL-ZENWORKS-ORAZLM.DMP...
Page 98: Synchronizing The Object Store And Data Store
9.5 Cleaning Up the ZENworks Database 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 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 99: Part Iii Device Registration
Device Registration I I I ® ® The following sections provide information about Novell ZENworks Linux Management device registration: Chapter 10, “Registration Overview,” on page 101 Chapter 11, “Registering Devices,” on page 103 Chapter 12, “Managing Registration Keys and Rules,” on page 107 Chapter 13, “Unregistering and Reregistering Devices,”...
Page 100 100 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 101: Registration Overview
ZENworks Object Store and allows you to manage it through the ZENworks Control Center. 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.
Page 102 102 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 103: Registering 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.3 Linux Management Installation Guide. 11.2 Registering a Device after Installing the ZENworks Agent...
Page 104: Automatically Registering The Services At The Initial Startup Of Zmd
If you want to use special characters such as $ ! & ; ‘ “ in the key value, you must enclose the value within single quotes. A sample file is as follows: initial-configuration [https://10.0.0.0] type=zenworks [https://update.novell.com/data] type=rce [http://www2.ati.com/suse] type=YUM 104 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 105 key=yum_service Registering Devices 105...
Page 106 106 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 107: Managing Registration Keys And Rules
Managing 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 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.
Page 108: Managing Registration Keys
12.1.1 Creating Keys to Register Devices 1 In the ZENworks Control Center, click the Configuration tab. 2 In the Registration Keys section, click New, then click Registration to launch the Create New Registration Key Wizard. 108 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 109 3 Fill in the fields: Name (used as the registration key code): Provide a name for the registration key. When devices register during installation or later using the command, this is the name the rug sa device provides to be assigned this registration. Any device that presents this name is given the assignments associated with this registration.
Page 110 6 Click Next to display the Group Membership page. 110 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 111: Editing Existing Registration Keys
Adding groups causes registering devices to receive any assignments provided by membership in the groups. Assignments from group membership are additive, so if a device is assigned to both group A and group B, the device receives all assignments from both groups. Click Add to add a group.
Page 112: Renaming, Copying, Or Moving Registration Keys
Rename and Copy options are not available from the Edit menu. 12.1.4 Deleting Registration Keys 1 In the ZENworks Control Center, click the Configuration tab. 2 Select the key by clicking the check box next to the key, then click Delete. 112 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 113: Managing Registration Rules
12.2 Managing Registration Rules Registration rules let you 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.
Page 114 5a Select an option from the drop-down list in the left field, select Equal to, Contains, Starts with, or Ends with from the drop-down list in the center field, then type a value in the right field. 114 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 115 The options you can use are listed below, along with possible values. The format for all values, with the exception of Device Type, is free form string. Criteria Possible Value Intel Pentium M processor 1600MHz abc.xyz.com Device Type Server or Workstation GUID 5bf63fb9b1ed4cd880e1a428a1fcf737 Hostname...
Page 116 8 Click Next to display the Group Membership page. 116 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 117: Editing Existing Registration Rules
Adding groups causes devices to receive any assignments provided by membership in the groups. Assignments from group membership are additive, so if a device is assigned to both group A and group B, the device receives all assignments from both groups. Click Add to add a group.
Page 118: Renaming Or Copying Registration Rules
3 Select a registration rule by selecting the box next to its name, click Edit, then click an option: Rename: Click Rename, type a new name for the registration rule, then click OK. 118 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 119: Reordering Registration Rules
Copy: Click Copy, type a new name for the registration rule, then click OK. The copy option is useful to create a new registration rule that is similar to an existing rule. You can copy a key and then edit the new rule's settings. If more than one check box is selected, the Rename and Copy options are not available from the Edit menu.
Page 120 605. Folder: Type the name or browse to the folder that contains this folder in the ZENworks Control Center interface. Description: Provide a short description of the folder's contents. 4 Click OK. 120 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 121: Unregistering And Reregistering Devices
Unregistering and Reregistering Devices Under certain circumstances, it might be necessary to unregister devices from or reregister devices ® against the ZENworks Server. The following sections contain additional information: Section 13.1, “Possible Scenarios for Unregistering and Reregistering Devices,” on page 121 Section 13.2, “Unregistering Devices,”...
Page 122: Unregistering Devices
For SUSE Linux Enterprise Server 10 (SLES 10) and SUSE Linux Enterprise Desktop 10 (SLED10) managed devices: /usr/bin/rug sa https://ZEN_Server_address For other managed devices: /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. 122 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 123: Part Iv Policy Management
Policy Management ® ® The following sections provide information about Novell ZENworks Linux Management Policy Management features and procedures: Chapter 14, “Policy Management Overview,” on page 125 Chapter 15, “Understanding Policies,” on page 127 Chapter 16, “Creating Policies,” on page 133 Chapter 17, “Managing Policies,”...
Page 124 124 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 125: Policy Management Overview
(servers and workstations). ZENworks Linux Management provides policies for a number of popular applications, including the Novell Linux Desktop. It also includes a policy to execute script, binary, or Java files and a policy to apply changes to text files.
Page 126: Managing Policies
Section 16.8, “Text File Policy,” on page 176. NOTE: The Epiphany, Evolution, Firefox, Generic GNOME, Novell Linux Desktop, and SUSE Linux Enterprise Desktop policies are referred as GConf-based policies. 14.3 Managing Policies In addition to creating policies, as described in Chapter 16, “Creating Policies,”...
Page 127: Understanding Policies
Understanding Policies ® ® Novell ZENworks Linux Management policies provide a mechanism of uniformly configuring applications. ZENworks policies let you configure system and application settings and then set them as Lockdown or Default. Lockdown lets you restrict users from changing settings, so the application must use the values that are configured in the policy.
Page 128: Assignments
Section 16.4, “Generic GNOME Policy,” on page 151. Novell Linux Desktop policy: Lets you configure the Novell Linux Desktop settings. This policy lets you remove certain items from the system menu, program menu, and personal settings. It also lets you configure background image settings, shade settings, proxy settings, and more.
Page 129: Groups
Event The User Login event triggers the Epiphany, Evolution, Firefox, enforcement of the policy. Generic GNOME, Novell Linux Desktop, and SUSE Linux Enterprise Desktop policies. Monthly Select the day of the month on Remote Execute and Text File...
Page 130: System Requirements
If not, all the settings configured in the policy are not effective. For example, if the Distribution >= Novell Linux Desktop 9 requirement is removed from the Firefox policy and the policy is specified to be enforced on all platforms, the settings are not effective because the lockdown option for Firefox is available only for the Novell Linux Desktop.
Page 131 For the Text File and Remote Execute policies, all policies whose system requirements are met are applied on the device. For all other policies, the first policy amongst the effective policies, whose system requirements are met, is applied on the device Understanding Policies 131...
Page 132 132 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 133: Creating Policies
Section 16.3, “Firefox Policy,” on page 145 Section 16.4, “Generic GNOME Policy,” on page 151 Section 16.5, “Novell Linux Desktop Policy,” on page 156 Section 16.6, “Remote Execute Policy,” on page 164 Section 16.7, “SUSE Linux Enterprise Desktop Policy,” on page 169 Section 16.8, “Text File Policy,”...
Page 134 Description: Provide a short description of the policy. This description displays on the policy's Summary page in the ZENworks Control Center interface. 5 Click Next to display the Epiphany Lockdown Settings page. 134 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 135 6 Select the desired options (by default, all options are disabled): Disable JavaScript control of window chrome: Select this option to disable the JavaScript control and modification of the Epiphany Web browser's window chrome. The chrome is part of an application window that is positioned outside of the window's content area.
Page 136 Allow Java: Select this option to allow or disallow Java applications to run on the Epiphany Web browser. Allow JavaScript: Select this option to allow or disallow JavaScript applications to run on the Epiphany Web browser. 136 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 137 Cookies: Select this option to configure how the Epiphany Web browser handles cookies. A cookie is a piece of information given to a Web browser by a Web server. The browser, in turn, stores this information in a file. The available options are Always accept, Only from the sites you visit, and Never accept.
Page 138 The settings you configure on this page determine when the policy is applied to devices. Section 15.3, “Schedules,” on page 128 for information about the available schedules and their options. 16 Click Next to display the Policy Groups page. 138 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 139: Evolution Policy
17 (Optional) Click Add to open the Select Groups dialog box, then click the underlined links in the Name column to select the desired policy groups and display their names in the Selected list box. Using policy groups eases administration efforts by letting you group several policies so you can use common assignments, schedules, and so forth, rather than configuring these settings for each policy you create.
Page 140 Description: Provide a short description of the policy. This description displays on the policy's Summary page in the ZENworks Control Center interface. 5 Click Next to display the Evolution Lockdown Settings page. 140 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 141 6 Select the desired options (by default, all options are disabled): The options on this page allow you to prevent users from changing the following Evolution e- mail client settings. Select an option to prevent users from changing that setting in the Evolution e-mail client.
Page 142 European (ISO-8859-1). Empty trash folders on exit: Lets you specify when to empty the Trash folder. The available options are Never, Every time, Once per day, Once per week, and Once per month. 142 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 143 Check inbox for junk mail: Lets you specify if the incoming mail must be checked for junk mail. Include remote junk mail tests: Lets you specify if the remote junk filtering option should be used for filtering incoming mail. For example, the Evolution client stores a message in the Junk Mail folder if it finds the mail address a blacklisted address.
Page 144 Assigning a policy to a Group object is the preferred method of assigning the policy. Assigning the policy to a large number of objects (for example, more than 250) might cause increased server utilization. 13c Click OK. 14 Click Next to display the Policy Schedule page. 144 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 145: Firefox Policy
15 Select the schedule to apply to the assignments from the drop-down list, then select the desired options, which vary, depending on the schedule type you select. The settings you configure on this page determine when the policy is applied to devices. Section 15.3, “Schedules,”...
Page 146 The Firefox policy is supported only if the lockdown version of Firefox is available on the Novell Linux Desktop, SLED 10, and SLED 11 devices. The Firefox policy is additionally supported on SLES 10 and SLES 11 devices if you apply ZENworks 7.3 Linux Management Hot Patch 1.
Page 147 6 Select the desired options (by default, all options are disabled): Disable Javascript control of window chrome: Select this option to disable the JavaScript control and modification of the Firefox Web browser's window chrome. The chrome is part of an application window that is positioned outside of the window's content area.
Page 148 . The options that are not enabled are excluded from the policy and are not applied to the device. Homepage URL: Specify the URL to automatically display when users launch the Firefox Web browser. 148 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 149 Allow popups: Select this option to allow or disallow pop-ups to be displayed in the Firefox Web browser. Allow Java: Select this option to allow or disallow Java applications to run on the Firefox Web browser. Allow JavaScript: Select this option to allow or disallow JavaScript applications to run on the Firefox Web browser.
Page 150 12 Click Next to display the Policy Schedule page. 13 Select the schedule to apply to the assignments from the drop-down list, then select the desired options, which vary, depending on the schedule type you select. 150 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 151: Generic Gnome Policy
The settings you configure on this page determine when the policy is applied to devices. Section 15.3, “Schedules,” on page 128 for information about the available schedules and their options. 14 Click Next to display the Policy Groups page. 15 (Optional) Click Add to open the Select Groups dialog box, then click the underlined links in the Name column to select the desired policy groups and display their names in the Selected list box.
Page 152 Folders display in the ZENworks Control Center. Description: Provide a short description of the policy. This description displays on the policy's Summary page in the ZENworks Control Center interface. 5 Click Next to display the Source page. 152 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 153 6 Select the desired option, then click Next. Import the settings from a device: Use this option to import the existing GConf settings from any device that is registered with the ZENworks Linux Management Server. The system obtains all settings, including default settings, from that device. You can enforce these settings on a desired managed device or group of devices at a later time.
Page 154 GConf settings. If you have not included this setting in the policy, and if the operating system of a managed device (where the 154 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 155 policy is to be applied) is different than the operating system of the device from which the settings have been imported, a warning message is generated. However, the policy settings are enforced. If you chose the Define a setting on your own option in Step 6 on page 153, and you want to include the default system requirement in the policy, you must specify the distribution and...
Page 156: Novell Linux Desktop Policy
Back button as necessary. Click Finish to create the policy as configured according to the settings on the Finish page. 16.5 Novell Linux Desktop Policy The Novell Linux Desktop policy is used to configure the GNOME Novell Linux Desktop settings on a device. 156 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 157 1 In the 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 Novell Linux Desktop Policy, then click Next to display the Policy Name page.
Page 158 Remove trash icon from desktop: Lets you remove the trash icon from users' desktops. Remove user's home icon from desktop: Lets you remove the Home icon from users' desktops. 7 Click Next to display the Novell Linux Desktop Menu Lockdown page. 158 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 159 (by default, all options are disabled): Remove from System menu: Lets you remove items from the System menu of the Novell Linux Desktop. Select an item you want to remove and move it to the box on the right side. The item is removed from the users' System menus.
Page 160 (by default, all options are disabled): Remove from personal settings: Lets you remove items from the Personal Settings of Novell Linux Desktop. Select an item you want to remove and move it to the box on the right side. The item is removed from the users' Personal Settings.
Page 161 12 Select the desired options (by default, all options are disabled). For each option you enable, provide a value. When you enable an option, it is locked by default. You can unlock the option by clicking . The options that are not enabled are excluded from the policy and are not applied to the device.
Page 162 Policy settings are applied only if a device has the same version or a newer version of the Novell Linux Desktop. If a device does not have Novell Linux Desktop 9 or newer, the policy does not apply correctly.
Page 163 Specify the schedule for this policy Specify groups for this policy 17 Assign the policy to the devices. 17a Click Add to browse for and select the appropriate Server or Workstation objects. You can also select Folder or Group objects. 17b Click the down-arrow next to Servers or Workstations to expand the list, then click the underlined link in the Name column to select the desired objects and display their names in the Selected list box.
Page 164: Remote Execute Policy
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. 164 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 165 4 Fill in the fields: Policy name: (Required) Provide a unique name for the policy. The name you provide displays in the ZENworks Control Center interface, which is the administrative tool for ZENworks Linux Management. For more information, see Appendix C, “Naming Conventions in the ZENworks Control Center,”...
Page 166 NOTE: The launched program is not terminated by the enforcer if you select the Do not wait or Wait for <n> sec options. (Conditional) If you chose Script in the Executable Type field in Step 6 on page 166, the following options are available: 166 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 167 Script to run: Select an option from the drop-down list: Specify a file: Fill in the fields: Script filename: Specify the complete absolute path, including the filename, of the script you want to run on a managed device. Script parameters: Specify any parameters to be passed to the specified script file. If you want to specify Shell operators such as redirection operators in Script parameter, then you must select Script in the Executable Type field and Define your own script in the Script to run field.
Page 168 Start Time, and then Repeat until End Time Every, and if the Start Time and End Time spans midnight, the Remote Execute policy is executed only at the Start Time and fails to repeat execution. 11 Click Next to display the Policy Groups page. 168 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 169: Suse Linux Enterprise Desktop Policy
12 (Optional) Click Add to open the Select Groups dialog box, then click the underlined links in the Name column to select the desired policy groups and display their names in the Selected list box. Using policy groups eases administration efforts by letting you group several policies so you can use common assignments, schedules, and so forth, rather than configuring these settings for each policy you create.
Page 170 Description: Provide a short description of the policy. This description displays on the policy's Summary page in the ZENworks Control Center interface. 5 Click Next to display the SUSE Linux Enterprise Desktop Main Menu Settings page. 170 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 171 6 Select the desired options (by default, all options are disabled). Selecting an item from the list disables or removes the associated feature on the user's desktop. The user cannot access menu items or controls associated with the feature. Remove Search from Main Menu: Lets you remove Search from the main menu of the user's SUSE Linux Enterprise Desktop.
Page 172 To remove an item from the list, select the application you want to delete, and click Remove. 9 Click Next to display the SUSE Linux Enterprise Desktop Proxy Settings page. 172 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 173 10 Select the desired options (by default, all options are disabled). For each option you enable, provide a value. When you enable an option, it is locked by default. You can unlock the option by clicking . The options that are not enabled are excluded from the policy and are not applied to the device.
Page 174 15b Click the down-arrow next to Servers or Workstations to expand the list, then click the underlined link in the Name column to select the desired objects and display their names in the Selected list box. 174 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 175 Assigning a policy to a Group object is the preferred method of assigning the policy. Assigning the policy to a large number of objects (for example, more than 250) might cause increased server utilization. 15c Click OK. 16 Click Next to display the Policy Schedule page. 17 Select the schedule to apply to the assignments from the drop-down list, then select the desired options, which vary, depending on the schedule type you select.
Page 176: Text File Policy
Folders display in the ZENworks Control Center. Description: Provide a short description of the policy. This description displays on the policy's Summary page in the ZENworks Control Center interface. 5 Click Next to display the General page. 176 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 177 6 Select the desired options: Filename: Specify the name and the complete path of a file you want to change. Maximum number of versions to retain: Specify the maximum number of backups to be maintained for a file that has been changed. If the maximum limit of backups is reached, the oldest backup of a file is deleted.
Page 178 (Conditional) If you chose Script in the Executable type field, the following options are available: Script to run: Select an option from the drop-down list (Specify a File or Define Your Own Script): Specify a file: Fill in the fields: 178 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 179 Script filename: Specify the complete path, including the filename, of the script you want to run on a managed device. Script parameters: Specify any parameters to be passed to the specified script file. Script engine: Specify the name and location of the script engine that runs the script. For example, /usr/bin/perl Script engine parameters: Specify any parameters to be passed to the specified...
Page 180 The settings you configure on this page determine when the policy is applied to devices. Section 15.3, “Schedules,” on page 128 for information about the available schedules. 13 Click Next to display the Policy Groups page. 180 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 181 14 (Optional) Click Add to open the Select Groups dialog box, then click the underlined links in the Name column to select the desired policy groups and display their names in the Selected list box. Using policy groups eases administration efforts by letting you group several policies so you can use common assignments, schedules, and so forth, rather than configuring these settings for each policy you create.
Page 182 182 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 183: Managing Policies
Generic GNOME policy: Configures GConf applications. For step-by-step instructions to create this policy, see Section 16.4, “Generic GNOME Policy,” on page 151. Novell Linux Desktop policy: Configures the Novell Linux Desktop settings. For step-by-step instructions to create this policy, see Section 16.5, “Novell Linux Desktop Policy,” on page 156.
Page 184: Creating Folders
Policy, and Policy Group objects. To create a folder: 1 In the ZENworks Control Center, click the Policies tab. 2 Click New, then click Folder to display the New Folder dialog box. 184 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 185: Creating Policy Groups
3 Fill in the fields: Name: Provide a unique name for your folder. This is a required field. For more information, see Appendix C, “Naming Conventions in the ZENworks Control Center,” on page 605. Folder: Type the name or browse to the folder that contains this folder in the ZENworks Control Center interface.
Page 186 Folder: (Required) Type the name or browse to the folder that contains this policy group. Description: Provide a short description of the policy group's contents. This description displays in the ZENworks Control Center. 4 Click Next to display the Summary page. 186 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 187 Review the information on the Summary page, making any changes to the policy-group settings by using the Back button as necessary. Depending on your needs, you can create the policy group now or you can specify members, assignments, and schedules for this policy group. 5 Click Finish to create the policy as configured according to the settings on the Summary page.
Page 188: Assigning Policies
Action, then click Assign Policy to display the Policy Assignments page. 2 Assign the policy to the desired devices. 2a Click Add to browse for and select the appropriate Server or Workstation objects. 188 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 189: Removing Policy Assignments
You can also select Folder or Group objects. 2b Click the down-arrow next to Servers or Workstations to expand the list, then click the underlined link in the Name column to select the desired objects and display their names in the Selected list box. Assigning a policy to a Group object is the preferred method of assigning the policy.
Page 190: Adding Policies To Existing Groups
17.7.1 Editing Epiphany, Evolution, Firefox, and NLD Policies You can edit, include, or remove lockdown settings, configuration settings, and system requirements of the application policies. Epiphany, Evolution, Firefox, Novell Linux Desktop, and SUSE Linux Enterprise Desktop policies are the application policies.
Page 191 2a Review the information in the General section, then make the desired configuration changes (you can edit only the Revision and Description options in this section). Policy type: Displays the policy type (Novell Linux Desktop Policy, Firefox Policy, and so forth).
Page 192 Summary page, must be incremented for the updated policy to be applied to associated devices. If the policy revision is not incremented, the changes made to the policy are not applied on the device. 192 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 193: Editing Generic Gnome Policies
17.7.2 Editing Generic GNOME Policies 1 In the ZENworks Control Center, click the Policies tab. 2 Click the policy's name to display the Summary page, then make the desired configuration changes. If you do not want to edit any item on the Summary page, skip to Step 3 on page 194.
Page 194 If you want to configure more application keys using the same policy, the Import From a Device option is more appropriate. You can configure the device, test it, and then import the settings to update the policy. 194 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 195: Editing Remote Execute Policies
You can import from the same device that was used to create the original policy or you can import from any other device. When you import settings, you have additional options, such as the following: Add the new imported settings that are not present in the policy: Adds only those GConf settings that are not part of existing policy settings.
Page 196 Advanced, select the check box next to the appropriate event, then click Acknowledge (a check mark displays on the right side of the Date column to indicate that the item has been acknowledged). 2d Review the information in the Upcoming Events section. 196 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 197: Editing Text File Policies
The Upcoming Events section lists events scheduled for the selected policy. You can click the calendar icon to display a calendar to view events for the desired date. You can also use the arrows to view events for the previous or next day, week, or month. 2e Review the information in the Groups section, then make the desired configuration changes.
Page 198 The Event Log section lists all unacknowledged errors and warnings. The Status column displays an icon indicating each item's status. Position the mouse pointer over each icon to display a short message describing the status of the item. 198 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 199 To acknowledge an error or warning, click its name in the Event column, then click Acknowledged in the Message Detail Information dialog box that displays. You can also click Advanced, select the check box next to the appropriate event, then click Acknowledge (a check mark displays on the right side of the Date column to indicate that the item has been acknowledged).
Page 200: Viewing Policy Enforcement Status
1 In the ZENworks Control Center, click the Policies tab. 2 Select a policy for which you want to edit the system requirements. 3 Click the Details tab. 4 In the Combine Filters Using field, select AND or OR. 200 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 201 This setting lets you specify the logical relationship between filter sets and filters. Select And to satisfy all the sets of filters and select Or to satisfy any one of the filter sets. By default, the filters are defined in one filter set. Within a filter set, select OR to satisfy any one of the filter conditions and select AND to satisfy all the filter conditions.
Page 202: Refreshing Policies
Event log of the policy that was applied. To verify the enforcement of the GConf-based policies, you need to re-login to the assigned device. You can then start the application and verify that the policy has been enforced correctly. 202 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 203: Renaming, Copying, Or Moving Policies
The updated settings are reflected only when the user logs in via the user interface session again. In the Novell Linux Desktop policy, some of the configuration settings are file-permission-based, and hence for a...
Page 204: Deleting Policies, Policy Groups, And Folders
Center. The policies contained in the folder are unenforced from the device to which they were assigned. For more information, see Section 17.13, “Unenforcing Policies,” on page 205. To delete a policy, policy group, or folder: 1 In the ZENworks Control Center, click the Policies tab. 204 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 205: Unenforcing Policies
2 In the Policies list, select the box next to the desired item's name, then click Delete. If the item you are deleting is a folder, you are prompted whether or not to delete the folder and its contents. When a policy folder is deleted, each of its policies and subfolders are also deleted. 17.13 Unenforcing Policies Policies are unenforced when either a policy is deleted or it is unassigned from a device.
Page 206 206 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 207: Part V Package And Content Management
Package and Content Management ® ® The following sections provide information about Novell ZENworks Linux Management Package and Content Management features and procedures: Chapter 18, “Package and Content Management Overview,” on page 209 Chapter 19, “Understanding RPM Packages,” on page 213 Chapter 20, “Using RPM and File Bundles,”...
Page 208 208 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 209: Package And Content Management Overview
ZENworks Linux Management server. For example, to distribute updates to the SLES 10 devices mirrored from updates.novell.com, you need to ensure that all the packages from the SLES 10 media are imported to the ZLM server. You need to assign the bundles or catalogs containing the dependent RPMs to the managed devices.
Page 210 -; OFS="/"; print $0}'| sort | uniq`; do cd $STARTDIR cd $dir echo "Loading RPM's from `pwd`" zlman -V -U administrator -P$3 bap $1 $2 *.rpm; done ENDTIME=`date` echo "Load started at $STARTTIME" echo "and ended at $ENDTIME" 210 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 211: Understanding Rpm And File Bundles
18.1 Understanding RPM and File Bundles 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.
Page 212: Understanding Dell Update Package Bundles
You also use mirroring to obtain Dell Update Packages from the Dell FTP site or from a CD obtained from Dell support. For more information, see Chapter 25, “Mirroring Software,” on page 293. 212 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 213: Understanding Rpm Packages
SLED 9. An RPM package file is identified with a extension. .rpm For example, the package format for the file novell-zenworks-install-7.2-2-0.0.0.i386 novell-zenworks-install-7.2-2-0.0.0.i386.rpm Review the following section to understand how to install the RPM packages: Section 19.1, “Installing the RPM Packages,” on page 213 Section 19.2, “Understanding the RPM Repositories,”...
Page 214: Yast Online Update (You) Repository
This repository is available at YaST Online Update (https://you.novell.com/update). This server requires authentication with your Novell account name and password. 19.2.3 RCE Repository The RCE repository contains metadata files that contain the packages and patches along with their information. The ZENworks Linux Management 6.6 server hosts this repository. This repository...
Page 215: Loading Base Packages
19.5 Patching the Client Systems If you are using the SLES 10 ZENworks Linux Management agents, you can receive updates by registering with the Novell Customer Center. You can then apply these updates to your system by using the command. However, this process is not recommended in a ZENworks...
Page 216 216 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 217: Using Rpm And File Bundles
Using RPM and File Bundles ® ® Using Novell ZENworks Linux Management, you can install software using either a bundle or a catalog. A bundle contains one or more files that are installed to particular locations on a device. A catalog is a collection of RPM bundles, Dell Update Package bundles, or bundle groups;...
Page 218: Rpm Bundles
Bundle Commands section of zlman (1) (page 562). 1 In the ZENworks Control Center, click the Bundles tab. 2 In the Bundle list, click New, then click Bundle to display the Select Bundle Type page. 218 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 219 3 Select RPM package bundle (the default option), then click Next to display the Name and Description page. For information about the other bundle types, see Part VI, “Preboot Services,” on page 323, Chapter 23, “Using Dell Update Package Bundles,” on page 283, and Section 20.3, “Creating File Bundles,”...
Page 220 Name column. You can remove a selected package from the list by using the Remove option. 6a (Optional) Click Add > Upload RPM to open the RPM File Upload dialog box, then fill in the fields: 220 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 221 ZENworks Control Center. Click OK to upload the packages to the ZENworks Linux Management server. The package repository is the directory on the ZENworks Server. /var/opt/novell/zenworks/pkg-repo Target platforms: Select one or more platforms from the Target Platforms list. You can press to select multiple platforms.
Page 222 6b (Optional) Click Add > Import from repository to open the Package Import dialog box, then select the packages to import. You can use the Search options on the right side of the Package Import dialog box to locate packages. 222 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 223 6c Select an install type from the drop-down list: Auto-detect: Automatically detects whether the bundle is already installed on assigned devices and either installs the bundle or updates an existing bundle, if necessary. Basically, the Auto-detect option determines whether the Update or the Install option functionality (explained below) is best, and then performs that operation.
Page 224 Do not wait: Specify that the ZENworks Management Daemon (ZMD) does not block while the script completes. Wait until the program completes the execution: Specify that ZMD blocks until the script completes. 224 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 225 9b, fill in the fields: Java program name: (Required) Type the class path to the class file you want to launch, for example, com.novell.TestProg Program parameters: Specify any additional parameters to pass to the Java class at execution time. Java Runtime Executable (JRE): (Required) Specify the path to the JRE* that launches the class, for example, .
Page 226 Assigning the bundle to a large number of objects (for example, more than 250) might cause increased server utilization. 12c Click OK. 13 Click Next to display the Bundle Options page. 226 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 227 RPM bundle from being deployed, you can look at the log file to troubleshoot the bundle-creation process. The log file is located in /var/opt/novell/ log/zenworks A successful dry run ensures that the bundle can be successfully deployed or installed on assigned devices (packages are available, dependencies are met, etc.).
Page 228 Wizard completes, providing that the assigned devices are online. The packages inside the bundle deploy to and install on devices that are not online when they refresh. 16 Click Next to display the Bundle Groups page. 228 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 229: Creating File Bundles
17 (Optional) Click Add to open the Select Groups dialog box, then click the underlined links in the Name column to select the desired bundle groups and display their names in the Selected list box. Using bundle groups eases administration efforts by letting you group several bundles so you can use common assignments, schedules, and so forth, rather than configuring these settings for each bundle you create.
Page 230 5 Click Next to display the Files page to add the files to include in this bundle. 6 Add the files to include in the bundle using the Upload and the Import from bundle options. 230 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 231 The files that you upload to a bundle must already exist on the local device on which you are running the ZENworks Control Center. You can use either the Upload option or the Import from bundle option, or you can use both options, depending on your needs. After you upload or import files into the list, you can remove a selected package from the list by using the Remove option.
Page 232 NOTE: You can configure multiple scripts for each bundle. Repeat the configuration process as many times as desired, choosing different options from the Scriptable Action and Executable Type drop-down lists, explained below. 232 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 233 8 Click New to display the New Scriptable Action dialog box. 9 Fill in the fields: 9a Scriptable Action: Select one of the following actions: Pre-distribution/post-distribution: Lets you perform tasks that must be done before or after a bundle is deployed to assigned devices. Deploying a bundle means that the packages or files inside the bundle are downloaded from the ZENworks server to the assigned devices.
Page 234 Back button as necessary. Depending on your needs, you can create the bundle now or you can configure additional options for this bundle. 234 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 235 11 Click Finish to create the bundle as configured per settings on the Summary page. If you click Finish, the bundle is created but it does not have devices assigned, a schedule, and so forth. At some point in the future, you need to configure additional options for the bundle by continuing with Section 20.4, “Assigning Bundles,”...
Page 236 Click the Schedule icon to choose the schedule type. The following schedules are available. Click the link in the left column in the table below for more information about each schedule type and its options. 236 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 237 Schedule Type Description Date Specific Select one or more dates on which to install the bundle on assigned devices and set other restrictions that might apply. Relative to Refresh Schedule when the bundle is installed, either immediately after the device refreshes or a specified amount of time after the device refreshes.
Page 238: Assigning Bundles
Assigning the bundle to a large number of objects (for example, more than 250) might cause increased server utilization. 2c Click OK. 3 Click Next to display the Bundle Options page. 238 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 239 The log file is located in . This option is not applicable for File bundles. var/opt/novell/log/zenworks A successful dry run ensures that the bundle can be successfully deployed or installed on assigned devices (packages are available, dependencies are met, etc.).
Page 240 7 Review the information on the Finish page, making any changes to the bundle settings by using the Back button as necessary. Click Finish to create the bundle as configured per settings on the Summary page. 8 Click OK. 240 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 241: Editing Bundles
20.5 Editing Bundles You can edit an existing bundle to change its description, add or remove assignments, add or remove the bundle from existing catalogs or bundle groups, add or remove packages from the bundle, deploy a different version of the bundle, and more. You can use the ZENworks Control Center or the zlman command line utility to edit bundles.
Page 242 2e Review the information in the Catalogs/Groups sections, then make the desired configuration changes. The Catalogs/Groups sections list the catalogs and groups that contain the selected bundle. You can also use the following options: 242 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 243 Advanced: Click Advanced to display the Edit Catalogs/Groups page to display a list of the catalogs and groups that contain the selected bundle. You can click Add to open the Select Groups dialog box to add the selected bundle to existing catalogs or groups. You can also remove a bundle or group by clicking the check box next to the Name column, then clicking Remove to remove the bundle from that catalog or group.
Page 244 Auto-detect: Automatically detects whether the bundle is already installed on assigned devices and either installs the bundle or updates an existing bundle, if necessary. Basically, the Auto-detect option determines whether the Update or the 244 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 245: Adding Bundles To Catalogs
Install option functionality (explained below) is best, and then performs that operation. Any kernel packages are installed using the Install option functionality; other packages are installed using the Update option functionality. This is the default option and should be used in most situations. Update: Updates the packages on assigned devices if the packages in the bundle are newer than what is installed on the devices.
Page 246 605. Folder: Type the name or browse to the folder that contains this folder in the ZENworks Control Center interface. Description: Provide a short description of the folder's contents. 4 Click OK. 246 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 247: Creating Bundle Groups
20.8 Creating Bundle Groups A bundle group lets you group bundles to ease administration and to provide easier assigning and scheduling of the bundles in the bundle group. You can use the ZENworks Control Center or the zlman command line utility to create bundle groups.
Page 248 6b Click the underlined link in the Name column to select the desired bundles and display their names in the Selected list box. 6c Click OK. 7 Click Next to display the Add Assignments page. 248 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 249 8 Assign the bundle group to the devices that you want to distribute the bundle group to. 8a Click Add to browse for and select the appropriate device objects. You can also select Folder or Group objects. 8b Click the down-arrow next to Servers or Workstations to expand the list, then click the underlined link in the Name column to select the desired objects and display their names in the Selected list box.
Page 250 You can also specify whether the bundle's installation is repeated and specify a time period when you do not want the bundle installed to help minimize network traffic during that time. 250 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 251: Adding Bundles To Existing Groups
The Deploy and install at separate scheduled times option is not set by default. In most situations, there is no need to deploy and install packages inside bundles at different times. You can, depending on your needs, schedule deployment and installation at different times to conserve network bandwidth or to perform the actions at more convenient times for users.
Page 252: Uninstalling Bundles From Devices
2 In the Bundles list, click the underlined link for the desired bundle to display its Summary page. 3 In the Assignments section, select the box next to the device's name from which you want to remove the bundle, then click Remove to launch the Uninstall Bundle Wizard. 252 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 253 4 Specify a removal option: No: Although the device is removed from the Assignments section and the bundle is no longer assigned to the device, the software remains installed on the previously assigned device. Yes: The software is uninstalled from previously assigned devices according to the schedule you specify in the next step of this wizard.
Page 254: Using The Devices Page To Remove Bundles From Devices
The settings you configure on this page determine when the assignments are removed from previously assigned devices. The following schedules are available. Click the link in the left column for more information about each schedule type. 254 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 255: Deleting Bundles, Bundle Groups, And Folders
Schedule Type Description Date Specific Select one or more dates on which to remove assignments and set other restrictions that might apply. Relative to Refresh Schedule when the assignments are removed, either immediately after the device refreshes or a specified amount of time after the device refreshes.
Page 256: Renaming, Copying, Or Moving Bundles
2 In the Bundles list, select the box next to the bundle's name, click Edit, then click an option. Rename: Click Rename, type a new name for the bundle, then click OK. 256 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 257: Deploying A Different Version Of A Bundle
IMPORTANT: Do not rename patch bundles. Copy: Click Copy, type a new name for the copy, then click OK. The copy option is useful to create a new bundle that is similar to an existing bundle. You can copy a bundle and then edit the new bundle's settings. If you create a copy of the YOU patch bundle, the copied version is converted to the RPM package bundle type.
Page 258: Using A Remote Execute Policy To Remove Bundles And Packages From Devices
Folders display in the ZENworks Control Center. Description: Provide a short description of the policy. This description displays on the policy's Summary page in the ZENworks Control Center interface. 5 Click Next. 258 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 259 6 Select Script from the Executable type drop-down list. 7 Specify the waiting time after starting the script. 8 Select Specify your own script from the Script to run drop-down list. 9 Type your script in the script box. The following table provides example scripts that you can use, depend on your needs: Sample Script Description Removes bundle1 from all devices that you assign the...
Page 260 The settings you configure on this page determine when the policy is assigned to devices. The following schedules are available. Click the link in the left column for more information about each schedule type and its options. 260 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 261: Generating Bundle Reports
Schedule Type Description Date Specific Select one or more dates on which to assign the policy to devices and set other restrictions that might apply. Day of the Week Specific Select one or more days of the week on which to assign the policy to devices and set other restrictions that might apply.
Page 262: Best Practices For Adding Packages To Bundles
To quickly deploy large package sets, adjust the level of security provided by the connection between the managed device and the ZENworks Server. To change the security level: 1. On the ZENworks Server, open the /etc/opt/novell/zenworks/tomcat/base/ file. server.xml 262 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 263 2. In the Connector section for port 443, change the value of ciphers to 128 bits as shown below: ciphers="SSL_RSA_WITH_RC4_128_SHA" This reduces the workload of the managed device and increases the speed of the streaming of the packages to it. IMPORTANT: Setting this attribute instructs the server to offer RC4 encryption at 128b as the only available cipher suite.
Page 264 264 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 265: Understanding The Package And Content Management Features Available On A Managed Device
Understanding the Package and Content Management Features Available on a Managed Device The following sections provide detailed information about the Package and Content Management features available on a managed device: Section 21.1, “Locking and Unlocking a Package on a Managed Device,” on page 265 Section 21.2, “Locking and Unlocking a Bundle on a Managed Device,”...
Page 266: Locking And Unlocking A Bundle On A Managed Device
You can also lock bundles in ZENworks Control Center while performing the following actions: Creating RPM Bundles Creating File Bundles Assigning Bundles Creating Bundle Groups Creating Catalogs Assigning Catalogs Assigning Dell Update Package Bundles 266 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 267: Locking A Bundle By Using The Command Line Utility
21.2.2 Locking a Bundle by Using the Command Line Utility 1 List all the bundles installed on the managed device by entering the command. From rug bl the list, select the bundle you want to lock. 2 Lock the bundle by entering the command.
Page 268: Installing The Best Package
The Software Installer window is displayed. 2 Click Configure, then click the Preferences tab. 3 Ensure that the Show Version Details option is deselected. The option is deselected by default. 4 Click Close. 268 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 269 The Software Installer window displays the packages available for installation. 5 Select the package to be installed, then click Install. zmd installs the package version best suited for the managed device. If you want to install a specific version of the package, and do not want zmd to choose the best package: 1 On the managed device, enter the command.
Page 270 270 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 271: Using Catalogs
Using Catalogs ® ® Using Novell ZENworks Linux Management, you can install packages using either a catalog or a bundle. A catalog is a collection of RPM bundles or Dell Update Package bundles; bundles included in a catalog are usually considered optional. Packages included in a bundle that is directly assigned is considered mandatory;...
Page 272 ZENworks Control Center interface and in the user interface. In the next step in this wizard, Catalog Attributes, you can specify to hide this catalog in the user interface. 4 Click Next to display the Catalog Attributes page. 272 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 273 5 (Optional) Select the Hide this catalog in the client user interface option to hide the catalog from users; the catalog displays in the ZENworks Control Center interface, which is the administrative tool for ZENworks Linux Management, but is hidden from users. This option is useful if you have a bundle or catalog containing a primary package that has dependent packages that must already be installed on devices.
Page 274 Assigning the catalog to a large number of objects (for example, more than 250) might cause increased server utilization. 10c Click OK. 11 Click Next to display the Bundles Options page. 274 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 275 12 Specify the desired Scheduling options: Deploy and update at a scheduled time: Use this option to schedule the deployment and installation of the bundles contained in this bundle group. Click the Schedule icon to choose the schedule type. The following schedules are available. Click the link in the left column in the table below for more information about each schedule type and its options.
Page 276: Assigning Catalogs
1 In the ZENworks Control Center, click the Bundles tab, select the desired catalog in the Bundles list by clicking the box next to its name, click Action, then click Assign Catalog to display the Devices To Be Assigned page. 276 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 277 2 Assign the catalog to the devices that you want to distribute the catalog to. 2a Click Add to browse for and select the appropriate device objects. You can also select Folder or Group objects. 2b Click the down-arrow next to Servers or Workstations to expand the list, then click the underlined link in the Name column to select the desired objects and display their names in the Selected list box.
Page 278 5 Click Next to display the Finish page, review the information on the Finish page, make any changes to the settings by using the Back button as necessary, then click Finish to assign the catalog as configured per settings on the Finish page. 6 Click OK. 278 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 279: Adding Bundles To Catalogs
22.4 Adding Bundles to Catalogs You can use the ZENworks Control Center or the zlman command line utility to add bundles to catalogs. The following procedure explains how to perform this task using the ZENworks Control Center. If you prefer the zlman command line utility, see the Catalog Commands section of zlman (1) (page 562).
Page 280: Deleting Catalogs
Catalog Commands section of zlman (1) (page 562). To delete a catalog from the ZENworks Control Center: 1 In the ZENworks Control Center, click the Bundles tab. 280 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 281: Creating Folders
2 In the Bundles list, check the box next to the catalog's name, then click Delete to remove the catalog from the ZENworks Control Center. 3 Click OK on the warning window that displays. 22.7 Creating Folders A folder is an organization object that displays in the ZENworks Control Center interface, which is the administrative tool for ZENworks Linux Management.
Page 282 605. Folder: Type the name or browse to the folder that contains this folder in the ZENworks Control Center interface. Description: Provide a short description of the folder's contents. 4 Click OK. 282 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 283: Using Dell Update Package Bundles
IMPORTANT: Before you can use Dell Update Packages on your Dell servers, you must complete the steps in “Enabling Dell PowerEdge Support” in the Novell ZENworks 7.3 Linux Management Installation Guide. The following sections contain additional information: Section 23.1, “Obtaining Dell Update Packages,” on page 283 Section 23.2, “Assigning Dell Update Package Bundles,”...
Page 284 Assigning the bundle to a large number of objects (for example, more than 250) might cause increased server utilization. 3c Click OK. 4 Click Next to display the Bundle Options page. 284 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 285 RPM bundle or file bundle from being deployed, you can look at the log file to troubleshoot the bundle-creation process. The log file is located in var/opt/novell/log/zenworks A successful dry run ensures that the bundle can be successfully deployed or installed on assigned devices (packages are available, dependencies are met, etc.).
Page 286 8 Review the information on the Finish page, making any changes to the settings by using the Back button as necessary. Click Finish to assign the bundle as configured per settings on the Summary page. 9 Click OK. 286 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 287: Determining If Newer Dell Package Updates Are Available For Poweredge Servers
23.3 Determining If Newer Dell Package Updates Are Available for PowerEdge Servers 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.
Page 288: Modifying The Contents Of A Dell Update Package Bundle
You can also click the down-arrow on the show x items option to display more items in the list. 2 Click the underlined link in the Name column to display the bundle’s Summary page. 3 Click the Details tab. 288 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 289 4 Use the Version drop-down list to select the desired version number, then click Copy. 5 Provide a new name for the copy of the bundle, then click OK. To modify the contents of the copy of an existing Dell Update Package bundle: 1 In the ZENworks Control Center, click the Bundles tab.
Page 290 290 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 291: Replicating Content In The Zenworks Management Zone
Replicating Content in the ZENworks Management Zone ® ® Novell ZENworks Linux Management uses a hierarchical organization to simplify device management. At the top level, a ZENworks Management Zone provides an autonomous unit of ZENworks servers and managed devices (workstations and servers). The ZENworks servers manage the devices.
Page 292: Configuring A Content Replication Schedule
Secondary Servers and set other restrictions that might apply. Monthly Select the day of the month on which to replicate content to. Secondary Servers and set other restrictions that might apply 4 Click Apply. 292 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 293: Mirroring Software
Management server, the 6.6.x server must also be a YaST Online Update (YOU) server. ® Novell, Dell, SUSE , and Red Hat each maintain servers of their respective types, enabling you to simply mirror the catalogs and bundles you are interested in without needing to maintain or update these repositories.
Page 294: Zlmmirror
2. Mirroring patch bundles. Section 25.3.3, “Mirroring Patch Bundles for SLES 10 / SLED 10 / SLES 11 / SLED 11 / OES 2 from the NU and RCE Type Repositories,” on page 306 294 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 295: Creating The Configuration Files By Using The Command Line Utility
-c filename.xml If no configuration file is specified, the default configuration file location is /etc/opt/novell/ zenworks/zlmmirror.xml You can check the configuration file for errors and display the parsed configuration information by using the conf-validate (cv) filename command.
Page 296 SLES 9 and OES, /etc/opt/novell/zenworks/zmd/deviceid for SLES 10 and SLED 10 /etc/zmd/deviceid For the Novell Updates (NU) server, the device must be registered with NCC to use the deviceid as User. 296 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 297 SLES 9 and OES, /etc/zmd/secret for SLES 10 and SLED10 For the Novell Updates (NU) server, the device must be registered with NCC to use the device secret as Password. Proxy The Proxy configuration element is optional and is used with an Internet Proxy.
Page 298 <CatalogConf> <Name>Red Carpet 2</Name> <LocalName>Red Carpet 2</LocalName> <Target>sles-9-i586</Target> <Package>lib.*</Package> </CatalogConf> Configuration Element Description Name Name of the catalog you want to mirror from this remote server. This is the only required parameter. 298 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 299 Configuration Element Description Local Name Name of the catalog you want the mirrored software placed in. If no Local Name is specified, the catalog name from the remote server is used. The local name for the catalog should not be same as that reserved for the <catalogname>-patches folder Folder Specifies the eDirectory...
Page 300: Creating A Configuration File By Using The Xzlmmirror Utility
Do the following tasks in the order listed to create a configuration file: “Configuring the Servers” on page 301 “Configuring the Catalogs” on page 302 You can also edit the configuration file. For more information, see “Editing the Configuration File” on page 305. 300 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 301 ZENworks 6.x Linux Management YAST: YaST Online Updates RHN: Red Hat Network YUM: YUM NU: Novell Updates The default URL of the server you want to mirror is displayed automatically in the following format, depending on the server type you have selected: ZLM:...
Page 302 Settings window. Review the following sections: “Adding Catalogs” on page 302 “Editing Catalog Settings” on page 305 Adding Catalogs The Add Catalogs page lets you configure each catalog you want to mirror. 302 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 303 1 In the Catalog drop-down list, select the catalog that you want to configure. 2 In the Local Name field, specify a name for the selected catalog. The local name for the catalog should not be same as that reserved for the <catalogname>- patches folder.
Page 304 13 (Optional) To configure a different server, or to reset the server settings that you have already configured, click Back. 14 Continue with initiating the mirroring process. For more information, see Section 25.3.5, “Testing and Performing the Mirroring Operation by Using the xzlmmirror Utility,” on page 307. 304 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 305 Editing Catalog Settings 1 Click Catalog Summary. The page displays the catalog names, the local names, and the category of the catalogs that you configured in the Add Catalogs page. 2 To view or edit the settings for a specific catalog, click the catalog. The Catalog Details dialog box is displayed.
Page 306: Mirroring Patch Bundles For Sles 10 / Sled 10 / Sles 11 / Sled 11 / Oes 2 From The Nu And Rce Type Repositories
11 / SLED 11 / OES 2 from the NU and RCE Type Repositories You can mirror patch bundles for SLES 10, SLED 10, SLES 11, SLED 11 and OES 2 from the NU and RCE type repositories such as nu.novell.com and update.novell.com. Review the following sections for more information: “Mirroring the Monolithic and Patch Bundles for SLES 10 / SLED 10 / SLES 11 / SLED 11 /...
Page 307: Testing And Performing The Mirroring Operation By Using Zlmmirror
<ExcludeBundle></ExcludeBundle> <Package>Mozilla*</Package> <ExcludePackage></ExcludePackage> </Catalog> NOTE: The local name for the catalog should not be same as the name reserved for the folder . In other words, the tag of the mirror configuration file <catalogname>-patches <localName> should not use the same name as the <catalogname>-patches 25.3.4 Testing and Performing the Mirroring Operation by Using zlmmirror...
Page 308: Distributing Catalogs From A Public Zenworks Linux Management Server
Command Line Utility,” on page 295. 2 Install the ZENworks Linux Management agent on a workstation and register against the public ZENworks Linux Management Server using no registration key (to use the default registration rule). 308 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 309: Mirroring Dell Update Packages To Your Zenworks Server
For more information, see “Installing the ZENworks Agent and Registering the Device” in the Novell ZENworks 7.3 Linux Management Installation Guide. 3 Copy the contents of the file from that workstation ( deviceid secret /etc/opt/ on SLES 9 and OES,...
Page 310 --help 6 In the section, edit the following configuration elements: <Catalog> Configuration Element Setting <Name></Name> Name of the catalog you want to mirror from this remote server: <Name>catalog_name</Name> 310 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 311 Configuration Element Setting Name of the folder where the Dell Update Packages are created and <Folder></Folder> updated: <Folder>/folder_name</Folder> Specifies the eDirectory folder (for example, /Dell ) where bundles and catalogs are created and updated. If not specified, the catalogs and bundles are created and updated in the /zlmmirror folder.
Page 312: Mirroring Bundles Between Zenworks Linux Management Servers Located In Different Management Zones
The servers use the HTTPS protocol at TCP port 443 to communicate with each other. You can mirror RPM package bundles, patch bundles, file bundles, and DUP bundles from the remote ZENworks server to the local ZENworks server. When you mirror bundles 312 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 313 from the remote server, only the version of the bundle that is currently deployed is mirrored to the local server. A new version of the bundle is created on the local server irrespective of the deployed version of the bundle on the remote server. 1 Before registering to the remote server, delete the existing ZENworks service on the local server by entering the following command: Local-ZLM-Server# rug sd <URL_of_the_existing_ZLM_server>...
Page 314: Mirroring Red Hat Updates From The Nu Repository By Using A Yum Subscription
1 Run the following command to verify if there are any RES or Red Hat catalogs on the remote NU server: zlmmirror slc -c NU_mirror_configuration_file This lists the catalogs on the remote NU server. 314 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 315 Configuration Element Setting Specify the path to the server you want to mirror, the catalog name, <Base></Base> and the architecture. <Base>https://nu.novell.com/repo/$RCE/ catalog_name/architecture</Base> For example: The base URL for a 32-bit target of a RES5 catalog is <Base>https://nu.novell.com/repo/$RCE/RES5/i386</ Base>...
Page 316: Mirroring Dell Updates From The Openmanage Server Administrator Repository By Using A Yum Subscription
1 Run the following command to verify if the required catalogs for a given target platform are available on the remote Dell Repository: zlmmirror slc -c yum_mirror_configuration_filename -v 2 In the YUM mirror configuration file’s section, edit the following <RemoteServer> configuration elements: 316 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 317 Configuration Element Setting Specify the path to the server you want to mirror, the device model, <Base></Base> and the operating system information. <Base>http://linux.dell.com/repo/hardware/latest/ device_model/osinfo</Base> For example: If the device model is DELL PowerEdge R710 server, and the operating system is 64-bit SLES 10, the base URL is <Base>http://linux.dell.com/repo/hardware/latest/ per710/suse10_64/</Base>...
Page 318: Deploying Red Hat Network Updates
For SUSE Linux Enterprise Server 10 (SLES 10) and SUSE Linux Enterprise Desktop (SLED 10) devices: /usr/bin/rug up For other managed devices: /opt/novell/zenworks/bin/rug up For more information, see rug (1) (page 586). 318 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 319: Delivering Specific Rpm Packages (Pushing)
For SUSE Linux Enterprise Server 10 (SLES 10) and SUSE Linux Enterprise Desktop (SLED 10) devices: /usr/bin/rug refresh For other managed devices: /opt/novell/zenworks/bin/rug refresh For more information, see rug (1) (page 586). 25.10 Encoding the ZENworks Server Password When you configure the XML configuration file prior to performing a mirroring operation, you specify your ZENworks Server’s password in the...
Page 320 320 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 321: Creating Rpm Packages From Tarballs
Creating RPM Packages From Tarballs ® ® Novell ZENworks Linux Management uses Red Hat Package Manager (RPM). RPM is a powerful package management system capable of installing, uninstalling, verifying, querying, and updating computer software packages on different devices. ZENworks Linux Management- Dell Edition supports the RPM format.
Page 322: Example Usage
3 Verify that the package is valid and list its contents by entering the following commands: $ rpm -qlp helloworld-1-2.noarch.rpm /usr /usr/share /usr/share/myapp /usr/share/myapp/README The alien utility has other options, such as to set the version and description of the package. See “man alien” for more information. 322 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 323: Part Vi Preboot Services
Preboot Services ® ® The following sections provide information on Novell ZENworks Linux Management Preboot Services features and procedures: Chapter 27, “Preboot Services Overview,” on page 325 Chapter 28, “Understanding Preboot Services in ZENworks Linux Management,” on page 329 Chapter 29, “Setting Up Preboot Services,” on page 353 Chapter 30, “Using Preboot Services,”...
Page 324 324 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 325: Preboot Services Overview
Preboot Services Overview ® ® Novell ZENworks Linux Management Preboot Services contains functionality that allows you to perform tasks on devices before their operating systems boot. Currently for ZENworks Linux Management, “devices” are servers and workstations. The following sections provide an overview of Preboot Services: Section 27.1, “Preboot Services Functionality,”...
Page 326: Preboot Bundles
5) Start DELL DTK; 6) Start DELL DTK (Maintenance Mode); and, 7) Exit, which resumes booting. You can configure whether the Preboot Services Menu is displayed upon booting, not displayed, or allowed to be displayed only when Ctrl+Alt is pressed during booting. 326 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 327: Setting Up Devices To Use Preboot Bundles
Image storage security: You can restrict where to save image files on the imaging server. Non-registered device settings: You can use Preboot Services to automatically name your non-registered devices using such criteria as prefixes, BIOS information (like asset tags or serial numbers), DNS suffixes, and you can set up DHCP or IP addresses.
Page 328 Assigns the selected bundles to the devices that you select in the wizard. For more information on assigning bundles and how to set up devices to apply the assigned bundles, Section 29.2, “Setting Up the Preboot Services Methods,” on page 354. 328 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 329: Understanding Preboot Services In Zenworks Linux Management
Understanding Preboot Services in ZENworks Linux Management ® ® This section provides an understanding of Novell ZENworks Linux Management Preboot Services and how you can use it in your Linux network: Section 28.1, “How Do You Implement Preboot Services?,” on page 329 Section 28.2, “What Is the Preboot Execution Environment (PXE)?,”...
Page 330: Understanding The Zenworks Nbps
For more information on and its configuration files, see the syslinux home page (http:/ pxelinux.0 /syslinux.zytor.com/pxe.php). For a copy of the Novell modifications to the syslinux open-source project, see Novell Forge (http:// forge.novell.com). 330 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 331: Preparing To Use Pxe
Before you can use Preboot Services with PXE, you need to do the following: 1. Install ZENworks 7.3 Linux Management on your imaging server. For more information, see Novell ZENworks 7.3 Linux Management Installation Guide. 2. Enable PXE on your ZENworks Linux Management devices. For more information, see Section 29.6, “Enabling PXE on Devices,”...
Page 332 It is ideal for labs, classrooms, and staging areas. For more information, see Section 28.5.6, “Multicasting Device Images,” on page 348. 332 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 333: Preboot Services Menu
Using the same image on multiple devices means they all have the same network identities. However, you can install the ZENworks Linux Management Imaging Agent (novell-zislnx) on these devices prior to performing the multicast, because this agent saves each device’s network identity settings and restores them after the multicast image is applied.
Page 334: Image Storage Security
ZENworks Linux Management Imaging Agent (novell-zislnx). The settings that can be adjusted for a ZENworks Management Zone are: NDS suffix: Provides a suffix for all of your devices’ names. For example, provo.novell.com. 334 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 335: Preboot Work Assignment Rules
Name servers: Controls which DNS servers a device uses. You can specify multiple DNS name servers. Device name: Configured device names can include a prefix, the BIOS asset tag, the BIOS serial number, or none of these. IP configuration: For the IP configuration, you can specify to use DHCP or a specific IP address.
Page 336: Preboot Referral Lists
When a PXE device boots, it makes a broadcast request on the network for PXE services. The ZENworks Proxy DHCP server (novell-proxydhcp) responds to this request with information that includes the IP address of an imaging server where the device can send requests for assigned preboot work.
Page 337: Intel Active Management Technology (Amt)
Preboot bundles using the device’s ZENworks identity without having to re-register the device. If you are using Intel AMT, support for it should be enabled in the novell- file. zmgprebootpolicy.conf Understanding Preboot Services in ZENworks Linux Management 337...
Page 338 For the procedures in providing Intel AMT enterprise names to ZENworks Linux Management, see Section 29.4.6, “Configuring Intel Active Management Technology (AMT),” on page 395. Accessing AMT Resources For more information, see “Downloading and Installing the iAMT Redirection Drivers” on page 395. 338 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 339: The Preboot Services Processes
Services imaging server. 4. The DHCP server responds with an IP address for the device to use. 5. The novell-proxydhcp daemon responds with the IP addresses of the TFTP server, as well as the filename of the Preboot Services bootstrap program ( nvlnbp.sys...
Page 340 Phase 1: Beginning the Process Depending on whether novell-proxydhcp is configured on the same server as the standard DHCP server or on a different server, the imaging process begins differently. The following sections illustrate how the process begins for each configuration, then the phases illustrated in “Phases 2...
Page 341 2. The DHCP server responds with IP configuration information on port 68, including tag 60 for PXEClient, which indicates that novell-proxydhcp is running on the same server. Standard DHCP and Novell Proxy DHCP Configured on the Same Server: Part B DHCP Configuration on the Same Server, Part B Figure 28-3...
Page 342 Figure 28-5 Data Model novell-pbserv Imaging Server PXE Device novell-zmgprebootpolicy PXE Menu? nvlnbp.sys Hot-key: PXE BIOS novell-tftp pxemenu.text novell-proxydhcp Processes: 1. Hardware detection is performed by and it reads the image-safe data. nvlnbp.sys 342 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 343 Processes: 1. Assuming no Preboot Services Menu is displayed, the device asks the Data Model (via novell- zmgprebootpolicy) if any work is assigned. 2. Assuming work is assigned, the novell-zmgprebootpolicy daemon responds with the name of the configuration file to use in performing the preboot work ( in this example).
Page 344 TFTP server. Pxelinux.0 /boot/root requests and receives from the TFTP server, but is Pxelinux.0 /boot/updateDrivers.tgz denied because the file does not exist (it is used to provide post-release software updates). 344 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 345: Preboot Strategies
Phase 8 Phase 8 of the Preboot Services Process Figure 28-10 Data Model Image image.zmg Imaging novell-pbserv Server novell-zmgprebootpolicy Imaging Engine novell-tftp SUSE Linux Enterprise Server 9 SP1 PXE Device novell-proxydhcp Processes: 1. SUSE Linux Enterprise Server (SLES) 9 SP1 is loaded and run on the device.
Page 346: Creating, Installing, And Restoring Standard Images
“Manually Taking an Image of a Device” on page 415. These images should include the Novell ZENworks Linux Management Imaging Agent (novell-zslnx). 3. Optionally, you can create a preboot imaging bundle for this image. This allows the image to be assigned automatically for later use.
Page 347: Reimaging Corrupted Devices
28.5.3 Reimaging Corrupted Devices Without data loss or undue disruption to users, you can fix devices that have become misconfigured or corrupted. 1. When a device needs to be fixed, have the user back up any files to the network that he or she wants to keep (if possible).
Page 348: Setting Up Devices For Future Reimaging
This process might need to be phased in by local administrators. Each administrator can do the following: 1. Install the Novell ZENworks Linux Management Imaging Agent (novell-zislnx) on each device. 2. If the devices are PXE capable, make sure PXE is enabled (see Section 29.6, “Enabling PXE on...
Page 349 When using a Preboot bundle to perform multicasting, the imaging server is the session master, which sends the image file to the session participants. The novell-pbserv daemon is used in .zmg this process. All problems are reported and displayed on the session master device.
Page 350: Configuring Dell Linux Devices
For a handful of devices, this might not be a problem. But for a larger number of devices, you should install the Novell ZENworks Linux Management Imaging Agent (novell-zislnx) on each device before doing the multicast (see Section 29.7.2, “Enabling a Device for Imaging Operations,” on page 403).
Page 351 Create a Dell Configuration Preboot bundle (see Section 30.5.2, “Creating Dell Configuration Bundles,” on page 457). Troubleshoot Dell Configuration Preboot bundles (see “Dell DTK” in the Novell ZENworks 7.3 Linux Management Troubleshooting Guide). Understanding Preboot Services in ZENworks Linux Management 351...
Page 352 352 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 353: Setting Up Preboot Services
ZENworks Linux Management. 29.1 Preparing a Preboot Services Server When you install Novell ZENworks Linux Management on a server, the server is nearly ready to act as a Preboot Services server. To avoid confusion, the Proxy DHCP daemon (novell-proxydhcp) is installed, but not enabled.
Page 354: Setting Up The Preboot Services Methods
29.2 Setting Up the Preboot Services Methods The Novell ZENworks Imaging Engine that performs the actual imaging of a device is a Linux application. Unless you use automated Preboot Services with PXE-enabled devices, you need to prepare a boot medium that has the Linux kernel, ZENworks Imaging Engine, and network drivers installed.
Page 355 /opt/novell/zenworks/zdm/winutils the imaging server where ZENworks Linux Management is installed. 2 In an ISO editor, open the temporary copy of the file. bootcd.iso If you experience ISO corruption after adding files into the ISO, such as a checksum error, use a more reliable ISO editor.
Page 356: Using The Zenworks Imaging Media Creator
/opt/novell/zenworks/zdm/winutils/settings.txt: The imaging server copy of this file needs to be modified for your network environment and a working copy of it should be maintained at the root of the imaging boot device (imaging CD or DVD, or a blank floppy diskette). When burning the imaging CD or DVD, be sure to include the edited copy of this file.
Page 357 Open. settings.txt The default location is . Browse to the /opt/novell/zenworks/zdm/winutils/ directory for the copy to be modified. When the file is loaded, the fields in this dialog box are populated from the information contained in the file.
Page 358 Domain Suffix: You can also specify as many DNS domain suffixes as you want. The editing, moving, and removal functions are also available for the suffixes. 358 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 359 5 (Required) In the Imaging Proxy Server Address section on the CD Media Boot page, specify either the fixed IP address or the full DNS name of Preboot server (where novell-pbserv is running). This specifies which Preboot server to connect to when you boot a device with the bootable diskette.
Page 360 3 (Required) In the Imaging Proxy Server Address section on the CD Media Boot tab, specify either the fixed IP address or the full DNS name of Preboot server (where novell-pbserv is running). This specifies which Preboot server to connect to when you boot a device with the bootable diskette.
Page 361 To create a PBI configuration file and then the PBI file: 1 On a Windows device, browse to the directory on opt/novell/zenworks/zdm/winutils your Linux imaging server and run zmediacreator.exe You might need to configure Samba on the Linux server in order for the Windows device to have access to this directory.
Page 362: Managing Zenworks Partitions
Section 29.2.3, “Using the ZENworks Imaging Media Creator,” on page 356.) Then, do the following: 1 Boot the device with the imaging CD or DVD, then select Install/Update ZEN partition from the menu. 362 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 363 This starts the process of creating the ZENworks partition in the first partition slot. It destroys all existing partitions, except an existing ZENworks partition or the Dell or Compaq configuration partitions. By default, the ZENworks partition size is 150 MB. If the ZENworks partition already exists, it is upgraded, and your existing partitions are left intact.
Page 364: Deploying And Managing Preboot Services
The following sections explain how to set up, deploy, and manage Preboot Services: Section 29.3.1, “Checking the Preboot Services Imaging Server Setup,” on page 365 Section 29.3.2, “Deploying Preboot Services In a Network Environment,” on page 366 364 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 365: Checking The Preboot Services Imaging Server Setup
The PXE devices use the novell-zmgprebootpolicy daemon to check if there are any Preboot bundles that are assigned to the device. The novell-proxydhcp daemon must be started manually and does not need to be run on all imaging servers. The other three daemons are started automatically when installing ZENworks Linux Management, or any time the server is rebooted, and must run on all imaging servers.
Page 366: Deploying Preboot Services In A Network Environment
DHCP server. Preboot Services daemons: The four Preboot Services daemons (novell-pbserv, novell-tftp, novell-proxydhcp, and novell-zmgprebootpolicy) are all installed on the imaging server when you install ZENworks Linux Management. These daemons must run together on the same server.
Page 367 The Preboot Services Proxy DHCP server runs alongside a standard DHCP server to inform PXE devices of the IP address of the TFTP server, the IP address of the server where novell- zmgprebootpolicy is running, and the name of the network bootstrap program ( nvlnbp.sys...
Page 368 The following illustrates the differences for a LAN configuration between installing Preboot Services on the same server as DHCP, or on a separate server. In this case, only the PXE devices on the LAN connect to the Preboot Services imaging server. 368 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 369 LAN Configuration Differences Between the Same and Separate Servers Table 29-3 Information On the Same Server On Separate Servers Configuration Because Preboot Services and DHCP are None required. running on the same server, option tag 60 must be set on the DHCP server. For information on setting this tag, see “Configuring LAN Environments for Preboot Services”...
Page 370 DHCP is installed and running. However, you must do the following to make it work: Set option tag 60 on the DHCP server so that it can work with the novell-proxydhcp daemon. See the steps in the previous section (“Configuring LAN Environments for Preboot Services”...
Page 371 The second VLAN gateway is 10.1.1.1. This VLAN hosts the DHCP server with IP 10.1.1.2. This VLAN is named VLAN2. The third VLAN gateway is 196.10.229.1. This VLAN hosts the server running novell-proxydhcp and novell-zmgprebootpolicy. The server’s IP is 196.10.229.2. This VLAN is named VLAN3.
Page 372 IP address of the gateway that serves the PXE device, and is the IP agent server address of the server that the DHCP frame should be forwarded to. 3 Save the configuration. 372 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 373 IMPORTANT: If the switch is acting as a firewall and limiting the type of traffic on the network, understand that the novell-tftp and novell-zmgprebootpolicy daemons are not firewall or network filter friendly. You should not attempt to run these daemons through a firewall. If users need to pass preboot work through a firewall, then all Preboot Services work needs to be on the outside and merely reference a Web service inside the firewall.
Page 374: Administering Preboot Services
The Proxy DHCP server provides PXE devices with the information that they require to be able to connect to the Preboot Services system. Use the following steps to modify the settings of novell-proxydhcp: 1 Open the following file in an editor: /etc/opt/novell/novell-proxydhcp.conf...
Page 375 /etc/init.d/novell-pbserv restart Configuring Novell-zmgprebootpolicy The novell-zmgprebootpolicy daemon is used to check if there are any imaging actions that need to be performed on the device. It forwards requests to novell-pbserv on behalf of PXE devices. Use the following steps to modify the settings of novell-zmgprebootpolicy: 1 Open the following file in an editor: /etc/opt/novell/zenworks/preboot/novell-zmgprebootpolicy.conf...
Page 376: Editing The Preboot Services Menu
PXE devices on this port. Although PXE devices make their initial requests to the novell-tftp and novell-zmgprebootpolicy daemons on the ports listed above, the remainder of the transactions can occur on any available port.
Page 377 The following procedure should be done on each imaging server where you want to customize the menu. To edit the Preboot Services Menu: 1 In a text editor, open the following file on an imaging server where novell-proxydhcp is running: /srv/tftp/pxemenu.txt...
Page 378 Hint4 = Re-enable a Disabled ZENworks Partition Hint5 = DELL Deployment Toolkit v2.1 in Automated Mode Hint6 = DELL Deployment Toolkit v2.1 in Maintenance Mode Hint7 = Boot to Local Hard Drive 378 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 379: Configuring Preboot Services Defaults
2 To change the appearance of the menu, edit the first seven sections (title and colors). To change colors, the mnemonics you enter must be selected from the following: BLACK GRAY LT_GREEN BLUE MAGENTA YELLOW LT_CYAN GREEN BROWN BRIGHT_WHITE LT_RED CYAN WHITE LT_BLUE...
Page 380: Configuring Preboot Services Menu Options
This sets the default Preboot Services Menu display mode for the ZENworks Management Zone. This can be overridden at the folder or device level. For more information, see Section 29.5, “Overriding Preboot Services Defaults,” on page 399. 380 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 381: Configuring Image Storage Security
IMPORTANT: PXE must be enabled on the device for the menu to be displayed. The Preboot Services menu provides options for how Preboot Services can be used on your devices. The following options are presented when the menu is displayed: Preboot Services Menu Options Table 29-6 Menu Option...
Page 382 To remove a directory path from the listing, select the path and click Remove. You can select multiple paths for removing. 5 Click either Apply or OK to save the changes. This sets the default image storage settings for the ZENworks Management Zone. 382 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 383: Configuring Non-Registered Device Settings
29.4.3 Configuring Non-registered Device Settings The following configurations can be set after a device is imaged. The settings are applied to devices not registered in the ZENworks Management Zone. For more information, see Section 28.3.4, “Non-registered Device Settings,” on page 334.
Page 384 DNS suffix: Provides a suffix for all of your device’s names. For example, if you enter “provo.novell.com” and a device’s name is “device1,” that device’s full name becomes “device1.provo.novell.com.” Name servers: To control what DNS servers the device uses, specify a DNS name server, then click Add to place it into the listing.
Page 385 These are the settings that the device is told to use after it is imaged. It uses them for Preboot Services work any time it reboots. Use DHCP: Allows the devices to be dynamically assigned IP addresses. For Red Hat Enterprise Linux, using the DHCP option causes a “Could not look up Internet address...”...
Page 386: Configuring Preboot Work Assignments
1 In the ZENworks Control Center, click the Configuration tab, which displays the following Management Zone Settings section: 2 In this section, click Preboot Services to display the configuration sections. 3 Locate the Preboot Work Assignment section: 386 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 387 4 If you plan to select Hardware Type when constructing a rule (see Step 12), you must first configure the hardware type in one of the following fields: Servers: Specify a full or partial string that identifies a server’s BIOS from a match in its Product Name field, then click Add to place the string into the Servers list.
Page 388 Use These Kernel Boot Parameters: Specify the boot parameters to be used with one of the Preboot Services Menu options. 9 Review the following to understand how to configure the work rule logic: 388 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 389 A rule is made up of one or more filters that are used to determine whether a device complies with the rule. The Rule Construction dialog box begins with one empty filter. A device must match the entire filter list of a rule (as determined by the logical operators that are explained below) for the rule to apply to the device.
Page 390 Subsequent clicks of the Add filter option add those filters to the end of the current set, which is the last listed filter set when there are multiple filters in the set (see Add Filter Set below). You cannot insert a new filter between existing filters. 390 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 391 The order of the filters in a set does not matter, and you cannot reorder the filters after you have created them. What matters in this structure is properly grouping the filters with respect to the selected OR and AND operator options. Add filter set: Adds the next filter as a filter set with either AND or OR placed between the filter sets, as dictated by your selection in the Combine filters using field.
Page 392 Server, Laptop, or Workstation. Server and Laptop must be defined to be useful, or the effect is the same as selecting Workstation, which is the default hardware type and does not need a BIOS identification defined. 392 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 393: Configuring The Server Referral List
IMPORTANT: Be aware of the possibility of creating conflicting filters. For example, if the RAM (in MB) field is used in multiple filters, make sure the effective logical operators where each is used make sense for the MB values that you enter. You could have one filter requiring exactly 512 MB of RAM and another accepting a device having at least 512 MB of RAM.
Page 394 6 Depending on the ZENworks version of the server, do the following to copy the necessary files from the ZENworks Linux Management imaging server to your directory on the servers \tftp in your referral list: ZENworks Version Files to Copy Action ZENworks 6.5 /svr/tftp/z_auto65.cfg Copy the files. /svr/tftp/pxelinux.0 394 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 395: Configuring Intel Active Management Technology (Amt)
ZENworks Version Files to Copy Action ZENworks 7 (running on a Copy both of the files, but /svr/tftp/z_auto.cfg NetWare or Windows server) rename z_auto.cfg /svr/tftp/pxelinux.0 z_auto65.cfg file may not contain the same information as /svr/tftp/z_auto.cfg /svr/tftp/ , so that when you rename it with the , it might have different content than the z_auto65.cfg file used for ZENworks 6.5 servers.
Page 396 5 If you configured the AMT device to use DHCP mode for IP addressing, you might need to boot the device into an operating system to discover a currently valid IP address. 396 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 397 . This provides the currently assigned IP address. ifconfig eth0 6 Run on a Windows XP /opt/novell/zenworks/zdm/winutils/smb-provisioning.exe workstation running .NET framework to display the following dialog box: This must be run on a different device than is being provisioned. 7 Fill in the fields: 7a Enter the appropriate administrator account and passwords in their respective fields.
Page 398 Name list: Enterprise names are given to AMT devices when they are provisioned. This list should contain at least one valid AMT enterprise name for every AMT device in the ZENworks Management Zone. Click Add to place each one into the list box. 398 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 399: Overriding Preboot Services Defaults
Move up/Move down: Arranges the order in which the AMT names are listed. You can move only one at a time. Remove: To remove a name from the list, select the name, then click Remove. 5 Click either Apply or OK to save the changes 29.5 Overriding Preboot Services Defaults You can determine which Preboot Services Menu displays a configuration to use and whether the menu should be displayed on a device when it boots.
Page 400 Pressed for your Preboot Services Menu option, which allows PXE-enabled Linux devices to automatically implement the AutoYaST or kickstart bundles. 7 Click Apply or OK. OK: Enables the change and exits the page. 400 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 401: Enabling Pxe On Devices
Apply: Enables the change and retains focus on the page, so you can click Revert to temporarily disable the configuration change. 8 To temporarily disable the change, click Revert and the ZENworks Management Zone settings for the menu remain in effect. 29.6 Enabling PXE on Devices To image a device using Preboot Services, you need to find out if the device is PXE capable, and then make sure that PXE is enabled.
Page 402: Verifying That Pxe Is Enabled On A Device
This section gives the requirements for using a network-connected device. It is possible (but usually not as convenient) to image a device without connecting to the network. Such operations can’t be fully automated. The following are the requirements for the device: 402 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 403: Enabling A Device For Imaging Operations
Device Requirements Table 29-7 Device Must Have Because A supported Ethernet The device must connect with the imaging server to store or retrieve the card images. This connection is made when the device is under the control of the ZENworks Imaging Engine. Therefore, make sure the device has a supported Ethernet card.
Page 404: Disabling Persistent Device Names
X represents the number of Ethernet devices on ifcfg-ethX, the system. For example, the name for the configuration eth0 ifcfg-eth0 3 In file, change the value of the /etc/sysconfig/network/config FORCE_PERSISTENT_NAMES 4 Reboot the device. 404 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 405 Disabling the Persistent Network Device Names for SLES 9 / NLD You must rename the Ethernet configuration file to initialize the Ethernet devices on boot. 1 Go to /etc/sysconfig/network 2 Find the file for each Ethernet device. In the filename, the trailing identifier for an ifcfg-eth Ethernet device represents the MAC address for the device.
Page 406 406 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 407: Using Preboot Services
Using Preboot Services ® ® This section provides instructions on how to use Novell ZENworks Linux Management Preboot Services: Section 30.1, “Imaging Devices,” on page 407 Section 30.2, “Multicasting Images,” on page 429 Section 30.3, “Configuring AutoYaST or Kickstart Installation Script Bundles,” on page 440 Section 30.4, “Configuring ZENworks Script Bundles,”...
Page 408 Actions > Take image. If you do so, you are asked to select a device from the group. Then the File Information page is displayed. 4 Click Next to display the File Information page: 5 Fill in the fields: 408 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 409 Server and file path: (Required) Browse for the object, DNS name, or IP address of the server where the image file is to be stored, then specify the path to the storage location. This must be a server where ZENworks Linux Management is installed. Images can take up a large amount of disk space.
Page 410 1 In the ZENworks Control Center, click the Bundles tab. 2 Click New > Bundle to start the Create New Bundle Wizard: 3 In the Create New Bundle Wizard, select Preboot bundle, then click Next. 410 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 411 4 On the Select Preboot Bundle Type page, select ZENworks Image bundle. 5 Click Next to display the Set General Information page: 6 Fill in the fields: Name: (Required) Although bundles can be identified in ZENworks Control Center by their type of icon, as well as the folder they are listed under, you should develop a naming scheme that differentiates the ZENworks Image bundles that are listed together in a folder.
Page 412 Explorer to determine which data to exclude and assign this to a file set number, such as 2. When a device assigned to this ZENworks Image bundle boots, it is imaged with the smaller version (file set 2) of device1image.zmg 412 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 413 1, which is the default file set if you don’t select a file set when using this wizard. Add: Accesses the Server and Path Information dialog box: Server object, IP, or DNS: The identity of the imaging server where the Novell ZENworks Linux Management Imaging Agent (novell-zislnx) is installed and running, and where the base image file is stored.
Page 414 DVD when finished. For information on creating a ZENworks Script bundle, see Section 30.4, “Configuring ZENworks Script Bundles,” on page 450. 414 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 415: Performing Manual Imaging Tasks
30.1.2 Performing Manual Imaging Tasks The following manual imaging tasks are available: “Manually Taking an Image of a Device” on page 415 “Using Image Explorer to Customize an Image” on page 418 “Creating an Add-On Image” on page 419 “Manually Putting an Image on a Device” on page 420 “Making an Image Available for Automatic Imaging”...
Page 416 6 is the same as Balanced. 9 is the same as Optimize for space. (Optimize for speed takes the least amount of time but creates 416 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 417 the largest image file. Optimize for space creates the smallest image file but might take a significant amount of time. Balanced is a compromise between compression time and image file size.) For example: img makel /imgs/dellnt.zmg comp=6 IMPORTANT: Make sure to use forward slashes in the UNC path as shown above. Backslashes are not recognized by Linux.
Page 418 CDs or DVDs. Splitting a device image is helpful for putting down or restoring images in a disconnected environment. For more information, see Section D.1.15, “Splitting an Image,” on page 611. 418 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 419 To create an add-on image: 1 Run the Image Explorer utility, which is located on the Linux imaging server at: /opt/novell/zenworks/zdm/winutils/ImgExp.exe 2 Drag files and folders from an existing device into a new image archive. For more information, see Section D.1, “Image Explorer (imgexp.exe),”...
Page 420 6 Enter a command at the bash prompt using one of the following formats: To restore an image from the imaging server and put it down on a device, enter: img restorep serverIPaddr_or_DNSname //uncpath/newimg.zmg 420 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 421 The restorep parameter stands for “restore from proxy,” which retrieves an image from the imaging (proxy) server and puts it on this device. The IP address or DNS name should be that of your imaging server, and the UNC path specifies the location and filename where the image is to be retrieved from.
Page 422 When you boot a device from an imaging method and allow the boot process to proceed in auto- imaging mode, the imaging operation that is performed on the device is determined by default Preboot Services settings that you define in the ZENworks Control Center. 422 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 423 Creating a Preboot Services bundle also allows you to combine a base image and one or more add- on images into a single entity that can be put down on target devices. You can specify a standard image file to put down, or you can create a script to further customize your imaging operation. You can also specify that a particular file set of an image be used.
Page 424: Setting Up Disconnected Imaging Operations
You can put down an image from a bootable or non-bootable imaging CD or DVD using either the bash prompt or using the ZENworks Imaging Engine menu. 424 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 425 The following sections contain additional information: “Putting Down an Image Using the Bash Prompt” on page 425 “Putting Down an Image Using the ZENworks Imaging Engine Menu” on page 425 Putting Down an Image Using the Bash Prompt 1 Use your CD- or DVD-burning software to burn the source image onto a CD or DVD. 2 Boot the device using one of the following methods: If the device is PXE-enabled, boot it from the Preboot Services imaging server.
Page 426 Boot the device using an imaging boot CD or DVD. For more information, see Section 29.2.2, “Preparing Imaging Boot CDs or DVDs,” on page 354. Boot the device from the ZENworks partition. For more information, see “Creating a ZENworks Partition” on page 362. 426 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 427 2 Enter from the bash prompt. manual 3 At the Linux prompt, enter to view the available partitions. img dump Note the number of the partition where you will store the new image. 4 Enter a command using the following format: img makel[pNumber] /path/image.zmg [comp=comp_level] where pNumber is the number of the partition to store the image in, and comp_level is the amount of compression used when creating the image.
Page 428 1 Boot the device using one of the following methods: If the device is PXE-enabled, boot it from the Preboot Services imaging server. For more information, see Section 29.2.1, “Using Preboot Services (PXE),” on page 354. 428 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 429: Multicasting Images
Boot the device using an imaging boot CD or DVD. For more information, see Section 29.2.2, “Preparing Imaging Boot CDs or DVDs,” on page 354. Boot the device from the ZENworks partition. For more information, see “Creating a ZENworks Partition” on page 362.
Page 430 2 Click New > Bundle to start the Create New Bundle Wizard: 3 In the Create New Bundle Wizard, select Preboot bundle, then click Next to display the Select Preboot Bundle Type page: 430 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 431 4 Select ZENworks Multicast bundle, then click Next to display the Set General Information page: 5 Fill in the fields: Name: (Required) Although bundles can be identified in ZENworks Control Center by their type of icon, as well as the folder they are listed under, you should develop a naming scheme that differentiates the ZENworks Multicast bundles that are listed together in a folder.
Page 432 Explorer to determine which data to exclude and assign this to a file set number, such as 2. When a device assigned to this ZENworks Image bundle boots, it is imaged with the smaller version (file set 2) of device1image.zmg 432 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 433 The advantage file sets provide is that you can create a base image and modify it slightly for various devices, instead of creating separate, somewhat different base images for each device. However, because file sets only concern excluded files, if you add files to the base image using Image Explorer, all file sets will include those additional files.
Page 434 1 In the ZENworks Control Center, click the Bundles tab to display the Bundles page: 2 Select the check box next to a ZENworks Multicast bundle. 3 Click Actions > Enable multicast session to start the Enable Multicast Session Wizard: 434 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 435: Multicasting Manually
If it is not running, then enter: /etc/init.d/novell-pbserv -start 2 In the shell console, enter the following command to enable a multicast session: /opt/novell/zenworks/preboot/bin/novell-zmgmcast -mcast arguments where arguments represents the following that you can append to the command line: Using Preboot Services 435...
Page 436 IMPORTANT: The image is sent to and put down on each participating device only after you initiate the multicast session from each participating client. 3 To view the status of the multicast session, enter: 436 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 437 “Using the ZENworks Imaging Engine Menu to Perform the Multicast Session” on page 438 Using the Bash Prompt to Perform the Multicast Session 1 (Optional) Install the Novell ZENworks Linux Management Imaging Agent (novell-zislnx) on each of the participating devices.
Page 438 Using the ZENworks Imaging Engine Menu to Perform the Multicast Session 1 (Optional) Install the Novell ZENworks Linux Management Imaging Agent (novell-zislnx) on each of the participating devices. If you do not install the Imaging Agent on each participating device, the devices have duplicate network identities.
Page 439 The session name is any string that uniquely identifies this multicast session from other multicast sessions that might be in progress on the network. Use the same session name on each of the participating devices in this multicast session. You can specify any multicast session, including one that originates from the imaging server (as long as you specify the session name used by the imaging server).
Page 440: Configuring Autoyast Or Kickstart Installation Script Bundles
To configure an AutoYaST bundle, and assign devices to the bundle: 1 In the ZENworks Control Center, click the Bundles tab to display the Bundles page: 2 Click New > Bundle to start the Create New Bundle Wizard: 440 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 441 3 In the Create New Bundle Wizard, select Preboot bundle, then click Next to display the Select Preboot Bundle Type page: 4 On the Select Preboot Bundle Type page, select AutoYaST bundle, then click Next to display the Set General Information page: 5 Fill in the fields: Name: (Required) Although bundles can be identified in ZENworks Control Center by their type of icon, as well as the folder they are listed under, you should develop a naming scheme...
Page 442 6 Click Next to display the Set AutoInstall Attributes page: 7 Fill in the fields: Linux kernel file: The path should be relative to the home directory of the novell-tftp daemon. For example, you might do the following: a. Copy the kernel file, whose default location is...
Page 443 Path to the network installation directory (relative to protocol): The path should be relative to the home directory of the selected protocol daemon. For example, if you specify the HTTP protocol, enter myserver.provo.novell.com as the DNS name, and specify the path as , then the URL to the /installs/scripts/myscript.cfg...
Page 444 AutoYaST script name and path (relative to the protocol default directory): The path should be relative to the home directory of the selected protocol daemon. For example, if you select the HTTP protocol, enter myserver.provo.novell.com as the DNS name, and enter the path and filename as , then the URL to the /scripts/autoyast.xml...
Page 445 (Optional) Select one or both of the following options: Use the IP Address from Content in the Preboot Bundle Rather Than from the Device’s Image Safe Data Use this option if you have previously taken an image of the device and are using that image with this Preboot bundle.
Page 446: Configuring A Kickstart Bundle
1 In the ZENworks Control Center, click the Bundles tab. 2 Click New > Bundle to start the Create New Bundle Wizard: 3 In the Create New Bundle Wizard, select Preboot bundle, then click Next. 446 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 447 4 On the Select Preboot Bundle Type page, select Kickstart bundle, then click Next to display the Set General Information page: 5 Fill in the fields: Name: (Required) Although bundles can be identified in ZENworks Control Center by their type of icon, as well as the folder they are listed under, you should develop a naming scheme that differentiates the kickstart bundles that are listed together in a folder.
Page 448 7 Fill in the fields: Linux kernel file: The path should be relative to the home directory of the novell-tftp daemon. For example, you might do the following: a. Copy the kernel file, whose default location is on a Red Hat Enterprise /isolinux/vmlinuz Linux 4 bootable CD.
Page 449 Kickstart script name and path (relative to the protocol default directory): The path should be relative to the home directory of the selected protocol daemon. For example, if you select the HTTP protocol, enter myserver.provo.novell.com as the DNS name, and enter the path and filename as , then the URL to the installation /config/ks.cfg...
Page 450: Configuring Zenworks Script Bundles
To configure a ZENworks Script bundle and assign devices to the bundle: 1 In the ZENworks Control Center, click the Bundles tab. 2 Click New > Bundle to start the Create New Bundle Wizard: 450 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 451 3 In the Create New Bundle Wizard, select Preboot bundle, then click Next. 4 On the Select Preboot Bundle Type page, select ZENworks Script bundle, then click Next to display the Set General Information page: 5 Fill in the fields: Using Preboot Services 451...
Page 452 IP address and ZENworks Control Center object information. (Optional) Select one or both of the following options: Use the IP Address from Content in the Preboot Bundle Rather Than from the Device’s Image Safe Data 452 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 453 Use this option if you have previously taken an image of the device and are using that image with this Preboot bundle. This option causes the imaging process to write the device’s IP address that is contained in this image to the Image Safe Data location on the replacement hard drive.
Page 454: Using Dell Configuration Bundles
When you create a Dell Configuration bundle you might need specialized scripts or files to already exist, depending on which settings you employ in the bundle. Novell recommends that you follow the instructions in the Dell DTK documentation to create the necessary configuration files and scripts.
Page 455 2 Boot a Dell device that is PXE-enabled and press the Ctrl-Alt keys during booting. Press these keys when a string starting with “Novell ...” is displayed during the boot process. IMPORTANT: Choose the correct device to boot for creating the BIOS, BMC, or DRAC 5 file.
Page 456 2 Boot a Dell device that is PXE-enabled and press the Ctrl-Alt keys during booting. Press these keys when a string starting with “Novell ...” is displayed during the boot process. IMPORTANT: Choose the correct device to boot for creating the RAID script. The devices to receive the update must be the same as the device you are using to configure the script.
Page 457: Creating Dell Configuration Bundles
2 Boot a Dell device that is PXE-enabled and press the Ctrl-Alt keys during booting. Press these keys when a string starting with “Novell ...” is displayed during the boot process. IMPORTANT: Choose the correct device to boot for creating the DRAC 4 file. The devices to receive the update must be the same as the device you are using to configure the file.
Page 458 3 In the Create New Bundle Wizard, select Preboot bundle, then click Next. 4 On the Select Preboot Bundle Type page, select Dell Configuration bundle, then click Next to display the Set General Information page: 5 Fill in the fields: 458 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 459 Name: (Required) Although bundles can be identified in ZENworks Control Center by their type of icon, as well as the folder they are listed in, you should develop a naming scheme that differentiates the Dell Configuration bundles that are listed together in a folder. For more information, see Appendix C, “Naming Conventions in the ZENworks Control Center,”...
Page 460 MBR (the default). However, you must set this boot partition as Active. Then, when the Dell utility partition writes its MBR information, it does not conflict with grub, because its boot loader is not located in the same place. 460 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 461: Assigning Unassigned Preboot Bundles
Grub menu item for the Dell utility partition: If the devices are not using the Dell utility partition boot loader, you can use grub in the MBR (the default) and still provide an F10 menu option to the Dell utility partition. Edit the file and add the /boot/grub/menu.1st following lines:...
Page 462 3 Browse for and select the devices that you want to be assigned to this bundle, then click OK. You can select individual devices, or the Servers or Workstations folders containing such devices, or mixtures of folders and devices. 4 Click Next to display the Bundle Groups page: 462 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 463: Editing Preboot Services Work
This is optional. You can click Next to display the Summary page without assigning a bundle group. In this case, skip to Step 5 Click Add to display the Select Groups dialog box: 6 Browse for and select the groups that you want to be assigned to this bundle, then click OK. You can select individual groups, including browsing the folders containing groups.
Page 464 Take an image: Continue with Step 5 If you select Do nothing, review the image files, then skip to Step The Applied Image Files section displays the image files most recently applied to this device. 464 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 465 6 If you select Apply Preboot bundle, fill in the field under Bundle to Apply, then skip to Step Bundle: Select or specify the bundle. Its bundle name, folder, and description are displayed. The Bundle field displays the currently effective bundle. You can select the bundle to apply from the drop-down list, which changes the effective bundle for the device.
Page 466 Optimize for space: Optimizes the compression to minimize the image file’s size to conserve disk space. This can cause reimaging to take longer. 8 Click OK to exit the wizard. Your changes should be displayed in the Preboot Work section for the device. 466 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 467: Imaging Utilities And Components
Imaging Utilities and Components ® ® The following sections provide reference information on Novell ZENworks Linux Management imaging utilities, commands, and configuration settings. Section 31.1, “Starting Image Explorer,” on page 467 Section 31.2, “Determining the Image Explorer Version,” on page 467 Section 31.3, “Image Explorer versus Linux Konquerer,”...
Page 468: Opening An Image
Author: Specify the author of this version of the image. Comments: Specify any information that is helpful. 6 Save the image file to save your properties changes. 7 To close the properties dialog box, click OK. 468 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 469: Image File Operations
31.6.2 Viewing the Properties of an Image File Item 1 Click File > Open. 2 Browse for and select the image file. Large image files might take a few moments to open. 3 Select a partition, directory, or file in the image. For other information on a partition’s properties, see Section 31.6.3, “Changing a Partition’s Size,”...
Page 470: Compressing An Image File
This option is used by default when an image is created. Compress for Size: Creates the smallest image file but takes longer to compress. 5 Click Compress to compress the image file, using the settings you specified. 470 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 471: Splitting An Image
Compressing an Unopened Image File Use this dialog box to set compression options to quickly compress an image file without waiting for the file to fully load into Image Explorer. To quickly compress an image file: 1 Click Tools > QuickCompress. 2 Fill in the fields: Image File to Compress: Specify or browse to an existing imaging file to compress.
Page 472: Hiding And Removing Content In The Image File
3 Select the directories and files that were previously hidden that you want to unhide. 4 Click Image > Undelete. You can also right-click the selected directories and files, then select Undelete. This makes them available in the image when it is applied to a device. 472 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 473: Configuring File Sets
Removing Hidden Directories and Files from the Image File To permanently remove hidden directories and files from the open image in order to create a different version of the image file: 1 Click File > Open. 2 Browse for and select the image file. Large image files might take a few moments to open.
Page 474: Extracting Content As Files
Click Image > Add Directory and select the directories to be added. Click the Add Directory icon and select the directories to be added. Click the Add File icon and select the files to be added. 474 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 475: Modifying Image Content
4 Click File > Save As, then specify the filename of the add-on image, including the .zmg filename extension. 31.8 Modifying Image Content You can modify the content of an image file in the following ways: Section 31.8.1, “Adding Directories and Files,” on page 475 Section 31.8.2, “Creating a New Directory,”...
Page 476: Creating A New Image File
.zmg 2 Click Image > Create Partition. 3 Repeat Step 1 through Step 2 as necessary. 4 To add content to the partitions, continue with “Adding Content” on page 477. 476 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 477 Adding Content 1 See Section 31.8, “Modifying Image Content,” on page 475 for instructions on adding new content. 2 Continue with “Configuring File Sets” on page 477, or return to Step 3 “Creating, Configuring, and Saving the New Image File” on page 476.
Page 478 478 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 479 Hardware and Software Inventory V I I ® ® The following sections provide information on Novell ZENworks Linux Management hardware and software inventory features: Chapter 32, “Inventory Overview,” on page 481 Chapter 33, “Reviewing the Device Inventory,” on page 483 Chapter 34, “Rolling Up Hardware Inventory,”...
Page 480 480 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 481: Inventory Overview
Inventory Overview ® ® The Server Inventory component of Novell ZENworks Linux Management allows you to collect hardware and software inventory information from local and remote servers or workstations of your enterprise. This inventory information is scanned and stored in a database that can be accessed by the ZENworks administrator.
Page 482 482 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 483: Reviewing The Device Inventory
Reviewing the Device Inventory ® From the ZENworks Control Center you can view the complete hardware and software inventory of servers and workstations. This section discusses the following topics: Section 33.1, “Accessing the Device Inventory,” on page 483 Section 33.2, “Reviewing Device Inventory Summaries,” on page 483 Section 33.3, “Reviewing Hardware (General),”...
Page 484: Reviewing Hardware (General)
Dell applications installed on the selected managed device 33.5 Reviewing Hardware Details The following table provides common device information that might be useful for troubleshooting. For detailed information about each device, click the hardware component name in the interface. 484 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 485 Common Device Information Table 33-4 Inventory Item Attributes Description Batteries Name Battery name. Manufacturer Battery manufacturer name. Serial Number Battery serial number. Chemistry The battery chemistry, for example, lithium-ion or nickel metal hydride. BIOS Name BIOS name. Manufacturer BIOS manufacturer name. Version The version or revision level of the BIOS.
Page 486 Parallel Ports Name Port name. Description Port description. Physical Disks Name Disk name. Manufacturer Disk manufacturer. Capacity Capacity of the disk. Free Space Remaining free space on the disk. 486 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 487 Inventory Item Attributes Description Pointing Devices Name Pointing device name. When a pointing device is connected through a KVM (keyboard, video, mouse) switch, the system might not pass the correct name and configuration of the device, because of manufacturing limitations for the device.
Page 488: Refreshing Device Inventory
Remote Execute policy. For more information, see Section 16.6, “Remote Execute Policy,” on page 164. IMPORTANT: The Device Refresh Schedule setting does not affect refresh inventory information. 488 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 489: Rolling Up Hardware Inventory
Rolling Up Hardware Inventory ® ® You can roll up the hardware inventory data from the Novell ZENworks Linux Management database to the ZENworks 7 Server Management or ZENworks 7 Desktop Management Inventory database to view the inventory data at the enterprise level.
Page 490: Understanding The Roll-Up Process
ZENworks uses the following process to collect inventory and roll it up to the Inventory server 1. The Sender converts the hardware inventory stored in the ZENworks 7 Linux Management database into files, and places the files into the .str /var/opt/novell/zenworks/ directory. inventory/entmerge 490 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 491: Understanding The Components Involved In The Inventory Roll-Up
) if a database is attached to .zip dbdir the Inventory server. 7. The Sender-Receiver logs the status in Novell eDirectory 34.4 Understanding the Components Involved in the Inventory Roll-Up The Sender on the Inventory servers transfer the scan files from the ZENworks 7.3 Linux Management Inventory server to the ZENworks 7 Server Management or ZENworks 7 Desktop Management Inventory server.
Page 492: Viewing The Inventory Data Stored In The Zenworks 7 Server Management Or Zenworks
For more information on how to invoke and work with these utilities, see the “Workstation Inventory” section in the Novell ZENworks 7 Desktop Management Administration Guide (http:// www.novell.com/documentation/zenworks7)or the see the “Server Inventory” section in the Novell ZENworks 7 Server Management Administration Guide (http://www.novell.com/documentation/ zenworks7).
Page 493: Part Viii Remote Management
VIII Remote Management V I I I ® ® The Remote Management component of Novell ZENworks 7.3 Linux Management gives you the ability to remotely manage devices from the management console. Remote Management allows you Remotely control the managed device...
Page 494 494 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 495: Remote Management Overview 35.1 Remote Management Terminology
Remote Management Overview ® ® You can use Novell ZENworks 7.3 Linux Management to remotely manage all the supported platforms. To see details on supported platforms, see “Managed Device Requirements” in the Novell ZENworks 7.3 Linux Management Installation Guide. The following sections provide information to help you understand the functionality of Remote Management components: Section 35.1, “Remote Management Terminology,”...
Page 496: Understanding Remote Control
Remote Login session. During a Remote Login session, you can now switch between the active applications running on the managed device using Alt+Z in the Remote Management Viewer. 496 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 497: Setting Up Remote Management
Setting Up Remote Management The following sections provide information on deploying the Remote Management component of ® ® Novell ZENworks 7.3 Linux Management in a production environment: Section 36.1, “Configuring the Remote Management Settings,” on page 497 Section 36.2, “Configuring Remote Management Agent,” on page 500 Section 36.3, “Starting Remote Management Operations Using the ZENworks Control Center,”...
Page 498 NOTE: We recommend you to use the No password option judiciously as it allows access to the managed device without any password. 8 Click Apply. These changes will be effective on the managed devices on their next Settings Refresh Schedule. 498 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 499: Configuring Remote Management Settings At The Folder Level
36.1.2 Configuring Remote Management Settings at the Folder Level 1 In the ZENworks Control Center, click Devices. 2 Click the folder you wish to configure. 3 Click Settings, then click Remote Management. 4 Click Override. 5 Edit the Remote Management Settings as required. 6 Click Apply.
Page 500: Configuring Remote Management Agent
# /opt/novell/zenworks/sbin/zrmservice --passwd The password is case-sensitive and should be between three to eight characters in length. NOTE: This step is not necessary if the Password Policy is configured to No password. 500 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 501: Clearing The Remote Management Agent Password
To clear the Agent password on the managed device, enter the following command at the shell prompt: # /opt/novell/zenworks/sbin/zrmservice --clrpasswd 36.2.3 Clearing Remote Management Agent Log Files To clear the Agent log files on the managed device, enter the following command at the shell...
Page 502: Initiating A Remote Management Session From The Device Context
Workstation Tasks (if you have selected Workstation) in left pane. 4 If you have selected the device in step 3, click Remote control in the Action menu to open the Remote Management dialog box: 502 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 503: Starting Remote Management Operations Using The Native Vncviewer
5 Select the IP address of the device. 6 Select the Remote Management operation to be performed on the device. The drop-down list of operations is based on the effective Remote Management Settings for the managed device. The available options are Remote control, Remote view, and Remote login. The following table lists and explains all the operations you can select from the drop-down list: Option Description...
Page 504: Starting Remote Management Operations Using The Windows Vnc Viewer
3 Launch Tight VNC Viewer by specifying the following command at the Shell prompt: $ vncviewer 4 In serverDialog, specify the IP address with a port number as configured, then click OK. 504 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 505: Establishing Ssh Tunneling
You can specify the port number after the IP address with a double colon (::) preceding it. For example, if the IP address of the managed device is 192.168.0.1, and the Remote Control Service port number is 5950, specify the IP address as 192.168.0.1::5950. You can specify the display number after the IP address with a single colon (:) preceding it.
Page 506 Reduce the depth of color pixels. More Performance Tuning Tips For additional information on performance tuning tips, refer to the following Web sites for specific components: www.tightvnc.com (http://www.tightvnc.com) www.realvnc.com (http://www.realvnc.com) FAQs on x11VNC (http://www.karlrunge.com/x11vnc) 506 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 507: Part Ix Event Monitoring
Event Monitoring ® ® Novell ZENworks Linux Management includes a Message Logger component that tracks and logs significant system events. Administrators can use this information to monitor events related to devices, policies, and bundles. Specifically, event monitoring allows you to do the following:...
Page 508 508 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 509: Event Monitoring Overview
Event Monitoring Overview Event monitoring allows you to manage your environment by taking messages from the Message Logger and displaying them in various event logs, making it easy to track errors, problems, and successful events for your devices, policies, and bundles. You can capture and store specific events related to devices, policies, and bundles that you or your organization’s help desk can analyze and use to monitor problems without visiting the server or workstation, which can reduce problem resolution times and increase productivity.
Page 510: Monitoring Device Events
Those with the most problems are listed first. With the Hot List, you can see at a glance which device, policy, or bundle needs the most attention. 510 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 511: Backing Up The Log Files
37.6 Backing Up the Log Files You can take a backup of or any other /var/opt/novell/log/zenworks/tomcat/catalina.out log file using the logrotate utility. The logrotate utility is available with the operating system. The utility eases the administration of systems that generate large numbers of log files. It allows automatic rotation, compression, and removal of log files.
Page 512 The configuration defined in the file creates a maximum of five rotating log4j.properties backups for the file. The maximum size of each backup log file can be upto 100 MB. catalina.out 512 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 513: Working With Event Logs
Working with Event Logs Event logs are automatically created for important events, such as successful installations or critical errors. Section 38.1, “The Event Log Page,” on page 513 Section 38.2, “Working with the Log Pages,” on page 515 38.1 The Event Log Page The Event Log page gives you an overview of the recorded events.
Page 514 Event Log is displayed only for servers that are functioning as primary or secondary ZENworks Servers. The System Event Log lists the system event messages generated by the ZENworks Server for activities that it performs on behalf of all managed devices in its management zone. 514 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 515: Working With The Log
38.2 Working with the Log Pages After an event has been logged, you can view and acknowledge it. Section 38.2.1, “Viewing an Event Log,” on page 515 Section 38.2.2, “Acknowledging an Event,” on page 516 Section 38.2.3, “Using the Advanced Page,” on page 518 Section 38.2.4, “Clearing the Event Log,”...
Page 516: Acknowledging An Event
You can acknowledge a single event, acknowledge multiple events, or acknowledge all events. To acknowledge a single event: 1 Open the Summary page. (For information, see Section 38.2.1, “Viewing an Event Log,” on page 515.) 2 Click the event you want to acknowledge. 516 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 517 3 Click Acknowledge. The event disappears from the list but remains in the database and is listed on the Advanced page. To acknowledge several events: 1 Open the Summary page. (For information, see Section 38.2.1, “Viewing an Event Log,” on page 515.) 2 Click Advanced on the toolbar in the Event Log section.
Page 518: Using The Advanced Page
To clear the event log for a workstation: 1 Open the Devices page, then click Workstations. 2 Click the check box of the workstation you want cleared of events. 3 Click Action on the toolbar. 4 Click Message Cleanup. 518 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 519 From here you can do the following: Acknowledge all event messages for the device. This acknowledges all events within a specified date range and deletes them from the Hot List, event log, and system event log. Clear all event messages. This clears all events within a specified date range from the event log, system event log, advanced event log, and advanced system event log.
Page 520 520 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 521: What Is Message Logger
Message Logger ® ® You can use the Message Logger component of Novell ZENworks Linux Management to log the messages on managed devices and servers. The following sections provide information to help you understand the functionality of the Message Logger component: Section 39.1, “What Is Message Logger?,”...
Page 522: Debugging And Logging Zmd
<LoggerModule trace = "true"> <param name="fileDebug" enable = "true" value ="true" /> 2. Edit the file to /etc/opt/novell/zenworks/logger-log4j-loader-conf.xml configure any specific loader module as follows: <logger name="LocalLogger.ComponentName" additivity="true"> <level value="debug"/> 522 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 523 </logger> where component name can be DataModelModule, QueueRunner, Sender, ZLMCleanupDevice, SettingsRefreshModule, etc. 3. Restart all the zlm services by using the command. zlm-config --restart ZENworks Agent (zmd) Logs: The ZENworks Agent (zmd) logs are in the zmd- files. On SLES 11 devices, the backend logs are in the messages.log zmd-backend.log file.
Page 524 524 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 525: Configuring Message Logger Settings For The Primary Server
3 Under Central Server, specify the name of the server that is responsible for purging message log entries from the database. You can also select a server by clicking . ® The ZENworks servers that are displayed here are the ones that are registered with Novell ZENworks Linux Management Server. Configuring Message Logger Settings...
Page 526: Configuring Centralized Log Settings
You can specify a DNS name or IP address as a server address. 5 Select SMTP Server Requires Authentication to authenticate to the SMTP server. 6 Specify the username to use to authenticate to the SMTP server. 526 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 527: Configuring Snmp Settings
These settings allow you to send messages as SNMP traps. The location of the MIB file is /opt/ novell/zenworks/share/loggermodule/messageloger.mib. NOTE: The MIB file should not be modified or deleted, or sending of traps does not work. 1 In the ZENworks Control Center, click Configuration.
Page 528: Configuring Message Logger Settings For A Managed Device
The default value is 1 if you are on ZENworks 7.3 Linux Management and does not change if you upgrade to ZENworks 7.3 Linux Management with IR1IR2. For a new installation of 528 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 529: Configuring System Log Settings
ZENworks 7.3 Linux Management with IR1IR2, the default value is 5. For more information, “Event Monitoring Troubleshooting Strategies” in the Novell ZENworks 7.3 Linux Management Troubleshooting Guide. The maximum number of backup files is 99. The most recent backup file is named central- , the second most recent file has the number 2 and so on.
Page 530 530 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 531: Part X Reports
Reports ® ® The following sections provide information on Novell ZENworks Linux Management reporting features: Chapter 41, “Reports Overview,” on page 533 Chapter 42, “Generating ZENworks Reports,” on page 535 Reports...
Page 532 532 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 533: Reports Overview
Reports are generated in HTML. After a report is generated, it can be printed, saved, or exported to XML or comma-separated value (CSV) format. ® When you create reports, the system stores them as objects in Novell eDirectory The following reports are provided with ZENworks Linux Management: Section 41.1, “Bundle Reports,”...
Page 534: Device Reports
Lists all devices that have been inactive for the past 90 days. Devices Registered in the Past 24 Hours Lists all devices registered in the past 24 hours. Devices Registered in the Past Week Lists all devices registered in the past week. 534 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 535: Generating Zenworks Reports
Generating ZENworks Reports This section includes the following topics: Section 42.1, “Creating a Folder,” on page 535 Section 42.2, “Creating a Report,” on page 536 Section 42.3, “Organizing Reports and Folders,” on page 539 Section 42.4, “Modifying Report Details,” on page 540 Section 42.5, “Generating Reports,”...
Page 536: Creating A Report
1 In the ZENworks Control Center, click the Reports tab. 2 Click New > Report. 3 Use the Report Information page to specify the following information: Report name: Specify a report name. 536 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 537 Folder: Specify the folder name, or browse to locate the folder in which you want to store the report. When you browse to locate a folder, the system displays the Select Folder dialog box. After you locate the desired folder, click the Select icon to select the folder, then click OK. Report description: Specify a report description.
Page 538 9 Click Next. Use the Summary page to review the report information. 10 Click Finish to create the new report, then click OK on the Results page to return to the Reports page. 538 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 539: Organizing Reports And Folders
® Novell recommends that you use the Message From This Type Object column only in conjunction with other message and device columns and filters. If you add other types of columns or filters, the message displayed in this column may be inaccurate. Known exceptions of device columns and...
Page 540: Modifying Report Details
42.4 Modifying Report Details 1 In the ZENworks Control Center, click the Reports tab. 2 Select a report. 3 To modify the settings of an existing report, complete any of the following fields or options: 540 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 541: Generating Reports
Novell recommends that you use the Message From This Type Object column only in conjunction with other message and device columns and filters. If you add other types of columns or filters, the message displayed in this column might be inaccurate.
Page 542: Exporting Reports
When you view a report in XML, the system displays the information using rows, rather than in table format. You can view this data in any application that can display XML. 542 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 543: Resetting Default Reports
42.7 Resetting Default Reports Click Reset Default Reports to reset the default reports to their original settings when you installed ZENworks. The default reports are the bundle and device reports that come with the installed software. NOTE: When new Dell devices are defined, Reset Default Reports regenerates the Dell default reports as well as adding reports for the new Dell devices.
Page 544 544 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 545: Part Xi Appendixes
Appendixes ® ® The following sections are accessed from other sections of the Novell ZENworks 7.3 Linux Management Administration Guide: Appendix A, “Command Line Utilities,” on page 547 Appendix B, “Bundle and Policy Schedules,” on page 601 Appendix C, “Naming Conventions in the ZENworks Control Center,” on page 605 Appendix D, “Imaging Utilities and Components,”...
Page 546 546 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 547: A Command Line Utilities
Command Line Utilities “zmd (8)” on page 548 “zrmservice (1)” on page 551 “zlm-debug (1)” on page 552 “zlmmirror (1)” on page 554 “zlman (1)” on page 562 “rug (1)” on page 586 Command Line Utilities...
Page 548: Zmd
(8) Name ® ® zmd - The back-end daemon for the Novell ZENworks Linux Management agent. Syntax zmd [options] Description 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.
Page 549 SLES 9, OES 1, NLD, and RHEL 3/4/5; and in etc/opt/novell/zenworks/zmd/ /etc/ on SLES 10, SLED 10, and OES 2. zmd/ Examples This program normally runs as root /etc/init.d/novell-zmd start Runs the program in the standard way. /opt/novell/zenworks/sbin/zmd /usr/sbin/zmd Runs the program directly. Command Line Utilities 549...
Page 550 Authors Copyright 2005-2010, Novell, Inc. (http://www.novell.com). All rights reserved. See Also rug (1) To report problems with this software or its documentation, visit Novell Bugzilla (http:// bugzilla.novell.com). 550 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 551: Zrmservice
® zrmservice - Configures the Novell ZENworks Remote Management agent. Syntax zrmservice [options] Description zrmservice is a command line interface to configure the Novell ZENworks Remote Management agent. Options Configuration Options --passwd Changes the Remote Management Agent password. --clrpasswd Clears the Remote Management Agent password.
Page 552: Zlm-Debug
--no-packages Do not collect package data. Package data includes all version information for packages in the ZENworks Linux Management package repository. Package data is located in the /var/opt/ directory. novell/zenworks/pkg-repo 552 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 553 --no-server Do not collect server data. Server data includes PostgreSQL and Novell eDirectory data. Authors Copyright 2005-2010, Novell, Inc. (http://www.novell.com). All rights reserved. See Also (1), zlman (1), zlmmirror (1), (8), zrmservice (1) To report problems with this software or its documentation, visit Novell Bugzilla (http:// bugzilla.novell.com).
Page 554: Zlmmirror
- Mirrors bundles and catalogs of software, in whole or in part, from remote ZENworks Linux Management, YaST Online Updates, Novell Updates, YUM, and Red Hat Network servers, to your local ZENworks Linux Management server or to a local directory. For detailed information about mirroring Dell Update Packages to your ZENworks server, see Mirroring Software in the ZENworks 7.3 Linux Management Administration Guide.
Page 555 -c,--conf=[filename] - Specifies the configuration file to use; otherwise, the default ( /etc/ ) is used. opt/novell/zenworks/zlmmirror.xml -t,--target - Restricts the listing to the specified target. catalog-list-bundles(clb) [options] [catalog] Lists the bundles available in the specified catalog. Accepts the following option flags: -c,--conf=[filename] - Specifies the configuration file to use;...
Page 556 Options --help Displays a help message. --log=[logfile] Logs messages to a file. If no log file is specified, the default (/var/opt/novell/log/ ) is used. zenworks/zlmmirror.log --verbose Displays verbose output. 556 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 557 ZLM: ZENworks 7 Linux Management DELL: Dell Update Package FTP Server RCE: Red Carpet Enterprise, or ZENworks 6.x Linux Management YaST: YaST Online Updates RHN: Red Hat Network NU: Novell Updates YUM: Yellow Dog Updater, Modified Command Line Utilities 557...
Page 558 ZENworks Server. The format looks like the following example: <SystemID> /etc/opt/novell/zenworks/zlmmirror-example-rhn-conf.xml</ SystemID> Local Server The local server is specified according to the following: <LocalServer> <Base></Base> <Type>zlm</Type> <User>Administrator></User> <Password>letmein</Password> </LocalServer> 558 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 559 Base - If the Type attribute is ZLM, leave this field empty. If the Type attribute is STATIC, enter the path to the local directory where you want the packages copied, in the following format: /path/on/filesystem Type - Type of mirroring you want to perform: ZLM: Mirrors catalogs and bundles directly to your ZENworks Linux Management server.
Page 560 This option creates an equivalent RPM package bundle in .patch.rpm the local server. Accepts only the Boolean values (true or false). By default, the option is set to false. This option is supported only for the YOU patches. 560 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 561 ZENworks Linux Management supports all the Java regular expressions. For more information on the Java regular expressions, see the Java documentation (http://java.sun.com/j2se/1.5.0/ docs/api/java/util/regex/Pattern.html). Authors Copyright 2005-2010, Novell, Inc. (http://www.novell.com). All rights reserved. See Also (1), zlman (1), (8), zlm-debug (1),...
Page 562: Zlman
(1) Name ® ® zlman - zlman is the command-line interface to Novell ZENworks Linux Management, which provides comprehensive Linux* server and workstation management. Syntax zlman [command] [options] [arguments] In general, zlman commands have both a short form and a long form. The long form is assembled in the form object-actionobject.
Page 563 Administrators Every action in zlman is governed by the access limitations of the administrator. The initial Administrator account created during the initial installation has rights to all objects. Additional administrator accounts you create are granted read-only rights by default. These accounts must be explicitly granted rights to any objects they are to manage.
Page 564 A single type flag must be specified. One of the following options can be specified to indicate the object type: -w,--workstations -s,--servers -a,--administrators -b,--bundles -p,--policies -R,--reports -r,--registrations Additionally, this command accepts the following option flags: 564 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 565 -n,--none - All rights to the specified object are revoked. -v,--view - Grants view-only access to the specified object. -m,--modify - Grants rights to modify the specified object. -c,--create - Grants rights to create new objects. admin-set-password (asp) [options] [admin name] [password] Sets an administrator’s password.
Page 566 Removes a bundle from the specified bundle group. bundle-info (bi) [options] [bundle] [version] Displays detailed information about a bundle. The version can be specified for software bundles. If now version is specified, the deployed version is shown. 566 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 567 bundle-list (bl) [options] [folder] Lists all bundles and bundle folders in the specified folder. Accepts the following option flags: -r,--recursive - Includes subfolders. -f,--filter - Displays options matching the specified filter. Wildcard characters * and ? can be used if they are enclosed in quotation marks. bundle-list-dups (bld) [options] [bundle] Lists the Dell Update Packages contained in a DUP bundle.
Page 568 Product Name - Name of the product to which this patch applies, must be one of the following: SUSE LINUX, SUSE SLES, SUSE CORE, Novell Linux Desktop, SuSE SLED. Product Version - Version of the product to which this patch applies.
Page 569 catalog-remove-bundle (crb) [options] [catalog] [bundle] [...] Removes the specified bundle from the specified catalog. Hotlist Commands This command is used to view the list of devices that have unacknowledged warnings or errors. hotlist Displays a list of devices that have unacknowledged warnings or errors. Warning or errors can be acknowledged using the commands.
Page 570 (qf) [options] [status] Flushes the queue by deleting the contents based on the status. Accepts the following values for the status argument: N - New F - Failed. S - Succeeded 570 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 571 I - In progress If you don’t specify a status, all entries in the queue are deleted. queue-list (ql) [options] [status] Lists all queue entries. If a status is provided, only queue entries matching the specified status are displayed. Accepts the following option flags: -f,--filter - Displays options matching the specified filter.
Page 572 Each rule in a rule set must evaluate to TRUE in order for the rule set to be applied. Accepts the following arguments: Attribute - Valid attributes are: Alias, AssetTag, CPU, DNS, DeviceType, GUID, HostName, IPAddress, Location, MacAddress, OS, and SubnetMask. 572 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 573 Operator - Valid string operators are: contains, starts, ends, equals. Valid integer operators are: <, <=, =, >, >=. Value - The format and contents of value are determined by the attribute. For additional information about attribute values see the Inventory section in the ZENworks Linux Management Administration Guide.
Page 574 For example, if you specify MWF, the action is executed every Monday, Wednesday, and Friday. The values for the days of a week are: Monday = M Tuesday = TU Wednesday = W 574 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 575 Thursday = TH Friday = F Saturday = SA Sunday = SU --monthly=[DD] - Specifies the day of the month when the action must be performed. If specified, the action is repeated on the specified day every month. You can specify only one day and not multiple days.
Page 576 Lists devices in the specified folder. Accepts the following option flags: -r,--recursive - Includes subfolders. -f,--filter - Displays options matching the specified filter. Wildcards * and ? can be used if they are enclosed in quotation marks. 576 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 577 server-list-bundles (slb) [options] [server] Lists bundles associated with a server. server-list-catalogs (slc) [options] [server] Lists catalogs associated with a server. server-list-policies (slp) [options] [server] Lists policies associated with a device. server-messages (sm) [options] [server] Displays a list of unacknowledged messages associated with the specified device. Accepts the following option flag: -a, --all - Displays all messages including acknowledged messages.
Page 578 Primary Role - Role of the operating system, set to Server or Workstation. Product Name - Name of the product, such as SUSE Linux Enterprise Server. Vendor - Product vendor, such as Novell or SUSE. Version - Product version, such as 10 for SUSE Linux Enterprise Server.
Page 579 --arch=[arch] - Specifies a new arch value. --pkgmgr=[package manager] - Specifies a new Package Manager value. --enable - Enables a disabled OS Target. --disable - Disables an enabled OS Target. --role=[primary role] - Specifies the primary role of this target. --product=[product name] - Specifies a new product name.
Page 580 For example, if you specify MWF, the action is executed every Monday, Wednesday, and Friday. The values for the days of a week are: Monday = M Tuesday = TU Wednesday = W 580 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 581 Thursday = TH Friday = F Saturday = SA Sunday = SU --monthly=[DD] - Specifies the day of the month the action must be performed. If specified, the action is repeated on the specified day every month. You can specify only one day and not multiple days.
Page 582 --gmt - The specified time is taken as GMT. If this is not specified, the time is the local time of the device. workstation-remove-catalog (wrc) [options] [workstation] [catalog] [...] Removes the association between a device and one or more catalogs. 582 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 583 workstation-remove-policy (wrp) [options] [workstation] [policy] [...] Removes the association between a device and the specified policies. [options] workstation-health (wh) Determines the health status of a device. Policy Commands These commands are used to modify and manage policies. Policies must be initially created using the ZENworks Control Center.
Page 584 Specifies the host name to connect to. (default: localhost) --port=[port] Specifies the port that the server is listening on. (default: 443) --cleartext Disables SSL for debugging purposes. The port must be set to the clear text port. 584 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 585 All times are converted to UTC, and used without regard to time zones. If you want to execute a transaction at a particular local time, you must create one transaction for each time zone. Authors Copyright 2005-2010, Novell, Inc. (http://www.novell.com). All rights reserved. See Also (1), zlmmirror (1),...
Page 586: Rug
(1) Name rug - The command line interface for the Novell ZENworks Linux Management Agent. Syntax rug [global-options] [command] [command-options] rug --version rug --help Description rug is the command-line interface to the ZENworks Linux Management agent. It works with the ZENworks Linux Management daemon to install, update, and remove software according to the commands you give it.
Page 587 Ellipsis (...) An ellipsis indicates that a command accepts multiple entries of the last argument type. For example, the ellipsis in the following command indicates that catalog-add-bundle accept multiple bundles: rug bundle-history [options] [search-string] [...] Option Flags Commands that do not have command-specific options (they accept only the standard option flags) do not have options listed as an argument in the command reference.
Page 588 Lists the locks that have been put in place. Locks are sorted by ID number. The bundles that are locked by the administrator on the server are not listed. bundle-remove (brm) [options] [bundlename] [...] Removes the specified bundles. Accepts the following option flags: 588 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 589 -y,--no-confirmation - Does not prompt for confirmation. -p,--prepare-only - Only prepare bundles, do not install. -f,--freshen - Freshens children. -r,--allow-removals - Removes all conflicting packages. -N,--dryrun - Tests and displays, but does not actually perform the requested actions. NOTE: The -N and -r options are not applicable for File bundles. bundle-search (bse) [options] [querystring] Searches for bundles matching the query string.
Page 590 Searches package history for the search term you specify. By default, searches package names for the search term, displaying the package version history. Use the following option flags to perform a different search: -n, --search-name - Searches by package name (default). 590 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 591 -a, --search-action - Searches by action. -d, --days-back - Maximum number of days to look back (default 30) info (if) [options] [package name] [...] Displays complete information for the specified package. Accepts the following option flags: -i, --uninstalled - Searches for uninstalled packages. -u, --unsubscribed - Searches in unsubscribed catalogs.
Page 592 -i, --installed-only - Shows only installed packages. -u, --uninstalled-only - Shows only uninstalled packages. --sort-by-name - Sorts packages by name (default). --sort-by-catalog - Sorts packages by catalog. --show-nevra - Shows the NEVRA details of the packages. 592 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 593 If the --show-nevra option is not specified, the output for this command is presented in the Status, Bundle, Name, Version, and Arch columns. These provide the details of every package that is part of the given bundle. Bundle, Name, Version, and Arch represent the bundle name, package name, package version, and package architecture respectively.
Page 594 -N, --dry-run - Tests and displays, but does not actually perform the requested actions. -i, --confirm - Prompts for confirmation. -y, --no-confirm - Does not prompt for confirmation. what-conflicts (wc) [package-dep] Lists packages that conflict with the item you specify. 594 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 595 what-provides (wp) [querystring] Displays packages that provide the library, program, or package that you specify as [querystring] what-requires (wr) [querystring] Lists packages that require the library, program, or package you specify as [querystring] Patch Management Commands patches (pch) [options] [catalog] [catalog] [...] Shows the patches in a given catalog.
Page 596 3. If you do not use the -f option, the service is not added if the ZENworks Management Daemon (ZMD) cannot resolve the service and register it. 596 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 597 -r, --rebuild - Registers a managed device with the ZENworks server by performing a point-in- time replacement of the old agent. The point-in-time replacement of the managed device lets you replace the older device object on the ZENworks Server with the current device object that is requesting the rebuild.
Page 598 Global Options The following options can be applied to any rug transaction: --normal-output Normal output (the default mode). This is somewhere between debug output and terse output. --terse Terse output. --no-abbrev No abbreviation. 598 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 599 --quiet Quiet output; prints only error messages. --debug Debug output, prints full exception traces. --version Prints the rug version and exits. Authors Copyright 2005-2010, Novell, Inc. (http://www.novell.com). All rights reserved. See Also zlman (1), (8), zrmservice (1), zlm-debug (1), zlmmirror (1)
Page 600 600 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 601: Date Specific
Bundle and Policy Schedules ® ® Using Novell ZENworks Linux Management, you can schedule when bundles are deployed to or installed on assigned devices. You can also schedule when policies are applied to assigned devices. The following scheduling options are available: Section B.1, “Date Specific,”...
Page 602: Day Of The Week Specific
Specify Black-Out Time Period dialog box. Use the Start/End date and the Start/End time options to specify the time period in which you do not want the scheduled event run. You can use this option to minimize network traffic during a certain time period. Novell ZENworks 7.3 Linux Management Administration Guide...
Page 603: Event
B.3 Event The User login option lets you trigger the event schedule when the user logs in to the device. B.4 Monthly Select the day of the month to run the scheduled event on and set other restrictions that might apply. The Monthly schedule applies to policies only;...
Page 604: Relative To Refresh
Specify Black-Out Time Period dialog box. Use the Start/End date and the Start/End time options to specify the time period in which you do not want the scheduled event run. You can use this option to minimize network traffic during a certain time period. 604 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 605: C Naming Conventions In The Zenworks Control Center
Naming Conventions in the ZENworks Control Center When you name an object in the ZENworks Control Center (folders, bundles, bundle groups, catalogs, and so forth), ensure that the name adheres to the following conventions: The name must be unique in the folder. Uppercase and lowercase letters, as well as underscores and spaces, are displayed as you first entered them, but they aren’t distinguished.
Page 606 606 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 607: D.1 Image Explorer (Imgexp.exe)
Linux Management imaging utilities, commands, and configuration settings. Section D.1, “Image Explorer (imgexp.exe),” on page 607 Section D.2, “Novell ZENworks Linux Management Imaging Agent (novell-zislnx),” on page 612 Section D.3, “Image-Safe Data Viewer and Editor (zisview and zisedit),” on page 613 Section D.4, “ZENworks Imaging Floppy Boot Disk Creator (zmediacreator.exe),”...
Page 608: Starting Image Explorer (Imgexp.exe)
2 In the left pane, browse to the partition or directory where you want to add the file or folder. 3 Click on the toolbar, browse to the file or folder, then click Add or OK. 608 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 609: Creating A Folder In An Open Image
D.1.4 Creating a Folder in an Open Image 1 Start Image Explorer. 2 In the left pane, browse to the partition or folder where you want to create the folder, click type the name of the folder, then click OK. D.1.5 Excluding a File or Folder from a File Set in the Open Image 1 Start Image Explorer.
Page 610: Viewing A File From The Open Image In Its Associated Application
4 Browse to a folder, specify a new image filename, then select a compression option: Optimize for Speed: Takes the least amount of time to compress, but creates the largest compressed image file. 610 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 611: Splitting An Image
Balanced (Recommended): Represents a compromise between compression time and image file size. This option is used by default when an image is created. Optimize for Space: Creates the smallest image file, but takes longer to compress. 5 Click Compress. Files marked for deletion in the image are removed during the compression operation. Compressing Any Image without Waiting for the File to Fully Load into Image Explorer You can set compression options to quickly compress an image file without waiting for the file to...
Page 612: Resizing A Partition In An Image
Installing the Linux Management client automatically installs the Novell ZENworks Linux Management Imaging Agent (novell-zislnx). The Imaging Agent’s purpose is to save certain device- unique data (such as IP addresses and host names) to an area on the hard disk that is safe from imaging.
Page 613: Image-Safe Data Viewer And Editor (Zisview And Zisedit)
DNS suffix DNS hostname DNS servers The novell-zislnx daemon is generally run automatically. However, if you want to run it manually, for the command line arguments that can be used with the Imaging Agent, see “Understanding Script Arguments” on page 629.
Page 614 Category Information Image-safe Data Version: The version number of the Novell ZENworks Linux Management Imaging Agent (novell-zislnx). Just Imaged Flag: If this is set to False, the Imaging Agent reads data from Linux and writes it to the image-safe data store. If this is set to True, the Imaging Agent reads data from the image-safe data store and writes it to Linux.
Page 615: Using The Image-Safe Data Viewer
Category Information Network Information DHCP: Displays whether this device uses DHCP to obtain its IP address. IP Address: Displays the static IP address that this device uses. Gateway: Displays the gateway that this device uses. Subnet Mask: Displays the subnet mask that this device uses. DNS Servers: The number of DNS nameservers used for DNS name resolution.
Page 616: Using The Image-Safe Data Editor
, enter any of the following commands at the Linux bash prompt: zisedit zisedit Commands Table D-3 Command Explanation Displays a screen showing all of the image-safe data fields. You can add zisedit or change any of the information in the fields. 616 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 617: Zenworks Imaging Floppy Boot Disk Creator (Zmediacreator.exe)
Command Explanation You can change the information for one field using this syntax, where field zisedit is any valid field name and new_information is the information you want field=new_information this field to contain. field is not case sensitive. For example, enter zisedit Mask=255.255.252.0 to enter this information in the subnet mask field.
Page 618: Imaging Configuration Parameters (Settings.txt)
Linux operating system begins to load. If you set this parameter to Yes, you are automatically prompted for each configuration setting when booting. 618 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 619 Parameter Specifies MANUALREBOOT Specifies whether you must reboot a device manually after it was booted from the imaging boot media in automatic mode. If the device was booted from the imaging boot media in manual mode, you must always reboot the device manually. If you boot a device from the imaging boot media and you let the boot process proceed in automatic mode, the ZENworks Imaging Engine starts and checks the imaging server to see if an imaging operation...
Page 620 Use to alter the behavior of automated imaging. If this variable is defined as a script (or a series of commands), then that script (or those commands) are executed instead of the usual command img auto (see /bin/imaging.s 620 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 621: Imaging Boot Parameter For Pcmcia Cards
Parameter Specifies export This feature is not supported in Novell ZENworks Linux Management. ENTERPISE_NAME=name This should be a valid Enterprise Name for an AMT device, such as entZENworks. It allows imaging utilities to access image-safe data in AMT NVRAM when AMT devices are disconnected from the ZENworks Management Zone.
Page 622 “Understanding the novell-pbserv Components” on page 622 “Configuring novell-pbserv” on page 622 Understanding the novell-pbserv Components To initiate the novell-pbserv daemon, enter the following command on the Linux command line in a terminal program: /etc/init.d/novell-pbserv Table D-5...
Page 623 By default, this is commented out. novell-proxydhcp The novell-proxydhcp daemon provides PXE devices with the information that they require to be able to connect to the ZENworks Preboot Services system. This daemon is not started automatically when installing ZENworks Linux Management.
Page 624 By default, this parameter is commented out. NovellPolicyEngine = The IP address of the server where a Novell Preboot policy engine is running. 10.0.0.1 Most often, this is a ZENworks imaging daemon. If no value is specified, the Proxy DHCP assumes that the daemon is running on the same server.
Page 625 “Understanding the novell-tftp Components” on page 625 “Configuring novell-tftp” on page 625 Understanding the novell-tftp Components To initiate the novell-tftp daemon, enter the following command (listed under Script Location) on the Linux command line in a terminal program: /etc/init.d/novell-tftp Table D-9...
Page 626 1428. Older TFTP clients might be restricted to 512 bytes, the original transfer block size before the adoption of RFC 2348. The Novell TFTP server is compatible with these clients. By default, this parameter is commented out.
Page 627 RFC 2349 - TFTP Timeout Interval and Transfer Size Options novell-zmgprebootpolicy The novell-zmgprebootpolicy daemon allows PXE devices to query the ZENworks Linux Management system for work to do and for Preboot Menu policies. This daemon is started automatically when installing ZENworks Linux Management, or when rebooting the server.
Page 628 Understanding the novell-zmgprebootpolicy Components To initiate the novell-zmgprebootpolicy daemon, enter the following command (listed under Script Location) on the Linux command line in a terminal program: /etc/init.d/novell-zmgprebootpolicy Table D-11 lists the arguments for this command, the executable it starts, and the configuration file it...
Page 629 However, this daemon does not automatically start when the server reboots. (See install below.) start setjustimagedflag For novell-zislnx only, it sets the Just Imaged flag so that a device can be imaged using its existing Image Safe Data. stop Stops the daemon. restart Stops and restarts the daemon if it is already running.
Page 630: Viewing Information About Imaging Requests
Novell ZENworks Imaging Service running 10211 install For novell-proxydhcp only, causes the daemon to be automatically loaded when the server boots. D.7.2 Viewing Information About Imaging Requests After the imaging server has started, you can view information about the status and results of the imaging requests that it has received from imaging clients.
Page 631: E Zenworks Imaging Engine Commands
ZENworks Imaging Engine Commands After booting a device from an imaging boot media, you can use the img command at the Linux ® bash prompt or the ZENworks Imaging Engine menu to do any of the following: Take an image of the device’s hard disks Put down an image on the device’s hard disks View or manipulate the device’s hard disk partitions View the device’s hardware configuration or image-safe data...
Page 632: Automatic Mode (Img Auto)
ZENworks Imaging Engine to those servers to complete those tasks. After the ZENworks Imaging Engine has completed its work, it communicates the results to the original imaging server, and the results are logged on that server. 632 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 633: Make Mode (Img Make)
For information on configuring the settings that control what happens in this mode, see Section 29.4, “Configuring Preboot Services Defaults,” on page 379. E.3 Make Mode (img make) Use the Make mode to take an image of the device and store it in a specified location. Normally, all partitions on the local hard disks are included in the image, but there are some exceptions noted in Table E-1 on page 633.
Page 634: Make To Proxy (Img Makep)
“make to proxy” parameter: makep img makep address filepath [comp=comp level] [xpartition] Commands makep Commands Table E-3 Parameter Specifies address The IP address or DNS name of the imaging server to store the image on. 634 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 635: Restore Mode (Img Restore)
Parameter Specifies filepath The image filename, including a extension (case sensitive) and the complete .zmg path in UNC style. The directories in the path must exist. If the file already exists, the imaging server won’t overwrite it unless you enable this behavior in the ZENworks Control Center.
Page 636: Restore From Local (Img Restorel)
The number of the image file set to put down. Valid values are 1 through 10. For information on creating file sets of an image, see Section 28.5.2, “Creating, Installing, and Restoring Standard Images,” on page 346. If you omit this parameter, file set 1 is used. 636 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 637 Parameter Specifies apartition:ppartition A mapping between a partition in the image archive (apartition) and a target physical partition on the local machine (ppartition). Use this parameter to selectively restore a specific part of the image to a specific local partition. IMPORTANT: If you use this parameter, none of the existing local partitions are removed, and only the target local partition is updated.
Page 638: Restore From Proxy (Img Restorep)
In doing so, you can apply multiple parts of the image to a single local partition, but you can’t apply the same part of an image to multiple local partitions in a single operation. 638 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 639: Session (Multicast) Mode (Img Session)
Examples restorep Examples Table E-8 Example Explanation img restorep 137.65.95.127 // Removes all existing local partitions, retrieves the image xyz_server/sys/imgs/dellnt.zmg from sys/imgs/dellnt.zmg xyz_server , and puts down the partitions and contents of that image on the available local writable devices (assuming there is sufficient local space and that 137.65.95.127 is the IP address of xyz_server...
Page 640 Manually start multicast, providing the required information, then selecting Yes. 640 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 641: Partition Mode (Img Part)
Example Explanation Starts a multicast session named and designates img session mcast01 m mcast01 this device as the master. Each successive device that issues before the imaging img session mcast01 begins joins the session as a participant. Imaging doesn’t start until the master user presses img session mcast01 master Starts a multicast session named mcast01...
Page 642: Using The Bash Prompt
E.7 ZENworks Partition Mode (img zenPartition) Use the ZENPartition mode to enable, disable, or remove the installed ZENworks partition. 1 Do one of the following: From the bash prompt, enter the following: 642 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 643: Dump Mode (Img Dump)
img zenPartition operation where operation is enable, disable, or remove. Enter to display the ZENworks Imaging Engine menu, click Partitioning, then click one of the following: Disable ZENworks partition Enable ZENworks partition Remove ZENworks partition 2 Enter to make this change effective. lilo.s IMPORTANT: If you remove an installed ZENworks partition, you must immediately restore a base image with a valid non-LILO MBR (Master Boot Record).
Page 644 This data is saved by the Novell ZENworks Linux Management Imaging Agent (novell-zislnx) during each device’s session to ensure that it can be restored after the device is reimaged. If the device is new and doesn’t have an operating system yet, an initial set of data is supplied from the default configuration for the ZENworks Management Zone, such as IP addresses.
Page 645 Examples Examples Table E-12 Example Explanation img info Lists the detected hardware devices on the device. Lists the Linux Management image-safe data currently stored on the device img info zisd and the last base image that was put down. ZENworks Imaging Engine Commands 645...
Page 646 646 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 647: F Updating Zenworks Imaging Resource Files
Updating ZENworks Imaging Resource Files ® ® In Novell ZENworks 7 Linux Management, you can manually update ZENworks imaging resource files. The following sections provide concepts on how the boot process works with ZENworks imaging, and instructions for updating imaging resource files: Section F.1, “The Linux Distribution for Imaging,”...
Page 648: Understanding Device Boot Processes In A Zenworks Imaging Environment
The file system is located on an imaging CD as the file . For root /boot/root PXE booting, the file system is stored on the ZENworks imaging server as root /srv/tftp/boot/ root 648 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 649: Zenworks.s
Linuxrc attempts to locate and load the file, either on the root of the imaging CD, or settings.txt on the ZENworks imaging server in the directory. From , linuxrc /srv/tftp/boot settings.txt reads and processes any parameters that pertain to itself, then copies to the root ( settings.txt ) of the file system.
Page 650: Command Line Parameters And Variables
You can use the following methods to update imaging resource files: The easiest method is to edit the file, which is located on the root of the settings.txt imaging CD or in on the ZENworks Imaging Server for PXE booting. /srv/tftp/boot 650 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 651: Adding Files To An Imaging Boot Cd
/srv/tftp Server for PXE booting. This method is only available for Linux Imaging Servers, because the configuration files are provided by Novell’s version of PXE. You can modify files in the file systems, but you need a Linux environment for...
Page 652 If the kernel version has changed with the newer resource files from Novell, previously added drivers must be updated either by obtaining a new version from the manufacturer or recompiling the driver using the correct Linux kernel version source.
Page 653 9 To zip the new file, enter: initrd gzip -v9c initrd > initrd.gz 10 To rename back to , enter: initrd.gz initrd mv initrd.gz initrd 11 To copy the file back: For PXE, copy the updated file to the directory on the PXE server. initrd /tftp/boot For the CD, copy the updated...
Page 654: Using The Driverupdate File Method
F.4.3 Using the Driverupdate File Method Another way to customize the Novell imaging distribution is to utilize the driver update mechanism that is built into all SUSE distributions. This entails modifying a file named that is driverupdate located in the...
Page 655 The contents of the file should contain lines similar to those listed below. You dud.config should maintain the keywords by supplying your own data. However, you can use the listed values: UpdateName: ZENworks 10 Patch 1 UpdateID: a37f92556e4dd99e UpdatePriority: 100 file should be an executable script that contains the following lines: adddir.s echo "Processing: adddir.s"...
Page 656: Adding Or Updating Lan Drivers
-r However, you might need to modify the results from the command to get your kernel uname versions to match. For more information, see Section F.6, “Using Uname,” on page 658. 656 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 657 -r This displays the kernel version of the Imaging distro. 2 From the Novell Downloads Web site (http://download.novell.com/patch/finder/ ?familyId=7261&productId=8162&yearValue=2009&keywords=kernel), download the kernel source RPM for the kernel version obtained in Step The kernel source RPM filename is in the following format: kernel-source-kernel_version.i586.rpm...
Page 658: Loading Drivers With Parameters
/bin/orig mv /bin/uname /bin/orig/uname 4 Use a Linux editor (such as vi) to create the file that contains the following lines: /bin/uname 658 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 659: Variables And Parameters
#!/bin/sh #uname if [ $KRNLVERSION"a" = "a" ] ; then if [ $(/bin/orig/uname -r) = "2.6.13-15-smp" ] ; then export KRNLVERSION=2.6.13-15-smp else export KRNLVERSION=2.4.31 if [ $1"a" = "-ra" ] ; then echo $KRNLVERSION else /bin/orig/uname $* IMPORTANT: Replace the strings “2.6.13-15-smp” with the version you found in Step 1. 5 To make the new command script executable, enter: uname...
Page 660: Linuxrc Parameters Specified In Settings.txt
= Define which network device to configure. F.7.3 Image Engine Variables Image Engine Variables Table F-4 Variable Definition DEVELOPER_LOG “A” creates a verbose debug file. imglog ZENIMGLOG “A” creates a less verbose imglog debug file. 660 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 661: Troubleshooting Linux Driver Problems
For example, hwinfo hwinfo -pci | less If you need to contact Novell Support for help, you should capture the output from hwinfo - to a file for their use. You can gather the most information with this command: hwinfo –pci –log /logfilename...
Page 662 662 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 663: G Upgrading The Dell Dtk
DTK become available, you can upgrade to a newer version. To obtain the current Dell DTK build from Dell: 1 Make sure the novell-proxydhcp daemon is running on a server in your network. This service must be available so that the device’s PXE can access files from the ZENworks server, such as the Preboot Services Menu file and the Dell DTK (Maintenance Mode) files.
Page 664 5, when the bash (#) prompt is displayed, view the content of the file: /BUILD If the build number has not incremented, either it really isn’t an update, or the copy operations failed. 664 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 665: H Supported Ethernet Cards
Supported Ethernet Cards ® ® Novell ZENworks Linux Management provides the Ethernet card drivers contained in the Linux kernel (2.6) that ships with ZENworks 7. To determine which Linux kernel you are using, enter at the bash prompt. uname -r If your device or laptop computer uses a different card that is not supported, you must supply your own Ethernet driver.
Page 666 666 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 667: Using A Specific Network Card For Devices Running Dual Nics
Using a Specific Network Card for Devices Running Dual NICs You can chose to use a specific network card for a device running dual NICs by using one of the following ways: Modify the or the file (or both) by adding /srv/tftp/z_auto.cfg /srv/tftp/z_maint.cfg the following line at the end of the Append command:...
Page 668 AutoYaST bundle. For more information on how to create and configure the AutoYaST bundle, see Section 30.3.1, “Configuring an AutoYaST Bundle,” on page 440. This eliminates the need to select a NIC’s IP address manually. 668 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 669: J Establishing Ssh Tunneling
Establishing SSH Tunneling If you are using Remote Management over a network that is not secure, the data between the Remote Management Viewer running on the management console and the Remote Management Agent on the managed device is unencrypted and could be viewed by someone with access to the intervening network.
Page 670: Ssh Tunneling Between A Windows Management Console And A Linux Managed Device
The second argument is the main non-option parameter to SSH, which tells it to connect to the device that runs the SSH daemon. 670 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 671: Compression
2 In the PuTTY Security Alert dialog box, verify that the key matches with that of the “gateway” device, then click Yes. 3 To establish the SSH tunnel between “viewer” and “gateway,” you need to require authentication to “gateway.” Specify a valid username and password of the “gateway” device in the PuTTY dialog box, then click Yes.
Page 672 672 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 673: K License Agreement For Libacl And Libgconf
License Agreement for libacl and libgconf The following is the license agreement for the libacl and libgconf library that is used in the ® ZENworks 7 Linux Management Policy Handler/Enforcer software: K.1 Library GNU Public License This License Agreement applies to any software library or other program which contains a notice placed by the copyright holder or other authorized party saying it may be distributed under the terms of this Lesser General Public License (also called “this License”).
Page 674 Library by being compiled or linked with it, is called a “work that uses the Library.” Such a work, in isolation, is not a derivative work of the Library, and therefore falls outside the scope of this License. 674 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 675 However, linking a “work that uses the Library” with the Library creates an executable that is a derivative of the Library (because it contains portions of the Library), rather than a “work that uses the library.” The executable is therefore covered by this License. Section 6 states terms for distribution of such executables.
Page 676 If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the section is intended to apply, and the section as a whole is intended to apply in other circumstances. 676 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 677 It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free software distribution system which is implemented by public license practices.
Page 678 678 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 679: L Documentation Updates
Documentation Updates This section contains information on documentation content changes that were made in this Administration Guide after the initial release of Novell® ZENworks® 7.3 Linux Management. The information can help you to keep current on updates to the documentation.
Page 680: Appendix
Added the following important note in this chapter: Mirroring YaST online updates for a SLES 9 platform with ia64, ppc, or s390 architectures is not supported in ZENworks 7.2 Linux Management or later. 680 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 681: Appendix
L.2.3 Appendix The following changes were made in this section: Loation Change rug (1) (page 586) Added the list of options in the service-add (sa) [options] [uri] command. L.3 November 4, 2009 Updates were made to the following sections. The changes are explained below. Section L.3.1, “ZENworks System Management,”...
Page 682: Policy Management
Section L.5.4, “Appendix,” on page 683 L.5.1 ZENworks System Management The following changes were made in this section: Loation Change Section 3.3, “Accessing the ZENworks Control Updated this section. Center through Novell iManager,” on page 42 682 Novell ZENworks 7.3 Linux Management Administration Guide...
Page 683: Policy Management
Loation Change Section 9.1.3, “Deleting the Dangling Objects from Added the following note: ZENworks Object Store,” on page 87 NOTE: If you have installed ZENworks 7.3 Linux Management HP1, you must replace the <TreeName></TreeName> tag with <ZoneName></ZoneName> Section 9.2.4, “Restoring the ZENworks Data Updated this section.
Page 684 684 Novell ZENworks 7.3 Linux Management Administration Guide...

This manual is also suitable for:

Zenworks linux management 7.3 ir2

Novell ZENWORKS LINUX MANAGEMENT 7.3 IR2 - ADMINISTRATION GUIDE 02-12-2010 Administration Manual

About this Guide

Part I Understanding Zenworks Linux Management

1 Quick Tutorial on Basic Zenworks Linux Management Features

2 Using Zenworks Linux Management with Dell Poweredge Servers

Part II Zenworks System Management

3 Zenworks Control Center

4 Command Line Administration Utilities

5 Zenworks Server

6 Zenworks Agent

7 Configuring Management Zone Settings

8 Zenworks Administrator Accounts

9 Zenworks Object Store and Data Store Maintenance

Part III Device Registration

10 Registration Overview

11 Registering Devices

12 Managing Registration Keys and Rules

13 Unregistering and Reregistering Devices

Part IV Policy Management

14 Policy Management Overview

15 Understanding Policies

16 Creating Policies

17 Managing Policies

Part V Package and Content Management

18 Package and Content Management Overview

19 Understanding RPM Packages

20 Using RPM and File Bundles

21 Understanding the Package and Content Management Features Available on a Managed Device

22 Using Catalogs

23 Using Dell Update Package Bundles

24 Replicating Content in the Zenworks Management Zone

25 Mirroring Software

26 Creating RPM Packages from Tarballs

Part VI Preboot Services

27 Preboot Services Overview

28 Understanding Preboot Services in Zenworks Linux Management

Quick Links

Related Manuals for Novell ZENWORKS LINUX MANAGEMENT 7.3 IR2 - ADMINISTRATION GUIDE 02-12-2010

Summary of Contents for Novell ZENWORKS LINUX MANAGEMENT 7.3 IR2 - ADMINISTRATION GUIDE 02-12-2010