Readme

During the upgrade process, the previous version of ActiveImage Protector will be completely uninstalled and the new version will be installed in its place. A reboot of your computer is required once the upgrade process is complete. If an error occurs during the upgrade process, it will be necessary to re-run the installer as ActiveImage Protector has been uninstalled from your computer.
If the ActiveImage Protector package includes a patch file, please install the patch immediately after the ActiveImage Protector installation is complete.
Ensure no tasks are running before applying any patch (e.g. backup tasks).
AIP 2016's detailed task logs cannot be viewed from the ActiveImage Protector 2018 console.
Credentials to access network shared folders that have been saved in the AIP 2016 console will not be migrated to AIP 2018 during the upgrade process. You will be prompted to enter your credentials again when you try to access shared folders from the AIP 2018 console.
* Backup task credentials are migrated during the upgrade process so you won't have to re-enter shared folder credentials for backup tasks.
If you have any tasks that have Post Backup Process options configured, please edit, update, or recreate the schedules for those tasks after upgrading to AIP 2018.
After upgrading to this version of ActiveImage Protector from AIP 2018 SP3 or earlier and migrating your schedule settings, be aware that the first time a task is executed, ActiveImage Protector will create a base backup image file (*.aiv), even if the next task is scheduled to run an incremental backup.
After upgrading the HyperAgent Edition of ActiveImage Protector from "Update 3" for AIP 2018, the hypervisors in the connection log in the HyperBack wizard and [Preferences] - [HyperAgent] - [Hypervisor] are displayed as unknown. If this occurs, please click [+] in the HyperBack wizard, double-click on the host name or right-click on the host name to display the host name.
If vStandby and HyperStandby tasks are created by using Update 5 or earlier version and migrated, the conversion target folder of the migrated tasks will be shared with Everyone full control when upgraded to Update 6 or later version. After upgrading, you can recreate the task and specify a no shared different folder as the conversion target.
Before starting upgrading / updating process, please ensure that no tasks are running. Also make sure no backup image is mounted.
When upgrading from Update 6 or earlier version to Update 7 or later version, you will be prompted to restart the system. However, the system may not reboot even when you click [OK] in the prompt message. In this case, please manually restart the system.
When upgraded from Update 6 or earlier to Update 7 or later version, the subsequent and first backup task creates a full backup file.
When push-upgrading from Update 6 or earlier version to Update 7 or later version, please push-uninstall the program before starting a push-upgrade.
If Microsoft .Net Framework 4 or later is not configured, the patch program will not be automatically applied in background.
Before manually applying the patch program, please make sure that no tasks are running.

Back to Table of Contents

Overview

ActiveImage Protector supports a maximum number of 128 disks per system, 24 volumes per disk, and 64TB per volume.
You are not allowed to edit Deduplication Compression level or Password Protection / Encryption by editing schedule setting.
When performing operations in ActiveImage Protector, please be sure to not select image files that are in use on another host. If selecting image files that are currently in use on another host, the operation may fail.
Example 1: If you attempt to restore an incremental file that is already being consolidated on another host, the task will fail and with an error..
Example 2: If you select an image file for consolidation that is mounted as a writable volume on another host, the consolidation task will be logged as having succeeded in the task history; however, the files will not have been consolidated.
ActiveImage Protector 2018 supports backup image files created by AIP version 3.5 SP7 or later.

* The ReZoom it! feature, used to restore virtual machines, is not supported.

If login credentials to access a network shared folder are changed, you may be prompted to restart the system.
If the [SMB 1.0/C IFS file sharing support] option is disabled on the system, the list of networked hosts will not be displayed when using the following features and you will have to manually re-specify the hostname to perform any operations.
Browse files and folders to select files.
Run the Restore Image Wizard
Run the Push Installer

* The behavior is the same on WindowsPE-based boot environments built with Windows ADK for Windows 10 Version 1703 or later.

If you deployed ActiveImage Protector via the Group Policy's [Software Installation] feature, the installer will not display progress during the uninstallation process. Please make sure the install folder is empty before restarting the system.
Your task may fail if you run a task that requires access to a network shared folder at the same time as a wizard creating another task is accessing that folder.
After a [Typical] or [Custom] installation and, enabling [Windows PE Boot Environment], if the system is not rebooted then the [Boot Environment Builder (Windows PE)] and [Boot Environment Builder (vStandby)] are not displayed in the console window. If this occurs, please reboot the system or restart the ActiveImage Protector Service.
Please do not select the backup image file of which file version is not supported. That image file will not be displayed in the console.
Even after uninstalling this product, the added iSCSI Server may not be deleted. In this case, please uninstall the iSCSI Servers respectively. Before uninstallation, ensure that the iSCSI Server is not used by any other application.
Operating a Linux FS in a backup image on Windows system is not supported.
When ActiveImage Protector for Windows is installed on the source system created / converted by using the following features, if there exists a scheduled backup task, the schedule is disabled on the created virtual machine. If you continue to use, please enable the schedule. The subsequent and first backup task creates a backup file according to the settings you configured.
Virtual Conversion
vStandby
HyperRestore
HyperStandby
Concurrent execution of backup tasks for Hyper-V host by using ActiveImage Protector agent and backup task for VM on the same host by using HyperBack is not supported. This is because a check point for a virtual machine cannot be created while taking a snapshot of Hyper-V host due to the limitation to Hyper-V hosts.。
Before staring uninstallation of the program, please make sure no task is running.
When using a backup image of Windows 10 system, ID4 event is alerted in Windows Event Log.
Mount Image
File Recovery (run from [Recovery] menu instead of HyperAgent)
Consolidate (Mount driver is installed, [Use Smart Consolidation] option is enabled for Post-backup Process)
Virtual Conversion (Conversion of an Image File)
HyperRestore
HyperStandby
When virtualized by specifying a mount point for CSVFS volume by using the Virtual Conversion, vStandby, or HyperStandby feature, the created virtual machine is registered as a VM on the specified Hyper-V host. If needed, the virtual machines can also be configured for high availability.

Software Activation

Activation is automatically performed at:
3 minutes after a system restart.
24 hours after the last activation occurred.
If the product key currently in-use is set to offline bundle, Actiphy's activation server does not accept activation of the product key.

Agent Version 5.1.11.6454 or later

An activation request is proceeded in the following order. For futher details, please access here.

Requests for a software license activation to Actiphy Authentication Service (AAS) in host name.
Requests for a software license activation to Actiphy's Activation Server
Discovers AAS's host name and requests for license activation

When activation request is submitted to AAS operateing in Server Mode, check-for-update feature is disabled.

Agent Version 5.1.11.6454 or earlier

