Release Notes

• Alarm Window. The Global Alarm Window did not always sort correctly. This has been fixed. (1338, 05/01/2007)
• Configuration Wizard. When a password for the service account was automatically generated by the configuration wizard, it was not automatically also filled in in the "confirm password" field. This has been fixed.(1337, 12/22/2006)
• GUI. When closing the GUI, The GUI would wait for possible existing background execution threads to finish, before actually closing. As the actions performed by these threads (mostly background network browsing), are no longer required when closing the Gui, this bevior is changed, and the GUI will exit faster. (1337, 12/22/2006)
• EventLog Archiving. Storing of the eventlog message in the MonitorMagic SQL database failed, when the event message text to be stored contained single quote ' characters, or some other chars that ODBC might convert at a later stage to single quote characters. Single quote characters are now replaced by ? characters, when stored in the database. (1336, 05/19/2006)
• EventLog Archiving. When reading event log messages from the event log , and a particular single message was very long (longer than 10240 bytes), it failed to read correctly, and the particular eventlog was not or only partially archived. This has been modified to support the maximum allowed size (in XP/windows 2003)) of an single event log message of 0x7ffff (524287) bytes. (1337, 12/22/2006)
• Service connection. When the MonitorMagic Service was configured to connect over a different TCP/IP port number than the default port number, the GUI might fail to connect to the service. Part of the method the client uses to determine the correct port number consists of retrieving the list of services running. For servers containing a large amount of services, this list was not completely retreived, and as a concequence, the port number was not correctly found. This has been fixed.(1337, 12/22/2006)

• Plugin: T4eSql. The T4eSql Plugin database queries could fail to read date-time fields on systems with older ODBC 2.0 drivers because the obsolete data type (type 9) was not recognized by MonitorMagic. This has been corrected. (1337, 12/22/2006)

MonitorMagic 6.1 build 1323, Release date: December 5th, 2005

Features:

• Policies: The set of default policies has been updated.

Fixes:

• Web Interface: When the web interface was configured not to require a username/password, the network browse tree did not show up in the web client. This has been fixed. (1323, 12/05/2005)
• SMTP Get Monitor: When a simple object identifier (oid) was specified in a new user created policy without using the "advanced" dialog, the specified oid was not saved in the monitor. Furthermore, applying this policy could cause the MonitorMagic service to exit. Both errors have been fixed. (1323, 12/05/2005)

MonitorMagic 6.0 build 1320, Release date: November 15th, 2005

Features:

• The global alarm window has been updated. It is now possible to place alarm items in (user defined) groups. The group icon indicates if the folder contains any items in alarm state.

MonitorMagic 6.0 build 1309, Release date: October 14th, 2005

Features:

• Configuration Wizard: A Configuration Wizard has been added to facilitate the configuration of Monitor Magic. The Wizard allows you to automatically set some default policies for monitoring Active Directory, Exchange, backup and virus applications, Windows performance and devices.

MonitorMagic 6.0 build 1289, Release date: January 31, 2005

Features:

• Policies: The default policies have been revised and significantly extended.
• Report Templates: The default reports have been revised and significantly extended.
• Event Archiving: When in the database options is specified that data older than a specific date should be deleted, this now includes not only the data of the Monitors, but also the data collected with event archiving.

Fixes:

