Usable AVs (antivirus)
Usable AVs are the anti-malware engines that Metadefender Core uses to process scan requests. All embedded engines are usable anti-malware engines. For anti-malware applications that are installed by you, please check the list of products that Metascan supports.
This list can be retrieved from:
Any command line utility (omsCmdUtil.exe) command
Metadefender Core Management Console Configuration Page
Current AVs are anti-malware engines that Metadefender Core automatically uses for scans and updates. This list is affected by licenses and properties such as included antiviruses, excluded antiviruses, and supported pre-installed antiviruses.
Example of Current AVs vs. Usable AVs
For example, you install Metadefender 8 on a machine that also has McAfee VirusScan installed on it. In Metadefender 8 you disable Customer Licensed Engines option and you exclude the ESET scanning engine. Your "Current AVs" and "Usable AVs" will be designated as below:
Customer Licensed Engine
"Customer Licensed Engine" is the term used to describe an antivirus application that is already installed on your server (in other words, an antivirus engine for which you, the customer, has already purchased a license to use, such as an antivirus application that is installed on all computers in your corporate environment) which can then be incorporated as another engine to be used by Metadefender Core. You can view a list of antivirus applications that can be used as a Customer Licensed Engine here. A compatible antivirus application that is installed on the server will be automatically detected and made visible as an engine in the Metadefender Core Management Console (MMC). You can then use the MMC to enable the engine for Metadefender Core.
Note: Metadefender Core's embedded engines are configured for optimal performance, whereas a Customer Licensed Engine is not. Thus, the performance of Metadefender Core can be adversely affected by a Customer Licensed Engine.
Metadefender Core can be delegated to queue scan requests and return the results of queued scans via callbacks with extensive scan details. Even if your application is single threaded, you can process many scan requests without blocking. In other words, as soon as you have data to be scanned and you call the asynchronous scan API of Metadefender Core (for example, PutToScanQueue), you can continue to request scans without waiting for the results of the scan.
On the other hand, a synchronous scan is more suitable if your application creates scan requests in many threads. Refer to the ScanEx section on how to retrieve scan details when scanning synchronously.
Valid file name
A valid file name as a parameter for any API related to scanning files should meet the following requirements:
Absolute path to file, folder, and drive (e.g., c:, C:\Windows, C:\boot.ini)
File path should be limited to the local machine (e.g., “\\remote_machine\testfile.txt” would be recognized as an invalid path)