When the agent is managed by ActiveVisor, the agent requests ActiveVisor for activation. If not managed by ActiveVisor, the agent requests Actiphy's activation server for activation.
When the agent is managed by ActiveVisor in internet-offline mode, check-for-update feature is disabled.

Back to Table of Contents

Backup

Incremental backup of a volume formatted with the file system other than NTFS and CSVFS uses differential backup process.

* Cluster Edition does not support backup of CSVFS volumes together with the volumes formatted with other file systems.

* Backup by disk does not support a disk including CSVFS volume.

Backup of exFAT volume uses full sector backup process (both base and incremental backup).
Multiple schedules can be configured for the same backup source, however, only one schedule can be started at a time. Please make sure not to configure the multiple schedules for the same time.
Should an incremental file become compromised, deleted or corrupted, the subsequent incremental backup can be taken, keeping continuity in the incremental chain with a valid incremental file.
Backup by Disk does not support dynamic disks. Only mirroring or simple dynamic volumes are supported.

Incremental backup process takes longer in the following cases.
The backup source volume includes a large file (ex: fixed VHDX). Changes are made and identified in the file.
Created base backup of the virtual machine using the fixed VHDX "in which there are no checkpoints".

* Created base backup of the virtual machine using the fixed VHDX "in which there are checkpoints". The incremental backup process was faster compared to the scenario with no checkpoints (proportional to the amount of the changed data in the virtual machine).

* If a checkpoint is created for the virtual machine using fixed VHDX in the midst of the image chain, the subsequent incremental backup process takes mostly the same time as backup. However, the following incremental backups will be faster (proportional to the amount of the changed data in the virtual machine).

When running online backup on Windows 10/Server 2016 or later system, ID513 error is recorded in Windows Event Log.
We do not support the combined use of this software with any other products that use VSS. If another VSS-related product is already installed, please ensure that no ActiveImage Protector tasks are scheduled while the other VSS product is running.
If you configured the settings to run both a backup and vStandby tasks, please make sure that both tasks are scheduled at different times to avoid conflict.
In order to execute a hot backup on a Windows machine running Oracle Database 11g, including creating a snapshot of database using Oracle VSS writer, the backup source database must be running in ARCHIVELOG mode.
The following URL in the Oracle Database Platform Guide provides details on how to perform Database Backups and Recovery using VSS:

http://otndnld.oracle.co.jp/document/products/oracle11g/111/windows/E05885-02/vss.htm

When an image file containing a system volume, created via a scheduled task is restored and booted for the first time, the following error below may be logged. This error does not affect the consistency of the restored source image file nor does it affect the restored system.

"Could not create an image file using the schedule <schedule_name>

If a backup is configured with the [Separate image file for each disk] option enabled and the number of disks you want to backup is changed, a full backup will be created instead of an incremental backup when the scheduled task runs.
The Boot Environment for Linux does not recognize virtual disks converted from ReFS formatted volumes and memory. If you use an ReFS formatted virtual disk to store system backups, the Boot Environment will fail.
You cannot use the Smart Sector backup option on a VMware vSphere hypervisor (ESXi) datastore larger than 2TB. Instead, enable the [Include free space in image] option and perform a full-sector backup.
Also, if the volume is formatted using VMFS version 6, a full-sector backup will occur since Smart Sector information is not available.
If you have configured backups for dynamic volumes which are on multiple disks, the image file name will not be displayed correctly in the Summary page of the Backup Wizard.
After a base backup image file is created for a new image set, when the image file was lost or corrupted for some reason, the subsequently created incremental keeps continuity with the incremental image set of the previous generation.
(6700) If a backup image file is successfully created, but an error is logged in the task log, that error will be displayed on the [Dashboard] -> [System Protection Status] screen and may be regarded as an alert.
If you define a scheduled task within five minutes of the scheduled start time, the task will not run until the following occurrence of the schedule.
When the host is restarted in the midst of backup process, the running backup task will not be automatically resumed. You need to execute the backup task again.
If you change the destination for saving backup image files from Volume A to Volume B, the files from Volume A will be duplicated on Volume B. This is necessary to maintain consistency. All backup files must be contained on the same volume in order to guarantee the consistency of the backup.
In the [Post-backup Process] section of the [Schedule] tab, if you enable consolidation and set the [Working Agent] to something other than [This computer], incremental backups will not run until the consolidation task is complete. After the consolidation task is finished, incremental backups will resume according to schedule.
If you enable the [Eject the destination USB device once the backup is finished] option, regular USB devices will be unmounted. NOTE: The [Post Backup] option will be disabled when this option is selected.
If you have an RDX license, you can configure ActiveImage Protector to eject the RDX cartridge once a backup is complete.

* This option is only available with Tangberg RDX devices.

* Please make sure the RDX Manager is installed prior to configuring RDX devices in ActiveImage Protector.

* The auto-eject feature only supports weekly schedules. Additional scheduling options are not available for these devices.

If a Microsoft BitLocker encrypted volume is included in the backup source for cold backup in Windows PE boot environment, full sector backup of the encrypted volume is taken.
During Windows Update, backup tasks will be skipped.
When a backup task is started with IT Pro Edition Update 5, Windows Update service will be suspended and resumed upon completion of the backup process. If a backup task is started while checking Windows Update, the process will be suspended.
Please keep the following in mind when backing up CSVFS volume on Windows Server 2008 R2.
Backup of a disk or a volume with no ownership is not supported.
Before starting backup task, please make sure that every virtual guest machines on a CSVFS volume are shut down.
Only full backup is supported. Incremental backup is not supported.
In a cluster environment on Windows Server 2012 or later, please make sure multiple backup tasks are not scheduled for the same CSVFS source volumes on multiple nodes at the same time when using Server Edition. If backup tasks are executed at the same time for the same CSVFS source volumes on multiple nodes, a VSS conflict could occur.
If you add CSVFS volume restored from a backup image to cluster shared volume, or delete the backup source CSVFS volume from cluster shared volume and then add again, because a different ID is assigned, the subsequently executed backup task will fail in error -455. In this scenario, please edit the backup schedule and select the CSVFS volume as the backup source again.
When configuring the settings for Post-backup Process, please schedule the incremental backup tasks with a suitable interval. With an insufficient time interval, the post-backup process may not behave properly within the interval.
When using a script for backup task of CSV volumes, please make sure that the specified script file is located in the same path on every backup node.

Deduplication Compression

When using the Deduplication Compression feature in ActiveImage Protector, you can only use single-byte alphanumeric characters to specify the path of the temporary work folder. Multi-byte and special characters are not supported.
Tasks executed against a backup image file created using the Deduplication Compression feature will take longer to process than tasks running against a file created with the Common Compression feature.

