- 0 minutes to read

Uninstall Nodinite v7

Uninstalling Nodinite v7 is a straightforward process designed to help you quickly remove all Nodinite components from your environment. This guide walks you through each step, ensuring a clean and hassle-free experience. Whether you are upgrading, troubleshooting, or simply need a fresh start, you’ll find all the details here.

What you’ll achieve by following this guide:

  • ✅ Remove all Nodinite Core Services and Agents efficiently
  • ✅ Optionally retain your databases for future use
  • ✅ Use a single PowerShell script for a seamless uninstallation
  • ✅ Ensure your environment is ready for a fresh install or upgrade

Tip

You can keep your existing databases and configuration files if you plan to reinstall Nodinite v7 later. If you want to remove everything, including the databases, use the -DeleteDatabase parameter in the uninstallation script.

When you download the Nodinite v7 binaries (single ZIP file), you will find a PowerShell script named Nodinite7-%ENVIRONMENTNAME%-UnInstall.ps1. This script is your key to uninstalling Nodinite v7 from your environment with minimal effort.

Uninstall Script

To uninstall Nodinite v7, use the provided PowerShell 7 script. This script actively removes all Nodinite Core Services and Agents from your environment, ensuring no residual files are left behind.

  • Open a PowerShell 7 terminal with administrative privileges.
  • Navigate to the folder where you extracted the downloaded ZIP file containing the Nodinite binaries.
  • Unblock the script to allow execution:
  dir -r | unblock-file
  • Run the uninstallation script by executing the following command.
.\Nodinite7-%ENVIRONMENTNAME%-UnInstall.ps1

Remove Database Option

Tip

If you want to remove the database as well, use the -DeleteDatabase parameter.

  dir -r | unblock-file

.\Nodinite7-%ENVIRONMENTNAME%-UnInstall.ps1 -DeleteDatabase

Important

Dropping a database is a destructive action and you will lose all configurations and data from the Repository, Logging and Monitoring. Ensure you have backups if you need to retain any data.

Remove Settings Files

Tip

If you want to remove the settings files as well, use the -DeleteSettingsFile parameter.

.\Nodinite7-%ENVIRONMENTNAME%-UnInstall.ps1 -DeleteSettingsFile

After Uninstallation - Optional Cleanup

After running the uninstall script, consider cleaning up related configurations and resources that are not automatically removed. This is especially important for security and compliance when permanently decommissioning a Nodinite environment.

Azure AD (Entra ID) Cleanup

If you configured OpenID Connect authentication with Azure AD, you may want to remove the app registrations to maintain security hygiene:

  1. Remove App Registrations (if no longer needed):

    • Navigate to Azure Portal > Microsoft Entra ID > App registrations
    • Delete the following applications if they were created for this Nodinite environment:
      • webApi (or your custom name)
      • webClient (or your custom name)
      • NodiniteInstallationClient (or your custom name)
    • This removes client secrets, certificates, and prevents unauthorized access attempts

  2. Revoke Admin Consent (if app registrations remain):

    • If keeping app registrations for other environments, review and revoke any permissions granted to the uninstalled environment
    • Navigate to Enterprise applications > select each app > Permissions > Revoke admin consent

See also: Register Nodinite Applications in Azure AD (Entra ID) with OpenID for reference

SQL Server Cleanup

If the databases were retained (no -DeleteDatabase parameter), you may want to clean up associated SQL Server objects:

  • SQL Logins - Remove SQL logins or Windows accounts that were created specifically for Nodinite services
  • SQL Server Agent Jobs - Check for any Nodinite-related SQL Agent jobs and remove if no longer needed
  • Backup Jobs - Remove or update SQL Server backup jobs, maintenance plans, or third-party backup software configurations that were backing up Nodinite databases (Configuration Database, Log Databases, Agent Database)
  • Linked Servers - Remove linked servers that were configured for Nodinite agents (e.g., BizTalk logging, database monitoring)
  • Service Principal Names (SPNs) - Remove SPNs registered for Nodinite service accounts if they were created for Kerberos authentication across distributed environments
  • Orphaned Database Users - If databases were deleted, check for orphaned database users in other databases

Windows Service Accounts and Permissions

Review and clean up Windows service accounts and permissions that were configured for Nodinite

  • Service Accounts - Remove or disable dedicated Windows service accounts created for Nodinite services (IIS App Pools, Monitoring Service, Logging Service)
  • Local Security Policies - Remove "Log on as a service" rights (SeServiceLogonRight) for Nodinite service accounts
  • IIS_IUSRS Group - Remove Nodinite service accounts from the local IIS_IUSRS group
  • Local Administrators Group - Remove Nodinite service accounts from local administrators if they were added
  • File System Permissions - Review and remove custom NTFS permissions on installation folders (typically C:\Program Files\Nodinite\)

IIS Application Pool Cleanup

If Nodinite was installed with IIS components:

  • Application Pools - Remove dedicated IIS Application Pools for Nodinite Web Client, Web API, and Log API
  • Virtual Directories - Delete IIS virtual directories and applications for Nodinite components
  • IIS Bindings - Remove HTTP/HTTPS bindings configured for Nodinite websites

Certificate Cleanup

If you configured HTTPS/TLS certificates specifically for Nodinite v7:

  • IIS Bindings - Remove HTTPS bindings from IIS that were configured for Nodinite Web Client or Web API
  • Certificate Store - Consider removing certificates from the Windows Certificate Store if they were purchased/created solely for this Nodinite instance
  • DNS Records - Update or remove DNS entries pointing to the Nodinite server if the hostname is no longer in use

Firewall and Network Cleanup

  • Firewall Rules - Remove Windows Firewall or network firewall rules that were opened for Nodinite services (default ports: 41000, 50000, 41002)
  • Load Balancer Configuration - Update load balancer configurations if Nodinite was part of a load-balanced setup
  • Monitoring Exclusions - Remove any monitoring exclusions or whitelist entries for Nodinite endpoints

Email and Notification Cleanup

If you configured email alerts or webhook notifications:

  • Shared Mailboxes - Reclaim or repurpose shared mailboxes that were used for Nodinite alerts (e.g., nodinite-alerts@company.com)
  • Distribution Lists - Update or remove email distribution lists used for alert notifications
  • SMTP Relay Configuration - Remove SMTP relay whitelist entries for Nodinite servers if IP-based authentication was used
  • OAuth2 Client Registrations - If using OAuth2 for SMTP (e.g., Microsoft 365), remove the OAuth2 client registration for the Email Alarm Plugin
  • Webhook Endpoints - Deactivate or remove webhook endpoints configured for third-party integrations (Teams, Slack, ServiceNow, SMS gateways, etc.)

Monitoring and Logging Agent Cleanup

Before uninstalling Nodinite Core Services, ensure all monitoring and logging agents are properly cleaned up:

Documentation and Access Control

  • Remove User Access - Revoke access for users who were granted Nodinite-specific roles in your organization
  • Update Documentation - Update internal documentation, runbooks, and architecture diagrams to reflect the removed Nodinite installation
  • Archive Configuration - Save a copy of your Nodinite configuration files, database backups, and settings for reference or compliance requirements

Tip

Planning to reinstall? If you're uninstalling to perform a clean reinstall or upgrade, you may want to keep Azure AD app registrations, SQL logins, certificates, and service accounts in place to simplify the new installation process.

Next Step

Nodinite Portal

Update Nodinite v7
Install Nodinite v7