Please carefully read this document
March 11, 2024
This document contains information about the limitations to the use of the product.
It is highly recommended to read through this document before using this product.
For system requirements, please visit System Requirements.
Notes on upgrading/updating ActiveVisor
-
You are not prompted to enter the product key when installing the product.
-
When upgrading from Version 6.0.2.1507, please be aware of the following limitations.
- The templates and the product key for Version 2018, hypervisors except for Hyper-V/ESXi are not migrated.
- Web access, when enabled, is disabled.
Basic Points
-
This version supports agent of the following version.
- ActiveImage Protector 2022
- Management and operation of agent version 6.0.0.7292 or later are supported.
- ActiveImage Protector 2018
- Management and operation (except for push install) of agent version 5.1.11.6454 or later are supported.
- ActiveImage Protector 2022
-
You are recommended to operate Linux agent by using remote console. As you need to have root privilege to access Linux agent, please register the computer as root user. When operating agent installed on the computer added to the list from Active Directory, please log in as root user. If not using remote console, only the following operations are supported.
-
Monitor task status, log information
-
Operation of existing backup tasks
-
Activation
-
Reboot / shutdown system
-
-
Uninstallation of Linux agent does not update the information.
-
ActiveVisor does not support management, monitoring or operation of agents where the annual support service contract has expired, even with a product key applied.
-
The settings configured in ActiveVisor are always given priority for email notification. If the agent settings for email notifications are configured, or if task(s) or settings are deployed from ActiveVisor with the option, [Use ActiveVisor to send email] is set, or if agent settings are directly changed, then the agent settings for email notification are cleared and email notifications will not be sent directly from the agent. When resending email from the agent, please select [Use custom settings] in Agent Settings in ActiveVisor and configure the agent settings for email notifications again.
-
When an IP address is duplicated among PCs, the information of the PCs is not correctly displayed or the operation may fail. Please keep that in mind when you obtained the IP address through DHCP.
-
When the information of network computer list in Client tab is not updated, right-click on the computer, select [Delete] and try restarting the computer.
-
When referring to Active Directory, even when the computer on which ActiveImage Protector is installed joins domain, if IP address of the computer is not registered to DNS, the computer is recognized as “Network Computer”. In this case, register IP address of the computer to DNS and try rebooting the computer.
-
The client, when patch program is automatically applied, may be moved to unmanaged. To move the computer to [Managed], right-click on the computer and select [Move to Managed] from the right-click menu.
-
When ActiveVisor is not accessible from the client booted from RescueBoot, management / operation of the client is disabled. You are recommended to confirm the following points in advance.
-
NIC is recognized.
-
Valid IP address is obtained.
-
-
The domain computers selected from Active Directory and registered to the list cannot be deleted from the client list. Uninstallation of ActiveImage Protector enables you to move the computer from [All clients] list to [Networked computer] list.
-
When a task is created on agent by deploying backup template by enabling [Create sub-folder for each client] option with an earlier version and the agent is moved to Managed, the backup destination is registered in [Site Setting] - [Storage Device] including the sub-folder named with the computer name. With Version 2022 agent, under the sub-folder, a subsequent sub-folder in unique name is created for backup storage saving the backup images.
-
When selecting [Edit client setting] - [Backup and Standby] in the context menu displayed by right-clicking on a managed agent, the command displayed in the pull-down menu is disabled.
-
In the environment where [SMB 1.0/CIFS client] is not installed, [Add Computer] - [Auto-discovery] fails in Windows system error 1231.
-
ActiveVisor installed on local host does not support management of ActiveImage Protector installed on a virtual machine in cloud. ActiveVisor has to be installed on the same VLAN as the virtual machine in managed cloud.
Upgrade
-
Please be aware of the following limitations when upgrading from Version 6.0.2.1507.
-
After upgrading, you are not allowed to launch the console from update dialog. Please launch the console from Start menu.
-
The templates and the product key for Version 2018, hypervisors other than Hyper-V/ESXi are not migrated.
-
Web access, if enabled, is disabled.
-
After upgrading, the configured settings and logs remain in install path of the earlier version. If the configured settings and logs are unwanted, please delete them.
When launching the console after logging in as a user of Administrators group of local computer, and selecting [Ready for update] to install update, debug dialog may be displayed in the midst of update process. In this case please close the dialog.
-
-
When upgrading from Version 7.0.x or earlier to Version 7.0.1 or later and the migrated templates are deployed to the client on which ActiveImage Protector agent Version 7.0.0 or later is configured, the parameters may not be correctly configured. You are recommended to create the templates again.
Initial Settings
- Please configure the settings for the domain administrator or a user in Domain Admins group.
Push Install
-
Push Install supports Setup and patch files for version 6.0.0.7292 or later agents only.
-
Please configure the firewall settings to allow [File and printer sharing] on the computer. If the firewall settings are configured for group policy, please select [Network] - [Network Connection] - [Windows Firewall] and enable [Allow inbound file and printer sharing exception].
-
The push-installed products can be uninstalled by using the following operating procedures.
-
Push uninstall from ActiveVisor
-
Run uninstaller in silent mode on local computer
Ex : Run “C:\Program Files\Actiphy\ActiveImage Protector\uninstaller.exe” /qn on command prompt.
-
-
When this product is installed in the environment where MSI installer created from Setup of ActiveImage Protector 2022 (6.0.0.7292) is used for installation, push-installation to a remote computer by using Setup of the same version is not supported. You can push install by using MSI installer created in installation process, or try again after uninstallation of ActiveImage Protector.
This case is applied to the environment where the product is push installed by using Setup of ActiveImage Protector 2022 (6.0.0.7292) from ActiveVisor.
-
When the connection from the computer on which this product runs to Actiphy Activation Server or Actiphy Authentication Service (AAS) cannot be established, activation may fail on the agent push-installed by using Virtual (Guest). Please make sure that the connection from this product to Actiphy Authentication Service or Actiphy Authentication Service (AAS) can be established. Then, please try activation on the agent push-installed by using Virtual (Guest) key
-
If you use Actiphy Authentication Service (AAS) connected from agent, please use the following operating procedures.
-
Right-click on the agent and select [Launch command line interface]. Then, run the following command in the command prompt window.
config AASIP <IP Address>
-
Right-click on the agent and select [Edit client setting] - [Backup and Standby], enter the following command in the displayed dialog and click [Submit]. Press Ctrl or Shift key and select multiple agent to collectively edit the agent settings.
AASIP <IP Address>
-
-
Upgrading from Version 2018 fails when using Setup wizard of Version 2022 (6.5.0.7616). Please uninstall Version 2018, then install Version 2022.
Deploy
-
Deployment to the agent on the computer fails, unless the icon to the left of list in [Client] - [Managed by this ActiveVisor] is displayed in green for the computer (Client Connected).
-
If ActiveImage Protector installed on the deploy target computer does not provide the option, the option is disabled.
-
If the destination is not accessible from the deploy target agent, the deploy task fails.
Backup
- If the disk information of the target client is not properly obtained, deploy task fails. If you encounter the problem, move the computer to [Unmanaged] and move it back to [Managed] again. Then please make sure that the disk information is properly obtained.
Site Configuration
-
Addition / deletion of an item in the following settings is immediately applied.
-
Storage Device
-
Hypervisor
-
-
Re: hypervisor settings, you are not allowed to edit the credentials information for the registered host if not the Microsoft Hyper-V host. If you need to make any changes, you have to delete the registration of the host and then re-register it.
-
Re: hypervisor settings, before registering Citrix Hypervisor, please make sure that libvirt is configured on the target host and the port 16509 is opened in the Windows Firewall settings on the target host. If you changed the port on the target host, we do not provide support.
-
Re: hypervisor settings, if you need to add Nutanix Acropolis, please specify CVM for the connection target and enter the credentials information for Prism.
-
When detecting / adding agent with a backup task configured with SFTP server as the destination storage that needs Private key for accessing, the destination information is not registered to [Storage Device]. If the destination information has to be registered, please try from ActiveVisor.
-
When changing the credential information for accessing SFTP / cloud registered for storage device, please delete the registered information and register the information again.
File Recovery
If you try to create a new task while executing a file recovery task, Mount Image may fail or the process time for the running task may be longer.
Remote Console
-
[Virtual Conversion] - [Conversion from image] does not support backup files located on network shared folder.
-
When the version of the built-in console for remote managemeent is higher than the version of the managed agent, the features and options which the agent does not support may be displayed. Since the unsupported features and options do not work properly, please refrain from using them.
Web Console
-
When using SSL certificate, please copy it to [SSL-Certs] folder in the installation folder.
-
The following features are disabled.
-
Delete a template.
-
Delete a task created on a client, Export task log.
-
Add a target host in the Monitoring tab.
-
-
When adding an item in [Storage Device], [Hypervisor] in [Site Configuration], the added item will not be shown in the list until refreshing the information on the Web browser.
Supplementary
- The following ports are used for communication.
-
Host (ActiveVisor)
-
135 (Windows Management Interface (WMI))
-
139 (File and printer sharing)
-
445 (File and printer sharing)
-
57236 (Web access)
-
57237 (Web access)
-
60236
-
-
-
To use the Power-on feature on a physical computer client, please confirm that Wake on LAN (WOL) works properly on the computer. The following are the examples of the check points and settings to configure when Wake on LAN (WOL) does not work properly. If Wake on LAN (WOL) does not work even after the settings are properly configured, please contact the computer maker.
-
The status of NIC driver Wake on LAN (WOL) may not work due to improper installation of the driver. Or, updating to the supported version may be required.
-
Windows 10 or later Fast Startup feature is enabled. Wake on LAN (WOL) may not work when Windows 10 or later Fast Startup feature is enabled. Ex: Go to [Control Panel] - [Power Options]. Click [Choose what the power buttons do] - [Change settings that are currently unavailable] and uncheck [Turn on fast startup].
- PCI Express in power save mode When power save mode option is enabled for PCI Express (Link State Power Management), Wake on LAN (WOL) may not work. Ex: Go to [Control Panel] - [Power Options] - [Change plan settings] - [Change advanced power settings] - [PCI Express] and set [Link State Power Management] to “Off”.