Upgrade from v6 to v7 – Step-by-Step Guide

Upgrade your Nodinite v6 to Nodinite v7 confidently. This actionable guide ensures a smooth, secure, and efficient transition to the latest version.

✅ Unique Benefits of Upgrading

• ✅ Seamless migration of agents, app pools, and configuration data
• ✅ Enhanced security with new encryption and decryption mechanisms
• ✅ Automated database updates and backup guidance
• ✅ Step-by-step PowerShell 7 script instructions for reliability
• ✅ Visual review and confirmation at every stage
• ✅ Direct support and partner assistance available

💡Test the upgrade in a non-production environment first to validate all steps and configurations before applying to production.

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

Warning

Have all service account names and passwords ready. These accounts are required for new App Pools and Windows Services. Nodinite v7 uses a new encryption/decryption mechanism. Ensure you have access to all secrets, event hub connection strings, and storage connection strings before starting the upgrade.

Prerequisites

Before starting the update:

• Inform end-users about the update and potential downtime.
• Existing Nodinite v6 installation with Monitoring Agents and Log Agents (configurations will be migrated).
• Backup databases and configuration files to prevent data loss.
• Administrator access to the Nodinite Application Server.
• PowerShell 7 installed with execution policy set to Unrestricted or ByPass (guide).
• PowerShell 7 script user must be a sysadmin on the SQL Server instance for database migrations.
• Nodinite 7 contract and product key available in the Portal. Contact your partner or Nodinite Support if needed.
• .NET 9.0 - Install .NET Runtime 9.0.x AND ASP.NET Core Runtime 9.0.x (Hosting bundle).
• DacFX installed for database migrations.
• IIS Management Scripts and Tools installed for managing IIS during the update.
• Stop the Pickup Log Events Service before starting (the Log API address and configuration database name change during update).

Estimated time

The update process includes:

1. Register the Environment in the Portal.
2. Download and update Core Services.
3. Export the Monitoring Agent information.
4. Import the Monitoring Agents to the Portal.
5. Download and update Monitoring Agents.

Typical completion time: a few minutes including all Monitoring Agents and Log Agents.

Step 1: Register Environment

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

1. Navigate to the existing Customer entry.
   
   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.
   
   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.
   
   Example of the Add Environment button in the Nodinite Portal.

4. A modal appears; The default target run-time platform is Windows. Each has its own tab. At the time of this writing, only the Windows tab is available. Click on the Upgrade from Nodinite 6 button.
   
   Example of the Upgrade from Nodinite v6 button in the 'Add Environment' modal.

5. The modal changes and presents mandatory steps to follow in the specified order.

Configure Nodinite 7 variables

💡Configure the necessary variables for the Nodinite 7 environment.

Set required variables for your environment. Configuration values are difficult to change later—they're embedded in app pools, folders, and databases. Use placeholders if unsure; you can override them when running the PowerShell script.

Configure Database Settings

💡Configure the database settings for Nodinite 7.

Choose your database configuration:

1. Standalone - Single SQL Server instance (Standard, Enterprise, Express, or failover clusters).
2. Always on - SQL Server Always On Availability Group for high availability.
3. Azure - Managed Instance - Azure SQL Managed Instance (see Connection String guide).
4. Edit Connection String Manually - Custom configuration.

Step 2: Save

💡Persist your settings.

Review all settings carefully, then click Save. When successful, the Next button will be enabled.

Step 3: Review

💡Review settings using a visual graph before downloading binaries.

Review your settings before downloading. Click Overview to display a Mermaid diagram of your configuration.

Example of the updated Environment configuration.

Step 4: Download Binaries

Click Download Core to download the Nodinite 7 binaries.

Download Core binaries button.

A progress screen will display while the ZIP package is generated.

Downloading Nodinite Binaries screen.

Step 5: Run PowerShell 7 Script

💡Run the PowerShell 7 script to update your environment.

1. Stop and Disable the Pickup Log Events Service Windows Service (prevents data loss during update).

2. Open a PowerShell 7 terminal with administrative privileges.

3. Navigate to the folder where you extracted the downloaded ZIP file.

4. Run the script:

   dir -r | unblock-file
   .\Core-services-Only.ps1
   

   Important

   If you provided placeholder values in the portal, override them via script parameters (use tab completion). For passwords, use SecureString: $pwd = ConvertTo-SecureString 'P@ssw0rd' -AsPlainText -Force, then pass as -WebClientServiceAccountPassword $pwd. Use single quotes for account names to handle special characters.

5. Open the Web Client and perform some basic checks to ensure the update was successful.

6. Update all Alarm Plugins; the address to the Web Client might have changed.

7. Head back to the Nodinite Portal and proceed to the next step.

Warning

Critical: Non-Events Monitoring Will Fail Until URIs Are Updated

If you use the Non-Events Monitoring Agent, be aware that all monitoring configurations will fail until you update the Log View API URIs. This is because:

