---
title: "V4 ⬝ 2.0 12d Synergy File Replication Server Requirements"
slug: "v412dsynergyfilereplicationserverrequirements"
tags: ["server", "version4", "file", "frs", "requirements", "replication", "12dsynergy", "v4"]
updated: 2023-09-27T01:03:31Z
published: 2023-09-27T01:03:31Z
excludeFromSearch: true
---

> ## Documentation Index
> Fetch the complete documentation index at: https://help.12dsynergy.com/llms.txt
> Use this file to discover all available pages before exploring further.

# 12d Synergy File Replication Server Requirements

## **1.1 Communication**

The File Replication Server communicates using TCP/IP (encrypted with SSL/TLS), over the default port 1212. This includes communication between the FRS and:

- The Master Server
- Other File Replication Servers
- Any Clients using the FRS

The installed port should be opened in any relevant software firewalls, hardware firewalls, or routers, where appropriate/

## **1.2 Hardware Requirements**

| CPU | Intel i5 or AMD equivalent processor, 2 GHz or Higher (Minimum) Intel Xeon E7 or AMD equivalent processor, 3 GHz or Higher (Recommended) |
| --- | --- |
| RAM | 8 GB minimum, 16 GB recommended |
| HDD | 5.0 GB for installation |

## **1.3 Software Requirements**

### 1.3.1. Operating System

Windows 7 or Later, or Server 2008 SP2 or later.

12d Synergy is installed as a 32bit application

### 1.3.2. Required Components

The following software components are required:

- Microsoft .NET 4.6.1
- Microsoft SQL Server
  - Minimum version: SQL Server 2012
  - Recommended version: SQL Server 2014 or later
  - Full Text Search must be enabled

### 1.3.3. SQL Server

It is acceptable to use the SQL Server Express edition for an FRS installation, however Standard is generally recommended if it is available.

## **1.4. Data Storage**

You will need storage space available for the amount of data you expect 12d Synergy to be managing. You should take into account growth of this data set over time.

## **1.5. Service Account**

The 12d Synergy File Replication Server will run under a service account which:

- Can connect to the SQL Server and create a database and temporary tables
- Have full access to the aforementioned data storage areas