On‑premises: single server

At a glance

• Who: on‑prem deployments with M‑Files Server and SQL Server on the same machine

• Outcome: VAF installed, database created, content package imported, assemblies in place

Also read: Common installation notes

Prerequisites

• See Planning and prerequisites

• M‑Files Server and SQL Server installed on the same Windows Server

• M‑Files Desktop enabled on the server

• Installer user has M‑Files System Admin (temporary) and SQL sysadmin

• Network: not applicable (local), unless non‑default SQL ports

Steps

1. Confirm license agreement

   • Proceed after reading the terms

2. Select installation folder

   • Use defaults for fewer manual steps later

   • The folder will contain vault- and database-specific install files

3. Select installation mode and options

   • Single server scenario: select Both (M‑Files and SQL on this server)

   • Other options (cloud, workstation-only) have separate guides

4. Log into M‑Files

   • Select the target vault and authenticate with the MFSQL Connector user (Vault Admin)

   • Credentials are stored locally for subsequent runs

   • If the login button is unresponsive, delete: C:\Users\<user>\AppData\Local\MFSQL Vault Install

   • If prompted, re-enter credentials in the confirmation window (protocol/endpoint as required)

5. Log into SQL Server

   • Use a sysadmin account

   • Server name must include Instance (and Port if non‑default)

   • Create or select the MFSQL Connector database (recommended: MFSQL_<VaultName>)

   • The installer creates the database if it does not exist

Warning

Do not install MFSQL Connector into the M‑Files SQL database. Always use a separate database with a distinct naming convention.

6. Installing

   • The installer runs SQL and vault steps; you may be prompted to bring the vault offline/online

   • Installer steps: use images from Package installation - step by step

7. Validate SQL installation and vault connection

   • If the SQL-only validation window appears, confirm no errors are reported

8. Finish

   • If no errors are found, finish the installation

9. Post-install

   • Take the vault offline and back online once (if not already done)

   • License the product: License management (Post-Install)

   • Configure connection string/Web API (if needed): Connection and Web API

   • Configure context menu (optional): Configure the context menu

   • See also manual install notes: Manual installation path

Validate

• SQL: database exists, key tables present, assemblies loaded

• M‑Files Admin: VAF app installed, license status visible (unlicensed until added)

• See Validate and smoke tests

Troubleshooting

• If M‑Files login step is unresponsive, remove the local history folder and retry

• If assemblies don’t load, see HA notes or contact support