RightFax system requirements
and prerequisites

Core infrastructure checklist

• Confirm the target RightFax version first, because supported operating systems, SQL versions, and upgrade paths depend on the exact release you intend to run.
• Validate the Windows Server version and patch baseline for the target deployment.
• Confirm SQL Server compatibility, ownership, backup expectations, and connectivity requirements before install or migration work starts.
• Identify whether the deployment is single server, multiple server, high availability, or part of a broader migration sequence.
• Document hostname, DNS, firewall, certificate, and service account dependencies before production scheduling.

Minimum and recommended specifications by version

Exact requirements are published by OpenText and change from release to release, particularly for supported operating systems and SQL Server versions. The table below reflects current published specifications for the three versions most organizations are either running today or targeting in a near-term upgrade: a legacy release still common in unsupported environments, a widely deployed recent release, and the current release.

Editions (Express, Standard, Enterprise) are supported across each listed SQL Server version. The 50GB recommended disk figure is OpenText's published baseline and excludes stored fax image volume — OpenText's own estimate is roughly 35KB per page, which should be added on top based on expected retention. In practice, higher-volume or multi-channel environments often outgrow the 50GB baseline once conversion temp files, logs, and queued jobs are accounted for; we typically size the application/data disk at 100GB or more for those cases rather than the bare minimum. Because enhancement packs can update these numbers between releases, we verify the current OpenText-published requirements for the client's exact target version before scoping hardware, rather than relying on this or any other secondary reference alone.

Server and platform prerequisites

RightFax planning should assume that the application is only one layer of the environment. The operating system, SQL platform, storage, networking, and security controls all affect whether the implementation will be smooth or unstable.

Minimum and recommended CPU, memory, and disk specifications are published directly by OpenText and vary by RightFax release and by whether SQL Server is co-located on the application server. We confirm the current OpenText-published requirements for your exact target version before scoping hardware or VM sizing, rather than applying generic guidance across versions.

• Validate current OpenText minimum and recommended CPU, RAM, and disk specifications for the target RightFax version before sizing hardware or a VM.
• Size beyond the vendor minimum where fax volume, channel count, integration load, or document retention will exceed baseline assumptions.
• Separate production sizing from lab or staging sizing.
• Confirm whether antivirus exclusions, backup agents, EDR controls, or hardening baselines need special handling for RightFax services and file paths.
• Ensure time synchronization, name resolution, and certificate trust are already correct before application validation begins.

Database readiness

• Determine whether SQL is local or remote and who owns administration, backup, maintenance, and restore testing.
• Confirm collation, authentication approach, permissions, and connectivity requirements before the implementation window.
• For upgrades, define how historical fax data, database growth, and rollback options will be handled.
• For legacy environments, confirm whether intermediate upgrade steps are required before the final target version can be supported.

Fax transport and telephony readiness

• Identify whether the environment uses traditional telephony hardware, SIP-based connectivity, or RightFax Connect.
• Document carrier, channel, DID, routing, and cutover dependencies before migration planning starts.
• Confirm whether legacy boards, drivers, or line services create hidden constraints on the upgrade or migration path.
• Define how inbound and outbound validation will be tested after implementation.

Integration prerequisites

Many RightFax projects are constrained less by the core platform than by the applications attached to it. Print-to-fax, MFP workflows, email integration, EMR or ERP connectivity, and custom delivery routing should all be identified early.

• List all integrations and downstream systems that depend on the existing fax environment.
• Document service accounts, SMTP details, API or connector behavior, shared paths, and certificate requirements.
• Confirm whether non-production testing can replicate the critical workflows before change approval.

Operational prerequisites

• Define the maintenance window, rollback expectations, user communication plan, and validation checklist before the implementation date.
• Ensure the organization knows who signs off on infrastructure, application, database, and telecom dependencies.
• Use a staging or non-production environment when the current version or architecture makes the upgrade path uncertain.

When to escalate planning

A deeper planning exercise is usually justified when the environment is on an end-of-life RightFax version, tied to legacy telephony, dependent on undocumented integrations, or being moved as part of a larger server or cloud transition. Those cases benefit from an assessment before anyone treats the project like a routine in-place upgrade. If the environment is running RightFax 20.2 or earlier, aging telephony hardware, or unsupported infrastructure, see our legacy fax modernization guidance for the broader migration paths available.