30.1 Imaging Devices

Preboot Services provides tools for creating and compressing images of device hard disks, as well as images of specific add-on applications or file sets. ZENworks Linux Management also provides tools for customizing such images and for making images available to auto-imaging operations.

You can take images of devices, re-image them with those images, and image other devices with the images. In ZENworks 7.3 Linux Management, the available devices are servers and workstations.

ZENworks Linux Management imaging supports devices that physically connect to the network that meet the minimum requirements for devices. ZENworks Linux Management imaging does not support imaging operations (creating or restoring images) using wireless connectivity. Devices with logical volumes (LVMs) are not supported for imaging.

NOTE:ZENworks Linux Management imaging does not support devices running boot managers, such as System Commander. Boot managers create their own information in the MBR and overwrite the ZENworks boot system, which prevents the device from communicating with the imaging server. If you are using boot managers in your environment, you should disable or remove them before performing imaging operations.

Some imaging tasks can be performed manually on a device, some in the ZENworks Control Center, and some in both:

30.1.1 Imaging Using the ZENworks Control Center

The following imaging tasks are available in the ZENworks Control Center:

Taking a Base Image of a Device

A base image is an image of all 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.

You can take an image of an existing device and use it to image a similar device, or use it as a backup image for reimaging the device.

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

    Devices tab’s New menu options

  2. Click Servers or Workstations, then select the check box next to a device.

    This selects the device for taking the image.

  3. Click Actions > Take image.

    You can also select the check box next to Servers or Workstations to start this wizard, then click Actions > Take image. If you do so, you are asked to select a device from the group. Then the File Information page is displayed.

  4. Click Next to display the File Information page:

    Step 1 page for creating a new bundle: File Information (Server and File Path, Use Compression, and Create an Image Bundle fields)

  5. Fill in the fields:

    Server and file path: (Required) Browse for the object, DNS name, or IP address of the server where the image file is to be stored, then specify the path to the storage location. This must be a server where ZENworks Linux Management is installed.

    Images can take up a large amount of disk space. Make sure your imaging server has the disk space available before selecting it.

    Use compression: Compression is required. Choose one of the following:

    • Balanced: Automatically balances compression between an average of the reimaging speed and the available disk space for the image file.

    • Optimize for speed: Optimizes the compression to allow for the fastest reimaging time. Use this option if CPU speed is an issue.

    • Optimize for space: Optimizes the compression to minimize the image file’s size to conserve disk space. This can cause reimaging to take longer.

    Create an image bundle: If you select this option, another wizard page is displayed (see Step 6) where you can configure the new bundle. Otherwise, the Summary is your next wizard page (skip to Step 9).

  6. If you selected to create an image bundle, the New Image Bundle page is displayed:

    Step 2 page for creating a new bundle: New Image Bundle (Name, Destination Folder, and Description fields)

  7. Fill in the fields:

    Name: Specify a unique name for the bundle, because many other bundle names might be listed in the same folder.

    For more information, see Section C.0, Naming Conventions in the ZENworks Control Center.

    Destination folder: Specify a folder where you want to list the new bundle. This is a location in the ZENworks Control Center, not a file location on a device.

    Description: Enter information to help you later recognize the purpose and scope of this image bundle. For example, “Image taken after Linux OS was installed, but before GroupWise was installed.”

  8. Click Next to display the Summary page.

  9. Review the configuration, then click one of the following:

    Back: Allows you to make changes after reviewing the summary.

    Finish: Click to take the image. If you completed Step 7, the image is assigned to the bundle when it is created.

This base image can be used in Step 8 under Configuring the ZENworks Image Bundle for Automatic Imaging.

To create an add-on image for use in Step 8, see Creating an Add-On Image.

Configuring the ZENworks Image Bundle for Automatic Imaging

Using ZENworks Linux Management, you can install software using a bundle. Software included in a bundle that is assigned directly is considered mandatory; the software is installed on all assigned devices (the bundle is directly assigned to the devices, their groups, or their folders).

