Migrate from McAfee Active Response If you are using McAfee® Active Response 2.3 or later, you can migrate to MVISION EDR. Before you begin Make sure that you have: McAfee ePO 5.9.1 or later installed. Active Response 2.3 or later installed and configured. Note: For information about supported platforms, environments, and operating systems for McAfee Active Response, see KB84473. For information about installing the McAfee Active Response client, see KB89991. When creating the MVISION EDR account, use the same email address used to connect to MVISION Cloud Bridge for Active Response (Menu → Server Settings → MVISION CloudBridge Settings). Task Log on to MVISION EDR as administrator. Select Menu → Investigating → Configuration. On the Configuration panel, select Use McAfee ePO on-premises for management, then click Save. In the Choose telemetry and region settings section, select I choose to share telemetry data (defined below) with McAfee, then click Save. Check in the MVISION EDR extension: Log on to McAfee ePO as administrator. On McAfee ePO, select Menu → Software → Software Manager / Software Catalog, search for MVISION EDR. Select MVISION Endpoint Detection and Response package and click Check In. After checking in the extension, all dependent packages and extensions are installed: DXLBrokerMgmt DXL ePO client DXL Client Mgmt MVISION EDR Client Package MVISION EDR Endpoint Snapshot Tool MVISION EDR Client Extension MVISION Cloud Bridge Add your MVISION EDR account credentials to MVISION Cloud Bridge: On McAfee ePO, select Menu → Server Settings → MVISION Cloud Bridge. Click Edit. On the Edit MVISION Cloud Bridge page, enter the email address and password created for MVISION EDR and click Save. The message The server is actively linked. appears. Upgrade DXL Broker to 5.0 or later: Select Menu → Software → Software Manager / Software Catalog and search for Data Exchange Layer Broker 5.0. Select Data Exchange Layer Broker package and click Check in. Go to Menu → System Tree and select the required device on which DXL is to be upgraded. On the System Tree page, select Actions → Agent → Run Client Task Now. On the Run Client Task page, select Product as McAfee® Agent, Task as Product Deployment , and click Create New Task. In the Target Platform section, select the operating system of the selected device. In the Products and components section, select Data Exchange Layer. Click Run Task Now. When the task is complete, the Running Client Task Status page shows the status as green (Completed). Select Menu → Software → Software Manager / Software Catalog, search for Data Exchange Layer and click Check in. Deploy MVISION EDR client: Select Menu → Configuration → Software → Product Deployment and then click New Deployment. Enter a name and description for the deployment. Select McAfee MVISION EDR Client as the software package. Click Select Individual Systems. On the System Selection page, from System Tree, select the devices on which you want to deploy the MVISION EDR client and click OK. Save the new deployment. After you migrate the Active Response to MVISION EDR, the trace data and threats from Active Response is migrated to MVISION EDR. The existing trace data and threats remain in Active Response after the migration. All DXL brokers must be upgraded to 5.0 or later to allow the trace data to migrate from Active Response to MVISION EDR. Log on to MVISION EDR as administrator. Select Menu → Investigating → Configuration → Install components → Agent Deployment and click Save. Select Menu → Investigating → Configuration → Configure data sources, select McAfee ePO and verify whether the connection status is green. All basic components are now installed and MVISION EDR is connected to McAfee ePO. Results Devices using Active Response are now successfully migrated to MVISION EDR. The potential threats start appearing on the Monitoring dashboard in MVISION EDR. There are two linking or authentication extensions on McAfee ePO: McAfee® ePO™ Cloud Bridge -> MAR 2.x linking/authentication MVISION Cloud Bridge -> MVISION-EDR linking/authentication Traces or events from Active Response 2.x clients and Mvision-edr clients will go to MVISION-EDR Cloud. (Threats/Alerts appears in Monitoring Dashboard). Traces/Events from Active Response 2.x clients no longer go to Active Response Cloud, so MAR Workspace will not be updated anymore, it should be used only to view previous activity, no further actions should be triggered from MAR 2.x workspace. There will be two checks box to control where the traces will go under Server Settings -> DXL Topology. Unchecked -> Provides trace data to the cloud for MAR Workspace Checked -> Forward MVISION EDR DXL events to cloud Real-time Search could be executed from Real-time Search Dashboard on MVISION-EDR UI and from Active Response page on MAR 2.x. Both searches will reach all the Active Response 2.x Clients and Mvision-edr Clients and the results will go to the initiator only. Search errors handling is not supported in this MVISION-EDR and MAR 2.x mixed environment. MVISION-EDR does not support Saved Searches, but Saved Searches created on MAR 2.x remain available and usable on Active Response page and/or Catalog on MAR 2.x. MVISION-EDR supports Remediation and Containment actions like Stop And Remove or Quarantine. MVISION-EDR does not support Triggers, but existing Triggers on MAR 2.x remain available and usable on MAR 2.x. When the migration is complete, new threats are shown in the Monitoring dashboard and the old Active Response threats are still available in Workspace in McAfee ePO. To migrate to MVISION EDR, you can remove all Active Response extensions except the mar-client extension. This extension is required to monitor the devices that are not migrated to MVISION EDR. For information about disabling the DXL broker and Active Response server, see KB91043. Remove the McAfee Active Response extensions After you migrate Active Response to MVISION EDR, you can remove Active Response extensions from McAfee ePO. Remove the McAfee Active Response software packages Remove the Active Response software packages from the Master Repository.