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

# Installation Checklist

> The 10-step deployment sequence for installing Syteca on-premises: IIS setup on the Management Tool host, Application Server install, Management Tool install, serial key activation, multi-tenant setup, and Client installation for Windows, macOS, and Linux.

The 10-step sequence below deploys a working Syteca on-premises installation from scratch, starting with configuring the Management Tool host and finishing with Client installation on Windows, macOS, and Linux endpoints. Each step points to the detailed page for that action.

<Warning>
  **NOT AVAILABLE IN SAAS.** SaaS deployments do not require this checklist. The Syteca vendor manages the Application Server, Management Tool, database, and IIS infrastructure. SaaS customers only install Clients on their endpoints.
</Warning>

<Note>
  This is the technical deployment checklist. For onboarding after Syteca is installed and running (initial configuration, first users, first alerts), see the [Getting Started Checklist](/docs/get-started/checklist) instead.
</Note>

## 1. Configure the Management Tool host

Before installing the Management Tool, configure the Windows Server that will host it.

1. [Turn on Internet Information Services (IIS)](/docs/administration/deployment/management-tool-prerequisites#1-turn-on-iis) on the Management Tool host computer.
2. Install [.NET Framework 4.8](https://dotnet.microsoft.com/download/dotnet-framework/thank-you/net48-offline-installer) from the Microsoft site. Administrator permissions are required and the computer must be restarted after installation.
3. [Configure IIS](/docs/administration/deployment/management-tool-prerequisites#3-configure-iis) for Syteca (default site, application pools, features).
4. Generate a self-signed certificate, or import a trusted certificate. On Windows Server 2019 Core, use PowerShell commands for both certificate generation and IIS binding setup.
5. Export the self-signed certificate and add it to the Trusted Root Certification Authorities store.
6. Set up an HTTPS binding for the default website.

## 2. Install the Application Server

The [Application Server](/docs/administration/deployment/install-application-server) stores and processes all records sent to it by Clients on monitored endpoints. Install it on a dedicated Windows Server machine.

Sub-steps before running the Application Server installer:

1. Install PostgreSQL 10 or higher, if PostgreSQL will be the database. Alternatively, install MS SQL Server 2012, 2014, 2016, 2017, or 2019 (Standard license or higher) for MS SQL.
2. Install the Universal C Runtime and Visual C++ Runtime Redistributable Packages (v5.5 or higher) via the Microsoft Visual C++ 2015 Redistributable.
3. If the Application Server is on a different computer from the Management Tool, install .NET 8.0 (.NET Runtime 8.0 and ASP.NET Core 8.0 Runtime) for Syteca 7.23 or higher. For versions before 7.23, install .NET Framework 4.8 instead.
4. During installation, select the database type and set the administrator password used to log in to the Management Tool.
5. Define the location for binary data (screen captures).
6. After installation, [add the Application Server executable to the Windows Firewall exception list](/docs/administration/deployment/windows-firewall-configuration) if the firewall was off during installation.

For High Availability with multiple Application Server instances in a Microsoft failover cluster, see [Shared Storage High Availability](/docs/administration/deployment/shared-storage-ha).

## 3. Install the Management Tool

The [Management Tool](/docs/administration/deployment/install-management-tool) is the web-based interface for managing users, Clients, alerts, and the database. It requires connectivity to the Application Server.

If the Management Tool will be accessed from other computers, [configure the firewall to allow remote access](/docs/administration/deployment/install-management-tool#allow-remote-access-through-the-firewall) to the Management Tool.

## 4. Activate the serial key

[Activate a new serial key online](/docs/administration/licensing/activate-serial-key#online-activation) or [add an activated serial key offline](/docs/administration/licensing/activate-serial-key#offline-activation). Without an activated serial key, no Client data can be received and PAM features cannot be used.

## 5. Enable Multi-Tenant mode (optional)

If your deployment needs isolated tenants for separate customer or department data, [enable Multi-Tenant mode](/docs/administration/multi-tenant/overview), add tenants, and grant them licenses.

## 6. Configure target computers for remote Client installation

If Windows Clients will be installed remotely from the Management Tool, prepare each target computer:

1. Make sure shared folders are accessible on the remote computer. For workgroup computers, disable the Sharing Wizard.
2. [Verify the Server and Remote Procedure Call (RPC) services are running](/docs/administration/clients/windows-install-prerequisites) on the target computer.
3. [Configure the firewall](/docs/administration/deployment/windows-firewall-configuration) on the target computer for remote Client installation.

## 7. Install Windows Clients

[Install Windows Clients](/docs/administration/clients/install-windows) using the remote installation method (via the Management Tool) or one of the local or third-party installation methods.

To open the Management Tool, enter the following URL in a browser:

```text theme={"system"}
https://<Management_Tool_hostname_or_IP>/<URL_configured_during_install>
```

Log in as `admin` with the password defined during Application Server installation, then start the remote Client installation.

## 8. Install macOS Clients

[Install macOS Clients](/docs/administration/clients/install-macos) locally using the command line, or remotely using a mass deployment tool. Both approaches download the installation file from the Management Tool first.

## 9. Install Linux Clients

[Install Linux Clients](/docs/administration/clients/install-linux) locally using the command line. Linux Clients do not support remote installation from the Management Tool; every Linux endpoint is installed from its own Terminal.

## 10. Assign licenses to Clients

After Clients are installed, [assign endpoint licenses](/docs/administration/licensing/assign-endpoint-licenses) to the Clients that will be monitored.

Syteca is now deployed. All features are available for configuration and use.

## Related

<CardGroup cols={2}>
  <Card title="Install the Application Server" icon="server-cog" href="/docs/administration/deployment/install-application-server">
    Detailed Application Server installation procedure (step 2 above).
  </Card>

  <Card title="Install the Management Tool" icon="monitor" href="/docs/administration/deployment/install-management-tool">
    Detailed Management Tool installation, including update and uninstall (step 3 above).
  </Card>

  <Card title="Activate serial key" icon="key-round" href="/docs/administration/licensing/activate-serial-key">
    Online and offline serial key activation (step 4 above).
  </Card>

  <Card title="Getting Started Checklist" icon="list-checks" href="/docs/get-started/checklist">
    Post-installation onboarding checklist for using Syteca in production.
  </Card>
</CardGroup>