Capture Client migration across consoles

09/24/2024 6 People found this article helpful 101,346 Views

Description

SonicWall customers using Capture Client, can seamlessly transfer or re-register existing clients to a tenant in another console, using the “Migrate Client” feature introduced in Capture Client Management version 3.8.0. Windows & macOS clients having version 3.8.0 or later can be migrated across consoles (North America, Europe or MDR) without uninstalling and reinstalling Capture Client .

Below are relevant URLs for migration:

Capture Client console
1. NOAM – https://captureclient-36.sonicwall.com
2. EMEA – https://captureclient-eu.sonicwall.com
Capture Client MDR console
1. NOAM – https://captureclient-mdr.sonicwall.com
2. EMEA – https://captureclienteu-mdr.sonicwall.com

A new identifier called "Tenant token" is introduced, which needs to be provided as input. This article describes the pre-requisites and steps involved in performing migration.

Pre-requisites

Below are the pre-requisites for the migration process to commence. Please ensure these conditions are met for the clients being migrated.

Go to your Capture Client Tenant on MySonicWall and remove the CC license sharing with Firewall. Refer to this Firewall Enforcement article for more details.
Go to your CC enforced Firewall and disable the Firewall enforcement for the endpoints
Endpoints should be running agent version 3.8.0 or later.
The Endpoint agent should not be in the Full Disk Scan mode.
The Endpoint must not have unresolved threats
The Endpoint is online.
Target Management console should not be under maintenance or experiencing downtime
Destination tenant token should be valid

How to perform migration?

Below are the steps to migrate your client(s) across consoles . As an example, you can migrate existing clients on a tenant in North America console to a new tenant in Europe console.

Activate Capture Client using a trial or a valid license in your preferred data center, to which you want to migrate client(s)
Navigate to Capture Client Management Console. Go to “Tenant Settings” and copy the tenant token. This is the destination console i.e., the console TO which you want to migrate client(s).
On the source console i.e., the console FROM which you want to migrate the client
1. Navigate to Assets |Devices.
2. From the List View tab, select the device(s) for which you want to migrate the agents. Please note multiple devices can be selected at once for migration.
3. Click on the gear icon on the right side. The actions that you can take on that particular endpoint are displayed.
Click on Migrate Agent (showed in red outline above). The Input Tenant Token Window is displayed.
Enter the Tenant Token. This is the tenant token for the new tenant, copied earlier on the destination console.
Click Confirm. The Endpoints are automatically migrated to the new tenant on the destination console.

Please note that migration is not supported from one tenant to another within the same console.

Key Considerations

If the tenant token entered for migration is invalid, the migration will fail. However if the tenant token matches another tenant, the devices will successfully migrate to that tenant.
If the agent on which migration is being attempted has any one of below, the migration will not happen.
1. Has unresolved threats OR
2. is in Full Disk Scan mode
The Capture Client agent is auto-decommissioned 24 hours after a successful migration.
The S1 Agent is NOT decommissioned after a successful migration - it will show up under "Unmanaged SentinelOne Agents" in the source console.

Not Finding Your Answers?

ASK THE COMMUNITY

Was This Article Helpful?

YES NO

Capture Client migration across consoles

Description

Pre-requisites

Key Considerations

Related Articles

Categories

Not Finding Your Answers?

Was This Article Helpful?

Article Helpful Form

Article Not Helpful Form

Follow Us

Subscribe to newsletter

Stay In Touch