Management Tool Prerequisites

This page is the complete pre-install checklist for the Syteca Management Tool. Work through it top to bottom on the Windows computer where you’ll install the Management Tool — by the end, IIS will be enabled and configured, .NET Framework will be installed, a certificate will be issued and trusted, and HTTPS will be bound.

Not available in SaaS. The Management Tool is only installed on-premises and in self-hosted deployments. In SaaS, you access the equivalent functionality through your browser without local installation.

On Windows 7, the steps below must be followed in sequence — some steps depend on earlier ones.

After completing this checklist, return to Install the Management Tool for the installer itself.

1. Turn on IIS

Internet Information Services (IIS) is the web server that hosts the Management Tool’s web interface. Turn it on using the method that matches your OS.

Windows 10 / 8.1 / 7
Windows Server 2012 / 2016 (Server Manager)
Windows Server 2012 / 2016+ (PowerShell)
Windows Server 2019 Core (PowerShell)

Open Programs and Features

Select Control Panel → Programs → Programs and Features.

Open Windows Features

Click the Turn Windows features on or off link.

Enable IIS

In the Windows Features window, in the Features tree-view, select the Internet Information Services checkbox, then click OK.

Run this PowerShell command as administrator:

Install-WindowsFeature -Name Web-Server,Web-Mgmt-Tools

Server 2019 Core has no GUI — use PowerShell with the full set of features needed for the Management Tool:

Install IIS and its components

Install-WindowsFeature -Name Web-Server,Web-WebSockets,Web-Asp-Net,Web-Asp-Net45,Web-Mgmt-Console

Verify installed features

Get-WindowsFeature

Launch IIS Manager (when needed)

After installation, IIS Manager can be run by using its full path:

C:\Windows\System32\inetsrv\InetMgr.exe

2. Install .NET Framework

Server Manager IIS feature selection screen showing the required IIS sub-features checked for the Management Tool prerequisites — The IIS Web Server feature selection during Step 1 — every required sub-feature must be enabled before the Management Tool can install.

.NET Framework 4.8 is required to run the Management Tool.

.NET Framework 4.8 is included in Windows 10 (version 1903 and later) and on most current Windows Server versions.
If your version of Windows doesn’t have .NET Framework 4.8, download it from Microsoft. Installation requires administrator permissions.

After installing .NET Framework, restart the computer before continuing. The remaining steps depend on the framework being fully registered with IIS.

Syteca 7.23 and later also require .NET 8.0 for the Application Server (separate from .NET Framework 4.8 on the Management Tool host). See Syteca 7.23 release notes for details.

3. Configure IIS

After IIS is on, enable the specific roles and features the Management Tool needs. The exact list depends on your Windows version — pick the matching tab.

Windows 10
Windows 8.1
Windows 7
Windows Server 2016
Windows Server 2012

In the Windows Features window, select all of these checkboxes, then click OK:

.NET Framework 4.8 Advanced Services
Internet Information Services → Web Management Tools → IIS Management Console
Internet Information Services → World Wide Web Services → Application Development Features → ASP.NET 4.8 and WebSocket Protocol
Internet Information Services → World Wide Web Services → Common HTTP Features → Static Content

4. Provide an SSL certificate

You can either generate a self-signed certificate (sufficient for internal deployments — must then be added to Trusted Root manually) or import a purchased trusted certificate issued for the computer where the Management Tool will run.

If you already have a certificate generated or installed for this computer, skip this step and continue with Step 6 — bind HTTPS.

Generate a self-signed certificate
Import a purchased trusted certificate
Server 2019 Core (PowerShell)

Open IIS Manager

On Windows 8.1 / 7: Computer → Manage → Services and Applications → Internet Information Services (IIS) Manager.
On Windows Server 2012+: press Windows+R, enter inetmgr, press Enter.

The inetmgr command opens IIS Manager on any Windows version — fastest way regardless of OS.

Open Server Certificates

Click the main node in the Connections tree-view, then double-click the Server Certificates icon in the IIS section.

Create the certificate

In the Actions pane on the right, click Create Self-Signed Certificate.

Name it

In the Create Self-Signed Certificate window, enter a name in Specify a friendly name for the certificate, select Personal in the Select a certificate store drop-down, then click OK.

Open IIS Manager

Use inetmgr or the GUI route as in the self-signed tab above.

Open Server Certificates

Click the main node in the Connections tree-view, then double-click the Server Certificates icon in the IIS section.

Import

In the Actions pane on the right, click Import.

Choose the file

In the Import Certificate window, click the … button to browse for the certificate file. Enter the password in the Password field, then click OK. The certificate appears in the Server Certificates pane.

For purchased certificates that were issued for your computer, you can skip the next step (adding to Trusted Root) — they’re trusted automatically by Windows. Continue with Step 6.

Server 2019 Core has no GUI for IIS Manager — generate, export, and import the certificate with PowerShell.

Generate and bind a self-signed certificate to port 443

