Seqrite Endpoint Security 8.2

EPS 7.2 Migration

Print Friendly, PDF & Email

Seqrite recommends customers on EPS 7.2 to migrate to Seqrite EPS 8.2.
These guidelines will help the current EPS 7.2 customers perform migration from EPS 7.2 to EPS 8.2.

Pre-requisites:
Download these binaries from the following locations:

System Requirements

Note: EPS Migration 7.2 does not support the clients with Linux, Mac, Windows Vista, Windows XP, Windows 2000 server, and Windows 2008 server.

Important to Know:

  • If the OS requirements are not met, the clients, groups, and policies data will not be migrated to EPS 8.2.
  • 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 8.2 console > Configurations > Client Installation.

Migrating Data

To migrate the clients, groups, and policies data from the EPS Server 7.2 to the EPS Server 8.2, follow these steps:

  1. Extract the migrationexport.zip file that you downloaded.
  2. Execute the export tool (migrationexport.exe) on the EPS 7.2 server.
  3. 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 clients, groups, and policies, type ‘y’ and type the path.
  4. To export the data to the default path, type ‘n.’

    5. The default export path is < installation directory > \ Seqrite\Endpoint Security7.2\Admin\Export .
    After validating the path, the data is exported in the .DAT format at the set path. The Client.dat and Groups.dat files will be zipped automatically to Export.zip by the Export Tool.

  5. Go to EPS 8.2 console> Deployment > EPS 7.6 Migration page.
  6. Click the Import Data button. The Import Data dialog appears. By default, the Group, Client, and Policy check boxes are selected. Thus, all groups, clients, and policies are imported. If you do not want to import any of it, clear the respective check box.
  7. Click Upload File or Browse to import Export.zip file.
  8. Click Import Data. The data is imported successfully. The success message appears.

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


    For Group and Policy Migration, please note

    • If a duplicate group is found on both EPS 7.2 and EPS 8.2, it will be skipped. But if the applied policies are different on duplicate groups, the policy applied on EPS 8.2 remains the same.
      Example: If ‘Group1’ is present on both EPS 7.2 and EPS 8.2, after migration, the policy assigned to Group1 on EPS 8.2 remains the same.
    • If a duplicate name is found in EPS 7.2 and EPS 8.2 of the following components while importing, a timestamp will be appended to the imported name.
      • Policy
      • Device name
      • User Defined Dictionary

Migrating Clients

To migrate the local and roaming clients, follow these steps:

  1. On the EPS 7.6 Migration page, click the Client Migration Tool button. The Client Migration Tool, migrate.zip is downloaded.
  2. Extract the migrate.zip file. A folder named migrate gets created. The migrate folder contains accadef.ini, acsvpack.exe, agntsetp.exe, agsetp64.exe, clagnt.dat, and clagnt.ini files.
  3. Delete the acsvpack.exe from this folder.
  4. Copy acsvpack.exe from EPS 7.2 migration folder that you downloaded from the above mentioned location and paste it into the migrate folder that got created after downloading the migrate.zip from the console.
    Ensure that accadef.ini, acsvpack.exe, agntsetp.exe, agsetp64.exe, clagnt.dat, and clagnt.ini files are all in the same folder before executing acsvpack.exe
  5. Execute acsvpack.exe on the EPS 7.2 server.
  6. The Client Migration tool prompt appears.

    7. If you select Yes, the endpoints will be migrated group-wise.
    If you select No, all the endpoints will be migrated in one go.

  7. The success message appears. Click Ok.

    8. The Migration Service pack is applied on EPS 7.2 server successfully.

    Migrating Group-wise endpoints

    To migrate group-wise endpoints, follow these steps.

    1. Log on to the Seqrite Endpoint Security 7.2 console.
    2. Go to Clients > Manage Groups.
    3. Select the group from which the endpoints need to be migrated. You can migrate a group only once.
      A submenu list appears.
    4. Select Endpoint Migration.
      The confirmation screen appears.
    5. Click Yes.
    6. Restart the endpoint. You will receive two restart prompts during the migration process if you have not rebooted the system post EPS 7.2 client installation.

    The migration feature is applied to the selected parent group and all child subgroups if available. All the endpoints under the parent group and child group, if available are migrated to EPS 8.x.

    The clients, groups, and policies data will be migrated successfully.

    Migrated clients will appear online on the EPS 8.2 console.

Removing Inactive Clients from EPS 7.2

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

  1. Log on to the Seqrite Endpoint Security 7.2 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

  • The Default client on the EPS Server will not be migrated to EPS 8.2. To migrate EPS 7.2 default client, first uninstall the EPS 7.2 server and then install EPS 8.2 client manually.
  • EPS Migration 7.2 does not support the clients with Linux and Mac operating systems. To migrate Linux and Mac client, first uninstall the EPS 7.2 Linux/Mac endpoint and then install EPS 8.2 Linux/Mac client manually
  • Update Agent upgrade is not supported.
  • Migration of EPS Users and Reports are not supported.
Was this page helpful?
Yes No