Overview

This article lists the improvements and fixes that came with the GFI EventsManager 2013 (Build 20130116) release.

Environment

GFI EventsManager 2013

Information

Improvements:

• Added new database operation for exporting events to a Microsoft SQL Server database.
• Text logs collector to parse XML files.
• User roles: Administrator can filter what a new user is allowed to view in the management console.
• System Monitoring features based on GFI Network Server Monitor functionality.
• Updates can be downloaded through a proxy.
• Added support for offline updates.
• Physical deletion of events is now possible.
• Enhancements to the database operations and database rotation.
• Events Browser now has two modes: One for viewing events as before and another to view events that were marked as deleted.
• GFI database server can be installed on a separate server.
• Added support for reports that contain more than 10,000 entries.

Fixes:

• Reporting: various enhancements regarding usability and look, fixed some report generation issues.
• User Interface: various fixes for rules, events processing sources, dashboard.
• Events Browser: various UI enhancements, fixes for drill down, query execution and exporting of events.
• Issues that could cause a service crash.
• Database corruption issues.
• Improved dashboard stability.
• Issues related to event collection from SQL Server and Syslog sources

Known Issues:

• In some cases, queued jobs are not removed from the Job Activity panel.

System Requirements:

• Processor: 2.5GHz dual-core processor or higher
• RAM: 3GB
• Hard Disk: Minimum of 100GB of available space
• Others: Keyboard and mouse or compatible pointing device

• .NET Framework 4.0
• To properly scan Windows Vista or newer machines, GFI EventsManager must be installed on a Windows Vista or newer machine.

Software requirements - Scanned machine(s):

• Windows event log scanning:
  • For Vista and newer machines, remote event log management must be enabled.
  • For Vista and newer machines, UAC (User Account Control) must be disabled and the machines must be within the same domain.
  • For pre-Vista machines, the remote registry must be enabled.
  • Windows audit service must be enabled.
• W3C log scanning:
  • The source folders must be accessible via Windows shares.
• Syslog and SNMP (Simple Network Management Protocol) Traps:
  • Sources/senders must be configured to send messages to the computer/IP address where GFI Events Manager is installed.

The latest version of GFI EventsManager can be downloaded from the download page.