To configure a ZENworks Image bundle and assign devices to the bundle:

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

    Bundles tab’s New menu options

  2. Click New > Bundle to start the Create New Bundle Wizard:

    Step 1 page for creating a new bundle: Select Bundle Type

  3. In the Create New Bundle Wizard, select Preboot bundle, then click Next.

    Step 2 page for creating a new bundle: Select Preboot Bundle Type

  4. On the Select Preboot Bundle Type page, select ZENworks Image bundle.

  5. Click Next to display the Set General Information page:

    Step 3 page for creating a new bundle: Set General Information (Name, Folder, and Description fields)

  6. Fill in the fields:

    Name: (Required) Although bundles can be identified in ZENworks Control Center by their type of icon, as well as the folder they are listed under, you should develop a naming scheme that differentiates the ZENworks Image bundles that are listed together in a folder.

    For more information, see Section C.0, Naming Conventions in the ZENworks Control Center.

    Folder: Browse for the location where you want the ZENworks Image bundle displayed in ZENworks Control Center. The folder must exist. You cannot specify a non-existent folder, because ZENworks does not create them from this wizard.

    Description: Provide a description to help you later recognize the exact purpose of this ZENworks Image bundle.

  7. Click Next to display the Bundle Configuration page:

    Step 4 page for creating a new bundle: Preboot Bundle Creation (Base Image File, Add-On Image Files, and File Set fields)

  8. Fill in the fields:

    Base image file: This is an image file existing on an imaging server. You must provide the full path and filename here. The image filename must end in .zmg (case-sensitive). For information on creating a base image, see Taking a Base Image of a Device.

    Add-on image files: These are existing image files that you can add onto the device after it is re-imaged with the base image file. You must provide the full paths and filenames here. The image filename must end in .zmg (case-sensitive). For information on creating an add-on image, see Creating an Add-On Image.

    File set: File sets are assigned to the current ZENworks Image bundle using this File set field. File sets are defined on the imaging server from the base image using the Image Explorer utility, which can be run on a Windows device from a Linux server running Samba. The Image Explorer utility is located at /opt/novel/zenworks/zdm/winutils/ImgExp.exe on the Linux server.

    When you define a file set using Image Explorer, you specify files and directories to be excluded from the image. Thus, a file set is a subset of the original image that excludes the files you select in Image Explorer. A separate image file is not created for the file set; instead, a file set contains internal attributes representing the excluded information. Therefore, even though a file set does not exist as a separate, physical image file, it is accessed as though it is, placing the image on the receiving device, minus the excluded files.

    For example, device1image.zmg is the image file on your imaging server. You use Image Explorer to determine which data to exclude and assign this to a file set number, such as 2. When a device assigned to this ZENworks Image bundle boots, it is imaged with the smaller version (file set 2) of device1image.zmg.

    File sets provide an advantage because you can create a base image and modify it slightly for various devices, instead of creating separate, somewhat different base images for each device. However, because file sets only concern excluded files, if you add files to the base image using Image Explorer, all file sets will include those additional files. If you don’t want them included in a file set, you must use Image Explorer to exclude these new files from that file set.

    There are a maximum of 10 file sets. Each of the ten file set numbers represents the original base image, until you use Image Explorer and assign the results to a file set number.

    IMPORTANT:If you create 10 different file sets, the original image can be lost. If you want to maintain the original image’s information, do not use Image Explorer to assign exclusions to file set 1, which is the default file set if you don’t select a file set when using this wizard.

    Add: Accesses the Server and Path Information dialog box:

    • Server object, IP, or DNS: The identity of the imaging server where the Novell ZENworks Linux Management Imaging Agent (novell-zislnx) is installed and running, and where the base image file is stored.

    • File path on server: The full path to the base image file.

    A device’s Image Safe Data, such as the device’s IP address and other identity information that is defined for its ZENworks Control Center object, is contained on the hard drive that the device boots from. This information can be lost if that hard drive needs to be replaced. However, the following options allow you to retain a device’s IP address and other identity information when replacing the hard drive.

    These options are only applicable when this Preboot bundle is applied to a specific device. The image used in this bundle must contain the device’s previous IP address and ZENworks Control Center object information.

    (Optional) Select one or both of the following options:

    • Use the IP Address from Content in the Preboot Bundle Rather Than from the Device’s Image Safe Data  

      Use this option if you have previously taken an image of the device and are using that image with this Preboot bundle. This option causes the imaging process to write the device’s IP address that is contained in this image to the Image Safe Data location on the replacement hard drive.

      Do not use this option if the image being used for this bundle was not previously made from this device.

      If you do not select this option, then:

      • If the device that this Preboot bundle is applied to is still using its primary hard drive to boot from, the IP address in its Image Safe Data continues to be used.

        or

      • If the device that this Preboot bundle is applied to has been given a new hard drive to boot from, but you do not have a previous image of the old hard drive, then the IP address is assigned according to your ZENworks Management Zone configuration for non-registered devices.

    • Use the Identity Information from Content in the Preboot Bundle Rather Than from the Device’s Image Safe Data  

      If you are using a previous image of this device, this option writes ZENworks Control Center object identity information as contained in the image to the new hard drive’s Image Safe Data location, which allows the device to retain its ZENworks Control Center object.

      However, if the image contained in this bundle was not previously made from this device, it receives the new ZENworks Control Center object that is defined in the image.

      If you do not select this option and the device that this Preboot bundle is applied to has been given a new hard drive to boot from, then a new ZENworks Control Center object is created according to your ZENworks Management Zone configuration for non-registered devices.

  9. Click Next to display the Summary page.

  10. Review the configuration, then click one of the following:

    Back: Allows you to make changes after reviewing the summary.

    Next: Click to perform the following tasks before creating the bundle:

    • Specify device assignments for this bundle

    • Specify groups for this bundle

    Continue with Section 30.6, Assigning Unassigned Preboot Bundles to assign the bundle and complete the wizard.

    Finish: Creates the ZENworks 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, unless you click Next instead of Finish to make that assignment.

