Seqrite Endpoint Security 8.2

EPS 8.1 to 8.2 Migration

Print Friendly, PDF & Email

SEQRITE recommends EPS 8.1 customers to migrate to SEQRITE EPS 8.2.

These guidelines will help you to perform migration from 8.1 to 8.2. Existing customers go for server upgrade from 8.1 to 8.2 and can use new features available on 8.2 with no data loss.

Migration on Standalone IP to IP/Hostname

Follow these steps when you already have 8.1 server installed on CentOS machine and want to upgrade the EPSNG Server to 8.2:

You have 8.1 server data such as policies, configurations, custom packages, admin settings, reports for all features, registered endpoints, patch management, roaming, DLP policy, UA, AD, client actions, groups, users, file sandbox, 7.6 migrated client, monthly and weekly reports, and FAM. Just to double check, validate that all your previous data is loaded.

  1. To back up the data, follow these steps:

    a. You need to create a directory with the name Backup at /opt/Seqrite_EndPoint_Security/. Note that the directory name cannot be changed.

    b. Put run_backup.sh and backup_standalone.sh files on your server machine at /opt/Seqrite_EndPoint_Security/Backup. Copy these above files from this location: http://dlupdate.quickheal.com/builds/seqrite/uemcp/epsng/docs/Migration_8.1_to_8.2.zip.

    Note that you need to extract the zip before taking any further actions.

    c. Go the terminal and assign 755 permissions to both the files with this command: chmod 755 *file_name.*

    d. Execute the run_backup.sh file with this command: bash run_backup.sh 19.

    e. The success message appears as Backup is completed. The exportDump and MongoDump directories get created at the /opt/Seqrite_EndPoint_Security/Backup/ location.

    f. Download this directory to any other machine or any NFS or shared drive or any removable drive disk so in case of machine crash, your backup is not affected.

    Note: Minimum space requirement validation is 1GB. Ensure you have enough space to back up your data.

  2. After the backup is completed and copied to the new location (refer point f), shut down 8.1 server machine.
  3. Take new machine with Ubuntu 22.04 LTS installed. Assign the same IP that is server IP of 8.1 to Ubuntu machine which will be used for 8.2 server installation.

    Note: Ensure that all the 8.2 prerequisites are met before the installation starts.

  4. Install 8.2 with Activate Later option with basic configurations.

    a. If it is IP based Installation, then proceed with next steps.

    b. If it is a Hostname based installation, then the server machine Hostname needs to be properly FQDN configured.

    Note: Do Not activate unless you execute the following steps.

  5. Restore using following steps:

    a. Place the backup folder on your machine using the removable drive or get it from shared drive or any NFS. OR

    b. Open Mobaxterm and provide the server machine IP to log in to the backend of your server. From the left panel, go to this location to copy the backup /opt directory or from the CMD prompt cd/opt hit [Enter].

    c. Copy /Download exportDump and MongoDump and outputFilePath.txt file from backup directory to /opt directory.

    d. Rename exportDump and MongoDump directories to exportDump and MongoDump respectively.

    e. Put run_restore.sh, restore_standalone.sh and backward_compatibility_8.2.js in /opt directory and give 755 permissions to all the files with this command: chmod 755 *file_name*

    f. Execute run_restore.sh file using the bash run_restore.sh 19 command on terminal. Wait till you get a restoration success message, Restoration is Completed.

  6. Once all the above stages are completed, now activate the server with the same key used for 8.1 server.

    Note: To get the server activated again with the same key, first reset the AFG flag in activation DB.

  7. Just to double check once, validate that all your previous data is loaded.
  8. After the data restoration, decouple Cron needs to be executed to get the latest client/tool builds from the server.

    Important: Ensure that the migrated endpoints are updated to the latest VDB before performing the major upgrade.

  9. Perform the major upgrade on migrated clients (10.8) so they will upgrade to 10.9 CA version.
  10. Ensure that all Windows/Linux clients are upgraded to 10.9. Go to the Status page on the console and check the client agent version and the VDB.

