Connection failed

The Migrator cannot reach VSS, the agents, or the VIPRE Cloud / Site Manager instance

An incorrectly configured firewall can prevent access:

1. Ensure that the WMI services is enabled across the network.

• Enable the rules for "WMI in" and “File and Printer Sharing” in the Windows Firewall to allow traffic
• Alternatively, exceptions can be added for ports 135, 139, and 445

   

2. Disable VIPRE Server Firewall. Important Configuration Considerations:

• Windows XP (SP3): Ensure "Simple File Sharing" is disabled
• Vista and later: Ensure both "Network Discovery" and "File & Printer Sharing" are enabled

Policy doesn't exist in VIPRE Cloud

Policies cannot be copied from VSS to VIPRE Cloud

Indicates the policy associated to the agent was not able to be migrated to the Cloud (if it wasn’t already on the VIPRE Cloud side).

May also happen if policy was deleted after it was selected to be migrated, and before the migration occurred.

Agent migration failed

If a policy cannot be copied from VSS to VIPRE Cloud, the migration will fail. Agents must be assigned to a policy to migrate to VIPRE Cloud.

Verify the policy was successfully migrated prior to the agent move.

The Migrator cannot download the VIPRE Cloud MSI package

If the Migrator cannot download the MSI from the internet, the migration will fail. The MSI is needed to install on each agent so that the agent may connect to VIPRE Cloud.

Verify the system you're running the Migrator on has not experienced a connectivity/network issue.

Test connectivity by logging into your VIPRE Cloud site to which you are migrating.

Retry the download of the MSI again.

The VIPRE Server agent cannot complete the MSI installation

If the agent receives the MSI package but cannot complete installation, the migration will fail for this agent.

If you have performed an agent uninstall on the device, and/or if a reboot is pending on the device, the migration will fail

Connect to the agent and investigate.

• Check for previous pending work (agent uninstall, reboot) not completed
• Complete the pending work on the agent and/or reboot it
• If the process failed during the MSI install:
  • The MSI installer was pushed to the agent machine but the agent machine failed to complete the install
  • Since the migrator is performing a push install, the agent machine should have an MSI log (if the process got that far) which might indicate why the install failed

Verification Failed

The WMI push install reports success, but the agent has not been found by VIPRE Cloud yet.

There may be a delay in the agent reporting to VIPRE Cloud.

If the agent does not eventually appear in VIPRE Cloud, review The VIPRE Server agent cannot complete the MSI installation (above) for items to check.