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 as 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
You may need to review the steps accordingly if you have multiple Nodinite environments installed on the same server and intend to remove only one. 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 the 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 theC:\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)
- If you keep the other Nodinite instances, you must manually remove the %Environment% JSON object from the
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
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 and delete them individually.
- Make sure to verify the successful removal.
From within the MMC.
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, delete 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
Remember to Check the Close existing connections checkbox
Tip
You do not have to lose any data or configuration. You may re-use the old databases when 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 in use 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 make use of port 8000.
Decommission/remove the no longer required Servers, Licenses, disks, CPUs, IP addresses, DNS names...