The following provides a brief overview of Preboot Services:
Preboot Services allows you to automatically or do any of the following to a Windows or Linux device when it boots:
Make an image of the device’s hard drives and other storage devices
Restore an image to the device
Apply an existing image to multiple devices
Run Imaging scripts on the device
Run AutoYaST and kickstart installations
Configure Dell devices
To accomplish these tasks automatically by using ZENworks Control Center, you simply need to have PXE (Preboot Execution Environment) enabled on your devices, then have Preboot bundles configured and assigned to the devices. The devices automatically execute these bundles when they boot.
Preboot Services utilizes the following to make its imaging functions possible:
PXE (Preboot Execution Environment): An Intel specification that allows a device to boot from the network, instead of its hard drive or other local media. ZENworks can use PXE to launch Preboot Services.
Preboot Services Bootable CD or DVD: Used where PXE is not installed or where you want to perform a Preboot Services operation. This is applicable only for ZENworks Imaging.
ZENworks Partition: Enables you to set up a device for unattended imaging operations where the device is not PXE-enabled or does not have access to PXE network services. This is applicable only for ZENworks Imaging.
USB Boot: You can perform Imaging operations by creating a bootable USB drive to boot systems with BIOS and UEFI firmware.
For more information on these methods, see Section 3.0, Using Imaging.
Following are some of the uses of Preboot Services:
Create and Restore Standard Images: Create base images from existing devices, as well as restore images to any manageable device.
Set Up Devices for Future Reimaging: Set up devices so that the next time they reboot, they do the imaging work that is contained in their assigned Preboot bundle.
Multicast Device Images: Apply an image of one device to many other devices. This is an excellent feature for initially setting up a lab.
Restore Devices to a Clean State: Quickly and efficiently reset devices to an initial state, such as in a lab.
Automate Linux installations: Automate kickstart or AutoYaST installations.
MDT Deployment: Automate Windows desktop and server deployment.
Configure Dell devices. Configure basic boot settings on Dell devices.
For more information on these strategies, see Section 1.6, Preboot Strategies.
In ZENworks Control Center, Preboot Services tasks are contained in Preboot bundles. The following Preboot bundle types are available:
Empty Bundle: A bundle with no initial tasks. You can quickly create this bundle without performing all of tasks in the Create New Bundle wizard. Later, you can edit its details to add assignments, actions, and so forth.
AutoYaST Bundle: A bundle that contains the location and access protocol of an AutoYaST configuration file and network installation directory for SUSE Linux. This bundle allows you to launch an automated installation of SUSE Linux using Preboot Services. This is only available for Linux devices that are PXE-enabled. AutoYaST bundles cannot be run using a boot CD, a ZENworks partition, or a bootable USB.
DellDTK Configuration: A bundle that contains the location of files and scripts for configuring Dell servers. This bundle allows you to use Preboot Services to configure the BIOS, BMC, RAID, and DRAC for settings and to create a new Dell Utility partition. You can also identify another Preboot bundle to be run immediately after these configurations have completed. This is only available for Linux devices that are PXE-enabled. Dell Configuration bundles cannot be run using a boot CD, a ZENworks partition, or a bootable USB.
Imaging Script Bundle: Allows you to write a custom Linux Imaging script. This providesdetailed control over ZENworks imaging operations, as well as most Windows-based preboottasks. This is applicable only for ZENworks Imaging.
Kickstart: A bundle that contains the location and access protocol of a KickStart configuration file for Red Hat Linux. This bundle allows you to launch an automated installation of Red Hat Linux using Preboot Services. This is only available for Linux devices that are PXE-enabled. Kickstart bundles cannot be run using a boot CD, a ZENworks partition, or a bootable USB.
MDT Deployment: A bundle which supports the deployment of the Windows operating system using Microsoft Deployment Toolkit (MDT). This bundle enables you to upload and replicate the MDT WIM files to the required Primary and Imaging Satellite servers.
Multicast Image Set Bundle: Specifies an image that can be sent through the multicast protocol. This bundle allows you to send an image to a large number of devices in a single operation, which minimizes network traffic. It is ideal for labs, classrooms, and staging areas. This is applicable only for ZENworks Imaging.
Third-Party Image Bundle: The third-party image bundle can be used to place an image on a device that are taken using ImageX or Ghost third-party imaging tools.
Third-Party Script Bundle: Allows you to write custom WinPE imaging scripts that can be executed in the WinPE distro.
ZENworks Image Bundle: Lists one or more ZENworks images (base plus add-ons) that can be restored on a device. This bundle allows you to define simple imaging operations.
To create one of these bundles: in ZENworks Control Center, clickin the left pane, in the Bundles panel click > > > , then select a bundle type.
For more information on these bundles, see Section 1.4.1, Preboot Bundles.
In ZENworks Control Center, you can set up default Preboot Services configurations for all of your devices. 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)(automatically executes the bundle); 2) (accesses the imaging maintenance mode prompt); 3) ; 4) ; and, 5) (resumes booting). You can configure whether the menu is displayed upon booting, not displayed, or displayed only when Ctrl+Alt is pressed during booting.
Non-Registered Device Settings: You can use Preboot Services to automatically name your non-registered devices, using such criteria as prefixes, BIOS information (such as asset tags or serial numbers), DNS suffixes, and you can set up DHCP or IP addresses.
Device Imaging Work Assignment: Work assignment rules are used to determine which bundle should be applied to which device. The work rules use logic to determine whether a device meets the requirements for applying the Preboot bundle. A rule is made up of filters that are used to determine whether a device complies with the rule. The AND and OR logical operators are used for creating complex filters for the rule.
Server Referral List: When a device boots, it is necessary for it to find its home Management Zone to get its assigned imaging work. If multiple Management Zones exist on the network, server referral lists provide a method for allowing a managed device to find its home zone.
Intel Active Management Technology (AMT): Intel AMT provides Preboot Services with persistent device identification.
Third-Party Imaging Settings: You can upload WinPE (Windows Preboot Environment) and third-party Imaging tools such as Microsoft Imaging engine (imagex.exe) and Symantec Ghost (ghost32.exe). Before configuring the third-party Imaging settings, ensure that Microsoft Windows Automated Installation Kit (WAIK) or Windows Assessment and Deployment Kit (WADK) is installed on the device running the ZENworks Control Center.
When you are upgrading to a newer version of ZENworks, make sure that you re-upload the WinPE distribution (winpe.wim) under Third-Party Imaging Settings in ZCC, to see the latest zenworktodo application in the WinPE environment.
TFTP Replication Settings: You can replicate the changes made to the tftp directory on other Imaging servers (Primary Servers or Satellites with the Imaging role). The tftp directory contains files such as configuration files and binaries used by ZENworks to perform imaging tasks. The directory is located on the Imaging server in /srv/ on Linux and in %ZENWORKS_HOME%\share\ on Windows.
Third Party NTFS Driver Settings: You can download the latest high performance NTFS driver and save it on your system.You can view content replication status across all Primary and Satellite Servers with the Imaging role in the management zone. You can start the Imaging operation when the status is Available. When you are updating to the latest version of ZENworks or imaging driver update, and upload the new Tuxera driver.
To configure these settings, clickin the left pane to display the tab. If it’s not expanded, click , then click > to display the Preboot Services page.
For more information, see Section 1.4, Preboot Services Functionality.
In order for a device to automatically use an assigned Preboot bundle, you must complete two tasks:
Preboot Services utilizes PXE and other boot mechanisms and media to trigger the imaging work. For information, see Section 2.3, Setting Up the Preboot Services Methods for ZENworks Imaging.
The following paths represent many of the methods for assigning bundles to devices, or devices to bundles:
Click> > select the check boxes next to one or more servers, then click > .
You can assign bundles to all selected servers.
Click> > select the check boxes next to one or more workstations, then click > .
You can assign bundles to all selected workstations.
Click> > select a server, then click (in on the tab).
You can assign a specific bundle to the server.
Click> > select a workstation, then click (in on the tab).
You can assign a specific bundle to the workstation.
Click> > select the check box next to a server, then click > .
You can assign multiple bundles to the server.
Click> > select the check box next to a workstation, then click > .
You can assign multiple bundles to the workstation.
Click> select the check boxes next to one or more bundle names, then click > .
You can assign the selected bundles to the devices that you select in the wizard.