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)”

New Additions

• RFC 3195 Changes
  
  Enhanced Syslog/BEEP implementation for better interoperability with Cisco’s implementation in IOS. The BEEP support has been in our products for a long time, but so far no major vendor offered BEEP support. Now that a first major vendor implementation is available, we need to tweak a few protocol parameters to make it fully interoprable. This has happened now. Continue reading “2007-07-03 MonitorWare Agent 4.4 Final (Build Service 4.4.332/Client 4.4.1137)”

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)”

New Additions

• 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). Continue reading “2006-10-25 MonitorWare Agent 4.2 Final (Build Service 4.2.316/Client 4.2.1062)”

New Additions

• New Action: Resolve Hostname Action

  Customers asked for resolve hostname options in different services. This feature has now been implemented as an action. An action can be used with every service, and it doesn’t delay the work of a service. Continue reading “2006-07-10 MonitorWare Agent 4.1 Final (Build Service 4.1.312/Client 4.1.1038)”

New Additions

• x64 Build
  
  This is the first Version which introduces MonitorWare Agent on the x64 platform. Major compatibility changes for the x64 platform have been made in the Service core. For details see the changes listed below:
  – ODBC Database Action, fully runs on x64 now. Please note that there are currently very few ODBC drivers for x64 available!
  – Configuration Registry Access, a DWORD Value will now be saved as QWORD into the registry. However the Configuration Client and Win32 Service Build can handle these data type and convert these values automatically into DWORD if needed. The Configuration Client will remain a win32 application. Only the Service has been ported to the x64 platform. Continue reading “2006-05-09 MonitorWare Agent 4.0 Final (Build Service 4.0.306/Client 4.0.1020)”