Please carefully read this document

November 11, 2021

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.

Basic Points

• This version supports management and operation of ActiveImage Protector 2018 agents version 5.1.11.6500 or later.

  • ActiveImage Protector Version 5.1.11.6454 agents may be installed on managed clients however, this version of ActiveVisor only partly supports operation of Version 5.1.11.6454 agents. It is recommended to update ActiveImage Protector agents to Version 5.1.11.6500.

  • This version does not support management and operation of ActiveImage Protector Linux Edition.

• 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 auto-update applies the patch program and ActiveImage Protector agent’s product version is 5.1.11.6500 or later, the client computer may be removed from the managed clients list. Select the computer in the list and click [Move to Managed] from the right-click menu to move it back to the managed clients list 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 5.1.11.6500 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].

• When the [ActiveImage Mount] component is not installed, then the upgrade installation with [Do not change components] option enabled completes in the state that the [ActiveImage Mount] component is installed.

• When installing with Virtual License’s product key, installation process starts even when clicking [Cancel] button in the dialog.

Agent Setting

• You are not allowed to operate for PreBoot settings.

• After changing Lock Feature, the re-displayed dialog may not properly display the previous information.

• Lock local users from uninstallation of a software is not allowed on the computers to which ActiveImage Protector was deployed by using Group Policy’s [Software Installation] feature.

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.

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.

Web Console

• When using SSL certificate, please copy it to [SSL-Certs] folder in the installation folder.
  • This folder will be deleted when [SSL enabled port] is disabled.

• 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)

    • 60236

• Client (ActiveImage Protector)

    * 135 (Windows Management Interface (WMI))
  
    * 139 (File and printer sharing)
  
    * 445 (File and printer sharing)
      
    * 48236
  
    * 48238
  
    * 48239
  

• 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 Fast Startup feature is enabled. Wake on LAN (WOL) may not work when Windows 10 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”.