• Nodinite v7 changes the Web API base URL structure (different ports, paths, and environment names)
• Each Non-Events configuration (both Non-Events and ACK/NAK types) stores the Log View API URI pointing to specific Log Views
• These URIs reference the old v6 Web API endpoints which no longer exist after upgrade
• The Non-Events agent cannot automatically update these URIs—you must manually update each configuration

What you need to do:

1. ✅ Complete the Nodinite v7 core services update (Steps 1-5)
2. ✅ Update the Non-Events Monitoring Agent to v7 (Steps 9-10)
3. ✅ Open the Web Client and navigate to each Non-Events configuration
4. ✅ Update the Log View API URI in each configuration: Open the Log View in the v7 Web Client, copy the new API URI using the "Copy API URI" feature, and paste the new URI into the Non-Events configuration's "Log View API URI" field
5. ✅ Save each configuration
6. ✅ Force a sync or wait for the next scheduled sync to verify monitoring resumes

Impact if not updated:

• ❌ Non-Events monitoring will report errors or show no data
• ❌ ACK/NAK correlation monitoring will fail
• ❌ Alerts for missing/delayed messages will not trigger
• ❌ Monitor Views showing Non-Events Resources will display error states

See the Non-Events Configuration guide for detailed instructions on updating Log View API URIs. This same issue affects the Pickup Log Events Service which also requires URI updates (see Step 5 above).

Step 6: Remove Nodinite Core Services

💡Remove old Nodinite Web Applications for Core Services.

Navigate to IIS Manager and remove old Nodinite Core Services applications (Update Tool, Web Client, Web API, Log API). With the new product key, old applications are no longer operational.

1. Open IIS Manager on the Nodinite Application Server.
2. Expand the server node, then Sites.
3. Locate the site hosting old Nodinite applications (typically under Default Web Site).
4. Right-click each old application (e.g., /Nodinite/ENV/WebClient, /Nodinite/ENV/WebAPI, /Nodinite/ENV/LogAPI, /NodiniteUpdate/UpdateClient) and select Remove.
5. Delete the old application folders.
6. Remove old application pools.

Note

If you had another Web Site for the Web Client to enable SSL, you must also remove this application and possibly its Web site. You can re-add SSL in a later step by adding the host name and thumbprint to the Nodinite Portal.

Step 7: Export Monitoring Agent Info

💡Export the Monitoring Agent information for the next step.

In this step, you will export information about the Monitoring Agents; the output is JSON. This information will be used in the next step to help update also the Monitoring Agents for use with your updated Nodinite 7 environment.

• Open the Web Client and navigate to the Tools section in side bar.
• Click the Export Monitoring Agents button to export the information.
  
  Example of the Export Monitoring Agents button in the Tools section.

A modal will appear, the important piece of information is the 'UniqueId' that was set during the update process on each Monitoring Agent.

Example of the Export Monitoring Agents modal.

Click the on the Text area to copy the information to the clipboard. Be careful if you change the information in the text area, as it is used in the next step to import the Monitoring Agents information.

Head back to the Nodinite Portal and proceed to the next step.

Step 8: Import Monitoring Agents

💡Import the Monitoring Agents information to the Nodinite Portal.

In this step, you will import the Monitoring Agents information that you exported in the previous step.

• Review the information you copied to ensure it is correct. For example, Agents installed on remote servers shoud NOT be included in the import. If you have Agents installed on other servers, you will continue to update these using the MSI installer packages as you have done in the past. The update process does not affect these installations.
• Paste the possibly edited information into the text area and click the 'Upload & Save' button.
  
  Example of the Import Monitoring Agents JSON text area.
• A confirmation message appears, indicating that the Monitoring Agents information has been successfully imported.
• Click the 'Next' button to proceed with the next step.

Step 9: Download and Update Monitoring Agents

💡Download and update the Monitoring Agents for Nodinite 7 using the default ports and the common service account. If you have the need to change these; continue with the Use Custom Ports And Specific Service Accounts sub step.

In this step, you will download the updated Monitoring Agents for Nodinite 7 with default settings and install them in your environment. The process is similar to the previous steps, but now you will download the Monitoring Agents specifically for Nodinite 7. The current Windows Service based Monitoring Agents will be replaced with the new ones hosted in IIS.

Example of the Download Monitoring Agents button.

Use Default Ports

• The ports are set to the default values, but you can change them later if needed. Changing the ports will require you to update the IIS bindings and the Nodinite Portal settings.
• Click the 'Download Monitoring Agents' button to start the download process.
• Once the download is complete, extract the ZIP file to a folder on your Nodinite Application Server.
• Open a PowerShell 7 terminal with administrative privileges.
• Navigate to the folder where you extracted the downloaded ZIP file.
• Run the script:

dir -r | unblock-file
.\Core-Services-and-Agents.ps1

Once the script has completed successfully, you can open the Web Client and perform some basic checks to ensure the update was successful.

• In the Portal, click the 'Next' button to exit the update process.
• In the Nodinite Portal, you can now manage your updated environment and the Monitoring Agents.
  
  Example of the Edit Environment Overview page in the Nodinite Portal for a Windows Server run-time.

Important

