ImageBoot Release Note
Revised on July 12, 2017
Table of
Contents
Version 3.0.2.4110 (July 13,
2017)
Version 3.0.1.4092 (June 27,
2017)
Version 3.0.0.4080 (June 15,
2017)
Version 2.0.2.3795 (January 19,
2017)
Version 1.0.1.2376 (May 12,
2015)
Version 1.0.0.2298 (March 25,
2015)
Updates
- Following installation of this product, start up
time (boot time) for the system had increased. This issue has
been resolved.
- If a password protected backup image file was
selected and an incorrect password was entered, the dialog is
displayed to re-select a backup image file instead of
re-entering the correct password. This issue has been resolved.
- When upgrading the product, unnecessary folders
were copied. This issue has been resolved.
Back to
Table of Contents
Updates
- On Windows Server 2008 R2 with .NET Framework
4.5.2 or later configured and Hyper-V was selected as the
hypervisor to boot the VM, the console crashed. This issue has
been resolved.
- VMs created and booted by enabling the [continue
to use] option on the backup source host did not boot up from
the second time onward. This issue has been resolved.
Back to
Table of Contents
Updates
- The combined use of ImageBoot 3 with ImageCenter
2 on the same host is supported.
* After installation of this version, when ImageCenter 2 is
installed, invalid version information is provided for this
product. If you encounter this problem, please install this
product again.
- When Hyper-V is selected, an image file may be
booted as a VM by adding a virtual network adapter while the
virtual network adapter is connected to the selected virtual
switch.
- Even if the host disk and the disk in the image
used to boot VM have disk signature collision, the VM can be
booted.
- Backup images created by enabling [a separate
image file for each disk] option may be used in combination with
the images concurrently created for other disks.
- In the event that an image is booted while the
VM is connected to multiple disks, regardless of SAN policy
status, any disk except for the system disk may be booted
online.
Back to
Table of Contents
Precautions before upgrading
When upgrading from earlier version to this
version on Windows 10/Windows Server 2016, please uninstall the
earlier version before you start installing this version.
Upgrading to this version fails if the earlier version is
installed.
Updates
- The following hypervisors are supported:
- VMware Workstation 12 Pro
- VMware Workstation 12 Player
- Windows 10 and Server 2016 Hyper-V
- Oracle VirtualBox 5
- You can continue to use a created and booted VM.
- You can select VM to boot according to the
timing you specify.
- The changes made after the VM is booted will be
saved in a differential file (*.aix) in local storage.
* When booting VM from differential image file
(*.aix), the changes made after booting up are saved (overwritten)
to the image file you specified when booting.
- Operating procedures for Update Check are
changed.
- You can use and configure the settings for proxy
server for Update Check.
- You can select a preferred language for console
display.
- Loading time for an image file created as a
result of consolidation of a number of incremental image files
is reduced.
Back to
Table of Contents
- Supports image files that
were created with [a separate image file for each disk] option.
Multiple images that had been created by same profile can be
loaded together to create their own VM disks.
- Changes in the differential image file (*.aix)
creation architecture.
- The created differential image file contains
only the data which is added or modified when running the VM.
- By using a base image file (*.aiv), the created
differential image file is associated to that base image file.
- By using an incremental image file (*.aii), the
created differential image file is associated to the that
incremental image file. To use this differential image file, the
image file set (from the base image to the incremental) is
necessary. Please note, if the used incremental image file was
lost (e.g. consolidatied by ActiveImage Protector), this
differential file is no longer useful.
- By using a differential image file, the changes
are applied to that selected differential image file. A new
differential image is not created.
- Fixed: Selection of a differential image file
(*.aix) that has been mounting to the host system. This issue
has been resolved.
- Fixed: Cannot boot a VM with error 12289 when
using VMware Player 6. This issue has been resolved.
- Fixed: Cannot display a virtual machine
connection window, error 28675 when using Windows Server 2008 R2
Hyper-V. This issue has been resolved.
- Fixed: Cannot launch GUI if a re-launch of GUI
is attempted when the original process has not completed. This
issue has been resolved.
Back to
Table of Contents
Back to
Table of Contents
Back to Index