IMPORTANT:If this Preboot bundle has been created on a management device inside the firewall and you are assigning it to a device outside the firewall, port 8089 must be open both ways (PUBLIC -> PRIVATE, and PUBLIC <- PRIVATE).

When a device assigned to the ZENworks Image bundle boots, the bundle’s work is performed on the device before its operating system starts.

Imaging a Device Using a Script

You can perform scripted imaging using the ZENworks Script bundle. Any imaging commands can be entered for the script.

For example, if you want to mount a DVD and restore an image from it, you could enter something similar to the following in the Script text field in the Create New Preboot Bundle Wizard when defining a ZENworks Script bundle:

echo "Please insert the DVD containing the image into the drive."
mount /dev/cdrom /mnt/cdrom
img rl /mnt/cdrom/myimagefile.zmg
umount /mnt/cdrom
eject /dev/cdrom

This example is a combination of automatic and manual tasks, where you define the bundle in the 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.

For information on creating a ZENworks Script bundle, see Section 30.4, Configuring ZENworks Script Bundles.

30.1.2 Performing Manual Imaging Tasks

The following manual imaging tasks are available:

These instructions assume that you have already prepared the imaging server (see Section 29.1, Preparing a Preboot Services Server), prepared devices for imaging (see Section 29.7, Setting Up Devices for Imaging), and set up imaging defaults (Section 29.4, Configuring Preboot Services Defaults).

ZENworks Linux Management imaging supports devices that physically connect to the network and that meet the minimum requirements for devices. ZENworks Linux Management imaging does not support imaging operations (creating or restoring images) using wireless connectivity.

Manually Taking an Image of a Device

This section explains how to take an image of a device by booting from an imaging method and entering a particular imaging command. The image is stored on your imaging server.

If you want to store an image locally rather than on an imaging server, see Using a CD or DVD for Disconnected Imaging Operations and Using a Hard Disk for Disconnected Imaging Operations.

Ensure that your imaging server has enough disk space for the image. Otherwise, you receive a “Failed to write to proxy” error.

The following sections contain additional information:

