Update
By default, the Update type is set to Regular update. This ensures the detection signature database and application modules are updated automatically daily from ESET update servers.
Pre-release updates include the most recent bug fixes and detection methods available to the general public soon. However, they might not be stable at all times; therefore, it is not recommended to use them in a production environment.
Delayed updates allow updating from special update servers providing new versions of virus databases with a delay of at least X hours (that is, databases tested in a real environment and considered stable).
If an ESET Server Security for Linux update was not stable, roll back the module updates to a previous state. Click Status Overview > Module update > Module rollback, select the desired duration, click Rollback now.
By default, only one snapshot of modules is stored locally. To store more snapshots, increase the Number of locally stored snapshots to the desired number.
By default, the module updates have enabled the option Enable more frequent updates of detection signatures. Disabling this option may negatively impact the detection rate.
Application Update
Automatic application updates for ESET Server Security for Linux (ESSL) are enabled by default. We recommend that you keep this setting enabled to ensure that ESSL has the latest application updates applied when a new update is available.
Auto-updates
New packages are automatically downloaded and then installed after the next restart of OS. If there have been major updates to the End User License Agreement, the user must accept the updated End User License Agreement before downloading the new package.
Update timing
•Gradual update rollout—Choose gradual updates for stability, with timing determined by ESET. The update is rolled out per endpoint individually, and it may take from a few weeks to 1–2 months for the update to become available for all other endpoints.
•Immediate auto-updates—Choose immediate updates, installed right after release, for faster deployment.
Custom server, Username, Password
If you manage several ESSL instances and prefer update from a custom location, define the address and applicable access credentials of an HTTP(S) server, local drive, or removable drive.