EventReporter 12.0 Released

 Features

• Added support for IPv6:
  Support for IPv6 has been added into all network related facilities of the engine. All network related actions will automatically detect IPv6 and IPv4 target addresses if configured. You can also use DNS resolution to resolve valid IPv6 addresses. Network related Services can either use IPv4 or IPv6 as internet protocol. In order to support both protocols, you will need to create two services. The only exception is the RELP Listener, which uses IPv4 and IPv6 automatically if available.
• SETP Action:
  Extended MonitorWare SETP Protocol to V3. If Sender and Server support V3 or higher, UTF8 is now used to encode/decode messages. This maintains the correct character encoding after the messages is received and rebuild internally.
• ODBC / OLEDB Action:
  Implemented OutputEncoding for 8Bit (var)char fields. This means we can now write UTF8 encoded messages into varchar fields.
• Core Engine:
  Added Performance fix for UTF conversion for empty strings.
• EventLog Monitor V2:
  Added support for polling EventLog Records. This works almost like in the old EventLog Monitor, the Eventlog channel is polled frequently and new EventLog records are processed only. By default, the “Subscription Model” is used which processed events in Realtime.
  Added support to read and process EVTX files. This requires the new “Eventlog Polling” method. It is also possible to update the EVTX files while MonitorWare Agent is running.
• Upgraded internal NET-SNMP library to version 5.6.1.
• Send SNMP Action:
  Added support for IPv4/IPv6 and TCP/UDP. A combination of UDP/TCP and IPv4/IPv6 can now be configured.

 Bugfixes

• Send Email Action:
  Fixed an issue in Datestring creation of the Emailheader (Send Email Action). The first digit pair of the time was not correctly build with two digits as per RFC2822. Restrict Mailclients could not handle this.