- 7 minutes to read

Update Nodinite v7

Update your Nodinite v7 installation to a later 7.x release. An update uses the same tools as the installation: you download a new package for the same Environment from the Nodinite Portal and run it with Nodinite.Installer.Cli.exe. The CLI updates the Core Services, the Configuration Database, and every Monitoring Agent and Log Agent in the package.

What you'll achieve by following this guide:

  • ✅ Minimize downtime and disruption for end-users
  • ✅ Protect your data with clear backup and validation steps
  • ✅ Benefit from the latest features and improvements in Nodinite v7
  • ✅ Access expert support and resources throughout the process
graph LR subgraph "Nodinite Portal" roPortal["fa:fa-person-to-portal Nodinite Portal"] roEnvironment["fa:fa-leaf Environments"] roZIP["fa:fa-file-zipper Download ZIP"] roPortal --> roEnvironment roEnvironment --> roZIP end subgraph "Nodinite Instances" roDev["fa:fa-code-commit Development"] roPreProd["fa:fa-code-commit PreProd"] roProd["fa:fa-code-commit Prod"] end roZIP -->|"First: test"| roDev roZIP -->|"Then: validate"| roPreProd roZIP -->|"Last: production"| roProd style roPortal fill:#2678BD,color:#fff style roEnvironment fill:#2678BD,color:#fff style roZIP fill:#2678BD,color:#fff style roDev fill:#FFD525 style roPreProd fill:#E47528,color:#fff style roProd fill:#93d16d

Diagram: each Environment gets its own package from the Portal (blue); update the non-production Environments first (yellow, orange) and production last (green).

Tip

If you have a non-production Environment, test the update there first. This lets you validate all steps and configurations before you apply them to production.

Looking for a partner to help you update? Contact any of our certified Partners.

Still on Nodinite v6? Use Updating from v6 to v7 instead; v6 is no longer supported.

Important

You need administrative rights on the Nodinite servers, and the passwords of the service accounts, unless they are gMSA accounts. With OAuth 2.0 / OIDC, also have the Web Client and installation client secrets ready; the Portal doesn't store them (Step 2: Auth).

Prerequisites

Before you begin the update, make sure that:

  • End-users know about the update and the expected downtime.
  • You have a backup of the Nodinite databases and configuration files. The CLI also asks for a verified backup of the Configuration Database before it changes the schema (backup prompt).
  • You have an existing Nodinite v7 installation. Every Core Service and agent in the package is updated to the latest version.
  • A valid Nodinite 7 product key is available in the Nodinite Portal. If it has expired or is about to expire, create a new one. If you cannot, contact your partner or the Support page.
  • The Prerequisites are still met, for example the latest .NET 10 Hosting Bundle and DacFX.
  • The firewall rules in the Network and Firewall Overview match the ports in the Portal. When you update from a version before 7.4.0, add the MCP Server port in the Portal first (Update MCP Endpoint).

Estimated time

On a high level, the update has three steps:

The CLI commands typically take a few minutes, including the update of all agents. Then update the Log Databases if the Web Client reports a pending schema update (After the Update).

