- 3 minutes to read

Uninstall

This page provides a comprehensive, step-by-step guide to completely uninstall and remove Nodinite from your environment. Whether you are decommissioning a single instance or your entire integration landscape, follow these instructions to ensure a clean and secure removal.

✅ Remove all Nodinite services, agents, and applications from any environment
✅ Clean up SQL databases, app pools, certificates, and firewall settings
✅ Ensure no residual access rights or resources remain

Nodinite Services and Applications may exist on multiple servers—on-premise and/or in the cloud. As a best practice, generate and print a hard copy of the Overview page before starting the removal steps below.

Removal Steps

Note

You may need to adapt these steps if you have multiple Nodinite environments on the same server and only want to remove one. This guide details a total removal.

  • Stop the Monitoring Service for the environment to be removed.
    • Uninstall from Windows Services using the following command:
        SC delete "%Name of Monitoring Service%"
  • Stop the Logging Service for the environment to be removed.
    • Uninstall from Windows Services using the following command:
        SC delete "%Name of Logging Service%"
  • Stop all Monitoring Agent(s) you intend to remove.
    • Uninstall all Monitoring Agents using the MSI, or "Change or Remove a Program/Uninstall" in Windows.
  • Stop the Nodinite Update Service(s). Only perform this step if this is the last Nodinite instance to remove.
    • If you keep other Nodinite instances, manually remove the %Environment% JSON object from the settings.json file in C:\Program Files\Nodinite\Nodinite Update\UpdateClient\App_Data. Restart the App Pool for the Nodinite Install and Update Tool.
    • Uninstall using the MSI (removes both the IIS Web Application and the Windows Service).

Note

There may be multiple instances of the Nodinite Update Service on different servers (IIS Server with Web Components, Logging Service, Monitoring Service).

  • Stop the Pickup Service if this is the last environment where it is in use.
    • Uninstall using the MSI.

Note

If you used the Pickup Service, update all solutions that sent LogEvents to no longer do so.

  • If you used Log4Net, remove all configurations using the Nodinite Log4Net Appender.
  • Ensure clients no longer push data if you are using the Nodinite LogApi.
  • Stop all Nodinite-related AppPools (for the environment/instance to remove) in IIS.
  • Delete all IIS applications for the environment to remove.
    • Verify successful removal.

From within the MMC.
List Virtual Directories
List to verify the successful deletion.

C:\Windows\System32\inetsrv\appcmd.exe LIST VDIRS

Note

Do not delete the root folder; traverse the tree bottom-up, deleting one by one.

  • Delete the virtual directory either manually or using Powershell:
Remove-WebApplication -Name AppToBeDeleted -Site "Default Web Site"

Powershell example to remove the Web Application AppToBeDeleted from the "Default Web Site".

  • Delete all Nodinite related AppPools for the environment to remove.
  • Delete the folder with the instance to remove from the file system on the IIS server (default c:\Program Files\Nodinite\%EnvironmentName%).
  • Drop all Nodinite related SQL Server databases.

Info

Check the Close existing connections checkbox when dropping databases.

Tip

You do not have to lose any data or configuration. You may re-use the old databases if you re-install Nodinite later.

Info

To remove old backups, check the Delete backup and restore history information for databases option.

  • Remove the environment-specific Linked Servers exclusively used by Nodinite.
  • Remove all associated Nodinite accounts where applicable:
    • SQL Server
    • AD / Local rights
    • Policies
    • File shares
    • Monitoring related access rights (BizTalk Server, SQL, MSMQ, ActiveMQ, Azure, IBM Datapower, FTP, ...)

      Review settings using Local Security Policy, Computer Management | Local Users and Groups

  • Remove Nodinite-specific certificates.
  • Re-adjust firewall settings; Nodinite by default uses port 8000.
  • Decommission/remove any no longer required servers, licenses, disks, CPUs, IP addresses, DNS names, etc.

Next Step

Install Nodinite

Administration