E-mail has become the main infection vector of computers. Threats like viruses, worms and other malicious applications.
Therefore it should be, especially in large enterprises, checked at the highest possible level utilizing antivirus for Microsoft
Exchange.
ESET’s solutions always offer unsurpassed fast scanning and the highest rate of proactive detection. Moreover,
NOD32 antivirus for Microsoft Exchange offers multithreaded scanning in the background for higher performance and priority
or rule based predictive scanning . If MS Exchange Server is used as a gateway, NOD32 tests all incoming mails. NOD32 antivirus
protection for MS Exchange servers automatically generates detailed log files and enables administrators to send virus detection
messages using LAN or e-mail messages. Moreover, this solution offers flexible task scheduling via the NOD32 Remote Administrator.
New features in version 2.71 of the ESET NOD32 – Antivirus Protection for MS Exchange Servers
ESET NOD32 Antivirus for Microsoft Exchange brings lightweight and powerful protection for heavy-duty e-mail
servers. Version 2.71 is a major update which provides full Microsoft Exchange 2007 support and important changes to the product
architecture effectively increasing stability and performance.
Features:
Full Microsoft Exchange 2007 support
Product comes in two versions:
- 32-bit version for MS Exchange
5.5, 2000 & 2003
- 64-bit version for MS Exchange 2007
Improved architecture
Version 2.71 brings the possibility to use external scanning engine an ESET ThreatSense
engine running inside the ESET Control Center, independently of the MS Exchange server. Note that the 64-bit version can only
use external engine.
More detailed background scanning configuration
Background scan can be configured to run only on messages received in certain time period. Additionally the product
may be configured to scan only messages with attachments.
Background scan scheduling
Background scan can be scheduled to run only in specified time frame.
Rules based on mailbox name
Rules can be now executed also based on the name of mailbox.
Performance monitor
Log file can now include performance information, which can be used by the administrator
to optimize configuration.
