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

Also read: Common installation notes

Prerequisites

• See Planning and 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

1. 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

2. 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.

3. 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

4. Confirm network access

   • From M‑Files Server, verify connectivity to SQL instance and port

5. Post-install tasks

   • License the product: License management

   • Configure context menu if needed: Configure the context menu

Validate

• M‑Files Admin: VAF app present; dashboard loads

• SQL: assemblies, tables, and procedures present

• See Validate and smoke tests

Troubleshooting

• Connection string issues: verify instance name and port; SQL mixed auth enabled

Re-useable screenshots (optional)

• Installer screens: reuse from On Premise Installation

• M‑Files Configurations dashboard and connection string fields: reuse from context menu configuration page