Announcements: Join the VIPRE Beta Program

Release Notes for VIPRE Endpoint Migrator - Dec 16, 2021

Written By Marissa Fegan (Super Administrator)

Updated at January 31st, 2023

Product release information for VIPRE Endpoint Migrator version 2.4 on December 16, 2021.

What's New

The latest version of VIPRE Endpoint Migrator is now aware of VIPRE Site Manager policies. 

Agent migration will now assign migrated agents to policies depending, first, on if there is a VIPRE Site Manager policy with the same name. If not, it will then check for a VIPRE Cloud policy with the same name. If one does not exist, the policy will be migrated to the Cloud site and the agent will be assigned to the newly created policy. 

Policy migration takes both Endpoint Cloud and VIPRE Site Manager policies into account when naming migrated policies as well as now supporting password-protected agent uninstall. Please note, if the policy selected for migration has Uninstall Protection enabled, a new password will be automatically generated.

System Requirements

Important steps to follow prior to installing or running VIPRE Endpoint Migrator. Following these steps will help ensure a successful migration.

VIPRE Endpoint Migrator Requirements

Complete the steps below before running the Migrator.

Supported Environments

This section lists the VIPRE environments that are compatible with the Migrator.

  • Migration from the following VIPRE Server products (both console and agent versions)
    • VIPRE Antivirus Business - version 9.6 or later
    • VIPRE Business Premium - version 9.6 or later
    • VIPRE Endpoint Security - Server Edition - version 9.6 or later
  • Migration to one of the following
    • VIPRE Endpoint Security - Cloud Edition
    • VIPRE Site Manager

Supported Agent OS

The VIPRE Endpoint Migrator works exclusively with Windows-based agents. To migrate agents on a Mac system, you will need to uninstall the old agent and then deploy the Mac agent from the VIPRE Endpoint Cloud console. 

Migrator Requirements

The Migrator must be installed on a Windows PC with

  1. Network access to
    • Each agent you wish to migrate
    • Your VIPRE Site Service (VSS)
    • The internet (for access to VIPRE Cloud)
  2. .NET Framework 4.6.1 or above

User Privileges

The user account under which the Migrator is run must have domain administrator privileges.

System and Environment Requirements

The steps within this section must be completed prior to running the Migrator.

Create a VIPRE Cloud Site

Prior to running the Migrator, you must have a VIPRE Cloud site created. If using Site Manager, at least one VIPRE Cloud site must be created within Site Manager.

If you have not set up your VIPRE Cloud site

  1. Refer to Related Articles to take our guided tour of VIPRE Cloud for step-by-step guidance to setting up your site
  2. Return to this article to complete the migration

Pending reboots

Review the current state of your agents in VSS. Ensure there are no pending reboots or uninstalls, or the Migrator will not be able to migrate that device.

To verify agent reboot or uninstall states

  1. Make a list of agents/devices that have pending reboots or uninstalls
  2. Perform one of the following
    • Reboot each device now
    • Add a step to your execution plan to perform a reboot prior to running the Migrator

Firewall configuration

Before using the Migrator, you must perform some firewall configuration changes within both the VIPRE Server firewall and your Windows Firewall to allow traffic to pass.

Turn off the VIPRE Server firewall

  1. Login to your VIPRE Server console as a domain administrator
  2. From the console, disable the Firewall

Enable Windows firewall rules

The "WMI in" and "File and Printer Sharing" rules must be enabled in the Windows Firewall to allow traffic.

  1. Perform one of the following in the Windows Firewall
    • Enable the rules for both “WMI in” and “File and Printer Sharing”
    • Add exceptions for ports 135, 139, and 445
  2. Ensure that both Network Discovery and File and Printer Sharing are enabled 

Other things to consider

Non-local roaming agents

A roaming agent that is not currently connected to the same network as your VSS cannot be migrated using VIPRE Endpoint Migrator.

In this scenario, manual migration is necessary. One solution is presented below.

To manually migrate a roaming agent

  1. From the VIPRE Server console, remove the roaming agent device
  2. Using VIPRE Cloud, email the VIPRE Cloud agent installer to an administrator or user of that device

What's next?

When using the Migrator to migrate, the next step in the process is to download and install the VIPRE migrator tool. Refer to Related Articles for details.

Known Issues and Workarounds

This section lists issues that are known at the time of release. In some cases, these are bugs that we are working to resolve with a subsequent release. Other items may be due to causes outside of our control, such as bugs with other vendors' software. In all cases, we have tried to provide a workaround for you to consider, should you experience an issue.

If you have questions about a specific issue, please provide the issue ID (if applicable) when contacting our Technical Support team.

At this time there are no known issues with this release.