- 3 minutes to read

Step 13: Final Cleanup

Delete the old v6 Monitoring Agent folders and files. In v6, every agent had its own MSI installer, and the admin could choose any installation path, so the folders may be on different drives or under different roots, not only under C:\Program Files\Nodinite\.

Prerequisites

Tip

Before remove-legacy, Step 9 (Remove legacy v6 IIS applications and Windows services) saved each v6 service's folder to Nodinite-AgentFolders.txt; use that list. Without it, compare with the agents you exported in Step 5.

Important

If several environments share this server, remove only the folders of the environment you just migrated.

Folders to Keep and Delete

Nodinite program folder with v6 agent folders and the v7 environment folder
Example of a Nodinite program folder with the old v6 Monitoring Agent folders next to the v7 environment folder.

Keep These Folders

  • <EnvironmentName> (e.g., DEV, PROD) – contains the v7 installation
  • Monitoring Agent - DataPower and Monitoring Agent - Dynamics CRM – the IBM DataPower and Dynamics CRM agents stay on the MSI-based installer

Delete These Folders

In v7, the Portal package installs the agents as IIS web sites, so these v6 Windows service folders are no longer used:

  • Agent - Azure and Agent - Azure Logic Apps
  • Monitoring Agent - Database
  • Monitoring Agent - File Folder
  • Monitoring Agent - IBM MQ
  • Monitoring Agent - Log File Parser
  • Monitoring Agent - Message Queueing
  • Monitoring Agent - Microsoft BizTalk Server
  • Monitoring Agent - Mule
  • Monitoring Agent - Non Events
  • Monitoring Agent - RabbitMQ
  • Monitoring Agent - Web Services
  • Monitoring Agent - Windows Server
  • Nodinite Update – the old update service folder; delete it only when every environment on this server runs v7

Note

Delete only folders that exist; not every environment has every agent.

Steps

  1. Verify that all v7 services run correctly, and test logging, monitoring, and alerting.
  2. Open Nodinite-AgentFolders.txt and remove the paths of environments you are not cleaning up, and of the IBM DataPower and Dynamics CRM agents.
  3. Delete each listed folder.
  4. Delete the Nodinite Update folder if every environment on this server runs v7.
  5. Do NOT delete the <EnvironmentName> folder with your v7 installation.
  6. Empty the Recycle Bin when you are satisfied.

Optional: Delete Using PowerShell 

# Review first — open the file and verify paths before running
Get-Content .\Nodinite-AgentFolders.txt

# Delete each folder listed in the file
Get-Content .\Nodinite-AgentFolders.txt | ForEach-Object {
    if (Test-Path $_) {
        Write-Host "Removing: $_"
        Remove-Item -Path $_ -Recurse -Force
    } else {
        Write-Host "Not found (already removed or never existed): $_"
    }
}

Important

Always review Nodinite-AgentFolders.txt before you run the script.

Completion Checklist

  • Old v6 agent folders removed; IBM DataPower and Dynamics CRM folders kept
  • Nodinite Update folder removed (when all environments run v7)
  • Environment folder (e.g., DEV) preserved
  • v7 still works after the cleanup

Troubleshooting

Accidentally Deleted Environment Folder

You removed the environment folder (e.g., DEV) instead of an agent folder. Do the following:

  • Stop removing files
  • Restore from backup if available
  • Download the package again and rerun the CLI deployment to reinstall v7; see Update Nodinite v7
  • Read the Support page

v7 Not Working After Cleanup

Services fail after you removed old folders. Check the following:

  • You didn't remove the environment folder
  • The IIS application pools are running
  • Event Viewer for errors; restore from backup if needed

Cannot Find Old Monitoring Agent Folders

Listed folders don't exist in your installation. This is normal: each environment has different agents, so skip the missing ones.

Next Steps