Testing The Image - Neoware e140 - Thin Client User Manual

Testing the Image

When the Neoware Image Manager virtual disk on the destination
machine has been correctly modified by UbiBoot Inserter, you must
validate that the source machine can actually be booted off that
image:
1
If you were using CVolwrite/Normal mode on the destination
machine, you might:
rename or copy the CVol files to associate them with the
•
source machine. This implies that you already know the
MAC address of the source machine that is to be included in
the CVol file names. Refer to the section "Client Volume
Overlay Files" on page 80 for details.
use
•
CVolMerge
machine's CVol files into the HD image file.
If you had booted the destination machine in Admin mode, do
not forget to switch back to either CVolwrite/Volatile mode or
CVolwrite/Normal mode.
2 Boot test the source machine and the destination machine. Both
should now boot. The instance of Windows that booted the
source machine should now detect, configure or offer to config-
ure all of its "new hardware".
3
If the source machine has successfully booted, it is now possible
to add this enhancement to the HD image:
Shutdown the source and the destination machines and change
the writing mode to Admin or CVolwrite/Normal.
Boot the source machine off the virtual drive and let Windows
detect and install the hardware in the usual way. Re-boot each
time Windows asks you to.
When Windows has successfully detected all the hardware, if
you were using CVolwrite/Normal mode, you may now want to
commit the changes that are in the CVol files into the HD image
Adding Network Boot Devices to an Image
to merge the changes in the destination
Testing the Image 101