[KB7692] Migrate your EVS environment to ESET PROTECT

Issue

ESET business product in Limited Support status

This article applies to an ESET product version that is currently in Limited Support status and is scheduled to reach End of Life status soon.

For a complete list of supported products and support level definitions, review the ESET End of Life Policy for business products.

Upgrade ESET business products.

Details


Click to expand

The ESET Virtualization Security (EVS) is currently in the Limited Support status and no new version of the product is expected. The support of EVS ended with ESET PROTECT 8.1.

We recommend that you migrate your environment to endpoint management with the latest version of ESET PROTECT. To do this, install ESET PROTECT in your virtual environment and deploy ESET Management Agent with endpoint security products on the virtual machines.

Managing your virtual machines with ESET Endpoint Security enables you a higher level of security, with features such as HIPS, Brute-Force Attack Protection, firewall, device control, web control, email and antispam protection.


Solution

  1. Prerequisites
  2. Deploy ESET Management Agent and endpoint security products
  3. Set up the rules for virtual machines identification
  4. Unassign virtual machines from EVS security policies
  5. Remove EVS service policies from NSX manager
  6. De-register EVS Virtual Agent from the NSX manager
  7. Remove EVS service virtual machines
Test the migration on a single computer first

Before you perform these steps on large groups of machines in your environment, we recommend you try to migrate a single virtual machine first.


I. Prerequisites

  • You have an ESET PROTECT running on a server or as a Virtual Appliance in your virtual environment, with all your licenses imported.

  • Make sure you have enabled communication on port 2222 and other required ports and addresses.


II. Deploy ESET Management Agent and endpoint security products

  1. Using ESET PROTECT, deploy the ESET Management Agent and then deploy ESET endpoint products on your virtual machines.

  2. Your virtual machines are now protected and can be managed in ESET PROTECT.


III. Set up the rules for virtual machines identification

  1. To manage virtual machines in groups, create Dynamic Group templates or create Static Groups and then add the virtual machines to the Static Groups.

  2. To configure a VDI environment in ESET PROTECT, configure ESET PROTECT to match all clones to a master computer. For more information about managing a VDI environment in ESET PROTECT, read our Online Help topic.


IV. Unassign virtual machines from EVS security policies

  1. Open your virtualization client and log in.

  2. Click MenuNetworking and Security.

    Figure 1-1
  3. Click Service Composer → Security Policies, select your EVS Security policy and click Apply.

    Figure 1-2
  4. Select the check boxes next to all the groups and click the left arrow. This will unassign your virtual machines from the EVS security policy.

    Figure 1-3

V. Remove EVS security policies from NSX manager

  1. In your virtualization client, click MenuNetworking and Security.

    Figure 2-1
  2. Click Service ComposerSecurity Policies, select your EVS Security policy and click Delete.

    Figure 2-2
  3. Click Delete.

    Figure 2-3

VI. De-register EVS Virtual Agent from the NSX manager

  1. Open your Virtual Agent Host appliance.

  2. Press Enter, type your password, and press Enter.

    Figure 3-1
  3. With the arrow keys on your keyboard, navigate to Register to VMware NSX Manager and press Enter.

    Figure 3-2
  4. Type u and press Enter.

    Figure 3-3
  5. Wait for the de-registration to finish. Type q and press Enter.

    Figure 3-4

VII. Remove EVS service virtual machines

  1. In your virtualization client, click MenuNetworking and Security.

    Figure 4-1
  2. Click Installation and UpgradeService Deployment, select ESET Virtualization Security and click Delete.

    Figure 4-2
  3. Click Delete.

    Figure 4-3
  4. Verify ESET Virtualization Security has an Installation Status of Scheduled for uninstall and wait for the service to finish uninstalling.

    Figure 4-4
  5. Delete the Virtual Agent Host appliance from your disk.