You should NOT change the Environment Name or the Destination Root Path after the update process has completed. If you need to change these values, you must remove the environment and start over. Contact your Partner or Nodinite Support if you need help on this matter. Changing ports also requires you to update the IIS bindings and the Nodinite Portal settings

Use Custom Ports And Specific Service Accounts

💡A guide for changing ports and service accounts.

If you need to change the ports or use specific service accounts for the Monitoring Agents, follow these steps:

• Click on the 'Next' button to continue thus exiting the update process.
• Click on the 'Agents' tab to access the Monitoring Agents settings.
  • Change ports and service accounts as needed.
• Click the 'Save' button to save your changes.
• Close the Environment modal.
• Click the 'Actions' button and select Download (Now, the Package includes Core Services and selected Agents).
• Extract the ZIP file to a folder on your Nodinite Application Server.
• Open a PowerShell 7 terminal with administrative privileges.
• Navigate to the folder where you extracted the downloaded ZIP file.
• Run the script:

dir -r | unblock-file
.\Core-Services-and-Agents.ps1

Step 10: Remove Old Monitoring Agents

💡Remove old Nodinite Windows Services on the Nodinite Application Server.

In this step, you will remove the old Nodinite Windows Services. This is important to prevent conflicts and ensure that only the new IIS-hosted Monitoring Agents are active.

Note

If you have installed Agents on other servers, you will continue to update these using the MSI installer packages as you have done in the past. The update process does not affect these installations.
❗This might change in future releases.

Use the following PowerShell 7 script to generate a script that will stop and remove all services matching "Nodinite*". The generated script will skip services that cannot be queried due to permission errors.

# PowerShell 7 Script to generate Remove-Nodinite-Services.ps1
# The generated script stops and deletes all services matching "Nodinite*"
# Skips services that cannot be queried due to permission errors

try {
    $services = Get-Service | Where-Object { $_.Name -like "Nodinite*" }
} catch {
    Write-Warning "Some services could not be queried due to permission errors. Continuing with available services."
    $services = @()
}

# Filter out services that are not accessible
$nodiniteServices = @()
foreach ($service in $services) {
    try {
        $null = $service.Status
        $nodiniteServices += $service
    } catch {
        Write-Warning "Skipping service '$($service.Name)' due to permission error."
    }
}

$outputScript = "Remove-Nodinite-Services.ps1"

# Start of the generated script
$header = @"
# Auto-generated script to stop and remove Nodinite Windows services
# Generated on $(Get-Date -Format "yyyy-MM-dd HH:mm:ss")
`n
"@

Set-Content -Path $outputScript -Value $header

# Add per-service commands
foreach ($service in $nodiniteServices) {
    $serviceName = $service.Name
    $entry = @"
Write-Host "Stopping service: '$serviceName'"
Stop-Service -Name '$serviceName' -Force
Write-Host "Removing service: '$serviceName'"
sc.exe delete '$serviceName'

"@
    Add-Content -Path $outputScript -Value $entry
}

Write-Host "Script generated: $outputScript"

Example of the PowerShell 7 script to generate 'Remove-Nodinite-Services.ps1' script file.

Open the generated Remove-Nodinite-Services.ps1 script in a text editor to review its contents. Ensure that it includes commands to stop and delete all services matching "Nodinite*". If there are any services you do not want to remove, you can manually edit the script to exclude those services.

Open a PowerShell 7 terminal with administrative privileges and run the generated script:

.\Remove-Nodinite-Services.ps1

Note

This script merely stops and removes the services. It does not delete any files or folders associated with the old services. You will need to manually delete these files and folders if they are no longer needed.

Verify that all old Nodinite Windows Services have been stopped and removed successfully. You can do this by checking the list of services in the Services management console.

Step 11: Reconfigure Pickup Log Events Service

💡Reconfigure the Nodinite Pickup Log Events Service to point to the new address of the Log API and configuration database.

There is no in-place update for the Nodinite Pickup Log Events Service, please follow the instructions in the Installation v7 documentation to install the latest version of the Pickup Log Events Service Logging Agent.

Note

With the update, the address of the Log API has now changed.

Step 12: Verify Functionality

💡Perform basic checks to ensure the update was successful.

1. Open the Web Client and perform some basic checks to ensure the update was successful. Check that all servics are running, and that you can access the Web Client, Web API, Log API, Logging Service, and Monitoring Service without issues.
2. Verify that all Monitoring Agents are listed and have the correct status in the Web Client.
3. Check the logs for any errors or warnings that might indicate issues with the update process.
4. If you encounter any issues, refer to the logs and documentation for troubleshooting steps. You can also contact your Partner or Nodinite Support for assistance.

Step 13: Remove Old Files and Folders

Example of old files and folders to delete on the Nodinite App Server.

Important

Do NOT remove the folder with the name of the Environment you just updated. This folder contains the new installation of Nodinite 7. Only remove the old folders that are no longer needed.

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

Migrating to version 7 of the Pickup LogEvents Service Logging Agent

Related Topics

Update Nodinite v7