- 4 minutes to read

Release Notes

Install and Migrate the Pickup Log Events Agent on Nodinite 7.1.x

Note

This document applies to version >= 7.1.x

You install or migrate the Nodinite Pickup Log Events Service Logging Agent here for Nodinite 7.1.x. This version unifies end-to-end logging and monitoring with a GUI driven Remote Configuration experience and stronger encryption. Read this page before you touch production so you plan a smooth, low‑risk change.

✅ Faster operational insight with unified Monitoring Agent behavior
✅ Remote Configuration replaces manual file edits for safer change control
✅ Stronger encryption (requires re-entering secrets) hardens security
✅ Updated Log API and Configuration Database naming improves clarity
✅ IIS hosted model aligns with the broader Nodinite 7 deployment standard

You must already run Nodinite 7 (latest available) before you install or migrate the Nodinite Pickup Log Events Service Logging Agent. If you upgrade from <=7.0.8 expect a short delay in inbound logging while you transition. Inform stakeholders early.

Step 1: Prepare (Assess & Uninstall Legacy)

  • Identify the currently installed Nodinite Pickup Log Events Service Logging Agent version. If it is ≤7.0.8 you stop it and uninstall it. Keep a safe backup copy of the old installation folder (for reference only).
  • Record or export all existing connection details. The encryption format changed and is not backwards compatible; you must re-enter every secret, password and connection string.
  • Confirm you have required platform access (IIS admin, local admin, database access, Log API access).
  • Notify stakeholders about the expected brief logging gap during the cutover.
  • Decide a rollback point (for example snapshot or database backup) before you continue.

Step 2: Ensure Platform Currency

Step 3: Verify the Log API

  • Identify the new Nodinite 7 Log API base URL (it changed from version 6).
  • Open the Log API endpoint in a browser or use a simple health probe to ensure it responds (HTTP 200 / status OK).
  • Document the URL; you need it while updating each configuration referencing the Log API.

Step 4: Satisfy Runtime Prerequisites

  • Install the required .NET 9.0 Runtime and ASP.NET Core Hosting Bundle.
  • Restart IIS after the installation to load the new runtime.
  • Confirm the server time, TLS settings and outbound firewall rules allow secure communication with related systems.

Step 5: Install the New Agent (IIS Hosted)

Step 6: Configure through Remote Configuration

Remote Configuration replaces manual JSON file edits and enforces validation, reducing human error. Perform these updates:

  1. Add (or re-add) the Pickup configuration. If migrating, open the old settings.json (from your backup) in read-only mode and copy values across manually.
  2. Update each reference to the Configuration Database: rename from NodiniteConfig_<EnvironmentName> to Nodinite_<EnvironmentName>_Config.
  3. Update each Log API endpoint to the new Nodinite 7 URL you verified earlier.
  4. Re-enter all secrets: passwords, API keys, certificates, connection strings. (Previous encryption format cannot decrypt them.)
  5. Save and apply; confirm the Web Client reports a successful configuration load.
  6. Optionally tag or annotate the configuration with a change ticket reference for auditability.

Step 7: Validate Functionality

  • Trigger a controlled test event source and confirm the Pickup Log Events Agent forwards entries into the central log, you should be able to use your existing Log Views (for example, search for a unique correlation ID).
  • Check Monitoring dashboards for agent heartbeat and metrics.
  • Review Windows Event Log (Application + System) for warnings or errors.
  • Confirm no stale connections point to the legacy database name or old Log API URL.
  • Validate time stamps and environment naming conventions in the produced log events.

Step 8: Optimize and Harden

  • Enable only required Pickup sources; disable unused listeners to reduce noise and attack surface.
  • Apply least privilege on the service account (no interactive logon, log on as a service only).
  • If using custom certificates, verify expiration dates and ensure private keys are protected.
  • Document the new configuration baseline (store in internal CMDB or runbook).

Step 9: Clean Up Legacy Artifacts

  • After successful validation (and if you migrated from ≤7.0.8) delete the OLD installation folder.
  • Remove obsolete diagnostic files and the former settings.json to avoid future operator confusion.
  • Update internal documentation links pointing to outdated paths.

Support

Contact Support for advanced troubleshooting. Provide environment name, agent version, recent change summary and any relevant Windows Event Log entries.

Next Steps