ImageBoot Readme
Revised on July 12, 2017
This document contains the important information when using the
product. It is highly recommended that you read this document
carefully before installing the product.
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 (When using Windows Server 2008 R2, Microsoft.Net
Framework 4 or later should be configured)
- 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
- To keep the currently configured settings after
uninstalling the product, please copy the following items from
the installation folder to another location before you begin
uninstalling the product. After reinstalling the product,
overwrite these items to installation folder so you can continue
to use the same settings.
- settings.ini
- vNetConfig.ini
- VMDIR folder
- VMAIXFile folder
- When upgraded from Version 2.0.2, a VM created
by using Version 2.0.2 is not supported to boot up by selecting
it from [Most Recent used virtual machines] list.
- A VM booted on a hypervisor will be deleted
automatically when VM is shut down. The changes made while the
VM is running will be saved to a differential file (*.aix) as
the most current image file:
- The above described differential file is created
as follows by default:
Ex：<Installation Folder >\VMAIXFile\<booted
image file name>_x00001.aix
- The changes made to the VM booted from an image
file are saved in the differential file. When writing data to
the VM, please make sure that the destination storage of the
differential file have more available space than the data size
to write. The default destination storage to save the
differential image files may be changed to any location from the
[Settings] window.
- Move or copy the differential image file created
as the most current image file to the destination storage
specified when booting the image, so that ActiveImage Protector
can operate the file.
- If you use a differential image file for the
initial boot, the changes are applied to the image file
specified when booting the image.
- When selecting an image file that was created with
the [a separate image file for each disk] option enabled,
ImageBoot can boot a VM that includes only disks in the image
with the specified file type and number.
Please be attentive when images are consolidated or when a
differential image file is created using write mount feature in
ActiveImage Protector.
- If you use an image file including the disk that has
disk signature confilit with the hard disk configured for the
system, the conflicting disk signature of the VM is replaced
with a new one.
If you continue to use the VM, every time the VM is booted, a
newly created signature is assigned.
- 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.
- If booting Windows 7 or
earlier on VirtualBox, the SCSI storage controller is used and
the optical drive is not available.
- If 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 booted virtual machine could be
damaged. Retrying to boot the virtual machine by selecting it
from [Most Recent used virtual machines] list, the the VM
fails to boot up and Error 1359 is displayed. If this
issue is encountered, delete the virtual machine from the list
and then 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.
- In the event that you
boot a VM created and saved while the VM is connected to
multiple disks by selecting the VM from [Most recent used
virtual machines] list, all disks connected to the VM are
booted on line regardless of the previous shutdown status.
- While booting from an image file and the source
image file becomes inaccessible, the host system may be
unstable.
- In the event that you allocate an unavailable
memory size in the system, the VM may fail to boot up and Error
28703 is displayed. If you encounter the problem, go back to
[Select Image] dialog, re-select the image, allocate an
available memory size in the system, and then try again to boot
the VM.
- Suspend Booted VM (saving status) is not
supported.
- Snapshots created while booting VM (check
points) are entirely discarded when the VM is terminated.
- (8847) After selecting [Boot later] even though
you changed the destination storage for differential backup
images in [Virtual Machine Settings], the differential files of
the booted image file are created in the location specified when
the image was booted instead of the location specified when you
configured virtual machine settings.
- If Version 2.0.2 or 3.0.0 is upgraded to Version
3.0.0 or 3.0.1, the following folders are copied to the same
location and uninstallation of the product deletes the folders.
If necessary, the folders can be manually deleted.
- VMDIR folder
- VMAIXFile folder
Back to Table of Contents
Back to Index