Skip to main content
Use this when you need to:
  • Hand a customer or partner a single document covering everything required before a deployment or demo call.
  • Confirm infrastructure readiness (VM, OS, .NET Framework, IIS, ports, database) without walking through every detailed sub-guide individually.
  • Give a pre-sales or solutions engineer a fast way to confirm “yes, this environment is ready” before the technical portion of a call begins.
For the detailed step-by-step version of each item below, follow the linked guide. For what to do after installation (users, alerts, first session), see the Getting Started Checklist instead.

Before you start

1

Decide on-premises or SaaS

On-premises gives you full infrastructure control and is what the rest of this checklist covers. SaaS skips most infrastructure steps below — Syteca hosts the Application Server and database for you.
2

Size the deployment

Review deployment sizing — PoC, Small, Medium, or Large — based on expected concurrent sessions. This determines the hardware specs used in the rest of this checklist.
3

Confirm hardware and OS

Confirm the planned Application Server, Management Tool, and database machines meet the system requirements for your chosen size — vCPU, RAM, storage, and supported Windows Server version.
4

Confirm network ports

Review network port requirements and confirm your network team can open them between the Application Server, Management Tool, database, and Clients.
5

Have a serial key ready

Confirm you have a valid Syteca serial key (or know how to request a trial one) before starting installation.

Stage 1: Prepare the infrastructure

1

Provision the virtual machine(s)

Provision the Application Server VM (and a separate Management Tool VM, if not co-locating them) matching the specs confirmed above. A separate database server VM is optional — MS SQL Server or PostgreSQL can run on the same machine for smaller deployments.
2

Turn on IIS

Turn on Internet Information Services on the Management Tool machine — the exact steps depend on your Windows version.
3

Install .NET Framework

Install .NET Framework (version 4.8) on the Management Tool machine.
4

Configure IIS

Configure IIS with the required modules and application pool settings.
5

Provide an SSL certificate

Either generate a self-signed certificate (and add it to Trusted Root) or import a purchased one — required for HTTPS access to the Management Tool.
6

Bind HTTPS

Bind HTTPS on the default website using the certificate from the previous step.
7

Prepare the database

Confirm MS SQL Server or PostgreSQL is installed and reachable. If your organization requires DBA-managed database creation instead of letting the Application Server installer create it, see Creating databases manually.

Stage 2: Install the core platform

1

Install the Application Server

Run the Application Server installer, connecting it to the database prepared in Stage 1.
2

Install the Management Tool

Run the Management Tool installer on the machine prepared in Stage 1.
3

Activate the serial key

Activate your serial key — online or offline, depending on whether the Application Server has internet access.
4

Sign in and set a password

Sign in to the Management Tool as the default admin, set a new password when prompted, and (recommended) configure two-factor authentication.
For a High Availability deployment with multiple Application Server nodes instead of a single instance, see High Availability and Load Balancing installation — these replace Stage 2 with a multi-node variant of the same steps.

Stage 3: Prepare endpoints and install Clients

1

Check Windows Client prerequisites

Review Windows Client installation prerequisites — required Windows system services, firewall rules, and permissions on target endpoints.
2

Choose an installation method

Windows Clients can be installed remotely via the Management Tool, via Group Policy, or locally using an installation package — pick whichever matches your environment (domain-joined vs. workgroup, remote access vs. imaging pipeline).
3

Install Clients on target endpoints

Install Windows, macOS, or Linux Clients on the endpoints to be monitored, using the method chosen above.
4

Confirm Clients are reporting

Confirm installed Clients appear online on the Clients page in the Management Tool, and that a test session records correctly.

You’re ready for the technical call

At this point, the infrastructure is provisioned, the platform is installed and licensed, and at least one Client is confirmed reporting data. From here, the conversation can move to configuring monitoring behavior, alerts, and reports — the parts of Syteca that are actually differentiated, rather than infrastructure setup.

Getting Started Checklist

What to configure next — licenses, Client groups, alerts, and reports.

System architecture

A one-page mental model of how the components fit together.

Client Troubleshooting

If a Client isn’t showing up or isn’t recording, start here.

Installation Checklist

The detailed, IT-facing version of Stages 1–2 above.