If you are installing Triofox Server for the first time, we recommend the All-in-One installation, where you prepare a clean Windows 2012 R2/2016/2019/2022 virtual machine and run the installation with all default parameters. The All-in-One installation is the smallest fully functional setup and can be used for a production environment with < 1000 users.
Step 1: Prepare the file store
The Triofox server connects your local file servers to your remote workers by providing remote and mobile access with synchronization and sharing capabilities. So the first question is: What is your file storage solution?
Your file storage can be a Windows File Server network share or any storage device that supports the CIFS/SMB protocol. It can also be iSCSI devices that you can mount directly as drive letters in the Triofox server. It can also be a container inside a private instance of OpenStack Swift, a bucket in an Amazon S3-compatible storage, or a container from a Windows Azure Blob storage. You need to have the basic access information ready. For example,
Windows File Server
If it is a Windows File Server, you need the UNC path to the network share and the user credentials to access the folder.
If it is a local C: or D: drive, you need a local user credential that has full access rights to the local folder.
If it is OpenStack Swift, you will need the authentication URL and credentials. You also need to know the version of your authentication setup, such as KeyStone V2 or KeyStone V3, or just classic authentication.
If it is Amazon S3, you will need the access key and secret key and a bucket name. If the access key and secret key are from an IAM user, you must ensure that the IAM user has full permission to the bucket.
Windows Azure Blob Storage
You need the "Storage Account Name" and the "Primary Key" as well as a container name.
The initial deployment of Triofox configures the back end storage to use the
C:\Triofoxdirectory on the Triofox server. This default back end storage location can be changed to another location at a later time by modifying the back end storage of the default server.
Step 2: Prepare Active Directory (Optional)
If you are including Active Directory, you will need the following information:
- The DNS name (or IP address) of an Active Directory domain controller.
- A service account that can access Active Directory.
- The DNS name of the Active Directory domain.
If your Active Directory is local, the best practice is to join the Triofox Server machine to the Active Directory Domain first before the installation starts.
If your Active Directory is located remotely with respect to the Triofox server, you should use the Server Agent software to connect the Active Directory instead of using LDAP to connect to the Active Directory.
Step 3: Prepare the Database Server
If you are installing the All-in-One instance, you can skip this step because the All-in-One installer installs a PostgreSQL server and configures the database accordingly. See Step 5: Start Installation below for more about the all-in-one installation. This step is only for installations with a separate database that is not installed by default with a Triofox server in the server farm. All Triofox servers in a server farm share a single central database.
For Triofox, the default database engine for the "all-in-one" installation is PostgreSQL.
There are two places where persistent information is stored. The first place is the file store mentioned in step 1. The second place is the Triofox database. The database contains configuration information such as username, team folder, shared folder, and login token. The database also contains runtime information such as the audit trace and the file change log.
The default installation of Triofox uses a local PostgreSQL database on the Triofox server. We provide this option to make the POC (Proof of Concent) test installation as easy as possible.
Currently, Triofox supports PostgreSQL, MySQL or Microsoft SQL Server (DBMS) database management systems. Some good reasons for using an external database server are performance, scalability and high availability.
Microsoft SQL Server
If you are using an external Microsoft SQL Server instead of the default PostgreSQL All-in-One deployment, you must ensure that SQL Server authentication is configured for Mixed Mode Authentication. The Triofox Server connection requires the use of a SQL account, not a Windows built-in authentication account.
During the setup of the first Triofox Server in the server farm (the server farm can be so small that it contains only one Triofox Server), the installer needs to create a database, create tables in the database, and create stored procedures in the database. Therefore, a SQL security account with sufficient rights is required for the installation.
If the database server is located outside the Triofox server, make sure that the TCP protocol is enabled and the firewall is open for SQL connections. The default TCP port is 1433 and this port must be open in the firewall. If your SQL server listens for incoming connections through another port, this port must also be open instead of the default TCP port.
MySQL typically listens on TCP port 3306. Make sure this port is opened on the firewall.
The default TCP port for PostgreSQL is usually 5432, however this can easily be changed in the postgresql.
Step 4: Prepare the Triofox Server
The easiest way to prepare the Triofox server is to use a clean Windows Server 2012/R2/2016/2019/2022 OS with English locale. If you want to use multiple Triofox servers to form a server farm, please make sure that the servers in the server farm are all in the same time zone.
The Triofox server provides localization support for multiple languages, regardless of the fact that the base Windows OS works with the English locale.
We recommend Windows Server 2019 or Windows Server 2016 as the preferred server OS, running on a virtual machine.
Supported Operating Systems
- Windows Server 2008 R2 with latest updates
- Windows Server 2012
- Windows Server 2012 R2
- Windows Server 2016
- Windows Server 2019
- Windows Server 2022
- 64-bit Intel or AMD x64 architecture
- 2 - virtual CPUs minimum (4 - virtual CPUs or more are recommended)
8GB RAM minimum (16 GB or more is preferred)
Hard Disk Space
100 GB minimum, preferably SSD. This assumes back end file storage is not located on the Triofox server itself.
EC2 Server Type
If you are installing Triofox in Amazon Web Service (AWS), here is the minimum AWS EC2 instance types we recommend for production use.
- t2.xlarge (general purpose, 4 vCPU, 16 GB)
- t3.xlarge (general purpose, 4 vCPU, 16 GB)
Please check the AWS EC2 Instance Types for more information.
Azure Virtual Machine Size Recommendation
If you are installing Triofox in Microsoft Windows Azure, here is the minimum Azure Virtual Machine size we recommend for production use.
- D4a V4 (4 vCPU 16GB)
- D4as V4 (4 vCPU 16GB)
- D4d V4 (4 vCPU 16GB)
- D4ds V4 (4 vCPU 16GB)
- D4 v4 (4 vCPU 16GB)
Step 5: Start Installation
You can get the Triofox installation package from the Triofox customer portal (by login to http://www.triofox.com) and get to the Private Triofox section.
Log in to the Triofox server console (RDP or physical console are fine) with administrator privileges. Once you click on the "Download" button in the customer portal, the installer will appear either in the Downloads section or as a link at the bottom of your browser. Click the executable file to start the installation.
You will see the welcome screen.
And accept the EULA and click Next.
Select the path you wish to install Triofox to.
Then click Install.
Triofox will install and then you will need to restart your system to complete the installation.
After the installation, the server will need a reboot, a web browser will pop up for the initial configuration.