- 6 minutes to read

Updating from Version 6 to Version 7

Welcome to Nodinite 7 – a more secure, simpler platform with improved performance and modern architecture.

This page mainly focus on migrating version 6 to version 7 on Windows, quite possibly in-place upgrades. Other options exists.

What's New in v7

Security and Architecture

  • Multiple run-time environments - review for options:
    • Windows Service → IIS Hosting – Nodinite v7 hosts Core Services and many Monitoring Agents as IIS applications
  • Enhanced TLS Support – IIS hosting makes HTTPS configuration and certificate management much easier than the legacy Windows Service model
  • Modern .NET – Built on .NET 10 for better performance and stronger security. Install .NET 10 Hosting Bundle
    Ensure you install the Hosting Bundle — not the plain Runtime or SDK. The Hosting Bundle includes the .NET Runtime and the IIS support module (ASP.NET Core Module v2) required by Nodinite.
  • Container and cloud-ready foundation – v7 provides a stronger foundation for containerized and cloud-hosted deployments. See Container Runtime and Licensing and Hybrid and Multi-Cloud BPM scenario
  • Modern identity support – v7 adds first-class OAuth 2.0 / OpenID Connect support for enterprise and cloud identity providers. See OpenID Connect and OAuth 2.0 configuration
  • Portal-based management – Portal provides a single source of truth for environment configuration: shared knowledge, centralized access control, and full visibility into who can view, modify, and download

Expanded Feature Platform

  • Business Process Management – Build end-to-end process views with the BPM Designer
  • Mapify – Explore and collaborate on integration landscapes with Mapify
  • C4 modeling support – Design architecture views with C4 Diagrams
  • AI capabilities – Use built-in AI guidance and tools from the AI documentation
  • MCP endpoint support – Connect external AI tooling through the MCP Endpoint

Key Benefits

  • Better security with IIS application pool isolation
  • Easier TLS/HTTPS deployment for Core Services and agents
  • Improved performance and scalability
  • Portal-based configuration with shared knowledge, user access control, and team visibility into who can modify or download
  • Single zip download for Core Services and all locally installed agents — always the latest version, no version pinpointing or clicking through multiple packages
  • Stronger platform baseline for containerized and cloud-first operations
graph LR A[ v6 Environment] -->|Migrate| B[ Portal Registration] B --> C[ Download v7] C --> D[ Run Scripts] D --> E[ Configure TLS] E --> E1[ Configure OAuth/OIDC] E1 --> F[ v7 Ready] F --> G[ Container/Cloud Foundation] F --> H[ BPM] F --> I[ Mapify] F --> J[ C4 Diagrams] F --> K[ AI + MCP] style A fill:#e3f2fd style F fill:#c8e6c9 style G fill:#fff8e1 style H fill:#f3e5f5 style I fill:#e8f5e9 style J fill:#e1f5fe style K fill:#fce4ec

Prerequisites

Before starting, ensure you have:

  • Ensured that the v6 environment is fully operational and all services (including any agents) are running on the lastest v6 release (v6.x). If you have any agents on version 7 already, please contact our support team for guidance before proceeding.

  • Latest SSMS - Optional

  • Latest Microsoft OLEDB Driver for SQL Server, see Microsoft OLEDB Driver for SQL Server - ⚠️ MANDATORY⚠️
    OLEDB DRiver Validation Error
    Example of CLI based Validation error.

    Note

    You must have a supported OLEDB driver on all SQL Server nodes.

  • Backup databases and configuration files

  • Administrator access to Nodinite Application Servers

  • PowerShell 7 installed with execution policy set to Unrestricted or ByPass

  • PowerShell 7 script user must be sysadmin on SQL Server instance

  • Nodinite 7 contract and product key from the Portal

For rights rationale and non-sysadmin fallback actions after migration, see SQL Server Sysadmin Requirements.

  • IIS Windows Features installed (including Web-Scripting-Tools and Web-AppInit)
  • Remove WebDAV if it is not explicitly required — For dedicated Nodinite 7 IIS environments, remove WebDAV completely. If the IIS server is shared and no other application depends on WebDAV, remove it before migration. See WebDAV guidance and the PowerShell 7 removal script
  • Remove legacy IIS URL Rewrite rules — delete any server-level redirect rules left over from the v6 installation (e.g. a rule named Nodinite forward that redirects to the old HTTPS address). Leaving these rules in place will cause unexpected redirects on the new v7 HTTP endpoints.

Warning

Critical shared-IIS edge case during fresh v7 deployment: if you reuse the same certificate as other IIS sites and those sites have HTTPS bindings without both host name and SNI enabled, the installer can remove those existing bindings.

Correct this before running scripts. Either configure host name + SNI on those non-Nodinite sites, use another certificate for Nodinite, or install on another machine. See Step 11 TLS warning and mitigations.

  • .NET 10.0 Hosting Bundle

    Important

    Install the Hosting Bundle — not the plain Runtime or SDK. On the .NET download page, scroll to ASP.NET Core Runtime → Windows → Hosting Bundle. The Hosting Bundle includes the .NET Runtime and the IIS support module (ASP.NET Core Module v2) required by Nodinite. Install order matters: IIS Windows Features must be installed before the Hosting Bundle. Installing the Hosting Bundle on a server without IIS features means the IIS module is skipped. If you installed the Hosting Bundle first, run the installer again (repair) after enabling IIS features.

    Note

    The Logic Apps Monitoring Agent was previously the only component requiring the .NET 9 Hosting Bundle. From v7.3.9 onwards, it runs on .NET 10 as well. Only the .NET 10 Hosting Bundle is needed for v7.3.9 and later.

    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/x86.

  • Latest DacFX installed on App Server

  • Review Service Accounts and ensure SPNs are configured correctly for Windows authentication

  • Stop the Pickup Log Events Service before starting

Migration Steps

Step Task Complexity
1. Register Environment Create environment in Portal Simple
2. Review Review settings with visual diagram Simple
3. Download Binaries Download Core Services package Simple
4. Deploy Core Services with CLI Deploy v7 Core Services using the CLI installer Moderate
5. Remove Core Services Clean up old IIS applications Simple
6. Export Monitoring Agents Export agent configurations Simple
7. Import Monitoring Agents Import agents to Portal Simple
8. Update Monitoring Agents Install v7 agents Moderate
9. Remove Windows Services Remove old services Simple
10. Verify Functionality Test core functionality Simple
11. Configure TLS Enable HTTPS and close wizard Complex
12. Install Pickup Service Install v7 Pickup Service Moderate
13. Update Agent Configurations Update endpoints and URIs Moderate
14. Final Cleanup Remove old files and folders Simple
15. Post Migration Tasks Verify completion and follow post-installation guide Simple
16. Review Log Databases Check for database schema updates and run the Update Guide if needed Simple

Important

After the v7 migration is complete, review the Log Databases page in the Web Client and use the Update Log Database wizard if the page reports an available schema update. This is a required follow-up after the Core Services migration and after major v7 updates.

After Migration is Complete

See Step 15: Post Migration Tasks for the completion checklist, post-installation guidance, and recommendations for future enhancements such as gMSA accounts and OAuth 2.0 / OpenID Connect.

Contact your Partner or read more on the Support page for guidance on these features.

Troubleshooting

Need Help?

Next Step