D Third-Party Imaging; Things To Know Before Working On Zenworks Third-Party Imaging - Novell ZENWORKS 10 CONFIGURATION MANAGEMENT SP3 - PREBOOT SERVICES AND IMAGING REFERENCE 10.3 16-04-2010 User Manual

Third-Party Imaging
D
® ®
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.
Currently, only PXE is supported as the boot mechanism for third-party Imaging. Preboot Execution
Environment (PXE) is an Intel specification that allows a device to boot from the network, instead
of its hard drive or other local media. Configuration Management can use PXE to launch Preboot
Services.
Review the following sections:
Section D.1, "Things to Know Before Working on ZENworks Third-Party Imaging," on
page 167
Section D.2, "Performing ZENworks Third-Party Imaging by Using ZENworks Control
Center," on page 168
Section D.3, "Setting Up Preboot Services for ZENworks Third-Party Imaging," on page 168
Section D.4, "Performing ZENworks Third-Party Imaging in the Maintenance Mode," on
page 169
Section D.5, "Configuring the Destination Disk Structure Before Restoring a WIM Image," on
page 177
D.1 Things to Know Before Working on
ZENworks Third-Party Imaging
Before you begin to work on the ZENworks Third-Party Imaging, you need to know the following:
The ZENworks Third-Party Imaging solution does not work on VMware* for operating
systems other than Windows Vista* because of a network card driver problem in WinPE on
VMware.
Workaround: Do the following:
1. Close VMware.
2. Add the following line to the
ethernet0.virtualDev = "e1000"
3. Restart VMware.
Before taking an image of the Windows Vista device, run SysPrep on the device. Later on, you
must run Sysprep again on all the devices where the image is restored. This is essential because
the SIDchanger is not used for ZENworks Third-Party Imaging.
file:
.vmx
D
Third-Party Imaging 167