AdemeroHelp

Content Central system requirements

Hardware sizing, the Windows, IIS, .NET and SQL Server versions the server needs, what setup installs for you, the ports to open, what the QuickBooks Desktop integration adds, and the built-in health page that keeps checking your environment.

AdministratorsContent Central 7.x6 minute readVerified 2026-10-07

Everything a server needs to run Content Central: hardware sizing, software versions, what setup installs for you, the network rules, and the extra pieces the QuickBooks Desktop integration needs. Hand this page to whoever builds or looks after your server.

Server hardware

MinimumRecommended
Processor8 cores16 cores
Memory8 GB16 GB, ideally 32 GB
Storage250 GB, redundant500 GB or more, redundant SSD

These are starting points. Document volume, how many people search at once, and how much scanning and OCR you run all push the numbers up, so size for where you'll be in a few years, not where you are today. Virtual machines are fine. On your own hardware, aim for the full 32 GB of memory; on a cloud server, 16 GB is a workable floor that keeps hosting costs reasonable.

Note

Keep at least a few GB free on the system drive and the document storage drive at all times. Documents, search indexes and temporary files all fail to save on a full disk.

Server software

RequirementDetail
Windows Server, 64-bitWindows Server 2019 or later. Windows Server 2022 is recommended
IIS (Internet Information Services)Content Central is an IIS web application. Setup turns on the IIS features it needs, as long as you run setup.exe rather than the MSI file directly
.NET Framework 4.8 or laterSetup installs it when missing
SQL ServerSQL Server 2012 or later; SQL Server 2022 or later is recommended. Use your own instance, or let setup install its bundled SQL Server Express as a dedicated instance: SQL Server 2025 Express from Content Central 7.8.10186, SQL Server 2022 Express in earlier versions
Application poolSetup creates and configures Content Central's application pool. Leave its settings as installed, especially Enable 32-Bit Applications
Note

SQL Server Express limits each database's size: 50 GB on SQL Server 2025 Express, 10 GB on earlier versions. That's a fine starting point; growing installations move to a full SQL Server edition, and the server move guide covers that path when the day comes.

What setup installs for you

Run setup.exe and it brings along everything else Content Central depends on: the IIS features, .NET Framework 4.8, the Microsoft Visual C++ runtimes, the optional SQL Server Express instance, and Content Central's own Windows services. There's nothing else to download first, with one exception: the QuickBooks Desktop pieces described below.

Network

DirectionWhatWhy
InboundTCP 443 (HTTPS), or 80 if you haven't set up HTTPS yetHow people reach Content Central in their browsers. See Serve Content Central over HTTPS
OutboundHTTPS (443) to AdemeroContent Central checks its license online
OutboundSMTP to your mail serverNotification emails, on the server and port you configure
OutboundYour SQL Server's port (usually 1433)Only when SQL Server runs on a different machine

Content Central's Windows services don't listen on any network ports of their own. Everything else they use stays on the server itself.

Client workstations

  • A current web browser: Microsoft Edge, Google Chrome or Mozilla Firefox, on Windows or macOS. Content Central is browser-based, so there's nothing to install for everyday use.
  • DirectScan Agent (only for scanning workstations): Windows with .NET Framework 4.8. The installer on your server's Downloads page carries its one prerequisite along.
  • Office add-in (optional): installers for 64-bit and 32-bit Microsoft Office are on the Downloads page. Microsoft 365 organizations can deploy the web add-in centrally instead; see Set up the Office add-in.

If you export to QuickBooks Desktop

The QuickBooks Desktop integration talks to QuickBooks directly on the Content Central server, so that server needs a few things a plain install doesn't:

  • QuickBooks Desktop installed on the Content Central server, the same year and edition your company files use.
  • The QuickBooks SDK (QBFC 16) from Intuit, installed on the same server. Setup does not install it.
  • A Windows account for the Content Central Integration Service that can open your company files. Run the service under this account, not the default system account, and authorize Content Central in QuickBooks while signed in as that same account.
  • A dedicated QuickBooks user for Content Central, so its activity is easy to tell apart in QuickBooks' audit trail.
  • Access allowed even when QuickBooks isn't running. When QuickBooks asks whether to let Content Central into a company file, choose Yes, always; allow access even if QuickBooks is not running.
  • Keep QuickBooks running for quick startups turned off (Edit > Preferences > General) on the Content Central server, so a copy of QuickBooks left running after someone closes it doesn't block the integration.
  • Company files opened in multi-user mode, if people also work in them while Content Central exports.
  • UNC paths (\\server\share\Company.qbw), not mapped drive letters, for company files on another server. The service account needs read and write access to that share, and the file server must allow the ports shown on the Port Monitor tab of QuickBooks Database Server Manager.
Important

If your QuickBooks files or Content Central move to a new server, every item on this list has to be redone on the new server. Plan it into the move and test one export before switching over.

Taking over an existing server

If you're a new IT provider inheriting a Content Central server, or you're moving one, start with What to know before moving Content Central to a new server. The short version:

  • Keep the folder paths. Document, index and work folder locations are stored in the database, so a move goes smoothest when every path stays the same.
  • Keep the permissions. The Content Central services and the IIS application pool must be able to write to every storage folder. Some copy tools drop folder permissions, so check them after any copy.
  • Keep any inbound rules your capture services rely on. If your documents arrive from an outside service, its allow-list rules must move with the server.
  • Talk to Ademero support before the move, so the license and any integrations carry over cleanly.

The environment checks itself (7.8 and later)

Administration > System Health runs fourteen environment checks: database connection and version, document and index storage, working folders, application pool architecture and mode, single sign-on configuration, licensing, and disk space. Each one gives a plain verdict and a Suggested next step when something needs attention.

Make it your first stop after any server change (Windows updates, SQL moves, IIS edits). If the environment has drifted from what Content Central needs, this page says so before your users do.

Success check for a new server: System Health shows Environment checks passed across the board. Anything else names its fix.

Need help sizing a server?

Requirements change between releases. Before you buy or build hardware, contact Ademero support with your Content Central version, roughly how many documents you store and add each month, how many people use it, and which integrations you run, and we'll confirm the right setup.