Back to Table of Contents

HyperAgent

VMware HA Cluster is not supported.

HyperBack

Pass-through disks, such as iSCSI targets, that are attached to a virtual machine system cannot be included as a backup source.
When targeting Linux virtual machines with databases (MySQL, etc.), please use the "FLUSH TABLES WITH READ LOCK" option to stop the database before running a backup task.
Specifying the same virtual machine as a backup source from the multiple hyper-agents is not supported.
ReFS is not supported.
When configuring the settings for Post-backup Process, please schedule the incremental backup tasks with a suitable interval. With insufficient interval, the post-backup process may not behave properly within the interval.

Deduplication Compression

Only single byte alphanumeric characters are supported in the temporary work folder setting for the Deduplication Compression feature.
Backups tasks that are configured to create backup images files using the Deduplication Compression feature may take more time than image files created using the Standard compression option.

Hyper-V Virtual Machine

It is recommended that you install Integration Services on the backup source virtual machines.
Backing up a guest virtual machine configured with Pass-through connected disk is not supported.
During the execution of a backup task in the following scenarios, a checkpoint snapshot is created for the guest virtual machine. This checkpoint snapshot is not automatically deleted when you delete the associated backup schedule and can cause future scheduled backups to fail. To prevent future backup schedules from failing, manually delete this checkpoint snapshot when working with:
Guest virtual machines running Windows Server 2012 R2 or earlier, or the first generation guest machine of Windows Server 2016 or later.
Virtual machines backed up with the Using Microsoft Resilient Change Tracking (RCT) option disabled in Preferences.
Running incremental backup tasks after executing one of the following base backup tasks and restoring to another checkpoint (snapshot) creates an incremental image file of the same size as the image created by re-executing the base backup:

Guest virtual machine running Windows Server 2012 R2 or earlier, or the first generation guest machine of Windows Server 2016 or later.
Virtual machine backed up with Using Microsoft Resilient Change Tracking (RCT) option disabled in Preferences.
Oracle on a guest virtual machine must run in Archive Log Mode. If Oracle runs in No-archive Log Mode, VSS will fail to ensure the data integrity of the backup on the guest virtual machine.
When you select clustered guest virtual machines for the backup source, the backup task will fail if the connection to the specified cluster node is not established before starting the task.
Backing up a suspended guest virtual machine is only supported on Windows Server 2016 Hyper-V or later.
If you import a version 5.0 second-generation virtual machine into Hyper-V on Windows Server 2016 or later, and you back up that virtual machine With the RCT option enabled, the process fails with Error-631.
If you run an incremental backup on a version 5.0 second-generation virtual machine using the RTC option on Windows 2016 or later and you change the checkpoint on the virtual machine, the backup will fail with Error-630. If this issue occurs, you will need to recreate a base backup of the virtual machine again.
To access Hyper-V host, you need to log in by using the built-in Administrator account. You are not allowed to use other accounts in Administrators group.

VMware vSphere Virtual Machine

We recommended that you install VMWare Tools on the backup source's guest virtual machine.
If VMWare Tools is not installed, the backup of virtual machines which have databases such as Oracle or Microsoft SQL Server installed will fail to ensure data integrity.
ActiveImage Protector cannot backup VMs that have Independent mode disks or physical compatibility RDM disks.
You cannot select a VM on an ESXi host that has more than 31 snapshots. Doing so will cause the task to fail.
Running an incremental backup task after running a base backup task and restoring it to another snapshot will cause the base backup to be recreated.
Running backup tasks on a running virtual machines may fail with Error-630. If you get this error, shut down the virtual machine and run the task again.

HyperRestore

If you run the HyperRestore task against an image that only contains a a subset of the volumes from a disk, only the volumes included in the backup will be restored. All other partitions will be restored as RAW.
Please remember the following when restoring to Hyper-V on a remote computer.
Ensure that Administrative share is enabled on the managed remote computer.
You need to log in by using the built-in Administrator or a user in the Domain administrators group. Other users in Administrators group are not authenticated.

Hyper-V Virtual Machine

Restoring uEFI system by selecting [Restore as new virtual machine] option, Secure Boot is enabled, by default, on the created virtual machine. Please change the setting, if necessary.
When [Only Restore Disk] option is selected to restore from HyperBack image, if a folder named the same as the source virtual machine exists in the restore target volume, the task fails to start with Error Code 12.

VMware vSphere Virtual Machine

When restoring a backup image of Hyper-V guest virtual machine to ESXi host, the operating system is not automatically selected in the wizard. Please select the same or a proximate version in the list.
When restoring a backup image of Hyper-V guest virtual machine (Generation 2) to ESXi host, you need to configure EFI setting before booting up the restored virtual machine.
Recovery of a virtual machine spanning 16 or more hard disks or connecting 10 or more NICs is not allowed.
Virtual disk restored to NFS datastore is created by Thick Provision Eager Zeroed.
Depending on the OS version of the backup source guest virtual machine, Operating System may not be automatically configured in HyperRestore wizard. In this case, please select the same or the approximate version to proceed with the wizard. When the restored virtual machine does not boot up, please check the disk controller of the restored virtual machine. If the type of the disk controller is not the same as the backup source guest machine, please select the same disk controller and boot up the restored virtual machine again.

HyperStandby

The use of differential image files is not supported.
When you run ActiveImage Protector or ImageCenter LE to consolidate image files including an image file selected by HyperStandby, it is recommended to not include the image file last used by HyperStandby.
If losing the continuity between the incremental image selected by HyperStandby and the incremental image last used by HyperStandby , all images in the series of images from the full (base) image to the target incremental image will be selected as the conversion source.
If the image file lastly used by HyperStandby is lost as a result of execution of consolidation task in ActiveImage Protector or ImageCenter LE, the entire images in the image set will be converted to boot points when the HyperStandby task is subsequently executed.
After changing the credentials information by selecting [Change Credentials] in menu, system restart is needed to apply the changes.
To convert a backup image file created by using Deduplication Compression, up to 600MB memory is used per task while running the task.
You may get the message saying "Boot Failed. EFI SCSI Device." during the process of the first boot-up of a standby VM on uEFI system, however, the system normally boots up.

Microsoft Hyper-V (Target)