Migration on Distributed IP to IP/Hostname Installation

  1. Install 8.1 server with distributed method on CentOS and generate data for backup.
  2. Do sanity policies, configurations, custom packages, admin settings, reports for all features, registered endpoints, patch management, roaming, DLP policy, UA, AD, client actions, groups, users, file sandbox, 7.6 migrated client, monthly and weekly reports, and FAM.
  3. Just to double check, validate that all your previous data is loaded.
  4. To back up the data, follow these steps:

    a. You need to create a directory with the name Backup at /opt/Seqrite_EndPoint_Security/. Note that the directory name cannot be changed.

    b. Put run_backup.sh and backup_standalone.sh files on your server machine at /opt/Seqrite_EndPoint_Security/Backup. Copy these above files from this location: http://dlupdate.quickheal.com/builds/seqrite/uemcp/epsng/docs/Migration_8.1_to_8.2.zip.

    Note that you need to extract the zip before taking any further actions.

    c. Go to the terminal and assign 755 permissions to both the files with this command: chmod 755 *file_name*

    d. Execute the run_backup.sh file with this command: bash run_backup.sh 19.

    e. The success message appears as Backup is completed. The exportDump and MongoDump directories get created at the /opt/Seqrite_EndPoint_Security/Backup/ location.

    f. Download this directory to any other machine or any NFS or shared drive or any removable drive disk so in case of machine crash, your backup is not affected.

    Note: Minimum space requirement validation is 1GB. Ensure you have enough space to back up your data.

  5. After the backup is completed and copied to the new location (refer point f), shut down 8.1 server machine.
  6. Take two Ubuntu machines and assign the IP of 8.1 Server and DB machine to Ubuntu machine for 8.2 installation.

    Note: Ensure that all the 8.2 prerequisites are met before the installation starts.

  7. Install 8.2 with Activate Later option with basic configurations.

    a. If it is IP based Installation, then proceed with next steps.

    b. If it is Hostname based installation, then the server machine Hostname needs to be FQDN configured.

    Note: Do Not activate unless you execute the following steps.

  8. For roaming client for distributed, a script must be run on the server machine.
  9. Restore using following steps:

    a. Place the backup folder on your machine using the removable drive or get it from shared drive or any NFS. OR

    b. Open Mobaxterm and provide the server machine IP to log in to the backend of your server. From the left panel, go to this location to copy the backup /opt directory or from the CMD prompt cd/opt hit [Enter].

    c. Copy /Download exportDump and MongoDump and outputFilePath.txt file from backup directory to /opt directory.

    d. Rename exportDump< Date_time > and MongoDump< Date_time > directories to exportDump and MongoDump respectively.

    e. Put run_restore.sh, restore_standalone.sh and backward_compatibility_8.2.js in /opt directory and give 755 permissions to all the files with this command: chmod 755 *file_name*

    f. Execute run_restore.sh file using the bash run_restore.sh 19 command on terminal. Wait till you get a restoration success message, Restoration is Completed.

  10. Once all the above stages are completed, now activate the server with the same key used for 8.1 server.
  11. Note: To get the server activated again with the same key, first reset the AFG flag in activation DB
  12. Just to double check once, validate that all your previous data is loaded.
  13. After the data restoration, decouple Cron needs to be executed to get the latest client/tool builds from the server.
  14. Important: Ensure that the migrated endpoints are updated to the latest VDB before performing the major upgrade.
  15. Perform the major upgrade on migrated clients (10.8) so they will upgrade to 10.9 CA version.
  16. Ensure that all Windows/Linux clients are upgraded to 10.9. Go to the Status page on the console and check the client agent version and the VDB.

Follow these steps if you had Patch Management server configured on 8.1:

For Patch Management, one script is run on the client after upgrade. Thus 8.1 patch server will work same to 8.2 patch server. (Applicable only for Windows)

  1. Extract and keep file (set_eps_guid.bat) at this location: C:\Program Files\Seqrite\Seqrite Patch Management\Patch Server
  2. Execute the batch file with parameter {PM Server Path} in command prompt in admin mode.

    set_eps_guid.bat C:\Program Files\Seqrite\Seqrite Patch Management\Patch Server UUID

    Note: To get the UUID, you need to run this command on the server machine: sudo dmidecode -q | grep -w UUID

    UUID: 423a6fb9-faf2-2ef1-f164-cba48f87ed1c

  3. You need to enter the password to execute this file. Get in touch with the Seqrite support team for the same.

Steps to Set FQDN

  1. Login as a root user.
  2. Check the status of hostname file using this command: hostname –fqdn. Check if it is within the domain, if not proceed with the following steps:
  3. Set hostname using this command: hostnamectl set-hostname *VMNAME*
  4. Edit hosts file using this command: nano /etc/hosts.
  5. Add this entry: VMIP vmname.qh.lan vmname.

    Example: 172.18.14.78 UEMQAC75x64-027.qh.lan UEMQAC75x64-027

Perform the Major Upgrade

Follow these steps to perform the major upgrade on migrated clients from 10.8 to 10.9 CA version.

Windows:

  1. Open the EPSNG server console.
  2. Go to Status page and select the endpoint.
  3. Select the Client Action as Upgrade Clients.

Linux:

Follow these steps to upgrade client when old client is already installed in new console:

  1. Go to the console.
  2. Go to Deployment section.
  3. Download the required Linux package that is, 32/64 bit.
  4. Go to the Client and log in as a root user.
  5. Go to the downloaded package location.
  6. Unzip the package using this command: tar -xvf package_name
  7. Check if all these files are present:

    o bu`ildNumber.txt

    o clagnt.dat

    o epslin64.tar

Was this page helpful?
Yes No