MVISION Endpoint Support



Clean Installation

McAfee defines a clean installation as a deployment where there is no McAfee software pre-existing on the endpoint. See “Upgrade” if there is existing MVISION software. See “Migration” if there is existing legacy McAfee software or if McAfee Endpoint Security is installed.

Review the supported environments documentation to ensure the environment is compatible before deploying McAfee MVISION Endpoint:

You can manage McAfee MVISION Endpoint with any of the following:

Read the guides below for information about how to install McAfee MVISION Endpoint and for additional details regarding system requirements.

Note: Windows Firewall management is not enabled by default in McAfee MVISION Endpoint policies.

Note: If using McAfee MVISION ePO, sign up for and activate your MVISION ePO account.

Consider the following before installation:

  • The Windows Defender Antivirus client is installed as a core part of Windows 10. It is important to consider group policies that are configured for Windows Defender Antivirus on your endpoints and how they affect the McAfee MVISION Endpoint implementation.
  • Review the current configuration sources used by Windows Defender Antivirus to check for signature updates and consider the use in the McAfee MVISION Endpoint policy settings.
  • Policy and Task approval feature with McAfee ePO 5.10
  • McAfee MVISION Endpoint will abort installation (both manual and McAfee ePO deployed) if it detects McAfee Endpoint Security installed on the system.

Review reference configurations, which are deployment scenarios that have undergone extensive testing to ensure proper sequencing and improve ease of execution.

Each reference configuration document contains a product mix that is validated to work together for a specific type of customer profile. Review the following articles to learn more:

If you have an issue during installation, see the following documentation:

Upgrade

McAfee defines an upgrade as a deployment where a version of McAfee MVISION Endpoint already exists on the endpoint. See “Migration” if legacy McAfee software, such as McAfee VirusScan Enterprise or McAfee Endpoint Security, already exists on the endpoint.

Review the supported environments documentation to ensure the environment is compatible before deploying McAfee MVISION Endpoint:

Review the guides below for information about how to install McAfee MVISION Endpoint and for additional details regarding system requirements.

If you have an issue during installation, see the following documentation:

Migration

McAfee defines a migration as a deployment where legacy McAfee products, such as McAfee VirusScan Enterprise, McAfee Host Intrusion Prevention, or McAfee SiteAdvisor Enterprise, already exist on the endpoint where McAfee MVISION Endpoint will be deployed.

Review the supported environments documentation to ensure the environment is compatible before deploying McAfee MVISION Endpoint:

  • Supported platforms, environments, and operating systems
    • McAfee MVISION Endpoint can be deployed directly over existing installations of the following legacy McAfee products and will automatically uninstall them prior to its own installation.

  • McAfee VirusScan Enterprise
  • McAfee SiteAdvisor Enterprise
  • McAfee Host Intrusion Prevention

Note: McAfee MVISION Endpoint will abort installation, both manual and McAfee ePO deployed, if it detects McAfee Endpoint Security installed on the system. McAfee Endpoint Security must be uninstalled separately prior to installing McAfee MVISION Endpoint, if it is preferred.

Review reference configurations, which are deployment scenarios that have undergone extensive testing to ensure proper sequencing and improve ease of execution.

Each reference configuration document contains a product mix that is validated to work together for a specific type of customer profile. Review the articles below to learn more:

If you have an issue during migration, see the following documentation:

Configuration & Best Practices

To get acquainted with the software, review the documentation below:

Consider the following:

  • The Windows Defender Antivirus client is installed as a core part of Windows 10. It is important to consider group policies that are configured for Windows Defender Antivirus on your endpoints and how they affect the McAfee MVISION Endpoint implementation.
  • Review the current configuration sources used by Windows Defender Antivirus to check for signature updates and consider the use in the McAfee MVISION Endpoint policy settings.

Additional references:

Root Certificate Expiration

The McAfee product line uses TLS for secure communication. Two certificates validate McAfee TLS chains, including a primary expiring in 2038 and a secondary expiring on May 30, 2020. If either certificate, or both, are present in your environment, TLS will function correctly prior to May 30, 2020. After May 30, 2020, only the primary certificate will be valid. Out of an abundance of caution McAfee is informing customers of this impending event.

Generally, certificates are auto-updated through operation systems and customers will not be impacted. However, in environments where automatic management of root certificates is disabled and the primary certificate has not been manually deployed, customers will potentially be impacted. KB92937 provides information on how to verify and install the primary certificate.

Failure to have a valid certificate will cause product issues including reduced detection efficacy.

The primary certificate that needs to be validated is in a customer's environment as below:

Subject : CN=USERTrust RSA Certification Authority, O=The USERTRUST Network, L=Jersey City, S=New Jersey, C=US
Thumbprint : 2B8F1B57330DBBA2D07A6C51F70EE90DDAB9AD8E
Expiration : 2038-01-18

Subscribe to KB92937 to receive updates.

Data Sheet

Download

Free Demo

Request

More Information

Contact Us