Title
Create new category
Edit page index title
Edit category
Edit link
System Requirements
Hardware Requirements
Minimum | Recommended | |
|---|---|---|
CPU | 4 cores | 16 cores |
RAM | 8 GB | 32 GB |
Free Disk Space | Sufficient to temporarily hold at least double the size of the file you wish to process. For instance, to process a 1 TB file, ensure at least 2.1 TB of free space is available. Once processing is complete, the space will be restored. | |
DB sizing | Determined by log retention policies (default: 90 days). Unlikely to exceed 1 GB. Examples:
Note: files themselves are not stored in the database. |
Software Requirements
Operating Systems
Windows 11
Windows 10
Windows Server 2012 R2 / 2016 / 2019 / 2022
Bitness: 64-bit only
Windows Installer 5.0 or higher
Minimum Supported Browsers
Chrome
Microsoft Edge 38 or later
Safari 5.1 or later
Firefox 52.9.0 or later
Additional Installation of Third-Party Frameworks/Components
MetaDefender Managed File Transfer automatically installs the following frameworks/components which should not be removed:
Name | Details |
|---|---|
.NET Framework | |
Microsoft Visual C++ 2015-2019 redistributable | |
.NET Runtime | |
ASP.NET Runtime |
Database Installation
MetaDefender Managed File Transfer bundles Microsoft SQL Server 2019 Express LocalDB by default. However, using an SQL Server from the following table is recommended:
Name | Editions | Supported |
|---|---|---|
SQL Server 2014 | All | Yes |
SQL Server 2016 | All | Yes |
SQL Server 2017 | All | Yes |
SQL Server 2019 | All | Yes |
SQL Server 2022 | All | Yes |
An SQL Server local account must have at least the following server roles: public, sysadmin.
Windows Authentication (Integrated Security) is supported, and the service account should have "Logon as Service" rights.
Azure SQL Managed Instance can serve as the database for MetaDefender Managed File Transfer™. However, network speed and the physical distance between MetaDefender® MFT and the database instance can result in slower response times for MetaDefender® MFT.
Web Server Configuration
MetaDefender Managed File Transfer uses NGINX as the embedded HTTP(S) and reverse proxy server. The web server is embedded in the application and is not shared with other processes running on the machine. After uninstalling MetaDefender Managed File Transfer, all NGINX processes will be stopped, and the program will be physically removed from the hard drive.
On startup, the web server will listen on the configured HTTP(S) port or on the default HTTP port (8010 if free) in case of a clean install.
From versions 1.3.7 onwards, REST API calls should be made to the Web UI port because TLS/SSL connections are no longer supported and the REST API service connection is thus unsecured. NGINX acts as a TLS/SSL termination proxy for the REST API service.
Port Usage
MetaDefender Managed File Transfer requires two free ports to run.
Service name | Port | Firewall Rule |
|---|---|---|
MetaDefender Managed File Transfer Web UI | 8010 | Needed |
MetaDefender Managed File Transfer REST API | 8000 | Not needed; Internal usage only |
MetaDefender Managed File Transfer Next | 8001 | Not needed; Internal usage only |
Whitelisting Requirements
To access the user interface externally, open port 8010 (default).
Whitelist any processes running from the MetaDefender Managed File Transfer install directory. Exclude the folder from any real-time protection.
Exclude the file storage (permanent and temporary) or the installation folder from real-time protection.
The service account should have "Logon as Service" rights to:
start, stop, and interact with services without requiring interactive logon privileges
log on and run scheduled or automatically executed batch jobs
connect to the database using Windows Authentication.