Objective: These guidelines will help you perform migration from EPS 7.4 to EPS Cloud 3.0.
Description: Existing customers go for server and client upgrade from EPS 7.4 to EPS Cloud 3.0 and can use new features available in EPS Cloud 3.0 with no data loss.
Pre-requisites: Download these binaries from the following locations:
- migrationexport.zip – This is an export tool which is used to export Groups, Clients, and Policy Data from EPS 7.4 server. https://dlupdate.quickheal.com/builds/seqrite/uemcp/migrate/74/cloud/migrationexport.zip
- acsvpack.exe – This is a client migration tool which is used to migrate local and roaming clients from EPS 7.4 to EPS Cloud 3.0
https://dlupdate.quickheal.com/builds/seqrite/uemcp/migrate/74/cloud/acsvpack.exe
OS Requirements:
- Service Pack 2 applied on EPS 7.4 Server and Clients
- Windows: For System requirements for Seqrite EPS clients, See System Requirements.
Note: EPS Migration 7.4 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 Groups, Clients, and Policy data will not be migrated to EPS Cloud.
- The client is installed in the default path. If you want to change the path, it needs to be changed before migration begins.
To change the client installation path, go to EPS Cloud console > Configurations > Client Installation.
To migrate clients, groups, and policies data from EPS 7.4 to EPS Cloud 3.0, follow these steps:
1. Extract the migrationexport.zip file that you downloaded.
2. Execute the export tool (migrationexport.exe) on the EPS 7.4 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’. The default export path is <installation directory> \Seqrite\Endpoint Security7.4\Admin\Export.
After validating the path, the data is exported in the .DAT format at the set path. The Client.dat, Groups.dat, and Policy files will be zipped automatically to Export.zip by the Export Tool.
5. Go to EPS Cloud 3.0 console > Deployment > EPS 7.6 Migration page.
6. Click the Import Data button. The Import Data dialog appears. By default, the Groups, Client, and Policy check boxes are selected. Thus, all clients, groups, 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.
Limitations:
- Maximum no. of groups to be imported: 999.
- Maximum no. of policies to be imported: 198.
Note:
- If a duplicate group is found on both EPS 7.4 and EPS Cloud 3.0, it will be skipped. But if the applied policies are different on duplicate groups, the policy applied on EPS Cloud 3.0 remains the same.
Example: If ‘Group1’ is present on both EPS 7.4 and EPS Cloud 3.0, after migration, the policy assigned to Group1 on EPS Cloud 3.0 remains the same.
- While importing the Firewall policy, ensure the following things.
- In EPS 7.4, if multiple Remote IP addresses are added to the Firewall exception, then in the imported policy in EPS Cloud 3.0, multiple exceptions will be created for each IP.
- Domain name exceptions are not imported.
- If a duplicate name is found in EPS 7.4 and EPS Cloud 3.0 of the following components while importing, a timestamp will be appended to the imported name.
- Policy
- Device name
- User Defined Dictionary
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 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.
5. 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.
6. Execute acsvpack.exe on the EPS 7.4 server.
7. The Client Migration tool prompt appears.
a. If you select Yes, the endpoints will be migrated group-wise. Refer steps from Migrating Endpoints by Group.
b. If you select No, all the endpoints will be migrated in one go.
1. The success message appears. Click Ok.
The Migration Service pack is successfully applied on EPS 7.4 server.
To migrate group-wise endpoints after applying SSP, follow these steps.
1. Log on to the SEQRITE Endpoint Security 7.4 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 sub-menu list appears.
1. Select Endpoint Migration.
The confirmation screen appears.
2. Click Yes. A restart prompt appears on the endpoint.
3. Restart the endpoint. You will receive two restart prompts during the migration process if you have not rebooted the system post EPS 7.4 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 Cloud.
The clients, groups, and policies data will be migrated successfully.
Migrated clients will appear online on the EPS Cloud console.
The migrated clients appear offline/inactive on the EPS 7.4 web console.
To remove inactive clients, follow these steps:
1. Log on to the Seqrite Endpoint Security 7.4 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 as inactive.
5. To apply the setting, click Apply.
- The default client on the EPS Server will not be migrated to EPS Cloud. To migrate EPS 7.4 default client, first uninstall the EPS 7.4 server and then install EPS Cloud client manually.
- EPS Migration 7.4 does not support the clients with Linux and Mac operating systems. To migrate Linux and Mac client, first uninstall the EPS 7.4 Linux/Mac endpoint and then install EPS Cloud Linux/Mac client manually.
- Update Agent upgrade is not supported.
- Migration of EPS Users and Reports are not supported.
Please contact Seqrite Technical Support for more assistance.