Please remember the following when performing a virtual conversion to Hyper-V on a remote computer.
Ensure that Administrative share is enabled on the managed remote computer.
Please configure firewall settings to allow [File and Printer Sharing] on the remote computer. If the firewall settings are configured via Group Policy, go to [Network] - [Network Connection] - [Windows Firewall] and enable [Allow inbound file and printer sharing exception].
You need to log in by using the built-in Administrator or a user in Domain administrators group. Other users in Administrators group are not authenticated.
If you run a task while a standby virtual machine is up and running, the task fails in error.
Secure Boot is enabled, by default, on the standby virtual machine created from the backup image of uEFI.
If Secure Boot is not supported in the backup source system environment, please manually change the setting to disable Secure Boot when booting the standby VM.
If establishing the connection by selecting domain user from the connection history, you need to re-enter the credentials information again.

VMware vSphere (Target)

VMware vSphere Hypervisor 6.5 or later free license version is not supported.
If the free license version of ESXi host (VMware vSphere Hypervisor) is specified for the target host, standby VM and boot points are not created. VMDK files are created and updated.
If VMware vSphere is specified for the target host, VMDK files are created and updated from cold images (a backup image created in Linux-based or Windows PE-based Boot Environment).
If virtual conversion to vCenter Server of VMware vSphere or datastore on ESXi hypervisor, please establish the connection by using port 902. If you fail to establish the connection, please check the Firewall setting on the target host.
Virtual conversion of a backup image including 16 or more disks fails.
Migration by using vMotion is not supported.

Windows Image File

Backup images containing dynamic volumes are not supported.

Image List

The status in Image List is not correctly indicated.
Go to [Current Task] to monitor the task progress and [Task Log] tab in [Dashboard] for the tasks execution results.

Create / Edit Task

When OS and firmware are selectable in [Standby Setting] page, please manually select OS and firmware for the image and proceed.
Please remember the following when creating a task.
Up to 20 tasks can be concurrently executed.
Concurrent execution of multiple tasks for the same host and the same datastore takes longer process time.
Running a task for a datastore where a live virtual machine exists, depending on the actual usage conditions, the process time may be longer or the performance of live virtual machines may be impacted.

Linux image file supported by HyperRestore/HyperStandby

The backup images in version [209] of LVM system created by ActiveImage Protector 2018 Update Linux Edition are not supported. Only the backup images of basic partition configuration on Red Hat Enterprise Linux/CentOS 6.x are supported.
When using a backup image of EFI firmware on Red Hat Enterprise Linux/CentOS 6.x, CentOS 7.5 or earlier, you need to create a boot entry before booting up the created VM.
In case you created a VM on Hyper-V by using a backup image of EFI firmware, please manually change the setting to disable Secure Boot before booting the standby VM.

To use the backup images created by using ActiveImage Protector Linux Edition, please enable [Create a virtual machine compatible image] option in the setting for backup task. Please aware of the following limitations:
Backup image of multiple VGs is not supported.
To create a standby VM from an image file of LVM system, the backup images are supported only if the backup source VG is configured with a single PV including the entire volume of "/dev/sda" excluding "/boot/efi” and "/boot"on "/dev/sda".
As for the Standby VM created from Linux image, the schedules created in ActiveImage Protector are not disabled.
IP address setting supports DHCP only.
If OS information is not included in the image files selected by HyperStandby, free license version of ESXi server and storage server are not supported to create a task.
The backup image of a system configured on mdraid is not supported.
Before restoring or creating a virtual machine from a backup image created by using HyperBack on different hypervisor, please enable [Create a virtual machine compatible image of Linux system] option to run the backup task.

File Recovery

After selecting "Recovery Point", the volume including the item you selected to restore may not be indicated under [Mounted] in [File Recovery]. In this case, please try the following:
Go to [Disk Management] of the operating system.
Check if there is a volume assigned with a drive letter in the disk as the image applicable to the specified recovery point is mounted as the disk.
If there is a volume assigned with a drive letter in the disk, please delete the drive letter and start the wizard by selecting the recovery point again.
File Recovery does not support backup images including a volume formatted with the file system which the computer to run the task does not support.
If a backup image or archived image is copied to the specified destination, the indicated "Recovery Point" is date/time-stamped the same as the original.
If 25 or more of volumes are included in an image set, or if the total number of the mounted images and the images which file recovery is in progress becomes 25 or more, restore of the 25th or later volume fails.
If restoring the files under the root of the image or in hidden attributes folder, the restore target folder attribute is "hidden" until the recovery process completes.
In the event of restoring a folder including a massive amount of items or a huge file, the progress bar may be indicated as follows:
The progress bar remains to be 1% for some time.
The indication of the percentage remains to be the same for some time (in the event that you selected a number of items for restore source).
It takes some time from 99% until the task completes.
When you select a folder to restore, the restoring folder name is appended with "-Recovering". In the event that you cancel the task in process, the folder name remains to be appended with "-Recovering".
Alternate Data Streams (ADS) of a folder are not retained. If you selected the destination formatted with FS which does not support ADS, the file's ADS is also not retained.
Recovery of EFS encrypted file / folder is not allowed.

Back to Table of Contents

Post Backup Process

The tasks other than HyperBack / HyperStandby tasks and post-backup processes run sequentially.
For example, if a replication task is configured for the target that can deliver only slow write speed, the subsequent tasks will run only after the replication task completes. In this case, you need to shift the replication task to a later schedule.
The multiple post-backup tasks configured for one backup task will run in the following order:
Immediately / When new xx image files are created:1 Verify Image, 2 BootCheck and Replication, 3 Consolidation
At xx:xx: The tasks run at the specified time.

Using Destination Isolation option with a Post Backup Process is not supported.

BootCheck

Please ensure Actiphy iSCSI Service is running. This service is not started automatically if you install ActiveImage Protector prior to configuring the Microsoft .NET Framework (version 4.0 or later).
Please configure your firewall to allow File and printer sharing and Windows Management Interface (WMI) when using Hyper-V on a remote computer.
Please ensure Virtual Conversion is enabled on the computer running BootCheck. For more information on how to enable Virtual Conversion, please contact the manufacturer of your computer.
Since BootCheck bootstraps systems from backup images, you'll need to be aware of the limitations of the hypervisor you are using before implementing BootCheck. For example, since Hyper-V does not support using uEFI to boot Windows Server 2008 R2 and Windows 7 x64, BootCheck will not work in these situations.
Please do not enable BootCheck when configuring tasks against backup sources that do not have system volumes.
BootCheck is not supported when active partitions (e.g. system reserved area) are not included in the backup source.
BootCheck does not support cases where the boot partition and system partition are on different disks.
BootCheck uses 1 GiB of memory on the hypervisor.
Image files of BitLocker encrypted system are not supported.
Running a BootCheck task for a backup image of a system configured on a dynamic volume is not supported.
Running a BootCheck task for a backup image of Linux virtual machine is not supported.
BootCheck provides confidence that the backup images are bootable. BootCheck does not guarantee that every features normally work when the system boots up.
If shutting down or rebooting the system, BootCheck's virtual machine remains on Hyper-V host of the working agent. Before shutdown / reboot the system for the sake of system maintenance please make sure BootCheck is not running. You are also recommended to apply Windows Update which requires system restart while BootCheck is not running.
If the virtual machine for BootCheck remains on Hyper-V host of the working agent, please delete the virtual machine from Hyper-V host.

