Skip to main content
This guide walks new Syteca SaaS customers through the first hour after receiving their license. The steps differ slightly from on-premises deployments — SaaS enforces stricter login security (mandatory password change, mandatory 2FA) and some features are vendor-managed rather than admin-configurable. For the post-install task sequence (assigning licenses, adding Client groups, configuring monitoring, etc.), continue to the Getting Started checklist afterwards.
Conventions used throughout this documentation:

​
What you receive from your vendor

After your SaaS product license serial key is issued, your Syteca vendor emails you:
  • A URL for the Management Tool — in the form <Customer_name>.syteca.com.
  • The admin account credentials (login + initial password).
The SaaS serial key type is currently subscription-only.

​
1. Log in for the first time

Syteca SaaS mandatory password change screen showing two password fields with complexity requirements listed beneath

The mandatory password change screen — every SaaS user is forced through this on first sign-in, with the complexity requirements visible inline.

1

Open the Management Tool

Enter the URL provided by your vendor into your browser. The Management Tool login screen opens.
2

Enter the admin credentials

Sign in with your login and the initial password your vendor provided.
3

Change your password (mandatory)

SaaS forces every user to change their password on first sign-in. Enter a new password in both fields and submit.
Password requirements: at least 8 characters, containing at least one lowercase letter, one uppercase letter, one numeric character, and one special character. Cannot contain more than 3 consecutive identical characters.
4

Sign in again with the new password

The system signs you out — sign back in with the password you just set.
5

Set up two-factor authentication (mandatory)

A QR code appears. Scan it with an authenticator app on your phone (Google Authenticator, Microsoft Authenticator, or any TOTP-compatible app).
Save the recovery code displayed alongside the QR code. It’s the only way to regain access if you lose your authenticator device. Store it somewhere safe and not on the same device as the authenticator.
IN SAAS ONLY: 2FA setup is mandatory on first sign-in for every user, every login afterwards uses 2FA, and this requirement can’t be disabled — unlike in on-premises deployments where 2FA is configurable per user on the Users page.
6

Confirm 2FA

Click Confirm, then enter the 6-digit code generated by your authenticator app. You’re now signed in.

​
2. View your serial key and Client licenses

1

Open Configuration

Click the Configuration (gear) icon at the top of the Management Tool.
2

Open the Serial Key Management tab

On the Configuration page, select the Serial Key Management tab. Your serial key details — the activated SaaS key, included Client licenses, expiration date — are displayed.
IN SAAS ONLY: Your serial key is already activated by your vendor — no user action required to activate it. However, if your vendor updates the existing serial key, you need to click Update Serial Key on the Serial Key Management tab for the changes to take effect.
You’ll receive expiration notifications 14 days, 5 days, and 1 day before the serial key expires. If the key isn’t renewed by 7 days after expiration, monitoring stops — Clients will no longer be able to send data. Track the renewal date and coordinate with your vendor well ahead.
For full serial key details (licensed Client counts, included applications, license types), see View the serial key and licenses.

​
3. Install Clients on endpoint computers

Clients are downloaded from the Management Tool and installed on each endpoint computer (Windows, macOS, or Linux) to be monitored.
1

Sign in with Client Installation permission

Sign in as a user with the administrative Client Installation and Management permission.
2

Open the Install Clients page

Click Clients in the left navigation. On the Client Management tab, click Install Clients in the top right.On the Computers without Clients page, click Download Installation File.
3

Download the installation file for your OS

On the Installation File Download page, pick your OS in the drop-down and download the file:
4

Install the Client on each endpoint

Copy SytecaClient.msi (or the .zip for custom parameters) to each Windows endpoint, then install with one of:
  • Windows Installer (GUI): double-click SytecaClient.msi and follow the Setup Wizard.
  • Command line: open cmd or PowerShell as administrator, navigate to the folder containing the file, and run:
  • Custom parameters: use SytecaClient.zip and follow Install Windows Clients locally with custom monitoring parameters.
Network ports required:
  • Port 443 — open for Windows, macOS, and Linux Clients.
  • Port 9447 — also open for Windows Clients.
See Network Requirements for full network specifications.
5

Confirm monitoring is active

Once installed, the Client appears in the Clients list. Monitoring starts as soon as any user logs in to the endpoint.

​
4. Continue with the post-install checklist

Now that the platform is reachable and Clients are installed, work through the Getting Started checklist — assigning licenses, adding Client groups, defining monitoring configuration, creating PAM secrets, and configuring alerts and reports. In SaaS, features marked NOT AVAILABLE IN SAAS in this Knowledge Base are either vendor-configured on request or on-prem-only. Features marked IN SAAS ONLY behave differently from on-premises — the page where each label appears explains the variant.

Getting Started checklist

The post-install task sequence — licenses, Client groups, monitoring, PAM, alerts, reports.

Management Tool basics

Sign-in patterns, navigation, default brute-force lockout behavior.

Users and permissions

Add users, define groups, grant administrative and Client permissions.

Getting started with PAM

Configure Password Management for your SaaS deployment.