Tag: release

2007-10-11 MonitorWare Agent 5.1 Final (Build Service 5.1.340/Client 5.1.1166)

MonitorWare Agent 5.1 Released

Build-IDs: Service 5.1.340, Client 5.1.1166

New Additions

  • EventLog Monitor

    Added new option to use the new Checksum method to verify if the LastRecord is still valid. This option can be set in each EventLogType. We also had to redesign the Client advanced options form, as all the options did not fit into it anymore. This option will prevent you from modifying the LastRecord value which means if you change the LastRecord value, the whole EventLog will be reprocessed! Continue reading “2007-10-11 MonitorWare Agent 5.1 Final (Build Service 5.1.340/Client 5.1.1166)”

2007-08-22 MonitorWare Agent 5.0 Final Released

MonitorWare Agent 5.0 Released

Adiscon is proud to announce the 5.0 release of MonitorWare Agent. A prime focus of this release is on reliability. That, of course, not just meaning proper program execution but on delivering messages even under bad circumstances. Circumstances, that other solutions may not even be aware of, much less are capable to handle. Main new features include: Continue reading “2007-08-22 MonitorWare Agent 5.0 Final Released”

2007-08-22 MonitorWare Agent 5.0 Final (Build Service 5.0.336/Client 5.0.1161)

MonitorWare Agent 5.0 Released

Build-IDs: Service 5.0.336, Client 5.0.1161

New Additions

  • Forward Syslog Action– Added support for sending multiple messages over a persistent syslog/TCP connection.
    – Added capability to force -transport-tls like octet-counted framing for syslog/TCP connections.
    – Added a new major feature into this Action, Diskqueue. This new option is only available for TCP based Syslog. Whenever a connection to a remote syslog server failes, the action starts caching the syslog messages in a local temp file. The folder for these files can be configured. You do not need to worry about multiple Actions using this feature, the filenames are generated using a unique GUID which is automatically generated for each Action. Continue reading “2007-08-22 MonitorWare Agent 5.0 Final (Build Service 5.0.336/Client 5.0.1161)”

2007-07-03 MonitorWare Agent 4.4 Final (Build Service 4.4.332/Client 4.4.1137)

MonitorWare Agent 4.4 Released

Build-IDs: Service 4.4.332, Client 4.4.1137

New Additions

2007-01-22 MonitorWare Agent 4.3 Final (Build Service 4.3.323/Client 4.3.1099)

MonitorWare Agent 4.3 Released

Build-IDs: Service 4.3.323, Client 4.3.1099

New Additions

  • New EventLog Monitor V2 ServiceA new Service has been added to fully support the new EventLog of Windows Vista. Currently the Service is just called EventLog Monitor V2 and can only be configured and used on Windows Vista or Windows Longhorn Server. This new Service fully supports the new EventLog structure, the new Channels and so on. Please note that this is the initial release of the new EventLog Monitor, slight enhancements and changes will follow in future versions. Currently we fully support Serviced Channels only, which also includes all classic EventLogs. To gain support for fully reading the new Vista EventLog, we highly recommend to use the new Service. Continue reading “2007-01-22 MonitorWare Agent 4.3 Final (Build Service 4.3.323/Client 4.3.1099)”

2006-10-25 MonitorWare Agent 4.2 Final Released

MonitorWare Agent 4.2 Released

Adiscon is proud to announce the 4.2 release of MonitorWare Agent. This release contains a few features and some bugfixes. This is primarily a maintenance release. Find a list of changes below:

  • EventLog Monitor – A ressource library cache has been added. This new feature will mainly be useful for the Eventlog Monitor. All libraries will be cached for 30 minutes by default. For events with the same reoccuring event sources, this will be a great performance enhancement. The cache will also work for remote system libraries (requires administrative default shares).
  • Syslog Service, MonitorWare Echo Reply, SETP Receiver – TCP and UDP Services can now be bound to specific IP Addresses. This feature is useful for multihome environments where you want to run different Syslog Servers on different IP Addresses. Please note that the default IP Address 0.0.0.0 means ANY IP Address.
  • OpenSSL – Updated the OpenSSL components and libraries with the latest Version openssl-0.9.8d.
  • ForwardSyslog Action – Fixed a wrong Session Timeout value in case TCP was selected as protocol. This caused each TCP Session to be closed after usage. The session will now remain open for 30 minutes by default.
  • Database Service – Fixed a bug in the Database Monitor that caused saving the wrong LastID Value. Also fixed a bug in the Client that caused bogus error messages when a new Database Monitor was created.

More Details can be found in the version history

Version 4.2 is a free download. Customers with existing 3.x keys can contact our Sales department for upgrade prices. If you have a valid Upgrade Insurance ID, you can request a free new key by sending your Upgrade Insurance ID to sales@adiscon.com. Please note that the download enables the free 30-day trial version if used without a key – so you can right now go ahead and evaluate it.

2006-10-25 MonitorWare Agent 4.2 Final (Build Service 4.2.316/Client 4.2.1062)

MonitorWare Agent 4.2 Released

Build-IDs: Service 4.2.316, Client 4.2.1062

New Additions