Replication

If WebDAV is selected as the replication target, the progress percentage of the task does not increase since the start until the completion of the task. If you select multiple files for replication source, the progress percentage increases for the ratio of the processed files to the total source files upon completion of the replication task
If WebDAV is selected as the replication target, Pause/Resume does not work for the task.
In the system environment with 8GB or above memory, network throttle does not work.
While you are configuring the replication target setting and you select Amazon S3, a new bucket cannot be created.
When backing up CSV volume and accessing SFTP server by using Private Key, the specified Private Key file has to be located in the same path on every backup nodes.

Back to Table of Contents

Recovery

Backup images created by HyperBack are not supported.

Volume Recovery

Backup images cannot be restored to disks with a different sector size than the backup source disk.
If you have multiple hard disks connected to your system and one of the drives has the same signature as the source disk, you will need to select Use disk signature of restore target in order to restore.
Restoring to two or more bare-metal hard disks is not supported.
Restore a backup image file including a volume formatted with a file system other than NTFS in enlarged size is not supported.
When you restore the MBR or first track of a disk, the MBR or first track in the base backup image is used during the restore process.
The Restore drive letter option is not supported.
Tasks that restore backups to bare-metal disks or that restore multiple backups at the same time may result in a -701 error. If you encounter this problem, please retry the restore task again.
You will need to select the restore target from the context menu in boot environments created using Windows 10 ADK. Dragging and dropping restore sources to restore targets is not supported in this scenario.
When you select Restore by Disk to restore an image of an MBR disk onto a bare-metal disk, the largest supported volume size is 2TB.
Partitions created using Create Partition will be unformatted.
There is a limitation in the Restore Wizard that won't allow you to create multiple partitions via the Create Partition drop-down menu and then restore multiple volumes to those partitions. To work around this limitation, you will need to create a single partition and then restore a volume to that partition. You will need to repeat this process, one partition at a time, until you have restored all volumes into these new partitions.
You cannot recover an entire system on mirror-configured dynamic volumes.
You cannot restore split-images with deduplication compression from optical media.
You cannot restore uEFI system-disk images with ratio expanding, even if you select a larger disk than original disk as the restore target.
When restoring only the system volume on a bare-metal recovery, if you use the option Restore as BIOS boot system, the Boot Configuration Data (BCD) will be created with hypervisorlaunchtype set to "Auto".
When restoring a backup source volume / disk which backup schedule is configured, incremental backup is executed after restoring the volume / disk, keeping continuity in the existing incremental chain.
When restoring mirror-configured dynamic volumes, you need to restore both primary and secondary disks.
Backup by Disk does not support dynamic disks as the restore target. Only mirroring or simple dynamic volumes are supported.
Creation of a partition on dynamic disk is not supported.
Restore of dynamic volume supports overwriting restore on existing volume on dynamic disk and restore by volume to basic disk.

File Recovery

Before using the File Recovery feature, please make sure that the mount driver (ActiveImage Mount Component) is configured.
File Recovery does not support backup images that include a volume formatted with a file system that the computer running the task does not support.
Before you enable the Keep Access Control Lists option on Windows XP/Server 2003, please make sure that the Windows Server 2003 Resource Kit Tools is enabled.
If there are multiple copies of the same backup or archived image file in a backup destination, in the user interface multiple date/time-stamped Recovery Points will be displayed.
If you include more than 24 volumes in an image set or if more than 24 of the total number of images are mounted while file recovery is in progress, the restoration of all volumes after the 24th will fail.
If the restore source files include files under the root of an image or in a hidden folder, the attribute of the restore target folder will be "hidden" until the recovery process completes.
If you restore a folder that includes a large number of files or a file that is large in size, the progress bar may:
Remain at 0% for an extended period of time, in the case of a single large file.
Seem to hang at various percent markers if multiple large files are present.
Take a long time to move from 99% to a completed state
When you select a folder to restore, "-Recovering" will be appended to the folder's name. In the event that you cancel the task while it is in process, the "-Recovering" part of the name will remain.
If you select a destination in the file system that does not support Alternate Data Streams (ADS), the file's ADS information will not be retained.
Restoring from an optical media is supported, but only if the image is saved on one optical disk. Restoring an image that spans multiple optical disks is not supported.
ActiveImage Protector does not support the recovery of EFS encrypted files and folders.
File Recovery in the IT Pro Edition may fail with the error, "Device not found." If you get this error, please try again.

Image File Management

Consolidation and Archiving Incremental Backup Files

Before running consolidation tasks, please make sure that at least the same or more available space than the size of consolidated image files is in the storage of source image files.
While executing an incremental backup task on the backup source host machine, a consolidation task for the image file set cannot be executed from another host. Please execute the consolidation task only after the incremental backup task is completed on the backup source host machine.
If any of the following conditions are met in the system environment or consolidation source, even if some data are deleted from incremental image files up to the latest one, the processed image size is not decreased by the deleted data size but may increase.
Mount driver is not configured in the system environment.
Source volume is formatted with file system other than NTFS.

Mount Backup Image

Up to the maximum number of 24 volumes are supported to mount in the product. Other than this feature, [File Recovery] feature allows to mount the volumes included in an image.
The entire volumes included in the image are mounted, when you proceeded with [2. File Recovery] in Restore File Wizard.
While File Recovery is in progress, the volume including the items to restore is mounted.
The backup images created by HyperBack are not supported.
You may get "Device not found" error in IT Pro Edition. If you get this problem, please try again.

iSCSI Target Server

Please make sure Actiphy iSCSI Service is running and remember that this service is not automatically started if Microsoft .NET Framework 4.0 or later is not configured when installed.
The volume formatted with FS which the connected system does not support cannot be used even after iSCSI Target is connected.

Back to Table of Contents

Virtual Conversion

Virtual conversion from image file or physical disk

Virtual conversion does not support dynamic disks as a conversion source.
Virtual conversion does not support backups of dynamic volumes as a conversion source.
If you perform a virtual conversion with thick provisioning (for VMware products) or fixed virtual disk size (for Microsoft Hyper-V), the process time may be significantly longer depending on the source disk size.
When converting from image files, the task execution progress may appear to be stopped 0% after the task is started. This task isn't stopped and will increase as the file is processed.
If the task doesn't start when converting to a target location on VMware vSphere vCenter Server, please specify an ESXi host directly as the target for conversion.
P2V Conversion to ESXi 6.5 or later host must be performed from a 64-bit OS.
Virtual conversion of a hard disks that don't have a logical sector size of 512 bytes will fail.
Backup images created by HyperBack are not supported.
[Convert from Disk] in IT Pro Edition may fail with a "pipeline error". If you get this error, please try again.
If virtual conversion to ESXi host fails in Error -4101, apply Windows Update and try again.

