MVISION Endpoint does not work after migrating from existing products on Windows Server 2016/2019

Technical Articles ID: KB92637
Last Modified: 4/22/2020

Environment

McAfee Endpoint Security (ENS) 10.x
McAfee MVISION Endpoint 20xx, 19xx
McAfee VirusScan Enterprise (VSE) 8.x
Microsoft Windows Server 2019, 2016

Problem

MVISION Endpoint might not work properly when migrating from the existing product ENS or VSE on Windows Server 2016/2019. This problem is not always reproducible, but when the problem occurs, you might see the following symptoms:

The message Not installed displays in Windows Defender in the Server Manager.
The EICAR file is not detected.

This problem occurs when you use the following migration procedure:

Uninstall the existing product (ENS or VSE) from the Control Panel.
Reboot the operating system.
Install MVISION Endpoint from ePolicy Orchestrator (ePO) with a deployment task.
Verify that MVISION Endpoint has been installed.
Reboot the operating system.

Cause

ENS and VSE leave Windows Defender in an inconsistent state after they are uninstalled on Windows Server 2016/2019. MVISION Endpoint currently can't recover Windows Defender under these circumstances.

Solution

It is hard to provide a hotfix or update for this issue as a regular bug fix, because it might require the redesign and implementation of some new features for MVISION Endpoint. A Feature Modification Request (FMR) has been submitted for a future release of MVISION Endpoint to implement some kind of checks to fix this issue.

To receive email notification when this article is updated, click Subscribe on the right side of the page. You must be logged on to subscribe.

Workaround

Perform the following steps. Make sure to complete each step before going to the next step. Also, make sure that Windows Defender is installed and running in between each step. This procedure requires a reboot of the endpoint after removing ENS or VSE. This procedure might require a second reboot before you install MVISION Endpoint to make sure that Windows Defender is up and running correctly after a reboot.

Uninstall ENS or VSE. Then, reboot the endpoint to make sure that ENS or VSE is completely removed.
Verify that Windows Defender is installed and running. If not, install and enable Windows Defender.
Reboot the endpoint and verify that Windows Defender is up and running after the reboot. If not, repair Windows Defender and repeat this step.
Install MVISION Endpoint only after Windows Defender is up and running.

Affected Products

Known Issue/Product Defect
MVISION Endpoint - All Versions
Upgrade/Migrate

Languages:

This article is available in the following languages:

English United States
Spanish Spain
French
Italian
Portuguese Brasileiro

Glossary of Technical Terms

Highlight Glossary Terms

Please take a moment to browse our Glossary of Technical Terms.

Knowledge Center

MVISION Endpoint does not work after migrating from existing products on Windows Server 2016/2019

Environment

Problem

Cause

Solution

Workaround

Affected Products

Languages:

Glossary of Technical Terms

Title

Title

Knowledge Center

MVISION Endpoint does not work after migrating from existing products on Windows Server 2016/2019

Environment

Problem

Cause

Solution

Workaround

Affected Products

Languages:

Glossary of Technical Terms

Choose your region

Title

Title