Knowledge Center

Legacy products cannot coexist with Endpoint Security modules
Technical Articles ID:   KB86504
Last Modified:  8/10/2018


McAfee Endpoint Security (ENS) Firewall 10.x
McAfee ENS Threat Prevention 10.x
McAfee ENS Web Control 10.x
McAfee SiteAdvisor (SAE) 3.5
McAfee VirusScan Enterprise (VSE) 8.8


ENS 10.x cannot coexist with the legacy products SAE and VSE, even if the ENS replacement module for the product is not installed.

Endpoint Security 10.x includes the replacement technologies for these legacy products:
  • VSE 8.8 is replaced by ENS Threat Prevention 10.x
  • SAE 3.5 is replaced by ENS Web Control 10.x
The following scenarios provide examples of how ENS 10.x products maps and replaces your current legacy products.

Scenario 1
If you have VSE and SAE and only want to install the ENS Web Control functionality, both VSE and SAE are removed, and only the ENS Web Control module is installed.

Scenario 2
If you only have VSE and want to install ENS Web Control, VSE is removed, and the ENS Web Control module is installed.
When you upgrade to ENS 10.x, all legacy products are upgraded to the new platform, even if you do not install the replacement technology itself.

The base platform of the new technologies (called Endpoint Security Platform), ensures the removal of any incompatible code.

The policies associated with any legacy product that was removed are preserved during the ENS upgrade, if you elected to preserve legacy product settings. This occurs even if you did not install the replacement technology.
Scenario 3
If you have ENS Threat Prevention installed and then try to install SAE, the McAfee Agent tries to run the SAE installation. You might see that the installation generates errors. SAE will not be functional after installation. You might be unable to remove SAE afterwards. Use the Endpoint Product Removal tool if SAE does not uninstall.

Rate this document

Glossary of Technical Terms

 Highlight Glossary Terms

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