• Event Archiving: When event logs are read from remote computers it is required for proper display of the event description that the MonitorMagic service has access to certain message.dll files specific for the application that logged an event. For performance reasons these files need to be copied to the machine running MM. It is possible that this fails, either because the specific message.dll file does not exist in its proper location, or because NTFS rights settings prevent the copy. Previously, MonitorMagic did not remember past failures to access and copy the message file, which caused performance loss and superfluous error messages because the process was repeated each time the message dll was required. Now it does remember recent past failures. As a result, there will be less error messages, and database storage will be significantly faster. (1288, 01/13/2005)
• Event Archiving. When in the database options is specified that data older than a specific date must be deleted, this now includes not only the data of the monitors, but also the data collected with event archiving. (1288, 01/13/2005)
• Reports, Save to HTML. When a certain report query finds no data in the database that matches the query, the report shows correctly "no table data found in database". If the report is then saved to HTML, this specific phrase was omitted. The phrase is not also included in the HTML report.(1288, 01/13/2005)
• Reports, Save to HTML. The process of saving reports that are shown in the gui into a HTML file , is now (very) significantly faster, Especially for reports containing large tables.(1288, 01/13/2005).
• Policies and Reports Update. The automatic process of installing new and updated policies and report templates when a new version of the MonitorMagic program is installed, has been inproved. The program will now add and replace existing policies and reports on a update, also if a policy with the same name already exist. This makes sure that the newest policies are always available. If an existing policy is replaced, a backup will be made automatically of the original policy. The backup will be placed in a special backup directory located in the data directory of the GUI.
• GUI, Network Tree. When a custom folder of the network browse tree was renamed, without any other modification to the tree, the changes where not saved automatically on exit of the application. This has been fixed (1288, 01/13/2005) Alarm Action, Remote shutdown. The remote shutdown action could fail on windows 2003 and XP machines, because activation of a certain required account privilege could fail. This has been fixed.(1288, 01/13/2005)
• Alarm Action, Email. There was a problem specifying a long subject name. This has been fixed. (1288, 01/13/2005)
• File Monitor: The maximum file size that a rule could check was about 4.2 GB. This has been fixed.(1288, 01/13/2005)
• SNMP Get Monitor: Solved license issue that required a server license instead of a device/workstation license for the queried device when dropping and dragging SNMP policies to a "Manual SNMP host" entry. This was caused because de display name of manual host was initally used to check the license, instead of the actual ip address. This is fixed. (1289, 01/31/2005)
• GUI, Creating Monitors. The default sheduling for newly created eventlog and disk monitors has been increased fror 60 to 600 sec.(1288, 01/13/2005)
• GUI, Editing Monitors. When editing the properties of a monitor and then canceling, a confirmation window is now only shown if there have been made modifications to rules.(1288, 01/13/2005)
• GUI, Editing Monitors. When editing the name of a Monitor Rule, this failed when pasting information that exceeded a specific length. This has been fixed. (1288, 01/13/2005)
• GUI, Editing Monitors. When modifying a name of a Rule, the new name was sometimes overwritten by an automatically generated name. This has been fixed.(1288, 01/13/2005)
• GUI, Editing Monitors , Rule criteria. In the Rule Criteria dialog, the size of the "limit/reference value" field was limited to around 24 characters. Now there is no longer a limit.(1288, 01/13/2005)
• GUI, Editing Monitors, Rule criteria. When in the Rule Criteria for the EventLog monitor the "equals (case insensitive)" operator was specified, the rule was correctly( i.e. case insensitive) analyzed when executed. However, in the "Rule spec" tab the operator was incorrectly displayed as "equals (case sensitive)". This has been fixed (1288, 01/13/2005)
• Web Interface: For very large networks the browse tree was sometimes not correctly shown because of a timeout building the web page on the server. This process has been speeded up to prevent timeouts.(1288, 01/13/2005))
• Printing Monitors: When printing monitors, some items where truncated when they did not fit on the page. This has been fixed.(1287, 12/27/2004)
• Plugin: Web Ping. When connecting to the Internet, the Web ping plugin does now use the proxy settings that are specified in the Internet properties of Windows. Usually this means a direct connection, as the Internet properties for the service account at the machine that runs the MonitorMagic service are rarely specified. But when they are specified, they are now used.

MonitorMagic 6.0 build 1279, Release date: July 26, 2004

Features:

• Manual SNMP Hosts: In the network tree it is now possible to add manually SNMP hosts by specifing the TCP/IP adress and community string. If an SNMP policy is then applied to such a host (either by dragging or selecting "Apply Policy" from the context menu), all IP-addresses within that SNMP policy are replaced by the IP address of the selected host before the policy is applied. This makes it possible to apply an SNMP policy to different target computers without having to modify the IP-adresses in the policy. (1278, 07/20/2004)
• Report E-mail distribution: All reports can now be sent on a scheduled basis in HTML format to any number of recipients. See Configure report E-mail distribution for more information.
• Global alarm window: A new alarm window is introduced. The Global alarm window presents summary information for all monitored systems. See Global alarm window for more information (1218, 9/5/2003).
• File monitor: The file monitor is extended with 4 new fields (rules): Age oldest file (sec), Age most recent file (sec), Modification elapsed time (sec) - minimum, Modification elapsed time (sec) - maximum. The fields can be used to trigger rules based on the creation and modification time of one ore multiple files. (1218, 9/5/2003)
• File monitor: The file monitor is extended with 2 new keywords: Matching text and Matching file. These fields can be used in alarm actions when searching for specific keywords (for example: ERROR) . See File monitor - File monitor values for more information.
• Plugin - Directory size: The directory size plugin determines available diskspace, and the size occupied by files, directories and shares. Rules can be triggered when to much disk space is used or the available diskspace drops below a configurable minimum. See Plugin - T4eDirSize for more information. (1218, 9/5/2003)
• Plugin - SQL query: The SQL query plugin can execute any SQL query to any database. The output of the query can be used to trigger rules, based on various criteria. See Plugin - T4eSql for more information. (1218, 9/5/2003)
• Plugin - Unix Remote execution. The Plugin - T4eRexec is a MonitorMagic plugin. It is used to execute remotely a command on computer running an operating system that supports the standard Rexec protocol, such as the UNIX operating system. (1271, 4/29/2004)
• Plugin - Unix information. The Plugin - T4eUnixInfo is a MonitorMagic plugin. It is used to collect specific information from a computer running a UNIX compatible operating system. It uses the Rexec protocol to retreive information from the remote computer. (1271, 4/29/2004).
• Alarm action execution: A new option is added to execute alarm actions when a rule is not triggered, regardless of the previous rule state. See Managing alarm action execution for more information. (1244, 1/8/2004)