for VMware products (conversion to virtual machines)

Network names containing double-byte characters are not displayed on wizard.
Conversion to datastores on ESXi 4.x hosts is not supported.
If no destination folder is specified, the files are created in root directory on the datastore.
(6532) Conversion to NFS datastores is not supported.
(7655) You cannot convert more than 16 HDD in the same task.

for VMware products (conversion to virtual disks)

Before selecting a local or shared folder as a destination, please ensure that the location is NTFS formatted. Storage destinations formatted with Linux file systems, FAT/FAT32, etc. are not supported.
Direct conversion to a new folder is not supported when converting to a VMWare ESXi host running VMware vSphere free license.
Virtual conversion to ESXi 6.5 (or later versions) is not supported.

If you select a vCenter Sever for virtual conversion, the created virtual machines are created as follows:
If you specify no folder or specify an existing folder：tempVM＜task start date and time＞

After the process completes, please delete the virtual machine from the inventory using the vSphere Client.

After copying the vmdk file to another folder/path, please delete the temporary created folder if its unnecessary.

If you create a new folder： the created folder name

After the process completes, please dispose the registered virtual machine from the inventory by using vSphere Client.

Please delete the vmx or vmsd file in the created folder if unnecessary.

for Microsoft Hyper-V (conversion to virtual machines)

Please remember the following when performing a virtual conversion to Hyper-V on a remote computer.
Ensure that Administrative share is enabled on the managed remote computer.
You need to log in by using the built-in Administrator or a user in Domain administrators group. Other users in Administrators group are not authenticated.
uEFI system conversion is supported only with conversion target host supporting Generation 2 virtual machines.
If a Hyper-V host on Windows Server 2008 R2 is selected as the target host, the network settings are not applied to the created virtual machines.

for Microsoft Hyper-V (conversion to virtual disks)

Conversion to VHDX format is only supported on Windows 8/Windows Server 2012, or later, operation systems.

Virtualization Adapter

Please make sure Actiphy iSCSI Service is running and remember that this service is not automatically started if Microsoft .NET Framework 4.0 or later is not configured when installed.
Virtualization Adapter does not support Windows XP (x86/x64), Server 2003 (x86/x64).
You may get "Unknown platform error" in IT Pro Edition. If you encounter the problem, please try again.

Back to Table of Contents

vStandby

Dynamic disks, storage spaces, and 4K sector native hard disks are not supported as the source disk.
Double-byte characters cannot be used to specify virtual machine names or a VMDK file names.
WINS addresses are not supported when configuring network settings for a virtual standby replica.
Deleting virtual standby replica deletes the created virtual standby replica only.
In [Preparing Virtual Standby Replica...] dialog, there may be instances that an existing virtual standby replica cannot be deleted. If you encounter this problem, please use the vSphere Client to manually delete the virtual standby replica, or change the name of the new virtual machine.
If a NIC or a disk is added to the source machine only after the virtual standby replica was created, the changes are not applied to the newly created virtual standby replica. If you encounter this problem, please delete the schedule and recreate virtual standby replica.
If you configured the settings to run both a backup and vStandby tasks, please make sure that both tasks are scheduled at different times to avoid conflict.
If you selected Thick Provisioning for Disk Provisioning (Disk Type) or Static, it takes more time to create a virtual disk as the virtual disk depending on the size of the conversion source disk.
The boot point created after upgraded to the current version should include the full data just like the first boot point.

VMware vSphere

VMware vSphere Hypervisor 6.5 (ESXi) or later free license version is not supported.
If free license version of ESXi host is specified for the target host, vStandby creates VMDK files in the specified datastore instead of creating virtual standby replica and boot points.
VMDK file created on free license version of ESXi server is not supported to restore to physical environment.
If an NFS datastore is specified as the target, thick provisioned virtual machine is created.
If the ESXi host is set to maintenance mode, a virtual standby replica cannot be created. Creation of boot points terminates with an error.
Virtual conversion of 32 bit OS to ESXi 6.5 or later host is not supported.
If virtual conversion via vCenter Server of VMware vSphere fails, please directly specify ESXi hypervisor as the target.
If a network name is specified using a double-byte character, it cannot be indicated in the wizard.
(7894) Virtual conversion from 16 or more hard disks is not allowed.
If failed in Error -4101, apply Windows Update and try again.

Microsoft Hyper-V

Ensure that Microsoft .NET Framework 4 or later is installed on the host on which vStandby tasks are executed.
Ensure that Administrative share is enabled on the managed remote computer.
Please configure firewall settings to allow [File and Printer Sharing] on the remote computer. If the firewall settings are configured via Group Policy, go to [Network] - [Network Connection] - [Windows Firewall] and enable [Allow inbound file and printer sharing exception].
You need to log in as the built-in Administrator account. The use of an account in Administrator group shall not be authenticated.
uEFI system conversion is supported only with conversion target host supporting Generation 2 virtual machines.
uEFI system conversion is not supported for Windows Server 2008 R2/ Windows 7 source machine.
Execution of a task, while a virtual standby replica is up and running, fails with an error.
If Hyper-V target host on Windows Server 2008 is selected, virtual switch settings are not applied to virtual standby replica.
(8465) Restoring virtual standby replicas created on Hyper-V target host on Windows Server 2008 R2 to physical machine is not supported.
The pull-down list for selecting a folder is not scrollable. If you want to select an unshown folder, please select [New...] and specify the folder name.
The virtual standby replica deployed from ActiveVisor are created as follows:
Virtual hard disk file：Folder named with the virtual machine in "vStandby_x" folder shared with Everyone full control
Except for virtual hard disk file: The default location on Hyper-V target host

Back to Table of Contents

Boot Environment Builder (Windows PE)

To create USB boot media, please make sure 1GB or more available space in USB device. If USB HDD is selected as the target device, the boot area is built in the first 2GB and the rest is reserved as data storage space.
To create (Windows PE-based) Boot Environment (ISO or PreBoot environment), please make sure Windows AIK or Windows ADK is configured in the system.
Windows ADK needs to include the following components:
Deployment Tools
Windows Pre-installation Environment (Windows PE)
To create boot media or to create a PreBoot environment on a BIOS boot system, it is recommended to use Windows AIK or Windows ADK of the same version as the system.
To create PreBoot environment in a uEFI boot system, please use the following Windows AIK or Windows ADK depending on the system environment.

