FortiClient
FortiClient proactively defends against advanced attacks. Its tight integration with the Security Fabric enables policy-based automation to contain threats and control outbreaks. FortiClient is compatible with Fabric-Ready partners to further strengthen enterprises’ security posture.
arleniscg
Staff
Staff
Article Id 314312
Description This article describes how to migrate some configurations from the FortiClient EMS server on-premise to a FortiClient EMS cloud instance. 
Scope FortiClient EMS v7.4.x.
Solution

Option 1: For an On-prem EMS server migration, the recommendation is to use Best Practices Service.

 

Option 2: If there is no BPS license, use the following options for the migration of some configurations:

 

Import only XML profiles on EMS Cloud if the original EMS was running the same version as the FortiClient EMS Cloud instance.

FortiClient EMS database from an on-prem server cannot be migrated to FortiClient EMS Cloud.

It is only supported to migrate the FortiClient EMS database from the FortiClient EMS server on-premise to the FortiClient EMS server on-premise (both servers running the same version).

 

Migrating to another EMS instance:

  1. Upgrade the FortiClient EMS server on-premise to the same version running on the FortiClient EMS Cloud.
  2. Download XML profile from the FortiClient EMS on-premise server:

 

EMS7.png

EMS8.png

 

  1. Import XML profile on FortiClient EMS Cloud:

 

EMS9.png

EMS10.png

 

  1. Create Endpoint policy:

 

EMS11.png

 

  1. Identify endpoints that will connect to the new FortiClient EMS Server Cloud, for example: UserEMS.
    Use the option 'Switch EMS' available on FortiClient EMS -> Endpoint -> Action -> Switch EMS and use the FortiClient EMS Cloud invitation code. 

 

EMS12.png

EMS12 part2.png

EMS13.png

EMS14.png