Release date: November 3, 2026
Service build: 26.11.0.693
Configuration Client build: 26.11.0.1776
User Interface build: 26.11.0.1020
Upgrade assessment
Recommendation: Recommended update
Why update now: This release adds Microsoft 365 application OAuth for mail and manual hostname mappings. It also verifies TLS, DTLS, and HTTPS destinations, limits SMTP reception, preserves the first Event Log event after a subscription resumes, recovers pending file rotation at startup, and corrects listener and configuration handling.
If you defer: Existing processing continues, but Microsoft 365 application OAuth, hostname mappings, and the forwarding, SMTP, Event Log, file, and configuration corrections in this release remain absent.
Who benefits most: Administrators who send mail through Microsoft 365, receive SMTP or Syslog, monitor the Event Log, map hostnames, or write dynamic files.
Upgrade and verification: Update MonitorWare Agent using the normal supported upgrade path. Confirm that the installed service version is 26.11.0.693. Test the changed functions that are relevant to your deployment.
Important changes
Mail action
- Change: The Mail action can send mail through Microsoft 365 using application-based OAuth authentication. SMTP LOGIN credentials are protected in diagnostic output and authentication failure reports, and encrypted mail verifies the destination. HTTPS probes verify destination certificates and identities.
- Operational impact: Mail can use Microsoft 365 application authentication, and diagnostic output no longer exposes SMTP LOGIN credentials.
- Applies to: MonitorWare Agent installations that send mail or use HTTPS probes.
- Verification: Configure Microsoft 365 application OAuth, send a test mail, and confirm the message arrives. Confirm an authentication failure report does not include the SMTP LOGIN password.
Hostname and IP mappings
- Change: General settings can define hostname and IP address mappings in the Configuration Client and in the User Interface.
- Operational impact: Events can use a configured hostname or IP address mapping instead of the resolved value alone.
- Applies to: MonitorWare Agent installations that resolve hostnames.
- Verification: Add a hostname and IP address mapping, then confirm a processed event uses the mapped value.
TLS and DTLS forwarding
- Change: TLS and DTLS forwarding verify destination certificates and identities. Stalled TLS forwarding no longer blocks shutdown indefinitely.
- Operational impact: A destination with an unexpected certificate or identity is not treated as verified, and a stalled TLS send does not keep the service from shutting down.
- Applies to: MonitorWare Agent installations that forward over TLS or DTLS.
- Verification: Exercise one TLS or DTLS forwarding destination you use. Confirm the service shuts down after a TLS send that does not complete promptly.
File output and rotation
- Change: The File action keeps dynamic output paths within their configured directories and writes queued data more efficiently. File rotation starts recovery before new events are processed, so pending rotated files can be recovered after service startup.
- Operational impact: Dynamic file output stays inside the configured directory, and a pending rotation can be recovered when the service starts.
- Applies to: MonitorWare Agent installations that use the File action or file rotation.
- Verification: Use a dynamic file path and confirm the output remains inside the configured directory. Restart the service with a pending rotated file and confirm recovery starts before new events are processed.
Listeners, SETP, and Event Log
- Change: The Syslog Listener rejects malformed message headers. The RELP Listener does not acknowledge records that could not be processed and handles diagnostic output safely. SETP handles malformed, empty, or deeply nested messages safely. The SMTP Listener limits incoming message size and reception time and does not accumulate memory across connections. The Event Log Monitor preserves the first event after a subscription resumes.
- Operational impact: Malformed input and oversized SMTP reception are contained, and the first Event Log event after a subscription resumes is preserved.
- Applies to: MonitorWare Agent installations that receive Syslog, RELP, SETP, or SMTP, or that monitor the Event Log.
- Verification: In a test environment, confirm a malformed Syslog header is rejected, an SMTP message above the configured limit is refused, and the first Event Log event is present after a subscription resumes.
Remote configuration, licensing, and diagnostics
- Change: Remote configuration rejects invalid HTTPS certificates and insecure redirects. Registry configuration detects the default license file more reliably when the license path is empty and no separate data directory is configured. If a different data directory is configured, that directory remains the default license location. When a listening socket cannot be opened, diagnostics include possible owners.
- Operational impact: Insecure remote configuration downloads are rejected. The default license file is found for the empty-path registry case described above, and a failed listening socket identifies possible owners.
- Applies to: MonitorWare Agent installations that download remote configuration, use registry licensing, or open listening sockets.
- Verification: Confirm an invalid HTTPS certificate or an insecure redirect is rejected when downloading configuration. With an empty license path and no separate data directory, confirm the service finds the default license file. Confirm a failed listening socket reports possible owners.
Configuration Client
- General settings can define hostname and IP address mappings.
- The Syslog action can set the TLS send progress timeout.
- The Mail action can use Microsoft 365 application OAuth, and a test mail can check the settings.
- A partial configuration is not saved after loading fails, and existing settings are preserved when a selective import fails.
User Interface
- General settings can define hostname and IP address mappings.
- The Syslog action can set the TLS send progress timeout.
- The Mail action can use Microsoft 365 application OAuth, and a test mail can check the settings.
- A partial configuration is not saved after loading fails, and existing settings are preserved when a selective import fails.
- The dashboard displays content in the selected language.
- SMTP LOGIN username validation accepts a valid username.
Partner deployment notes
Availability: Use the canonical MonitorWare Agent download and this Technical Release Notes page as the release reference; do not use temporary build links as the long-term reference.
Localization: The User Interface translation workflow is being prepared. Translation strings and contribution guidance will be published in the Adiscon community repository when available.
Partner verification: Confirm the installed service, Configuration Client, and User Interface builds. Where relevant, send a Microsoft 365 test mail, resume an Event Log subscription, and save a configuration change.