IMF Tune - Bringing Back the Exchange Connection Filter
IMF Tune - Disk Anti-Virus Configuration
On-access disk anti-virus scanning is known to interfere with disk access operations that other applications perform. Here we describe the IMF Tune Server directory structure explaining which disk directories are to be excluded from aggressive anti-virus scanning.
On-access scanning processes files as soon as these are written to disk. Scanning is triggered by most disk write operations, including creating and editing files.
For the duration of the scan, files become inaccessible to the application. Most often this forces applications to wait until the file becomes accessible again. In other cases an application may abort file access causing some failures. Less commonly anti-virus interference may even lead to data corruption.
Whereas on-access scanning may cause significant interference, scheduled scans are less intrusive. These can be configured to run after-hours when applications are running under less load. Thus applications are better able to cope with the impact of locked files.
IMF Tune Server Application Directory
The default IMF Tune application directory is:
Immediately under the application root we find the server binaries and various sub-directories. It is ok to have on-access scanning at the application root, but application performance will suffer if on-access scanning is also applied to the sub-directories.
The table that follows shows the recommended anti-virus settings using the labels:
Scheduled - Disabling of on-access AV scanning is recommended. Scanning may be configured to run on a fixed schedule when the email load is low.
On-Access - Enabling on-access AV scanning won't have a significant performance impact.
Note: Some directories in the table that follows contain other sub-directories. Apply the same AV scanning setting to the directory tree as for the parent directory.
This article was authored for WinDeveloper IMF Tune v6.x. It is normal for IMF Tune to retain the same directory usage definition across versions. So this article should remain largely applicable to future versions. Check with WinDeveloper Support for more details.