Manually Taking an Image of a Device Using the Bash Prompt

  1. Boot the device using one of the following methods:

  2. Enter manual at the bash prompt.

    or

    Select Start ZENworks imaging maintenance from the Preboot Services Menu.

  3. (Optional) At the bash prompt, type img dump, then press Enter.

    This displays a list of the partition slots on the device. For your reference, note the number and type of partitions and which one is active.

  4. Enter a command at the bash prompt using one of the following formats:

    • To create an image and store it on the imaging server, enter:

      img makep serverIPaddr_or_DNSname //uncpath/newimg.zmg [comp=comp level]

      The makep parameter stands for “make on proxy,” which creates an image and stores it on the imaging (proxy) server.

      The IP address or DNS name should be that of your imaging server.

      The UNC path specifies the location and filename where the new image is to be stored.

      The .zmg filename extension is case-sensitive.

      The directories in the path must exist. You can use the following characters in the path and filename:

      • Letters: a through z (uppercase and lowercase)

      • Numbers

      • Special Characters: $ % ' - _ @ { } ~ ` ! # ( )

      comp level is 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 the same as Balanced. 9 is the same as Optimize for space. (Optimize for speed takes the least amount of time but creates the largest image file. Optimize for space creates the smallest image file but might take a significant amount of time. Balanced is a compromise between compression time and image file size.)

      For example:

      img makep 137.65.95.127 //xyz_srv/sys/imgs/cpqnt.zmg comp=6

    • To create an image and store it locally, enter:

      img makel filepath [comp=comp level]

      The makel parameter stands for “make locally,” which creates an image and stores it on a local hard disk.

      NOTE:Unless you mount a drive before using makel, the image is created in RAM and is lost during a reboot of the device.

      filepath is the image filename, including the .zmg extension (case-sensitive) and the complete path from the root of the partition.

      The directories in the path must exist. You can use the following characters in the path and filename:

      • Letters: a through z (uppercase and lowercase)

      • Numbers

      • Special Characters: $ % ' - _ @ { } ~ ` ! # ( )

      comp level is 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 the same as Balanced. 9 is the same as Optimize for space. (Optimize for speed takes the least amount of time but creates the largest image file. Optimize for space creates the smallest image file but might take a significant amount of time. Balanced is a compromise between compression time and image file size.)

      For example:

      img makel /imgs/dellnt.zmg comp=6

    IMPORTANT:Make sure to use forward slashes in the UNC path as shown above. Backslashes are not recognized by Linux. Or, you can use backslashes and enclose the entire UNC path in quotes. The path you specify must exist on your imaging server.

    For more information on the parameters you can use and usage examples, see Section E.3, Make Mode (img make).

    Depending on the amount of data on the hard disk, the image might take several minutes to create. If the screen goes blank, just press any key. (Linux enters a screen-saving mode after a few minutes.)

  5. After the image is created and the bash prompt is displayed, remove any CD or DVD from the drive and reboot the device.

  6. (Optional) Verify that the image file was created on your imaging server. You might also want to check its size.

Manually Taking an Image of a Device Using the ZENworks Imaging Engine Menu

  1. Boot the device using one of the following methods:

  2. Enter manual at the bash prompt.

    or

    Select Start ZENworks imaging maintenance from the Preboot Services Menu.

  3. Enter img 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.

    For your reference, note the number and type of partitions and which one is active.

  5. Click Imaging > Make image.

  6. In the Make Image Wizard window, specify the destination where the image is stored (Local or Server), then click Next.

    The directories in the path must exist. You can use the following characters in the path and filename:

    • Letters: a through z (uppercase and lowercase)

    • Numbers

    • Special Characters: $ % ' - _ @ { } ~ ` ! # ( )

  7. Browse to and specify the path to the image archive.

  8. Select the partitions that you want to include in the image.

  9. Select a compression option:

    None: No compression is used.

    Speed: Takes the least amount of time to compress but creates the largest compressed image file. This option is used by default when an image is created.

    Balanced: Represents a compromise between compression time and image file size.

    Size: Creates the smallest image file but takes longer to compress.

  10. Click Next.

  11. (Optional) Fill in the fields:

    Author: The name of the person creating this image.

    Computer: The name of the computer being imaged.

    Image description: A description of the image.

    Comments: Any additional comments about the image.

  12. Click Next.

    Depending on the amount of data on the hard disk, the image might take several minutes to create. If the screen goes blank, just press any key. (Linux enters a screen-saving mode after a few minutes.)

  13. After the image is created, exit from the ZENworks Imaging Engine menu, remove any CD or DVD from the drive, then reboot the device.

  14. (Optional) Verify that the image file was created on your imaging server. You might also want to check its size.

Using Image Explorer to Customize an Image

After you have created a base or add-on image as explained in the previous sections, you can customize it with the Image Explorer utility. Specifically, you can:

  • Compress the image: You can compress an image (including images created by previous versions of ZENworks Linux Management) to 40-60% of the original file size, if you have not done so already during the imaging process. There are three compression options. Optimize for speed takes the least amount of time but creates the largest compressed image file. Optimize for space creates the smallest image file but might take a significant amount of time. Balanced is a compromise between compression time and image file size. This option is used by default when an image is created.

    ZENworks Linux Management provides the following compression methods:

  • Split the image: You can specify a device image file that you want to split into separate files so that the entire image can be spanned across several CDs or DVDs. Splitting a device image is helpful for putting down or restoring images in a disconnected environment. For more information, see Section D.1.15, Splitting an Image.

  • 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 Section D.1.16, Resizing a Partition in an Image.

  • Purge deleted files: Excluded or hidden files and folders can be completely removed from an open image. This saves space in the image if you no longer want to include the files. For more information, see Section D.1.5, Excluding a File or Folder from a File Set in the Open Image.

  • Exclude individual files and folders from the image: In doing this, you create subsets of the image by specifying which of ten possible file sets to exclude a given file or folder from. This exists merely as internal attributes of the same image archive. For more information, see Section D.1.7, Purging Files and Folders Marked for Deletion from the Open Image.

    IMPORTANT:Do not exclude BPB files from a base image or the device won’t be able to boot the new operating system after receiving the image.

  • Add files and folders to the image: By default, any file or folder you add is included in all file sets. To change this, you must explicitly exclude the file or folder from one or more file sets. For more information, see Section D.1.3, Adding a File or Folder to an Open Image.

