--- title: "Removable Media (RM) device events migration" slug: "removable-media-rm-device-events-migration" tags: ["Migration", "MV-FRP"] updated: 2026-09-12T21:11:45Z published: 2026-09-12T21:11:45Z canonical: "docs.trellix.com/removable-media-rm-device-events-migration" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.trellix.com/llms.txt > Use this file to discover all available pages before exploring further. # Removable Media (RM) device events migration This Server Task migrates Removable Media device events for clients already migrated using the migration wizard, and includes the last 100 days of device events for the system. A removable media device can be used across multiple endpoints. So, not all associated events migrate until all relevant endpoints are migrated. > [!NOTE] > Note > > Events other than Removable Media device events are not migrated. If you're planning to decommission ePO - On-prem, make sure to create a backup. > [!WARNING] > Important > > If you delete already migrated systems, their events do not migrate. After migration, access device events using the following queries in ePO - SaaS: - Removable Media: Device Events - Removable Media: Activations - Removable Media: Protection Status - Removable Media: Recent Usage > [!NOTE] > Note > > Information displayed for the migrated events in the Queries and Reports will be from ePO - On-prem. ### Run the device event migration Server Task manually **Task** 1. On the ePO - On-prem console, select **Menu** → **Automation** → **Server Tasks**. 2. Select FRP: **Migrate All Removable Media Device Events to ePO SaaS** and click Run. When the tasks are complete, the results can be viewed in the Server Task Log and Audit Log. ### Schedule a device event migration Server Task We recommend scheduling this task to run regularly. This ensures device events are migrated as Trellix FRP endpoints are migrated. **Task** 1. On the Server Tasks page, click Edit in **FRP: Migrate All Removable Media Device Events to ePO SaaS**. 2. On the Description tab, enable the **Schedule Status**, then click Next. 3. On the Actions tab, update the settings or click Next to continue. For more information, see [Prerequisites](/data-and-email/docs/prerequisites-2). 4. On the Schedule tab, configure the Start date and End date, then click Next. By default, it runs every 12 hours. We recommend this interval because it uses system resources to preprocess RM recovery events for migration. 5. On the Summary tab, review the configuration, then click Save. For information on troubleshooting, see [Troubleshooting migration Server Task messages](/data-and-email/docs/troubleshooting-migration-server-task-messages).