- 0 minutes to read

Install Nodinite v7

Welcome! This guide walks you through installing Nodinite v7, whether you are upgrading from a previous version or starting fresh. If you are new to Nodinite, you’ll find all the Planning steps, requirements, and tips needed for a smooth, secure deployment.

What you'll achieve by following this guide:

  • ✅ Rapid, reliable installation with minimal downtime
  • ✅ Clear prerequisites and configuration steps for success
  • ✅ Flexible agent and database setup for any Environment
  • ✅ Access to expert support and resources throughout the process

Update Nodinite v7

Before you start, make sure you:

  • ✅ Have administrator access to the Application Server and SQL Server
  • ✅ Know all required account names and passwords
  • ✅ Have reviewed prerequisites and downloaded necessary installers
  • ✅ Understand if you are performing a fresh install or an upgrade

Tip

If you have a non-prod Environment, we recommend testing the install process there first. This ensures you can validate all steps and configurations before applying them to your production Environment.

Looking for a partner to help you install? Please contact any of our certified Partners.

Important

You must have knowledge of account names and their passwords and you must have administrative rights on the Nodinite Application Server to perform the installation.

Prerequisites

General Requirements:

  • Administrator access to the Nodinite Application Server
  • PowerShell 7 with Unrestricted or ByPass execution policy
  • sysadmin role on SQL Server for database operations

Important

Installation Order: IIS features → .NET Framework 4.8 → .NET 9 Hosting Bundle. Installing in the wrong order causes ASP.NET Core Module V2 installation failures.

Required Components:

  • IIS Windows Features - Web Server role with required features
  • .NET Framework 4.8 - Required for Log API WCF services
  • Latest .NET 9.0 Runtime + ASP.NET Core Hosting Bundle - Required for Web Client and Web API
    Failed to load ASP.NET Core runtime
    If you see this image, please ensure the LATEST .NET 9.0 Hosting Bundle is installed correctly.
  • DacFX (SqlPackage.exe) - Database deployment tool
  • MSDTC - Distributed transaction coordinator

Detailed Prerequisite Verification - Complete verification scripts and troubleshooting

Tip

Run the detailed verification checks before starting installation to catch missing prerequisites early.

Estimated time

On a high level, there are a few distinct steps in the installation process:

Running the script typically takes a few minutes. This estimate includes installing all Monitoring Agents and Log Agents.

graph LR A["Register Environment"] --> AA["Configure Agents"] AA --> B["Download/Extract ZIP (Core and Agents)"] B --> C["Run PowerShell Script"]

Visual overview of the installation process.

Step 1: Register Environment

In the Nodinite Portal, register your Environment by following these steps:

  1. Navigate to the existing Customer entry.
    Customer Overview
    Find and Click on the Customer entry.

  2. Ensure you have Nodinite 7 product key available. If not, create it by clicking on 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 upgrade. If you can't create one, please contact your partner or Nodinite Support.

  3. Click the Environment tab, then click the Add Environment button.
    Add Environment
    Example of the Add Environment button in the Nodinite Portal.

  4. A modal appears, click 'Install Fresh Nodinite 7' button.
    Install Fresh Nodinite 7
    Example of the 'Install Fresh Nodinite 7' button.

  5. The modal changes and you must now enter variables (ultimately parameters in the PowerShell 7 scripts).
    Add Environment
    Example of the 'Add Environment' modal.

Configure Nodinite 7 variables

Tip

Configure the necessary variables for the Nodinite 7 Environment.

In this step, you will set the required variables for your Nodinite 7 Environment. These variables are essential for the proper functioning of Nodinite and must be configured correctly.

Please ensure that you set the configuration values correctly, as some of them are difficult to change later. Your runtime platform is configured with these values, and they are utilized in the PowerShell script that will run later in the process. If you need to modify these values, you might have to remove everything except for the databases and start over.

If you are unsure about some values, enter placeholder information to continue. You can override these parameters later when you run the PowerShell 7 installation script. This flexibility allows you to update settings before finalizing the installation, ensuring you have full control over your Environment configuration.

Mandatory Variable Default Description
Environment Name* The name of the target Environment
NOTE: Once set, this should not be changed as databases, app pools, folders and more are poisoned with this name.
Description Description to clarify purpose or usage.
Destination Root Path C:\Program Files\Nodinite Leave it empty to select default value.
App Server Name localhost Leave it empty to set default app server name as localhost.
Admin Account Email Enter Nodinite Administrator Account Email.
Web Client Port 40000 / 443 IIS Port for Web Client, If you are using TLS, use port 443.
Web API Port 40001 IIS Port for Web API
Log API Port 40002 IIS Port for Log API
Logging Service Port 40003 IIS Port for Logging Service
Monitoring Service Port 40004 IIS Port for Monitoring Service

