Novell ZENWORKS LINUX MANAGEMENT 7.2 IR2 - ADMINISTRATION GUIDE 09-25-2008 Administration Manual

Table of Contents

Quick Links

Download this manual

AUTHORIZED DOCUMENTATION

Administration Guide

Novell

ZENworks

Linux Management

7.2 IR2

September 25, 2008

www.novell.com

Novell ZENworks 7.2 Linux Management Administration Guide

Table of Contents

Troubleshooting

Need help?

Do you have a question about the ZENWORKS LINUX MANAGEMENT 7.2 IR2 - ADMINISTRATION GUIDE 09-25-2008 and is the answer not in the manual?

Questions and answers

Summary of Contents for Novell ZENWORKS LINUX MANAGEMENT 7.2 IR2 - ADMINISTRATION GUIDE 09-25-2008

Page 1 AUTHORIZED DOCUMENTATION Administration Guide Novell ® ZENworks Linux Management ® 7.2 IR2 September 25, 2008 www.novell.com Novell ZENworks 7.2 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 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 ........72 Viewing Default Target Platforms and Configuring Custom Target Platforms ... . . 73 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 7 Configuring the ZENworks Management Daemon (zmd) Settings..... . 74 7.11 Integrating Novell Customer Center with ZENworks Linux Management ....75 7.12 Configuring the ZENworks Server Preferences .
Page 8 Novell Linux Desktop Policy ........
Page 9 17.8 Editing System Requirements ..........194 17.9 Refreshing Policies .
Page 10 Mirroring Dell Update Packages to Your ZENworks Server......305 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 11 25.6 Mirroring Bundles Between ZENworks 7.2 Linux Management Servers Located in Different Management Zones ............309 25.7 Deploying Red Hat Network Updates .
Page 12 Image File Operations ............460 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 13 31.7.1 Compressing an Image File ......... . . 460 31.7.2 Splitting an Image .
Page 14 Configuring System Log Settings ........517 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 15 Part X Reports 41 Reports Overview 41.1 Bundle Reports ............521 41.2 Dell Reports .
Page 16 Resizing a Partition in an Image ........596 Novell ZENworks Linux Management Imaging Agent (novell-zislnx) ....596 Image-Safe Data Viewer and Editor (zisview and zisedit) .
Page 17 F.5.2 Building Drivers ........... . 643 F.5.3 Loading Drivers with Parameters.
Page 18 Package and Content Management ........673 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 19: About This Guide
ZENworks 7.2 Linux Management is supported by other documentation (in both PDF and HTML formats) that you can use to learn about and implement the product: Novell ZENworks 7.2 Linux Management Installation Guide Novell ZENworks 7.2 Linux Management Troubleshooting Guide In addition, the other capabilities included in the ZENworks 7 suite have extensive documentation for your use.
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.2 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.2 Linux Management Administration Guide...
Page 25: Folders Vs. Groups
During installation of the ZENworks Agent on a device, the registration key must be input manually or through a response file (see “Automating Installation of the ZENworks Agent” in the Novell ZENworks 7.2 Linux Management Installation Guide). When A Quick Tutorial on Basic ZENworks Linux Management Features...
Page 26: Setting Up Zenworks Administrator Accounts
For more detailed information about registering devices, see Part III, “Device Registration,” on page 1.3 Setting Up ZENworks Administrator Accounts During installation, a default Administrator account is created. This account provides rights to administer all of your ZENworks system. Novell ZENworks 7.2 Linux Management Administration Guide...
Page 27: Delivering Software Packages
You can create additional administrator accounts that provide full access to your ZENworks system. You can also create accounts that limit administrative rights to specific folders (device folders, policy folders, bundle folders, and report folders). To limit administrator rights, you assign an account rights at the folder level. The root folders are / Bundles, /Devices, /Policies, and /Reports.
Page 28: Bundles
1.5 Delivering Content Using File Bundles A File bundle lets you create a bundle and distribute compressed files of the type tar.gz and tar.bz2. For example, you can include configuration files or data files in file bundles. Novell ZENworks 7.2 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
4 Click the Inventory tab. You can also roll up device inventory to a ZENworks 7 inventory database. For more information about collecting software and hardware inventory, see Part VII, “Hardware and Software Inventory,” on page 469. Novell ZENworks 7.2 Linux Management Administration Guide...
Page 31: Managing Remote Devices
The remote session appears. If you receive an error message stating that additional plug-ins are required, see “Administration Workstation Requirements” in the Novell ZENworks 7.2 Linux Management Installation Guide. For more information about managing remote devices, see “Remote Management” on page 483.
Page 32: Hot List
The ZENworks Server can log messages (the ones that appear in the server's System Event Log) to a file on the server's local disk. For more information about message logs, see Part IX, “Event Monitoring,” on page 497. Novell ZENworks 7.2 Linux Management Administration Guide...
Page 33: Generating Reports
1.11 Generating Reports You can generate reports to display bundle and device information, such as the bundle delivery information for each device or the devices registered in the last 24 hours. The ZENworks Control Center provides several predefined reports and lets you create new reports. You can export the reports to XML, CVS, or HTML formats.
Page 34 Novell ZENworks 7.2 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.2 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 527. Novell ZENworks 7.2 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.2 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
3.3 Accessing the ZENworks Control Center through Novell iManager ZENworks Linux Management includes a Novell plug-in module (.npm) that you can use to access the ZENworks Control Center from Novell iManager, which is a management console used by a number of other Novell products.
Page 43: Changing The Debug Settings Of Zenworks Control Center
Control Center To change the debug settings of ZENworks Control Center: 1 Open the /var/opt/novell/zenworks/www/tomcat/base/webapps/ zenworks/WEB-INF/config.xml file in a text editor. 2 Make sure that the value of debug.enabled is set to True. (By default, the option is set to True.)
Page 44 Novell ZENworks 7.2 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 537). Novell ZENworks 7.2 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
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
Section 5.2.3, “Package Administration,” on page 50 5.2.1 Package Repository Location The package repository is the /var/opt/novell/zenworks/pkg-repo directory on the ZENworks Server. When you add an RPM package to a bundle, the package is automatically uploaded to the package repository. When you mirror Dell Update Packages, the packages are automatically bundled and uploaded to the package repository.
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.2 Linux Management Administration Guide...
Page 51: Uninstalling A Secondary Zenworks Server 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.2 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 /opt/novell/zenworks/bin and running zen-updater with root privileges. To run it as a daemon, run zen-updater &. The Software Updater icon appears in the notification area (GNOME) or the system tray (KDE) of your panel as an icon depicting a globe, which changes to an orange circle with an exclamation point in it when updates are available.
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.2 Linux Management Administration Guide...
Page 59 Software Updater configuration screen, that service will appear in the Software Installer configuration and vice versa. To add a package source: 1 Launch the Software Installer by navigating to /opt/novell/zenworks/bin and running zen-installer with root privileges. 2 Click Configure.
Page 60 The source is listed in the Services tab and is ready to be used and checked for available packages. Selecting Installation Catalogs You can configure the Software Installer to accept various catalogs: 1 Launch the Software Installer by navigating to /opt/novell/zenworks/bin and running zen-installer with root privileges. 2 Click Configure. 3 Click the Catalogs tab.
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/ novell/zenworks/bin directory. 1 Launch Software Remover by navigating to /opt/novell/zenworks/bin and running zen-remover with root privileges. ZENworks Agent...
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.2 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 rug get. For more information, see rug (1) (page 571). 6.3.5 Editing System Preferences 1 Right-click the Software Updater icon, then click Configure. If the Software Updater icon is not in the system tray, you need to launch the program.
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.2 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.URL for the proxy server. NOTE: If you modify the system proxy, you must set the proxy-url with the system proxy URL for the device to use the system proxy.
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: Configuring Management Zone Settings
Section 7.9, “Viewing Default Target Platforms and Configuring Custom Target Platforms,” on page 73 Section 7.10, “Configuring the ZENworks Management Daemon (zmd) Settings,” on page 74 Section 7.11, “Integrating Novell Customer Center with ZENworks Linux Management,” on page 75 Section 7.12, “Configuring the ZENworks Server Preferences,” on page 76 Section 7.13, “Understanding the StoreFileDeps Preference,”...
Page 68: Creating System Variables
In this scenario, you have a SLES 9 and a SLES 10 managed device. Both devices have a common file, deviceid. On SLES 9, the file is located at /etc/opt/novell/zenworks/zmd, and on SLES 10 it is located at /etc/zmd. Assume that you want to place a copy of deviceid in the /tmp directory on both devices by using the Remote Execute policy.
Page 69 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 70: Configuring The Device Refresh Schedule
Configure the settings on this page to roll up the hardware inventory information from a ZENworks 7 Linux Management database to a ZENworks 7 or later Server Management or Desktop Management Inventory server: 1 In the ZENworks Control Center, click the Configuration tab. Novell ZENworks 7.2 Linux Management Administration Guide...
Page 71: Configuring Local Device Logging
For SUSE Linux Enterprise Server 10 (SLES 10) and SUSE Linux Enterprise Desktop (SLED 10) devices, the path is /var/log. For all other devices, it is / var/opt/novell/log/zenworks. Log message to a local file if severity is: Specify filtering criteria based on severity.
Page 72: Configuring Preboot Services
ZENworks Server to all secondary ZENworks Servers in the Management Zone. During replication of a bundle, only new packages and updates to existing packages are sent. For detailed information, see Section 24.2, “Configuring a Content Replication Schedule,” on page 288. Novell ZENworks 7.2 Linux Management Administration Guide...
Page 73: Viewing Default Target Platforms And Configuring Custom Target Platforms
7.9 Viewing Default Target Platforms and Configuring Custom Target Platforms This Target Platforms page lists the server and workstation platforms that ZENworks Linux Management supports as managed devices. You can also define additional custom platforms by adding an entry to the Custom Target Platforms list. 1 In the ZENworks Control Center, click the Configuration tab.
Page 74: Configuring The Zenworks Management Daemon (Zmd) Settings
After you click OK, if displays next to the Value box, the setting you typed is either too small/large or you typed an invalid setting. Description: Displays the description of the selected setting. Novell ZENworks 7.2 Linux Management Administration Guide...
Page 75: 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 76: Configuring The Zenworks Server Preferences
This enables the server to periodically transmit information about itself and its managed devices to Novell Customer Center. In Update Interval (Hrs), specify how often the server must send information to Novell Customer Center. By default, the interval is 3 hours.
Page 77: Understanding The Storefiledeps Preference
4 Configure the following settings: In the Preference drop-down list, select the preference whose value you want to change. In the Value drop-down list, select the desired value for the selected preference. 5 Click OK. NOTE: The Apply and Reset buttons are not available for the ZENworks Server Settings page. 7.13 Understanding the StoreFileDeps Preference StoreFileDeps is a preference on the ZENworks Linux Management server.
Page 78 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 79: 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 80: Modifying Account Rights
You assign rights at the folder level. The root folders are /Bundles, /Devices, / Policies, and /Reports. Rights assigned at a root folder are effective in all subfolders (for example, /Bundles/Workstations) unless specifically overridden at the subfolder level. Novell ZENworks 7.2 Linux Management Administration Guide...
Page 81 For example, if you want the administrator to be able to view bundles that are located in the / Bundles folder and create, delete, or modify bundles in the /Bundles/Workstations folder, you would assign the administrator View rights to the /Bundles folder and All rights to the /Bundles/Workstation folder.
Page 82 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 83: Zenworks Object Store And Data Store Maintenance
Section 9.1.3, “Deleting the Dangling Objects from ZENworks Object Store,” on page 84 9.1.1 Backing Up the ZENworks Object Store You use zlm_ndsbackup.sh, located in /opt/novell/zenworks/sbin, to back up the Object Store. 1 Make sure you are logged in as root to the ZENworks Server.
Page 84: Restoring The Zenworks Object Store
® Backup creates a directory with the current date in /var/opt/novell/zenworks/ backup/nds. The backup file is saved in this directory. The log information about the backup operation is saved to /var/opt/novell/log/ zenworks/ndsbackup.log. 9.1.2 Restoring the ZENworks Object Store If necessary, you can restore the ZENworks Object Store from a backup you created. You use zlm_ndsrestore.sh, located in /opt/novell/zenworks/sbin, to restore the Object...
Page 85: Maintaining The Zenworks Data Store On Postgresql
</ZLMedirectoryCleanup> The ZENworks server uses the information in the XML file to establish connection with eDirectory. 3 At the server console prompt, go to /opt/novell/zenworks/sbin and execute the following command: zlm_edirCleanup complete_path_of_the_xml_file Where complete_path_of_the_xml_file is completed path of the XML file created in...
Page 86: Displaying The Password For The Default Postgresql Database
Section 9.2.5, “Optimizing the Server Database,” on page 88 Section 9.2.6, “Restarting Novell Zenworks Server Services After Restarting the Database,” on page 89 9.2.1 Displaying the Password for the Default PostgreSQL Database The password for the default ZENworks PostgreSQL database is stored as plaintext on your ZENworks Primary Server.
Page 87: 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 88: Optimizing The Server Database
/etc/opt/novell/zenworks/hibernate.cfg.xml that is used for authenticating the PostgreSQL database. The log information about the restore operation is saved in the file /var/opt/novell/ log/zenworks/dbrestore.log. 8 After the restore is complete, you need to ensure that the Data Store is synchronized with the Object Store.
Page 89: 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 90: Backup And Recovery Solutions
ORACLE_HOME: The directory where the Oracle software is installed. For example: ORACLE_HOME=/home/oracle/product/9ir2 CLASSPATH: The paths to the libraries installed by Oracle. For example: CLASSPATH=$CLASSPATH:/oracle/opt/oracle/product/9ir2/JRE:/ oracle/opt/oracle/product/9ir2/jlib:/oracle/opt/oracle/ product/9ir2/rdbms/jlib:/oracle/opt/oracle/product/9ir2/ network/jlib PATH: The Oracle installation’s bin directory. For example: PATH=$PATH:/home/oracle/product/9ir2/bin Novell ZENworks 7.2 Linux Management Administration Guide...
Page 91: Connecting To The Database
9.3.3 Connecting to the Database You can use either of the following methods to connect to the Oracle database being used for the Data Store: Start RMAN at the operating system command line without connecting to a database, by issuing the RMAN command without any connection options: $ rman RMAN>...
Page 92: Recovering The Database
1 Use the following sequence of commands to perform a complete recovery of the database: RMAN> connect target / RMAN> run { 2> startup mount; 3> restore database; 4> recover database; 5> alter database open; 6> } Novell ZENworks 7.2 Linux Management Administration Guide...
Page 93 This results in all data files being restored and then recovered. RMAN applies archive logs as necessary until the recovery is complete. 2 After the restore is complete, you need to ensure that the Data Store is synchronized with the Object Store.
Page 94: Shutting Down The Database
3 Enter the password to authenticate to the Object Store. The GUIDs and names of the devices and bundles that are in the Data Store but not in the Object Store are logged in the /var/opt/novell/log/zenworks/dbsync-message.log file. 9.5 Cleaning Up the ZENworks Database The ZENworks Database Clean-Up utility of ZENworks 7.2 Linux Management IR2 helps you to...
Page 95: 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 97 Chapter 11, “Registering Devices,” on page 99 Chapter 12, “Managing Registration Keys and Rules,” on page 101 Chapter 13, “Unregistering and Reregistering Devices,”...
Page 96 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 97: 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 98 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 99: 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.2 Linux Management Installation Guide. 11.2 Registering a Device after Installing the ZENworks Agent...
Page 100: 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 initial-configuration file is as follows: [https://10.0.0.0] type=zenworks [https://update.novell.com/data] type=rce [http://www2.ati.com/suse] type=YUM key=yum_service 100 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 101: 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 102: 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. 102 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 103 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 rug sa command, this is the name the device provides to be assigned this registration. Any device that presents this name is given the assignments associated with this registration.
Page 104 6 Click Next to display the Group Membership page. 104 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 105: 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 106: 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. 106 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 107: 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 108 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. 108 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 109 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 110 8 Click Next to display the Group Membership page. 110 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 111: 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 112 For example, if you specified the /Devices/Workstations folder, you can only choose workstation groups. To remove a group, select the box next to the group's name, then click Remove. 6 Click Apply. 112 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 113: Renaming Or Copying Registration Rules
12.2.3 Renaming or Copying Registration Rules 1 In the ZENworks Control Center, click the Configuration tab. 2 In the Default Registration Rules section, click Advanced. 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.
Page 114 589. 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. 114 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 115: 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 115 Section 13.2, “Unregistering Devices,”...
Page 116: 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. 116 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 117: 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 119 Chapter 15, “Understanding Policies,” on page 121 Chapter 16, “Creating Policies,” on page 127 Chapter 17, “Managing Policies,”...
Page 118 118 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 119: 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 120: Managing Policies
Section 16.8, “Text File Policy,” on page 171. 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 121: 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 122: Assignments
Section 16.4, “Generic GNOME Policy,” on page 146. 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 123: Groups
Event Select the event that 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 124: 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 125 Icon Description The policy is not effective and will not be enforced. 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 125...
Page 126 126 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 127: Creating Policies
Section 16.3, “Firefox Policy,” on page 139 Section 16.4, “Generic GNOME Policy,” on page 146 Section 16.5, “Novell Linux Desktop Policy,” on page 151 Section 16.6, “Remote Execute Policy,” on page 159 Section 16.7, “SUSE Linux Enterprise Desktop Policy,” on page 164 Section 16.8, “Text File Policy,”...
Page 128 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. 128 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 129 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 130 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. 130 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 131 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 132 The settings you configure on this page determine when the policy is applied to devices. Section 15.3, “Schedules,” on page 122 for information about the available schedules and their options. 16 Click Next to display the Policy Groups page. 132 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 133: 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 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 Evolution Lockdown Settings page. 134 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 135 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 136 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. 136 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 137 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 138 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. 138 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 139: 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 140 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. To configure the Firefox policy: 1 In the ZENworks Control Center, click the Policies tab.
Page 141 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 142 . 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. 142 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 143 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 144 10 Specify the minimum system requirements that must be satisfied for the Firefox Web browser policy settings to be effective. The Apply policy on Novell Linux Desktop with Firefox version field displays the minimum version of Firefox required for all policy settings to be effective. Firefox 1.0.4 is the minimum required version.
Page 145 13 Assign the policy to the devices. 13a Click Add to browse for and select the appropriate Server or Workstation objects. You can also select Folder or Group objects. 13b 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 146: Generic Gnome Policy
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. 146 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 147 For more information, see Appendix C, “Naming Conventions in the ZENworks Control Center,” on page 589. Folder: (Required) Type the name or browse to the folder that this policy will be created in. Folders display in the ZENworks Control Center. Description: Provide a short description of the policy.
Page 148 Gconf settings by adding and deleting keys on the Gconf Tree, then click Next. For detailed information about defining your own Gconf settings, click the button on the Built Gconf Tree page. 148 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 149 9 Click Next to display the default system requirements for Generic GNOME Policy page. 10 Specify the minimum system requirements for Generic GNOME policy settings to be effective. The value you specify in the Apply policy on devices with distribution field indicates the distribution and minimum version that is required for the policy settings to be effective.
Page 150 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. 150 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 151: Novell Linux Desktop Policy
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 152 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 Novell Linux Desktop Lockdown Settings page. 152 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 153 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. Creating Policies 153...
Page 154 (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 155 (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 156 Solid to have the background image uniform across the desktop. Select Vertical to have the image become darker as you go up, and select Horizontal to have the image become darker as you go from left to right. 156 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 157 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 158 The settings you configure on this page determine when the policy is applied to devices. Section 15.3, “Schedules,” on page 122 for information about the available schedules and their options. 20 Click Next to display the Policy Groups page. 158 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 159: Remote Execute Policy
21 (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 160 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. 160 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 161 6 Select the desired options: Executable type: Select an executable type to run on a managed device (script, binary, or Java). Depending on the executable type you select, different options are available, as described below. Maximum waiting time: Indicate the waiting time after starting the script, binary, or Java program.
Page 162 At some point in the future, you need to configure additional options for the policy by continuing with Section 17.4, “Assigning Policies,” on page 182. Click Next to display the Policy Assignment page to perform the following tasks: Specify assignments for this policy 162 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 163 Specify the schedule for this policy Specify groups for this policy 9 Assign the policy to the devices. 9a Click Add to browse for and select the appropriate Server or Workstation objects. You can also select Folder or Group objects. 9b 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: Suse Linux Enterprise Desktop 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 SUSE Linux Enterprise Desktop Policy, then click Next to display the Policy Name page. 164 Novell ZENworks 7.2 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 To remove an application from the list, select the application you want to delete, and click Remove. Remove Application Browser from Main Menu: Lets you remove the application browser from the main menu of the user's SUSE Linux Enterprise Desktop. 166 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 167 System Area Configuration: Lets you configure the following settings: Remove System Area from Main Menu: Lets you remove the system area from the main menu of the user's SUSE Linux Enterprise Desktop. Configure System Area: Lets you to configure items in the system area of the main menu of SUSE Linux Enterprise Desktop.
Page 168 Direct Internet Connection: Lets users connect to the Internet without using the proxy server. Manual Proxy Configuration: Lets you manually configure the proxy. Specify the HTTP Proxy value, HTTP Secure Proxy value, FTP Proxy value, Socks Proxy value, and corresponding port numbers. 168 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 169 To authenticate the user before proxy configuration, click Authentication. In the HTTP Proxy Authentication dialog box, select Use Authentication, specify the username and password, then click OK. Automatic Proxy Configuration: Lets you automatically configure the proxy from a certain URL by specifying the URL. 11 Click Next to display the Default System Requirements for the SUSE Linux Enterprise Desktop Policy page.
Page 170 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. For more information, see Section 17.3, “Creating Policy Groups,” on page 179. 170 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 171: Text File Policy
20 Click Next to display the Finish page. 21 Review the information on the Finish page, making any changes to the policy settings by using the Back button as necessary. Click Finish to create the policy as configured according to the settings on the Finish page.
Page 172 Append lines to file: Lets you append the given lines of text to the file Prepend lines to file: Lets you prepend the given lines of text to the file. 172 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 173 New string: Specify the text to be used for carrying out the specified action in the file. For example, you can select to replace a search string with a new string. Create the file, if it does not exist: Allows you to create the specified file, if it does not exist. The file is created with the specified contents.
Page 174 Select Binary, Java, Script, or None from the drop-down list. Depending on which type you select, the available options vary. For more information about the specific options, see the descriptions in the Pre-Change Action section directly above. 9 Click Next to display the Summary page. 174 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 175 10 Click Finish to create the policy as configured according to the settings on the Summary page. If you click Finish, the Text File policy is created but it does not have devices assigned or a schedule specified. At some point in the future, you need to configure additional options for the policy by continuing with Section 17.4, “Assigning Policies,”...
Page 176 16 Review the information on the Finish page, making any changes to the policy settings by using the Back button as necessary. Click Finish to create the policy as configured according to the settings on the Finish page. 176 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 177: 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 146. 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 151.
Page 178: 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. 178 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 179: 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 589. Folder: Type the name or browse to the folder that contains this folder in the ZENworks Control Center interface.
Page 180 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. 180 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 181 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 182: 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. 182 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 183: 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 184: 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 185 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 186 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. 186 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 187: 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 188.
Page 188 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. 188 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 189: 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 190 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. 190 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 191: 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 192 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. 192 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 193 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 194: 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. 194 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 195 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 196: 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. 196 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 197: Renaming, Copying, Or Moving Policies
In the Novell Linux Desktop policy, some of the configuration settings are file-permission-based, and hence for a root user, these settings such as items in the Program menu and System menu will be accessible even if it is locked.
Page 198: 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 199. To delete a policy, policy group, or folder: 1 In the ZENworks Control Center, click the Policies tab. 198 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 199: 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 200 200 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 201: 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 203 Chapter 19, “Understanding RPM Packages,” on page 207 Chapter 20, “Using RPM and File Bundles,”...
Page 202 202 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 203: Package And Content Management Overview
RPM are also imported to the ZLM 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 not assign the bundles or catalogs containing the dependent RPMs to the managed devices.
Page 204 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" 204 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 205: 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 206: 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 289. 206 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 207: Understanding Rpm Packages
The RPM packages are usually targeted at particular distributions such as SLES 9 or SLED 9. An RPM package file is identified with a .rpm extension. For example, the package format for the file novell-zenworks-install-7.2-2- 0.0.0.i386 is novell-zenworks-install-7.2-2-0.0.0.i386.rpm.
Page 208: 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 209: Loading Base Packages
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 rug/zen-updater command. However, this process is not recommended in a ZENworks Linux Management setup because of the excessive usage of bandwidth by the SLES 10 agents to download the updates.
Page 210 210 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 211: 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 212: Rpm Bundles
Bundle Commands section of zlman (1) (page 547). 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. 212 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 213 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 315, Chapter 23, “Using Dell Update Package Bundles,” on page 279, and Section 20.3, “Creating File Bundles,”...
Page 214 ZENworks Control Center. During the bundle-creation process, packages are copied to the ZENworks Server and placed in the package repository (/var/opt/novell/zenworks/ pkg-repo). 6 Add the RPM packages to include in the bundle using the Upload RPM and the Import from Repository options.
Page 215 ZENworks Control Center. Click OK to upload the packages to the ZENworks Linux Management server. The package repository is the /var/opt/novell/zenworks/pkg-repo directory on the ZENworks Server. Target platforms: Select one or more platforms from the Target Platforms list. You can press Shift+click or Ctrl+click to select multiple platforms.
Page 216 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. 216 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 217 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 218 Java: Specify a Java executable class that launches on assigned devices. 9c Maximum waiting time: Select one of the following options: Do not wait: Specify that the ZENworks Management Daemon (ZMD) does not block while the script completes. 218 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 219 Step 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.
Page 220 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. 220 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 221 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/logs/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 222 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. 222 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 223: 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 224 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. 224 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 225 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 226 OK. The ZENworks Server contains all of the files that are included in bundles defined within your Management Zone. The package repository is the /var/opt/novell/ zenworks/pkg-repo directory on the ZENworks Server. When you add a file or RPM package to a bundle, the file or package is automatically uploaded to the package repository.
Page 227 As part of the process of distributing a bundle, ZENworks Linux Management can launch scriptable actions that will be executed before and after the bundle is distributed, installed, and uninstalled. For example, you can get data files from a Web server before installing an application that uses them, run applications, and so forth.
Page 228 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. 228 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 229 Java Runtime Executable (JRE): (Required) Specify the path to the JRE that launches the class, for example, /usr/local/JRE/bin/java. The JRE must be already installed on the assigned device. JRE parameters: Specify any parameters you want to pass to the JRE system, for example, -cp/usr/lib/tools.jar.
Page 230 If you do not select this option, the packages will be deployed and installed on assigned devices according to the schedule. Click the Schedule icon to choose the schedule type. 230 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 231 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. 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.
Page 232: 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. 232 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 233 The log file is located in / var/opt/novell/logs/zenworks. This option is not applicable for File bundles. 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 234 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. 234 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 235: 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 236 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: 236 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 237 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 238 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 238 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 239: 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 240 589. 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. 240 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 241: 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 242 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. 242 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 243 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 244 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. 244 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 245: 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 246: 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. 246 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 247 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 248: 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. 248 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 249: 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 250: 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. 250 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 251: 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 252: 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. 252 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 253 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 254 The following schedules are available. Click the link in the left column for more information about each schedule type and its options. Schedule Type Description No Schedule Use this option to indicate no schedule; no action occurs. 254 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 255: 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 256: 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/server.xml file. 256 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 257 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 258 258 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 259: 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 259 Section 21.2, “Locking and Unlocking a Bundle on a Managed Device,”...
Page 260: Locking And Unlocking A Bundle On A Managed Device
1 List all the bundles that are locked on the managed device by entering the rug bll command. This displays the bundle name and its lock index. 2 Select the bundle you want to unlock. 260 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 261: Reverting To A Previously Installed Software Configuration State
3 Unlock the bundle by entering the rug bld lock_index command. 4 Ensure that the bundle is unlocked by entering the rug bll command. This displays only the locked bundles. 21.3 Reverting to a Previously Installed Software Configuration State You can use the rug ro date_time command or create a checkpoint by using rug cpa checkpoint_name command to revert to a previously installed software configuration state.
Page 262: Installing The Best Package
1 On the managed device, enter the zen-installer command. The Software Installer window is displayed. 2 Click Configure, then click the Preferences tab. 3 Select Show Version Details. 4 Click Close. 262 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 263 The Software Installer window displays the packages and versions available for installation. 5 Select the package to be installed, then click Install. Understanding the Package and Content Management Features Available on a Managed Device 263...
Page 264 264 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 265: 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 266 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. 266 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 267 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 268 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. 268 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 269 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/logs/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 270 14 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 create the item as configured per settings on the Finish page. 15 Click OK. 270 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 271: Assigning Catalogs
22.3 Assigning Catalogs When you assign catalogs, you specify device assignments, special flags, and deployment or update schedules for an existing catalog. Step 7 under Section 22.2, “Creating Catalogs,” on page 265, you were given the choice of clicking Finish or Next. If you clicked Finish, the catalog was created without assigning devices to it, setting special flags, or specifying deployment or update schedules for the catalog.
Page 272 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. 272 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 273 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 274: Adding Bundles To Catalogs
Use the Edit drop-down list on the Bundles page to edit an existing object. To access the Edit drop- down list, you must select an object by clicking the check box next to the object's name in the list. 274 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 275: Deleting Catalogs
Depending on the type of object you select, you can rename, copy, or move the selected object. For example, if you select a catalog object, you can rename and move the catalog, but you cannot copy it. If you select a bundle object, you can rename, copy, or move the object. If the option is dimmed, that option is not available for the selected object type.
Page 276: Creating Folders
Bundle, Bundle Group, Catalog, Device, and Device Group objects. To create a folder: 1 In the ZENworks Control Center, click the Bundles tab. 2 Click New, then click Folder to display the New Folder dialog box. 276 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 277 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 589. Folder: Type the name or browse to the folder that contains this folder in the ZENworks Control Center interface.
Page 278 278 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 279: 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.2 Linux Management Installation Guide. The following sections contain additional information: Section 23.1, “Obtaining Dell Update Packages,” on page 279 Section 23.2, “Assigning Dell Update Package Bundles,”...
Page 280 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. 280 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 281 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/logs/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 282 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. 282 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 283: 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 284: 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. 284 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 285 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 286 286 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 287: 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 288: Configuring A Content Replication Schedule
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. 288 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 289: 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 290: Zlmmirror
All of the software components necessary to use zlmmirror are installed during the ZENworks Linux Management installation process. The zlmmirror executable is located in /opt/novell/zenworks/bin/. You can view help for zlmmirror at any time by running the following command: zlmmirror --help...
Page 291: Creating The Configuration Files By Using The Command Line Utility
Red Carpet, or create configuration files manually. Configuration files are specified using the -c flag: zlmmirror command -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 292 NU: /etc/opt/novell/zenworks/zmd/deviceid for SLES 9 and OES, /etc/zmd/deviceid for SLES 10 and SLED 10 For the Novell Updates (NU) server, the device must be registered with NCC to use the deviceid as User. 292 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 293 When connecting to an RHN server or Dell server, leave this element empty. NU: /etc/opt/novell/zenworks/zmd/secret for SLES 9 and OES, and /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 294 <catalogname>-patches folder Folder Specifies the eDirectory folder (for example, /folder1/folder2) where bundles and catalogs are created and updated. If not specified, the catalogs and bundles are created and updated in the /zlmmirror folder. 294 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 295 Configuration Element Description Target Restricts the mirroring operation on this catalog to packages and patches that support the specified target platforms. If no target is specified, packages for all platforms are mirrored. This element can be specified multiple times, and can contain either a target name or a regular expression string for wildcard matching of target names.
Page 296: Creating A Configuration File By Using The Xzlmmirror Utility
You can also edit the configuration file. For more information, see “Editing the Configuration File” on page 301. Configuring the Servers 1 To start the xzlmmirror utility, enter the following command at the command line: xzlmmirror The xzlmmirror-Server Settings window is displayed. 296 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 297 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: https://server DELL: http://ftp.dell.com...
Page 298 4b Specify the username and password to connect to the local server. 4c To validate the credentials for the servers, and to connect to the remote server, click Connect. 5 To view the log information of the server configurations, go to /var/opt/novell/log/ zenworks/zlmmirror.log file. 6 Continue with “Configuring the Catalogs”...
Page 299 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 300 12 (Optional) To configure a different server, or to reset the server settings that you have already configured, click Back. 13 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 303. 300 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 301 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 302: Mirroring Patch Bundles For Sles 10 / Sled 10 / Oes 2 From The Nu And Rce Type Repositories
NU and RCE Type Repositories You can mirror patch bundles for SLES 10, SLED 10, 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 / OES 2” on page 302 “Mirroring the Patch Bundles for SLES 10 / SLED 10 / OES 2”...
Page 303: Testing And Performing The Mirroring Operation By Using Zlmmirror
NOTE: The local name for the catalog should not be same as the name reserved for the folder <catalogname>-patches. In other words, the <localName> tag of the mirror configuration file should not use the same name as the <catalogname>-patches. 25.3.4 Testing and Performing the Mirroring Operation by Using zlmmirror Before starting the mirroring operation, make sure that at least 10 GB of diskspace is available on the device.
Page 304: Distributing Catalogs From A Public Zenworks Linux Management Server
ZENworks Linux Management Server using no registration key (to use the default registration rule). For more information, see “Installing the ZENworks Agent and Registering the Device” in the Novell ZENworks 7.2 Linux Management Installation Guide. 304 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 305: Mirroring Dell Update Packages To Your Zenworks Server
3 Copy the contents of the deviceid and secret file from that workstation (/etc/opt/ novell/zenworks/zmd on SLES 9 and OES, /etc/zmd on SLES 10 and SLED 10) to the zlmmirror.conf file in the <User> and <Password> tags of the <RemoteServer>...
Page 306 --help. 6 In the <Catalog> section, edit the following configuration elements: Configuration Element Setting Name of the catalog you want to mirror from this remote server: <Name></Name> <Name>catalog_name</Name> 306 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 307 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. Your edited zlmmirror configuration file should look similar to the following example.
Page 308 Section 22.1, “Understanding Catalogs,” on page 265. During installation of the Dell Update Packages, if you get an error message stating that your system needs more contiguous RAM, reboot the system and retry the installation. 308 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 309: Management Zones
You should periodically run the zlmmirror utility to obtain updated Dell Update Packages. You can automate the process by creating a cron job to perform the mirror session as often as needed (monthly, for example). 25.6 Mirroring Bundles Between ZENworks 7.2 Linux Management Servers Located in Different Management Zones You can mirror bundles in a catalog from a remote primary ZENworks Linux Management server...
Page 310: Deploying Red Hat Network Updates
Following are two scenarios for updating devices with RPM packages: Section 25.7.1, “Providing All RPM Packages and Package Bundles through a Catalog (Pulling),” on page 311 Section 25.7.2, “Delivering Specific RPM Packages (Pushing),” on page 311 310 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 311: Providing All Rpm Packages And Package Bundles Through A Catalog (Pulling)
Using rug: On a managed device, start a console session and enter the rug up command. 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 571). 25.7.2 Delivering Specific RPM Packages (Pushing)
Page 312: Encoding The Zenworks Server Password
To encode the ZENworks Server’s password, execute the following command: echo mypassword | recode ../b64 where mypassword represents your ZENworks Server’s password. You can then use the resulting text in place of the clear text password. 312 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 313: 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 314: 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. 314 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 315: 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 317 Chapter 28, “Understanding Preboot Services in ZENworks Linux Management,” on page 321 Chapter 29, “Setting Up Preboot Services,” on page 345 Chapter 30, “Using Preboot Services,”...
Page 316 316 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 317: 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 318: 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. 318 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 319: 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 320 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 346. 320 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 321: 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 321 Section 28.2, “What Is the Preboot Execution Environment (PXE)?,”...
Page 322: Understanding The Zenworks Nbps
For more information on pxelinux.0 and its configuration files, see the syslinux home page (http://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). 322 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 323: Preboot Services Functionality
Before you can use Preboot Services with PXE, you need to do the following: 1. Install ZENworks 7.2 Linux Management on your imaging server. For more information, see Novell ZENworks 7.2 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 324 It is ideal for labs, classrooms, and staging areas. For more information, see Section 28.5.6, “Multicasting Device Images,” on page 340. 324 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 325: 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 326: 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. 326 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 327: 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 328: 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 329: 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 329...
Page 330 ZENworks Linux Management provides a utility (smb-provisioning.exe) to help provision AMT-devices in small business mode with enterprise names. This utility can be found in the /opt/ novell/zenworks/zdm/winutils directory on your imaging server. It requires .NET framework. For the procedures in providing Intel AMT enterprise names to ZENworks Linux Management, see Section 29.4.6, “Configuring Intel Active Management Technology (AMT),”...
Page 331: 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 332 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 333 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 334 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 nvlnbp.sys and it reads the image-safe data. 334 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 335 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 (z_auto.cfg in this example).
Page 336 3. Pxelinux.0 requests and receives /boot/root from the TFTP server. 4. Pxelinux.0 requests and receives /boot/updateDrivers.tgz from the TFTP server, but is denied because the file does not exist (it is used to provide post-release software updates). 336 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 337: 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 338: Creating, Installing, And Restoring Standard Images
“Manually Taking an Image of a Device” on page 405. 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 339: Reimaging Corrupted Devices
If you are not using Preboot Services, boot the device with the imaging boot CD or DVD and consider installing the ZENworks partition to enable auto-imaging without needing to supply the CD or DVD. For more information, see Step 3 on page 355 Section 29.7.2, “Enabling a Device for Imaging Operations,”...
Page 340: 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 341 When using a Preboot bundle to perform multicasting, the imaging server is the session master, which sends the .zmg image file to the session participants. The novell-pbserv daemon is used in this process. All problems are reported and displayed on the session master device.
Page 342: 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,”...
Page 343 Create a Dell Configuration Preboot bundle (see Section 30.5.2, “Creating Dell Configuration Bundles,” on page 447). Troubleshoot Dell Configuration Preboot bundles (see “Dell DTK” in the Novell ZENworks 7.2 Linux Management Troubleshooting Guide). Understanding Preboot Services in ZENworks Linux Management 343...
Page 344 344 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 345: 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 346: 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 347 1 Copy the settings.txt file containing the settings you want for the imaging boot process onto a floppy diskette. This file is located in the /opt/novell/zenworks/zdm/winutils directory on the imaging server where ZENworks Linux Management is installed. Setting Up Preboot Services 347...
Page 348: 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).
Page 349 2 Click Load, browse for the settings.txt file, then click Open. The default location is A:\. 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 settings.txt file.
Page 350 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. 350 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 351 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 352 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 353 Preboot information. To create a PBI configuration file and then the PBI file: 1 On a Windows device, browse to the opt/novell/zenworks/zdm/winutils directory on 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 354: Managing Zenworks Partitions
Section 29.2.3, “Using the ZENworks Imaging Media Creator,” on page 348.) Then, do the following: 1 Boot the device with the imaging CD or DVD, then select Install/Update ZEN partition from the menu. 354 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 355 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 356: 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 357 Section 29.3.2, “Deploying Preboot Services In a Network Environment,” on page 358 356 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 357: 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 358: Deploying Preboot Services In A Network Environment
There are three important points about configuring servers for Preboot Services: DHCP server: The Preboot Services environment requires a standard DHCP server. It is up to you to install your standard DHCP server. 358 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 359 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 360 If you are using Intel AMT, support for it should be enabled in the novell- zmgprebootpolicy.conf file. (This feature is not currently supported in Novell ZENworks Linux Management.) Network Configuration The configuration required to run Preboot Services in your network depends on your network setup.
Page 361 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 362 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 363 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 364 IP address of the gateway that serves the PXE device, and server is the IP address of the server that the DHCP frame should be forwarded to. 3 Save the configuration. 364 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 365 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 366: 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 367 /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 368: 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 369 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 IMPORTANT: If you want to save the default options for this menu, we recommend that you make a backup copy of pxemenu.txt, such as pxemenu_orig.txt.
Page 370 CFG#: The configuration file that is used upon selecting the menu option. Hint#: Displayed in the bottom of the screen to explain the highlighted menu option’s function. It changes as you highlight a menu option. 370 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 371: Configuring Preboot Services Defaults
IMPORTANT: If you add or subtract a menu option, make sure that you do the same thing to each of the last three sections. The numbering should be consecutive (such as 1 through 5). Be sure to keep the corresponding items matched in each of the last three sections. 4 When finished, save the pxemenu.txt file.
Page 372 Start DELL DTK Starts the DELL Deployment Toolkit v2.1 in the automated mode where it checks for details on assigned work, performs the assigned work, and reboots. No user input is allowed or required. 372 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 373: Configuring Image Storage Security
Menu Option Function Start DELL DTK (Maintenance Mode) Starts the DELL Deployment Toolkit v2.1 in the maintenance mode by loading it into a RAM drive so that you can configure the scripts and files used in the Dell Configuration bundle. Exit Resumes booting of the device without doing any Preboot bundle work.
Page 374: Configuring Non-Registered Device Settings
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 Non-Registered Device Settings section: 374 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 375 4 Fill in the fields: 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 376 10.0.0.5 and 10.0.0.25. If you select this option, the following fields are displayed: Subnet mask: (Optional) For assigning devices to a specific subnet mask. 376 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 377: Configuring Preboot Work Assignments
Default gateway: (Optional) For assigning devices to a specific gateway for access to the Internet or network after the device is imaged and rebooted. IP addresses available for machines: According to the information you provide in this section, this list box displays the available IP addresses for your devices to use. Start and end of IP address range: Do either of the following: Specify one IP address at a time in the first field and click Add each time to place it into the list box.
Page 378 Devices whose BIOS identification matches one of the strings listed in the Servers or Laptops fields above are classified for the rule as either a server or a laptop. 378 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 379 A workstation is a hardware type that does not require a BIOS string definition. Therefore, if you select Servers or Laptops in the Rule Construction dialog, but you have not entered BIOS identification strings for them here, they are treated as workstations by the rule. These hardware type definitions are applicable only to rules;...
Page 380 For example, “(u AND v AND w) OR (x AND y AND z)” means “match either uvw or xyz.” In the Rule Construction dialog box, this looks like: 380 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 381 u AND v AND w OR x AND y AND z Filter sets cannot be nested. You can only enter them in series, and the first filter set to match the device is used to validate using the applied bundle to do preboot work on the device. Therefore, the order they are listed does not matter.
Page 382 The options are: BIOS Asset Tag BIOS Serial Number BIOS Version CPU Chipset Hard Disk Controller Hard Drive Size (in MB) 382 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 383 Hardware Type IP Address MAC Address Model Network Adapter RAM (in MB) Sound Card System Manufacturer Video Adapter If the drop-down list on the left displays NOT, then the work rule is stating that the device should not match the component as described in the next two fields. To use the Hardware Type option effectively, you must first configure the settings for either the Server or Laptop field in the Hardware Type Definitions section in the work assignment configuration.
Page 384: Configuring The Server Referral List
Zones can access their home zone. For more information, see Section 28.3.6, “Preboot Referral Lists,” on page 328. To set up referral lists: 1 In the ZENworks Control Center, click the Configuration tab, which displays the following Management Zone Settings section: 384 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 385 2 In this section, click Preboot Services to display the configuration sections. 3 Locate the Server Referral List section: 4 Specify the ZENworks Linux Management servers: List of server IP addresses and DNS names: Specify the DNS name or IP address of a server that can host Preboot operations, then click Add to place the server into the referral list.
Page 386: Configuring Intel Active Management Technology (Amt)
6 Unzip the .tar.gz file and decompress the iamt-1.1.8.tar (or later version) file. 7 To install the drivers, follow the instructions contained in the Readme file that is contained in the .tar file. 386 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 387 This creates binaries of the drivers. 8 After following the instructions to compile the iAMT Redirect Drivers, make RPMs of the binaries, then distribute the RPMs to the other devices that need the drivers. For more information, see Chapter 20, “Using RPM and File Bundles,” on page 211.
Page 388 Each AMT device itself may have up to four different enterprise names. You can use the View Current Enterprise Names or the Delete Existing Enterprise Names to manage the names in the Progress list box. 8 Select Add Enterprise Name, then click Exit. 388 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 389 This adds the defined enterprise name into the Progress list box and to the device. 9 Repeat Step 1 through Step 8 for each device to be provisioned with the Small Business mode. 10 To provide the provisioned enterprise names to ZENworks Linux Management, continue with Section , “Setting Up the Global Intel AMT Enterprise Names,”...
Page 390: Overriding Preboot Services Defaults
The Servers folder, then a server contained in the folder The Workstations folder, then a workstation contained in the folder 3 On the page that is displayed, click the Settings tab to display the Settings page options: 390 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 391 4 Click Preboot Services to display the Preboot Services configuration page: If you have not previously configured for this folder or device, the following is displayed: Current: (System) (Override settings) and the Preboot Menu Options section is disabled for editing. The above text varies depending on whether you are at the folder or device level.
Page 392: Enabling Pxe On Devices
Integrated Devices section of the BIOS, which might have an option to enable PXE. PXE might be called by another name, such as MBA (Managed Boot Agent) or Pre-Boot Service. 392 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 393: Verifying That Pxe Is Enabled On A Device
After enabling PXE in the Integrated Devices section, look at the Boot Sequence options and move PXE so that it is first in the boot sequence. 3 Save any changes you have made and exit the system BIOS. 4 Reboot the device. If the device does not have the network adapter and PXE integrated into the motherboard, it uses the installed NIC management software to prompt you to start PXE configuration during the boot process.
Page 394: Device Requirements
“Using a ZENworks Partition” on page 395 “Using a CD or DVD” on page 395 Using PXE You can set up a device to be automatically imaged from Preboot bundles by enabling PXE on the device. 394 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 395: Disabling Persistent Device Names
For more information, see Section 29.6.1, “Enabling PXE on a PXE-Capable Device,” on page 392. Using a ZENworks Partition If you cannot enable PXE on the device, you can use a partition to perform unattended imaging operations. For more information, see “Creating a ZENworks Partition”...
Page 396 3 Remove storage-specific entries, such as SAN or iSCSI volumes, that are not local to the system. 4 In /boot//grub/menu.lst and/etc/fstab files, replace the /dev/disk/by-* entries from the scratch file with the device names the symlinks point to. 5 Reboot the device. 396 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 397: 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 397 Section 30.2, “Multicasting Images,” on page 419 Section 30.3, “Configuring AutoYaST or Kickstart Installation Script Bundles,” on page 430 Section 30.4, “Configuring ZENworks Script Bundles,”...
Page 398 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: 398 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 399 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 400 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. 400 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 401 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 402 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. 402 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 403 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 404 DVD when finished. For information on creating a ZENworks Script bundle, see Section 30.4, “Configuring ZENworks Script Bundles,” on page 440. 404 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 405: 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 405 “Using Image Explorer to Customize an Image” on page 408 “Creating an Add-On Image” on page 409 “Manually Putting an Image on a Device” on page 410 “Making an Image Available for Automatic Imaging”...
Page 406 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 406 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 407 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 408 QuickCompress: Use this option to compress an image file without waiting for the file to fully load into Image Explorer. For more information, see “Compressing Any Image without Waiting for the File to Fully Load into Image Explorer” on page 595. 408 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 409 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 410 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 410 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 411 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 412 15 Run lilo.s from the bash prompt. 16 Remove any CD or DVD from the drive and reboot the device. 17 Verify that the device boots to the operating system that was installed by the new image. 412 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 413 Making an Image Available for Automatic Imaging 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.
Page 414: Setting Up Disconnected Imaging Operations
The following sections explain how to set up and perform disconnected operations: “Using a CD or DVD for Disconnected Imaging Operations” on page 415 “Using a Hard Disk for Disconnected Imaging Operations” on page 416 414 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 415 Using a CD or DVD for Disconnected Imaging Operations In ZENworks Linux Management, you can use CDs and DVDs only as the storage medium for an image to put down, not for an image to be created. 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.
Page 416 “Creating an Image Using the ZENworks Imaging Engine Menu” on page 417 “Putting Down an Image Using the Bash Prompt” on page 418 “Putting Down an Image Using the ZENworks Imaging Engine Menu” on page 419 416 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 417 Creating an Image Using the Bash Prompt 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 346.
Page 418 5 When the imaging is done, remove the imaging boot media (if applicable) and do the following to boot the device with the new image: 5a At the Linux prompt, type lilo.s, then press Enter. 5b Press Ctrl+Alt+Delete. 418 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 419: Multicasting Images
If the device doesn’t boot to the new operating system (that is, if the Linux prompt is displayed), enter lilo.s again and reboot the device a second time. Putting Down an Image Using the ZENworks Imaging Engine Menu 1 Boot the device using one of the following methods: If the device is PXE-enabled, boot it from the Preboot Services imaging server.
Page 420: Multicasting In The Zenworks Control Center
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: 420 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 421 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 422 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. 422 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 423 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 424 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: 424 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 425: 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 425...
Page 426 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: 426 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 427 “Using the ZENworks Imaging Engine Menu to Perform the Multicast Session” on page 428 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 428 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 429 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 430: 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: 430 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 431 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 432 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 /boot/loader/linux on a SLES 9 SP1 bootable CD.
Page 433 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 /installs/scripts/myscript.cfg, then the URL to the installation directory is http://myserver.provo.novell.com/installs/...
Page 434 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 /scripts/autoyast.xml, then the URL to the installation directory is http://myserver.provo.novell.com/scripts/...
Page 435 (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 436: 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. 436 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 437 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 438 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 /isolinux/vmlinuz on a Red Hat Enterprise Linux 4 bootable CD.
Page 439 For example, if you select the HTTP protocol, enter myserver.provo.novell.com as the DNS name, and enter the path and filename as /config/ks.cfg, then the URL to the installation directory is http://myserver.provo.novell.com/config/ks.cfg, where /...
Page 440: 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: 440 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 441 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 441...
Page 442 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 442 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 443 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 444: 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 445 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 446 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 447: 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 448 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: 448 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 449 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 450 MBR (the default) and still provide an F10 menu option to the Dell utility partition. Edit the /boot/grub/menu.1st file and add the following lines: 450 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 451: Assigning Unassigned Preboot Bundles
title Dell Utility Partition chainloader (hd0,0)+1 Preboot Bundle: This option allows Preboot Services to complete the above configurations, then immediately apply a destructive image or installation script from another Preboot bundle. Select this option, then browse for or specify the path and filename of the Preboot bundle. 8 Click Next to display the Summary page.
Page 452 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: 452 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 453: 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 454 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. 454 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 455 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 456 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. 456 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 457: 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 457 Section 31.2, “Determining the Image Explorer Version,” on page 457 Section 31.3, “Image Explorer versus Linux Konquerer,”...
Page 458: Image Explorer Versus Linux Konquerer
Section 31.6.2, “Viewing the Properties of an Image File Item,” on page 459 Section 31.6.3, “Changing a Partition’s Size,” on page 459 31.6.1 Viewing and Modifying the Properties of the Image File 1 Click File > Open. 458 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 459: Viewing The Properties Of An Image File Item
2 Browse for and select the image file. Large image files might take a few moments to open. 3 Select the top line of the opened image file. This is the line that displays the path to the .zmg file. 4 Click File >...
Page 460: Image File Operations
1 Click File > Open. 2 Browse for and select the image file. Large image files might take a few moments to open. 3 Click File > Compress Image. 4 Fill in the fields: 460 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 461: Splitting An Image
Image File to Compress: Specifies the name of the existing imaging file to compress. Save Compressed Image As: Click the browse button next to this field to specify the location and filename under which to save the image. Compression Level: Specify an image-compression level: Compress for Speed: Takes the least amount of time to compress but creates the largest compressed image file.
Page 462: Hiding And Removing Content In The Image File
Deleting a file in the Image Explorer merely marks it for deletion; it can still be retrieved. A file marked as deleted is not removed from the image until the image is purged; files and folders marked as deleted are not restored during imaging. 462 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 463: Configuring File Sets
Unhiding Directories or Files in the Image You can unhide directories or files so that they are available when the image is applied to a device. 1 Click File > Open. 2 Browse for and select the image file. Large image files might take a few moments to open. 3 Select the directories and files that were previously hidden that you want to unhide.
Page 464: Extracting Content As Files
If any changes have been made, this must be done before you can extract the information. 4 Click File > Extract > As Add-on Image. 5 Specify the name and location of the new add-on image, then click OK. 464 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 465: Modifying Image Content
31.7.7 Creating an Add-on Image You can create an add-on image from existing directories and files on your system and add partitions to the new add-on image. 1 Click File > New. 2 To add a partition, click the root of the image, click Image, then click Create Partition. You cannot add a partition to an existing image.
Page 466: Creating A New Image File
4 Specify an image filename, including the .zmg filename extension, then click Save. 31.9.2 Selecting New Image File Options You can do the following in this new image file: “Adding Partitions” on page 467 466 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 467 “Adding Content” on page 467 “Configuring File Sets” on page 467 Adding Partitions 1 Select the top line of the new image file. This is the line that will display the path to the new .zmg file when you save it. 2 Click Image >...
Page 468 468 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 469 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 471 Chapter 33, “Reviewing the Device Inventory,” on page 473 Chapter 34, “Rolling Up Hardware Inventory,”...
Page 470 470 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 471: 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 472 472 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 473: 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 473 Section 33.2, “Reviewing Device Inventory Summaries,” on page 473 Section 33.3, “Reviewing Hardware (General),”...
Page 474: Reviewing Hardware (General)
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. Common Device Information Table 33-4 Inventory Item Attributes Description Batteries Name Battery name. 474 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 475 Inventory Item Attributes Description 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 476 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. Novell ZENworks 7.2 Linux Management Administration Guide 4 7 6...
Page 477 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 478: Refreshing Device Inventory
Remote Execute policy. For more information, see Section 16.6, “Remote Execute Policy,” on page 159. IMPORTANT: The Device Refresh Schedule setting does not affect refresh inventory information. 478 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 479: 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 480: 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 .str files, and places the files into the /var/opt/novell/zenworks/ inventory/entmerge directory.
Page 481: Understanding The Components Involved In The Inventory Roll-Up
6. The Receiver copies the .zip files to the database directory (dbdir) if a database is attached to 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.2 Linux...
Page 482: 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 483: Part Viii Remote Management
VIII Remote Management V I I I ® ® The Remote Management component of Novell ZENworks 7 Linux Management gives you the ability to remotely manage devices from the management console. Remote Management allows you Remotely control the managed device...
Page 484 484 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 485: Remote Management Overview
Remote Management Overview ® ® You can use Novell ZENworks 7.2 Linux Management to remotely manage all the supported platforms. To see details on supported platforms, see “Managed Device Requirements” in the Novell ZENworks 7.2 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 486: 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. 486 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 487: Configuring The Remote Management Settings
Setting Up Remote Management The following sections provide information on deploying the Remote Management component of ® ® Novell ZENworks 7 Linux Management in a production environment: Section 36.1, “Configuring the Remote Management Settings,” on page 487 Section 36.2, “Configuring Remote Management Agent,” on page 490 Section 36.3, “Starting Remote Management Operations Using the ZENworks Control Center,”...
Page 488 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. 488 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 489: 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 490: 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. 490 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 491: 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 492: 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: 492 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 493: 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 494: 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. 494 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 495: 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 496 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) 496 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 497: 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 498 498 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 499: 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 500: 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. 500 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 501: Backing Up The Log Files
The logrotate utility uses the file to rotate the existing and the new log files created in /var/opt/novell/log/zenworks on the ZENworks Linux Management server. These server log files are compressed with date extension, rotated, and backed up daily for 33 days before being discarded.
Page 502 The tomcat server logs rotated within the tomcat subdirectory are not affected by the logrotate file. For SLES 9 and RHEL4 servers, the logrotate utility is also applied to zmd-messsages.log, the agent log file because the path is common for both server and agent log files. 502 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 503: 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 503 Section 38.2, “Working with the Log Pages,” on page 505 38.1 The Event Log Page The Event Log page gives you an overview of the recorded events.
Page 504 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. 504 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 505: 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 505 Section 38.2.2, “Acknowledging an Event,” on page 506 Section 38.2.3, “Using the Advanced Page,” on page 508 Section 38.2.4, “Clearing the Event Log,”...
Page 506: 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 505.) 2 Click the event you want to acknowledge. 506 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 507 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 505.) 2 Click Advanced on the toolbar in the Event Log section.
Page 508: 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. 508 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 509 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 510 510 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 511: 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 512: Debugging And Logging Zmd
The file is located in the /var/log/ directory on SLES 10 and SLED 10 devices, and in the /var/opt/novell/log/zenworks directory on all other devices. For detailed ZMD logging information on SLES 10 and SLED 10, you can also refer to /var/ log/zmd-backend.log.
Page 513: Configuring Message Logger Settings
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 514: 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. 514 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 515: Configuring Snmp Settings
40.1.4 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.
Page 516: Configuring Message Logger Settings For A Managed Device
The maximum number of backup files is 99. The most recent backup file is named central- message.log.1, the second most recent file has the number 2 and so on. When the maximum file size is reached, the oldest file is deleted. 7 Click OK or Apply. 516 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 517: Configuring System Log Settings
40.2.2 Configuring System Log Settings These settings allow you to insert messages into the system file. The path of the system log file is / var/log/messages. 1 In the ZENworks Control Center, click Configuration. 2 In Management Zone Settings, click Local Device Logging. 3 Under System Log, select the Send Message to Local System Log if Severity Is check box to enable the fields.
Page 518 518 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 519: Part X Reports
Reports ® ® The following sections provide information on Novell ZENworks Linux Management reporting features: Chapter 41, “Reports Overview,” on page 521 Chapter 42, “Generating ZENworks Reports,” on page 523 Reports...
Page 520 520 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 521: 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 522: 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. 522 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 523: Generating Zenworks Reports
Generating ZENworks Reports This section includes the following topics: Section 42.1, “Creating a Folder,” on page 523 Section 42.2, “Creating a Report,” on page 524 Section 42.3, “Organizing Reports and Folders,” on page 527 Section 42.4, “Modifying Report Details,” on page 528 Section 42.5, “Generating Reports,”...
Page 524: Creating A 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. 524 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 525 Report description: Specify a report description. The system displays this description beneath the report name in the generated report. 4 Click Next. 5 Use the Columns page to add and sort the columns that you want to display on the report. Columns: Select a column, then click Add.
Page 526 If you add other types of columns or filters, the message displayed in this column may be inaccurate. Known exceptions of device columns and filters that also cause this inaccuracy are: Device Code Page Device Virtual Memory Device Visible Memory 526 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 527: Organizing Reports And Folders
42.2.1 Using Templates to Create Dell Reports ZENworks Linux Management includes two report templates you can use to create reports: Devices Not Having Valid Dell Update Package Bundles Devices Not Having Valid RPM Package Bundles Because these are templates, you must modify them before you can generate a report. 1 In the ZENworks Control Center, click the Reports tab.
Page 528: Modifying Report Details
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 529: Generating Reports
42.5 Generating Reports You can generate an existing report, or generate multiple reports simultaneously. After the system displays the report, you can print the information or export and view the data in HTML, CSV, or XML formats. 1 In the ZENworks Control Center, click the Reports tab. 2 To generate a report, select the report’s check box, then click Generate.
Page 530: Resetting Default Reports
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. 530 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 531: Part Xi Appendixes
Appendixes ® ® The following sections are accessed from other sections of the Novell ZENworks 7.2 Linux Management Administration Guide: Appendix A, “Command Line Utilities,” on page 533 Appendix B, “Bundle and Policy Schedules,” on page 585 Appendix C, “Naming Conventions in the ZENworks Control Center,” on page 589 Appendix D, “Imaging Utilities and Components,”...
Page 532 532 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 533: A Command Line Utilities
Command Line Utilities “zmd (8)” on page 534 “zrmservice (1)” on page 537 “zlm-debug (1)” on page 538 “zlmmirror (1)” on page 540 “zlman (1)” on page 547 “rug (1)” on page 571 Command Line Utilities...
Page 534: 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 535 Configuration file. Options such as proxy and cache settings can be adjusted through this file directly or with the rug set command. The file is located in /etc/opt/novell/ zenworks/zmd/ on SLES 9, OES 1, NLD, RHEL 3/4/5; and in /etc/zmd/ on SLES 10, SLED 10, and OES 2.
Page 536 Authors Copyright 2005-2009, 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). 536 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 537: 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 538: Zlm-Debug
Specifies the modules directory. --tar-dir=[directory_path] Specifies the directory to place the tarball in. -a, --no-cache Do not collect cache data. Cache data is located in the /var/opt/novell/zenworks/ cache/zmd directory. -c, --no-client Do not collect client data. Client data is gathered from the /var/opt/novell/ zenworks/cache/zmd directory.
Page 539 -s, --no-server Do not collect server data. Server data includes PostgresSQL and Novell eDirectory data. Authors Copyright 2005-2009, 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 540: 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.2 Linux Management Administration Guide.
Page 541 Lists the packages available in the specified bundle. Accepts the following option flags: -c,--conf=[filename] - Specifies the configuration file to use; otherwise, the default (/etc/ opt/novell/zenworks/zlmmirror.xml) is used. -t,--target - Restricts the listing to the specified target. catalog-list-bundles(clb) [options] [catalog] Lists the bundles available in the specified catalog.
Page 542 RCE and NU servers. Options -h, --help Displays a help message. --log=[logfile] Logs messages to a file. If no log file is specified, the default (/var/opt/novell/log/ zenworks/zlmmirror.log) is used. -v, --verbose Displays verbose output. --version Prints zlmmirror version information and exits.
Page 543 User - Name to use when connecting to the remote server. If no user is specified, zlmmirror reads the identity from the following location depending on Type: ZLM: /etc/opt/novell/zenworks/zmd/deviceid on SLES 9 and OES, and / etc/zmd/deviceid on SLES 10 and SLED 10...
Page 544 Password - Password to use when connecting to the remote server. If no password is specified, zlmmirror reads the password from the following location depending on Type: ZLM: /etc/opt/novell/zenworks/zmd/secret on SLES 9 and OES, /etc/ zmd/secret on SLES 10 and SLED 10...
Page 545 Catalogs, Bundles, and Packages Each bundle and package you want to mirror must be contained in a catalog on the remote server, so Catalog is the only item necessary to mirror a catalog, bundle, or package. A configuration file can have multiple Catalog elements, and each catalog you want to mirror must have its own entry.
Page 546 Copyright 2005-2009, Novell, Inc. (http://www.novell.com). All rights reserved. See Also (1), zlman (1), (8), zlm-debug (1), zrmservice (1) To report problems with this software or its documentation, visit Novell Bugzilla (http:// bugzilla.novell.com). 546 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 547: 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 548 Administrator Commands These commands are used to create and adjust administrator accounts. Administrator commands begin with word admin in the long form or the letter a in the short form. 548 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 549 admin-create (ac) [options] [administrator] [password] Creates a new administrator account. By default, this account is created with view-only rights to all objects. Use the admin-rights-assign command to grant additional rights to this account. admin-delete (ad) [options] [administrator] [...] Deletes an administrator account. admin-list (al) [options] [folder] Lists all administrator accounts.
Page 550 Bundle - An existing bundle to which you want to add one or more RPM packages. Target - OS/Platform targets. (valid targets for your environment can be viewed using zlman tl.) Package File - RPM format package file. Accepts the following option flags: 550 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 551 --force-nevra - Force the package to add in spite of the NEVRA (name, epoch, version, release, and architecture) conflict. --freshen - Upgrade the package only if it is installed. --installtype=[upgrade|install] - Specify the rpm installation type. The upgrade value triggers the rpm -u behavior and the install value triggers the rpm -i behavior.
Page 552 [[package file] [...]] Update the properties of a package in a bundle. Accepts the following options. --arch=[arch] - Specifies the arch of package to update. --freshen=[true|false] - Only upgrade package if installed. 552 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 553 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 554 (lp) [options] Lists packages. Accepts the following option flags: --name-filter = [name-filter] - Name filter. --epoch-filter = [epoch-filter] - Epoch filter. --version-filter = [version-filter] - Version filter. --release-filter = [release-filter] - Release filter. 554 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 555 Using the package-replace-packages command results in the newer package with the same NEVRAT replacing the existing package in all bundles it is a member of. The following example shows the correct usage: rc-qa-client-402:/opt/novell/zenworks # zlman prp sles-9-i586 /root/nrmtest-same-nevrat-b.rpm Username:administrator Password:****** [package.command.replacePackage.success]...
Page 556 Creates a registration specifying folder membership for servers. registration-create-workstation (rcw) [options] [key] [workstation folder] [registration folder] Creates a registration specifying membership in the specified workstation folder. registration-delete (rd) [options] [key] [...] Deletes the specified registration. 556 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 557 registration-folder-create (rfc) [options] [folder name] [containing folder] Creates a folder specified by [folder name] in the location specified by [containing folder]. registration-info (ri) [options] [key] Displays detailed information about the specified registration. registration-list (rl) [options] [folder] [filter] Lists all registrations. Accepts the following option flags: -r,--recursive - Includes subfolders.
Page 558 (rslg) [options] [name or position] Displays a list of groups that a device will be a member of when it is created with the specified rule set. 558 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 559 ruleset-move (rsmv) [options] [name or position] [new position] Changes the position of a rule set. ruleset-remove-rule (rsrr) [options] [ruleset name or position] [rule position] Removes a rule from a rule set. ruleset-remove-server-group (rsrsg) [options] [name or position] [group] [...] Removes server group membership from a rule set. Group membership for devices that have already registered is unaffected.
Page 560 --gmt - The specified time is taken as GMT. If this is not specified, the time is the local time of the device. server-add-policy (sap) [options] [server] [policy] [...] Associates one or more policies with a device. Accepts the following option flags: 560 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 561 --time=[HH:MM] - Specifies a time of day when the action must be performed. The time must be specified in the HH:MM format, with hours in 24-hour format. --date=[YYYY-MM-DD] - Specifies a date when the action must be performed. The date must be specified in the YYYY-MM-DD format.
Page 562 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 562 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 563 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 564 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 Thursday = TH 564 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 565 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 566 -f,--filter - Displays options matching the specified filter. Wildcards * and ? can be used if they are enclosed in quotation marks. workstation-list-bundles (wlb) [options] [workstation] Lists bundles associated with a workstation. workstation-list-catalogs (wlc) [options] [workstation] Lists catalogs associated with a device. 566 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 567 workstation-list-policies (wlp) [options] [workstation] Lists policies associated with a device. workstation-messages (wm) [options] [workstation name] Displays a list of unacknowledged messages associated with the specified device. Accepts the following option flag: -a, --all - Displays all messages including acknowledged messages. workstation-move (wmv) [workstation name] [new folder] Moves a workstation to a different folder.
Page 568 -f,--filter - Displays options matching the specified filter. Wildcards * and ? can be used if they are enclosed in quotation marks. policy-move (pmv) [options] [policy] [folder] Moves a policy. policy-rename (prn) [options] [existing name] [new name] Renames a policy. 568 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 569 Provides a user name. If not provided, you are prompted. -P, --password=[password] Specifies a password. If not provided, you are prompted. --log=[logfile] Specifies the log file. (default: /var/opt/novell/log/zenworks/zlman.log) -d, --debug Displays debugging output. --version Prints the zlman version and exits.
Page 570 Copyright 2005-2009, Novell, Inc. (http://www.novell.com). All rights reserved. See Also (1), zlmmirror (1), zlm-debug (1), zrmservice (1), zmd (8) To report problems with this software or its documentation, visit Novell Bugzilla (http:// bugzilla.novell.com). 570 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 571: 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 572 Accepts the following option flags: --entire-catalog - Installs all of the bundles from the catalogs specified. -y,--no-confirmation - Does not prompt for confirmation. -p,--prepare-only - Only prepares bundles; does not install. 572 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 573 -f,--freshen - Freshens children. -g,--use-guid - Refer bundles by bundle GUIDs. -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 is not applicable for File bundles. bundle-list (bl) [options] [ [catalog] [catalog] [.
Page 574 Unsubscribes the specified catalogs. Accepts the following option flags: -s,--strict - Fails if attempting to unsubscribe from an unsubscribed catalog. -a,--all - Unsubscribes to all catalogs. -e, --service - Specifies the service. 574 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 575 File Management Commands bundle-files (bf) [options] [bundle] Shows the files in a given file bundle. Accepts the following option flag: -g,--use-guid - Refer bundles by bundle GUIDs. The Status column is empty if the file is not installed. It displays “i” if the file is installed,“c” if the file is in the compressed form, or “p”...
Page 576 For the lists to match, the client must be subscribed to all available catalogs. Accept the following option flags: -t, --type - Specify the type of updates. 576 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 577 lock-add (la) [options] [name or pattern] [version] [...] Adds a package lock rule. This prevents changes to the installation state of the package that is specified in the lock. The package name can be specified individually, with wildcard patterns, or even with version number relations. The package_name can include wildcard characters.
Page 578 -d, --search-descriptions - Searches in package descriptions, but not package names. -i, --installed-only - Shows only packages that are already installed. -u, --uninstalled-only - Shows only packages that are not currently installed. 578 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 579 -c, --catalog - Shows only the packages from the catalog you specify. --sort-by-name - Sorts packages by name (default). --sort-by-catalog - Sorts packages by catalog, not by name. --show-nevra - Shows the NEVRA details of the packages. --show-duplicates - Shows the duplicate packages available in all catalogs. If the --show-nevra option is not specified, the output for this command is presented in Status, Catalog, Bundle, Name, Version, and Arch columns.
Page 580 [product] Shows detailed information for a product. products (pd) [options] [catalog] [catalog] [...] Shows the products in a given catalog. Accepts the following option flags: -i, --installed-only - Shows only installed products. 580 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 581 -u, --uninstalled-only - Shows only uninstalled products. Security Management Commands key-add (ka) [keyname] [keyid] Adds to the list of whitelisted keys for a service. key-delete (kd) [keyid] Removes from the list of whitelisted keys for a service. key-list (kl) [...] Displays whitelisted keys for a service.
Page 582 Put the daemon to sleep. Accept the following option flags: -f, --force - Force the restart. you-clean-cache (yc) [options] Cleans the YOU cache directory, /var/lib/YaST2/mnt on SLES 9, Novell Linux Desktop, and OES. 582 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 583 --terse Terse output. --no-abbrev No abbreviation. --quiet Quiet output; prints only error messages. --debug Debug output, prints full exception traces. --version Prints the rug version and exits. Authors Copyright 2005-2009, Novell, Inc. (http://www.novell.com). All rights reserved. Command Line Utilities 583...
Page 584 See Also zlman (1), (8), zrmservice (1), zlm-debug (1), zlmmirror (1) To report problems with this software or its documentation, visit Novell Bugzilla (http:// bugzilla.novell.com). 584 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 585: B Bundle And Policy Schedules B.1 No Schedule
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, “No Schedule,”...
Page 586: Day Of The Week Specific
If your network spans different time zones and you schedule an application to run at 1:00 p.m., it runs at 1:00 p.m. in each time zone. This option lets you specify a single time across the globe. 586 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 587: Event
You can, for example, select this option to have bundles deployed or installed on devices at the same time regardless of their time zones. Set the “Black Out” Time Ranges when Execution Should Not Occur: Click Add to display the Specify Black-Out Time Period dialog box.
Page 588: 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. 588 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 589: 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 590 590 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 591: Image Explorer (Imgexp.exe)
Linux Management imaging utilities, commands, and configuration settings. Section D.1, “Image Explorer (imgexp.exe),” on page 591 Section D.2, “Novell ZENworks Linux Management Imaging Agent (novell-zislnx),” on page 596 Section D.3, “Image-Safe Data Viewer and Editor (zisview and zisedit),” on page 597 Section D.4, “ZENworks Imaging Floppy Boot Disk Creator (zmediacreator.exe),”...
Page 592: 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. 592 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 593: 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 594: 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. 594 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 595: 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 596: 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 597: 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 613.
Page 598 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 599: 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 600: Using The Image-Safe Data Editor
To use zisedit, enter any of the following commands at the Linux bash prompt: 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. 600 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 601: 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 602: Imaging Configuration Parameters (Settings.txt)
(settings.txt) The settings.txt file contains parameters that control how the imaging boot process occurs. A copy is located in the /opt/novell/zenworks/zdm/imaging/winutils directory on the imaging server where ZENworks Linux Management is installed. You should maintain the working copy of settings.txt at the root of the imaging boot device (CD or DVD, or ZENworks partition).
Page 603 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 604 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 img auto command (see /bin/imaging.s). 604 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 605: 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 606 “Understanding the novell-pbserv Components” on page 606 “Configuring novell-pbserv” on page 606 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 607 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 608 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 609 “Understanding the novell-tftp Components” on page 609 “Configuring novell-tftp” on page 609 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 610 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 611 Description TFTPLogLevel = 2 The value assigned here determines which events are entered in novell- tftp.log. Specifying a high level in an active system can quickly fill the log. Valid values are: 0, 1, 2, 3, and 4. The default is 2.
Page 612 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 613 Description PolicyLogLevel = 1 The value assigned here determines which events are entered in novell- zenprebootpolicy.log. Specifying a high level in an active system can quickly fill the log. Valid values are: 0, 1, 2, 3, and 4. The default is 2.
Page 614: Viewing Information About Imaging Requests
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 615: Starting A Manual Multicast Session
Statistic Specifies Images Sent The number of images that the imaging server has sent to imaging clients since the imaging server was started. This includes only images that were retrieved from this imaging server. Images The number of new images that have been received and stored on the imaging server Received since it was started.
Page 616 616 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 617: 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 618: 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. 618 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 619: 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 371. 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 619.
Page 620: Make To Proxy (Img Makep)
“make to proxy” parameter: 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. 620 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 621: Restore Mode (Img Restore)
Parameter Specifies filepath The image filename, including a .zmg extension (case sensitive) and the complete 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 622: 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 338. If you omit this parameter, file set 1 is used. 622 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 623 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 624: 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. 624 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 625: Session (Multicast) Mode (Img Session)
Examples restorep Examples Table E-8 Example Explanation Removes all existing local partitions, retrieves the image img restorep 137.65.95.127 // from sys/imgs/dellnt.zmg on xyz_server, and puts xyz_server/sys/imgs/dellnt.zmg 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 626 Manually start multicast, providing the required information, then selecting Yes. 626 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 627: Partition Mode (Img Part)
Example Explanation Starts a multicast session named mcast01 and designates img session mcast01 m this device as the master. Each successive device that issues img session mcast01 before the imaging begins joins the session as a participant. Imaging doesn’t start until the master user presses g. Starts a multicast session named mcast01.
Page 628: 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: 628 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 629: Dump Mode (Img Dump)
img zenPartition operation where operation is enable, disable, or remove. Enter img 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 lilo.s to make this change effective. 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 630: Information Mode (Img Info)
The data currently stored in the image-safe area on the device 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...
Page 631 Menu item or parameter Action System Information > Lists the data currently stored in the image-safe area on the device. The items Image Safe Data that comprise this data are listed in Section D.3, “Image-Safe Data Viewer and Editor (zisview and zisedit),” on page 597.
Page 632 632 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 633: 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 634: Understanding Device Boot Processes In A Zenworks Imaging Environment
The root file system is located on an imaging CD as the file /boot/root. For PXE booting, the root file system is stored on the ZENworks imaging server as /srv/tftp/ boot/root. 634 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 635: Zenworks.s
Linuxrc attempts to locate and load the settings.txt file, either on the root of the imaging CD, or on the ZENworks imaging server in the /srv/tftp/boot directory. From settings.txt, linuxrc reads and processes any parameters that pertain to itself, then copies settings.txt to the root ( / ) of the file system.
Page 636: Command Line Parameters And Variables
F.4 Modifying ZENworks Imaging Resource Files From time to time you might want to modify an imaging distribution by adding your own files. These can be additional programs, scripts, data files, or updated Linux drivers. 636 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 637: Adding Files To An Imaging Boot Cd
Imaging 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 initrd or root file systems, but you need a Linux environment for performing the modification process.
Page 638: Adding Files To The Initrd Or Root File Systems
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 639 Other files to be included in the initrd file system should be copied to the appropriate directory. 8 To re-package the initrd file system, enter: cd work find . | cpio -quiet -o -H newc > ../initrd cd .. 9 To zip the new initrd file, enter: gzip -v9c initrd >...
Page 640: Using The Driverupdate File Method
For the CD, copy the updated root file to the /boot/i386/ directory on the boot CD. 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 driverupdate that is located in the /srv/tftp/boot directory on your Imaging Server or on the root (/) of an imaging boot CD.
Page 641 -xzvf driverupdate.tgz The driverupdate.tgz file contains the same directory structure as is created in Step 3 If you are manually creating the directories, create the following structure under the /work directory: `-- linux...
Page 642: Adding Or Updating Lan Drivers
New LAN drivers should be obtained from the manufacturer. Most LAN card manufacturers have drivers available for free downloading from their Web site. Some drivers are available from www.scyld.com/network, and the source to the Broadcom BCM5700 driver can be downloaded from http://www.broadcom.com/drivers/downloaddrivers.php. 642 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 643: Building Drivers
To compile a module, you need the Linux source code tree that contains the configuration matching the ZENworks kernel. To obtain the necessary source code, download the zenimgk2657244.tgz Linux source code tree file (http://support.novell.com/servlet/ filedownload/pub/zenimgk2657244.tgz). To use the Linux source code tree: 1 Unzip the file and install the source code tree in the /usr/src directory.
Page 644: Using Uname
The uname command enables you to find the current kernel version of your Linux environment. However, you might need to modify the results from the uname command to get your kernel versions to match. 644 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 645: Variables And Parameters
The following steps modify the uname command to provide the value you need: 1 To obtain your current kernel version, enter: uname -r Write down the version number so you can use it in Step 4. This example uses version 2.6.13- 15-smp from a SLES 9 SP2 installation.
Page 646: Imaging Script Variables
Go to the bash prompt after imaging is complete. F.7.2 Linuxrc Parameters Specified in Settings.txt Linuxrc Parameters Table F-3 Variable Definition netsetup dhcp = Use DHCP. 1 = Static IP. HostIP Static IP address to use. NetMask Network mask. 646 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 647: F.7.3 Image Engine Variables
Variable Definition Gateway Network gateway. HostName Host name to assign. Nameserver DNS name server. Domain Domain suffix. NetDevice ethx = 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 imglog debug file. ZENIMGLOG “A”...
Page 648: Troubleshooting At The Bash Prompt
Pipe to “less,” because hwinfo can create a lot of output. For example, hwinfo -pci | less. If you need to contact Novell Support for help, you should capture the output from hwinfo - pci to a file for their use. You can gather the most information with this command: hwinfo –pci –log /logfilename...
Page 649: 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 650 5, when the bash (#) prompt is displayed, view the content of the /BUILD file: If the build number has not incremented, either it really isn’t an update, or the copy operations failed. 650 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 651: 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 uname -r at the bash prompt.
Page 652 652 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 653: 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 /srv/tftp/z_auto.cfg or the /srv/tftp/z_maint.cfg file (or both) by adding the following line at the end of the Append command: netdevice=eth0 In ZENworks Control Center, add netdevice=eth0 as an additional kernel parameter while...
Page 654 This eliminates the need to select a NIC’s IP address manually. 654 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 655: 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 656: J.2 Ssh Tunneling Between A Windows Management Console And A Linux Managed Device
PuTTY site (http://www.chiark.greenend.org.uk/ ~sgtatham/putty). If you are using other SSH client software, use the appropriate commands for that software. 1 Enter the following command in the shell prompt: putty -L 5952:work:5950 gateway 656 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 657: Ssh Tunneling Between A Windows Management Console And A Linux Managed Device . 656 J.3 Compression
The first argument is the local forwarding option, which says that the local fake port 5952 should be created and connected to the genuine port work:5950. The second argument is the main non-option parameter to SSH, which tells it to connect to the device that runs the SSH daemon.
Page 658 658 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 659: K License Agreement For Libacl And Libgconf K.1 Library Gnu Public License
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 660 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. 660 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 661 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 662 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. 662 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 663 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 664 664 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 665: 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.2 Linux Management. The information can help you to keep current on updates to the documentation.
Page 666: July 28, 2008
Updates were made to the following sections. The changes are explained below. Section L.4.1, “ZENworks System Management,” on page 667 Section L.4.2, “Package and Content Management,” on page 667 Section L.4.3, “Preboot Services,” on page 667 666 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 667: Zenworks System Management
Section L.4.4, “Event Monitoring,” on page 668 Section L.4.5, “Appendix,” on page 668 L.4.1 ZENworks System Management The following changes were made in this section: Location Change Section 7.12, “Configuring Added this section. the ZENworks Server Preferences,” on page 76 Section 7.13, Added this section.
Page 668: January 11, 2008
NICs,” on page 653 L.6 October 16, 2007 Updates were made to the following sections. The changes are explained below. Section L.6.1, “Package and Content Management,” on page 669 Section L.6.2, “Appendix,” on page 669 668 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 669: September 3, 2007
L.6.1 Package and Content Management The following changes were made in this section: Location Change Section 21.1, “Locking and Updated this section with the relational operators that can be used in the Unlocking a Package on a command. Managed Device,” on page 259 L.6.2 Appendix The following changes were made in this section:...
Page 670: August 23, 2007 (Interim Release 1)
L.8.3 Appendix The following changes were made in this section: Location Change zlmmirror (1) (page 540) Updated this section. zlman (1) (page 547) Updated this section. rug (1) (page 571) Updated this section. 670 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 671: L.9 June 11, 2007
L.9 June 11, 2007 Updates were made to the following sections. The changes are explained below. Section L.9.1, “Package and Content Management,” on page 671 Section L.9.2, “Appendix,” on page 671 L.9.1 Package and Content Management The following changes were made in this section: Location Change Section 20.3, “Creating File...
Page 672: L.11 May 18, 2007
Added the following note: Using the Software Installer” on page 60 NOTE: Even though the user has been assigned rights by the administrator for installing the software, the installation of bundle fails. 672 Novell ZENworks 7.2 Linux Management Administration Guide...
Page 673: L.12.2 Device Registration
Location Change Section 6.4, Added the following note: “Uninstalling the ZENworks Agent,” on NOTE: When you uninstall ZENworks Linux Management on SLES 10 and page 66 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.
Page 674 To prevent the removal of packages, you must individually lock the packages. For more information on how to lock a package, see Section 21.1, “Locking and Unlocking a Package on a Managed Device,” on page 259. 674 Novell ZENworks 7.2 Linux Management Administration Guide...

This manual is also suitable for:

Zenworks linux management 7.2ir2

Novell ZENWORKS LINUX MANAGEMENT 7.2 IR2 - ADMINISTRATION GUIDE 09-25-2008 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

Troubleshooting

Need help?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for Novell ZENWORKS LINUX MANAGEMENT 7.2 IR2 - ADMINISTRATION GUIDE 09-25-2008

Summary of Contents for Novell ZENWORKS LINUX MANAGEMENT 7.2 IR2 - ADMINISTRATION GUIDE 09-25-2008