rsyslog Windows Agent 2026 — New major release, new licensing, new release cycle
Overview
rsyslog Windows Agent enters a new calendar-year major line starting with 2026. This release introduces a monthly update cadence, modern License V2 file licensing, and a next-generation Configuration Client Preview in the installer.
If you are upgrading from rsyslog Windows Agent 8.x (or earlier), read this article before you deploy. Your existing licensee name and numeric license keys do not authorize the 2026 major—you will receive a new license.alic file from Adiscon.
A new way to read version numbers
Old major versions (through 8.x)
Historically, rsyslog Windows Agent used sequential major versions that increased independently of the calendar. Different Adiscon products used different major numbers (WinSyslog 18, EventReporter 19, MonitorWare Agent 15, and so on).
| Component | Legacy (8.x) | New (2026+) |
|---|---|---|
| Example | 8.3.0.236 | 2026.7.0.1001 |
| Major | Sequential 8 | Calendar year 2026 |
| Minor | Feature release (e.g. 3) | Calendar month (e.g. 7 = July) |
| Third part | Reserved (0) | Always 0 |
| Build | Service build counter | Service build counter |
New major versions (from 2026)
Starting with the 2026 major, the year is the major version. The About dialog may display spaces after dots (e.g. 2026. 7. 0. 1001).
Why this matters: A license issued for 2026 is bound to that year. When Adiscon ships 2027 builds, you will need a license that lists 2027 in its allowed major years.
New release cycle: monthly updates within a year
Adiscon is aligning rsyslog Windows Agent with a predictable monthly rhythm:
- One major per calendar year (2026, 2027, …)
- Minor version = release month (January = .1, July = .7, December = .12)
- Regular monthly builds with fixes and improvements during the year
The first general-availability minor for this announcement is 2026.7 (July). You can plan upgrades knowing that 2026.8, 2026.9, and so on will arrive through the year while staying on the same 2026 major line. Detailed change lists belong in release notes, not in this overview.
License V2: from name + keys to a signed license file
The largest operational change in the 2026 major is License V2. In rsyslog Windows Agent 8.x, licensing was stored as szLicensee and five numeric keys (nLicenseKey1 through nLicenseKey5). The 2026 service reads a signed license file instead; those legacy fields are ignored.
| Topic | Legacy keys | License V2 (2026+) |
|---|---|---|
| Storage | Registry / config fields (szLicensee, nLicenseKey1-5) | license.alic file |
| Customer input | Licensee name + five numbers | Deploy file; optional szLicenseV2Path |
| Security | Arithmetic encoding | Cryptographic signatures (offline validation) |
| Cross-major | Keys tied to old algorithm | New major requires new file |
| Trial | Legacy heuristics | Built-in eval window |
Important: Keys from rsyslog Windows Agent 8.x do not carry forward. Contact Adiscon support or sales to obtain a new license.alic for your edition.
Licensing
License V2 details and migration
What you use now (License V2)
| File name | license.alic |
| Default location | %ProgramData%\Adiscon\RSyslogAgent\license.alic |
| Configuration | szLicenseV2Path — optional path to the file (path only, not license text) |
| Format | Cryptographically signed, offline-validated token (not editable by hand) |
| Old key fields | Ignored on the 2026 major |
Editions (Basic, Professional, Enterprise) still exist as commercial labels. Remote Event Log and client connection limits are enforced from signed entitlements in the license file. Trial licenses are explicit in the signed file; if no valid file is present, a built-in evaluation window may apply until it expires. Cryptographically invalid or revoked files do not qualify for that fallback.
How to migrate to License V2
- Request a 2026 license file from Adiscon for rsyslog Windows Agent (correct edition and entitlements).
- Save the file as license.alic in the default directory, or set szLicenseV2Path to your preferred folder.
- Upgrade the service to the 2026 major build using your normal installer or deployment process.
- Open the configuration client and confirm license status shows registered (or trial if applicable).
- Restart the service after placing or updating the license file.
- Stop maintaining legacy key fields in new configurations—they are not used on 2026.
Configuration snippet (optional)
Administrators using file-based configuration may set:
szLicenseV2Path C:\ProgramData\Adiscon\RSyslogAgent\license.alic
Frequently asked questions (licensing)
Do my 8.x license keys work on 2026?
No. The 2026 major requires a new License V2 file (license.alic). Contact Adiscon to obtain one.
Can I copy license.alic from another product?
No. Each license is issued for specific product SKUs (RSyslog-WA-Basic, RSyslog-WA-Pro, RSyslog-WA-Enter). The service rejects mismatched products.
What if license.alic is missing?
The service may enter a time-limited built-in evaluation mode if no valid license is present. Cryptographically invalid or revoked files do not qualify for that fallback.
Do I need internet activation?
No for normal operation. License V2 is validated offline using embedded public keys in the product.
Will 2026.7 accept a license that only lists 2027?
No. The build year must appear in the license majorVersions list. A 2026 build requires 2026 (or a range that includes 2026).
Upgrade
Upgrade path and compatibility
Upgrade planning for rsyslog Windows Agent 8.x to 2026 should start with a License V2 request before production rollout. Install or upgrade to 2026.7 (July GA) or a later 2026.x monthly build within the same year major.
Note: The rsyslog Windows Agent is Adiscon’s native Windows agent for rsyslog-compatible deployments—it is not the open-source Linux rsyslog project.
Next-generation Configuration Client Preview
The rsyslog Windows Agent installer for the 2026 major includes two configuration clients:
- Established configuration client — familiar UI, updated for License V2 path and verification.
- Next-generation Configuration Client Preview — modern WinUI-based workbench (adiscon-client-ng), shipped as a preview alongside the classic client.
The preview is intended for early adopters. Both clients target the same service and the same license.alic contract. Expect the preview label until Adiscon declares general availability.
What changed between 8.x and 2026 (overview)
The 2026 major is a platform refresh, not a single-feature update. Alongside calendar-based versioning and monthly updates, it introduces file-based License V2, expanded file/YAML configuration options, operational metrics (disabled by default), installer improvements, and ongoing reliability hardening across listeners, actions, and the core engine. For detailed changes in a specific month build, see the product release notes for 2026.7 and later.
rsyslog Windows Agent continues to focus on reliable Windows log ingestion and forwarding in rsyslog-compatible deployments; the 2026 line modernizes how you license, version, and configure the product. This is Adiscon’s Windows agent only—not the Linux rsyslog project.
Frequently asked questions (upgrade)
Where is the license file?
Default: %ProgramData%\Adiscon\RSyslogAgent\license.alic
Is the nextgen client required?
No. It is a preview. The classic configuration client remains supported for License V2 deployment.
Where should backup tools copy the license?
Back up license.alic together with your configuration directory under the product’s ProgramData folder.
Next steps
- Existing customers: Contact Adiscon support or sales to request your 2026 license.alic before or during upgrade.
- New deployments: Install the 2026 major, deploy license.alic, verify in the configuration client, then roll out rules and services as usual.
- Monthly updates: Check release notes for 2026.7, 2026.8, and subsequent monthly builds.