On‑premises: split servers¶
At a glance¶
Who: M‑Files Server and SQL Server on different machines (same domain/network)
Outcome: VAF on M‑Files Server, database on SQL Server
Installer steps is similar for both single and split server installations: use images from Package installation - step by step
Also read: Common installation notes
Prerequisites¶
Two servers in same domain/network: one M‑Files Server, one SQL Server
M‑Files Desktop installed on both servers
Installer user has M‑Files System Admin (temporary) and SQL sysadmin
Network: SQL instance and port open from M‑Files Server to SQL Server
Steps¶
- On M‑Files Server: run installer
Choose M‑Files only
Log into M‑Files and select the vault (Vault Admin user)
Complete and take the vault offline/online
- On SQL Server: run installer
Choose SQL only
Log into SQL with sysadmin; create/select MFSQL database (e.g.,
MFSQL_<VaultName>
)Complete the installation
Warning
Do not install MFSQL Connector into the M‑Files SQL database. Always use a separate database.
- Configure connectivity (post‑install)
In M‑Files Admin > Configurations > MFSQL Connector Vault App, set server, instance/port, database, and credentials
If required, set Web API only when using cross‑domain or cloud
- Confirm network access
From M‑Files Server, verify connectivity to SQL instance and port
- Post-install tasks
License the product: License management (Post-Install)
Configure context menu if needed: Configure the context menu
Validate¶
M‑Files Admin: VAF app present; dashboard loads
SQL: assemblies, tables, and procedures present
Troubleshooting¶
Connection string issues: verify instance name and port; SQL mixed auth enabled