Fixes:

• Global alarm window: A resource leak in the global alarm window of the MonitorMagic client is resolved. Because of the leak, various desktop windows shown at the computer that runs the MonitorMagic client were drawn incorrectly after some period of time. The period after which this could happen varies from several hours to several days, depending on several update frequencies. (1233, 11/27/2003)
• Reports: A problem with date and time values in reports is fixed. In previous versions, the time value (minutes field) could be incorrect while the date was correct. (1228, 11/14/2003)
• Reports: HTLM E-mail report distribution failed when no default font setting was ever changed when designing a new report. This has been fixed. (1273, 05/14/2004)
• Graphs: A problem with incorrect legend graph item colors has been fixed. When items from a graph were deleted, the color of remaining items as shown in the legend could become corrupted. (1222, 9/26/2003)
• Graphs: The context sensitive menu option Print... from (2D) graph windows now works properly. (1222, 9/26/2003)
• Policies: When applying a policy, and the monitor window of the corresponding MonitorMagic service is not open, the policy is now applied as expected. In previous version, the monitor window had to be open to apply the policy.(1222, 9/26/2003)
• Policies: A problem regarding the installation of default policies has been fixed. The problem caused the policies no to be installed automatically. (1222, 9/26/2003)
• Performance counter monitor: A problem regarding the calculation of performance counter values has been fixed. The problem could cause incorrect values for some performance counters. (1222, 9/26/2003)
• Client - server connection: When the MonitorMagic service runs on a computer with multiple NIC's, a problem could occur when the client tried to connect to the MonitorMagic service. The problem is fixed. (1222, 9/26/2003)
• Client - server connection: On fast machines, a timing problem could occur in previous versions when the connection between client and service was setup. The problem caused the window showing connection setup progress information not to be removed when the connection was established. This did not have any further consequences. (1222, 9/26/2003)
• MonitorMagic access rights: When user rights are configured for users running MonitorMagic clients, the application now behaves correctly. In previous versions, all access was denied incorrectly. (1228, 11/14/2003)
• Plugins: When specifying command line arguments for MonitorMagic plugins, the quote characters (single and double) are no longer trimmed from the argument if the argument does not contain blank characters (spaces). (1222, 9/26/2003)
• Event monitor: The events processed by event monitors are now first stored in a file instead of RAM. In previous versions, storing the events RAM could cause memory shortage problems for very large event logs (> 750,000 events). (1228, 11/14/2003)
• Event monitor: When a system is rebooted, the processing of event monitors is now more robust. In previous versions, the MonitorMagic service could process event monitors incorrectly when monitoring computers that were shutting down or rebooting. (1228, 11/14/2003)
• File monitor: When viewing monitored files from the monitor dialogs, the MonitorMagic user interface application crashed when the target file was deleted. This problem has been fixed. (1222, 9/26/2003)
• File monitor: When the MonitorMagic service accesses a file through the file monitor, the file is opened in shared instead of exclusive mode. This allow multiple monitors to access the same file at the same time. (1250, 2/6/2004)
• File monitor: A problem regarding the analysis of text files is fixed. Under some circumstances, the MonitorMagic service could crash on subsequent updates of monitored text files with a file size greater then 40k bytes. (1271 4/29/2004)
• Command monitor: A resource leak problem has been solved. The problem caused the MonitorMagic service to use 2 resource handles when a command monitor was processed. The handles were never released. After a long time this could cause the computer running the MonitorMagic service to run out of resources. This could happen after a day (1000 command monitors, processed every minute) or after a year (40 command monitors, processed every 15 minutes). (1228, 11/14/2003)
• Command monitor: A problem regarding the termination of a process started by a command monitor is solved. There is always some risk involved when terminating a process. In previous versions, the termination of the started process could cause the MonitorMagic service to crash. The implementation is now more robust. (1228, 11/14/2003)
• Disk Monitor: When retrieving disk information for all disks on a system, use is made of administrative shares (C$, D$, ADMIN$) if available, instead of an arbitrary existing share to the disk, this is because an arbitrary share may have security settings that prevent the collecting of disk information. (1275, 6/9/2004)
• SNMP Get Monitor: On windows 2003 systems, The SNMP monitors could stop functioning after some time (showing a data error status for the particular monitor in the GUI). This has been fixed (1276, 7/8/2004)
• Alarm action, E-mail: The SMTP E-mail implementation of the MonitorMagic service has been improved. It now more strictly complies with RFC's 821 and 822. In previous versions, the E-mail alarm actions could fail when using an SMTP server that strictly obeys the RFC's only. (1228, 11/14/2003)
• Alarm action, Popup: When multiple destinations are specified by using a single service keyword, the destinations are now correctly extracted from the specified keyword. (1273, 05/14/2004)
• MonitorMagic user-interface: A problem with configuration file NmDesktop.cfg is fixed. In build 1239 only, the user-interface could not upgrade the file. As a result the user had to delete this file to startup the user-interface. (1242, 12/17/2003)
• Database: The mechanism to store event records into an SQL Server database has been updated. The new implementation is much faster but uses a little more disk space. (1223, 10/3/2003)
• Database: The mechanism to store event records into an MS Access (Jet) database has been updated. The new implementation is much faster but uses a little more disk space. (1239, 12/12/2003)
• Database: The mechanism to store event records into an MS Access (Jet) database is again improved (see also build 1239, 12/12/2003). Depending on the size of the database, the new implementation is 10-1000 times faster compared to old versions. (1250, 2/6/2004)
• Database: Localization problems in database functions are resolved. These problems could occur in for instance Japanese, German, French and Dutch versions of Windows and or SQL Server. (1250, 2/6/2004)
• Database: A problem with the ' character is solved. When a text field of a monitor contains the '-character, the MonitorMagic service could not save the monitor data in the database. The problem is solved.(1271, 4/29/2004)
• Pager: A problem with the display of information in the pager log files is solved (1271, 4/29/2004)
• Cosmetic: A various locations in the MonitorMagic user interface, the lists from expandable list boxes do now get the appropriate width to show all visible strings completely. (1222, 9/26/2003)
• License: When using a ping monitor, the calculation of the number connected systems was one higher than the actual number, which could lead to license issues. this has been fixed.(1276, 7/8/2004)
• General: Changes made to local policies, and manual changes to the local network tree are now automatically saved to disk within 30 seconds after modification, and not only when exiting the GUI. This prevents the loss of the modifications in case of an irregular shutdown of the GUI, for instance when the client computer is powered off. (1279, 7/26/2004)
  

MonitorMagic 5.0 build 1209, Release date 7-03-2003

Features:

• Control center: A new control window is introduced: the MonitorMagic control center. The window shows all MonitorMagic services to which the MonitorMagic client is connected. See Control center for more information (1209, 7/3/2003).
• Reports: Supports powerful reporting capabilities, including report data collection, storage and report generation. The product ships with a number of predefined report templates you can use to generate reports. (1189, 2/28/2003)
• Monitor rules: For all monitor types, you can use the last monitor evaluation time as a rule criteria. This allows you to let the MonitorMagic execute different alarm actions at different evaluation times, e.g. E-mail from 9AM to 5PM and a SMS message during all other hours. (1189, 2/28/2003)
• Ping monitor: The ping monitor now supports the fields Pings failed and Total pings failed. The fiel Pings failed is reset to zero when an alarm action is executed for the monitor. (1189, 2/28/2003)
  

Fixes:

• Database: MonitorMagic now supports both Windows 2000/NT Authentication and SQL Server authentication. In previous versions, the SQL Server authentication method was not working properly. (1189, 2/28/2003)
• Database: A problem when using SQL Server 7 has been fixed. In some MonitorMagic build versions, the problem caused an error when the SQL Server 7 database was created. (1189, 2/28/2003)
• Database: When an error occurs storing monitor data in to the database, the database connection is now automatically shutdown and re-setup by the MonitorMagic service. (1189, 2/28/2003)
• Monitors: When creating a monitor directly from within the monitor window, the configured scheduling information is now correctly saved. In previous version, the program always used the default scheduling parameters. (1189, 2/28/2003)
• Monitors: The scheduling of monitors is improved. When the MonitorMagic service is restarted, the monitor scheduling time are re-evaluated and monitors are not immediately executed. (1209, 7/3/2003).
• E-mail: The MonitorMagic service E-mail software has been updated to prevent problems when sending multiple E-mails at the same time. (1195, 4/25/2003)
• Ping monitor: When specifying a range to find responding TCP/IP addresses, the program now also accepts a zero (0) as part of the address. (1189, 2/28/2003)
• SNMP get monitor: The automatic name generation of SNMP get monitors is now correct. (1189, 2/28/2003)
• Ping monitor: When specifying a range for TCP/IP destination addresses, the last address is now included. (1209, 7/3/2003).
• Pager: The recipient (pager number) of the pager alarm action can now contain keywords. (1209, 7/3/2003).
• MonitorMagic client: The network tree now supports drag-scrolling (When you drag an item to the bottom of the window, the window starts scrolling automatically). (1189, 2/28/2003)
• MonitorMagic client-service: A different mechanism is used to setup the communication between MonitorMagic client and service. In previous versions, the MonitorMagic client application was not always able to find the TCP/IP address of the computer running the MonitorMagic service. (1189, 2/28/2003)
• Policies: When creating a monitor policy with a name that is already in use, you can now rename the policy. (1189, 2/28/2003)
• Cosmetic: A number of menu items have been updated to reflect the appearance of a new window when selected (...). (1189, 2/28/2003)
• Cosmetic: When changing the order of alarm actions, the corresponding alarm action icon images are now updated as well. (1209, 7/3/2003).

MonitorMagic 4.2 build 1168, Release date 11-29-2002

Features:

• Report data collection: event log archiving: Support to archive any event log from any computer is included. See Reporting: Overview for more information. (1166, 11/22/2002)
• Command monitor: A generic command monitor is now supported. The command monitor can execute any executable, script and batch file and process the output to update rules and execute alarm actions. (1148, 10/4/2002)
• MonitorMagic Plugins: To extend the monitoring capabilities of MonitorMagic, the MonitorMagic Plugins are introduced. MonitorMagic Plugins are separate monitoring applications that are part of the MonitorMagic software. The plugins can be used with command monitors for instance to monitor a web page or specifc port on a host. (1148, 10/4/2002)
• Database: To limit the database size it is now possible to delete old data from the database automatically. (1157, 11/1/2002)
• 3-dimensional graphics: The MonitorMagic user interface supports 3 dimensional graphs. (1148, 10/4/2002)
• Snmp get monitor: A new monitor is introduced to collect information from any host that supports SNMP. By using the new type of monitor, you can now monitor any device that support SNMP, including computer that run other operating systems (Unix, Linux, Novell) and many other types of devices like bridges, routers, hubs, switches and so on. See Snmp get monitor - Overview for more information. (1124, 6/14/2002)
• Snmp trap monitor: The MonitorMagic service is now able to receive SNMP traps from any other device that generates SNMP traps. On its turn, the MonitorMagic service can process the SNMP trap and associated information, and execute new alarm actions. See Snmp trap monitor: Overview for more information. (1124, 6/14/2002)
• Network browse window: A new enhanced network browse window replaces the original implementation. The new browse window supports the 2003/XP/ 2000/NT platforms, saves and restores the current tree state and allows you to create folders and manual entries of computers. See Network browse window for more information. (1135, 8/2/2002)
• Alarm action, E-mail: MonitorMagic now supports sending authenticated SMTP E-mail messages. See SMTP E-mail setup for more information. (1124, 6/14/2002)
• Alarm action, Pager - SMS: MonitorMagic now supports the ServerSMS GSM Device from Anrich Systems to send SMS messages. See Pager - SMS provider selection for more information. (1168, 11/29/2002)
• Service monitor: The service monitor now contains a new field that indicates a service state change. The field can be used in rules to trigger certain alarm actions when the alarm action should not be executed when the monitor is created. (1124, 6/14/2002)
• File monitor: The file monitor is extended with 2 new fields: File accessed and File changed. The two fields can be used to trigger rules and execute actions when a file has been accessed or changed. (1124, 6/14/2002)
• Rules: For text items, the does not contain and is not equal to operators are added. (1138, 8/22/2002)
• MonitorMagic service: The MonitorMagic service is now installed as a service that is dependent on the following services: Event log, Workstation service. In previous version a reboot of the computer could cause the MonitorMagic service not to startup properly because one of these services was not already running. (1124, 6/14/2002)

Fixes:

• Report data collection: A problem has been fixed regarding the storage of collected report information in the MonitorMagic database. The error occurred on systems running Windows NT version 4 only. When the MonitorMagic service tried to store the content of temporary files in the database, the service could crash on Windows NT 4 systems. See Reporting - Report profile data storage for more information. (1168, 11/29/2002)
• Performance monitor: A problem is fixed that might cause the MonitorMagic service to crash when the system was rebooted. The crash occured when the service was configured to monitor multiple performance counters of performance objects that were not initialized when the service started monitoring. In this case, the computer application log contained the event message: "Error: Error -1 initializing performance counter cache query on computer ...". (1157, 11/1/2002)
• Service monitor: When creating a service monitor, it was not possible in previous versions to select a service with a comma in the display name. The problem has been fixed. (1124, 6/14/2002)
• File monitor: You can now define rule criteria based on the file size in bytes. In previous version, this was not possible. (1124, 6/14/2002)
• Ping monitor: A memory problem for ping monitors has been fixed. The problem caused the ping monitor to use little extra memory every time the monitor was processed. Eventually this could cause severe problems for the MonitorMagic service to run. (1135, 8/2/2002)
• Ping monitor: When storing ping response time values into the database and no response is received for a ping monitor, a value of 999999 is now stored in the database. (1138, 8/22/2002)
• File monitor: A problem with file size evaluation has been fixed. Rules on files sizes are now evaluated correctly. (1135, 8/2/2002)
• Command monitor: When editing a command monitor policy, the name of the command monitor is now processed correctly. (1147, 10/4/2002)
• SNMP trap monitor: When multiple SNMP traps are received by the MonitorMagic service, the evaluation of rules and execution of alarm actions is done for each received SNMP trap. (1125, 6/14/2002)
• SNMP trap monitor: You can now create rules with field criteria that are object identifiers, for instance the trap monitor fields Enterprise and Trap data oid's. (1126, 6/17/2002)
• Cluster monitor: A memory leak has been taken care of. The leak caused the MonitorMagic service to use a little memory when processing a cluster monitor. (1168, 11/29/2002)
• Cluster monitor: When applying a policy containing cluster monitors, the cluster monitors now obtain the correct scheduling parameters. In previous version, the scheduling parameters for cluster monitors were always set to a 60 seconds interval. (1168, 11/29/2002)
• Monitor policies: You can change the name of a monitor in a monitor policy with the Rename menu option. (1124, 6/14/2002)
• Monitor policies: When deleting a monitor policies, you will be asked to confirm the deletion of the monitor policy. (1166, 11/22/2002)
• Alarm action, E-mail: When specifying multiple E-mail addresses, the same message was sent to multiple destinations. The problem is fixed. (1124, 6/14/2002)
• Alarm action, E-mail: MonitorMagic now supports sending authenticated SMTP E-mail messages. See SMTP E-mail setup for more information. (1124, 6/14/2002)
• Database: A problem is fixed when using a database and monitors for which data must not be stored in the database. The problem caused a number of eventlog messages to be generated in the application log. (1160, 11/13/2002)
• Database: A problem has been fixed causing database maintainenance each time the MonitorMagic service was started. The problem occurred only for build version 1166 and only caused a delay for the MonitorMagic service to startup. (1168, 11/29/2002)
• 3D graphs: Printing of 3D graphs is supported. (1157, 11/1/2002)
• 3D graphs: 3D graphs can be read and saved in files. (1157, 11/1/2002)
• 3D graphs: The 3D graphs automatically update the projection depth parameters to ensure that all graphs elements are visible in the graph window. (1157, 11/1/2002)
• On-line help: The on-line help is no longer Always on top by default. (1124, 6/14/2002)
• MonitorMagic service: The MonitorMagic service is now installed as a service that is dependent on the following services: Event log, Workstation service. In previous version a reboot of the computer could cause the MonitorMagic service not to startup properly because one of these services was not already running. (1124, 6/14/2002)
• MonitorMagic service: A problem has been fixed that could cause the MonitorMagic service to crash during initialization when multiple Snmp get monitors were maintained by the MonitorMagic service. (1126, 6/17/2002)
• MonitorMagic service: A problem has been fixed that could cause problems when installing the MonitorMagic service. In some circumstances, MonitorMagic tried to copy the service setup files from the non existing directory ......NSVCSETUP. When installing the MonitorMagic service, the following error message was shown: "Error 3 copying file C:Program FilesMonitorMagicNSVCSETUPNM.EX_ to ... (1135, 8/2/2002)
• MonitorMagic service: When the MonitorMagic service fails for whatever reason to collect computers from the local domain, no error message is written to the event log. The message is only written if debug logging is enabled. (1135, 8/2/2002)
• MonitorMagic service: When the service is not able to stop since threads continue running for whatever reason, the service will continue the stopping process after 5 minutes. (1135, 8/2/2002)
• MonitorMagic service: Various error messages regarding performance counter monitors are improved. (1135, 8/2/2002)
• MonitorMagic service setup: A problem is fixed related to the length of a domain or workgroup name. During the setup of the MonitorMagic service, the following message was shown: "Error 122 looking up account SID for account with RID=501 ...". The problem caused the MonitorMagic service not to be installed. (1138, 8/22/2002)
• Web interface: When terminating a process on a remote machine (e.g. not the machine that runs the MonitorMagic service) from the MonitorMagic web interface, a problem could occur causing the process not to terminate. The problem has been fixed. (1157, 11/1/2002)
• Web interface: From the MonitorMagic web interface it is now possible to reboot and shutdown the computer that runs the MonitorMagic service. In previous versions, it was only possible to shutdown and reboot other computers. (1157, 11/1/2002)
• Web interface: From the MonitorMagic web interface you can now (again) acknowledge rules that are maintained by the MonitorMagic service that runs the MonitorMagic Web Service. In a previous version, you could only acknowledge a rule of a MonitorMagic service running on another computer then the computer that was running the MonitorMagic Web Service. (1157, 11/1/2002)
• General: The licensing model now supports site licenses. (1136, 8/14/2002)
• Cosmetic: When creating a rule for an Events monitor in the policy tree, the icon shown for the rule is now always correct. (1124, 6/14/2002)
• Cosmetic: When sending an SMTP E-mail test message from within the MonitorMagic client application, an hourglass is shown until the action is completed. (1135, 8/2/2002)
• Cosmetic: In the MonitorMagic help file, the link to the Tools4ever web site's partners page is now OK. (1135, 8/2/2002)
• Cosmetic: When changing the plugin in the command monitor specification window, the directory location list in updated correctly. (1147, 10/4/2002)
• Cosmetic: The Apply policy sub menu option of the main Computer menu is now correct. (1157, 11/1/2002)

MonitorMagic 3.0 build 1112, Release date 05-03-2002

Features:

• File monitor: A new monitor is introduced to monitor (log) files, check the existance of files, search for text in files etc. The new monitor also allows you to view the content of any file, both in the MonitorMagic user interface application and web interface. (1112, 5/3/2002)
• Database: Full database support for SQL Server, MS Access and ODBC compliant databases. See Database - Introduction for more information. (1085, 3/8/2002)
• Graphs: Supports historical and real-time graphs. See Graph window - Introduction for more information. (1085, 3/8/2002)
• Reporting: Supports printing of graphs and printing of monitor reports. (1085, 3/8/2002)
• Reporting: More extensive logging information is available for the MonitorMagic user-interface. See Logging information for more information. (1094, 3/21/2002)
• General: You can now set an option to place the Help window always on top or not always on top. (1094, 3/21/2002)
• Policies: Supports storing monitor policies at a central location. This way, multiple MonitorMagic clients can share the same policies. See Local and central monitor policies. (1094, 3/21/2002)
• Web Interface: A function is added in order to update the domains and computer tree shown in the MonitorMagic Web Interface. (1112, 5/3/2002)

Fixes:

• MonitorMagic service: The MonitorMagic service now correctly reports the Stopped status. In previous versions, the service reported the status Stopped status before it was actually stopped. This could cause problems when upgrading the MonitorMagic service to a new version. A workaround would be stopping the service before upgrading. (1094, 3/21/2002)
• MonitorMagic service: When deleting the MonitorMagic service from a computer, you can not optionally delete all directories and files created by the MonitorMagic service. (1112, 5/3/2002)
• MonitorMagic service: You can no longer downgrade the MonitorMagic service when connecting with a MonitorMagic user-interface of an older version. (1112, 5/3/2002)
• Performance counters: A problem is fixed when collecting performance counter information from multiple counters at the same time. The problem caused a lot of event log message to be generated ( related to error code 21) in the application log. (1094, 3/21/2002)
• Performance counters: The threading mechanism used to obtain performance counter information is improved. (1102, 3/29/2002)
• Performance counters: When a performance counter monitor of a specific instance cannot find the instance, no error message is written to the aplication log. The message is only generated if service debug logging is enabled. (1112, 5/3/2002)
• Graphs: A problem in build 1094 causing graph windows not to be restored automatically when starting the MonitorMagic client has been resolved. (1102, 3/29/2002)
• Graphs: The description of disk monitors shown in the legend of a graph is updated and now contains the name of the logical disk. (1112, 5/3/2002)
• Policies: You can now export selected monitor policies to a file. In previous versions, the export of local and central policies was not supported. (1102, 3/29/2002)
• Policies: Imported central policies are now processed correctly. (1105, 4/3/2002)
• SNMP: A problem sending SNMP traps is fixed. In some circumstances, the bug caused the MonitorMagic service to generate but not send the trap. (1094, 3/21/2002)
• Database: The MonitorMagic can use up a lot of internal memory when using the MS Access database. This is due to the design of the MS Access Jet engine. For more information on this subject, please refer to Microsoft's knowledgebase article Q154384. To release memory, the database is closed and re-opened by the MonitorMagic service automatically every hour. To change the interval delay time, see MonitorMagic service registry settings. (1102, 3/29/2002)
• Database: The Back button in the wizard to create and setup and MS Access database is now enabled in the last window of the wizard. (1105, 4/3/2002)
• General: In various Windows in the MonitorMagic user interface application, browse functionality to find and select users and groups in Windows 2000/NT is now available. (1102, 3/29/2002)
• Cluster monitor: The cluster resource monitors are now shown correctly in the MonitorMagic web interface. (1105, 4/3/2002)
• Online help: The Release notes button referring to the online help in the MonitorMagic About box now opens the correct topic when pressed. (1102, 3/29/2002)
• Online help: When pressing the Help button or F1 in the tab Database from the monitor properties window, the correct help topic is now shown. (1102, 3/29/2002)
• Cosmetic: Several misspellings in the online help and windows are corrected. (1102, 3/29/2002)
• Cosmetic: The buttons shown in the introduction tour are updated to Next and Finish when the user changes the selected option. (1102, 3/29/2002)
• Cosmetic: When a policy is applied, the user must select a computer running the MonitorMagic service (This depends on the policy specification). When no computer is selected from this window, the OK button is grayed. (1105, 4/3/2002)
• Cosmetic: When no monitor policies are available the main menu options Computer, Apply policy, Central monitor policies and Local monitor policies now show an empty menu item. (1102, 3/29/2002)
• Cosmetic: When no monitos are selected in the monitor window and only status information describing the connection status with the MonitorMagic service is shown, the menu options Edit, Delete and View, Properties are grayed out and cannot be selected. (1105, 4/3/2002)
• Cosmetic: The menu options Policy, Import policies... and Policy, Export policies... are updated when the active window is changed and a message is shown when the menu option cannot be executed. (1105, 4/3/2002)
• Cosmetic: The Apply buttons in various tabbed windows are no longer shown if they had no function. In previous version, the buttons were grayed out. (1105, 4/3/2002)
• Cosmetic: The window to change database storage settings for multiple monitors has been changed. (1105, 4/3/2002)
• Cosmetic: When the Local monitor policies and Central monitor policies contain no policies, and a new policies is created, the corresponding item is automatically expanded. (1105, 4/3/2002)

MonitorMagic 2.0 build 1074, Release date 01-31-2002

Features:

• Support SNMP traps. See SNMP traps for more information (1074, 1/31/2002).
• Support sending pager - SMS messages using a modem (1074, 1/31/2002).
• Dragging a policy directly to a open Monitor Window is now supported; (1060).
• In the web interface, in you can now view MonitorMagic rules and acknowledge them when triggered.(1060)
• The possibility to terminate processes through the web interface is added. (1060)
• Implemented the option to enable anonymous access to the web interface. The option to use the Service account has been removed.(1060).
• Added several pre-configured example policies. (1065)

Fixes:

• Web interface: A problem to acknowledge rules has been fixed.
• Web interface: Performance counter icons are now displayed correctly.
• When creating a monitor on processes, the "add" button is now correctly enabled when specifying the the name of the monitored process manually instead of from the list of running processes. (1060)
• When connecting with SSL to the browser, and entering an incorrect password, the notification to the user was unclear(1060).
• An alarm action could be configured to fire when a rule is "no longer triggered". The alarm action was however not actually fired. Now it correctly is. (1060)
• An alarm action could be specified to fire when "rule triggered and not acknowledged within ... minutes". This wait time was incorrectly calculated relative to the time that the rule criteria where exceeded, and not relative to the time that the rule was triggered. (a rule can be specified to trigger only after the criteria are exceeded for a specified amount of time). Now the time the program waits for the acknowledgment is relative to the time at which the rule triggered.(1060)
• Slightly modified the position of some buttons in window for editing monitors to prevent accidentally pressing the cancel button. (1060)
• When renaming alarm actions directly in a active monitor, the alarm action was duplicated instead of renamed. Now it correctly renames.(1060)
• When a monitor was created on a specific server, e.g. by applying a policy, the monitor was always executed once on creation. For monitors that should execute at a fixed time this does not happen anymore(1060).
• Windows XP computers showed up in the browse window with the description of the computer name, instead of the real computer name, which caused connection problems. Now XP computers are also listed with their real computer name (1060).
• Fixed a missing picture (Mmeventlog.jpg) in the web interface.(1060)
• The license mechanism did not correctly distinguish workstations and servers. Workstations where counted as servers. It now correctly distinguishes them. (1060)
• When upgrading the service, the service installation dialog will show the current license key for the service, and other current service settings. (1060)
• On slow or busy computers, when upgrading the service, the GUI tried to connect to the service before the service was sufficiently initialized which caused a connection failure after the upgrade. This has been fixed. (1060)
• In the Monitor Window , if a process is monitored, the field "Time running" did not always show 0 if the process was stopped. (1060)
• When sending popup messages to multiple destinations, the destinations can also be separated by a return character. (1060)
• When using the web interface, if the user account had not enough rights to show the specific data, the first time a specific web page was browsed this was reported correctly, but the second time it just showed no specific data. Now it will then also report the correct info about the insufficient rights.(1060)
• In the dialog for configuring the access rights to the web interface, when entering a user name you may now enter either a forward or a backward slash between the domain name and the user name.(1060)
• When a demo licence was expired, the Gui displayed "demo license expired for 0 days".