What changed, and when.

• Your mail server’s password could be sent unencrypted. The setting that chose encryption had only two positions, and the off position meant “encrypt if the server offers it” — if it did not, AI NetRiva carried on and sent your username and password in readable form, without saying so. You now choose explicitly between STARTTLS, TLS, and none, and STARTTLS refuses to send rather than quietly falling back. Existing setups keep working exactly as they did; nothing changes until you pick a setting.
• Mail server presets for Microsoft 365, Gmail and Google Workspace, SendGrid, Mailgun and Amazon SES. Each fills in the server, port and encryption, and tells you the one credential detail that provider gets asked about most — SendGrid wants the literal word “apikey” as the username, Amazon SES needs SMTP credentials rather than an AWS key, Microsoft 365 needs SMTP AUTH switched on for the mailbox.
• Back up and restore your own configuration. Settings, Backup. Downloads a plain zip holding your devices, thresholds, notification settings, map and dashboard layout and any floor plan or alarm sound you uploaded — enough to rebuild this install on another machine. Stored credentials are left out unless you tick the box. Restoring keeps a copy of everything it replaces, so a wrong file is not the end of it. The old “Config backup” tab, which saves the configs of the switches you monitor, is now called “Monitored devices’ configs” — it does the same as before.
• Notes on devices, and a way to delete them. Write anything worth remembering against a device — which cabinet it is in, who owns it, who to ring before power-cycling it. Devices can now be deleted, one at a time or several at once, which was previously only possible by hand-editing the configuration file.
• Three layouts on the Devices page. Cards as before, plus List and Table for sites with more devices than fit on a screen. Your choice is remembered.
• Passwords now have a confirmation box everywhere they are set: your own, a new user’s, and when an administrator resets someone else’s. A mistyped password used to lock the person out with no warning. Users can also have an email address recorded against them.
• Deleting a device could silence its neighbours. If other devices were set to depend on the deleted one, they kept pointing at something that no longer existed, and AI NetRiva read that as “their upstream is down” — so it stopped alerting on them. Affected 1.0.0 onwards, but only if you removed a device by editing the configuration file, which was the only way to do it before this release.
• Saving mail settings and then reloading the page showed an empty form, as though the save had been thrown away. It had not been, but there was no way to tell.

• “Check for updates” now actually checks. The button reported “up to date” whatever the release server said — it reused a result cached when the app started, then read the answer from the wrong fields. Both fixed. On 1.0.0–1.0.3 that button will keep telling you the same thing until you install this build: the fault is in the older program, not the server.

• The Windows service could not start on any machine where AI NetRiva had been run by hand first. The credentials file is locked to its owner, which also locked out the system account the service runs under; it failed at startup and Windows retried until it gave up. The service showed as installed and monitored nothing. It now grants the system account access as well — ordinary users still have none.

• Run as a Windows service, offered by the installer and ticked by default. A monitor that only runs while you are logged in is not monitoring. Uninstalling removes the service cleanly.
• Service status in Settings → Updates — whether it is installed, running, and starting at boot, with the exact command to change it.
• Update checking works on a fresh install. The release source had no default, so new installs had checking silently switched off.

• Somewhere to enter your licence. Settings → Licence. The program accepted licences all along but had no screen to paste one into, so a purchase could not be activated.
• Update checking became possible at all. 1.0.0 shipped with a verification key whose counterpart had never been created, so no release could ever have satisfied it. 1.0.0 installs cannot update themselves and must be replaced by hand.

First public release — the build that had been running in production for a year, made generally available.

• ICMP polling with latency history, subnet discovery, the topology map, SNMP interface and host metrics.
• Syslog receiver with retention, SSH console capture, configuration backup with diffs and restore.
• Service and port monitoring — HTTP status and content, TCP ports, TLS certificate expiry. The step from “is it pingable” to “is it working”.
• Alarms with acknowledgement and escalation, multi-user accounts, and the AI assistant.
• Device-type icons and OS indicators inferred from vendor, model and SNMP sysDescr, with a manual override when the guess is wrong.
• Troubleshooting tools in the browser — ping, traceroute, port check, DNS lookup, SNMP walk — and a one-click diagnostic bundle, redacted before you see it.