- 3 minutes to read

Uninstall

This page describes how to remove all parts of Nodinite altogether.

Nodinite services and applications may exist on multiple servers, on-premise and/or in the cloud. A report of all the installed services and applications is available for users part of the built-in Administrator role.

  • Please print/make a hard copy of the Overview page before performing the removal steps below.

Removal Steps

NOTE: If you have multiple Nodinite environments installed on the same server and intend to remove only one of them, you may need to review the steps accordingly. The 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) that you intend to remove.

    • Uninstall all Monitoring Agents using MSI or "Change or Remove a Program/Uninstall" within Windows
  • Stop the Nodinite Update Service(s). Perform this step only if this is the last Nodinite instance to remove.

    • If you keep the other Nodinite instances, you must manually remove the %Environment% JSON object from the settings.json file in the C:\Program Files\Nodinite\Nodinite Update\UpdateClient\App_Data folder. Restart the App Pool for the Nodinite Install and Update Tool.
    • Uninstall using the MSI (this step removes both the IIS Web Application and the Window 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 were using the Pickup Service, you would need to alter all the solutions that sent LogEvents to no longer do so.

  • If you were using Log4Net, now remove all configurations using the Nodinite Log4Net Appender

  • If you were using the LogApi, make sure clients no longer push data

  • Stop all Nodinite related AppPools (for the environment/instance to remove) in IIS

  • Delete all IIS applications for the environment to remove, delete them one by one.

    • Make sure to verify the successfull removal.

From within the MMC.
List Virtual Directories
Verify successful deletion

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

NOTE: Do not delete the root folder, traverse the tree bottom-up, delete one by one

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

Powershell example to remove the Web Application AppToBeDeleted from "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

    Note1: Remember to Check the Close existing connections checkbox

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

  • Remove the 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, ...
  • Remove Nodinite specific certificates

  • Re-adjust firewall settings; Nodinite by default uses port 8000.

  • Decommission/remove the no longer required Servers, Licenses, disks, CPUs, IP addresses, DNS names...

Next Step

Install Nodinite

Administration