For information on starting Image Explorer, see Section D.1, Image Explorer (imgexp.exe).

Creating an Add-On Image

An add-on image is an archived collection of files to be applied to an existing installation on a target device. This is sometimes referred to as an application overlay. The existing partitions and files on the target device are left intact, except for any files that the add-on image might update.

An add-on image typically corresponds to an application or utility, or simply to a set of data files or configuration settings.

To create an add-on image:

  1. Run the Image Explorer utility, which is located on the Linux imaging server at:

    /opt/novell/zenworks/zdm/winutils/ImgExp.exe

  2. Drag files and folders from an existing device into a new image archive.

    For more information, see Section D.1, Image Explorer (imgexp.exe).

  3. Save this image with the .zmg extension (case-sensitive) in the same directory on the imaging server where you store base images.

    Generally, an add-on image created in this manner doesn’t require any post-processing on the target device. It is simply a set of files that are copied to the appropriate locations on the hard disk, much like what happens when you unzip an archive. For more information, see Using Image Explorer to Customize an Image.

This add-on image can be used in Step 8 under Configuring the ZENworks Image Bundle for Automatic Imaging.

Manually Putting an Image on a Device

The section explains how to put an image on the device by booting from an imaging method and entering a particular imaging command. The image is retrieved from your imaging server.

Ensure that the device receiving a new image has enough disk space for the image. Otherwise, you receive a “Failed to write to proxy” error.

The following sections contain additional information:

Manually Putting an Image on a Device Using the Bash Prompt

  1. If you haven’t already done so, create the image to put on the device, as instructed in Manually Taking an Image of a Device.

    Make sure that the image is of the same type of device (same hardware configuration) and is stored on your imaging server. You can use a previous image of the same device.

    IMPORTANT:If you are putting an image on a device without a ZENworks partition, make sure the image was made on a device without a ZENworks partition. Otherwise, the wrong MBR (Master Boot Record) is restored, and the device fails to boot.

  2. (Optional) Boot the device from a Windows startup disk and run fdisk to remove all partitions from the hard disk.

    Running fdisk is not required, but it is recommended for purposes of comparing workstation or server partitions before and after the imaging operation.

  3. Boot the device using one of the following methods:

  4. Enter manual at the bash prompt.

    This step is not the same as in the previous step’s manual processes.

  5. (Optional) At the bash prompt, type img dump, then press Enter to display a list of the partition slots on the device.

    For your reference, note the number and type of partitions and which one is active. If you removed all partitions using fdisk, each slot should be empty and none should be active.

  6. Enter a command at the bash prompt using one of the following formats:

    • To restore an image from the imaging server and put it down on a device, enter:

      img restorep serverIPaddr_or_DNSname //uncpath/newimg.zmg

      The restorep parameter stands for “restore from proxy,” which retrieves an image from the imaging (proxy) server and puts it on this device. The IP address or DNS name should be that of your imaging server, and the UNC path specifies the location and filename where the image is to be retrieved from.

      For example:

      img restorep 137.65.95.127 //xyz_srv/sys/imgs/cpqnt.zmg

    • To retrieve an image from a local device and put it down on a device: 

      img restorel filepath

      The restorel parameter stands for “restore from local,” which retrieves an image from a local device and puts it on this device. Filepath represents the filename of the image to retrieve, including the .zmg extension (case-sensitive) and the complete path from the root of the partition.

    IMPORTANT:Make sure to use forward slashes in the UNC path as shown above. Backslashes aren’t recognized by Linux. However, you can use backslashes and enclose the entire UNC path in quotes. The server portion of the path must be the name of your imaging server.

    If you want to manually restore an image from a folder that uses extended or double-byte characters in its name, you should perform an automatic image restoration. For more information, see Section 28.5.2, Creating, Installing, and Restoring Standard Images or Section 28.5.4, Restoring Lab Devices to a Clean State.

    For more information on the parameters you can use and usage examples, see Section E.4, Restore Mode (img restore).

    Depending on the size of the image, it might take several minutes to put the image down. Images usually take slightly longer to put down than they do to take.

  7. (Optional) After the image is put down and the bash prompt is displayed, type img dump, then press Enter.

    As before, this displays a list of the partition slots on the device. You should now see information about the new partitions that are created and activated by the image that you just put down.

  8. At the bash prompt, type lilo.s, then press Enter.

  9. Remove any CD or DVD from the drive and reboot the device.

  10. Verify that the device boots to the operating system that was installed by the new image.