Windows 10/2016

Windows ADK for Windows 10 (Windows Assessment & Deployment Kit for Windows 10)

Windows 8.1/2012R2

Windows ADK 5.1（Windows Assessment & Deployment Kit for Windows 8.1 Update）

Windows 8/2012

Windows ADK 4.0（Windows Assessment & Deployment Kit for Windows 8)

Windows 7/2008 R2

Windows AIK 3.0（Windows auto-installation kit for Windows 7 SP1)

Built-in device drivers must support Windows PE based OS version to create the boot environment. Windows PE based OS version will be displayed in "Detailed information of the Windows PE tool" in [Windows PE kit] of [Windows PE based boot environment builder].
Boot environment in a USB device using Windows AIK 3.0 (Windows auto installation kit for Windows 7 SP1) is not supported to build in uEFI environment.
You can build Boot Environment of the same bit version as OS only.

Back to Table of Contents

Boot Environment Builder (vStandby)

To create USB boot media, ensure that there is 1GB or more of available space in the USB memory.
To create (Windows PE-based) Boot Environment, please make sure Windows ADK is configured in the system.
Windows ADK needs to include the following components:
Deployment Tools
Windows Preinstallation Environment (Windows PE)
To create 64-bit Boot Environment (Windows PE), you need to build the boot environment on 64-bit OS.
Built-in device drivers must support Windows PE based OS versions to create the boot environment. Windows PE based OS versions will be displayed in "Detailed information of the Windows PE tool" in [Windows PE kit] of the [Windows PE based boot environment builder].
(9155) Use of Windows AIK does not allow to build Boot Environment (Windows PE).

Back to Table of Contents

Boot Environment (Linux)

uEFI boot with secure boot option is not supported. With CSM (Compatibility Software Module) enabled, uEFI boot is supported in legacy mode (MBR) or compatible mode. With CSM disabled or if CSM boot is enabled in uEFI mode only, uEFI boot is not supported.
Add Device Driver feature is not supported.
If a single byte space is included in the path to storage destination for saving volume backup image, you may encounter an error.
If a Windows 7 system disk or later is created in Boot Environment and restored in Windows module (including Windows PE boot environment), please execute restore task without changing restore settings. Should you change restore settings, disk meta data is not restored and the restored system fails to boot up.
Once Boot Environment boots up, please do not remove the media until all operations are complete.
If clicking on [Create Support Info], the message dialog is not displayed. The support information file is created in "/opt/BE" in the following format:
AipSupportInfo_yyyymmdd_hhmm.tgz
Drive letters indicated in disk map are not consistent with those in Explorer for browsing a file.
When overwriting to restore the mounted volume, please unmount the target volume by selecting [Utilities]-[Mount (Local)] before you proceed with further operation.
You cannot restore split image from optical media.
(7669) You cannot mount image.
Before you start using USB HDD, please make sure that the USB HDD is connected to the system before booting up. If you use network shared folder mounted to the system, ensure that the network shared folder is mounted before launching Restore Image Wizard. In the event that you connect USB HDD to the system or mount the network shared folder only after Restore Image Wizard is launched, the USB HDD or network shared folder may not be displayed in [Backup Destination].

Back to Table of Contents

Boot Environment (Windows PE)

You can access a network shared folder by taking the following operating procedures:
Directly access in Explorer.
Go to [Utilities] - [Network Setting] and create network drive to access.
Japanese language input is not supported.
To use the Deduplication Compression feature, folders on local storage can be selected as temporary work folders.
Once Boot Environment boots up, do not remove the media until all operations are complete.
Conversion to VHDX file is not supported in boot environment created by using Windows AIK 3.0 (Windows Automated Installation Kit for Windows 7 SP1).
In the event [Utility] - [Restore Boot Setting] - [Create BCD] is selected to run for the system which has no Boot Configuration Data (BCD), BCD is created with [hypervisorlaunchtype] set to "Auto".
Execution of a backup task is not allowed in boot environment built in the environment where HyperAgent license is applied.

Back to Table of Contents

Boot Environment (vStandby)

Japanese language input is not supported.
Please do not eject the media once the system is started until the operation completes.
(8465) Restoring virtual standby replicas created on Hyper-V target host on Windows Server 2008 or 2008 R2 to physical machine is not supported.
Restoring VMDK file created on free license version of ESXi server to physical environment is not supported.
Restoring from virtual standby replica created on VMware vSphere 6.5 or later host is not supported. Please create a backup image in the virtual standby replica and restore the image to the source machine.
Restore via vCenter Server fails. Please establish the connection directly to ESXi host where the virtual standby replica is configured and restore.

Back to Table of Contents

Image Explorer

Copying a large number of files may take a long time to complete.
Internal files cannot be booted from an image file.
Browsing the contents of ReFS and Linux file systems is not supported.
File properties are not maintained when copying file. If file properties need to be maintained, please use the Mount Image feature.
Items in the image file are grayed out in the UI, however, you can browse or copy items inside folders.
HyperBack images created are not supported.

Back to Table of Contents

Push Installer

Push Installer supports version 2016 R2 or later installation packages.
You cannot select a remote host which does not return response to Ping command.
To obtain a host list from Active Directory, please make sure that the settings for Ping command with Active Directory name to be responded from searching host.
If incomplete search result is obtained, please retry the searching.
Cancelling host search may take long.
Before you execute Push Installer, please make sure that the log-in user has administrative right and is authorized to access administrative shared resource on the target host.
Upgrading by Push Installer supports the version 2016 SP1 or later.
Upgrading by Push Installer can migrate the entire existing files including setting files and schedules.
Uninstallation by Push Installer deletes all files. If you select [No reboot on uninstall] option, some of the files are not deleted until the system is rebooted.
The use of the installation package for Version 2016 installs the package in every languages licensed with the product key.
The combined use of an unsupported installer and the product key enables you to push installation. Upon completion of push installation, even if "Succeeded" is indicated for the status, the installation is not completed on the target host. Please check and see if the installer is combined with the proper product key.
HyperAgent Edition is not supported.

Back to Table of Contents

Remote Client Management Console

Remote Host Management List supports the following versions for monitoring the status :
Windows Edition：Version 3.5 SP7 or later
Linux Boot Environment：Version 2016 or later
Windows PE Boot Environment：Version 2016 or later
Linux Edition：Version 2016 or later
Boot Environment：Version 2016 or later
When multiple schedules are created on the remote host, only the schedules for the most immediate execution are listed.
(7532) To select any host from the search result, please click on the host name. The checkboxes may be disabled even if you click on.
In the event that the host name on Remote Host Management List is changed, please delete the host name from the list and add it to the list again.
When adding the remote host which booted into Boot Environment to the list, please enter "root" to user name/password.
HyperBack task is not supported.

