- 6 minutes to read

Updating from Version 6 to Version 7

Nodinite 7 is a more secure and simpler platform than Nodinite 6, and it changes how the product is installed, hosted, and updated. Nodinite 6 is no longer supported, so plan the migration now. This guide upgrades an existing v6 environment in place on the same Windows Server and reuses your existing Configuration Database and Log Databases. When you also replace the Windows Server or the SQL Server, start with Migrating v6 to v7 on New Hardware.

Understanding the Migration Journey

You register the environment in the Nodinite Portal, download a package, and run it with Nodinite.Installer.Cli.exe from an elevated PowerShell 7 prompt. The migration runs in two packages: first the Core Services, then the locally installed Monitoring Agents, imported from the running v7 Web Client. Only then do you remove the v6 installation.

flowchart LR subgraph Portal["Portal"] direction TB S1["fa:fa-id-card 1. Register Environment"] --> S2["fa:fa-eye 2. Review"] --> S3["fa:fa-download 3. Download Core package"] end subgraph Core["Core Services"] direction TB S4["fa:fa-terminal 4. Deploy with CLI"] end subgraph Agents["Staged agent import"] direction TB S5["fa:fa-file-export 5. Export Monitoring Agents"] --> S6["fa:fa-file-import 6. Import into Portal"] --> S7["fa:fa-terminal 7. Deploy agents package"] end subgraph Finish["Verify and finish"] direction TB S8["fa:fa-circle-check 8. Verify"] --> S9["fa:fa-trash 9. Remove v6 legacy"] --> S10["fa:fa-lock 10. Configure TLS"] --> S11["fa:fa-inbox 11. Pickup Service"] --> S12["fa:fa-link 12. Update URIs"] --> S13["fa:fa-broom 13. Final Cleanup"] --> S14["fa:fa-list-check 14. Post Migration"] --> S15["fa:fa-database 15. Review Log Databases"] end S3 --> S4 --> S5 S7 --> S8 style S1 fill:#2678BD style S2 fill:#2678BD style S3 fill:#2678BD style S4 fill:#E47528 style S5 fill:#9E59BB style S6 fill:#9E59BB style S7 fill:#E47528 style S8 fill:#93d16d style S9 fill:#D5396D style S10 fill:#3F827B style S11 fill:#3F827B style S12 fill:#3F827B style S13 fill:#D5396D style S14 fill:#93d16d style S15 fill:#93d16d

The 15 migration steps. Blue steps run in the Portal, orange steps run the CLI on the server, purple steps move the Monitoring Agents through the Nodinite Overview export and the Portal import, pink steps remove v6 leftovers, teal steps configure TLS, the Pickup Log Events Service, and agent URIs, and green steps verify the result and review the Log Databases.

What Changes from v6 to v7

Area Nodinite 6 Nodinite 7
Installer Install and Update Tool (deprecated) Portal wizard plus Nodinite.Installer.Cli.exe in elevated PowerShell 7
Hosting Windows services and IIS applications under one web site 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
Ports Fixed ports, such as port 8000 Set per environment in the Portal Servers step
TLS A custom IIS web site with a manual binding Core host Configuration: the CLI finds the certificate by subject and binds it at every install and update
Configuration Database NodiniteConfig_<EnvironmentName> The same database, upgraded in place; it keeps its v6 name
Monitoring Agents One MSI per agent One Portal package; IBM DataPower and Dynamics CRM agents stay on the MSI installer
Pickup Service Local Settings.json Remote Configuration in the Web Client
Authentication Windows Windows during the migration; OAuth 2.0 / OpenID Connect afterwards

What's New in v7

Prerequisites

The master checklist is Prerequisites for Installing Nodinite, including its v7 migration-specific checks. Before you start, confirm:

  • The v6 environment is fully operational and all services, agents included, run the latest v6 release. If any agent already runs v7, contact support before you continue.
  • Backups of all databases and configuration files.
  • Administrator access to the Nodinite application server, and an Environment with a Nodinite 7 product key in the Portal.
  • PowerShell 7, run elevated (the CLI is an executable, so the execution policy doesn't apply); the user running the CLI must be sysadmin on the SQL Server instance. Rights rationale and post-migration reduction: SQL Server Sysadmin Requirements.
  • The latest Microsoft OLE DB Driver for SQL Server on all SQL Server nodes ⚠️ Mandatory; see the OLE DB Driver release notes.
    CLI validation error for a missing or outdated OLE DB driver
    Example of the CLI validation error shown when the OLE DB driver is missing or outdated.
  • IIS Windows Features installed, including Web-Scripting-Tools and Web-AppInit, before the .NET 10.0 Hosting Bundle. Install the Hosting Bundle, not the plain Runtime or SDK; it adds the ASP.NET Core Module v2 to IIS. If you installed it first, run it again (Repair).
    Download the Hosting Bundle from the ASP.NET Core Runtime section on the .NET download page
    Select Hosting Bundle under Windows in the ASP.NET Core Runtime section, not x64 or x86.
  • The latest DacFX (SqlPackage.exe) on the application server; SSMS is optional.
  • Service accounts with the Logon as a Service right, DCOM Local Activation for the Monitoring Service account, and a configured MSDTC. These are required, not optional.
  • Service Principal Names (SPN) planned for Windows authentication with custom domain accounts.
  • Firewall rules for the new per-site ports; the ports live in Network and Firewall Overview.
  • Remove WebDAV when no other application on the server needs it; see WebDAV guidance and the PowerShell 7 removal script.
  • Remove legacy IIS URL Rewrite rules from v6, such as a rule named Nodinite forward; they cause unexpected redirects on the new v7 endpoints.
  • Stop the Pickup Log Events Service.

Warning

Shared IIS server: if you reuse the Nodinite certificate on other IIS web sites whose HTTPS bindings lack a host name with SNI enabled, the installer can remove those bindings. Fix those bindings, use another certificate, or install on another machine before you run the CLI. See the TLS warning and mitigations in Step 10.

Migration Steps

Step Task Complexity
1. Register Environment Create the environment in the Portal Simple
2. Review Review settings in the architecture diagram Simple
3. Download Binaries Download the Core Services package Simple
4. Deploy Core Services with CLI Upgrade the Core Services and the Configuration Database Moderate
5. Export Monitoring Agents Export local agent definitions from the v7 Web Client Simple
6. Import Monitoring Agents into the Portal Analyze and import the exported definitions Simple
7. Download and Update Monitoring Agents Deploy the agents package and mark the migration complete Moderate
8. Verify Functionality Verify v7 before you remove v6 Simple
9. Remove legacy v6 IIS applications and Windows services Remove the v6 installation Moderate
10. Configure TLS Enable HTTPS on the v7 web sites Complex
11. Install Pickup Service Install the v7 Pickup Log Events Service Moderate
12. Update Agent Configurations Update Web Client, Log API, and Log View URIs Moderate
13. Final Cleanup Delete old v6 files and folders Simple
14. Post Migration Tasks Confirm completion and follow post-installation guidance Simple
15. Review Log Databases Run the Update Log Database wizard when a schema update is available Simple

Important

After the migration, open Log Databases in the Web Client and use the Update Log Database wizard if the page reports an available schema update. Repeat this check after every major v7 update.

Getting Help

After the migration, keep the environment current with Update Nodinite v7, and consider gMSA accounts and OAuth 2.0 / OpenID Connect (Step 14).

Next Steps