Manually Putting an Image on a Device Using the ZENworks Imaging Engine Menu

  1. If you haven’t already done so, create the image to put on the device, as instructed in Manually Taking an Image of a Device.

    Make sure that the image is of the same type of device (same hardware configuration) and is stored on your imaging server. You can use a previous image of the same device.

    IMPORTANT:If you are putting an image on a device without a ZENworks partition, make sure the image was made on a device without a ZENworks partition. Otherwise, the wrong MBR (Master Boot Record) is restored, and the device fails to boot.

  2. (Optional) Boot the device from a Windows startup disk and run fdisk to remove all partitions from the hard disk.

    Running fdisk is not required, but it is recommended for purposes of comparing the workstation or server partitions before and after the imaging operation.

  3. Boot the device using one of the following methods:

  4. Enter manual at the bash prompt.

    or

    Select Start ZENworks imaging maintenance from the Preboot Services Menu.

  5. Enter img to display the ZENworks Imaging Engine menu.

  6. (Optional) Click System information > Drive information to display a list of the partition slots on the device.

    For your reference, note the number and type of partitions and which one is active. If you removed all partitions using fdisk, each slot should be empty and none should be active.

  7. Click Imaging > Restore image.

  8. In the Restore Image Wizard window, specify the source location of the image (Local or Server), then click Next.

  9. Browse to and specify the path to the image archive.

  10. (Optional) Specify a file set.

  11. (Optional) Specify any advanced options, such as sfileset or apartition:ppartition.

    For details on this and other related img command parameters, see ZENworks Imaging Engine Commands.

  12. Click Next.

    Depending on the size of the image, it might take several minutes to put the image down. Images usually take slightly longer to put down than they do to take.

  13. (Optional) Click System information > Drive information to display a list of the partition slots on the device.

    As before, this displays a list of the partition slots on the device. You should now see information about the new partitions that are created and activated by the image that you just put down.

  14. Exit the ZENworks Imaging Engine menu.

  15. Run lilo.s from the bash prompt.

  16. Remove any CD or DVD from the drive and reboot the device.

  17. Verify that the device boots to the operating system that was installed by the new image.

Making an Image Available for Automatic Imaging

When you boot a device from an imaging method and allow the boot process to proceed in auto-imaging mode, the imaging operation that is performed on the device is determined by default Preboot Services settings that you define in the ZENworks Control Center.

Creating a Preboot Services bundle also allows you to combine a base image and one or more add-on images into a single entity that can be put down on target devices. You can specify a standard image file to put down, or you can create a script to further customize your imaging operation. You can also specify that a particular file set of an image be used.

The sections that follow give instructions for performing these tasks:

Creating a Base Image

  1. Create the base image using one of the following methods:

  2. After the base image is created, perform one of the following procedures in the ZENworks Control Center:

    • If you created the image using a Preboot bundle, assign the bundle to the devices to be imaged:

      1. In the ZENworks Control Center, click Bundles, click the bundle containing the base image that you want to associate the add-on images with, then click Details.

      2. In the Assignments section, click Add to start the Assign Bundle wizard.

      3. Click Add to open the Select Objects dialog box.

      4. Select the devices or groups containing devices, then click OK.

      5. Click Next to display the Summary page, then click Finish > OK 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. Follow the instructions in Configuring the ZENworks Image Bundle for Automatic Imaging.

      2. In Step 10, click Next to assign the bundle to the devices.

    The next time these devices boot, they are imaged from this Preboot bundle.

