Migrating Between Regions
To support data protection laws and compliance standards enforced in your country, Action1 enables customers to choose where to store the endpoints and associated data. Currently, Action1 data centers are located in the following regions:
- North America
To ensure data integrity and compliance, consider moving your account and endpoints to a relevant region. This article explains how to migrate your account and endpoints manually, and provides step-by-step instructions. Automated migration will be available later.
Note: Groups, user accounts, policies, custom applications, scripts, data sources, and reports cannot be transferred and should be moved manually.
Step 1: Create a New Action1 Account
Start by registering a new Action1 account with the same email address, make sure to specify a different region, e.g., Europe.
- Free subscription: complete verification of a new account
- Paid subscription: contact support to transfer your license to a new region. As soon as the license is transferred to the new account, the subscription of the initial account will be expired in a month.
Step 2: Prepare Endpoints for Migration
Before you start migrating endpoints, complete the following tasks in your initial account. For each organization:
- Sign in to the initial account.
- Make sure endpoints are online.
- Disable Action1 Deployer. Follow to the endpoint where Action1 Deployer is installed, open Services snap-in, stop and disable the appropriate service.
- Navigate to Configuration > Agent Deployment and ensure Deployer doesn’t manage your endpoints.
- Disable all policies.
- Make sure there are no policies running against the endpoints.
Step 3: Create New Organizations
In your new account:
- Re-create the organizations you had in your initial account.
- For each organization, download the Action1 agent.
Step 4: Create the Agent Migration Package
Note: Organizations can be migrated one by one. The steps for migrating for a single organization are described below. Repeat the following steps for all organizations.
For an organization, create the zip archive:
- Download migration_v1.20.zip
- Add agent MSI from a respective new organization to zip file.
The zip file should include the following files:
Step 5: Create Apps for Migration
In your initial account, create software package for the migration_v1.20.zip file. This package will update endpoints from a respective initial organization and move them to organization in your new account.
- Navigate to Software Repository and select + Add to Repository.
- Provide a name ‘Agent_Migration’, vendor ‘Action1’ and specify description.
- Add a new version.
- On the General tab:
- Version number is set to 1.20
- App Name Match is set to ^(Action1AgentMigration)$
- On the Installation tab:
- Select Windows 32 bit download and upload the .zip file with the Action1 agent
- Silent install switches is set to launcher.ps1
Step 6: Test Deployment
In your initial account, test a single endpoint migration. To do it, navigate to the Endpoints view, select an endpoint and install the Agent_Migration software package. After execution, check the automation is completed without errors.
Navigate to your new account and verify that the endpoint was added to a proper organization.
Step 7: Move Endpoints
In your initial account, create an automation for the organization. This automation should install the migration software package (Agent_Migration) to all endpoints within the organization.
Step 8: Close the Initial Account
Once all your endpoints are up and running in their respective organizations within a new account, contact Action1 Support to close your initial account. To maintain multi-region topology, you can keep both accounts, be sure to contact Action1 Support to avoid account closure.