Update Guide: Endpoint Data Protection
Update procedure
During an update, the EgoSecure Server, the database and the EgoSecure Management Console are updated. In addition, the MSI package becomes available to install the EgoSecure Agent client component and can be deployed immediately. Depending on the version, configuration and environment, problems during an update may occur, which limits the software functionality on servers and endpoints.
Before you start
Before updating to the latest version, please review and confirm the following:
Compatibility
- Review the compatibility with your installed Server and Agent version in the Compatibility Matrix
- Always make sure that the EgoSecure Agent version is never higher than the EgoSecure version
Dependencies
- If you are using EgoSecure 23.0 Update 2 or earlier and you plan to update to EgoSecure 23.0 Update 3 or newer, there is an extra check you will need to perform manually to ensure a smooth update with no issues. Please run this SQL script on your EgoSecure database, if it returns any results (for each admin returned you will have name and email), you need to change their password ensuring the new one is meeting minimum password requirements, before updating to EgoSecure 23.0 Update 3 or newer. Then rerun the script to confirm there are no entries returned after you have addressed the issue.
- If you plan to update or already updated to 23.0 Update 3 or newer, please review this article.
- Starting with version 24.0.2, software requirements have changed, please check this article System Requirements.
The new usage of the MSOLEDBSQL v19 SQL driver changes the way the MultiSubnetFailover flag is handled. As per Microsoft documentation, "specifying MultiSubnetFailover=Yes when connecting to something other than an availability group listener or Failover Cluster Instance [...] is not supported". MultiSubnetFailover should be disabled (via AdminTool), before updating to 24.0.2, if EgoSecure Server does not connect to an Availability Group/Application Failover environment.
Perform the update
To avoid problems during update, we recommend to perform the update process in the following order:
Check and save the database
- Create a database backup before the update. For details, see Database migration
- To prevent the disk space from being insufficient during the update, configure the transaction log settings. For details, see Microsoft Docs: Troubleshoot a full transaction log
Disable automatic updates
- In the EgoSecure Console, navigate to Installation » EgoSecure agents » Installation settings.
- Under Download parameters, enable the option manually or schedule.
- Under Update parameters, enable the schedule option.
- Click Save.
Start update
- To ensure that you will be able restore the prior installation on the clients if needed, save the most recently used MSI package.
- Close the Console.
- Download the latest Endpoint Data Protection version from the Marketplace.
- Run the EgoSecureSetup_x64.exe file and follow the instructions:
- Proceed with Next
- Wait until the update process is finished
- Close the Update Complete with Finish
Additional Checks for Agents
- To check the functionality of endpoints, install the newly generated MSI package locally on a single computer and test the basic features you are using.
- Once the new Agent version is successfully tested, start the installation on the clients.