Page 1 AUTHORIZED DOCUMENTATION Preboot Services and Imaging Reference Novell ® ZENworks 10 Configuration Management SP3 ® 10.3 April 16, 2010 www.novell.com ZENworks 10 Configuration Management Preboot Services and Imaging Reference...
Page 2 Further, Novell, Inc., reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes.
Page 3 Novell Trademarks For Novell trademarks, see the Novell Trademark and Service Mark list (http://www.novell.com/company/legal/ trademarks/tmlist.html). Third-Party Materials All third-party trademarks are the property of their respective owners.
Page 4 ZENworks 10 Configuration Management Preboot Services and Imaging Reference...
Page 5: Table Of Contents
2.4.4 Editing the Novell Preboot Services Menu ....... . 71 Configuring Preboot Services Defaults for ZENworks Imaging .
Page 6 2.5.2 Configuring Non-Registered Device Settings ......75 2.5.3 Configuring Device Imaging Work Assignments ......79 2.5.4 Configuring the Server Referral List .
Page 7 Novell ZENworks Configuration Management Imaging Agent (novell-ziswin) ... . 194 Novell ZENworks ISD Service (novell-zisdservice) ....... . 195 E.3.1...
Page 8 Imaging Configuration Parameters (settings.txt) ........203 Imaging Boot Parameter for PCMCIA Cards ........206 Imaging Server .
Page 9 G.6.1 Imaging Script Variables ..........252 G.6.2 Linuxrc Parameters Specified in Settings.txt .
Page 10 ZENworks 10 Configuration Management Preboot Services and Imaging Reference...
Page 11: About This Guide
About This Guide This Novell ZENworks 10 Configuration Management Preboot Services and Imaging Reference ® includes information to help you successfully use Preboot Services and Imaging in a Novell ® ZENworks 10 Configuration Management SP3 system. The information in this guide is organized as follows: Chapter 1, “Overview,”...
Page 12 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 13: Overview
Overview ® ® In Novell ZENworks 10 Configuration Management, Preboot Services provides functionality that allows you to perform automatic imaging tasks on managed devices (Windows* Primary Servers and Windows workstations) before their operating systems boot. You can also perform manual imaging operations on these devices, as well as any other device with the supported file system, such as legacy Windows workstations, Linux Primary Servers, and Linux workstations.
Page 14: Preboot Services Strategies
Preboot Services Bootable CD or DVD: Used where PXE is not installed or where you want to manually perform a Preboot Services operation. This is applicable only for ZENworks Imaging. Preboot Services Bootable Diskette: Enables using the Preboot Services bootable CD or DVD when the device doesn’t support booting from a CD or DVD.
Page 15: Configuring Preboot Services
Some settings can be overridden at the device, group, and folder levels. You can configure the following settings per ZENworks Management Zone: Novell Preboot Services Menu Options: The menu contains five options: 1) Start ZENworks Imaging (automatically executes the bundle); 2) Start ZENworks Imaging Maintenance (accesses the imaging maintenance mode prompt);...
Page 16: Setting Up Devices To Use Imaging Bundles
1.1.5 Setting Up Devices to Use Imaging Bundles In order for a device to automatically use an assigned Imaging bundle, you must complete two tasks: “Setting Up the Device to Apply the Bundle” on page 16 “Assigning a Bundle” on page 16 Setting Up the Device to Apply the Bundle Preboot Services utilizes PXE and other boot mechanisms and media to trigger the imaging work.
Page 17: What Is The Preboot Execution Environment (Pxe)
Click Devices > Workstations > select the check boxes next to one or more workstations, then click Action > Assign Bundle. You can assign bundles to all selected workstations. Click Devices > Servers > select a server, then click Advanced (in Imaging Work on the Summary tab).
Page 18 For more information on and its configuration files, see the syslinux home page (http:/ pxelinux.0 /syslinux.zytor.com/pxe.php). For a copy of the Novell modifications to the syslinux open source project, see Novell Forge (http:// forge.novell.com). ZENworks 10 Configuration Management Preboot Services and Imaging Reference...
Page 19: Preparing To Use Pxe
1.2.3 Preparing to Use PXE Before you can use Preboot Services with PXE, you need to do the following: 1. Install Novell ZENworks 10 Configuration Management SP3. For more information, see the ZENworks 10 Configuration Management Installation Guide. 2. Enable PXE on your Configuration Management devices. For more information, see Section 2.7, “Enabling PXE on Devices,”...
Page 20 Using the same image on multiple devices means they all have the same network identities. However, you can install the ZENworks Configuration Management Imaging Agent (novell-ziswin) 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 21 %ZENWORKS_HOME% is the complete path of the ZENworks installation directory. Linux: /var/opt/novell/zenworks/content-repo/images If you need more disk space for large imaging files than is available in your current content repository location, you can change this location to a different partition. For more information, see “Content...
Page 22: Novell Preboot Services Menu
1.3.2 Novell Preboot Services Menu Where PXE is enabled on a device, the Novell Preboot Services Menu can be displayed during the boot process. The following menu choices are displayed on the menu: Start ZENworks Imaging: Executes the effective Preboot Services imaging bundle.
Page 23: Device Imaging Work Assignment
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. If you select to use IP addresses, you can provide a range of addresses in a list, or you can specify certain IP addresses.
Page 24 BIOS Version CPU Chipset Hard Drive Controller Hard Drive Size Hardware Type IP Address MAC Address Network Adapter Product Name Sound Card System Manufacturer Video Adapter Relationship: This defines the relationship for a filter between the Device component field and the value you specify for it.
Page 25: Server Referral List
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 imaging work.
Page 26: Intel Active Management Technology (Amt)
Services Imaging Server. 4. The DHCP server responds with an IP address for the device to use. 5. Novell-proxydhcp responds with the IP addresses of the TFTP server, as well as the filename of the Preboot Services bootstrap program ( nvlnbp.sys...
Page 27: Illustrating The Preboot Services Processes
“Standard DHCP and Novell Proxy DHCP Configured on Separate Servers” on page 27 “Standard DHCP and Novell Proxy DHCP Configured on the Same Server: Part A” on page 28 “Standard DHCP and Novell Proxy DHCP Configured on the Same Server: Part B” on page 29...
Page 28 3. Continue with “Phases 2 through 8: Continuing the Process” on page Standard DHCP and Novell Proxy DHCP Configured on the Same Server: Part A For this example, the DHCP server and the Preboot Services Imaging Server are configured on the same server on the network.
Page 29 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 1-3...
Page 30 “Phase 6” on page 32 “Phase 7” on page 33 “Phase 8” on page 33 Phase 2 Phase 2 of the Preboot Services Process Figure 1-4 Data Model Imaging novell-pbserv Server PXE Device novell-zmgprebootpolicy nvlnbp.sys nvlnbp.sys novell-tftp PXE BIOS novell-proxydhcp Processes: 1.
Page 31 Processes: 1. Hardware detection is performed by and it reads the image-safe data. nvlnbp.sys requests the Novell Preboot Services Menu configuration from the Data Model Nvlnbp.sys via novell-zmgprebootpolicy. 3. Novell-zmgprebootpolicy returns the Novell Preboot Services Menu configuration. In this case, the menu described in is displayed when a user presses the hot key.
Page 32 Processes: 1. Assuming no Novell Preboot Services Menu is displayed, the device asks the Data Model (via novell-zmgprebootpolicy) if any work is assigned. 2. Assuming work is assigned, novell-zmgprebootpolicy responds with the name of the configuration file to use in performing the preboot work ( for ZENworks Imaging z_auto.cfg...
Page 33 Phase 7 Phase 7 of the Preboot Services Process Figure 1-9 Data Model Imaging novell-pbserv Server PXE Device novell-zmgprebootpolicy pxelinux.0 novell-tftp PXE BIOS novell-proxydhcp Processes for ZENworks Imaging (as shown in the above illustration): requests and receives from the TFTP server.
Page 34: Preboot Strategies
Processes for ZENworks Third-Party Imaging: 1. WinPE distro is loaded and run on the device. 2. The Novell ZENworks Third Party Imaging utility requests the assigned Preboot Services work details and performs the work. 3. The image is laid down on the device and it automatically reboots.
Page 35: Creating, Installing, And Restoring Standard Images
When a device boots, the assigned bundle is automatically applied before the device’s operating system starts. You can also manually accomplish these tasks per device using the Novell Preboot Services Menu’s Start ZENworks Imaging Maintenance option to access the imaging maintenance mode prompt, if you have enabled the menu for the device.
Page 36: Reimaging Corrupted Devices
1.5.3 Reimaging Corrupted Devices Without data loss or undue disruption to users, you can fix devices that have become misconfigured or corrupted. 1. When a device needs to be fixed, have the user back up any files to the network that he or she wants to keep (if possible).
Page 37: 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 Configuration Management Imaging Agent (novell-ziswin) on each device. 2. If the devices are PXE-capable, make sure PXE is enabled (see Section 2.7, “Enabling PXE on...
Page 38 When using an Imaging bundle to perform multicasting, the Imaging Server is the session master, which sends the image file to the session participants. Novell-pbserv is used in this process. .zmg All problems are reported and displayed on the session master device.
Page 39 For a handful of devices, this might not be a problem. But for a larger number of devices, you should install the Novell ZENworks Configuration Management Imaging Agent (novell-ziswin) on each device before doing the multicast (see Section 2.8.2, “Enabling a Device for Imaging Operations,”...
Page 40 ZENworks 10 Configuration Management Preboot Services and Imaging Reference...
Page 41: Setting Up Preboot Services And Imaging
(novell-pbserv) makes all Primary Servers an Imaging Server. To avoid confusion, the Proxy DHCP service or daemon (novell-proxydhcp) is installed, but not enabled. For PXE devices to be able to communicate with Preboot Services, this service or daemon must be started manually on at least one server on each network segment.
Page 42: Preparing A Satellite With The Imaging Role
Imaging services on the device, and enables you to perform the Imaging operations in auto and maintenance mode. The Imaging components installed on the device include Novell ZENworks PXE Client Files, Novell ZENworks PXE Update Files, and Novell ZENworks Multicast Application (zmgmcast).The Imaging services installed on the device include Novell TFTP, ZENworks Preboot Policy (zmgpbpolicy), ZENworks Preboot (pbserv), and Novell Proxy DHCP.
Page 43: Illustrating The Preboot Services Processes On The Imaging Satellite
3. The device sends a DHCP discovery request to determine the IP address of the Imaging Satellite. 4. The DHCP server responds with an IP address for the device to use. 5. Novell-proxydhcp responds with the IP addresses of the TFTP server, as well as the filename of the Preboot Services bootstrap program ( nvlnbp.sys 6.
Page 44 Preboot Services Process for PXE Boot on the Imaging Satellite Figure 2-1 Data model DHCP port novell-zmgprebootpolicy novell-zmgprebootpolicy Request novell-tftp novell-tftp novell-pbserv novell-pbserv Primary Imaging novell-proxydhcp novell-proxydhcp Server Server port nvlnbp.sys BIOS IP Configuration port PXE Device DHCP Request Network Processes: 1.
Page 45 Preboot Services Process for ZENworks Imaging on the Imaging Satellite Figure 2-2 Data model novell-zmgprebootpolicy novell-pbserv Request novell-tftp novell-zmgprebootpolicy novell-pbserv novell-tftp Primary Imaging novell-proxydhcp novell-proxydhcp Server Server Image image.zmg Imaging Engine SUSE Linux Enterprise Server PXE Device Processes: 1. SUSE Linux Enterprise Server (SLES) is loaded and run on the device.
Page 46: Setting Up The Preboot Services Methods For Zenworks Imaging
2.3 Setting Up the Preboot Services Methods for ZENworks Imaging 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 47: Using Preboot Services (Pxe)
On the Imaging Server where ZENworks is installed, the file is located in: bootcd.iso Windows: %ZENWORKS_HOME%\bin\preboot\ Linux: /opt/novell/zenworks/preboot/bin/winutils/ 2 In an ISO editor, open the temporary copy of the file. bootcd.iso Setting Up Preboot Services and Imaging...
Page 48 On the Imaging Server where ZENworks is installed, the file is located in: settings.txt Windows: %ZENWORKS_HOME%\bin\preboot\ Linux: /opt/novell/zenworks/preboot/bin/winutils/ 4 Copy any other files or drivers that you want included on the CD or DVD to the addfiles directory in the temporary image. bootcd.iso...
Page 49: Configuring With Zenworks Imaging Media Creator
The zmgbootcd imaging utility is available at the following locations: https://primary_server_ID/zenworks-downloads/msi/novell-zenworks-zmgbootcd- 10.3.0.xxxxx.msi https://primary_server_ID/zenworks-downloads/rpm/novell-zenworks-zmgbootcd- 10.3.0-xxxxx.i586.rpm Creating a Boot CD or DVD without Additional Files If you do not want to include the file or any other files or drivers in the imaging boot settings.txt...
Page 50 Windows: %ZENWORKS_HOME%\bin\preboot\ Linux: /opt/novell/zenworks/zdm/winutils/ The Imaging Server copy of this file needs to be modified for your network environment and a working copy of it should be maintained at the root of the imaging boot device (imaging CD or DVD, or a blank floppy diskette). When burning the imaging CD or DVD, be sure to include the edited copy of this file.
Page 51 Windows: %ZENWORKS_HOME%\bin\preboot\ Linux: /opt/novell/zenworks/zdm/winutils/ For the Linux server path, to use a Windows management device to access to this directory you might need to configure Samba. The following dialog box is displayed: 2 Click Load, browse for and select the file, then click Open.
Page 52 Prompt for Configuration When Booting from Diskette: Specifies whether to prompt for these configuration settings when you boot a device with the bootable diskette and CD or DVD. If you leave this option deselected, the device boots using the configuration settings that you make here and you are not able to override the settings during bootup.
Page 53 5 (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).
Page 54 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 55 Windows: %ZENWORKS_HOME%\bin\preboot\ Linux: /opt/novell/zenworks/zdm/winutils/ For the Linux server path, to use a Windows management device to access to this directory you might need to configure Samba. The following dialog box is displayed after you click the Preboot Bootable Image tab:...
Page 56: Managing Zenworks Partitions
TFTP Relative Path: Specify the path for the PBI file, relative to the TFTP server’s default path. This is where the PBI file will be accessed by the device booting with PXE. Load: Load a previously defined PBI configuration file, which populates the fields on this page with its information.
Page 57 When you boot to Linux using any imaging boot device or method other than booting from the ZENworks partition, you can disable (or enable) the ZENworks partition. Just select the menu option to do so when the Novell Preboot Services Menu is presented. Removing a ZENworks Partition Because you should not delete the ZENworks partition if you booted using the partition, you should boot the device from an imaging boot method other than the ZENworks partition.
Page 58 “Using an Imaging Script Bundle” on page 58 “Using Fdisk” on page 58 Using an Imaging CD or DVD If you cannot perform a full restoration of the ZENworks partition at this time, you should consider removing it. To remove a ZENworks partition: 1 Boot the device using the ZENworks imaging CD or DVD.
Page 59: Deploying And Managing Preboot Services
Linux kernel, initrd, and nvlnbp.sys A PXE device uses this server to download the bootstrap program ( nvlnbp.sys novell-zmgprebootpolicy The PXE devices use this to check if there are any novell- Imaging bundles that are assigned to the device. zmgprebootpolicy. Novell ZENworks...
Page 60: Deploying Preboot Services In A Network Environment
Novell-proxydhcp must be started manually and does not need to be run on all Imaging Servers. While taking an image, the novell-pbserv service must be running on the server where the ZENworks image is to be stored. During restoring the image, the novell-pbserv service must be running on the server where the ZENworks image is located.
Page 61 PXE devices. The scope options should also specify the gateway or router that the PXE devices should use. If Preboot Services (specifically novell-proxydhcp) is installed on the same server as the DHCP server, the DHCP server must be configured with a special option tag. For more information, see “Configuring LAN Environments for Preboot Services”...
Page 62 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 63 In a WAN, the PXE device is usually separated from the Proxy DHCP and DHCP servers by one or more routers. The PXE device broadcasts for DHCP information, but by default the router does not forward the broadcast to the servers, causing the Preboot Services session to fail. In a VLAN (Virtual LAN) environment, the PXE device is logically separated from the Proxy DHCP server and the DHCP server by a switch.
Page 64 WAN/VLAN Configuration Differences Between the Same and Separate Servers Table 2-4 Information On the Same Server On Separate Servers Configuration The routers/switches have been A DHCP relay agent or IP helper is configured with IP helpers to forward configured on the router/switch serving network traffic to the DHCP server.
Page 65 You can install Configuration Management (which includes Preboot Services) on the same server where 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 novell-proxydhcp. See the steps in the previous section (“Configuring LAN Environments for Preboot Services”...
Page 66 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 67 Preboot Services session to be successful. The Preboot Services session uses the following destination ports: Destination Ports for Preboot Services Table 2-5 Component Port DHCP and Proxy DHCP servers UDP Ports 67, 68, and 4011 TFTP server UDP Port 69 novell-zmgprebootpolicy UDP Port 13331 Setting Up Preboot Services and Imaging...
Page 68: Administering Preboot Services
IMPORTANT: If the switch is acting as a firewall and limiting the type of traffic on the network, understand that novell-tftp and novell-zmgprebootpolicy are not firewall or network filter friendly. You should not attempt to run these services or 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 69 2 Edit the configuration settings according to the instructions within the file. 3 Save the changes. 4 On a command line, enter the following: Windows: In the Services dialog box, right-click Novell TFTP Service, then select Restart. Linux: /etc/init.d/novell-tftp restart...
Page 70 /etc/init.d/novell-pbserv restart Configuring Novell-zmgprebootpolicy Novell-zmgprebootpolicy 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:...
Page 71: Editing The Novell Preboot Services Menu
2.4.4 Editing the Novell Preboot Services Menu Depending on the configuration settings for Preboot Services in ZENworks Control Center, PXE devices might be able to display the Novell Preboot Services Menu during the boot process. The menu has the following options:...
Page 72 The following is the content of the default menu’s file: pxemenu.txt #This file describes a PXEMenu ScreenName = Novell Preboot Services Menu ScreenInfo = Version 2.0 July, 2007 MenuTitle = ZENworks Preboot Options FormatVersion = 2 #The screen colors determine the color of the main part of the menu screen...
Page 73: Configuring Preboot Services Defaults For Zenworks Imaging
For more information, see Section 2.6, “Overriding Preboot Services Defaults,” on page The following default settings can be configured in ZENworks Control Center: Section 2.5.1, “Configuring Novell Preboot Services Menu Options,” on page 74 Setting Up Preboot Services and Imaging...
Page 74: Configuring Novell Preboot Services Menu Options
Generally, if your Preboot Services work is completely automated, you should select to never display the Novell Preboot Services Menu on the device when it boots. Conversely, if you need to do manual Preboot Services functions for some or all devices, then select to always display the menu. A compromise is where you select to display the menu if Ctrl+Alt is pressed, allowing unattended Preboot Services work while allowing you the opportunity to display the menu when needed.
Page 75: Configuring Non-Registered Device Settings
4 Select one of the following: Always Show Imaging Menu Never Show Imaging Menu Show Imaging Menu if CTRL+ALT Pressed 5 To provide PXE boot options, specify them in the PXE Kernel Boot Parameters field. Each parameter should be separated by a space. 6 Click either Apply or OK to save the change.
Page 76 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.” Workgroup: Specify the Windows workgroup that you want the device to be a member of.
Page 77 If this option is used, the prefix you enter here is appended with a random string of letters and numbers to make the device name 15 characters long. Underscores and hyphens are valid in your prefix. The remaining random string uniquely names the device. For example, if you enter Lab1_, then ten other characters are randomly generated to complete the name with Lab1 separated from the random characters by the underscore for readability.
Page 78 If you select Specify Address List, perform the tasks contained in the following table: Task Steps Additional Details Add an IP address 1. In the IP Address After a device is imaged, IP settings range Configuration panel, click Add are applied to the device. The IP to open the Range Information address that gets assigned to the dialog box.
Page 79: Configuring Device Imaging Work Assignments
Task Steps Additional Details Remove specific 1. In the IP Address IP addresses from Configuration panel, click Edit the Range to open the Range Information Information dialog dialog box. 2. In the Used Address Ranges section, enter a specific IP address or a range of addresses in the Remove field, then click Remove.
Page 80 4 Configure the following: “Hardware Rules” on page 80 “Custom Hardware Types” on page 86 “Allow Overwrites” on page 90 5 Click either Apply or OK to save the changes. This sets the default imaging work assignments for devices registered in the Management Zone. Hardware Rules You can specify hardware-based rules for a Imaging bundle.
Page 81 Hardware Rules Tasks Table 2-7 Task Steps Additional Details Add a hardware rule 1. Click Add next to the Hardware The information that you configure in the Rules list box, which opens the Rule Construction dialog box comprises Rule Construction dialog box. one rule.
Page 82 Task Steps Additional Details Remove hardware 1. Select one or more hardware You can use the Ctrl or Shift keys to rules rules, then click Remove. select multiple hardware rules to remove them from the list. 2. Click Apply at the bottom of the configuration page to cause If you remove a hardware rule, any work removal of the rules from the list.
Page 83 Rule Name: This name is displayed in the rules listing on the Preboot Services page in the Device Imaging Work Assignment section. Make it descriptive enough that you can later remember its purpose. Bundle to Apply: When a device is seeking work to be done, it scans the rules until it finds a rule where all of the rule’s filters match the device, then executes the bundle assigned to the rule.
Page 84 Combine Filters Using: The default is to have filters ANDed and filter sets ORed. You can use this field to reverse these Boolean functions for the filters and sets. Using OR for filter sets means that all filters in a set must be matched to apply the rule, but any of the sets can be matched to apply the rule.
Page 85 Filters can be added individually or in sets. Each set contains logical operators within the set and logical operators determine the association between the sets. By default, the logical operator AND is displayed for the filters within a set in the Combine Filters Using field (which you can change), and OR is displayed in the Filter Sets Will Be Combined Using field (display-only).
Page 86 To determine what you need, consider the following possibilities: One filter set with multiple filters Multiple filter sets with only one or a few filters per set Multiple filter sets each with multiple filters Multiple rules per bundle Remember that the logical operators for filters within a set are the opposite of the operators between the sets, and all rules for a bundle use the OR condition.
Page 87 Custom Hardware Type Tasks Table 2-9 Task Steps Additional Details Add a custom 1. Click Add next to the Custom In the Custom Hardware Type dialog hardware type Hardware Types list box, which box you can add multiple strings, which opens the Custom Hardware Type identify specific hardware type dialog box.
Page 88 Task Steps Additional Details Remove custom 1. Select one or more custom You can use the Ctrl or Shift keys to hardware types hardware types, then click select multiple custom hardware types Remove. to remove them from the list. 2. Click OK to exit the dialog box and By removing a custom hardware type, save the deletions.
Page 89 Custom Hardware Type Tasks Table 2-10 Task Steps Additional Details Configure a custom 1. Specify a name for the custom The new custom type does not display hardware type type in the Hardware Type Name in the Rule Construction dialog box until field.
Page 90: Configuring The Server Referral List
Task Steps Additional Details Remove strings 1. In the Custom Hardware Type You can use the Ctrl or Shift keys to from the list dialog box, select one or more select multiple strings to remove them strings, then click Remove. from the list.
Page 91 Server Referral List Configuration Tasks Table 2-11 Task Steps Additional Details Add a server to the 1. In the List of Server IP Addresses You can add a range of IP addresses by server referral list and DNS Names field, specify the typing the beginning IP address, type a DNS name or IP address of a space, a dash, another space, then type...
Page 92 Location Files %ZENWORKS_HOME%\share\tftp\referral\zfd70 pxemenu.txt z_auto100.cfg z_maint100.cfg z_zpdis100.cfg z_zpen100.cfg To the following directory on the ZENworks 7 NetWare or Windows Imaging Server: NetWare: drive:\tftp Windows: drive:\Program Files\ZEN Preboot Services\tftp\data Do not replicate any directory structure from the ZENworks 10 server. Just copy the files to the directory.
Page 93 Location Files /srv/tftp/ memdisk nvlnbp.sys pxelinux.0 /srv/tftp/referral/zfd70/ pxemenu.txt z_auto100.cfg z_maint100.cfg z_zpdis100.cfg z_zpen100.cfg Copy the files to the following directory on the ZENworks 7 NetWare or Windows Imaging Server: NetWare: drive:\tftp Windows: drive:\Program Files\ZEN Preboot Services\tftp\data Do not replicate any directory structure from the ZENworks 10 server. Just copy the files to the directory.
Page 94: Configuring Intel Active Management Technology (Amt)
5 Click either Apply or OK to save the changes 2.6 Overriding Preboot Services Defaults You can determine which Novell Preboot Services Menu displays a configuration to use and whether the menu should be displayed on a device when it boots. By default, the Management Zone configuration applies to all folders and devices.
Page 95 To override the default configuration at the folder or device level: 1 In ZENworks Control Center, click the Devices in the left pane to display the Devices panel in the Managed tab. 2 Select one of the following in the Name column: The Details option next to the Servers or Workstations folder The Servers folder, then a server contained in the folder The Workstations folder, then a workstation contained in the folder...
Page 96: Enabling Pxe On Devices
Apply: Enables the change and retains focus on the page, so you can click Revert to temporarily disable the configuration change. 8 To temporarily disable the change, click Revert and the Management Zone settings for the menu remain in effect. 2.7 Enabling PXE on Devices To image a device using Preboot Services, you need to find out if the device is PXE capable, and then make sure that PXE is enabled.
Page 97: Verifying That Pxe Is Enabled On A Device
If the computer system does not have an integrated NIC, you might need to use NIC management software to configure your NIC to support PXE. Refer to your NIC documentation for support of PXE. 2.7.2 Verifying That PXE Is Enabled on a Device After you have activated PXE, it becomes available in the Boot section of the BIOS.
Page 98: Enabling A Device For Imaging Operations
Device Must Have Because Free disk space for a Unless you are using PXE, unattended operations require a ZENworks partition ZENworks partition to be installed on the device hard disk, so that the ZENworks Imaging Engine (optional) can gain control when booting. The default partition size is 150 MB, and the minimum partition size is 50 MB.
Page 99: Using Imaging
Using Imaging ® This section provides instructions on how to use Preboot Services imaging operations in Novell ® ZENworks 10 Configuration Management: Section 3.1, “Imaging Devices,” on page 99 Section 3.2, “Multicasting Images for ZENworks Imaging,” on page 122 Section 3.3, “Configuring Imaging Script Bundles for ZENworks Imaging,” on page 132 Section 3.4, “Assigning Imaging Bundles,”...
Page 100 “Creating and Configuring the Third-Party Image Bundle for Automatic Imaging” on page 105 “Using a Script to Image a Device” on page 106 Taking a Base Image of a Device A base image is an image of partitions and data on a source device’s hard disks. Normally, such an image is prepared with the intent to completely replace the contents of a target device’s hard disks.
Page 101 .gho CIFS or SMB share, and you must have the Write permission to it. If the Novell File Upload extension is not installed on the device, you must install it before you can browse to and upload the file. Image Filename: Specify the filename to save the .
Page 102 %ZENWORKS_HOME%\work\content-repo\images Primary Server and in on the Linux /var/opt/novell/zenworks/content-repo/images Primary Server, or on the device that is promoted to the Imaging Server role. However, the ZENworks images are not replicated from the Primary Server to other Primary Servers or Satellites.
Page 103 %ZENWORKS_HOME%\work\content-repo\images\addon-image The remainder of the path is fixed. For Linux servers, the path to the add-on image files is: /var/opt/novell/zenworks/content-repo/images/addon-image directory might not exist until the first add-on image has been created on the addon-image server. This directory is automatically created the first time you create an add-on image for a bundle,...
Page 104 111. Click the browse button to access the Server and Path Information dialog box: Server Object, IP, or DNS: The identity of the Imaging Server where the Novell ZENworks Configuration Management Imaging Agent (novell-ziswin) is installed and running, and where the base image file is stored.
Page 105 Consequently, it creates only one single partition on the destination hard disk. To prevent this issue, you must take an image by using ZENworks Control Center or the Novell ZENworks Third Party Imaging utility in the maintenance mode. To configure the Third-Party Imaging settings: 1 In ZENworks Control Center, click Bundles in the left pane to display the Bundles panel.
Page 106 The directory must be a Windows share or a Linux CIFS or SMB share, and .wim .gho you must have the Write permission to it. If the Novell File Upload extension is not installed on the device, you must install it before you can browse to and upload the file. Network Credential: Click...
Page 107: Using The Command Line For Zenworks Imaging
This example is a combination of automatic and manual tasks, where you define the bundle in ZENworks Control Center, assign it to the device, then when the device boots, it runs the bundle’s script, prompting you to insert the DVD containing an image into the device’s DVD drive. The script then runs the commands to restore the image on the device and ejects the DVD when finished.
Page 108 CD: Enter at the imaging maintenance mode (bash) prompt. manual PXE: Select Start ZENworks imaging maintenance from the Novell Preboot Services Menu. ZENworks Partition: Select Enable ZENworks Partition from the Novell Preboot Services Menu. 3 (Optional) At the prompt, type , then press Enter.
Page 109 NOTE: Unless you mount a drive before using , the image is created in RAM and is makel lost during a reboot of the device. In the above syntax, filepath is the image filename, including the extension (case- .zmg sensitive) and the complete path from the root of the partition where you want it locally stored.
Page 110 PXE: Select Start ZENworks imaging maintenance from the Novell Preboot Services Menu. ZENworks Partition: Select Enable ZENworks Partition from the Novell Preboot Services Menu. 3 Enter to display the ZENworks Imaging Engine menu. 4 (Optional) Click System information > Drive information to display a list of the partition slots on the device.
Page 111 1 Run the Image Explorer utility, which is located on the Imaging Server at: Windows: %ZENWORKS_HOME%\bin\preboot\zmgexp.bat Linux: /opt/novell/zenworks/preboot/bin/zmgexp 2 Drag files and folders from an existing device into a new image archive. For more information, see Section E.1, “Image Explorer (zmgexp),” on page 181.
Page 112 Resize a Partition in an Image: For base images, you can edit the value in the Original size text box to allow you to change how big the ZENworks Imaging Engine makes the partition when the image is restored. For more information, see “Changing a Partition’s Size”...
Page 113 3 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 2.3.1, “Using Preboot Services (PXE),” on page Boot the device using an imaging boot CD or DVD. For more information, see Section 2.3.2, “Preparing Imaging Boot CDs or DVDs,”...
Page 114 4 Depending on how you boot, do one of the following: CD: Enter at the imaging maintenance mode (bash) prompt. manual PXE: Select Start ZENworks imaging maintenance from the Novell Preboot Services Menu. ZENworks Partition: Select Enable ZENworks Partition from the Novell Preboot Services Menu. 5 Enter to display the ZENworks Imaging Engine menu.
Page 115 12 Click Next. Depending on the size of the image, it might take several minutes to restore the image. Images usually take slightly longer to apply than they do to take. 13 (Optional) Click System information > Drive information to display a list of the partition slots on the device.
Page 116 3. Select the devices or groups containing devices, then click OK to display the Assign Bundle Wizard page. 4. Click Next to display the Summary page, then click Finish to assign the devices to the bundle and exit the wizard. If you created the image manually, assign the image to a Preboot Image bundle, then assign that bundle to the devices to be imaged: 1.
Page 117: Setting Up Disconnected Imaging Operations
Image File Set Usages Table 3-1 Type of imaging How to specify the file set to use operation Automatic In the ZENworks Image Wizard in ZENworks Control Center, specify the number of (Preboot the file set in the File Set field. You must create the file set using the Image Explorer Services based utility.
Page 118 2 Boot the device by 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 2.3.1, “Using Preboot Services (PXE),” on page Boot the device by using an imaging boot CD or DVD. For more information, see Section 2.3.2, “Preparing Imaging Boot CDs or DVDs,”...
Page 119 12 Click Next. Depending on the size of the image, it might take several minutes to restore the image. Images usually take slightly longer to apply than they do to take. 13 When the imaging is done, remove the imaging boot media (if applicable) and reboot the device with the new image.
Page 120 compromise between compression time and image file size.) Path and image are the path and filename of the new image relative to the partition root. If you omit the partition number, the local ZENworks partition is used. For details on other related commands and parameters, see Appendix F, “ZENworks Imaging Engine Commands,”...
Page 121 Using the Imaging Maintenance Mode Prompt to Apply an Image 1 Boot the device by 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 2.3.1, “Using Preboot Services (PXE),” on page Boot the device by using an imaging boot CD or DVD.
Page 122: Multicasting Images For Zenworks Imaging
For details on this and other related commands and parameters, see Appendix F, “ZENworks Imaging Engine Commands,” on page 217. 10 Click Next. Depending on the size of the image, it might take several minutes to restore the image. Images usually take slightly longer to apply than they do to take.
Page 123 “Creating a Multicast Image Containing the Base Operating System, ZENworks Agent, and Add-on Application Image” on page 125 “Adding Participants to a Multicast Session” on page 125 “Enabling or Disabling a Multicast Image Set Bundle” on page 127 Configuring Multicast Image Set Bundles With Preboot Services, multicasting is an automated procedure.
Page 124 Windows: %ZENWORKS_HOME%\bin\preboot\zmgexp.bat Linux: /opt/novell/zenworks/preboot/bin/zmgexp 8 Fill in the fields: There are two triggers that you can use to determine when to start the ZENworks Multicast session. The fist trigger is the number of clients for a session and the second trigger is the time within which the clients need to connect to the session.
Page 125 Creating a Multicast Image Containing the Base Operating System, ZENworks Agent, and Add-on Application Image 1 Create the directory structure by using an add- C:\Program Files\Novell\ZENworks\work on image. For more information on creating an Addon image, see “Creating an Add-On Image for an Existing Bundle”...
Page 126 7 On the Summary tab for the device, click Advanced in the Imaging Work panel. 8 In the Scheduled Work field, select Apply Assigned Imaging Bundle, then click OK. This sets up a device to do Multicast Image Set bundle work for its effective bundle the next time it boots.
Page 127: Using The Command Line To Multicast An Image
When devices fulfilling the requirements that you defined in these steps boot, they can become part of the multicast session and be imaged from the image contained in the Multicast Image Set bundle. 7 (Conditional) If the multicast session needs to be enabled, continue with “Enabling or Disabling a Multicast Image Set Bundle”...
Page 128 “On Linux” on page 129 On Windows 1 In the Services window, determine whether the Novell ZENworks Preboot Service is running. If it is not running, then right-click the service and select Start. 2 On the command line, enter the following to enable a multicast session: %ZENWORKS_HOME%\bin\preboot\zmgmcast.exe -mcast arguments...
Page 129 If it is not running, then enter: /etc/init.d/novell-pbserv start 2 On the command line, enter the following 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: Argument Description...
Page 130 “Using the ZENworks Imaging Engine Menu to Perform the Multicast Session” on page 131 Using the Imaging Maintenance Mode Prompt to Perform the Multicast Session 1 (Optional) Install the Novell ZENworks Configuration Management Imaging Agent (novell- ziswin) on each of the participating devices.
Page 131 CD or DVD, or if it is PXE-enabled, boot it. 4 Enter at the prompt. manual Select Start ZENworks Imaging Maintenance from the Novell Preboot Services Menu. 5 To identify each participating device in the multicast session, type at the prompt to display the ZENworks Imaging Engine screen.
Page 132: Configuring Imaging Script Bundles For Zenworks Imaging
9 (Optional) If you chose Master in Step 8, click Specify additional options, click Next, then fill in the fields: Compression Level: Specify the compression level you want to use for this multicast session: None: No data compression is used. Data is sent immediately across the network to participating devices.
Page 133 5 Fill in the fields: Bundle 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 Imaging Script bundles that are listed together in a folder. For more information, see “Naming Conventions in ZENworks Control Center”...
Page 134: Assigning Imaging Bundles
Back: Allows you to make changes after reviewing the summary. Finish: Creates the Imaging Script bundle as configured per the settings listed on this Summary page. This bundle is not assigned to any device or group after it is created until you make that assignment on a Relationships tab.
Page 135: Assigning Devices To Bundle Groups
4 Click Add as necessary to include the desired bundles. 5 In the Shortcut Location section, make sure all check boxes are deselected. Imaging bundles do not use shortcut locations. 6 Click Next to display the Summary page. 7 Review the configuration, then click one of the following: Back: Allows you to make changes after reviewing the summary.
Page 136: Using The Bundles Tab To Assign Bundles
For information on adding to a new group, see “Creating Bundle Groups” in the ZENworks 10 Configuration Management Software Distribution Reference. 5 Click Add to open the Select Groups dialog box. 6 Select the groups and click OK. 7 Repeat this step as necessary to include the desired groups, then click Next to display the Summary page.
Page 137: Assigning Bundles To Non-Registered Devices
4b Click Add as necessary to include the desired devices. 4c In the Shortcut Location section, make sure all check boxes are deselected. Imaging bundles do not use shortcut locations. 4d Click Next to display the Summary page. 4e Click Finish to complete the assignment. 4f Repeat these steps until all of the desired devices have been assigned to the bundle.
Page 138: Editing Imaging Work
4 In the Bundle to Apply field, browse for and select the desired Imaging bundle. 5 Fill in remaining the fields to configure the type of device that you want to image in the multicast session. For more information on the Rule Construction dialog box, see “Rule Construction Dialog Box”...
Page 139 5 In the Imaging Work section, select one of the following from the drop-down list for the Scheduled Work field: Do Nothing: Review the image files: The Applied Image Files section displays the image files most recently applied to the device.
Page 140 The directory must be a Windows share or a Linux CIFS or .gho SMB share, and you must have the Write permission to it. If the Novell File Upload extension is not installed on the device, you must install it before you can browse to and upload the file.
Page 141 Imaging Bundle: To create a new image bundle, select the Create an Image Bundle option and configure the following options Name: Provide a name for the bundle. The bundle name must be different than the name of any other item (bundle, group, folder, and so forth) that resides in the same folder.
Page 142 142 ZENworks 10 Configuration Management Preboot Services and Imaging Reference...
Page 143: Imaging Operations In A Zenworks Asset Management Agent And Zenworks Desktop Management Agent Coexistence Environment
This takes a backup of DeviceGUID and DeviceID files, and subsequently deletes the files. The file is created in .sav zenworks_installation_directory/novell/zenworks ® 2 Launch ConsoleOne on the ZDM 7.x server, and create a task to take an image of the managed device.
Page 144: Restoring The Image
4.2 Restoring the Image The image of device that has the ZDM 7.x agent and the ZENworks Adaptive Agent with Asset Management installed can be restored in the following ways: Section 4.2.1, “Restoring the Image on the Same Device Whose Image was Taken,” on page 144 Section 4.2.2, “Restoring the Image to Another Device that Has Only the ZDM 7.x Agent Installed,”...
Page 145: Restoring The Image To A Non-Registered Device
The image is successfully restored to the device. After the image is restored, the ISD data and GUID of the device remain unchanged, and the device can communicate to both the ZDM 7.x server and the ZENworks Configuration Management server. In ZENworks Control Center, a new object is created within the Workstation folder of the Devices tab.
Page 146 146 ZENworks 10 Configuration Management Preboot Services and Imaging Reference...
Page 147: A Preboot Actions
Preboot Actions The Actions panel displays the action sets available for the bundle. Depending on the bundle type, the possible action sets are Install, Launch, Verify, Uninstall, Terminate, and Preboot. For example, if you select a Windows bundle, five actions sets are available. If you select an Imaging bundle, Preboot is the only action set available.
Page 148: Adding A New Imaging Script
Section A.1.1, “Adding a New Imaging Script,” on page 148 Section A.1.2, “Editing an Existing Imaging Script,” on page 148 A.1.1 Adding a New Imaging Script 1 Specify a script name in the Action Name field. 2 Specify the text of the script in the Script Text field. The script is restricted to doing imaging work prior to the device’s operating system startup.
Page 149: Action - Multicast Image Set
The add-on image is dynamically created from the linked application bundle when the imaging bundle is applied. However, you must create the add-on image in the application bundle in order for this to work. To link to the application bundle and create the add-on image in that bundle: 1 On the Actions tab of the Imaging bundle, then click Add in the Preboot section.
Page 150: Adding A Multicast Image Set
There are two triggers (elapsed time or number of clients joining) that you can use to determine when to start the multicast session. The first trigger to be encountered starts the session. These triggers are useful if you want economy of scale in having multiple clients join, but you don’t want to stall the session too long.
Page 151: Action - Zenworks Image
2 If necessary, change the number of clients needed in order to start the multicast session. 3 If necessary, change the time to wait before starting a multicast session if not enough clients have connected. 4 As necessary, edit the Items to be Included in the Multicast Session field. You can add or remove items, edit existing items, or change their order of execution.
Page 152: Action - Third Party Image
The directory must be a Windows share or a Linux Samba/ .wim CIFS share. If the Novell File Upload extension is not installed on the device, you must install it before you can browse to and upload the file. 4 In the Network Credential field, click...
Page 153 2 In the Image Type drop-down list, select the type of the image to be used in the bundle. 3 In the Shared Network Path for Image File field, specify the shared-network path where you want to save the or . files.
Page 154 154 ZENworks 10 Configuration Management Preboot Services and Imaging Reference...
Page 155: B File Sets And Image Numbers
File Sets and Image Numbers This section contains the following information: Section B.1, “File Sets,” on page 155 Section B.2, “Image Numbers,” on page 155 B.1 File Sets File sets allow you to create subsets of an image for applying to different devices. This is done by using a file set number that represents a version of the image where certain content is excluded.
Page 156 156 ZENworks 10 Configuration Management Preboot Services and Imaging Reference...
Page 157: C Replicating The Tftp Directory
Replicating the TFTP Directory ® ZENworks 10 Configuration Management allows you to replicate the changes made to the tftp directory on other Imaging servers (Primary Servers or Satellites with the Imaging role). directory contains files such as configuration files and binaries used by ZENworks tftp Configuration Management to perform imaging tasks.
Page 158 3 In the Master Primary Server to Start the TFTP Replication field, specify or click to browse for and select the Primary Imaging server whose directory changes you want to replicate tftp on all other servers in the zone. Ensure that there is no circular dependency on the selected Primary Server.
Page 159 Imaging server and messages.log loader-messages.log the master Primary server. zmd-messages.log file is located in %ZENWORKS_HOME%\logs\LocalStore\ on a Windows Satellite and /var/opt/novell/log/localstore/ on a Linux Satellite. loader-messages.log is located in %ZENWORKS_HOME%/log/ on a Windows Primary Server and /var/opt/novell/log/ zenworks/ on a Linux Primary Server.
Page 160: Configuring The Tftp Directory Replication Settings At The Folder Level
C.2 Configuring the TFTP Directory Replication Settings at the Folder Level To replicate the changes made to the directory on all the Imaging servers (Primary Server or tftp Satellite with the Imaging role) located within the folder: Servers Workstations 1 In ZENworks Control Center, click the Devices tab. The Managed tab is displayed by default.
Page 161: Configuring The Tftp Directory Replication Settings At The Device Level
6b (Conditional) If you do not want to replicate the directory changes on a specific tftp server within the folder, click Add in the Excluded Servers Servers Workstations pane, then select the server to be excluded. The server is added to the Excluded Servers list. 6c Configure the schedule when you want the directory changes to be replicated on the tftp...
Page 162 6 In the Preboot Services panel, click Override settings to enable you to configure the setting at the device level. 7 Configure the TFTP Replication Settings: 7a In the Master Primary Server to Start the TFTP Replication field, specify or click browse for and select the Primary Imaging server whose directory changes you want tftp...
Page 163: Understanding The Tftp Replication Schedule Types
If two tftp replication tasks are consecutively performed on a device and if the second task is triggered prior to the completion of the first task, only the changes in the last triggered replication (which is a cumulative of the first and the second tasks) are applied on the device. C.4 Understanding the TFTP Replication Schedule Types The following schedules are available:...
Page 164: Resolving Circular Dependency On The Master Primary Server
Monthly This schedule lets you specify one or more days during the month to run the event. Select Monthly, then fill in the following fields:. Day of the Month: Specifies the day of the month to run the event. Valid entries are 1 through 31.
Page 165: Resolving Circular Dependency At The Management Zone Level
To understand how circular dependency can occur at different levels in ZENworks Control Center and how to resolve it, review the followings sections: Section C.5.1, “Resolving Circular Dependency at the Management Zone Level,” on page 165 Section C.5.2, “Resolving Circular Dependency at the Folder Level,” on page 165 Section C.5.3, “Resolving Circular Dependency at the Device Level,”...
Page 166 166 ZENworks 10 Configuration Management Preboot Services and Imaging Reference...
Page 167: D Third-Party Imaging
Third-Party Imaging ® ® Novell ZENworks 10 Configuration Management supports Microsoft’s ImageX and Symantec Ghost 11.5 third-party imaging tools. ImageX takes the image in the WIM file format and Ghost takes the image in the GHO file format. NOTE: Third-party Imaging by using Ghost is not supported on Windows 7 and Windows 2008 R2 because Ghost is not yet supported on these platforms.
Page 168: Performing Zenworks Third-Party Imaging By Using Zenworks Control Center
ZENworks 10 Configuration Management supports only the default operations that are supported by the third-party Imaging tools. To perform advanced imaging operations that are not directly supported by ZENworks, you can use the third-party Imaging tools later. For more information on the third-party Imaging tools, see Section E.9, “TFTP Client for WinPE,”...
Page 169: Performing Zenworks Third-Party Imaging In The Maintenance Mode
\waik\tools\petools\x86 NOTE: If the Novell File Upload extension is not installed on the device, you must install it before you can browse to and upload the file. 2f Click OK. This downloads the Imaging files from server to the device running ZENworks Control Center and also uploads files from the device to the server.
Page 170: Taking An Image Of A Device And Storing It Locally
D.4.2 Taking an Image of a Device and Storing it Locally The Novell ZENworks Third Party Imaging utility allows you to take an image of an existing device and store it locally. The image can be used to image a similar device or reimage the same device.
Page 171: Taking An Image Of A Device And Storing It In A Remote Repository
D.4.3 Taking an Image of a Device and Storing it in a Remote Repository The Novell ZENworks Third Party Imaging utility allows you to take an image of an existing device and store it in a remote image repository on a shared-network path. The image can be used to image a similar device or reimage the same device.
Page 172 4 In the Include Partitions field, select the partition of the disk whose image you want to take. By default, the Include Partitions field displays all the partitions of the device on which the Novell ZENworks Third-Party Imaging utility is launched. NOTE: The drives displayed might not correlate with the original drives of the device. You must manually ensure that the correct drive is selected.
Page 173: Restoring A Locally Stored Image
D.4.4 Restoring a Locally Stored Image The Novell ZENworks Third Party Imaging utility allows you to restore a locally stored image on the device. 1 (Optional) If you want to change the destination disk structure before restoring a WIM image, perform the tasks explained in Section D.5, “Configuring the Destination Disk Structure Before...
Page 174: Restoring An Image To A Device On A Shared Network Location
D.4.5 Restoring an Image to a Device on a Shared Network Location The Novell ZENworks Third Party Imaging utility allows you to restore an image to the device on a shared-network path. 1 (Optional) If you want to change the destination disk structure before restoring a WIM image, perform the tasks explained in Section D.5, “Configuring the Destination Disk Structure Before...
Page 175: Adding, Deleting, Or Activating Disk Partitions
You must manually ensure that the correct drive is selected 8 Click OK. D.4.6 Adding, Deleting, or Activating Disk Partitions The Novell ZENworks Third Party Imaging utility allows you to create, delete, and activate disk partitions. Creating a Partition 1 Click the Partitioning menu >...
Page 176 A list of partitions available on the device, total disk space, and the free disk space on the device is displayed. Select the disk whose partition you want to modify. Note: The drives displayed might not correlate with the original drives of the device. You must manually ensure that the correct drive is selected.
Page 177: Querying For The Third-Party Imaging Work
3 Click Apply. D.4.7 Querying for the Third-Party Imaging Work In the Novell ZENworks Third Party Imaging utility, click the Imaging menu > Query for Work to query for any third-party imaging task assigned to the device. The device is not rebooted after this operation.
Page 178 You can configure the destination disk structure only if the image is restored in one of the following modes: Automatic Imaging mode For more information on the Automatic Imaging mode, see Section 3.1.1, “Using ZENworks Control Center for Imaging,” on page Maintenance Imaging mode without configuring the Advanced options.
Page 179 Drive - Letter to represent the partition. You must specify the disk settings in the following order: Partition Number, Type, Size, Offset, Active, FSType, Drive Third-Party Imaging 179...
Page 180 180 ZENworks 10 Configuration Management Preboot Services and Imaging Reference...
Page 181: E Imaging Utilities And Components
Section E.9, “TFTP Client for WinPE,” on page 216 E.1 Image Explorer (zmgexp) Use the Novell ZENworks Image Explorer utility to view or modify device images, create add-on images, compress image files, and split images. Section E.1.1, “Starting Image Explorer on ZENworks Server,” on page 181 Section E.1.2, “Installing and Starting the Image Explorer on a Standalone Device,”...
Page 182: Installing And Starting The Image Explorer On A Standalone Device
On Windows: You can install Java JRE in one of the following ways: ZENworks 10 Configuration Management SP3 Installation DVD: Copy from the DVD to the \common\msi\novell-zenworks-jdk-1.5.0_21.msi system drive, and run the installer. Java Web site: Download and install Java JRE 1.5 or later from the...
Page 183: Determining The Image Explorer Version
If Java is installed from the Java Web site, go to /opt/novell/zenworks/preboot/ and run the following command: java/lib java -Djava.library.path=/opt/novell/zenworks/preboot/lib -Xmx256m - jar ./zmgexp.jar If the Java is not set in the System path, then you must enter the following command: /usr/java/jdk-1_5_0_11/bin/java -Djava.library.path=/opt/novell/ zenworks/preboot/lib -Xmx256m -jar ./zmgexp.jar...
Page 184: Saving Image Changes And Exiting The Utility
E.1.6 Saving Image Changes and Exiting the Utility To save your changes when exiting the utility: 1 Click File > Save or Save As. For Windows, the default image location should open ( ...\content-repo\images For Linux, the file browser opens to the directory;...
Page 185 6 Save the image file to save your properties changes. 7 To close the properties dialog box, click OK. Viewing the Properties of an Image File Item 1 Click File > Open. For Windows, the default image location should open ( ...\content-repo\images For Linux, the file browser opens to the directory;...
Page 186: Image File Operations
6 Click OK to save the change. This only saves the partition size change. You must save the image file for it to be in effect the next time the image is applied. E.1.8 Image File Operations You can do the following with an image file: “Compressing an Image File”...
Page 187 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. Balanced Compression: Represents a compromise between compression time and image file size. This option is used by default when an image is created. Compress for Size: Creates the smallest image file but takes longer to compress.
Page 188 Image File to Split: Enter or browse to an existing base image file to split. Directory to Store Split Images: Specify the location and filename under which to save the split-image files, or click the browse button next to this field to locate and select it. The split-image files are named automatically.
Page 189 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. For Windows, the default image location should open ( ...\content-repo\images For Linux, the file browser opens to the directory;...
Page 190 2 Browse for and select the image file. Large image files might take a few moments to open. 3 Select the directories and files in the image that you want excluded from the image. Ways that you can select content: Click a single file in the right pane.
Page 191: Modifying Image Content
Extracting Content as an Add-on Image To extract a file or directory from the open image as an add-on image: 1 Click File > Open. For Windows, the default image location should open ( ...\content-repo\images For Linux, the file browser opens to the directory;...
Page 192 “Resizing a Partition” on page 193 “Adding a Windows Registry File” on page 193 Adding Directories and Files To add directories and files to the open image: 1 Click File > Open. For Windows, the default image location should open ( ...\content-repo\images For Linux, the file browser opens to the directory;...
Page 193: Creating A New Image File
Resizing a Partition You can resize the partitions in a base image, but not an add-on image. For more information, see “Changing a Partition’s Size” on page 185. Adding a Windows Registry File (Windows only) To add specific Windows registry settings that are to be applied after the open image is laid down: 1 Click File >...
Page 194: Novell Zenworks Configuration Management Imaging Agent (Novell-Ziswin)
E.2 Novell ZENworks Configuration Management Imaging Agent (novell-ziswin) The Novell ZENworks client (which includes novell-ziswin) should be installed on devices where you want to apply images. For information on installing the client on your devices, see the “Installing the ZENworks Adaptive Agent”...
Page 195: Novell Zenworks Isd Service (Novell-Zisdservice)
DNS hostname DNS servers By default, novell-ziswin runs automatically when the device boots up. You can delete the image- safe data from the Windows device by using one of the following ways: At the command prompt, execute the following command:...
Page 196: Understanding The Sid
DNS suffix DNS hostname DNS servers Novell-ziswin usually runs automatically. The ZENworks SIDchanger runs automatically after the image restoration on the Vista and Windows Server 2008 managed device. It runs within the ZENworks imaging distro, which is a Linux environment. Consequently, the SIDchanger changes the Windows SID within the Linux environment.
Page 197: Understanding The Zenworks Sidchanger
1 is the revision level. 5 is the identifier authority value. 12-7623811015-3361044348-030300820 is the domain or local computer identifier. 1013 is a relative ID (rid). A SID should be unique across different machines because duplicate SIDs can lead to problems if the machine or user must be uniquely identified.
Page 198: Disabling The Sidchanger
E.3.3 Disabling the SIDchanger You must disable the ZENworks SIDchanger by using either ziswin or Image Explorer if you want to use a third-party tool such a SYSPREP to change the SID. “Using Ziswin to Disable the SIDchanger” on page 198 “Using Image Explorer to Disable the SIDchanger”...
Page 199: Information Displayed By The Image-Safe Data Viewer
Category Information Image-safe Data Version: The version number of the Novell ZENworks Configuration Management Imaging Agent (novell-ziswin). 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 200: Using The Image-Safe Data Viewer
Category Information Workstation Identity If the device is a member of a Management Zone or there is image-safe Information data present: Zone GUID: The Management Zone that contains the device, if it has been imported. Device GUID: The Globally Unique Identifier of this computer’s device.
Page 201: Using The Image-Safe Data Editor
Command Explanation Displays information about a specific field or fields. field is one or more zisview -z field field names separated by a space. field is not case sensitive. All of the following are valid field names (the corresponding minimum names that can also be entered on the command line follow each field name in parenthesis): JustImaged (J)
Page 202: Zenworks Imaging Floppy Boot Disk Creator (Zmediacreator)
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 203: Imaging Configuration Parameters (Settings.txt)
For instructions on using the utility, see Section 2.3.3, “Configuring with ZENworks Imaging Media Creator,” on page E.6 Imaging Configuration Parameters (settings.txt) file contains parameters that control how the imaging boot process occurs. You settings.txt should maintain the working copy of at the root of the imaging boot device (CD or settings.txt...
Page 204 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 205 Specifies the list of DNS domain suffixes to be used to identify connections used by this device. Use a space to separate entries. For example: domain=example.novell.com example.xyz.org If DHCP is being used, leave this parameter commented out. PROXYADDR Specifies the IP address or full DNS name of the imaging (proxy) server to connect to when you boot a device from the imaging boot media in auto-imaging mode.
Page 206: Imaging Boot Parameter For Pcmcia Cards
.conf .conf arguments instead of parameters. The following ZENworks services or daemons run the Imaging Server processes: “Novell-pbserv” on page 207 “Novell-proxydhcp” on page 208 “Novell-tftp” on page 210 ZENworks 10 Configuration Management Preboot Services and Imaging Reference 2 0 6...
Page 207 “Novell-zmgprebootpolicy” on page 213 “Understanding the Arguments” on page 214 Novell-pbserv Novell-pbserv provides imaging services to devices. Novell-pbserv is started automatically when installing Configuration Management, or when rebooting the server. “Understanding the Novell-pbserv Components” on page 207 “Configuring Novell-pbserv” on page 207...
Page 208 /opt/novell/zenworks/preboot/lib By default, this is commented out. Novell-proxydhcp Novell-proxydhcp provides PXE devices with the information that they require to be able to connect to the ZENworks Preboot Services system. Novell-proxydhcp is not started automatically when installing Configuration Management. “Understanding the Novell-proxydhcp Components” on page 208 “Configuring novell-proxydhcp”...
Page 209 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 service or daemon. If no value is specified, the Proxy DHCP assumes that the service or daemon is running on the same server.
Page 210 Novell-proxydhcp is compliant with the following RFCs: RFC 2131 - Dynamic Host Configuration Protocol RFC 2132 - DHCP Options and BOOTP Vendor Extensions Novell-proxydhcp is compliant with the Preboot Execution Environment (PXE) Specification v2.1 industry specification, published by Intel. Novell-tftp Novell-tftp provides TFTP services to imaging clients.
Page 211 Ethernet segments; otherwise, use 1428. Older TFTP clients might be restricted to 512 bytes, which was 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 212 When the log file exceeds the TFTPLogFileSize value, it is deleted and restarted. By default, this parameter is commented out. Novell-tftp is compliant with the following RFCs: RFC 1350 -- THE TFTP PROTOCOL (REVISION2) RFC 2347 - TFTP Option Extension...
Page 213 Novell-zmgprebootpolicy Novell-zmgprebootpolicy allows PXE devices to query the Configuration Management system for work to do and for Preboot Menu policies. Novell-zmgprebootpolicy is started automatically when installing Configuration Management, or when rebooting the server. “Understanding the Novell-zmgprebootpolicy Components” on page 213 “Configuring Novell-zmgprebootpolicy”...
Page 214 Valid values are: 0, 1, 2, 3, and 4. The default is 2. Each message from the novell-zmgprebootpolicy server is assigned a priority level. If PolicyLogLevel is set to a value equal to or greater than a message’s priority level, that message is entered in novell-zmgprebootpolicy.log...
Page 215: Viewing Information About Imaging Requests
For Windows, open the Services dialog box, right-click the Novell service, then select Start. start setjustimagedflag (Linux only) For novell-ziswin only, sets the Just Imaged flag so that a device can be imaged by using its existing image-safe data. stop For Linux, stops the daemon.
Page 216: Starting A Manual Multicast Session
The information in Table E-14 explains what is displayed: Imaging Request Statistics Table E-14 Statistic Specifies PXE Requests The number of imaging requests of any kind that have been received by the Imaging Server since it was last started. This includes requests that failed, were denied, or were referred to other Imaging Servers.
Page 217: F Zenworks Imaging Engine Commands
After booting a device from an imaging boot media, you can use the command at the imaging ® ® maintenance mode prompt or use the Novell ZENworks Imaging Engine menu to do any of the following: Take an image of the device’s hard disks Restore an image on the device’s hard disks...
Page 218: Using The Zenworks Imaging Engine Menu For Help
In the ZENworks Imaging Engine menu, you can access help for legacy commands by clicking Help > Legacy Command-line Options. The legacy commands still work, but the newer ZENworks Configuration Management commands introduce added functionality. To use the Help mode: Section F.1.1, “Using the ZENworks Imaging Engine Menu for Help,”...
Page 219: Using The Zenworks Imaging Engine Menu To Query For Work
If any tasks involve storing or retrieving images with other Imaging Servers, the Imaging Server refers the ZENworks Imaging Engine to those servers to complete the 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 it.
Page 220: Make Locally
You can take an image of a device by using either the imaging maintenance mode prompt or by using the ZENworks Imaging Engine menu. For step-by-step instructions, see “Manually Taking an Image of a Device” on page 107. You can also use the Make Locally mode command to take an image of the device and store it in a partition on the local hard disk.
Page 221 7 Click Next to make the image. The ZENworks Imaging Engine Menu displays a progress bar while making image. 8 If the imaging process was successful, click OK in the Information dialog box, then click Close to return to a blank ZENworks Imaging Engine Menu display. If the imaging process was unsuccessful, determine and resolve the issue, then repeat these steps.
Page 222: Make To Proxy
Parameter Specifies -exclude=partition_number The partition number of a local partition to exclude from the image or include in the image. You can repeat this parameter as needed to exclude -x=partition_number or include multiple partitions. Available partitions can be displayed using img -dump -include=partition_number If you omit the exclude parameter, all partitions are included in the image...
Page 223 Compression: Specify any number from 0 to 9 where 0 means no compression, 1 means the least compression, and 9 means the most compression. 5 Click Next to continue. The next Make Image Wizard dialog box is displayed. 6 (Optional) Fill in the fields: Author: Specify who created the image file.
Page 224 Imaging Server: Windows: %ZENWORKS_HOME%\work\content-repo\images\ Linux: /var/opt/novell/zenworks/content-repo/images/ If no folders are specified in the path (added_path), the image is created in this images directory. A forward slash is not needed at the beginning of any added path.
Page 225: Restore Mode
F.4 Restore Mode Use the mode command to retrieve an image from a specified location and restore it to a -restore device. You can restore an image of a device by using either the imaging maintenance mode prompt or by using the ZENworks Imaging Engine menu.
Page 226 Path to Image Archive: Click Browse to select the image file, or specify its full path and filename, including the filename extension. .zmg File Set: The number of the image file set to be restored. Valid values are 1 through 10. File set 1 defaults.
Page 227 Parameter Specifies -ap=partition:partition 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 228: Restore From Proxy
F.4.2 Restore from Proxy Use the mode command to retrieve an image from an imaging (proxy) server -restore -proxy and restore it to the device. For more information, see “Manually Restoring an Image on a Device” on page 112. To use the Help mode: “Using the ZENworks Imaging Engine Menu to Restore an Image from a Proxy”...
Page 229 img -restore -proxy added_filepath/filename.zmg -ip=IP_address [-s=set] [-ap=advanced_options] where the [...] brackets indicate optional commands. To restore an Imaging bundle: img -restore -proxy bundle_name -ip=IP_address You can abbreviate , or -restore -proxy -r -proxy -restorep For more information, see: “Command Details” on page 229 “Examples”...
Page 230: Session Mode (Multicast Image Set)
Examples Restore Proxy Mode Examples Table F-9 Example Explanation img -restorep subdir1/ Removes all existing local partitions, retrieves the image from myimage.zmg subdir1/myimage.zmg on the Imaging Server, and restores the partitions and contents of that image on the available local writable devices (assuming there is sufficient local space).
Page 231: Multicasting Using The Zenworks Imaging Engine Menu
To use the Help mode: Section F.5.1, “Multicasting Using the ZENworks Imaging Engine Menu,” on page 231 Section F.5.2, “Multicasting Using the Imaging Maintenance Mode Prompt,” on page 231 F.5.1 Multicasting Using the ZENworks Imaging Engine Menu 1 To display the ZENworks Imaging Engine menu, enter: 2 Click Imaging >...
Page 232 You can abbreviate -session -master For more information, see: “Command Details” on page 232 “Examples” on page 233 Command Details Session Mode Commands and Parameters Table F-10 Parameter Specifies name The name of the multicast session. Each device joining the session uses the same value for this parameter.
Page 233: Partition Operations Mode
Parameter Specifies -comp=comp_level The amount of compression used when creating the image. Specify any number from 0-9. 0 means no compression. 1 is the same as Optimize for Speed and is used by default if you do not specify this parameter; 6 is similar to Balanced; and, 9 is the same as Optimize for Space, which provides the slowest performance.
Page 234: Using The Zenworks Imaging Engine Menu To Partition
Using the imaging maintenance mode prompt, the following example explains the syntax and available parameters that you can use with the various partition mode commands: img -pa partition_number img -pc partition_number -type=type [-size=size] [-cluster=cluster_size] img -pd partition_number img -pd -all The Partition mode can be used in two ways: Section F.6.1, “Using the ZENworks Imaging Engine Menu to Partition,”...
Page 235 Command Details Partition Mode Commands and Parameters Table F-12 Operation Action -pc partition_number type Creates a new partition, where: [size] [cluster=clusterSize] partition_number is the number of the partition slot (as displayed ) in which to create the partition img dump type is a keyword, a partition name, Extended, or a numerical value for the partition type, for example 0x0C (hexadecimal) or 11 (decimal)
Page 236: Zenworks Partition Management Mode
Example Explanation Creates a active partition in slot 1. img -pa 1 img -pa1 F.7 ZENworks Partition Management Mode Use the mode command to enable, disable, or remove the installed ZENworks partition. -zenpart To use the Help mode: Section F.7.1, “Using the ZENworks Imaging Engine Menu to Manage a Partition,” on page 236 Section F.7.2, “Using the Imaging Maintenance Mode Prompt to Manage a Partition,”...
Page 237: Dump Mode
IMPORTANT: If you remove an installed ZENworks partition, you must immediately restore a base image with a valid non-grub MBR (Master Boot Record). If you do not, the device cannot boot properly. 2 Enter to make this change effective. grub.s F.8 Dump Mode mode command provides information about the device’s hard drives and partitions.
Page 238: Information Mode
This data is saved by the Novell ZENworks Configuration Management Imaging Agent (novell-ziswin) during each device’s session to ensure that it can be restored after the device is reimaged. If the device is new and doesn’t have an operating system yet, an initial set of data is supplied from the default configuration for the ZENworks Management Zone, such as IP addresses.
Page 239: Using The Zenworks Imaging Engine Menu To View Device Information
F.9.1 Using the ZENworks Imaging Engine Menu to View Device Information 1 To display the ZENworks Imaging Engine menu, enter: 2 Click System information, then click Detected Hardware or Image-Safe Data. Table F-16 for details. F.9.2 Using the Imaging Maintenance Mode Prompt to View Device Information 1 Enter one of the following from the imaging maintenance mode prompt: img -info -hardware...
Page 240 Menu item or parameter Action System Information > Lists the data currently stored in the image-safe area on the device. The Image Safe Data items that comprise this data are listed in Section E.4, “Image-Safe Data Viewer and Editor (zisview and zisedit),” on page 198.
Page 241: G Updating Zenworks Imaging Resource Files
Updating ZENworks Imaging Resource Files ® ® In Novell ZENworks 10 Configuration 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 G.1, “The Linux Distribution for Imaging,”...
Page 242: Linuxrc
The SLES-based imaging distribution uses as the boot loader for imaging CDs, a isolinux modified for booting using PXE or when using a single diskette with the CD. If you pxelinux have a ZENworks partition installed, it uses the grub program to boot alternately between the ZENworks partition and the installed operating system.
Page 243: Zenworks.s
Linuxrc also loads a file system, which is combined with the file system that is set up root initrd by the boot loader. The file system is located on an imaging CD as the file root /boot/i386/root For PXE booting, the file system is stored on the ZENworks Imaging server as: root Windows:...
Page 244: Command Line Parameters And Variables
Some devices have a faulty BIOS, where you must turn off ACPI processing for the kernel to load properly. To do this, use the kernel parameter acpi=off. For more information, see Novell Support (http://www.novell.com/support/ search.do?cmd=displayKC&docType=kc&externalId=10099330&sliceId=&dialogID=128433 7&stateId=1%200%20548668). Linuxrc Parameters: These parameters affect the way linuxrc detects hardware or sets hardware settings.
Page 245: Modifying Zenworks Imaging Resource Files
/srv/tftp Server for PXE booting. This method is only available for Linux Imaging Servers, because the configuration files are provided by Novell’s version of PXE. You can modify files in the file systems, but you need a Linux environment for...
Page 246: 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 247 where is the path to the file and module is the name of the module. your_path module.ko Other files to be included in the file system should be copied to the appropriate initrd directory. 8 To re-package the file system, enter: initrd find .
Page 248: Using The Driverupdate File Method
G.4.3 Using the Driverupdate File Method Another way to customize the Novell imaging distribution is to utilize the driver update mechanism that is built into all SUSE distributions. This entails modifying a file named that is driverupdate located in the...
Page 249 The contents of the file should contain lines similar to those listed below. You dud.config should maintain the keywords by supplying your own data. However, you can use the listed values: UpdateName: ZENworks 10 Patch UpdateID: a37f92556e4dd99e UpdatePriority: 100 file should be an executable script that contains the following lines: adddir.s echo "Processing: adddir.s"...
Page 250: Adding Or Updating Lan Drivers
If you want to simply include a new hardware driver or kernel module in the imaging operating system, an easier process might be to copy the file into the /dirstruct/linux/suse/i386- directory. Then, the imaging operating system automatically loads any files that 9.2/modules/ are in this directory.
Page 251 -r This displays the kernel version of the Imaging distro. 2 From the Novell Downloads Web site (http://download.novell.com/patch/finder/ ?familyId=7261&productId=8162&yearValue=2009&keywords=kernel), download the kernel source RPM for the kernel version obtained in Step The kernel source RPM filename is in the following format: kernel-source-kernel_version.i586.rpm...
Page 252: Loading Drivers With Parameters
2 Change directories to the source and compile the source according to the compilation instructions provided in the module’s Readme. 3 When you have your module compiled for ZENworks, take the generated module file (make sure you select the proper module name and not a work file) and install it by using driver update method placing it in the...
Page 253: Linuxrc Parameters Specified In Settings.txt
Environment Variables Table G-2 Variable Definition HDPARM NO = Do not set hdparm parameters. IMGCMD Imaging command to run instead of the img -a command. MANUALREBOOT YES = Do not automatically reboot. PARTITIONSIZE Size in MB to create the ZENworks partition. PROXYADDR IP/DNS address of the Imaging server.
Page 254: Troubleshooting Linux Driver Problems
For example, hwinfo hwinfo -pci | less If you need to contact Novell Support for help, you should capture the output from hwinfo - to a file for their use. You can gather the most information with this command: hwinfo –pci –log /logfilename...
Page 255: H Supported Ethernet Cards
Supported Ethernet Cards ® ® Novell ZENworks Configuration 10 Management provides the Ethernet card drivers contained in the Linux kernel (2.6) that ships with ZENworks 10 Configuration Management. To determine which Linux kernel you are using, enter at the bash prompt.
Page 256 256 ZENworks 10 Configuration Management Preboot Services and Imaging Reference...
Page 257: Accessing Ip Addresses For Devices Running Dual Nics
Accessing IP Addresses for Devices Running Dual NICs To automatically obtain an IP address for a device running dual NICs, you can modify the following files (one or both): Windows: %ZENWORKS_HOME%\share\tftp\z_auto.cfg %ZENWORKS_HOME%\share\tftp\z_maint.cfg Linux: /srv/tftp/z_auto.cfg /srv/tftp/z_maint.cfg In these files, add the following line at the end of the append command: netdevice=eth0 This eliminates the need to manually select a NIC’s IP address.
Page 258 258 ZENworks 10 Configuration Management Preboot Services and Imaging Reference...
Page 259: J Troubleshooting Preboot Services And Imaging
Imaging The following sections provide solutions to the problems you might encounter while working with ® ® Novell ZENworks 10 Configuration Management Preboot Services and Imaging: Section J.1, “Preboot Services and Imaging Error Messages,” on page 259 Section J.2, “Troubleshooting Preboot Services and Imaging Services,” on page 261 J.1 Preboot Services and Imaging Error...
Page 260 Possible Cause: The bootp parameters, which are not compatible with ZENworks imaging, are used to provide the boot filename and the TFTP server’s IP address. Action: While using PXE boot to perform imaging operations, use the novell- proxydhcp service. 260 ZENworks 10 Configuration Management Preboot Services and Imaging Reference...
Page 261: Troubleshooting Preboot Services And Imaging Services
Automatic mode” on page 265 “How to enable debug logs?” on page 266 “The Novell Proxy DHCP service is automatically stopped on the Imaging Satellite” on page 266 “A new workstation ID is created after restoring image on a non-registered device” on page 266 “novell-pbserv crashes during multicast imaging to 120 or more devices”...
Page 262 Action: To download and install the Imaging tools to a specific drive on the device, enter the following command at the command prompt: msiexec -i novell-zenworks-zmgexplorer-10.3.0.xxxx.msi TARGETDIR:"complete_path_of_the_target_directory" For example, if you want to download and install the Imaging tools to...
Page 263 Step 2a Open a Web browser on the managed device to the following address: http://localhost:port_number. A message containing the Novell ZENworks Content Server version is displayed. 2b (Conditional) If the ZENworks Content Server version is not displayed, restart the ZENworks Adaptive Agent or the managed device.
Page 264 NOTE: The log file is available only until the device is rebooted. To retain the log file, you must upload it to an FTP server. How do I exclude a particular partition from ZENworks Imaging? Source: ZENworks 10 Configuration Management; Preboot Services and Imaging. Action: Before performing any imaging operation, set the following environment variable in the ZENworks Imaging Maintenance mode: export Exclude_DEVICE=partition_name...
Page 265 Server and Path Information dialog box during taking an image: Can't browse the file system on the specified server: com.novell.zenworks.datamodel.exceptions. InternalDataModelException: java.rmi.UnknownHostException: server_name. Possible Cause: The device running ZENworks Control Center is unable to resolve the server name that you select in the Server Object, IP, or DNS option in the Server and Path Information dialog box to its IP address.
Page 266 The Novell Proxy DHCP service is automatically stopped on the Imaging Satellite Source: ZENworks 10 Configuration Management; Preboot Services and Imaging. Explanation: If you manually start the Novell Proxy DHCP service on the Windows or Linux Imaging Satellite, the service is automatically stopped during the next device refresh schedule.
Page 267 In the Windows Services window, stop the Novell ZENworks Agent Service and change the service’s Startup Type to Manual. c. Reboot the device. 2. Take the image of the device that has the ZDM 7.x agent and the ZENworks Adaptive Agent with Asset Management installed.
Page 268 Java not installed... Action: Manually copy the contents of the directories from to the c:\programfiles\novell\zenworks ZENworks_Installation_drive\programfiles\novell\zenworks directory. Unable to change the preconfigured master Primary Server whose tftp directory changes you want to replicate on all other servers at a specific schedule Source: ZENworks 10 Configuration Management;...
Page 269 Explanation: You have configured a master Primary Server whose directory changes tftp you want to replicate on all other servers at a specific schedule. Subsequently, if you want to select a different server as the master Primary Server, the following error message is displayed in the TFTP Replication Settings panel when you click Apply after selecting the new server: Unable to apply the TFTP Replication settings.
Page 270 270 ZENworks 10 Configuration Management Preboot Services and Imaging Reference...
Page 271: K Documentation Updates
This section contains information on documentation content changes that were made in this Preboot ® ® Services and Imaging Reference for Novell ZENworks 10 Configuration Management SP3. The information can help you to keep current on updates to the documentation.
Page 272 Location Update Section E.3, “Novell Added the following note: ZENworks ISD Service (novell-zisdservice),” on NOTE: After installing the ZENworks Adaptive Agent on a Windows 7 page 195 device or Windows Server 2008 R2 and subsequently rebooting the devices, only the device ID and the device GUID are written into the ISD.

This manual is also suitable for:

Zenworks 10 configuration management sp3

Novell ZENWORKS 10 CONFIGURATION MANAGEMENT SP3 - PREBOOT SERVICES AND IMAGING REFERENCE 10.3 16-04-2010 User Manual

About this Guide

1 Overview

2 Setting up Preboot Services and Imaging

3 Using Imaging

4 Imaging Operations in a Zenworks Asset Management Agent and Zenworks Desktop Management Agent Coexistence Environment

A Preboot Actions

B File Sets and Image Numbers

C Replicating the TFTP Directory

D Third-Party Imaging

E Imaging Utilities and Components

F Zenworks Imaging Engine Commands

G Updating Zenworks Imaging Resource Files

H Supported Ethernet Cards

Accessing IP Addresses for Devices Running Dual Nics

J Troubleshooting Preboot Services and Imaging

K Documentation Updates

Quick Links

Troubleshooting

Related Manuals for Novell ZENWORKS 10 CONFIGURATION MANAGEMENT SP3 - PREBOOT SERVICES AND IMAGING REFERENCE 10.3 16-04-2010

Summary of Contents for Novell ZENWORKS 10 CONFIGURATION MANAGEMENT SP3 - PREBOOT SERVICES AND IMAGING REFERENCE 10.3 16-04-2010

This manual is also suitable for:

Table of Contents