Connect to Remote Host

Connection only to version 2018 agent is supported.
If AIP was installed by selecting [Typical] or [Custom] - [Firewall Setting], the following TCP/UDP port rules required for network communication with the agent are applied to the inbound rule settings for Windows Firewall
AIP Console（TCP/UDP）
AIP Push Installer（TCP/UDP）
AIP Service（TCP/UDP）

If AIP was installed with otherwise configured settings, ensure that the Windows Firewall exception settings are configured for the following TCP/UDP ports on both managing and managed host's OS in order to include the remote networked computers in [Connect to Remote Host] list on which the AIP agent is installed.

TCP Port 48236
UDP Port 48238
UDP Port 48239
Windows File and printer sharing
If you change any of the above port numbers, a restart of the ActiveImage Protector Service is required.
To connect to an AIP agent on a remote host, the same or lower version of AIP agent as on local host must be configured on the managed remote host. A connection to AIP agent of upper version than the AIP agent on the local host cannot be established.
To connect to Boot Environment agent, please enter "root" in User Name and Password.
To connect to AIP agent Linux Edition, log in as "root" user.
When connected to Boot Environment (Windows PE) agent, AIP CLI is disabled.
To disconnect from a remote computer, select [Connect to local host]. The same is true if there is no agent installed on local host.
When connecting to Version 2016 Linux Edition agent, you cannot use the following functions.
[Image Manager] - [Mount] menu
[Advanced Options] - [Scripting] - "Run on" menu in Schedule Backup

Back to Table of Contents

Other Utilities

Use the Event Log Viewer to monitor the latest 200 events. If the number of events logged in the period you specify exceeds 200, no events are displayed.
All contents may not be displayed in Task Summary.

Back to Table of Contents

ReZoom it! (Restore Virtual Machines)

Before you start using ReZoom it! wizard, please make sure that you use the backup image file meeting the following conditions:
The backup image file must be created by using ActiveImage Protector 2016 for Hyper-V Enterprise or later.
The backup image file must include the following:
System volume (disk)

* To back up stand-alone Hyper-V host

The volume (disk) that includes the configuration file of the virtual machine and virtual hard disk file, the created snapshot.

ReZoom it! feature does not support restoring virtual machines from an image file that does not meet the above conditions.

ReZoom it! feature does not support the use of an image file created by Cold Backup feature.

Restoring to an earlier version of a Hyper-V host than the backup source host version is not supported. Restoring to Hyper-V host of the same or later version is supported.
Restoring a selected virtual machine from backup image file of Windows Server 2008 (Hyper-V 1.0) is not supported. Windows Server 2008 (Hyper-V 1.0) is not supported as the restore target either.
Even when the processor makers of the backup source Hyper-V host and restore target Hyper-V host are different, restoring virtual machines is allowed.

Restore of a virtual machine, which a differential virtual hard disk file created by using Hyper-V Manager is connected to, is not supported.

In the event that you cancel a task for restoring a virtual machine, the in-processing file may remain on the restore target host. If you encounter the problem, please manually delete the file.
If you select a password protected backup image file and enter an invalid password, please cancel the selection of the image file in ReZoom it! wizard and reselect an image file.
If you select a backup image file from the file’s History in network shared folder, and in the event that you are not authenticated to access from the system to the folder yet, you should not be allowed to select the image file. Please ensure that you are authenticated to access from the system to the folder before you try to select the image file again.
ReZoom it! does not support restoring a virtual machine named with a double-byte character or the config file name / path is defined by using a double-byte character.
It is recommended to use this feature in an environment where sufficient memory is available other than the main memory used for the live VM. In the event that booting a VM fails due to insufficient memory, please re-configure the memory setting to decrease the memory size for the live VM by using Hyper-V Manager, and try again.
In the event that the changes made during the operation of the live VM created by ReZoom it! Live feature are not merged with the ReZoomed virtual machine, the virtual disk file (xxxx_vhdx_rezoom.vhdx/xxxx_vhd_rezoom.vhd) used when booting the live VM remains in the restore target. Deleting this file does not cause any problem, so delete it if necessary.
If the connection to live VM booted by ReZoom it! Live is not automatically established, please establish the connection from Hyper-V Manager.
ReZoom it! does not support restoring a Linux guest virtual machine.

Back to Table of Contents

IT Pro Edition Creator

Windows ADK (or AIK) is required to create ITPro Media. When using the ADK to create media the following Windows ADK components must to be installed.
Deployment Tools
Windows Preinstallation Environment (Windows PE)
Please take into account, the following limitation when using the DVD media option to write media ISO When creating an ISO file and the DVD media option is selected to write the created ISO file:
Only blank media can be used to write ISO file. If you have to use RW media, please make sure that all data is purged from the media.
To use USB memory, please make sure you have USB memory with more than 1GB. 32GB or more media is not supported.
Creating a USB flash drive bootable environment by using Windows AIK 3.0 (Windows Automated Installation Kit for Windows 7 SP1) in a uEFI environment is not supported.
Depending on the display type, you may encounter the problem that the screen display is not properly adjusted to the screen resolution setting you configured.
Available device drivers have to support Windows PE OS version which the creating boot environment is based on.
Depending on the device driver type, addition of the device driver to boot environment media may fail. If this occurs, please boot up ActiveImage Protector Boot Environment (Windows PE) and go to [Utility] - [Driver Loader].
(7184) When you select network shared folder for the destination to save ISO files, you may get an error (GetDiskFreeSpaceEx). If you encounter this problem, please allocate a network drive for the network shared folder or specify a local storage for the destination.
Running an execution file (EXE) created in the environment where user account control feature is enabled on desktop OS or other OS, you will get "Publisher: Unknown" message. If you encounter this case, please press [Yes] and boot up the OS.
When starting IT Pro in USB media, the console may be displayed in English. In this case, please close the console, restart it, go to [Help] - [Change Language] and select a preferred language.

Back to Table of Contents

Others

Before using this product, ensure that [Windows System Restore] (System Protection) is disabled.
If using a disk de-defrag utility along side this product, it is highly recommended to create a full backup image after the completion of a defrag process. Disk de-frag software may change sectors on the disk and cause the size of incremental backup files to increase
When migrating virtual systems from VMware virtual environments to other hypervisors or physical computers, uninstall the VMware Tools from virtual guest machines before creating backup image files used for the migration.

Back to Table of Contents

Back to Index