MEET ACTION1 AT RSA CONFERENCE 2024

May 6 - 9 | San Francisco | Booth #5472

Action1 5 Documentation 5 Migrating Between Regions

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
  • Europe

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, automations, 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 expire 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:

  1. Sign in to the initial account.
  2. Make sure endpoints are online.
  3. Disable Action1 Deployer. Follow to the endpoint where Action1 Deployer is installed, open Services snap-in, stop and disable the appropriate service.
  4. Navigate to Configuration > Agent Deployment and ensure Deployer doesn’t manage your endpoints.
  5. Disable all automations.
  6. Make sure there are no automations running against the endpoints.
Migrating agents

Step 3: Create New Organizations

In your new account:

  1. Re-create the organizations you had in your initial account.
  2. 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:

  1. Download migration_v1.20.zip
  2. Add agent MSI from a respective new organization to zip file.

The zip file should include the following files:

  • action1_agent(My_Organization).msi
  • launcher.ps1
  • migration.ps1

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.

  1. Navigate to Software Repository and select + Add to Repository.
  2. Provide a name ‘Agent_Migration’, vendor ‘Action1’ and specify description.
  3. Add a new version.
  4. On the General tab:
    • Version number is set to 1.20
    • App Name Match is set to ^(Action1AgentMigration)$
Migrating agents
  1. 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
Creating a package for agent

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.

Running migration policy

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, you can close your original tenant.

  • Free subscription: in the Action1 console navigate to Subscription and select Close Account.
  • Paid subscription: contact Support to close the tenant for you.

To maintain multi-region topology, you can keep both accounts. Paid customers are advised to contact their Sales representative to get an updated quote.