Update Guide: Endpoint Data Protection
Update procedure
This guide is intended to avoid potential problems during an update and contains important information on dependencies, compatibility between the different versions and specific configurations to ensure that the update works smoothly on servers and endpoints. In general, the EgoSecure server(s), the database and the EgoSecure Management Console are updated during an update. In addition, the MSI package for installing the EgoSecure Agent Client component becomes available and can be used immediately.
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
- Since Endpoint Data Protection 24.0 Update 2, both Microsoft Visual C++ Redistributable x86 and x64 are required on the EgoSecure server before installing or updating.
- Before updating to Endpoint Data Protection 24.0 Update 2, MultiSubnetFailover should be disabled via the AdminTool if the EgoSecure Server does not connect to an Availability Group or Application Failover environment. The new usage of the MSOLEDBSQL v19 SQL driver changes the way how the Multi Subnet Failover 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.
- General MySQL and MySQL Community Server 5.x databases are no longer supported as of Endpoint Data Protection 24.0 and newer.
- If you plan to update or already updated to Endpoint Data Protection 23.0 Update 3 or newer, please review this article to avoid various problems and performance issues caused by some old malformed information still present in the DB.
- If you are using Endpoint Data Protection 23.0 Update 2 or earlier and you plan to update to Endpoint Data Protection 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 Endpoint Data Protection 23.0 Update 3 or newer. Then rerun the script to confirm there are no entries returned after you have addressed the issue.
- SQL Server 2012 and Windows 2012 R2 are no longer supported since Endpoint Data Protection 23.0 Update 2.
- If you use Windows Authentication to access the SQL Server, ensure to perform the update under the same account. Otherwise the setup will terminate with an Unhandled exception (0x800a0e78) due to missing permissions. You can review your current configuration by opening the EgoSecure Admin Tool.
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.