The following sections cover procedures to configure ZfD imaging services. The procedures that are applicable to you depend on your imaging deployment strategy. (See Imaging Deployment Strategies.)
If a Windows workstation hasn't been registered as a Workstation object in NDS and you boot that workstation from an imaging device or method in auto-imaging mode, the imaging server is contacted and checks its Imaging Server Policy in NDS to determine which image to lay down on the workstation. If the base image specified by the policy is the same as the base image currently on the workstation (as reported by the imaging engine), the imaging server doesn't send any new images to lay down on the workstation, unless a flag is set in the policy to force down the base image again. If such a flag is set, or if the base image currently on the workstation is different than the base image specified by the policy, the imaging server sends down the new base image and any add-on images specified by the policy, and the imaging engine lays these images down on the workstation.
In addition, if the imaging engine reports to the imaging server that data is missing from the workstation's image-safe area, the imaging server obtains the missing data from the Imaging Server Policy and sends it to the imaging engine, which then saves the data to the image-safe area.
To define the Imaging Server Policy for one or more imaging servers:
Prepare the various workstation images that the policy can prescribe. For details, see Preparing Images in Workstation Imaging in Administration.
If a Server Package hasn't already been created to hold the policies for the target imaging servers, create one as instructed in Creating the Policy Packages in Installation and Setup in Getting Started.
Right-click the Server Package > click Properties.
Enable the Imaging Server policy > click Properties.
Follow this step if you are using PXE:
If you are using PXE but previously booted workstations from a ZENworks imaging (Linux) partition, you can select to disable the imaging partition on the General Imaging Partition property page. The partition is not removed with this option.
Use the General PXE Settings property page to specify the availability of the PXE menu, which displays when you boot a PXE-enabled workstation. The default PXE menu includes the ability to Start ZENworks Imaging in Automatic Mode, Start ZENworks Imaging in Maintenance Mode, Disable the ZEN Partition, and Enable the ZEN Partition.
You can also specify a different PXE menu to use. You can create a custom menu using the Menu Editor. On a Windows machine that has Preboot Services (PXE Support) installed on it, click the Start button > Programs > ZEN Preboot Services > ZEN Preboot Services Menu Editor to locate the Menu Editor and the Menu Editor User Guide. You can also find this guide at the ZfD 3.2 Preboot Services Product documentation Web site.
NOTE: Menu Editor is not installed to a NetWare server. If you need to use Menu Editor from a NetWare server, locate the files on the ZfD 3.2 Preboot Services CD in \MENU EDITOR > copy them to your NetWare server. Then, from a Windows machine, you can map a drive to the location on the server and run Menu Editor.
If you want to specify a different image when using PXE, rather than the default image that is defined, specify the image file and pathname.
On the Image Selection tab, click Add > define the conditions under which the target imaging servers should send down a particular image > click OK.
For details on how to perform this task, click Help in the New Image Selection Rule dialog box.
Repeat the previous step as needed to provide rules that will cover all the workstations serviced by the target imaging servers.
(Optional) If you want the imaging server to force down the base image determined by this policy even if it's the same as the base image currently on the workstation, select the check box on the bottom of the page.
WARNING: Use this option with care, because laying down a base image destroys all data that was added to the workstation since the last base image was laid down. In most scenarios, you'll want to use this option only temporarily while a specific workstation is being imaged and not generally for all workstations, unless this policy is designed for a lab environment where you want the workstations to be reimaged every time they reboot. If you select this option as a temporary measure, be sure to deselect it once the specific imaging task is done.
On the Image-safe Data tab, fill in the IP Configuration and Windows Networking pages.
These pages supply image-safe data values that might be missing on the workstations that are serviced by the target imaging servers. For details on these pages, click Help.
Click OK to save the policy.
On the Associations page, add the containers and/or server objects that represent the target set of imaging servers.
Click OK to save the association.
Remember that the policy won't actually be consulted by the associated imaging servers unless the client requesting the imaging operation is an unregistered workstation that has been booted in auto-imaging mode.
Most of the rules that comprise an Imaging Server Policy are in force only when the imaging server is servicing a request to auto-image a workstation. Such rules aren't in force when the imaging server is servicing a manual (command line or menu) imaging request. However, the following two aspects of the Imaging Server Policy are always in force, no matter whether the imaging server is servicing an automatic or manual imaging request:
To define these general behaviors for one or more imaging servers:
If a Server Package hasn't already been created to hold the policies for the target imaging servers, create one as instructed in Creating the Policy Packages in Installation and Setup in Getting Started.
Right-click the Server Package > click Properties.
Enable the Imaging Server policy > click Properties.
Fill in the items on the Security tab. For how to do this, click Help.
Click OK to save the policy.
On the Associations page, add the containers and/or server objects that represent the target set of imaging servers.
Click OK to save the association.
Remember that these aspects of the server policy are always in force.
If a Windows workstation has been registered as a Workstation object in NDS and you boot that workstation from an imaging device or method in auto-imaging mode, the imaging server is contacted and checks the Workstation object in NDS to see if the administrator has flagged it to receive an image. If this is the case and the administrator hasn't specified which image to use, the imaging server consults the Workstation Imaging Policy associated with the Workstation object to determine which image to send down.
To define the Workstation Imaging Policy for one or more workstations:
Prepare the various workstation images that the policy can prescribe. For details, see Preparing Images in Workstation Imaging in Administration.
If a Workstation Package hasn't already been created to hold the policies for the target workstations, create one as instructed in Creating the Policy Packages in Installation and Setup in Getting Started.
Right-click the Workstation Package > click Properties.
Enable the Workstation Imaging policy > click Properties.
Follow this step if you are using PXE:
If you are using PXE but previously booted workstations from a ZENworks imaging (Linux) partition, you can select to disable the imaging partition on the General Imaging Partition property page. The partition is not removed with this option.
Use the General PXE Settings property page to specify the availability of the PXE menu, which displays when you boot a PXE-enabled workstation. The default PXE menu includes the ability to Start ZENworks Imaging in Automatic Mode, Start ZENworks Imaging in Maintenance Mode, Disable the ZEN Partition, and Enable the ZEN Partition.
You can also specify a different PXE menu to use. You can create a custom menu using the Menu Editor. On a Windows machine that has Preboot Services (PXE Support) installed on it, click the Start button > Programs > ZEN Preboot Services > ZEN Preboot Services Menu Editor to locate the Menu Editor and the Menu Editor User Guide. You can also find this guide under Preboot Services at the ZfD 3.2 Preboot Services Product documentation Web site.
NOTE: Menu Editor is not installed to a NetWare server. If you need to use Menu Editor from a NetWare server, locate the files on the ZfD 3.2 Preboot Services CD in \MENU EDITOR > copy them to your NetWare server. Then, from a Windows machine, you can map a drive to the location on the server and run Menu Editor.
If you want to specify a different image when using PXE, rather than the default image that is defined, specify the image file and pathname.
On the Image Selection tab, click Add > define the conditions under which the imaging server should send down a particular image > click OK.
For details on how to perform this task, click Help in the New Image Selection Rule dialog box.
Repeat the previous step as needed to provide rules that will cover all the target workstations.
Click OK to save the policy.
On the Associations page, add the container, Workstation Group, or Workstation objects that represent the target set of workstations.
Click OK to save the association.
Remember that the policy won't actually be consulted by the imaging server unless you (or another administrator) flags a Workstation object to receive an image on the next boot.
Disconnected imaging operations are inherently manual in the sense that they don't involve the network and thus can't be automated through NDS.
To perform a disconnected imaging operation on a computer, you must have a storage device to hold the image that will be created or laid down, and that storage device must be locally accessible to the imaging engine (in Linux) when you boot the computer from the imaging device. The following sections explain how to set up and perform disconnected operations using different storage devices:
Because a CD is read-only, you can only use it as the storage medium for an image that will be laid down, not for an image that will be created. The steps to lay down an image from a CD depend on whether the CD is the bootable imaging CD or some other (non-bootable) CD.
To lay down an image from the imaging boot CD:
Use your CD-burning software to put the source image on the imaging boot CD. See Preparing a Bootable CD for details.
Boot the target computer from the CD and type manual at the boot prompt.
If the computer fails to boot, see Can't Boot a Workstation from the Imaging CD in Troubleshooting Workstation Imaging in Troubleshooting.
At the Linux prompt, type img dump to view the available partitions. Note the partition number of the imaging CD.
or
Type img to display a menu > select Dump > No Geometry.
To lay down the image, you have two choices:
img restorelpNumber /path/image.zmg
where pNumber is the partition number of the imaging CD and path and image are the image path and filename from the root of the CD.
For details on these and other related img command parameters, see Imaging Engine (img: Command Line and Menu) in Imaging Utilities and Options in Workstation Imaging in Administration.
When the imaging is done, remove the CD and do the following to boot the computer with the new image:
To lay down an image from another (non-bootable) CD:
Use your CD-burning software to burn the source image onto a CD.
Boot the target computer from a ZfD imaging device and type manual at the boot prompt. Insert the second and third diskettes if you are prompted for them.
Insert the CD that contains the source image.
At the Linux prompt, type cdrom.s to mount the CD.
This mounts the CD to /mnt/cdrom.
To lay down the image, you have two choices:
img restorel /mnt/cdrom/path/image.zmg
where path and image are the path and filename of the image relative to the root of the CD.
For details on other related command parameters, see Imaging Engine (img: Command Line and Menu) in Imaging Utilities and Options in Workstation Imaging in Administration.
When the imaging is done, remove the imaging device (if applicable) and do the following to boot the computer with the new image:
When you boot a computer from a ZfD imaging device, you can create an image on, or lay down an image from, any primary FAT16 or FAT32 partition on an IDE or SCSI hard drive or Iomega* Jaz* drive. You can also use the local ZfD imaging (Linux) partition if one is installed. Any target partition must have sufficient space.
When you create an image, the partition where you will store the image is itself excluded from the image. When you lay down an image, the source partition will not itself be altered.
To create an image on a hard disk or Jaz drive:
Boot the source computer from a ZfD imaging device and type manual at the boot prompt. Insert the second and third diskettes if you are prompted for them.
At the Linux prompt, type img dump to view the available partitions.
or
Type img to display a menu > select Dump > No Geometry.
Note the number of the FAT partition where you'll store the new image.
To create the new image, you have two choices:
img makel[pNumber] [comp=comp_level] /path/image.zmg
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 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 may 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 ZfD imaging (Linux) partition is used.
For details on other related img command parameters, see Imaging Engine (img: Command Line and Menu) in Imaging Utilities and Options in Workstation Imaging in Administration.
To lay down an image from a hard disk or Jaz drive:
Boot the target computer from a ZfD imaging device and type manual at the boot prompt. Insert the second and third diskettes if you are prompted for them.
At the Linux prompt, type img dump to view the available partitions.
or
Type img to display a menu > select Dump > No Geometry.
Note the number of the FAT partition where the source image is stored.
To lay down the image, you have two choices:
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 ZfD imaging (Linux) partition is used.
For details on other related img command parameters, see Imaging Engine (img: Command Line and Menu) in Imaging Utilities and Options in Workstation Imaging in Administration.
When the imaging is done, remove the imaging device (if applicable) and do the following to boot the computer with the new image: