Migrate common objects to Trend Cloud One - Endpoint & Workload Security
Migrate to Trend Cloud One - Endpoint & Workload Security is a multi-step process.
You can use the migration tool to migrate common objects (with the exception of rules and malware configurations) to Trend Cloud One - Endpoint & Workload Security.
Prerequisites
- Check that you are running Deep Security Manager 20.0.585 (20 LTS Update 2022-01-17) or later.
- If you have not done so already, complete the earlier steps in Migrate to Trend Cloud One - Endpoint & Workload Security, including creating a Trend Cloud One account, creating an API key, and preparing a link to Workload Security.
Migrate common objects using the migration tool
The Migrate to Trend Vision One Endpoint Security tool (formerly called Migrate to Workload Security tool) enables migration for both Trend Vision One Endpoint Security - Server & Workload Protection and for Trend Cloud One - Endpoint & Workload Security. Note that in addition the tool itself, the related role configurations have been renamed.
- In the Deep Security Manager console, select Support > Migrate to Trend Vision One Endpoint Security.
- The Migrate to Trend Vision One Endpoint Security page appears with the Configurations tab selected. Click Migrate Common Objects to expand that section.
If a Link to Trend Vision One Endpoint Security Account page appears first, see Prepare a link to Workload Security for information on how to configure the link.
- In the Common Objects list, select the type of object to migrate.
The migrated object overwrites the existing object if the common object being migrated meets any of the following conditions:
- The common object has the same name as an existing common object in Workload Security.
- The common object is a default object created by Trend Micro, regardless of whether or not it has the same name as an existing common object in Workload Security.
- Select the common objects that you want to migrate, and then click Migrate Selected.
- When the migration begins, click Refresh to check the migration status. Possible statuses are:
- Requested: Common object migration to Workload Security has been requested but the migration has not started yet.
- Migrating: Common objects are being migrated to Workload Security. If the status stuck in Migrating, it means the Deep Security Manager cannot get the response from Workload Security. Check the network configuration.
- Migrated: Common objects have been migrated successfully to Workload Security.
- Failed: Common objects have failed to migrate to Workload Security for some reason. Check the error code:
- Error code 300: Selected common objects do not exist.
- Error codes greater than or equal to 900: Deep Security Manager has a problem communicating with Workload Security. Please make sure the Workload Security Link is correctly configured, or check server0.log for details.
Next, migrate your cloud accounts and agents.