- 8 minutes to read

Uninstall Nodinite v7

Uninstall Nodinite v7 with the same CLI, Nodinite.Installer.Cli.exe, that installed it. Whether you decommission an Environment, troubleshoot, switch the authentication method, or need a fresh start, this page shows which command to run and what to clean up afterwards.

What you'll achieve by following this guide:

  • ✅ Remove the Nodinite Core Services and agents from the Nodinite server with IIS
  • ✅ Optionally keep your databases for a later reinstall
  • ✅ Use CLI commands for a predictable uninstall and teardown
  • ✅ Leave your environment ready for a fresh install or upgrade

Tip

By default, the CLI keeps the databases and configuration files, so that you can reinstall Nodinite v7 later. For a complete removal, use the delete options below.

Understanding the Uninstall Options

flowchart TD Q{"What do you remove?"} -->|"One agent"| UA["fa:fa-plug uninstall-agent
--agent"] Q -->|"Core Services only"| UN["fa:fa-microchip uninstall"] Q -->|"Agents, then Core Services"| TD["fa:fa-trash teardown-environment"] UN --> D{"Delete the data too?"} TD --> D D -->|"No"| KEEP["fa:fa-database Databases and settings kept
for a reinstall"] D -->|"Yes"| DRY["fa:fa-flask Run with --dry-run first"] DRY --> DEL["fa:fa-triangle-exclamation --delete-databases, --delete-settings
--confirm with the Environment name"] style Q fill:#2678BD,color:#fff style UA fill:#E47528,color:#fff style UN fill:#E47528,color:#fff style TD fill:#E47528,color:#fff style D fill:#2678BD,color:#fff style KEEP fill:#93d16d style DRY fill:#FFD525 style DEL fill:#c33d34,color:#fff

Diagram: choose the command (orange) by what you remove. Without delete options, the Configuration Database, the Log Databases, and the settings stay (green). Deleting them is destructive (red): run a dry run first (yellow) and confirm with the Environment name.

Uninstall commands

Run Nodinite.Installer.Cli.exe from an elevated PowerShell 7 prompt in the extracted ZIP bundle root, the same bundle layout as in Step 7. nodinitesrv01 is an example server folder name.

Start by inspecting the command help:

.\Nodinite.Installer.Cli.exe teardown-environment --help

Important

With --delete-databases or --delete-settings, --confirm is required and must match the loaded Environment.Name in config.cli.json. --force cannot bypass this confirmation.

Uninstall the Core Services:

.\Nodinite.Installer.Cli.exe uninstall --config .\nodinitesrv01\config.cli.json

uninstall removes the Core Services only; it does not remove agents.

Remove Database Option

Tip

To remove the databases and settings too, add the delete options. --delete-databases drops every Nodinite database configured for the Environment in the Portal: the Configuration Database, the Log Databases, and the agent databases (such as the Monitoring Database of the Azure Logic Apps agent).

.\Nodinite.Installer.Cli.exe uninstall --config .\nodinitesrv01\config.cli.json --delete-databases --delete-settings --confirm "NAMEOFENV" --force

Important

Dropping a database is destructive: you lose all configuration and data of the Repository Model, logging, and monitoring. Make sure you have backups if you need to keep any data.

Remove Settings Files

Tip

You can remove the settings independently.

.\Nodinite.Installer.Cli.exe uninstall --config .\nodinitesrv01\config.cli.json --delete-settings --confirm "NAMEOFENV" --force

Remove one agent

Use uninstall-agent to remove one agent:

.\Nodinite.Installer.Cli.exe uninstall-agent --config .\nodinitesrv01\config.cli.json --agent AzureLogicApps --force

Remove complete environment

Use teardown-environment to remove the agents first and then the Core Services:

.\Nodinite.Installer.Cli.exe teardown-environment --config .\nodinitesrv01\config.cli.json

Use destructive removal only when you intend to delete the databases and settings too:

.\Nodinite.Installer.Cli.exe teardown-environment --config .\nodinitesrv01\config.cli.json --delete-databases --delete-settings --confirm "NAMEOFENV" --force

Use --skip-deregistration when you decommission the Portal side or cannot deregister the agents from the Web API during teardown:

.\Nodinite.Installer.Cli.exe teardown-environment --config .\nodinitesrv01\config.cli.json --skip-deregistration

Run a dry run before a destructive teardown:

.\Nodinite.Installer.Cli.exe teardown-environment --config .\nodinitesrv01\config.cli.json --delete-databases --delete-settings --confirm "NAMEOFENV" --dry-run

Useful flags from --help for automation and restricted environments:

  • --non-interactive for CI/CD-style execution
  • --database-connection-string and --agent-connection-string to avoid prompts during database deletion (passing arguments)
  • --accept-legacy-database to drop agent databases with pre-v7 names left from a v6 upgrade
  • --proxy-mode, --proxy-url, and the related proxy flags for controlled network egress

After Uninstallation - Optional Cleanup

The CLI doesn't remove everything around Nodinite. Review the following, especially when you permanently decommission an Environment, for security and compliance.

Azure AD (Entra ID) Cleanup

If the Environment used OAuth 2.0 / OIDC with Microsoft Entra ID, remove the app registrations it no longer needs:

  1. Remove app registrations:

  2. Revoke admin consent if the app registrations stay:

    • When other Environments still use the app registrations, review and revoke the permissions granted to the uninstalled Environment.
    • Go to Enterprise applications > select each app > Permissions > Revoke admin consent.

SQL Server Cleanup

If you kept the databases (no --delete-databases), you may want to clean up related SQL Server objects:

  • SQL logins: remove SQL logins or Windows accounts created only for the Nodinite services.
  • SQL Server Agent jobs: remove Nodinite-related jobs that are no longer needed.
  • Backup jobs: remove or update backup jobs, maintenance plans, and third-party backup configurations for the Nodinite databases (Configuration Database, Log Databases, Agent Database).
  • Linked servers: remove Linked Servers configured for Nodinite, for example between the Configuration Database and the Log Databases.
  • Service Principal Names (SPNs): remove SPNs registered for Nodinite service accounts for Kerberos.
  • Orphaned database users: if you deleted the databases, check other databases for orphaned Nodinite users.

Windows Service Accounts and Permissions

Review the Windows service accounts and permissions configured for Nodinite:

  • Service accounts: remove or disable dedicated service accounts, such as the identities of the IIS application pools of the Core Services; for gMSA accounts, ask your AD administrators.
  • Local security policies: remove the Logon as a Service right (SeServiceLogonRight) from the Nodinite service accounts.
  • IIS_IUSRS group: remove the Nodinite service accounts from the local IIS_IUSRS group.
  • Local Administrators group: remove the Nodinite service accounts if they were added.
  • File system permissions: review and remove custom NTFS permissions on the install folders (typically C:\Program Files\Nodinite\).

IIS Application Pool Cleanup

On Windows Server, every Core Service is its own IIS web site with its own application pool and port. After the uninstall, check IIS Manager for leftovers:

Certificate Cleanup

If you used HTTPS/TLS certificates only for this Nodinite Environment (Core host Configuration):

  • IIS bindings: remove the HTTPS bindings that served the Core Services.
  • Certificate store: consider removing the certificate from LocalMachine\WebHosting or LocalMachine\My if it was issued only for this instance; also remove the Secret Management certificate when the Environment is gone for good.
  • DNS records: update or remove DNS entries for the Nodinite host name when it is no longer in use.

Firewall and Network Cleanup

  • Firewall rules: remove the Windows Firewall and network firewall rules opened for the Nodinite ports. Each Environment has its own ports; find them in the Portal under Allocated ports, and the rules in the Network and Firewall Overview.
  • Load balancer configuration: update load balancers if Nodinite was part of a load-balanced setup.
  • Monitoring exclusions: remove monitoring exclusions or allowlist entries for the Nodinite endpoints.

Email and Notification Cleanup

If you configured alarms with the Alarm Plugins:

  • Shared mailboxes: reclaim or repurpose shared mailboxes used for Nodinite alerts (e.g. nodinite-alerts@company.com) by the E-mail Alarm Plugin.
  • Distribution lists: update or remove distribution lists used for alert notifications.
  • SMTP relay configuration: remove SMTP relay allowlist entries for the Nodinite servers if IP-based authentication was used.
  • OAuth2 client registrations: if the E-mail Alarm Plugin used OAuth2 for SMTP (e.g. Microsoft 365), remove that client registration.
  • Webhook endpoints: deactivate or remove endpoints used by the HTTP Webhook Alarm Plugin (Teams, Slack, ServiceNow, SMS gateways, and so on).

Monitoring and Logging Agent Cleanup

teardown-environment removes the agents in the package before the Core Services; uninstall doesn't. Make sure that no agent is left behind:

Documentation and Access Control

  • Remove user access: revoke organization-specific access granted for Nodinite Roles.
  • Update documentation: update internal documentation, runbooks, and architecture diagrams.
  • Archive configuration: keep a copy of the configuration files, database backups, and settings for reference or compliance.

Tip

Planning to reinstall? If you uninstall for a clean reinstall or to switch the authentication method, keep the Entra ID app registrations, SQL logins, certificates, and service accounts to simplify the new installation.

Next Steps