Install Nodinite v7
Use this page as the stable starting point for a fresh Nodinite v7 installation. The detailed procedure is now split into dedicated step pages so the guide is easier to follow, easier to maintain, and stays within the documentation size rules.
For production deployments, the preferred v7 model is to host Core Services and agents in IIS with TLS enabled. That gives you a consistent HTTPS endpoint model and avoids the extra configuration burden of Windows Service-based hosting.
If you are migrating from v6, use the Migration Guide instead. If you are already on v7 and want a later v7.x release, use Update Nodinite v7.
Understanding the Installation Flow
The installation starts in the Portal, where you define the Environment, authentication, SQL connectivity, server-level TLS and port settings, and selected agents. The final Portal step validates the Environment and exposes the download from the review flow or from the Environment Actions menu. After that, run Nodinite.Installer.Cli.exe from an elevated PowerShell prompt.
What the Installer Uses
| Area | Outcome |
|---|---|
| Portal settings | Generates the package and parameter defaults |
| Hosting model | Uses IIS for Core Services and agents so TLS can be configured consistently |
| SQL Server settings | Defines how the Configuration Database and Log Database are created |
| Authentication | Chooses Windows Authentication or OAuth 2.0 / OIDC |
| TLS | Controls HTTPS bindings and certificate usage |
| Agents | Includes Monitoring and Logging components in the package |
| SQL DB Lookup | Creates named connection strings that the sqllookup Formula plugin can use later |
Prerequisites Summary
- Administrator access to the application server
- SQL Server access with rights to create or manage the required databases
- PowerShell 7 available on the server
- IIS Windows Features and the LATEST .NET 10 Hosting Bundle installed in the correct order
- .NET Framework 4.8 still required on Windows for some agents and legacy components
- DacFX and MSDTC available when your deployment needs them
Important
On Windows, the main Nodinite v7 platform runs on .NET 10, but some agents and older Windows components still require .NET Framework 4.8. Review the master prerequisite checklist for the complete validation list before installation: Detailed Prerequisite Verification.
Warning
Critical shared-IIS edge case for fresh installs: when reusing a certificate that is already bound to other IIS web sites, those existing HTTPS bindings can be removed if they are configured without both a host name and SNI enabled.
Before 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.
For the full validation checklist, use Detailed Prerequisite Verification.
Installation Steps
The detailed instructions now live in the step set below and follow the current Portal flow. The old Advanced tab is no longer the primary configuration model; the Server-specific overrides are now managed in the dedicated Servers step.
| Step | Task | Key topics |
|---|---|---|
| Step 1: Basics | Create the Environment in the Portal and choose runtime | Environment name and runtime model (Windows or Container) |
| Step 2: Auth | Choose the sign-in model | Windows Authentication or OAuth 2.0 / OIDC |
| Step 3: Infrastructure | Configure SQL Server, SQL DB Lookup, and proxy | SQL connection strings, SQL DB Lookup values, outbound proxy settings |
| Step 4: Servers | Configure server-level values | Server/install path, TLS domain + thumbprint, service identities, and ports |
| Step 5: Agents | Choose packaged agents | Monitoring, Logging, MCP Endpoint |
| Step 6: Review and Download | Validate the architecture graph and download the generated package | Final Portal review and download flow |
| Step 7: Install the Generated Package | Execute the CLI installer | Validate, dry-run, deploy-environment, and optional runtime overrides |
SQL DB Lookup and sqllookup
The Portal now exposes SQL DB Lookup as part of the install flow. Use it when Search Field Expressions need reusable SQL Server reference-data connections. The dedicated registration step shows the Portal UI and points to the full sqllookup Formula page.