This section provides guidance that focuses on the three, most common migration paths.
Path 1 assumes that the currently installed legacy products on the endpoint already meet the requirements for migration, based on supported upgrade paths. Start migration using this path
Path 2 assumes that the version of the existing legacy products do not meet the necessary requirements, and as such the path of least effort, combined with the highest chance of success, is to uninstall the existing products and replace them with a clean installation of Endpoint. Start migration using this path
Path 3 is designed for those environments that wish to use 3rd-party deployment software, such as Microsoft System Center Configuration Manager (SCCM) or IBM BigFix. Start migration using this path
McAfee highly recommends performing this migration on test systems, prior to attempting within a production environment. During the migration, if there are any technical issues experienced, please do not move forward with any additional steps, and contact support using the service portal.
Common Migration Path 1: Using ePO and Endpoint Upgrade Assistant.
- ePolicy Orchestrator must be on version 5.9.x or higher, in order to migrate over to Endpoint Security 10.7. If your ePO server is older than the above version, please upgrade it first using the following installation guide.
- Check in the Endpoint Security software and extensions now. If you chose to use EMA to migrate existing settings, please use it now to migrate your policies before continuing. If you chose not to retain existing settings, please continue to step 5.
- Once ePO is successfully upgraded, please check in the Endpoint Upgrade Assistant extensions using the latest available version. Endpoint Upgrade Assistant allows you to perform a quick analysis of the systems already managed by ePO, to verify that they meet the requirements for migration to ENS. Once EUA is checked in, please access the following guide and start with the "Workflow for analyzing and resolving issues" section to complete analysis of the environment.
NOTE: If a small portion of the existing systems do not meet the requirement for migration, please consider focusing on the larger portion of the environment and actioning the remaining systems at a later time. Also, for any systems that are currently using McAfee's VirusScan Enterprise for Storage software, which requires use of VirusScan Enterprise, please exclude these from the migration steps for now.
- If you would like to retain existing product settings that can be migrated over to Endpoint Security, please check in the Endpoint Migration Assistant extensions now. If you do not wish to retain existing policy configuration, please proceed to step 5. Familiarize yourself with how the Endpoint Migration Assistant can automatically migrate certain policy configurations over to ENS, by watching this video. Please note that this is a comprehensive video, with a duration of 1 hour. You can use the EMA guide instead.
- Prepare the software deployment using the Endpoint Upgrade Assistant guide. Once the software deployment is complete, please use the "Verify the Deployment" section of this guide to report on successfully migrated systems.
NOTE: For any remaining systems for which migration was not successful, or that could not be migrated, please contact support using the service portal for further assistance.
Common Migration Path 2: Uninstall, Reboot, and Install Clean with Endpoint Security.
NOTE: Due to various complexities involving older legacy software versions such as VirusScan Enterprise releases prior to 8.8, there is no directly supported migration path to Endpoint Security. Particularities within each environment may require a customized migration path provided by McAfee. If you would like professional services to design a customized migration path for you, please contact your sales representative. As an additional option, this migration path discusses steps to remove legacy software using standard product uninstall tasks and prepares your ePO server to deploy Endpoint Security 10.7.
- Use ePO to create a product deployment task for the existing legacy software. If the systems currently have multiple installed McAfee products, such as VirusScan Enterprise, Host Intrusion Prevention, and SiteAdvisor Enterprise, McAfee recommends separating these uninstall tasks as opposed to a single, combined uninstall task for all products. Within this task, select the option to "uninstall", as opposed to "install."
- Within the uninstall task(s), select the desired schedule for the task. Please note that a task scheduled to "run immediately," is only expected to execute one time. If the uninstall task fails, it will not run again when selecting this scheduling option.
- Select the systems to perform the uninstall task and use ePO to send a McAfee Agent wake-up call. It is important here to allow enough time for successful execution and removal of the existing products. McAfee recommends that you restart systems at his point.
- Once removal is complete, you can send an additional McAfe Agent wake-up call so that the existing McAfee Agent reports back the current system properties, thus allowing ePO's System Tree view to confirm that products have been removed successfully.
- At this step, if the currently in-use ePO version does not meet the requirements to migrate to Endpoint Security (version 5.9.x or higher), please upgrade ePO now. If your ePO server version is already at 5.9.x or higher, please continue to step 6.
- Once ePO is successfully updated, you should consider taking an action here to also update the existing McAfee Agent to the latest available version. If the existing McAfee Agent version is already on a supported version, please continue to step 7.
- Download and check in the Endpoint Security extensions and software packages and start your ENS deployment.
- Once the software deployment is complete, to verify that Endpoint Security installed on your endpoints please check your results.