What's new
New features and enhancements in ESET Mail Security:
•Rebootless upgrades—When upgrading to ESET Mail Security version 12.1, the installer now includes a rebootless feature, allowing the upgrade to be performed without requiring a system restart. This feature is applicable when upgrading from ESET Mail Security version 10.0 or later. However, if you are upgrading from version 8.0 or 9.0, rebootless functionality is only available on systems where Device control is disabled. A server restart is required for upgrades from version 8.0 or 9.0 with Device control active.
•Support for rebootless installation parameter in ESET PROTECT software install task. If you manage ESET Mail Security via ESET PROTECT, you can achieve a rebootless upgrade by leaving the Automatically restart device option deselected in the software install task.
•Support for mandatory ESET HUB account subscription campaign.
•Optional switch to run Auto-updates in test-network/pilot-group first, before deployment into the production.
•Rule conditions exception—You can now define exceptions to your existing rule conditions using the usual parameters (Type and an Operation). However, when there is a match for the exception, this provides for exclusion from the rule conditions, and the actions will not be applied.
•ESET Vulnerability & Patch Management—Extended Vulnerability & Patch Management maintenance window scheduler, allowing monthly and more recurrence options.
•Vulnerability & Patch Management logs were extended with more detailed information about the patching results.
•Added Multithread scanning for Hyper-V and Device scans.
•Antispam now reports false positive detections.
•Quarantine reports can now be sent to members of security groups.
•The identity of the currently logged-in user was added to the detection logs.
•Limit incoming RDP connections—RDP access restriction feature for ESET Mail Security without a firewall component.
|
If you perform an attended fresh installation locally on the server, the Limit incoming RDP connections to is set to Trusted zone by default. If you perform an installation remotely over RDP, the Limit incoming RDP connections to is set to All networks by default. This setting is meant to be temporary and to prevent your RDP connection from being cut off until you configure the Trusted zone. In both cases, we recommend configuring the Trusted zone to include networks, IP addresses, or IP address ranges from which you specifically allow RDP connections to the server. Go to Network access protection > IP sets and edit Trusted zone IP set. After configuring the Trusted zone IP set to your needs, change the Limit incoming RDP connections to use the Trusted zone from the previous All networks setting to secure your server and take advantage of the RDP access restriction feature while having the RDP fully functioning within your company networks. |
Refer to detailed changelogs for ESET Mail Security.