Associating an Add-On Image with a Base Image

  1. Create the add-on image to associate with the base image. For more information, see Creating an Add-On Image.

  2. Copy the add-on image file to a ZENworks Linux Management imaging server that is accessible as a server object in your eDirectory tree.

    You might want to copy your add-on images to the same location as the base image.

  3. In the ZENworks Control Center, click Bundles, click the bundle containing the base image that you want to associate the add-on images with, then click Details.

  4. For the Add-On Image Files section, click Add.

  5. Browse for and select an add-on image.

    You can associate more than one add-on image with a base image. Repeat this step for each add-on image.

  6. Click Apply.

    When a device boots that is assigned to this bundle, the add-on images are put down after the base image in the order listed on this page.

Using a File Set of an Image

As explained in Using Image Explorer to Customize an Image, you can exclude individual files and folders from any of 10 possible file sets of an image.

Table 30-1 Image File Set Usages

Type of imaging operation

How to specify the file set to use

Automatic (Preboot Services based on default settings)

In the Multicast Wizard in the ZENworks Control Center, specify the number of the file set in the File set field. You must create the file set using the Image Explorer utility. For more information, see Section D.1, Image Explorer (imgexp.exe).

You can create multiple Preboot bundles that point to the same base image, but to different file sets of that image.

Manual (command line or menu)

Use the s parameter on the img restore command. For example, to specify file set number 3:

img restorel dellnt4.zmg s3

or

You can enter img at the bash prompt to display a menu, select Restore an image, then select Local image. Specify sfileset (for example, s3) in the Advanced parameters field.

For details, see ZENworks Imaging Engine Commands.

30.1.3 Setting Up Disconnected Imaging Operations

Disconnected imaging operations are inherently manual. To perform a disconnected imaging operation on a device, you must have a storage device to hold the image to be created or put down, and that storage device must be locally accessible to the ZENworks Imaging Engine (in Linux) when you boot the device from the imaging boot media.

The following sections explain how to set up and perform disconnected operations:

Using a CD or DVD for Disconnected Imaging Operations

In ZENworks Linux Management, you can use CDs and DVDs only as the storage medium for an image to put down, not for an image to be created.

You can put down an image from a bootable or non-bootable imaging CD or DVD using either the bash prompt or using the ZENworks Imaging Engine menu.

The following sections contain additional information:

Putting Down an Image Using the Bash Prompt

  1. Use your CD- or DVD-burning software to burn the source image onto a CD or DVD.

  2. Boot the device using one of the following methods:

  3. Enter manual from the bash prompt.

  4. Insert the CD or DVD that contains the source image.

  5. At the Linux prompt, enter cdrom.s to mount the CD or DVD.

    This mounts the CD or DVD to /mnt/cdrom.

  6. Enter a command using the following format:

    img restorel /mnt/cdrom/path/image_name.zmg

    where path and image_name are the path and filename of the image relative to the root of the CD or DVD.

  7. When the imaging is done, remove the imaging boot media (if applicable) and do the following to boot the device with the new image:

    1. At the Linux prompt, type lilo.s, then press Enter.

    2. Press Ctrl+Alt+Delete.

      If the device doesn’t boot to the new operating system (that is, if the Linux prompt is displayed), enter lilo.s again and reboot the device a second time.

Putting Down an Image Using the ZENworks Imaging Engine Menu

  1. Use your CD- or DVD-burning software to burn the source image onto a CD or DVD.

  2. Boot the device using one of the following methods:

  3. Enter manual from the bash prompt.

  4. Insert the CD or DVD that contains the source image.

  5. At the Linux prompt, enter cdrom.s to mount the CD or DVD.

    This mounts the CD or DVD to /mnt/cdrom.

  6. Enter img to display the ZENworks Imaging Engine menu.

  7. Click Imaging, then click Restore image.

  8. Click Local, then click Next.

  9. Browse to and specify the path to the image archive.

  10. (Optional) Specify a file set.

  11. (Optional) Specify any advanced options, such as sfileset or apartition:ppartition.

    For details on this and other related img parameters, see ZENworks Imaging Engine Commands.

  12. Click Next.

    Depending on the size of the image, it might take several minutes to put the image down. Images usually take slightly longer to put down than they do to take.

  13. When the imaging is done, remove the imaging boot media (if applicable) and do the following to boot the device with the new image:

    1. At the Linux prompt, type lilo.s, then press Enter.

    2. Press Ctrl+Alt+Delete.

      If the device doesn’t boot to the new operating system (that is, if the Linux prompt is displayed), enter lilo.s again and reboot the device a second time.

Using a Hard Disk for Disconnected Imaging Operations

When you boot a device from a ZENworks Linux Management imaging boot media, you can create an image on, or put down an image from, any primary partition on an IDE or SCSI hard drive. You can also use the local ZENworks partition if one is installed. Any target partition must have sufficient space.

