Skip to main content
Matrix42 Self-Service Help Center

Update Guide: EgoSecure Agents

EgoSecure Agent Update

In this part you can find information about the Agent update process. There are two ways:

  • Updating via EgoSecure Data Protection Console
  • Updating via install.bat or ESAgentSetup.exe file

Before you start

To avoid system conflicts, ensure always that the Agent version is NOT higher than Server version. If Agent version is higher, the connection between them cannot be established.  Review the compatibility with your installed Server and Agent version in the Compatibility Matrix .

Defining automatic update settings

  • Go to Installation | EgoSecure Agents | Installation settings.
  • In the Automatic update of EgoSecure agents – client parameters area, select a source from where MSI package is downloaded:
    • EgoSecure Server to update from the folder on the Server computer. The MSI package in this location is regenerated automatically along with the server update.
    • Network directory to update from the folder on the network. Once the Server is updated, the MSI package in this location must be regenerated manually.

The msi package stored on the network must have the name ESAgentSetup.msi. If a package is tenant-specific (has additions to the name, e.g., ESAgentSetupTenant1.msi) please, rename it.

  • If network directory was selected in the previous step, define the path to the MSI package and user login data to access the specified directory.
  • In the Directory field, select the directory from where the MSI package will be downloaded.
  • Under download parameters, select:
    • Manually to download MSI package manually (Installation | EgoSecure agents | Install/Update).
    • Automatically to download an updated MSI package each time when the EgoSecure Server is updating.
    • Schedule to download an updated MSI package at the specified date and time.
  • Under update parameters, select:
    • At once to start an update process shortly after finishing an automatic, scheduled or manual package downloading.
    • Schedule to start an update process at the specified date and time.
  • In the Automatic update of EgoSecure agents – server parameters area, set how many clients can be updated simultaneously.
  • Specify a maximum network load of a computer where the Server is installed. If this value is exceeded, other clients are waiting for an update.
  • Click Save.

Update via EgoSecure Data Protection Console manually

  • In the EgoSecure Data Protection Console, go to Installation | EgoSecure agents | Install/Update.
  • Check the Agents for update.
  • Click Install/Update.

Update via install.bat file locally

  • Go to Installation | Create MSI package.
  • Define the settings, path and name for the package, and then press Generate. To see the setting description, select the setting and read the description in the bottom of the dialog.
  •  Copy the following files to endpoints depending on the bitness of the system:
    • 64-bit: ESAgentSetup_x64.msi and install_x64.bat
    • 32-bit: ESAgentSetup.msi and install.bat
  • Open the .bat file with notepad and define the path to ESAgentSetup.msi (or ESAgentSetup_x64.msi) and to the AgentInstall.log file. If the password for update has been defined, add it via the ADMINPWD="" command.
    • Example: start /B msiexec /i C:\EgoSecure\MSI\ESAgentSetup_x64.msi /l* C:\EgoSecure\MSI\AgentInstall.log REINSTALL="ALL" REINSTALLMODE="vamus" ADMINPWD="" PKCS12_PASS=""
  • Save the changes.
  • Run install.bat (or install _x64.bat) as administrator.

Update via ESAgentSetup.exe file locally

  • Go to Installation | Create MSI package.
  • Define the settings, path and name for the package, and then press Generate. To see the setting description, select the setting and read the description in the bottom of the dialog.
  • Copy the following files to endpoints depending on the bitness of the system:
    • 64-bit: ESAgentSetup.exe and ESAgentSetup_x64.msi
    • 32-bit: ESAgentSetup.exe and ESAgentSetup.msi
  • Start ESAgentSetup.exe.
  • Enter the update password if it was defined in the MSI package settings.
  • Was this article helpful?