Introduction to Reference Configurations
Reference configurations are deployment scenarios that we recommend, which have undergone extensive testing to ensure proper sequencing. The scenarios reduce the need for restarts and improve ease of execution. Use the reference configuration report finder to find the scenario that you need. The search tool allows you to filter reference configuration documents by product, installation type (fresh installation or upgrade), and Windows version.
For more details about reference configurations and answers to frequently asked questions, see KB88274 - Introduction to Reference Configurations.
This reference configuration document is designed for customers who already have our products deployed. This document was created by building a baseline system matching the most commonly deployed versions of our products at that point in time, and then upgrading to recently released product versions. The intent is to provide a roadmap for upgrading to recent releases.
NOTE: Not all products are included in this document. It represents products that are commonly used. If your product mix is a subset of this configuration, you can skip over any product deployment that does not apply to your needs. The recommended products in this reference configuration don't necessarily represent the latest released versions of many products.
Before You Begin
Before beginning the deployment process, there are several preparatory actions that help lead to a successful deployment process.
Review the latest release notes and known issues
Although we officially recommend this reference configuration, we might discover issues that can impact the success of your deployment. See the "Recommended Product Configuration" table for links to known issues for each product version.
Plan for restarts
Some operating system driver modules installed during product upgrades are properly loaded into memory only at runtime. As a result, they need a restart to facilitate the loading of the new drivers. Limitations of the operating system require that only one version of these drivers be loaded at a time. So, depending on which products you're installing, you might need to restart multiple times. This deployment path has been optimized to minimize the number of restarts needed when you update all products listed in the sequence.
If you're planning to update only a subset of products, plan to restart after the updates are complete.
Adapt this guideline to your specific upgrade plan
Your current deployment baseline might differ from the versions mentioned in the "Recommended Product Configuration" table. If some of your product versions are more recent than this provided baseline, you can still follow the recommended sequence. If you don't use some of the products in the list, you can skip that product.
Configuration de produit recommandée
Le tableau ci-dessous répertorie les produits couramment déployés, déterminés en fonction des échantillonnages de télémétrie provenant d’un ensemble important de clients. Nous vous recommandons de déployer ces produits pour profiter de la dernière offre de produits pour MVISION Endpoint 2011. Cette configuration est testée de manière intensive pour la compatibilité entre les produits à l’aide de la liste des systèmes d’exploitation ci-dessous :
Systèmes d’exploitation :
- Mise à niveau1 vers Windows 10 version 20H2 (mise à jour 2020 d’octobre) à partir de l’un des systèmes d’exploitation suivants :
- Windows 10 version 1809 (October 2018 Update)
- Windows 10 version 1903 (May 2019 Update)
- Windows 10 version 1909 (mise à jour de novembre 2019)
- Windows 10 version 20H2 (mise à jour d'octobre 2020)
- Mettez à niveau1 vers Windows Server 2019 à partir du système d’exploitation suivant :
1 Pour plus d’informations sur la mise à niveau du système d’exploitation, reportez-vous aux articles suivants :
Produits |
Versions Partagés |
Versions recommandées |
Problèmes connus |
ePolicy Orchestrator (ePO) |
5.10.0.2428 Appliquez la mise à jour 9 après la
configuration du serveur |
|
KB90382 |
Espace de travail Protection |
Extension de service : 1.0.0.1742
Extension de l’interface utilisateur : 1.0.0.2070 |
Extension de service : 1.0.0.1765
|
|
Service Broker Data Exchange Layer |
6.0.0.203 |
|
KB92077 |
MVISION EDR Cloud |
|
Extension EDR : 3.3.0.1
Cloud Bridge : 2.1.0.100
Configurer pour fonctionner avec
Client MVISION EDR |
|
Web SaaS |
|
Configurer pour fonctionner avec
McAfee Client Proxy (MCP) |
|
McAfee Agent |
5.6.2.209 |
5.7.0.194 |
KB93773 |
MVISION Endpoint |
Offre groupée d’extensions ePO : 20.9.0.44
Package d’installation : 20.9.0.215 |
Offre groupée d’extensions ePO : 20.11.0.58
Package d’installation : 20.11.0.156 |
KB90738 |
MCP |
3.1.0.215 |
3.2.0.189 |
KB83131 |
Client MVISION EDR |
|
3.3.0.625 |
KB91275 |
Data Loss Prevention Endpoint |
Extension : 11.4.0.17
Il 11.4.0.452 |
Extension : 11.6.0.27
Il 11.6.0.762 |
KB89301 |
Drive Encryption |
Extension : 7.2.8.4
Il 7.2.8.4 |
Extension : 7.2.10.56
Il 7.2.10.56 |
KB84502 |
File and Removable Media Protection2 |
5.1.0.209 |
5.3.0.143 |
KB85807 |
Application et Change Control |
Extension : 8.3.0.225
Il 8.3.0.303 |
Extension : 8.3.2.103
Il 8.3.2.133 |
KB87838
KB87839 |
2 FRP n’est pas pris en charge sur les systèmes d’exploitation serveur.
Processus d’installation :
Cette section décrit l’ordre de fonctionnement recommandé.
REMARQUES :
- Archivez toutes les extensions dans ePO avant de mettre à niveau les produits.
- Les cases vertes indiquent les systèmes serveur.
- Les cases bleu foncé indiquent quand une mise à niveau du produit est recommandée.
- Les cases bleu clair indiquent un nouveau déploiement de produit.
- Les cases indiquées en rouge indiquent qu’un redémarrage du système est nécessaire pour activer ce produit.