When you create an image, the partition where you store the image is itself excluded from the image. When you put down an image, the source partition is not altered.

You can create or put down an image on a hard disk using either the bash prompt or using the ZENworks Imaging Engine menu.

The following sections contain the instructions:

Creating an Image Using the Bash Prompt

  1. Boot the device using one of the following methods:

  2. Enter manual from the bash prompt.

  3. At the Linux prompt, enter img dump to view the available partitions.

    Note the number of the partition where you will store the new image.

  4. Enter a command using the following format:

    img makel[pNumber] /path/image.zmg [comp=comp_level]

    where pNumber is the number of the partition to store the image in, and comp_level is the amount of compression used when creating the image. Specify any number from 0-9. 0 means no compression. 1 is the same as Optimize for speed. 6 is the same as Balanced and is used by default if you do not specify this parameter. 9 is the same as Optimize for space. (Optimize for speed takes the least amount of time but creates the largest image file. Optimize for space creates the smallest image file but might take a significant amount of time. Balanced is a compromise between compression time and image file size.) 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 img command parameters, see ZENworks Imaging Engine Commands.

Creating an Image Using the ZENworks Imaging Engine Menu

  1. Boot the device using one of the following methods:

  2. Enter manual from the bash prompt.

  3. Enter img 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.

    For your information, note the number of the partition where you will store the new image.

  5. Click Imaging > Make image.

  6. In the Make Image Wizard window, click Local > Next.

  7. Browse to and specify the path to the image archive.

  8. Select the partitions that you want to include in the image.

  9. Select a compression option.

    None: No compression is used.

    Speed: Takes the least amount of time to compress but creates the largest compressed image file. This option is used by default when an image is created.

    Balanced: Represents a compromise between compression time and image file size.

    Size: Creates the smallest image file but takes longer to compress.

  10. Click Next.

  11. (Optional) Fill in the fields:

    Author: The name of the person creating this image.

    Computer: The name of the computer being imaged.

    Image description: A description of the image.

    Comments: Any additional comments about the image.

  12. Click Next.

    Depending on the amount of data on the hard disk, the image might take several minutes to create.

  13. After the image is created, exit from the ZENworks Imaging Engine menu, remove any CD or DVD from the drive, then reboot the device.

  14. (Optional) Verify that the image file was created. You might also want to check its size.

Putting Down an Image Using the Bash Prompt

  1. Boot the device using one of the following methods:

  2. Enter manual from the bash prompt.

  3. (Optional) At the Linux prompt, enter img dump to view the available partitions.

    For your information, note the number of the partition where the source image is stored.

  4. Enter a command using the following format:

    img restorel[pNumber] /path/image.zmg

    where pNumber is the number of the partition where the source image is stored, and path and image are the image path and filename relative to the partition root. If you omit the partition number, the local ZENworks partition is used.

    For details on other related img command parameters, see ZENworks Imaging Engine Commands.

  5. When the imaging is done, remove the imaging boot media (if applicable) and do the following to boot the device with the new image:

    1. At the Linux prompt, type lilo.s, then press Enter.

    2. Press Ctrl+Alt+Delete.

      If the device doesn’t boot to the new operating system (that is, if the Linux prompt is displayed), enter lilo.s again and reboot the device a second time.

Putting Down an Image Using the ZENworks Imaging Engine Menu

  1. Boot the device using one of the following methods:

  2. Enter manual from the bash prompt.

  3. Enter img 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.

    For your reference, note the number of the partition where the source image is stored.

  5. Click Imaging > Restore image.

  6. Click Local > Next.

  7. Browse to and specify the path to the image archive.

  8. (Optional) Specify a file set.

  9. (Optional) Specify any advanced options, such as sfileset or apartition:ppartition.

    For details on this and other related img command parameters, see ZENworks Imaging Engine Commands.

  10. Click Next.

    Depending on the size of the image, it might take several minutes to put the image down. Images usually take slightly longer to put down than they do to take. If the screen goes blank, just press any key. (Linux enters a screen-saving mode after a few minutes.)

  11. When the imaging is done, remove the imaging boot media (if applicable) and do the following to boot the device with the new image:

    1. At the Linux prompt, type lilo.s, then press Enter.

    2. Press Ctrl+Alt+Delete.

      If the device doesn’t boot to the new operating system (that is, if the Linux prompt is displayed), enter lilo.s again and reboot the device a second time.