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, SQL Server strategy, authentication, TLS, agents, and optional SQL DB Lookup entries. After that, you download a generated ZIP package and run the PowerShell 7 installer, which creates the Core Services, web applications, and databases.
Diagram: The v7 installation flow starts in the Portal and ends with PowerShell 7 provisioning IIS, SQL Server resources, Core Services, and selected agents.
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, .NET Framework 4.8, and the .NET 10 Hosting Bundle installed in the correct order
- DacFX and MSDTC available when your deployment needs them
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 5: Configure TLS 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.
| Step | Task | Key topics |
|---|---|---|
| Step 1: Register Environment | Create the Environment in the Portal | Product key, SQL Server, SQL DB Lookup |
| Step 2: Save | Persist the configuration | Validation and transition |
| Step 3: Advanced Settings | Override service accounts and ports | Core Services exceptions |
| Step 4: Configure Authentication | Choose the sign-in model | Windows Authentication or OAuth 2.0 / OIDC |
| Step 5: Configure TLS | Prepare HTTPS | Certificate and DNS settings |
| Step 6: Select and Configure Agents | Choose packaged agents | Monitoring, Logging, MCP Endpoint |
| Step 7: Review | Validate the architecture graph | Final Portal review |
| Step 8: Download Binaries | Download the generated ZIP package | Portal actions |
| Step 9: Run PowerShell 7 Script | Execute the installer | Interactive, parameterized, and verbose install |
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.