flowchart LR A["fa:fa-leaf Select Environment"] --> CHG{"Change settings?"} CHG -->|"Yes"| WIZ["fa:fa-pen Edit the wizard steps"] CHG -->|"No"| B["fa:fa-file-zipper Download and extract ZIP"] WIZ --> B B --> C["fa:fa-terminal validate, dry-run,
deploy-environment"] C -->|"File locks"| L["fa:fa-lock iisreset or reboot,
then rerun"] L --> C C -->|"Done"| D["fa:fa-database Update Log Databases
if offered"] D --> E["fa:fa-circle-check Verify Core Services"] style A fill:#2678BD,color:#fff style CHG fill:#2678BD,color:#fff style WIZ fill:#9E59BB,color:#fff style B fill:#2678BD,color:#fff style C fill:#E47528,color:#fff style L fill:#FFD525 style D fill:#3F827B,color:#fff style E fill:#93d16d

Diagram: the update flow. Optional Portal changes (purple) go into the installation steps before the download; the CLI (orange) can stop on file locks (yellow); after the run, update the Log Databases (teal) and verify the Core Services (green).

Step 1: Select Environment

Tip

Find the Environment for the Licensee.

In the Nodinite Portal, select your Environment:

  1. Navigate to the existing Customer entry.
    Customer Overview
    Find and click the Customer entry.

  2. Make sure you have a valid Nodinite 7 product key. If not, create it with the Create Product Key button.
    Product Key Entry
    Example of a Nodinite 7 product key entry.

    Important

    You must have a valid Nodinite 7 product key to proceed with the update. If you can't create one, contact your partner or the Support page.

  3. Click the Environment tab and find the entry to update.
    Environment
    Example of the Environment to update for a selected Licensee in the Nodinite Portal.

To change settings before you update, such as ports, the certificate, agents, or service accounts, edit the Environment in the installation steps (Step 4: Servers, Step 5: Agents) and save it. To switch between Windows and OAuth 2.0 / OIDC sign-in, follow Migrate Authentication Method instead.

Step 2: Download/Extract ZIP (Core and Agents)

Tip

Download the CLI bundle ZIP for the selected Environment.

  1. Click the Download all packages button in the Review and Download step of the Environment entry (Step 6).
    Download
    Example of the Download all packages button in the Review and Download step of the Environment entry.

    Alternatively, in the Environments overview for the selected Customer, click the Actions button and select Download all packages.
    Action Download
    Example of the Actions button and the Download all packages menu item in the Environments overview for the selected Customer.

  2. The download begins immediately. Save the ZIP file and extract it on the Nodinite server.
    Downloading
    Example of the download in the browser.

Step 3: Run the CLI workflow

In the extracted ZIP bundle, the folder named after each server holds the generated config.cli.json and a readme.txt with the commands for that server (ZIP bundle content). Run the commands from an elevated PowerShell 7 prompt in the extracted ZIP bundle root.

Tip

  • The CLI runs as the user of the elevated prompt. That user must be sysadmin on the affected SQL Server instances, unless you use Azure SQL Managed Instance.
  • If the shell is not elevated, the CLI commands can fail with insufficient permissions.
  • Running the prompt as the account of the Logging Service can be a way to avoid adding your own account to the sysadmin role.

Review the SQL Server Sysadmin Requirements before you run the CLI workflow.

Use the recommended workflow; nodinitesrv01 is an example, replace it with the server folder name from the readme.txt file:

  1. Validate the package without changing the machine:

    .\Nodinite.Installer.Cli.exe validate --config .\nodinitesrv01\config.cli.json

  2. Run a dry run to check the update actions:

    .\Nodinite.Installer.Cli.exe deploy-environment --config ".\nodinitesrv01\config.cli.json" --dry-run

  3. Deploy when validation and the dry run are clean:

    .\Nodinite.Installer.Cli.exe deploy-environment --config ".\nodinitesrv01\config.cli.json"

For runtime overrides, pass arguments instead of editing the generated files, for example --database-connection-string, --agent-connection-string, and --service-password; see passing arguments.

File Locks Detected

When files are locked during the update, the CLI reports them. On Windows Server, run iisreset to release the locks, then rerun the CLI command. A reboot of the Nodinite server may also be needed to release locks, and some .NET 10 updates need a reboot to complete.
CLI File Lock Error
Example of a file lock error reported by the CLI; run iisreset to release the locks and rerun the command.

After the Update

  • Browse the Web Client and run basic checks.
  • Open the Log Databases page in the Web Client. When it reports an available schema update, run the Update Log Database wizard; this is a separate step from the Core Services update and often needed after larger v7 updates.
  • A stopped MCP Server can be by design; see Keep the MCP Server Stopped.
  • After a TLS certificate renewal, install the renewed certificate on the server and run the update package again. With a certificate subject in the Portal, nothing else changes (Core host Configuration).

Each Core Service has its own update page with what changes and how to verify it:

Core Service Update notes
Web Client Update the Web Client
Web API Update the Web API
Log API Update the Log API
Logging Service Update the Logging Service
Monitoring Service Update the Monitoring Service
MCP Endpoint Update MCP Endpoint
Configuration Database Update the Configuration Database
Log Databases Update a Log Database

Contact our support

If you have questions or run into issues during the update, contact your Partner for first-line support, or read more on the Support page.

Next Steps