Configure Database Settings

Tip

Configure the Configuration Database and Log Database settings for Nodinite v7.

There are different settings depending on the type of database you want to use.

  1. Standalone - Use a single SQL Server instance for all databases. Use this option if you are using SQL Server Standard, Enterprise, or Express edition. Tihs also works for failover clusters.
  2. Always on - Use a SQL Server Always On Availability Group for high availability and disaster recovery.
  3. Azure - Managed Instance - Use an Azure SQL Managed Instance for a fully managed database service in the cloud. This option is suitable for cloud-based deployments. See the Azure SQL Managed Instance section in the SQL Server Connection Strings guide for connection string examples, authentication requirements, and best practices.
  4. You can also choose to Edit Connection String Manually if you prefer to configure the connection string yourself.
Mandatory Option/Setting Default Description
Database Type
  • Standalone
  • Always on
  • Azure - Managed Instance
 Type of database to use for Nodinite 7. The default is Standalone. If you select Clustered, you must provide a connection string to the SQL Server instance.
Database Server Name localhost Name of the SQL Server instance. The default is localhost. If you are using a named instance, use the format ServerName\InstanceName.
Edit Connection String Manually No Whether to edit the connection string manually.
Connect without encrypt No Whether to connect without encryption.
Encrypt Connection Checked Whether to encrypt the connection, or not. Should be checked on most Environments
Trust server certificate Checked Whether to trust the server certificate, or not. Should be checked on most Environments
Trust Server Certificate Checked Whether to trust the server certificate, or not. Should be checked on most Environments
Sql Package Path C:\Program Files\Microsoft SQL Server\170\DAC\bin\SqlPackage.exe Path to the SqlPackage.exe tool.

Step 2: Save

Tip

Persist your settings.

You should save your settings before proceeding to the next step. Review all settings carefully to ensure they are correct.

Click the 'Save' button to persist settings.
Save Button
Example of the Save button.

If the save is successful, you will see a confirmation message and another tab will appear in the modal. You can click the Review button to review your settings before proceeding. Your settings display with a visual graph. See Step 7: Review for more details.

Step 3: Advanced Settings

Tip

This step is only required if you need different service account names on the different Nodinite Core Services.

Expand any of the accordions to configure the port and service account name.
Advanced Tab
Example of the Advanced tab with expanded sections.

Step 4: Configure Authentication

Tip

Configure authentication settings.

In this step, you will configure the authentication settings for your Nodinite 7 Environment. You can choose between Windows Authentication or OAuth 2.0/OIDC.

Configure Windows Authentication

This is the default authentication method when your Environment is running on Windows Servers. It leverages Active Directory for user management and provides a seamless experience for users within the organization. It is suitable for most on-premises deployments.

Nodinite version 6 only had the option to use Windows Authentication. If you are upgrading from version 6, this is the recommended option.

Mandatory Variable Default Description
Authentication Method Windows Select Windows to use Windows Active Directory and integrated security
Default Domain Name* <DomainName> Name of the Windows Active Directory Domain; Default prefix for accounts;
Admin Account <NodiniteAdminUsrAccountName> Enter Nodinite Administrator Account Name.
Default Services Account Name <DefaultServiceAccountName> Enter Default Services Account Name. You can override these in the 'Advanced' tab

Authentication Tab with Windows option
Example of the Authentication tab with Windows Authentication selected.

Configure OAuth 2.0 / OIDC

This topic is in details on Install Nodinite v7 - OpenID user guide.

Step 5: Configure TLS (Enable HTTPS)

Tip

Configure TLS settings for secure HTTPS communication.

In this step, you will configure the TLS settings for your Nodinite 7 environment. This step must be completed BEFORE running the installation script, as the script will automatically configure IIS bindings and HTTPS settings based on your Portal configuration.

TLS Tab - Hardening with HTTPS
Example of the TLS tab.

When is TLS Required?

  • ❗OAuth 2.0 / OIDC: If you are using OAuth 2.0 / OIDC authentication, you MUST enable TLS. This is non-negotiable.
  • ✅Windows Authentication: If you are using Windows Authentication, TLS is recommended but optional based on your security requirements.

Important

OAuth 2.0 / OIDC requires HTTPS! To use the OAuth 2.0 / OIDC authentication method, you must have a valid TLS/SSL certificate installed on the Nodinite Application Server. As such, you cannot continue without enabling TLS in your hosting environment.

