ImageBoot Readme
Revised on January 16, 2017
This document contains the important information when using
ImageBoot. It is highly recommended that you read this document
carefully before installing ImageBoot.
Table of
Contents
System
Requirements
Limitations
and Precautions
Before using
ImageBoot, ensure that all Windows based hypervisor system
requirements are met.
Hypervisor
- VMware Workstation 10, 11, 12 Pro
- VMware Player 6, 7,
12 Player
- Microsoft
Hyper-V (Windows Server 2008 R2 requires Microsoft .NET
Framework 4 or later is installed.)
- Oracle VirtualBox 5
Operating System (Host)
Windows 7 (32 bit, 64bit), Server 2008 R2 or later.
Operating System (Guest)
Windows XP (32 bit, 64bit), Server 2003 (32 bit, 64bit) or
later.
* Dependent on the Hypervisor's limitations.
Back to Table of
Contents
- A VM booted from a hypervisor will be deleted
automatically at shut down. The changes made while the VM was
running will be saved to a differential file (*.aix) using the
following naming convention:
Ex：<Installation Folder >\VMAIXFile\<booted
image file name>_x00001.aix
This option is enabled in ActiveImage Protector by
moving or copying the most current image file to the specified
destination of the image file.
* In the event that a differential file (*.aix) is
used to boot a VM, the changes are overwritten to the image file
selected that booted the VM.
- Cannot boot from multiple image files as one
VM (except for the image files
that were created using the [a separate image file for each
disk] option).
- When selecting an image file that was created with
the [a separate image file for each disk] option, ImageBoot can
boot only disks included in the specific image in which the file
type and number correspond to the selected image file.
Please note that a differential image file is created when
images are consolidated or when using ActiveImage Protector's
write mount feature.
- Cannot use an image file that includes the disk
which conflicts with the host disk's signature.
A disk included in the image file used to create a VM that is
already booted will conflict with the same disk signature from
the image file.
- When an image file
is used to boot a Hyper-V VM, and a network adapter is added
by selecting [Add], the virtual switch is not specified
automatically. Please specify a suitable virtual switch after
VM creation.
- If the uninstall does not complete properly due
to a crash by Au_.exe, re-install and then uninstall again.
- The changes made for the settings configured
for the booted VM on a hypervisor will not be saved.
Ex: Virtual switch assigned to booted Hyper-V VM
- In the event of booting Windows 7 or earlier on VirtualBox, SCSI storage controller is used. Optical drive is not available.
- In the event that this product or the hypervisor used for booting the virtual machine terminates with an unexpected error, the differential image file that includes the changes made during the virtual machine is running should be damaged. Then, should you try to boot the virtual machine by selecting it from [Recently used VM] list, you get Error 1359 and the VM fails to boot up. If you encounter this problem, please delete the virtual machine from the list and newly boot the virtual machine again.
- If you boot a virtual machine in this product while you log in as a user other than Administrator and VMware
Workstation is up and running, shutting down the virtual machine does not automatically delete the virtual machine.
- When you boot Hyper-V virtual machine from [Recently used VM] list, the network settings configured at the last booting are not kept.
Back to Table of Contents
Back to Index