System Requirements

Before installing OptimiDoc Server, verify that the target environment meets or exceeds every requirement listed on this page. Running the application on an under-specified server may result in degraded performance, failed installations or unsupported behaviour.

How OptimiDoc Is Deployed

Understanding the moving parts helps you size the host correctly:

• Web application — the administration UI and REST API, hosted in IIS as an ASP.NET application targeting .NET Framework 4.8. This is where the React interface, the legacy MVC interface and all device communication live.

• OptimiDoc Windows Service — a background service that performs delivery, scan processing, accounting, scheduled reports and device monitoring independently of web requests.

• Database — SQL Server (or LocalDB for small installations) stores users, devices, jobs, rules and configuration. A separate quota database is used when quotas are enabled.

• Print nodes (OPN, optional) — lightweight satellite components that receive and hold print jobs close to the users or devices, useful for branch offices and large or geographically distributed estates.

For a small pilot, every part runs comfortably on one server. Larger estates benefit from a dedicated SQL Server and, where appropriate, additional print nodes and cluster members.

Operating System

OptimiDoc Server runs on the following Windows editions:

A 64-bit operating system is required in all cases.

Web Server

OptimiDoc requires Internet Information Services (IIS) 10 or later with the following role services enabled:

• ASP.NET 4.8

• ISAPI Extensions

• ISAPI Filters

• Static Content

• Default Document

• WebSocket Protocol (optional, for real-time dashboard updates)

Runtime Prerequisites

The web application targets .NET Framework 4.8 (both its runtime and compilation model), which is what enables the modern asynchronous request handling used throughout the API. The OptimiDoc installer checks for these prerequisites and offers to install them automatically if they are missing.

Database

OptimiDoc supports the following database engines:

For production environments with more than 20 devices, SQL Server Standard or Enterprise is recommended. LocalDB is convenient for evaluation but does not support remote connections or clustering, so it cannot be used in a failover cluster. You can start on LocalDB and later move to a full SQL Server — see LocalDB to SQL Server.

Hardware

Disk usage grows with the volume of stored print and scan jobs. Configure job-retention periods under Settings > Print to manage storage consumption. Large deployments (hundreds of devices) should scale CPU and RAM above the recommended figures and place the database on dedicated storage.

Network Ports

Ensure that the Windows Firewall and any network firewalls permit traffic on the ports above. In a clustered or multi-node deployment, cluster members and print nodes must also be able to reach one another and the shared database.

Supported Browsers

The OptimiDoc web administration UI is tested and supported on the latest stable releases of:

• Google Chrome

• Microsoft Edge (Chromium-based)

• Mozilla Firefox

Internet Explorer is not supported.

Related Articles

• Installation

• Licence Activation

• Getting Started