Install Scops

Run Scops Setup on a Windows server to install the two Scops services and prepare the repository.

Before you begin

Run Setup

  1. Run Scops-Setup-<version>.exe as administrator. Accept the license agreement and keep the folder.

  2. On Ports, keep 5138 (web) and 5140 (API) if no other program uses them.

  3. On Repository database, enter the Host, Port, DB user, Password and Service name. Click Test Connection. If the test fails, the line beside the button shows the cause.

  4. If grants are missing, Missing Grants shows under Test Connection. Click it, click Copy and ask a DBA to run the script as SYS. Then click Test Connection again.

  5. Click Next. On Database schema, click Run next to 1. Create tables, then next to 2. Insert initial data. On a schema that already holds a Scops repository, Setup keeps its data, and 2. Insert initial data is not necessary.

  6. On Scops login, type a password for the admin user two times (8 characters or more). This is the Scops user for the browser, not a database account. If the repository already has users, this password replaces the old admin password.

  7. Keep the firewall task selected. Click Install.

  8. Setup copies the files and starts the services. The Starting Scops page shows each service. If a service does not start, this page shows the reason.

  9. The last page shows how Scops works. Keep both services running: if ScopsApi stops, monitoring stops. Click Finish.

What Setup installs

Windows serviceProgramListens on
ScopsApi (Scops API Service)C:\Program Files\Scops\api\Scops.Api.exehttp://localhost:5140
ScopsWeb (Scops Web Interface)C:\Program Files\Scops\blazor\Scops.exehttps://<server>:5138, and http://localhost:5137

Both services start with Windows and run as Local System.

Open Scops

Open https://<server>:5138, or use the Scops shortcut on the server. Then sign in as admin.

Trust the Scops certificate

Scops starts with its own certificate, so browsers show a warning such as "Your connection isn't private". Scops still encrypts the connection.

  1. Import C:\Program Files\Scops\blazor\certs\Scops-ui.cer into Trusted Root Certification Authorities. For many computers, use Group Policy. For one computer, double-click the file, click Install Certificate and select Local Machine.

  2. Open Scops by the server name. The certificate is valid for localhost, the server name, its DNS name and its IP addresses.

Scops makes a new certificate 30 days before the old one expires. Then install the new Scops-ui.cer again.

Add a name to the certificate

  1. Add the DNS alias or IP address to ExtraNames in C:\Program Files\Scops\blazor\appsettings.json:

    "Server": {
      "HttpPort": 5137,
      "HttpsPort": 5138,
      "Certificate": {
        "ExtraNames": [ "scops.example.com", "10.20.30.40" ]
      }
    }
  2. Restart the ScopsWeb service. Scops makes a new certificate.

  3. Install the new Scops-ui.cer again.

Use your company's certificate

  1. Import the certificate with its private key into Local Computer › Personal (certlm.msc). It must be for the name that users type, for server authentication. A wildcard certificate is correct.

  2. Add a Certificate block to the Server block of C:\Program Files\Scops\blazor\appsettings.json. A comment, or a missing comma or quote, stops ScopsWeb.

    "Server": {
      "HttpPort": 5137,
      "HttpsPort": 5138,
      "Certificate": {
        "Subject": "scops.example.com"
      }
    }
  3. Restart the ScopsWeb service.

SettingWhich certificate Scops uses
SubjectThe newest valid certificate for this name. Scops finds a renewed certificate within 15 minutes.
ThumbprintThis certificate in Local Computer › Personal.
Path, PasswordA .pfx file. To encrypt the password, run "C:\Program Files\Scops\api\Scops.Api.exe" --encrypt-config "<password>" and use the ENC(...) value.

If Scops cannot use the certificate, it uses its own certificate and writes the cause to the ScopsWeb log.

Install without prompts

Setup runs without prompts only for an upgrade, or in a folder that still has its configuration.

Scops-Setup-<version>.exe /VERYSILENT /SUPPRESSMSGBOXES /ACCEPTEULA ^
  /LOG="C:\Temp\scops-setup.log"
OptionWhat it does
/ACCEPTEULAAccepts the license agreement. Required.
/WEBPORT=, /APIPORT=The ports, when Setup asks for them. An upgrade keeps the current ports.
/MERGETASKS="!firewall"Does not add the firewall rule.
/DIR="..."Sets the folder.
/LOG="..."Also writes the Setup log to this file. Setup always writes it to the setup-logs folder of the installation.
Exit codeMeaning
0Installed, and the web port answers.
1Refused, nothing changed. The log gives the cause.
10Installed, but a service does not run. See Troubleshooting.

Upgrade

  1. Run the new Scops-Setup-<version>.exe as administrator.

  2. Accept the license agreement, click Next on each page, then click Install.

Setup keeps your ports, repository, certificates, keys and service accounts. ScopsApi then updates the repository. This can take some minutes: on the Starting Scops page, Setup waits up to 30 minutes before it starts ScopsWeb. Migrations shows what changed.

Uninstall

  1. In Windows, open Installed apps and find Scops Database Monitoring.

  2. Select Uninstall.

  3. When Setup asks if it must remove the configuration, select No if you will install Scops again.

Setup does not change the repository database. If you do not need the Scops schema, drop it yourself.

If you remove the configuration, Setup asks for the ports, the repository and a new admin password again, and Scops makes a new web certificate. On the same server with the same repository, Scops can read the stored passwords, and your license key stays active.

Updated November 9, 2026