Multiple Instances

Setup installs EnvisionSCADA as one or more instances on one server. Each instance is a separate EnvisionSCADA system with its own project, databases, license, IIS site and web address. Instances are added, updated and removed one by one. An update of one instance leaves the other instances running their version.

Every program version is installed once, in C:\Program Files\EnvisionSCADA\<version>, and serves every instance that runs it. The data of an instance (databases, project files, logs and Python libraries) is in its own data folder. A program version stays installed while an instance runs it. Setup removes it when no instance uses it any more.

Program Files and Data Folders

Only SYSTEM, the Administrators group and the IIS app pool of the instance have access to its data folder. One instance cannot read the databases of another, and a logged-on user cannot copy them.

The data folder belongs to the instance, not to the project. Export Project and Import Project work as on a single installation, and a project exported from one instance can be imported into another. To move a data folder, remove the instance with Keep the data folder, move the folder, and add the instance again with Existing data folder.

Other articles call the folder with the databases, project files and logs the installation folder. On a server with instances, that is the data folder of the instance.

Where antivirus exclusions are in use, add C:\Program Files\EnvisionSCADA and the data folders to them.

Install

Start the setup and accept the End-User Licence Agreement. The Installation Type page offers two options:

When the port or the data folder of the default instance is in use, the page shows the reason and selects Custom Installation, where the setting can be changed.

The Instances page lists the instances setup creates:

On a new server the list holds the instance EnvisionSCADA on port 80 with the demo project. Use Add instance..., Edit... and Remove to change the list. Program files shows the folder of the program files. On the first installation, Change... selects another folder; a folder outside Program Files receives the permissions of Program Files.

With both options, Install enables IIS and installs the program files, the ASP.NET Core Hosting Bundle and Python, then creates and starts the instances. The last page lists the instances with their web address, and Open opens an instance in the browser. Restart Windows when setup asks for it.

On a server installed with a version before 2026/11/02, Default Installation takes over the existing installation as the instance EnvisionSCADA. In a Custom Installation the list holds it with Existing project. Setup keeps its project, databases, IIS site, bindings and HTTPS certificate. The installation folder becomes the data folder of the instance, and the site runs the program from C:\Program Files\EnvisionSCADA. The earlier version is removed from Apps & Features.

Add Instance

Add instance... opens the settings of a new instance. Setup checks every setting while it is entered and enables OK when the instance can be created.

Ports

Each instance needs its own HTTP port, and its own HTTPS port when it has one, unless the instances are told apart by host name.

The same applies to the servers an instance runs itself: two instances cannot listen on the same port. When more than one instance enables one of these servers, give each of them its own port on the Parameters page:

BACnet devices are configured in one instance per server. All BACnet communication of a server uses UDP port 47808, and the answers of a device reach one instance only.

Update

Start the setup of the new version and accept the End-User Licence Agreement. The Update instances page lists the instances:

Only the selected instances stop; the other instances keep running their version. A stopped instance stays stopped and updates its database at its next start.

With Back up the configuration database of each selected instance first, setup copies Configuration.db to the Database folder of the instance, as Configuration_yyyy-MM-dd-HH-mm-ss.db, after the instance has stopped.

After the update, setup removes the program versions no instance runs any more.

Maintain

Run the setup of the installed version again, or click Modify for EnvisionSCADA in Apps & Features, to open Maintain EnvisionSCADA. It lists the instances with their data folder, version and state. Changes are collected in the list and carried out with Apply changes; only the instances that change stop.

Uninstall

Uninstall... on the Maintain page, or Uninstall for EnvisionSCADA in Apps & Features, removes all program versions and the IIS sites and app pools of all instances. The ASP.NET Core Hosting Bundle, Python and the Windows features stay installed.

The data folders are kept, unless Also delete these data folders permanently is selected and DELETE is typed to confirm. A kept data folder can be attached to a later installation with Add instance, Existing data folder.

Start Checks

An instance that cannot start on its data folder shows the page EnvisionSCADA cannot start with the reason, and starts no communication. Its databases are not changed. The details are in the Windows Application event log. Resolve the cause and restart the instance; the page reloads every 30 seconds.

Licenses

Each instance needs its own license. The Computer ID is the same for every instance on a server: request the Activation Code of each instance with that Computer ID and the License Code of its own license.

A license runs in one instance at a time. When a second instance starts with the Activation Code of a license that is already running on the server, its License page shows This license is already in use by another instance on this server. and it runs in Demo Mode. It takes the license within a minute after the other instance has stopped.

Unattended Installation

Setup runs without screens with /quiet, and with the progress page only with /passive. Run it from an elevated command prompt.

Without a plan file, setup installs the instance EnvisionSCADA on port 80 with the demo project on a new server, takes over a server installed with a version before 2026/11/02, or updates every instance whose license support covers the new version, each with a backup of its configuration database. /uninstall removes every instance and program version and keeps the data folders. /norestart leaves the restart to the operator; /forcerestart restarts Windows when the installation requires it.

A plan file defines what setup changes. Pass it with EnvisionPlan:

"EnvisionSCADA <version> MultiInstance.exe" /quiet /norestart EnvisionPlan=C:\Setup\plan.json

Every program version contains the instance tool, InstanceTool\EnvisionSCADA.InstanceTool.exe in its program folder. It lists the instances, writes an example plan, checks a plan, and carries out a plan on the installed program versions. With --dry-run it shows the commands a plan would run without changing anything.

EnvisionSCADA.InstanceTool.exe list
EnvisionSCADA.InstanceTool.exe example C:\Setup\plan.json
EnvisionSCADA.InstanceTool.exe validate C:\Setup\plan.json
EnvisionSCADA.InstanceTool.exe apply C:\Setup\plan.json --dry-run

The plan file written by example:

{
  "Operations": [
    {
      "Action": "Add",
      "BackupConfiguration": false,
      "CertificateThumbprint": "",
      "DataFolder": "C:\\ProgramData\\EnvisionSCADA\\Line2",
      "DeleteDataFolder": false,
      "DemoProject": false,
      "DesktopShortcuts": true,
      "ExistingDataFolder": false,
      "HostName": "",
      "HttpPort": 8081,
      "HttpsPort": 0,
      "Name": "Line2",
      "ProjectFile": "",
      "Version": ""
    },
    {
      "Action": "Update",
      "BackupConfiguration": true,
      "CertificateThumbprint": "",
      "DataFolder": "",
      "DeleteDataFolder": false,
      "DemoProject": false,
      "DesktopShortcuts": true,
      "ExistingDataFolder": false,
      "HostName": "",
      "HttpPort": 80,
      "HttpsPort": 0,
      "Name": "EnvisionSCADA",
      "ProjectFile": "",
      "Version": ""
    }
  ],
  "ProgramVersion": "2027.02.01.2",
  "RemoveUnusedVersions": true,
  "RestartIis": false
}

The fields that count depend on the Action: