EventSentry 2.91 introduces important changes that might affect your network and configuration. The text-matching algorithm has changed, and support for Windows NT 4 has been removed. Please see below for more details.
Windows NT4
Starting with EventSentry v2.91, Windows NT 4 is no longer a supported platform. If you are still running Windows NT 4 machines in your network and need to monitor these with EventSentry, then you should NOT upgrade those machines to v2.91 or later. It is recommended that you manage v2.90 agents with a separate management console, and setup a separate database as well as web reports profile for those machines.
Text Matching
|
Starting with version 2.91, the ability to match strings without using wildcards is no longer available, and all text matching needs to use wildcard characters if the filter text does not fully match the event text (e.g. source, category, event message, ...). This will not affect most installations, but users that have the wildcard functionality disabled in version 2.90 or earlier (it was enabled by default) will need to review their configuration and make adaptations.
|
|
Please see the table below for examples on how existing filters might have to be modified. The "Source Text" column shows the text to match, whereas the middle column shows how this text could have been matched in version 2.90 earlier with the wildcard feature disabled. The "2.91" column shows how a text like this would have to be matched in 2.91. Note that wildcards are only necessary for partial matches, not for full matches.
|
Source Text
|
Without Wildcard Support (2.90 and earlier only)
|
2.91
|
Microsoft-Windows-Security-Auditing
|
Microsoft-Windows
|
Microsoft-Windows*
|
Microsoft-Windows-Security-Auditing
|
Microsoft-Windows-Security-Auditing
|
Microsoft-Windows-Security-Auditing
|
Microsoft-Windows-Security-Auditing
|
Windows-Security
|
*Windows-Security*
|
Updating
PLEASE SEE Updating from version 2.7x or higher to the latest version for more information on the update process.
|