VIPRE Endpoint Migrator Requirements

Written By Marissa Fegan (Super Administrator)

Updated at August 10th, 2023

Table of Contents

Supported Environments Important Migrator Requirements User Privileges Environment Prerequisites Other things to consider What's next?

System requirements and other items to consider before migrating to one of our VIPRE Cloud products

Supported Environments

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

Migration from the following VIPRE Server products	Migration to one of the following VIPRE Cloud products
VIPRE Endpoint Security Server - version 12.3 or later	VIPRE Endpoint Security Cloud VIPRE Site Manager VIPRE Endpoint Detection & Response (EDR)

Migration from the following VIPRE Server products

Migration to one of the following VIPRE Cloud products

VIPRE Endpoint Security Server - version 12.3 or later

VIPRE Endpoint Security Cloud
VIPRE Site Manager
VIPRE Endpoint Detection & Response (EDR)

Important

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

Migrator Requirements

The Migrator must be installed on a Windows PC with:

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

User Privileges

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

Environment Prerequisites

The steps within this section must be completed before 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, navigate to one of the following articles (clicking the links will open up a new tab):
- Return to this article to complete the migration
Review the current state of your agents in VSS to ensure there are no pending reboots or uninstalls as the Migrator will not be able to migrate that device
Make a list of agents/devices that have pending reboots or uninstalls
Perform one of the following:
- Reboot each device now, or
- Add a step to your execution plan to perform a reboot prior to running the Migrator
Before using the VIPRE Migrator, you must perform some firewall configuration changes within both the VIPRE Server firewall and your Windows Firewall to allow traffic to pass through
1. Turn off the VIPRE Server firewall
  1. Login to your VIPRE Server console as a domain administrator
  2. From the console, disable the Firewall
2. Enable Windows firewall rules
  1. The "WMI in" and "File and Printer Sharing" rules must be enabled in the Windows Firewall to allow traffic
  2. 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
Ensure that both Network Discovery and File and Printer Sharing are enabled

Other things to consider

A non-local 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

From the VIPRE Server console, remove the roaming agent device
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.

VIPRE Security Knowledge