Seqrite Endpoint Security (EPS) Cloud

EPS 7.6 Migration

Print Friendly, PDF & Email

EPS Cloud is hosted Endpoint Security platform from SEQRITE.
SEQRITE recommends customers of EPS 7.6 should migrate to SEQRITE EPS Cloud.
For the current EPS 7.6 customers, SEQRITE is providing a tool to migrate data of clients, groups and policies from EPS 7.6 to EPS Cloud.
This page will guide you through the step-by-step migration process to migrate EPS 7.6 data of clients, groups and policies to EPS Cloud. This page is active for only 60 days from the activation date of Migration feature.

System requirements

Service Pack 5.0 applied on EPS 7.6 Server and clients
Windows and Linux
For System requirements for Seqrite EPS clients, refer System Requirements.
Important

  • If the OS requirements are not met, the client, groups and policies data will not be migrated to EPS Cloud.
  • The client is installed in the default path. You can modify the client installation path, if required. If you want to change the path, you should change the path before migration.
    To change the client installation path, go to EPS Cloud console > Configurations > Client Installation.

Migrating Data

EPS 7.6 Migration process means migrating the data of clients, groups and policies from the EPS Server to the EPS Cloud.

Migrating Clients, Groups, and policies

To migrate EPS 7.6 data of clients, groups and policies to EPS Cloud, follow these steps:

  1. Go to EPS Cloud console > Deployment > EPS 7.6 Migration page.

  2. Click the Export Tool button.
    The tool, migrationexport.zip is downloaded.

  3. Extract the zipped file on the EPS 7.6 server and execute migrationexport.exe.

  4. After the Export Tool is executed, ‘Do you want to change export location? [y/n]’, question appears. To provide local system path to export data of the Groups and clients, type ‘y’ and type the path.
    To export the data to the default path, type ‘n’. The default export path is installation directory SeqriteEndpoint Security 7.60AdminExport).
    After validating the path, the data is exported into the Export.zip by the Export Tool.

  5. Go to EPS Cloud console > Deployment > EPS 7.6 Migration page.

  6. Click the Import Data button.
    The Import Data dialog appears. By default, the Client, Groups and Policy check boxes are selected, so all clients, groups, and policies are imported.
    You can clear the Groups or Policy check boxes if you don’t want to import. If you don’t import Groups and you import only Policy, all clients will be imported in the default group. The policy will be imported but will not be assigned to any group.

  7. Click Browse to Import Export.zip file.

  8. Click Import.
    The data is imported successfully. The success message appears.
    Note

    • Maximum no. of groups to be imported: 999
    • Maximum no. of policies to be imported: 198

    Important: Group and Policy Migration

    • If a duplicate group is found on both EPS 7.6 and EPS Cloud, it will be skipped. But if the applied policies are different on duplicate groups, the policy applied on EPS Cloud remains the same. Example: If ‘Group1’ is present on both EPS 7.6 and EPS Cloud, after migration, the policy assigned to Group1 on EPS Cloud remains the same.
    • While importing the Firewall policy, ensure the following things.
      • In EPS 7.6, if multiple Remote IP addresses are added to the Firewall exception, then in the imported policy in EPS Cloud multiple exceptions will be created for each IP.
      • Domain name exceptions are ignored.
    • If a duplicate name is found in EPS 7.6 and EPS Cloud of the following components while importing, a timestamp will be appended to the imported name.
      • Policy
      • Device name
      • User Defined Dictionary|

  9. For Windows, do the following.

    1. If you want to change the default client installation path, go to EPS Cloud console > Configurations > Client Installation. Else, client will be installed at default location.
    2. Go to EPS Cloud console > Deployment > On EPS 7.6 Migration page, click the Client Migration Tool button.
    3. The Client Migration Tool, migrate.zip is downloaded.
    4. Extract the zipped file on the EPS 7.6 server and execute acsvpack.exe. This will apply Service pack on the endpoint.
    5. Restart the endpoint when the restart prompt will appear on the endpoint. You will receive 2 restart prompts during migration process in case you have not rebooted the system after EPS 7.6 client installation.
      For Linux, do the following.
      a. Go to EPS Cloud console > Deployment > Online Installer page.
      b. Download latest Linux Seqrite Client packager on the Linux client.
      c. The Client Installer tar file is downloaded. Extract the files on the Linux client.
      d. Execute the Installer. Uninstallation of previous version and installation of latest version will be done automatically.

The data of clients, groups and policies will be migrated successfully.
Migrated Clients will appear online on the EPS Cloud console.

Removing inactive clients from EPS 7.6

The migrated clients appear offline/inactive on the EPS 7.6 Web console.
To remove inactive clients, follow these steps:

  1. Log on to the Seqrite Endpoint Security 7.6 Web console.
  2. Go to Admin Settings > Clients.
    The Client Installation page appears.
  3. Under Inactive Client Settings, select the Enable automatic removal of inactive clients check box.
  4. In the Remove a client if inactive for list, select number of days after which Seqrite Endpoint Security considers a Client is inactive.
  5. To apply the setting, click Apply.

Limitations

  • EPS Migration 7.6 does not support the clients with Mac operating systems.
  • The Default client on the EPS Server will not be migrated to EPS Cloud.
  • Update Agent upgrade is not supported.
  • Master Secondary setup not supported for EPS Cloud.
  • Migration of EPS Users and reports are not supported.
Was this page helpful?
Yes No