- 5 minutes to read

Install Nodinite v7

Use this page as the starting point for a fresh Nodinite v7 installation. Nodinite v7 replaces the deprecated v6 Install and Update Tool with two parts:

  1. You register the Environment in the Nodinite Portal wizard. The Portal stores every setting and generates an installation package.
  2. You run the package with Nodinite.Installer.Cli.exe from an elevated PowerShell 7 prompt. The CLI creates the Configuration Database, sets up IIS, and installs the Core Services and the selected agents.

The installation step pages are the master for the procedure; this page explains the flow, sums up the prerequisites, and links to each step.

Are you on Nodinite v6? Use Updating from v6 to v7 (or Migrating v6 to v7 on New Hardware) instead. Already on v7 and want a later v7.x release? Use Update Nodinite v7.

Understanding the Installation Flow

Nothing is installed while you work in the Portal. The Portal only collects the values; the CLI applies them on each server. You keep the same Environment for its whole life: every later update or configuration change is a new package from the same Environment, run with the same CLI.

flowchart LR subgraph "Nodinite Portal" S1["fa:fa-leaf Step 1: Basics
Environment and runtime"] --> S2["fa:fa-key Step 2: Auth
Windows or OAuth 2.0 / OIDC"] S2 --> S3["fa:fa-database Step 3: Infrastructure
SQL Server, SQL DB Lookup, proxy"] S3 --> S4["fa:fa-server Step 4: Servers
TLS, identities, ports"] S4 --> S5["fa:fa-plug Step 5: Agents
Monitoring and Log Agents"] S5 --> S6["fa:fa-file-zipper Step 6: Review and Download
ZIP package"] end subgraph "Nodinite Core Services Server" S7["fa:fa-terminal Step 7: CLI in elevated PowerShell 7
validate, dry-run, deploy-environment"] IIS["fab:fa-windows One IIS web site per Core Service
own port and TLS binding"] end subgraph "Nodinite Agent Servers" AG["fa:fa-plug Selected agents"] end subgraph "SQL Server" CDB["fa:fa-database Configuration Database"] LDB["fa:fa-database First Log Database"] end S6 -->|"Download ZIP"| S7 S7 -->|"Install or update"| IIS S7 -->|"Install or update"| AG S7 -->|"SqlPackage (DacFX)"| CDB IIS -.->|"Logging Service, first start"| LDB style S1 fill:#2678BD,color:#fff style S2 fill:#2678BD,color:#fff style S3 fill:#2678BD,color:#fff style S4 fill:#2678BD,color:#fff style S5 fill:#2678BD,color:#fff style S6 fill:#2678BD,color:#fff style S7 fill:#E47528,color:#fff style IIS fill:#93d16d style AG fill:#93d16d style CDB fill:#93d16d style LDB fill:#FFD525

Diagram: the six Portal steps (blue) produce the package for the Environment; the CLI (orange) installs the Core Services, the Monitoring Agents and Log Agents, and the Configuration Database (green). The CLI creates no Log Database: the Logging Service creates the first Log Database (yellow) when it starts for the first time.

What the Installer Uses

Area Set in Outcome
Environment and runtime Step 1: Basics Names the instance permanently and selects Windows Server (IIS), the production path, or a container runtime (Runtime Environments Overview)
Authentication Step 2: Auth Windows Authentication or OAuth 2.0 / OIDC for the Web Client, Web API, Log API, and MCP Server, plus the Secret Management certificate
SQL Server Step 3: Infrastructure Connection string for the Configuration Database; the CLI creates or updates it with SqlPackage (DacFX)
SQL DB Lookup Step 3: Infrastructure Named connection strings that the sqllookup Formula plugin uses in Search Field Expressions
Hosting, TLS, and ports Step 4: Servers On Windows Server, every Core Service (Web Client, Web API, Log API, Logging Service, Monitoring Service, MCP Server) is its own IIS web site with its own port and a TLS certificate found by subject
Agents Step 4: Servers and Step 5: Agents The Monitoring Agents and Log Agents on each server, with their ports, identities, and agent databases
Package Step 6: Review and Download One ZIP with the CLI, the installation media, and one folder per server with its config.cli.json

Prerequisites Summary

  • Administrator rights on every server you install on.
  • Windows Server with the IIS Windows Features installed before the latest .NET 10 Hosting Bundle; the order matters.
  • PowerShell 7 on every server that runs the CLI.
  • SQL Server. The user who runs the CLI needs sysadmin on the affected SQL Server instances, unless you use Azure SQL Managed Instance; see SQL Server Sysadmin Requirements.
  • The latest DacFX (SqlPackage.exe) on the servers where the CLI runs.
  • A configured MSDTC.
  • Service identities with the Logon as a Service right; the Monitoring Service identity also needs DCOM Local Activation permission (Monitoring Service prerequisites).
  • .NET Framework 4.8 on servers that run the BizTalk Server, Windows Server, Dynamics CRM, or IBM DataPower agents; all other agents run on .NET 10.
  • A TLS certificate whose subject or SAN matches the host name, installed in LocalMachine\WebHosting or LocalMachine\My (Step 4: Servers).
  • Firewall rules for the ports you choose in the Portal; the Network and Firewall Overview is the one home for ports.
  • For OAuth 2.0 / OIDC: the identity provider app registrations (Install Nodinite v7 - OpenID).

Important

The Prerequisites page is the master checklist. Run its Detailed Prerequisite Verification on every server before you start.

Warning

Shared IIS edge case for fresh installs: when you reuse a certificate that is already bound to other IIS web sites, the installer can remove those existing HTTPS bindings if they are configured without both a host name and SNI enabled.

Before you install, either set host name + SNI on those non-Nodinite sites, use a different certificate for Nodinite, or install on another machine. See Step 4: Servers and TLS hardening guidance.

Installation Steps

Follow the steps in order. The Servers step replaced the old Advanced tab: every server-specific value now lives there.

Step Task Key topics
Step 1: Basics Create the Environment in the Portal and choose the runtime Permanent Environment name, Windows Server (IIS) or container runtime
Step 2: Auth Choose the sign-in model Windows Authentication or OAuth 2.0 / OIDC, service account defaults, gMSA, Secret Management
Step 3: Infrastructure Configure SQL Server, SQL DB Lookup, and proxy SQL connection string, SqlPackage path, sqllookup entries, outbound proxy
Step 4: Servers Configure each server Install path, TLS host name and certificate subject, service identities, one port per Core Service
Step 5: Agents Configure the packaged agents Monitoring Agents and Log Agents, agent ports, identities, Agent Database
Step 6: Review and Download Validate and download the package Workspace summary, server packages, allocated ports, ZIP download
Step 7: Run the CLI Workflow (Elevated PowerShell 7) Run the CLI from the extracted ZIP root validate, --dry-run, deploy-environment, runtime overrides

After the Installation

Next Steps