Before You Configure TLS

Prerequisites:

  • ✅ Valid SSL/TLS certificate from a trusted Certificate Authority (CA)
  • ✅ Certificate installed in IIS on the Nodinite Application Server
  • ✅ DNS record pointing to your server (e.g., nodinite.yourdomain.com)
  • ✅ Certificate thumbprint noted (optional but recommended)
  • ✅ Firewall rules allowing inbound HTTPS traffic (port 443)

How to perform hardening - Complete guide to certificate preparation, installation, and HTTPS configuration

Portal Configuration:

Field Label Default Value / Example Description
Host / Domain nodinite.yourdomain.com The DNS name or hostname for your Nodinite server. Must match your SSL certificate.
Certificate Thumbprint (optional) 9b27c9d1939b821bb... The certificate thumbprint from IIS. Optional but recommended for validation.

Note

All Nodinite Web Applications will use the same TLS settings. This includes Web Client, Web API, Log API, Logging Service, Monitoring Service, and any Agents you install.

Important Considerations:

  • Configure before download - Set TLS settings in this step before downloading the installation package
  • Upgrading from v6 - Enable TLS during upgrade, then update all client bookmarks (http:// → https://), system configurations, and firewall rules to allow port 443
  • Changing TLS settings - Requires uninstalling the environment (keeping databases and config files) and re-running installation with new settings

Warning

Environment name is permanent! You cannot change the environment name when re-installing with different TLS settings.

Step 6: Select and Configure Agents

Tip

Select and configure Agents to include in the installation.

In this step, you will select the Agents you want to include in the installation. The Agents are responsible for Monitoring and Logging.

Click the Agents tab to view the available Agents.
Agents Tab
Example of the Agents tab in the Nodinite Portal. Click on the accordion on any of the agents to expand the configuration options.

Check the checkboxes for the Agents you want to include in the installation.

You must enter a port number for use within the IIS for each Agent you select. The port numbers must be unique and not conflict with other services running on the same server. The default port numbers are provided, but you can change them if needed.

Some agents like BizTalk, Azure Logic Apps, Dynamics CRM and IBM DataPower require additional configuration, such as the database connection string. Ensure you provide the correct values for these settings.
Logic Apps Agent Configuration
Example of the Logic Apps Agent configuration entry with additional configuration properties.

Step 7: Review

Tip

Review settings using a visual graph before you continue with the installation operation.

In this step, you have the opportunity to review your settings before you download the necessary binaries for Nodinite v7.

We recommend reviewing all settings carefully to ensure they are correct before proceeding. Click on the 'Overview' tab to open a Mermaid diagram displaying the current configuration in a user-friendly graph.
Review Settings Graph
Example of how the Environment will look with the current settings after the installation operation has completed.

Step 8: Download Binaries

In this step, you will download the necessary binaries for Nodinite 7.

  1. Close the modal if it is still open, or navigate to the Environments tab.
  2. Click the Actions button, and the click the Download menu item to start the download process.
    Download Binaries
    Example of 'Download' menu item in the Actions button.

While generating your ZIP package with the necessary binaries the following screen will be displayed:
Downloading Nodinite Binaries
Example of the Downloading Nodinite Binaries screen.

Once the download is complete, you can proceed to the next step.

Step 9: Run PowerShell 7 Script

Tip

Run the PowerShell 7 script to install your environment.

Ensure you have completed all Prerequisites before running the installation script. The installation process involves database setup, IIS configuration, service installation, and agent deployment.

Step-by-Step Installation Process

Step 1: Unblock Downloaded Files

PowerShell blocks files downloaded from the internet by default. You must unblock all files before running the script.

  1. Open a PowerShell 7 terminal with administrative privileges

  2. Navigate to the folder where you extracted the downloaded ZIP file:

    cd "C:\Temp\Nodinite7-Installation"

  3. Unblock all files recursively:

    Get-ChildItem -Recurse | Unblock-File

    This command unblocks all files in the extracted folder and subfolders.

Note

Why unblock files? Windows marks files downloaded from the internet as potentially unsafe. The installation script contains PowerShell modules, DLLs, and executables that must be unblocked to run properly.

Step 2: Choose Installation Method

You have three options for running the installation script:

Run the script without parameters. You'll be prompted to enter values interactively:

.\Nodinite7-%ENVIRONMENTNAME%-Installation.ps1

Replace %ENVIRONMENTNAME% with the name of your environment (e.g., DEMO, PROD, TEST).

Interactive Installation Script Example
Example Screenshot of the Interactive Installation Script prompting for passwords.

Option B: Non-Interactive Mode with Parameters

Provide all required parameters in the command line. Useful for automated deployments or when you want to avoid interactive prompts:

# Example: Provide service account and password as parameters
$serviceAccountPassword = Read-Host "Enter service account password" -AsSecureString
.\Nodinite7-DEMO-Installation.ps1 `
    -WebClientServiceAccount 'Domain\NodiniteWebClient' `
    -WebClientServiceAccountPassword $serviceAccountPassword

Option C: Verbose Mode (Troubleshooting and Detailed Logging)

Add the -Verbose parameter to see detailed installation progress and diagnostic information:

.\Nodinite7-%ENVIRONMENTNAME%-Installation.ps1 -Verbose

When to Use Verbose Mode:

  • 🔍 Troubleshooting installation failures - See exactly which step failed and why
  • 📋 Detailed progress tracking - Monitor each stage (database creation, IIS configuration, service installation)
  • 🐛 Debugging configuration issues - View connection string validation, permission checks, file operations
  • 📝 Creating support tickets - Capture detailed logs to share with Nodinite Support
  • 🎓 Learning the installation process - Understand what the script does at each stage

Handling Passwords and Special Characters

Warning

Password Special Characters: PowerShell interprets certain characters differently depending on how you quote strings. Follow these guidelines to avoid password-related installation failures.

PowerShell Quoting Rules:

  • Double quotes (") - Enable variable expansion. Characters like $ are treated as variables
  • Single quotes (') - Treat everything as literal text. Recommended for passwords

Common Password Issues:

Password Wrong Correct Explanation
P@ssw0rd$123 "P@ssw0rd$123" 'P@ssw0rd$123' Dollar sign $ treated as variable in double quotes
P@ss'w0rd 'P@ss'w0rd' 'P@ss''w0rd' Escape single quote by doubling it
P@ss%w!rd "P@ss%w!rd" 'P@ss%w!rd' Percent and exclamation marks work in single quotes

Recommended Approaches:

Option 1: Interactive Read-Host (Most Secure) 

$password = Read-Host "Enter service account password" -AsSecureString
.\Nodinite7-DEMO-Installation.ps1 `
    -WebClientServiceAccount 'Domain\NodiniteWebClient' `
    -WebClientServiceAccountPassword $password

Benefits:

  • ✅ Password not visible on screen or in command history
  • ✅ Handles all special characters automatically
  • ✅ No escaping required

Option 2: Single Quotes (For Simple Passwords) 

$password = ConvertTo-SecureString 'P@ssw0rd$123!%' -AsPlainText -Force
.\Nodinite7-DEMO-Installation.ps1 `
    -WebClientServiceAccount 'Domain\NodiniteWebClient' `
    -WebClientServiceAccountPassword $password

Option 3: Single Quotes with Escaped Quotes (For Passwords Containing ') 

# Password: P@ss'w0rd
# Escape single quote by using two single quotes ('')
$password = ConvertTo-SecureString 'P@ss''w0rd' -AsPlainText -Force
.\Nodinite7-DEMO-Installation.ps1 `
    -WebClientServiceAccount 'Domain\NodiniteWebClient' `
    -WebClientServiceAccountPassword $password

Overriding Portal Configuration Values

Important

If you provided placeholder or incorrect values in the Nodinite Portal, you can override them when running the installation script. Do NOT edit the script file itself.

Common Parameters You Can Override:

# Override database connection settings
.\Nodinite7-DEMO-Installation.ps1 `
    -DatabaseServer 'SQL01\PROD' `
    -WebClientServiceAccount 'PROD\NodiniteWebClient' `
    -WebClientServiceAccountPassword $webClientPassword `
    -LoggingServiceAccount 'PROD\NodiniteLogging' `
    -LoggingServiceAccountPassword $loggingPassword `
    -MonitoringServiceAccount 'PROD\NodiniteMonitoring' `
    -MonitoringServiceAccountPassword $monitoringPassword `
    -Verbose

Available Parameters:

Use Get-Help to see all available parameters:

Get-Help .\Nodinite7-%ENVIRONMENTNAME%-Installation.ps1 -Detailed

Troubleshooting Installation Issues

If you encounter issues during installation:

Complete Troubleshooting Guide - Detailed solutions for all common installation issues

Post-Installation Validation

Contact our support

If you have questions or encounter issues during the upgrade, contact your Partner for 1st line support or email us at support@nodinite.com.

Next Step

Updating Nodinite v7

Uninstall Nodinite v7