服務請求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:
- McAfee MVISION ePO
- On-premises McAfee ePolicy Orchestrator (McAfee ePO) — For more information, see the McAfee ePO 5.10 Installation Guide
- Hosted McAfee ePO on Amazon Web Services (AWS) — For more information, review How to Configure AWS-Hosted McAfee ePO with AWS Active Directory
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:
- Introduction to Reference Configurations
- McAfee support for MVISION Endpoint adoption with fresh installation of MVISION Endpoint
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 VirusScan Enterprise
- McAfee SiteAdvisor Enterprise
- McAfee Host Intrusion Prevention
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.
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:
- Introduction to Reference Configurations
- McAfee support for MVISION Endpoint adoption with upgrade from VirusScan Enterprise 8.8 Update 11 to MVISION Endpoint 18.08
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:
- MVISION Endpoint and Windows Group Policy Management
- How to verify that Real Protect is installed correctly and can communicate with McAfee cloud for detections
- MVISION Policy and Task approval feature with McAfee 5.10
- “Go back to the previous version of Windows 10” downgrade functionality is currently not supported with McAfee MVISION Endpoint
Supplemental Documentation
- McAfee MVISION Endpoint Known Issues
- MVISION Endpoint and Windows Group Policy Management
- How to verify that Real Protect is installed correctly and can communicate with McAfee cloud for detections
- MVISION policy and task approval feature with McAfee ePO 5.10
- “Go back to the previous version of Windows 10” downgrade functionality is currently not supported with McAfee MVISION Endpoint
- McAfee On-Premises Release Cycle
- McAfee MVISION ePO Product Guide
- Migration paths for MVISION ePO
- FAQ for McAfee ePO Cloud
- Data Exchange Layer client Proxy settings do not have any policy options for connection via a Proxy