- 4 minutes to read

Installing Nodinite

Welcome to the Nodinite installation guide. This page helps you pick the right guide for your situation, shows how a v7 installation flows from the Portal to the CLI, and collects the prerequisite and troubleshooting guides you may need on the way.

On this page, you will learn

  • ✅ Which installation guide fits your situation
  • ✅ How the Portal wizard and the CLI work together
  • ✅ Which prerequisite guides to read before you start
  • ✅ What to do after installation

Understanding the v7 Installation Flow

Nodinite v7 is installed with a CLI (Nodinite.Installer.Cli.exe) that the Nodinite Portal generates for each Environment. You describe the environment once in the Portal wizard; the CLI then creates the Configuration Database, the IIS web sites, the Core Services, and the selected agents on Windows Server in one deployment. The same Portal and CLI pair also runs every later update.

flowchart LR subgraph Portal["Nodinite Portal wizard"] S1["fa:fa-leaf Step 1: Basics"] --> S2["fa:fa-key Step 2: Auth"] S2 --> S3["fa:fa-database Step 3: Infrastructure"] S3 --> S4["fa:fa-server Step 4: Servers"] S4 --> S5["fa:fa-monitor-waveform Step 5: Agents"] S5 --> S6["fa:fa-download Step 6: Review and Download"] end subgraph Server["Windows Server - elevated PowerShell 7"] V["fa:fa-list-check validate"] --> D["fa:fa-eye deploy-environment
--dry-run"] D --> R["fa:fa-terminal deploy-environment"] end S6 -->|"ZIP package"| V R --> W["fa:fa-globe Web Client and
Core Services running"] W -->|"First start"| L["fa:fa-database Logging Service creates
the first Log Database"] style S1 fill:#9E59BB style S2 fill:#9E59BB style S3 fill:#9E59BB style S4 fill:#9E59BB style S5 fill:#9E59BB style S6 fill:#9E59BB style V fill:#E47528 style D fill:#E47528 style R fill:#E47528 style W fill:#93d16d style L fill:#93d16d

Diagram: purple nodes are the Portal wizard steps (Basics, Auth, Infrastructure, Servers, Agents, Review and Download); orange nodes are the CLI workflow on the server; green nodes are the result: the Web Client and the other Core Services running, and the Logging Service creating the first Log Database.

Estimated time: 15-30 minutes for a basic installation once the prerequisites are in place.

Choose Your Installation Path

Your situation Follow this guide
New installation on Windows Server Install Nodinite v7 and its installation steps
New installation with OAuth 2.0 / OpenID Connect sign-in Install Nodinite v7 - OpenID, used together with Step 2: Auth
Already on v7 and want a later v7.x release Updating Nodinite v7
On v6 and staying on the same servers (in-place migration) Updating from v6 to v7
On v6 and moving to a new Windows Server or SQL Server Migrating v6 to v7 on New Hardware
Evaluating container runtimes Runtime Environments and Docker (Experimental POC)

Important

Nodinite v6 and its Install and Update Tool are no longer supported. Use v7 for new installations; the Version 6 archive is kept only for reference.

Prerequisites

Before you begin, work through the master checklist: Prerequisites for Installing Nodinite.

Quick Checklist

Prerequisites Deep Dive

Review these detailed guides when a checklist item needs more context.

Windows Server & IIS

SQL Server

Security & Authentication

Troubleshooting & Maintenance

After Installation

Once the CLI run completes:

  • Open the Web Client at the site root of its port, for example https://nodinite.contoso.com:<port>/
  • Expect the first Log Database only after the Logging Service has started; the package does not create it
  • A stopped MCP Server can be by design when Keep the MCP Server stopped is set
  • After a certificate renewal, install the renewed certificate and rerun the update; with a subject configured, nothing changes in the Portal

Then configure logging, monitoring, and access:

Need Help?

  • Read more on the Support page
  • Looking for professional installation services? Contact our certified Partners

Previous Step

Next Steps