2.2.2. Team Requirements
2.2.2.1. Team Account Requirements
The server will run as a Windows service. You need to have a service account during installation.
The requiremnts are:
A real Windows user account, local or domain. Built-in service accounts are rejected: LocalSystem, NetworkService, LocalService.
A non-empty password. The service registration explicitly refuses an empty one rather than creating a service that would fail at first start with error 1069.
The account must be able to log on right now and cannot be disabled, locked out, password expired, password-must-change, logon-hour restrictions, or have workstation restrictions.
If evidence lives on a UNC share — i.e. you enable Options → Deployment Mode → “Allow clients to add a data source that is accessible to the server” with a \servershare... root, the service account must be a domain account with read access to that share. A local account cannot authenticate to a remote share.
NOTE: if the account did not have the “Log on as a service” right (SeServiceLogonRight), the installer will grant it automatically.
The account does NOT need:
Local Administrator permissions
Interactive or Remote Desktop logon rights
Strong Recommendations:
Use a dedicated service account, not a person’s account. When that person leaves and their account is disabled, the server stops starting.
Use an account whose password does not expire. This is the single most common cause of a server that worked for 90 days and then didn’t. If the password does change, the service will not start until the new password is entered in services.msc → the service’s properties → Log On tab.
NOTE: PostgreSQL will use the Network Service account.
2.2.2.2. Team Software Requirements
- Cyber Triage Server Installer.
You will get a release link for this via email or contact support.
As of v4.0, there is a dedicated installer for Server.
It will have a name such as CyberTriage_Server_Setup-4.0.0.exe.
- A PostgreSQL installer (details are provided later).
NOTE: You can use SQLite for a quick evaluation
2.2.2.3. Team Hardware Requirements
The server requirements depend on if you are running the Server and PostgreSQL on the same system.
2.2.2.3.1. Team Server and PostgreSQL On The Same Host
OS: 64-bit version of Windows Server
RAM: 32GB+
CPU Cores: 8+
Free HD Space (SSD Recommended): 750GB+
2.2.2.3.2. Team Server and PostgreSQL on DIFFERENT Hosts
Team Server:
OS: 64-bit version of Windows Server
RAM: 16GB+
CPU Cores: 4+
Free HD Space (SSD Recommended): 500GB+
PostgreSQL Server
OS: Either Linux or Windows Server
RAM: 16GB+
CPU cores: 4+
Free HD Space (SSD Recommended): 250GB+
2.2.2.3.3. Team Thick Clients
If you are going to need to install a thick client (instead of using a web browser), then we recommend:
OS: 64-bit version of Windows 7 or newer
RAM: 12GB+
CPU Cores: 4+
Free HD Space (SSD Recommended): 50GB+
Display of at least 1366×768