📌 Supported versions: FCE 3.1 is the only version supported for new installations and installs directly onto your host (no virtual machine required). Existing FCE 3.0 (OVA) deployments remain supported and can be upgraded to 3.1; the 3.0 OVA will not be updated after the 3.1 release. See FileConnect Enterprise: Supported Versions.
FileConnect Enterprise v3.1 (FCE 3.1) installs directly onto a supported host operating system — no virtual machine or hypervisor is required. This document outlines the hardware, software, and network requirements necessary to successfully install and operate FCE 3.1
1. Hardware HostingÂ
FCE 3.1 runs directly on the host operating system. The host must provide adequate resources for the FCE application, Diskover, and a single-node Elasticsearch instance (or connect to an external Elasticsearch cluster for scaled deployments).
Minimum Host Requirements
| Component | Requirement |
|---|---|
| Processor (CPU) | x86-compatible processor with virtualization support (Intel VT-x or AMD-V) |
| Memory (RAM) | Minimum 32 GB (additional memory recommended for larger datasets) |
| Storage | Minimum 200 GB per TB of managed data (SSD recommended) |
| Network Interface | 1 Gbps or faster Ethernet interface |
Â
2. Supported Operating Systems (Host OS)
The following operating systems are supported for hosting the hypervisor and FCEv3 virtual machine.
CentOS
Supported Versions: 9 and 10
Red Hat Enterprise Linux (RHEL)
Supported Versions: 9 and 10
Must be a vendor-supported release of RHEL.
3.Host Resource Requirements
FCE 3.1 installs directly onto the host operating system — there is no guest virtual machine to size separately. Provision the host with at least the following, in addition to the resources needed by any other workloads it runs:
Â
| Component | Requirement |
| vCPU / CPU cores | 4 (minimum) |
| Memory (RAM) | 32 GB (more recommended for larger datasets) |
| Disk space | ≥200 GB per TB of managed data (SSD recommended) |
| Operating system | RHEL 9 or 10, or CentOS 9 or 10 |
For larger or scaled deployments, an external 2–3 node Elasticsearch cluster is recommended — contact RecordPoint for the FCE Advanced Deployment guide.
4. Legacy FCE 3.0 (OVA)
4a.Hypervisor Requirements
The hypervisor is responsible for running the FCEv3 virtual machine on the host OS.
Supported Hypervisors
VMware
Any VMware product capable of running x86-based virtual machines.
-
Examples:
VMware Workstation Pro
VMware ESXi
VMware vSphere
For installation and configuration details, refer to Broadcom’s official documentation: VMware by Broadcom – Cloud Computing for the Enterprise.
Oracle VirtualBox
Fully supported for FCEv3.
-
For installation and configuration details, see Oracle’s official documentation: VirtualBox Official Documentation.
Â
4b.Virtual Machine (Guest) Specifications
The FileConnect Enterprise v3 virtual machine is built on CentOS Stream 9 (x86 architecture).
Minimum Configuration
| Component | Requirement |
|---|---|
| vCPU | 4 |
| Memory | 32 GB |
| Disk Space | >200 GB per TB of managed data |
| Operating System | CentOS Stream 9 |
Â
Â
Network Requirements
The FCE virtual machine must be connected to all file shares and volumes it is intended to manage.
Required Network Access
The FCE virtual machine must have access to all relevant storage systems, file shares, and volumes.
Port Access
The following ports must be accessible for users and services outside of the VM:
| Port | Service | Description |
|---|---|---|
| 8000 | Diskover | Data indexing and analytics |
| 8080 | FCE Management UI | Web-based management interface |
| 9090 | FCE API | API access for integrations |
| 5601 | Kibana | Dashboard and reporting interface (if enabled) |
Note: For more detailed network and security configuration, refer to Security Hardening FCEv3 | Network Requirements.
Â
6. External Site Access
The FCE virtual machine requires external network access to several services for licensing, telemetry, and integration.
Required External Endpoints
| Service | Endpoint |
|---|---|
| Records365 Connector (Regional) | e.g., connector-usw.records365.com (for U.S. region) |
| LaunchDarkly (Feature Flags) |
app.launchdarkly.com, stream.launchdarkly.com, sdk.launchdarkly.com
|
| Microsoft Application Insights |
dc.applicationinsights.azure.com, dc.applicationinsights.microsoft.com, dc.services.visualstudio.com
|
| Microsoft Authentication | login.microsoftonline.com |
| Binary Submissions | *.windows.net |