$site = "Default Web Site"
New-WebBinding -Name $site -IPAddress * -Port 443 -Protocol https
$cert = New-SelfSignedCertificate -CertStoreLocation 'Cert:\LocalMachine\My' -DnsName "syteca"
$certPath = "Cert:\LocalMachine\My\$($cert.Thumbprint)"
$providerPath = 'IIS:\SslBindings\0.0.0.0!443'
Get-Item $certPath | New-Item $providerPath

On Server 2019 Core, this single block both creates the certificate and binds it to port 443 — you do not need Step 6.

Export an existing self-signed certificate (if you need to move it)

$password = ConvertTo-SecureString -String "my_password" -Force -AsPlainText
Get-ChildItem -Path Cert:\LocalMachine\My\<cert_thumbprint> |
    Export-PfxCertificate -FilePath "C:\cert.pfx" -Password $password

Import an existing self-signed certificate

$password = ConvertTo-SecureString -String "my_password" -Force -AsPlainText
Import-PfxCertificate -FilePath <path_to_certificate> -CertStoreLocation Cert:\LocalMachine\My -Password $password

5. Add the self-signed certificate to Trusted Root

If you generated a self-signed certificate in Step 4, you must export it and add it to Trusted Root Certification Authorities — otherwise the browser will show a certificate error when opening the Management Tool. Skip this step entirely if you imported a purchased trusted certificate.

Export the self-signed certificate

Open Export from IIS Manager

In IIS Manager, on the Server Certificates pane, select the certificate you generated. In the Actions pane on the right, click Export.

You can also right-click the certificate and choose Export from the context menu.

Save it

In the Export Certificate window, set the file location and a password, then click OK. The certificate is exported as a .pfx file.

Import into Trusted Root Certification Authorities

Open MMC

Press Windows+R, enter mmc, press Enter, then click Yes in the User Account Control prompt.

Add the Certificates snap-in

In the Console window, select File → Add/Remove Snap-in. In the dialog, select Certificates → Add.

Pick Computer account

In Certificates snap-in, select Computer account, then click Next. In Select Computer, select Local computer: (the computer this console is running on), then click Finish. Back in Add or Remove Snap-ins, click OK.

Open Trusted Root

In the Console window, expand the Certificates (Local computer) node. Find the Trusted Root Certification Authorities node.

Import the certificate

Right-click Trusted Root Certification Authorities, choose All Tasks → Import, then walk through the Certificate Import Wizard:

File to Import — browse to the .pfx you exported.
Private key protection — enter the password you set during export.
Certificate Store — accept the default (Trusted Root Certification Authorities).
Finish — confirm.

The Issued To field on the imported certificate contains the name of the computer the Management Tool will be installed on. You must use the same name in the address bar of your browser to open the Management Tool — otherwise the browser will still warn about the certificate.

Close MMC

Close the Console window.

6. Bind HTTPS on the default website

On Windows Server 2019 Core, this step is already done — the PowerShell block in Step 4 handled the binding. Skip to Next steps.

Open IIS Manager

Open IIS Manager (inetmgr from the Run window, or via Computer → Manage on Windows 8.1 / 7).

Select the Default Web Site

In the Connections pane on the left, expand the node with the target computer’s name, expand the Sites node under it, and select Default Web Site.

If there’s no Default Web Site, any other website can be selected — the name doesn’t matter.

Open Site Bindings

In the Actions pane on the right, click the Bindings link.

Add an HTTPS binding

If there’s no https binding yet, click Add. In the Add Site Binding window:

Type: select https.
SSL certificate: select the certificate from Step 4.

Click OK, then Close in the Site Bindings window.

Next steps

With all six steps complete, the Windows computer is ready to install the Management Tool. Continue to Install the Management Tool.

Installation checklist

The full Syteca deployment checklist (Application Server, Database, Management Tool).

System requirements

Supported Windows versions, hardware specs, and network ports.

Update best practice

The procedure to follow when upgrading an existing deployment.

Security and encryption

Encryption details for Client–Server communication.

Overview

Installation

Scaling & High Availability

Database

Users and Permissions

Clients

Access

Management Tool Settings

Client Parameters

Licensing

Multi-Tenant

Dashboards

Audit Log

Security

Management Tool Prerequisites

1. Turn on IIS

2. Install .NET Framework

3. Configure IIS

4. Provide an SSL certificate

5. Add the self-signed certificate to Trusted Root

Export the self-signed certificate

Import into Trusted Root Certification Authorities

6. Bind HTTPS on the default website

Next steps

Installation checklist

System requirements

Update best practice

Security and encryption

​1. Turn on IIS

​2. Install .NET Framework

​3. Configure IIS

​4. Provide an SSL certificate

​5. Add the self-signed certificate to Trusted Root

​Export the self-signed certificate

​Import into Trusted Root Certification Authorities

​6. Bind HTTPS on the default website

​Next steps

​Related

Installation checklist

System requirements

Update best practice

Security and encryption

1. Turn on IIS

2. Install .NET Framework

3. Configure IIS

4. Provide an SSL certificate

5. Add the self-signed certificate to Trusted Root

Export the self-signed certificate

Import into Trusted Root Certification Authorities

6. Bind HTTPS on the default website

Next steps

Related