MonitorMagic - Tools4Ever.com

MonitorMagic

Table Of Contents 

MonitorMagic Quick Start Guide...................................................................................................... 1 

Welcome to MonitorMagic ........................................................................................................... 1 

Quick start guide (15 minutes)..................................................................................................... 1 

Prerequisites............................................................................................................................. 1 

MonitorMagic client Installation ................................................................................................ 2 

MonitorMagic service installation ............................................................................................. 2 

Features ....................................................................................................................................... 5 

MonitorMagics' main features: ................................................................................................. 5 

Monitored components:............................................................................................................ 6 

Action and Alerting capabilities: ............................................................................................... 6 

Release notes.................................................................................................................................. 7 

MonitorMagic version 6................................................................................................................ 7 

Features MonitorMagic version 6............................................................................................. 7 

Fixes MonitorMagic version 6................................................................................................... 8 

MonitorMagic version 5.............................................................................................................. 10 

Features MonitorMagic version 5........................................................................................... 10 

Fixes MonitorMagic version 5................................................................................................. 10 


Features MonitorMagic version 4.2........................................................................................ 11 

Fixes MonitorMagic version 4.2.............................................................................................. 12 








Features ................................................................................................................................. 18 


Setup ............................................................................................................................................. 21 

Setup MonitorMagic ................................................................................................................... 21 

Introduction............................................................................................................................. 21 

MonitorMagic software package ............................................................................................ 21 

Requirements............................................................................................................................. 21 

Upgrading MonitorMagic............................................................................................................ 22 

MonitorMagic license ................................................................................................................. 22 

Demo and purchased version ................................................................................................ 22 

MonitorMagic license.............................................................................................................. 23 

How to find the NETBIOS domain name of the computer running the MonitorMagic service 

(Windows NT 4.0)................................................................................................................... 24 

How to find the NETBIOS domain name of the computer running the MonitorMagic service 

(Windows 2000) ..................................................................................................................... 26 

Specifying the MonitorMagic service license code................................................................. 29 

MonitorMagic license codes for multiple services and domains ............................................ 31 

MonitorMagic Web Interface license ...................................................................................... 32 

Using MonitorMagic....................................................................................................................... 35 

Policies, Monitors, Rules and Alarm actions.............................................................................. 35 

Policies ................................................................................................................................... 35 

Monitors.................................................................................................................................. 50 

Rules .................................................................................................................................... 121 

Alarm actions........................................................................................................................ 130 

Pre-defined Policies ............................................................................................................. 159 

Reporting.................................................................................................................................. 166 

iii

MonitorMagic 

Reporting - Overview............................................................................................................ 166 

Report data collection........................................................................................................... 167 

Report generation................................................................................................................. 175 

Report builder....................................................................................................................... 177 

Report E-mail distribution ..................................................................................................... 207 

MonitorMagic client .................................................................................................................. 209 

Different types of windows ................................................................................................... 209 

Network browse window....................................................................................................... 212 

Window navigation ............................................................................................................... 213 

Control center....................................................................................................................... 215 

Global alarm window ............................................................................................................ 218 

Monitor window .................................................................................................................... 219 

Graphs.................................................................................................................................. 231 

MonitorMagic service ............................................................................................................... 256 

Installing and upgrading the MonitorMagic service.............................................................. 256 

MonitorMagic service setup.................................................................................................. 257 

Single versus multiple MonitorMagic services ..................................................................... 260 

Deleting the MonitorMagic service ....................................................................................... 261 

Logging information.............................................................................................................. 262 

Checking the MonitorMagic service ..................................................................................... 263 

Advanced.............................................................................................................................. 271 

MonitorMagic topics..................................................................................................................... 273 

Configuring the MonitorMagic service ..................................................................................... 273 

Access Rights .......................................................................................................................... 273 

Different types of access rights ............................................................................................ 273 

Specifying MonitorMagic access rights ................................................................................ 274 

Keywords ................................................................................................................................. 275 

Keywords overview .............................................................................................................. 275 

Monitor keywords ................................................................................................................. 276 

Custom keywords................................................................................................................. 276 

SNMP....................................................................................................................................... 277 

MonitorMagic SNMP support ............................................................................................... 277 

MonitorMagic SNMP requirements ...................................................................................... 277 

SNMP traps .......................................................................................................................... 278 

Pager - SMS............................................................................................................................. 287 

Introduction to pager - SMS ................................................................................................. 287 

Pager - SMS installation and configuration overview........................................................... 288 

Pager - SMS modem installation and configuration............................................................. 288 

Pager - SMS provider selection............................................................................................ 291 

Pager - SMS managing provider configuration settings....................................................... 293 

Pager - SMS adding provider configuration settings............................................................ 294 

Pager - SMS message ......................................................................................................... 295 

Pager - SMS script ............................................................................................................... 297 

Pager - SMS troubleshooting ............................................................................................... 301 

Database.................................................................................................................................. 302 

Database - Introduction ........................................................................................................ 302 

Database - Supported databases ........................................................................................ 303 

Database - MS Access......................................................................................................... 303 

Database - SQL Server ........................................................................................................ 304 

Database - Viewing the database status.............................................................................. 304 

Create a new database ........................................................................................................ 305 

Use an existing database ..................................................................................................... 311 

Database - Delete old data................................................................................................... 313 

Database - Stop using a database....................................................................................... 315 

Database - System Data Sources........................................................................................ 315 

Database - Troubleshooting................................................................................................. 315 

iv

Table Of Contents 

MonitorMagic Plugins............................................................................................................... 315 

MonitorMagic Plugins ........................................................................................................... 316 

Plugin - T4eWebPing ........................................................................................................... 316 

Plugin - T4ePortPing ............................................................................................................ 317 

Plugin - T4eDirSize .............................................................................................................. 317 

Plugin - T4eSql..................................................................................................................... 318 

Plugin - T4eRexec................................................................................................................ 319 

Plugin - T4eUnixInfo............................................................................................................. 321 

MonitorMagic Web Interface........................................................................................................ 323 

Introduction to the MonitorMagic Web Interface ...................................................................... 323 

Installing and configuring the MonitorMagic Web Interface..................................................... 324 

MonitorMagic Web Interface scenarios................................................................................ 324 

Installation and configuration procedure .............................................................................. 325 

Configure MonitorMagic WebService: General.................................................................... 325 

Configure MonitorMagic WebService: HTTP ....................................................................... 327 

Configure MonitorMagic WebService: HTTPS..................................................................... 329 

Configure MonitorMagic WebService: Configure Certificate................................................ 330 

Configure MonitorMagic WebService: Save Certificate ....................................................... 332 

Configure MonitorMagic WebService: Access Rights.......................................................... 334 

Configure MonitorMagic WebService: Proxy MonitorMagic service .................................... 335 

WebService Access Rights (per computer) ......................................................................... 336 

Specify computer web access.............................................................................................. 338 

WebService Access Rights (per account)............................................................................ 340 

MonitorMagic Web Interface license .................................................................................... 343 

Security and the MonitorMagic Web Interface......................................................................... 343 

HTTP is not safe and secure................................................................................................ 343 

HTTPS is safe and secure ................................................................................................... 343 

Certificates............................................................................................................................ 344 

Man in the middle attack ...................................................................................................... 345 

Web site pages of the MonitorMagic Web Interface................................................................ 346 

Web interface navigation...................................................................................................... 346 

System Info........................................................................................................................... 347 

Services................................................................................................................................ 348 

Event logs............................................................................................................................. 350 

Processes............................................................................................................................. 351 

Monitors................................................................................................................................ 353 

Commands ........................................................................................................................... 354 

Examples ..................................................................................................................................... 355 

Quick start guide (15 minutes)................................................................................................. 355 

Prerequisites......................................................................................................................... 355 

MonitorMagic client Installation ............................................................................................ 355 

MonitorMagic service installation ......................................................................................... 355 

FAQ's ........................................................................................................................................... 359 

How can I open the network browse window?......................................................................... 359 

Do I need to install the MonitorMagic service on each monitored computer?......................... 359 

Why do I get all these application event log messages?......................................................... 359 

Why do I get all these application event log messages (2) - (error 2003)? ............................. 360 

Why do I get all these application event log messages (3) - (error 1008)? ............................. 360 

Index ............................................................................................................................................ 363 

v

MonitorMagic Quick Start Guide 

Welcome to MonitorMagic 

Welcome to MonitorMagic, the premium monitoring, alerting and reporting tool for 

Windows NT and Windows 2000 networks. 

MonitorMagic saves network administrators valuable time by monitoring the network and 

providing important management information. In spite of its powerful features, it is extremely easy 

to use. MonitorMagic greatly simplifies the implementation of network management by using a 

predefined and customizable set of monitoring and alerting criteria, called policies. MonitorMagic 

is a complete network monitoring and management solution. Its alerting capabilities include 

advanced escalation features. 

Besides monitoring and alerting another important feature of Monitor Magic 5.0 is reporting. This 

valuable addition makes Monitor Magic unique in the network management market. With the 

same simplicity as with monitoring and alerting network administrators can generate reports in 

which every kind of event log information can be presented in any format that is desired. 

See also: 

Quick start guide 

Quick start guide (15 minutes) 

This section describes how to start using MonitorMagic immediately. It will take you only 15 

minutes to setup a MonitorMagic service and configure some monitors, rules and alarm actions. 

reports. 

Prerequisites 

 

Make sure you have the latest version of MonitorMagic installed. The software is 

available from www.tools4ever.com. 

1


Log on as an administrator to a computer of one of the following types: Windows NT 4 

workstation or server, any Windows 2000 version including: Windows 2000 Professional, 

Windows 2000 Server, or Windows 2000 Advanced server. 

MonitorMagic client Installation 

 

Install the MonitorMagic software on the computer. The MonitorMagic software is 

contained in the software package SetupMonitorMagic.exe. This package contains all of 

MonitorMagics' software components. 

MonitorMagic service installation 

 

 

Start the MonitorMagic client. When you run the MonitorMagic client for the 1st time a 

wizard will start which introduces the package. Run the wizard to start the introduction or 

continue by using the procedure described in this section to skip it. To skip the wizard 

answer no to the wizards' 1st question. 

The MonitorMagic client shows up with a screen that is mostly empty and a network 

browse window on the left. To run MonitorMagic you need to have at least one 

MonitorMagic service installed. To start installing the MonitorMagic service, browse to the 

machine you are working on, right click the machine name and select the menu option 

Setup service. 

 

The MonitorMagic Service Setup dialog appears. The dialog is used to specify all the 

parameters needed to install the MonitorMagic service. By default, MonitorMagic fills in 

the Server name(s) section. If you are a member of the Domain Admins group of the 

domain you are logged on to, you don't need to specify any other parameters. Leave the 

Serial number blank and press the button Install/Upgrade. 

2


 

 

When the service has been successfully installed, MonitorMagic will open a monitor 

window that connects to the MonitorMagic service just installed. The new monitor window 

will show a single line of text, informing you that there is nothing to show ("Connection 

established with computer xxx. No monitors configured, nothing to show here ..."). 

To start monitoring you must apply a monitor policy to the computer. Select the name of 

the local computer in the network browse window, right click the mouse, and select the 

menu options Apply policy, then Disks standard control. MonitorMagic will find and start 

monitoring the disks on the computer according to the applied policy. Some rules and 

alarm actions will be created and executed. The rules of the monitors will check if the 

available disk space is less than 10%. When this occurs, a popup message is sent to the 

current machine. 

 

The results are shown in the new monitor window. If a rule is violated and triggered, the 

color of the monitored object will change. In the top part of the monitor window you can 

see the monitored objects (monitors). When a monitor is selected, you can see the 

associated rules in the bottom part of the monitor window. 

3


To summarize the previous steps: The MonitorMagic service is now installed on the local 

computer. From the MonitorMagic client a policy is applied. The policy contains disk monitors. 

Each disk monitor has a rule which checkins for available disk space. If the rule is violated, a 

popup message is sent to the local machine. You can now continue applying other policies to the 

same machine, or apply this policy to other machines. Next, you can configure your own policies 

and apply them to various systems. 

Generate your first Report 

To get an idea of how reporting works generate a report from one of our templates. First select a 

computer in the "Network" tab. Now select the "Reports" tab and click on the template you want 

to use, right click the mouse and select "open report template". You will now see what this 

template looks like. Select "generate report" from the menu bar or by right clicking your mouse 

and you will be presented with the report. 

If you want to create your own Reports, check out the Reporting part of the Help. 

4


Related topics: 

Policies, Monitors, Rules and Alarm actions 

Installing the MonitorMagic service 

Reporting - Overview 

Features 

MonitorMagic delivers enterprise-class solutions for operations and network management of 

Windows 2000 / NT servers, workstations, and SNMP devices. MonitorMagic offers proactive 

monitoring and alerting with escalation of all possible key events. 

MonitorMagics' main features: 

 

 

 

 

 

 

 

 

 

 

Supports Windows NT/2000. 

Supports SNMP devices. 

Supports monitoring with and without agents. 

Provides a web-interface without the need to have IIS installed. 

Supports logging to databases. 

Provides extensive reporting capabilities. 

Provides data for statistical analysis and trending. 

Shipped with predefined rules & monitor policies. 

Shipped with predefined report templates. 

Supports monitor configuration using a drag-and-drop interface. 

5


Monitored components: 

 

 

 

 

 

 

 

 

Event log messages 

Disk information 

Performance data 

Service status information 

System processes 

SNMP devices 

TCP/IP devices/ports 

Files & directories 

Action and Alerting capabilities: 

 

 

 

 

 

 

 

 

 

Escalation 

Command line, script, and batch file execution 

Service & server restart 

SMS messages 

E-mail messages 

Popup messages 

SNMP traps 

Paging 

Sounds 

6

Release notes 

MonitorMagic version 6 

Features MonitorMagic version 6 

Version 6.0 build 1282, August 19, 2004 

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) 

Manual SNMP Hosts: Added the posibility to apply a policy to multiple selected SNMP 

hosts, instead of applying a policy to each seperately. (1282, 08/19/2004) 

SNMP Trap Monitor: Some actual SNMP Traps encounterd in the field contained more 

than 8 variables. Therefore the number of variables in a SNMP trap message that are 

examined by MonitorMagic, is increased to 16. (1282, 08/19/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. (1239, 12/12/2003) 

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. (1222, 9/26/2003) 

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 secure remote execution. ThePlugin - T4eSsh is a MonitorMagic plugin. 

It is used to execute remotely a command on computer running an operating system that 

supports the Secure SHell (SSH) protocol (1278, 07/20/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) 

Plugin - Unix secure information. The Plugin - T4eSSHUnixInfo is a MonitorMagic 

plugin. It is used to collect specific information from a computer running a UNIX 

7


compatible operating system. It uses the Secure Shell (SSH) protocol to retreive 

information from the remote computer (1278, 07/20/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) 

See also: 

Fixes MonitorMagic version 6 



Version 6.0 build 1282, July 26, 2004 

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 

8

Release notes 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

monitors incorrectly when monitoring computers that were shutting down or rebooting. 

(1228, 11/14/2003) 

Event monitor: when analizing many rules for the same event log monitor, there could 

occur a sharing violation on a termpory file, because of a delay in the file system. The file 

handling has been modified to prevent this. 

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) 

9


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) 

See also: 






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) 

See also: 





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) 

10

Release notes 

 

 

 

 

 

 

 

 

 

 

 

 

 

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

See also: 




Features MonitorMagic version 4.2 

Version 4.2 build 1168, November 29, 2002 

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

11


 

 

 

 

 

 

 

 

 

 

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 .NET/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) 

See also: 

Fixes MonitorMagic version 4.0 



Version 4.2 build 1168, November 29, 2002 

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) 

Report data collection: A problem has been fixed regarding the archiving of event log 

information in the MonitorMagic database. The data in column 

LogMonitorMagicComputerId of table MmLog_EventRecord is now updated correctly. 

Performance monitor: A problem is fixed that might cause the MonitorMagic service to 

crash when the system was rebooted. The crash occurred 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) 

12

Release notes 

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) 

13


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 Files\MonitorMagic\NSVCSETUP\NM.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) 

See also: 




Version 3.0 build 1113, May 24, 2002 

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) 

14

Release notes 

Process monitor: The process monitor now supports multiple instances of the same 

process. This allows you to terminate specific process instances only, for instance 

process instances causing a high processor load. (1113, 5/24/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 userinterface. 

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) 

See also: 



Version 3.0 build 1113, May 24, 2002 

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 application log. The message 

is only generated if service debug logging is enabled. (1112, 5/3/2002) 

Cluster monitor: The cluster resource monitors are now shown correctly in the 

MonitorMagic web interface. (1105, 4/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) 

15


Alarm action, 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) 

Alarm action, E-mail: The E-mail alarm action status, as shown in the MonitorMagic 

user interface application, was not correct and always showed that the action was 

successfully executed. This is fixed. (1112, 5/3/2002) 

Alarm action, E-mail: The destination address can now contain keywords. (1112, 

5/3/2002) 

Alarm action, popup message: The destination address can now contain keywords. 

(1112, 5/3/2002) 

Alarm action, shutdown - reboot computer: The alarm action to shutdown or reboot a 

computer can now also be exected for the target computer being the computer that runs 

the MonitorMagic service. (1113, 5/24/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) 

Service monitor: When creating a service monitor, it was not possible in previous 

version to select a service with a comma in the display name. The problem has been 

fixed. (1112, 5/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 monitors 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) 

16

Release notes 

See also: 





Version 2.0 build (1074), February 8, 2002 

Support SNMP traps. See SNMP traps for more information (1073, 1/31/2002). 

Support sending pager - SMS messages using a modem (1073, 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) 

Version 2.0 build (1050) 

MonitorMagic version 2.0 supports the MonitorMagic Web interface. See the 

MonitorMagic Web Interface for more information. 

Supports monitoring process. 

Supports the alarm action to terminate a process on a local or remote computer. 

Supports the alarm action to reboot or shutdown a computer. 


Version 2.0 build (1074), February 8, 2002 

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

17


 

 

 

 

 

 

 

 

 

 

 

 

 

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". 

It now correctly displays the number of days it is expired. (1060) 

The registry key containing the license info of the service is now deleted when deleting 

the MonitorMagic service.(1060) 

When configuring the webservice communication port numbers, it is verified that the port 

number is available on the system.(1060) 

Adding a new rule to an existing monitor, did only work in the policy window, not when 

directly done in the monitor window.(1060) 

Fixed the text content of several messages that may be shown in the web browser.(1060) 

 

Version 2.0 build (1050) 

Fixed an error that caused some existing monitors of the same type not to be deleted 

when this options was specified in the policy properties(1050). 

In the server browse window, in the menu option "add monitor" was no menu option 

"process" visible. It is now. (1050) 

When applying a policy to a service, the option "remove existing monitor of the same 

type" now works correctly. 

See also: 




Features 

 

Different scheduling methods are supported. See Scheduling overview for more 

information (1026). 


18

Release notes 

 

 

For E-mail messages, keywords are supported in the 'Subject' field of the message 

(1026). 

The %RESULT_DATA_TIME% keyword for eventlog messages is supported and reflects 

the correct date instead of a long number (1026). 

19

Setup 

Setup MonitorMagic 

Introduction 

Installing MonitorMagic is a simple and straightforward procedure. When you have the software 

available, it will take you only 15 minutes to completely install MonitorMagic and run the Quick 

start guide. You can install MonitorMagic on most Microsoft Windows operating systems including 

all versions of Windows 2000 and Windows NT 4.0. See requirements for more information. To 

run a fully functional version of MonitorMagic, you need to install at least one MonitorMagic client 

and one MonitorMagic service. The MonitorMagic service is always installed from within the 

MonitorMagic client. Note that you can install the MonitorMagic service on a remote computer 

with the MonitorMagic client. This section describes how to install the MonitorMagic client. Once 

installed you can install the MonitorMagic service from the installed client. 

MonitorMagic software package 

All parts of the MonitorMagic software are contained in a single package: 

SetupMonitorMagic.exe. The software package contains the MonitorMagic client software and 

the MonitorMagic server software. The MonitorMagic client is installed by running the software 

package file SetupMonitorMagic.exe. To install the MonitorMagic client, simply start (left doubleclick) 

the software package file SetupMonitorMagic.exe and follow the instructions. When 

finished, start MonitorMagic with menu option Start, Programs, MonitorMagic, MonitorMagic. 

Once started it is advised to install a MonitorMagic service first. See Installing and upgrading the 

MonitorMagic service for more information. 


Quick (15 minute) start guide (continue at section 4) 

Requirements 


Requirements 

MonitorMagic contains client and server software. Note that the client and server software are 

contained within a single software package. To install MonitorMagic you must install the 

MonitorMagic client first. From within the MonitorMagic client you need to install at least a single 

MonitorMagic service. To run the MonitorMagic software your system needs to meet the following 

requirements: 

Operating 

system 


client (required) 

Windows NT 

4.0(*) , Windows 

2000 (*), Windows 

98, Windows ME, 

Windows XP 

Processor Pentium, 133 

MHz 


client 

(recommended) 

Windows NT 4.0 

(*), Windows 2000 

(*), Windows 98, 

Windows ME, 

Windows XP 

Pentium III or 

higher, 266 MHz 

or higher 


service 

(required) 


(*), Windows 2000 

(*), Windows XP 

(server) 

Pentium, 133 

MHz 


service 

(recommended) 

Windows NT 4.0, 

Windows 2000 (*), 

Windows XP 

(server) 

Pentium III or 

higher, 266 MHz 

or higher 

21


Memory (RAM) 64 MB 128 MB or more 64 MB 128 MB or more 

Free disk space 10 MB 16 MB 16 MB 32 MB 

(*): Windows 2000 means all Microsoft Windows 2000 operating systems, including: Professional, 

Server, Advanced server, and Datacenter. Windows NT 4.0 means all Microsoft Windows NT 4.0 

versions including workstation, server, and cluster server. 

For several functions, specifc requirements exist. See the following table for more information: 

Function 

See for more information 

SNMP (receiving and sending traps, collecting 

SNMP information) 

MonitorMagic SNMP requirements 

See also: 


Upgrading MonitorMagic 

To upgrade MonitorMagic, run the software package SetupMonitorMagic.exe. See Setup 

MonitorMagic for more information. 

Upgrading from MonitorMagic release candidate versions 

When you have installed a release candidate version of MonitorMagic, you first need to 

uninstall this version completely. This is due to the fact the installation procedure no longer 

uses the Microsoft Windows Installer software. The main reason for this choice is the required 

reboot of systems running Windows NT 4.0 without Windows Installer. 

See also: 

Release notes 


MonitorMagic license 

Demo and purchased version 

When you install MonitorMagic without specifying a license code, a 30-day demo version is 

installed automatically. The demo version supports all functions and features. The 30-day period 

starts counting when you install the MonitorMagic service. After 30-days, the demo license is 

expired and the MonitorMagic service will stop functioning. To obtain a valid license code, contact 

your MonitorMagic reseller. See MonitorMagic license for more information. 

Once expired, you can still upgrade a demo version to a purchased version. All configuration 

setting will be maintained and there is no need to reconfigure any settings. You only need to 

specify a valid license code. 

See also: 


How to find the domain name of the computer running the MonitorMagic service (Windows NT 

4.0) 

How to find the domain name of the computer running the MonitorMagic service (Windows 2000) 

22

Setup 

Specifying the MonitorMagic service license code 

MonitorMagic license codes for multiple services and domains 


MonitorMagic is licensed based on the number of monitored servers(*). Each server license 

includes 10 additional licenses for monitoring and managing workstations and other devices (for 

instance SNMP devices). See the following table for more information: 

License server count 

License server 

count 

Maximum number of 

monitored servers 

Maximum number of monitored nonserver 

computers/devices 

1 1 10 

2 2 20 

3 3 30 

4 4 40 

5 5 50 

... ... ... 

N N 10 X N 

(*) A server is a computer running one of the following operating systems: Windows NT 4.0 

Server, Windows NT 4.0 Terminal Server Edition, Windows NT 4.0 Enterprise Edition, Windows 

2000 Server, Windows 2000 Advanced Server, Windows 2000 Datacenter, Windows XP Server. 

Non-server computers and devices include SNMP devices and a computer running one of the 

following operating systems: Windows NT 4.0 Workstation, Windows 2000 Professional. 

The following license code examples show the type of license needed: 

Monitored number of servers: 1, monitored number of workstations: 0. License server 

count: 1 


count: 1 


count: 2 

Monitored number of servers: 1, monitored number of SNMP devices 15, monitored 

number of workstations 35. License server count: 5 

Monitored number of servers: 12, monitored number of SNMP devices and workstations: 

40. License server count: 12. 

Note: The license you need for your organization does not depend on the number of 

MonitorMagic clients and MonitorMagic services you want to install and configure. It only 

depends on the total number of monitored servers, workstations, and other devices. 

License code 

The MonitorMagic license is issued by means of a license code. The license code is a character 

string containing 6 times 5 digits. An example of the license code is: 12345-22345-32345-42345- 

52345. The license code needs to be specified when installing a MonitorMagic service. For each 

MonitorMagic service, you need to specify a license code. The license code depends on the 

following two aspects: 

The License server count for the MonitorMagic service; 

23


 

The name of the domain, in NETBIOS format, that the computer running the 

MonitorMagic service is a member of. 

To obtain a MonitorMagic license code, you need to know the license server count and the 

NETBIOS domain name of the computer running the MonitorMagic service. If you don't know the 

NETBIOS domain name of the computer see the following sections to find the name: NT4, 

Windows2000. If the computer is not a member of a domain, MonitorMagic uses the (NETBIOS) 

name of the computer instead of the name of the domain. 

See also: 



4.0) 




How to find the NETBIOS domain name of the computer running the MonitorMagic 

service (Windows NT 4.0) 

Finding the domain name of a local computer 

To find the domain of a local computer, log on to the computer as an administrator. Start the 

Control Panel with the menu options Start, Settings, Control Panel, and start the Network 

applet. The Identification tab shows the name of the computer and the NETBIOS domain name. 

24

Setup 

Finding the domain name of a remote computer 

To find the domain name of a remote computer, log on to a Windows NT 4.0 server as an 

administrator of the domain. Start the Server Manager application with the menu options Start, 

Programs, Administrative Tools, Server Manager. The Server Manager application connects 

to the domain of the logged on user and shows all computers (servers and workstations) that are 

a member of the domain. 

If the computer is not shown, connect to the domain of the computer with menu options 

Computer, Select Domain. 

25


Select the domain, press the OK button and confirm that the computer is listed. 

In the figures shown, the domain name is FLOWERS. If you are not able to find the name of the 

domain you will need to visit the computer and execute the procedure described at the beginning 

of this section. 

See also: 






How to find the NETBIOS domain name of the computer running the MonitorMagic 

service (Windows 2000) 

To find the NETBIOS domain name of a computer running Windows 2000 you need to know the 

DNS domain name. Start the Control Panel (Start, Settings, Control Panel) and select the 

System applet. The System Properties window appears. Select the Network Identification tab. 

26

Setup 

The domain field shows the DNS name of the domain. Next, log on to a Windows 2000 domain 

controller of the domain and start the Active Directory Users and Computers application (Start, 

Programs, Administrative Tools, Active Directory Users and Computers). In the left part of 

the window right click the DNS domain name, select the menu option Properties. 

27


The properties window of the domain appears. The field Domain name (pre-Windows 2000): 

shows the NETBIOS domain name. 

28

Setup 

By default, the first part of the Windows 2000 DNS domain name (fish in 

fish.tools4ever.internal) is equal to the NETBIOS domain name. But this is not always the case 

(SEEFISH instead of FISH). 

See also: 




4.0) 




This section describes where and how to specify the license code for the MonitorMagic service 

when the MonitorMagic service is already installed and up and running. When specifying the 

license code during a fresh MonitorMagic service install, see Installing the MonitorMagic service 

for more information. 

Start the MonitorMagic client and use a network browse window to find the computer that runs the 

MonitorMagic service. Right click the mouse and select the menu option Configure service. 

29


The tabbed window Configure MonitorMagic service appears. Select the tab License code. In 

the field License code, enter the license code. Note that the domain name of the computer is 

also shown. The domain name should correspond with the name of the domain used when you 

requested a license code. When entered, you can verify the code by pressing the Verify button. 

30

Setup 

When the license code is valid you will see the type of license code. Press OK to start using the 

license code. If you press Cancel, the license code will not be updated and the MonitorMagic 

service will continue to use the original or demo code. 

Site (site licenses only) 

When you have a MonitorMagic site license code, specify the name of the licensed site in this 

field. 

See also: 




4.0) 




If you use a single MonitorMagic service you only need a single license code. The license server 

count is based on the number of servers, workstations, and devices managed with MonitorMagic. 

But if you use multiple MonitorMagic services running on computers in various domains the 

licensing situation becomes more complex. This section describes how to determine the licenses 

and license code you'll need. Simply execute the following procedure to find the correct 

information. 

 

To start , you need to add the total number of servers (S), workstations (W), and other 

devices (D) you want to monitor with MonitorMagic. These systems should all belong to 

the organization. 

31


Divide W and D by 10 and round up to the nearest integer number: 56 / 10 = 5.6 -> 6. 

The results are W' and D'. 

Determine the maximum (N) of S, W', and D'. This number N is the total license server 

count. This number should be give to your MonitorMagic reseller when obtaining the 

license code(s) for MonitorMagic. 

Determine on which computers you are going to install the MonitorMagic service. 

Create a table with 5 columns and a number of rows. Each row in this table represents a 

MonitorMagic service. Fill in the table as shown in the example: 

Computer Domain Number of 

servers (S) 

Number of 

workstations 

and other 

devices ((W+D) 

License server 

count 

TULIP FLOWERS 4 45 5 

MARS PLANETS 8 67 8 

EARTH PLANETS 2 0 2 

Total 15 

 

Create the following table by adding the license server count for rows with the same 

domain 

Domain 

License server count 

FLOWERS 5 

PLANETS 10 

Total 15 

 

The table shows the domain and license server count for each domain. This 

information will be requested by your MonitorMagic reseller, and is required to provide 

you with license codes. 

Note that different computers in the same domain use the same license code. 

See also: 




4.0) 



MonitorMagic Web Interface license 

The MonitorMagic web interface if part and parcel of the MonitorMagic product. It is not a 

separate software package; hence, it is not licensed separately. If you purchase, or have 

purchased, MonitorMagic you get the web interface at no extra cost. However, the web interface 

does comply with the restrictions of your license code. Every server license for MonitorMagic 

comes with ten workstation licenses. If you purchased a five server license for MonitorMagic you 

are able to monitor five servers and fifty workstations. The same rules apply to the web interface, 

with a five server license you will be able to view/manage five servers and fifty workstations. If 

32

Setup 

you have further questions regarding licensing please contact your Tools4ever reseller. If you do 

not know who your reseller is please see the following: Tools4ever partners. 

33

Using MonitorMagic 


Policies 

Introduction 

To make it configuration easy MonitorMagic supports monitor policies. A monitor policy is a 

collection of monitors. These monitors can contain rules and the rules can contain alarm actions. 

To get a basic understanding of these concepts you are advised to read the general topic on 

policies, monitors, rules, and alarm actions first. The monitors of a policy do not directly relate to a 

physical or software "device" of a computer. Instead, they define what monitors must be 

generated when the policy is applied to a computer. Example: A policy can contain a monitor 

called "All disks". This monitor is not yet associated with any physical disk drive of any computer. 

When the policy is applied to computer ABC, MonitorMagic will find all disks in computer ABC 

and create monitors, rules, and alarm actions for each of them. 

Thus, a policy contains the complete specification of monitors, rules, and alarm actions except for 

the name of the computer. When the policy is applied to the computer MonitorMagic generates 

the monitors for each physical or software "device" of the computer. 

Policies make it very easy to configure multiple monitors for multiple computers. When you have 

similar network servers in your network you probably want to monitor these computers the same 

way. In this case you can create a policy that meets your monitoring needs and then apply this 

policy to each of these computers. 

Note: Since MonitorMagic version 3.0, policies can be stored on the MonitorMagic client and on 

the MonitorMagic service. See Local and central monitor policies for more information. 

More information: 

Creating a new policy 

Quick start guide 

Monitor policy window 

The monitor policy window is used to create and manage monitor policies. To activate the 

monitor policy window, right click the mouse in he grey area of the MonitorMagic client application 

or activate the main menu option View. Select menu option Network - policies. The tabbed 

window contains a network browse window and the monitor policies window. At the bottom of the 

window, select the Policies tab. 

35


The monitor policy window shows all monitor policies in a tree structure. At the root level two 

entries exists: Central monitor policies and Local monitor policies. The Central monitor 

policies are the policies stored on a central location that can be shared by multiple MonitorMagic 

application. Monitor policies stored under Local monitor policies are stored in a local file, that 

can be accessed by this MonitorMagic client applictions only. See Local and central monitor 

policies for more information. If you open the Local monitor policies item, you will see all locally 

stored monitor policies. If you open a policy, the monitors that are defined for the policy will be 

shown. If you open a monitor you will see the rules defined for the opened monitor. If you open a 

rule you will see the alarm actions defined for the rule. 

36


See also: 

Different types of windows 

Local and central monitor policies 

Creating a new policy 

MonitorMagic ships with a number of predefined policies. These policies can be used and applied 

to computers immediately when MonitorMagic is installed. You can also create your own monitor 

policies or edit existing policies. 

To create a new monitor policy, start the MonitorMagic client and activate the monitor policy 

window. Right click the mouse on one of the two root entries Central monitor policies or Local 

monitor policies and select menu option Create policy. Instead, you can also access this menu 

option from the main popup menu Policy. 

37


The tabbed Setup new monitor policy window appears. This window is used to configure the 

settings of the policy, not the monitors, rules or alarm actions contained in the policy. To continue, 

enter the name of the policy and press the OK button. If you want to change the policy options or 

the service selection defaults, you need to activate those tabs first. 

38


When specifying the name of a policy, use a name that reflects the specifics of the policy or the 

monitors and settings contained in the policy. For instance, if you create a policy that is applicable 

for all normal workstations running Windows 2000 Professional you can use a name like: Normal 

Windows 2000 Professional Computer. 

See also: 


Specifying the policy options 

Specifying the policy service selection 

Applying a policy to a computer 



A policy contains monitors, rules, and alarm actions. When a policy is applied to a computer, the 

monitors are generated and rules and alarm actions become effective. Normally you want to 

create all the monitors and rules and alarm actions as specified in the policy. But sometimes you 

only want to change the rules or alarm actions. These settings are specified by the policy options. 

The policy options define what operations with respect to monitors, rules, and alarm actions are 

executed when a policy is applied to a computer. 

To specify the options of a policy, select the policy in the monitor policy window. Right click the 

mouse and select menu option Properties. 

39


The Manage monitor policy '..." window is shown. The window has various tabs used to 

configure the monitor policy. Select tab Policy options. 

The policy options section is used to configure the actions executed when the policy is applied 

to a computer. 

40


Create monitors, rules and actions according to policy 

This is the default selected option. With this option, the monitors are generated according to the 

policy and all associated rules and alarm actions become effective. 

Remove existing monitors of the same type (disk, service, ...) 

If this option is selected, existing monitors of types that are also contained in the policy are 

removed. E.g., if the policy contains disk monitors, the disk monitors for the computer are 

removed. 

Apply rules and actions to existing monitors, do not create new monitors 

With this option, no new monitors are generated when the policy is applied. Instead, rules and 

alarm actions of existing monitors are updated. Note that the monitor policy still contains monitors. 

But with this option, the monitors are only used as entities that contain rules and alarm actions. 

MonitorMagic will apply the rules and alarm actions of the monitors contained by the policy to 

existing monitors of the same type. Example: Suppose that the policy contains a monitor for disks 

and this disk monitor contains rules and alarm actions. Now if the policy is applied to the 

computer, with this option, existing disk monitors will be updated so that these disk monitors get 

the same rules and alarm actions. 

Remove existing rules from monitors 

With this option, MonitorMagic will remove all rules and alarm actions of monitors of 

corresponding types. 

Apply alarm actions to existing rules, do not create monitors and rules 

With this option, no new monitors or rules are created. Only alarm actions are generated for 

existing rules of corresponding monitors. 

Remove existing actions from rules 

Use this option to delete the existing alarm actions before new alarm actions are created. 

See also: 






monitors are generated and rules and alarm actions become effective. With MonitorMagic you 

can specify the MonitorMagic service that must execute and maintain the monitors generated 

according to the policy. 

Example: Suppose you have installed the MonitorMagic service on computer A. The 

MonitorMagic service on computer A is checking a number of monitors on computer A, for 

instance all the disks, event logs, and some performance counters. Now you also want to monitor 

something of computer B, you now have the following options: 

Install the MonitorMagic service on computer B and let the new service maintain the 

monitors of computer B. 

Do not install the MonitorMagic service on computer B and let the MonitorMagic service 

on computer A monitor the objects of computer B. 

See Single versus multiple MonitorMagic services for more information. 

41


The selection of the MonitorMagic service is specified as part of the policy. So for a policy, two 

computer are involved: 

The target computer. This is the computer that contains the objects that must be 

monitored. 

The MonitorMagic service computer: This is the computer that is running the 

MonitorMagic service that will generate, execute, and maintain the monitors according to 

the policy. It is the computer that processes the policy. 

You have several options for configuring the policy settings related to the specification of the 

service selection. Select the policy in the monitor policy window, right click the mouse and select 

the menu option Properties. 

The Manage monitor policy '..." window is shown. The window has various tabs used to 

configure the monitor policy. Select the tab Service selection. The window shows the different 

options available. 

42


Ask the user 

When a policy is applied to a computer MonitorMagic will ask you which computer running the 

MonitorMagic service computer should process the policy. If you specify a computer where the 

MonitorMagic service is not yet running, MonitorMagic will automatically start the MonitorMagic 

service installation process. This option is selected by default. 

When only one window is open, automatically select the service associated with this 

window 

If you have specified the option Ask the user with this option and in the MonitorMagic client a 

single monitor window is open and connected to a MonitorMagic service, MonitorMagic will 

automatically select the MonitorMagic service of this computer. This is the default option. 

Use the service on the target computer. If the service is not installed on the target 

computer, ask the user 

Use this option if you want the target computer and the MonitorMagic service computer to be 

the same computer. Using this scenario, you will have multiple MonitorMagic services installed. 

Always use the MonitorMagic service running on server: 

Use this option if you want a single MonitorMagic service to manage all monitors for different 

target computers. In this scenario, you only have a single MonitorMagic service. This 

MonitorMagic service both controls local and remote monitors. Enter the name of the computer 

running the MonitorMagic service in the empty field. Use the ...-button to find this computer from a 

network browse window. If the MonitorMagic service is not installed on the specified computer, 

MonitorMagic will start the service installation process when a policy is applied with this option 

specified. 

See also: 


Single versus multiple MonitorMagic services 

Copying a policy 


43


Copying a policy 

Most policies contain similar contents. Instead of creating a new policy from scratch, you might 

want to copy an existing policy to a new policy first and then edit the new policy. With 

MonitorMagic, you can copy a single policy, multiple policies, monitors, rules and alarm actions 

with the cut, copy and paste operations. You can also use these operations to copy a monitor 

policy from a local to a central location. 

To copy a policy, simply select the policy in the monitor policies window, right click the mouse 

and select menu option Copy. 

In an empty area of the monitor policies window, again right click the mouse and select menu 

option Paste. The policy is copied including the full contents (monitors, rules, and alarm actions). 

MonitorMagic will automatically rename the policy to make the name unique. 

44


Similarly, you can copy monitors from policies, rules, and alarm actions using cut, copy and 

paste. 



monitors are generated and rules and alarm actions become effective. You can apply a policy to 

a computer in various manners, by menu selection and by drag-and-drop. You can apply a policy 

to a single computer or to multiple computers. As an example, this section described how to apply 

a policy to multiple (2) computers. 

When you apply a policy you don't need to have a monitor window connecting to the 

MonitorMagic service open. Since the monitor window shows all the monitors maintained by the 

MonitorMagic service, it is easy to see the effect of the apply policy operation. 

First, open a monitor window that connects to the computer that runs the MonitorMagic service. In 

the figure shown, the MonitorMagic service does not maintain any monitors, so the monitor 

window is blank. 

45


Now, open the browse window and select the computer you want to apply the policy to. (Note: in 

this example the policy is configured so that the MonitorMagic service that processes the policy is 

the service running on the computer TULIP. The monitor window for TULIP is shown in the 

diagram above. See Specifying the policy service selection for more information.) When you have 

selected the computer(s), right click the mouse and select the menu option Apply policy, [name 

of policy]. You can also select this menu option from the main menu: Computer, Apply policy, 

[name of policy]. 

In this example, the MonitorMagic service running on computer Tulip will process the policy and 

generate monitors accordingly. The MonitorMagic client will update automatically and show the 

generated monitors after some time. 

46


See also: 


Applying a policy with drag and drop 


Applying a policy with drag and drop 

A policy contains monitors, rules and alarm actions. When a policy is applied to a computer, the 

monitors are generated and rules and alarm actions become effective. You can apply a policy to 

a computer by a simple drag and drop operation or by menu selections. 

To apply a policy with drag and drop, you need to have the monitor policies window and a 

network browse window open. In network browse window, open the network tree so that the 

computer to which the policy should be applied is visible. In the monitor policies window, select 

the policy with a left mouse click and keep the mouse button down. 

47


Move the mouse with the left mouse button down to the computer that should be monitored. 

While doing so, the image of the mouse cursor changes to show that a drag and drop operation is 

taking place. On the target computer, release the mouse button. The policy is now applied to the 

computer. 

48


Once the policy is processed, by the MonitorMagic service, the MonitorMagic client is updated 

soon after. 

See also: 





Monitor policies can be stored on a local or central location. Central monitor policies can be 

shared by multiple MonitorMagic applications installed on different computer. Local 

monitor policies cannot be shared. Note that both central and local monitor policies can be 

You should use central monitor policies if: 

The monitor policy must be available for other computers running the MonitorMagic client. 

This is the case if you want to run the MonitorMagic client on different computers and 

always want to have the same monitor policies available. 

Use local monitor policies if: 

You want to create a monitor policy that is available only on the local computer running 

the MonitorMagic client. 

You do not have sufficient access rights to create central monitor policies. 

49


Typically, you will use central monitor policies for most circumstances and use local monitor 

policies for testing purposes only. Note that you can copy monitor policies from local to central 

and vice-versa. 

To configure local and central monitor policy settings, select the main menu option Policy, 

Storage options. You will be presented the following window: 

The window contain the following fields: 

Allow monitor policies to be stored in a local file 

Select this option if you want to use local monitor policies. In this case, you also need to specify 

the file that stores the monitor policies. This option is enabled by default and the file is 

NmMonPol.cfg, stored in the local MonitorMagic client program directory. 

Allow monitor policies to be stored on the following central location... 

Select this option if you want to be able to store monitor policies on a central location. The 

location is a computer running the MonitorMagic service. It is recommened to use a single 

computer running the MonitorMagic service for the central monitor policy database. 

See also: 


Monitors 

Introduction 

Monitors are the objects monitored by MonitorMagic. To get a basic understanding of 

MonitorMagic monitors, policies, rules and alarm actions, read the section Policies, Monitors, 

Rules and Alarm actions. Monitors are the essential components of MonitorMagic. Monitors are 

monitored by the MonitorMagic service. In most situations, the MonitorMagic service will process 

all the monitors it maintains on a regular basis. When a monitor is processed, the MonitorMagic 

service gets the latest information related to the monitor. As an example, suppose the 

MonitorMagic service has a disk monitor configured. On an interval basis, the MonitorMagic 

service retrieves, for instance, the available diskspace. Next, the MonitorMagic service evaluates 

50


all the rules of the monitor and checks if the rules are triggered or no longer triggered. According 

to these results, alarm actions, associated with each rules can be executed. 

MonitorMagic supports different types of monitors: ping, disk, service, events etc. A monitor can 

be created in two ways: directly, by the user creating a single monitor or when a policy is applied 

to the computer. 

See also: 


Real monitors and policy monitors 


This topic requires a little background knowledge of the concepts used by MonitorMagic. To get a 

basic understanding of monitors, policies, rules, and alarm actions you are advised to read the 

section Policies, Monitors, Rules, and Alarm actions first. 

With MonitorMagic you can monitor various objects like disks, services, performance counters, 

and so forth. MonitorMagic uses monitors that correspond with these "network devices". The 

monitors are maintained by the MonitorMagic service(s). For each monitor, a corresponding 

network device or software process exists. These monitors are referred to as real monitors. 

Monitor policies contain definitions of monitors, rules, and alarm actions. The monitors consist of 

the complete specification of real monitors except for the name of the computer. These monitors 

are referred to as policy monitors. This type of monitor does not correspond with an existing 

network device or software process. When a policy is applied to a computer the MonitorMagic 

service processes all the policy monitors. Each policy monitor defines how the MonitorMagic 

service must generate real monitors. The generated real monitors correspond with the physical 

or software objects of the computer to which the policy is applied. 

With the exception of the name of the computer, the policy monitors contain the complete 

specification of the rules and alarm actions. When the policy is applied to a computer, 

MonitorMagic will automatically generate the rules and alarm actions for each generated monitor. 

See also: 


Creating a (real) monitor 

Creating a monitor in a policy 



You can create a monitor in two ways: directly, by the user creating a single real monitor or when 

a policy containing policy monitors is applied to the computer. There are various ways to create a 

monitor directly: 

 

Open the monitor window, right click the mouse and select menu option Add monitor, 

[monitor type] 

51


 

From a network browse window. Browse to find the name of the computer. Right click the 

mouse and select menu option Add monitor (advanced), [monitor type]. 

In both cases, a tabbed window appears. In this window, you can specify the monitor, rules, 

alarm actions, scheduling parameters and MonitorMagic service. The target computer which will 

contain the monitored objects is the selected computer and cannot be changed. 

52


See also: 





You can create a monitor in two ways: directly, by creating a single real monitor or when a policy 

containing policy monitors is applied to the computer. When you apply a policy to a computer, the 

policy needs to contain policy monitors in order to create real monitors. For more information, 

see Real monitors and policy monitors. 

To create a monitor in a policy, activate the monitor policies window. Select the policy you want 

to create a monitor in, right click the mouse and select menu option Add monitor, [type of 

monitor]. 

53


A tabbed window shows up. In this window, you can specify the monitor, rules, alarm actions, and 

scheduling parameters. The target computer is not specified since a policy monitor is not related 

to a target computer. 

See also: 




Database - Monitor data 

For various monitor types, you can configure if MonitorMagic must store the monitor data in a 

database. To enable this feature, the MonitorMagic database must be configured to use a 

database. See Database - Introduction for more information. 

For the following monitor types you can store the monitor data in a database: 

Ping monitor 

Disk monitor 

Performance counter monitor 

Snmp get monitor 

You can specify the database storage parameter in both a policy and individual monitor. The 

following window is used to specify the database storage specification: 

54


Note: If the MonitorMagic service is configured not to use a database, you can still specify 

this option. In this case, no data will be stored in the database. Once a database is 

configured for the MonitorMagic service, data will be stored automatically. 

See also: 

Database - Introduction 

Database - Changing database storage for multiple items 

Database - Supported databases 

Database - MS Access 

Database - SQL Server 

Database - Viewing the database status 

Database - Create a new database 

Database - Use an existing database 

Database - Stop using a database 

Database - system data sources 

Database - Troubleshooting 


You can change the database storage specification for multiple items with a single operation. To 

start, select multiple monitors in a monitor window. Next, active the context sensitive menu by 

right clicking the selected monitors. Select menu option Properties, Database... You will be 

presented the following window: 

55


The window describes the current database storage specification for the selected monitors. You 

can either enable or disable database storage for all selected items. Select the option of your 

chioce and press OK. If you do not wish to change the database storaget settings, press Cancel. 

Note: If the MonitorMagic service is configured not to use a database, you can still use this 

function. In this case, no data will be stored in the database. Once a database is 

configured for the MonitorMagic service, data will be stored according to the specification. 

See also: 













Ping 

Ping monitor 

The ping monitor is used to check if a TCP/IP host is reachable and measures the response time 

of a host. The TCP/IP host can be any system or device as long as it supports TCP/IP: Windows 

NT/2000 servers, printers, routers, hubs, web-sites and so on. 

You can create ping monitors using two different methods: directly, by creating a ping monitor or 

by applying a policy containing TCP/IP host definitions. See Real monitors and policy monitors for 

more information. If you create a ping monitor in a policy, you can apply the policy to multiple 

MonitorMagic services. This allows you to find the difference in response times with respect to 

each computer running the MonitorMagic service. 

56


See also: 

Specify ping devices 



Ping monitor values 

Creating a ping monitor 

This section describes how you specify ping monitors for a monitor policy. The procedure to 

create a ping monitor directly is very similar. To start, activate the monitor policies window, 

select the policy, right click the mouse and select menu option Add monitor, Ping. The specify 

ping monitor window is shown. 

The section Specify ping devices to monitor contains the specification of all ping devices you 

want to monitor. 

Add 

Press this button to add a new TCP/IP host or range of hosts. 

Edit 

When an entry is selected, use this button to modify the entry. 

Delete 

Select an entry and press this button to delete the entry from the list. 

57


See also: 

Ping monitor 



Rules overview 


A ping monitor is specified by a single TCP/IP host address or a range of addresses. Use the 

Specify ping device(s) to add and edit ping monitors. To activate the window, see Creating a 

ping monitor. 

DNS name or TCP/IP address (xxx.xxx.xxx.xxx) 

Select this option if you want to add a single TCP/IP host instead of a range of addresses. 

Name or address 

Enter the address of the TCP/IP host in this field. You can specify a DNS name (for instance 

www.tools4ever.com) or the address in dot notation, for instance 192.168.195.201. 

TCP/IP address range 

Select this option if you want to select a range of TCP/IP addresses. MonitorMagic will create 

ping monitors for each address in the range. 

Start address (xxx.xxx.xxx.xxx) 

Enter the start address of the range in this field. The start address is included in the range of 

addresses. Example: 192.168.195.12 

End address (xxx.xxx.xxx.xxx) 

Enter the end address of the range in this field. The end address is included in the range of 

addresses. Example: 192.168.195.37 

58


Ping time-out value 

The time specified in milliseconds that the MonitorMagic service will wait for the TCP/IP host to 

respond to the ICMP echo request (ping). If no response is received, a time-out occurs. 

Ping packet size 

The size of the packet sent in the ICMP echo request (ping). Normally, you should use the default 

of 32 bytes. 

See also: 

Ping monitor 




The following ping monitor values exist: 

Monitor 

value 

Host 

Example(s) 

www.tools4ever.com 

192.168.195.201 

Description 

The specification of the TCP/IP host, either in DNS format, 

dotted address notation or as a NETBIOS name. 

Pings sent 16 The number of ICMP Echo Requests (pings) sent to the 

host by the MonitorMagic service. 

Response 

time 

65 The last response time of the host, specified in milli 

seconds. 

Pings failed 12 The number of pings sent for which no response was 

received by the MonitorMagic service. 

Evaluation 

time 

09:07:00 08-16- 

2001 

The time and date of the last ping sent to the host 

Status OK, Warning, Error The general status of the monitor. If not OK, there was no 

response from the remote host. 

DNS-name 

www.tools4ever.com The name of the TCP/IP host, specified in DNS format 

when the monitor was setup. 

IP address 192.168.195.201 The address of the TCP/IP host, specified in dotted notation 

when the monitor was setup. 

NETBIOS 

name 

TULIP 

The address of the TCP/IP host, specified as a NETBIOS 

name when the monitor was setup. 

Packet size 32 The size of the ICMP echo request (ping) in bytes. 

Ping time-out 10000 

Pings 

received 


service 

The ping time out value, specified in milli seconds. This is 

the time the MonitorMagic service will wait for a response 

from the TCP/IP host. 

4 The number of pings sent for which a response was 

received. 

Tulip 

The name of the computer that runs the MonitorMagic 

service that processes this monitor. 

Error code 70200 A ICMP specific error code. If this value is not equal to zero 

(0), something went wrong during sending or receiving the 

ICMP echo request. 

59


Ping monitor 



Disk 

Disk monitor 

The disk monitor is used to check the disk space on logical disk drives of computers. In a network 

environment, it is extremely important to have a good overview of total disk capacity and available 

disk space. If a computer running Windows 2000 or Windows NT 4.0 software runs out of disk 

space, serious (performance) problems may occur. 

You can create disk monitors directly or by using a monitor policy. It is recommended to create 

disk monitors by using monitor policies. For each logical disk drive, a disk monitor is used. 

See also: 


Creating a disk monitor 

Disk monitor values 


This section describes how you can specify disk monitors for a monitor policy. The procedure to 

create a disk monitor directly is very similar. To start, activate the monitor policies window, 

select the policy, right click the mouse and select menu option Add monitor, Disk. The specify 

disk monitor window is shown. 

60


Monitor 

For a monitor policy, you need to specify the name of the monitor. This name is used only to refer 

to the monitor in the policy. 

All disks 

Select this option if you want MonitorMagic to create monitors for each logical disk of the 

computer. When the policy is applied to a computer, MonitorMagic will find all the logical disks of 

the computer and create disk monitors for each of them. 

Specific disks of computer 

Select this option if you want to create disk monitors only for specific disks. In the field, specify 

the disk(s). Example: C:,D. 

See also: 

Disk monitor 



Each disk monitor has the following values: 

Monitor 

value 

Example(s) 

Description 

Computer Tulip The name of the computer on which the logical disk resides. 

Disk name C:\ The name of the logical disk 

Capacity 40000 The total capacity of the logical disk specified in megabytes (1 

61


(MB) 

Free space 

(MB) 

Used space 

(MB) 

Free space 

(%) 

Used space 

(%) 

Evaluation 

time 

Status 


service 

megabyte=1024 kilo bytes = 1048576 bytes) 

28000 The total available disk space of the logical disk specified in mega 

bytes (MB). 

12000 The total used disk space of the logical disk specified in mega 

bytes (MB). 

70 The total available disk space of the logical disk specified as a 

percentage of the total disk space. 

30 The total used disk space of the logical disk specified as a 

percentage of the total disk space. 

09:07:00 08- 

16-2001 

OK, Warning, 

Error 

Mars 

See also: 

Disk monitor 


The time and date when the disk values were last updated. 

The general status of the monitor. If the status is not OK, the 

MonitorMagic service was not able to collect the disk information. 

The name of the computer that runs the MonitorMagic service that 

processes this monitor. 

Service 

Service monitor 

The service monitor is used to check the status and other characteristics of a service. 

MonitorMagic uses a service monitor for each service. You can monitor all services of a 

computer, a selection of services, or a single service. 

You can create service monitors directly or by using a monitor policy. It is recommended to create 

service monitors by using monitor policies. 

See also: 

Specify service monitors 

Select services 

Service monitor values 


This section describes how you can specify service monitors for a monitor policy. The procedure 

to create a service monitor directly is very similar. To start, activate the monitor policies window, 

select the policy, right click the mouse and select menu option Add monitor, Service. The 

Specify service monitor is shown. 

62


Use the Specify service monitor to define the service monitors that must be generated when 

the policy is applied. 

Monitor, Name 



All services 

Select this option if you want MonitorMagic to create monitors for each service on the computer. 

When the policy is applied to a computer, MonitorMagic will find all the services of the computer 

and create service monitors for each of them. 

Specific services of computer 

Select this option if you want to generate service monitors for specific services only. You can add 

and delete services by using the corresponding buttons. Note that only the services are specified 

in this section, not the computer name. If the policy is applied to a computer that has the same 

service, a service monitor is generated. If the computer does not have the service installed, no 

service monitor is generated. 

See also: 




63



The Select services window is used to select one or more services. You can select the services 

from one or more computers. 

Server 

The name of the computer currently used to find the services shown in the Available services 

list. 

... 

Select this button to browse the network to find another server or workstation. 

Refresh 

Press to update the Available services list with the services found on the computer specified in 

the field Server. 

Available services 

The list of services from which you can select services. 

Add -> 

Press to add the selected services in the list with Available services to the list containing the 

Selected services. 


Cancel 

Press to ignore any changes made to the list containing the Selected services. 





Each service monitor has the following values: 

Monitor 

value 

Example(s) 

Description 

Computer Tulip The name of the computer on which the 

service resides. 

Service 

name 


Service state Stopped 

Start pending 

Stop pending 

Running 

Continue pending 

Pause pending 

Paused 

Startup type 

Automatic 

Manual 

Disabled 

Loader 

I/O system 

State change Not changed 

Evaluation 

time 

The name of the service. 

The current state of the service. 

The way the service is configured to start on 

the computer. 

The change of the service state since the last 

evaluation 

Not changed 

Changed to running 

Changed to not running 

09:07:00 08-16-2001 The time and date when the service values 

were last updated. 

Status OK, Warning, Error The general status of the monitor. If not OK, 

the MonitorMagic service was not able to 

collect the service information (completely). 


service 

Internal 

name 

Mars 


The name of the computer that runs the 

MonitorMagic service that processes this 

monitor. 

The name of the service used internally on 

the computer. 

Type 16 A parameter specifying several characteristics 

of the service: desktop interaction, shared 

process service, device driver service, runs in 

own process, file system driver. 

Executable C:\MmSvcDir\NM.EXE The full path of the executable (.EXE) that 

runs when the service is started. 

65


Startup 

account 

FLOWERS\MonitorMagicSvcAccnt 

LocalSystem 

The account used by the service. 

See also: 




Events 

Events monitor 

The event log monitor is used to check the occurrence of certain events generated on a computer. 

MonitorMagic uses an event log monitor for each event log you want to evaluate the events 

from. You can monitor all event logs of a computer, a selection of event logs, or a single event log. 

See also: 

Specify event log monitors 

Event log specification 

Event log advanced settings 

Event log monitor values 


This section describes how you can specify event log monitors for a monitor policy. The 

procedure to create a event log monitor directly is very similar to creating other monitors. To start, 

activate the monitor policies window, select the policy, right click the mouse and select menu 

option Add monitor, Events. The Specify event log monitor window is shown. 

66


Use the Specify event log monitor window to define the event log monitors that must be 

generated when the policy is applied. 

Monitor, Name 



All event logs 

Select this option if you want MonitorMagic to create monitors for each event log of the computer. 

When the policy is applied to a computer, MonitorMagic will find all the event logs of the computer 

and create event log monitors for each of them. 

Specific logs of computer 

Select this option if you want to generate event log monitors for specific event logs only. You can 

add and delete event logs by using the corresponding buttons. Note that only the event logs are 

specified in this section, not the computer name. If the policy is applied to a computer that has the 

same event log, an event log monitor is generated. If the computer does not have the event log 

available, no event log monitor is generated. 

Advanced 

Press this button to specify some additional settings. 

See also: 




67




Use the Event log specification window to select specific event logs. 

Select event log(s) from computer 

Enter the name of the computer from which you want to list the available event logs in this field. 

Press the ...-browse button to find other computers in the network. 

Refresh 

Press to update the event logs found on the computer specified. 

Log to add 

When you select a log from the list Available event logs, the name of the log will be copied into 

this field. You can also enter the name of the log by using the keyboard. 

Add -> 

Press to add the log specified in the field Log to add to the list of Selected event logs 





Use the Event log advanced settings window to specify additional settings that apply to events 

generated in the past and the way MonitorMagic processes the rules for event log monitors. To 

access this window, press the Advanced button in the Specify event log monitors window. 

When processing an event log monitor, the MonitorMagic service will process all the events that 

occurred since the last time the service processed the event log. If the event log monitor is 

processed for the first time, you need to specify how the MonitorMagic service must deal with old 

events. 

Processing of events from the past 

Include all events found in the log 

Select this option if you want to evaluate the rules for all events available from the log. 

Ignore all events from the past 

Select this option if all events from the past should be ignored. 

Include events from the past that are not older then ... minutes 

With this option, you also need to specify the period in minutes. 

Rule reset specification 

Reset rule when event did not re-occur 

If you want to reset a rule of an event log monitor, that is triggered, select this option if the event 

did not re-occur since the last evaluation of the event log. This selection implies that the rule is 

reset when the event log is evaluated and only other events occurred. 

Reset rule not until acknowledged 

Select this option if you don't want the rule to be reset unless the rule is acknowledged. 

69


Reset rule after a fixed period of ... minutes 

With this option, the rule is automatically reset after the specified some period. 

See also: 






The event log monitor has values associated with the event log itself and monitor values of the 

event log records (the events that occur). The event log monitor values can be shown in the 

columns of the monitor window. The values of the event log records can be used in rule criteria 

specifications and alarm actions. 

Event log monitor values: 

Monitor 

value 

Example(s) 

Description 

Computer Tulip The name of the computer on which the event log resides. 

Log Application The name of the event log. 

Number of 

events 


service 

Evaluation 

time 

Status 

546 The number of event records in the log 

Mars 

09:07:00 08- 

16-2001 

OK, Warning, 

Error 

Event log record monitor values: 

Monitor 

value 

Example(s) 

The name of the computer that runs the MonitorMagic service that 

processes this monitor. 

The time and date when the service values were last updated. 

The general status of the monitor. If not OK, the MonitorMagic 

service was not able to collect the event log information 

(completely). 

Description 

Computer Tulip The name of the computer on which the event log resides. 

Severity 

Error event 

Warning event 

Information 

event 

Success audit 

event 

Failure audit 

event 

Time 09:07:00 08- 

16-2001 

The type of the event record. 

The time and date when the event record was generated. 

Description [text] The description of the event record. 

Source 

MonitorMagic The name of the source of the event record. This name refers to 

the application or service generating the event log record. 

70


Category 2 The category of the event. This value is dependant on and 

determined by the source. In a lot of records, this value is not used. 

Event 34 The identification of the type of record as determined by the 

source. Different numbers correspond with different event log 

record messages. 

See also: 





Performance counter 


The performance counter monitor is used to check the value and contents of performance 

counters. MonitorMagic uses a performance counter monitor for each performance counter. 

MonitorMagic supports all performance counters, including the counters that are part of the 

operating system, but also the counters that are installed by other applications. 

You can create performance counter monitors directly or by using a monitor policy. It is 

recommended to create performance counter monitors by using monitor policies. 

See also: 

Specify performance counter monitor 

Performance counter specification 

Performance counter values 


This section describes how you can specify performance counter monitors for a monitor policy. 

The procedure to create a performance counter monitor directly is very similar. To start, activate 

the monitor policies window, select the policy, right click the mouse, and select the menu option 

Add monitor, Performance counter. The Specify performance counter monitor window is 

shown. 

71


Monitor Name 



Specify counters to monitor 

The list shows all performance counters specified so far. Use the Add or Delete buttons to add 

new entries or delete selected entries. 

See also: 





Use the Performance counter specification window to add performance counters. To activate 

this window, activate the Specify performance counter monitor window and press the Add 

button. 

72


From the window you can find all performance counters that exist on a computer in the network. 

Select counter from computer 

Enter the name of the computer from which you want to find the available performance counters. 

Press the ...-button to find the computer from a network browse window. Press the Refresh 

button to refresh the performance counter information of the specified computer. 

Performance object 

The list contains the different performance objects. Each performance object contains one or 

more performance counters associated with the performance object. When you change the 

selection in the Performance object list the list of Available counters will be updated. If you 

select a performance counter from the list, the available performance counter instances will be 

updated. 

All instances 

Select this option if you want to generate monitors for all performance counter instances. The 

available instances depend on the target computer of the performance counter monitor. E.g., for 

. 

73


the performance object Processor you will have instances and a corresponding counter for each 

CPU of the computer. Some performance objects have no direct instances, for example Memory. 

For these performance objects the instance options are not applicable. 

Selected instances 

Select this option and the instances from the list if you do not want to create performance counter 

monitors for all instances. See the remarks in the section All instances. 

Explain 

Press this button to see an explanation of the performance counter selected in the Available 

counters list. 

See also: 





Each performance counter monitor has the following values: 

Monitor 

value 

Example(s) 

Description 

Computer Tulip The name of the computer that maintains the performance 

counter. 

Objectcounterinstance 

specification 

Memory, 

Available 

bytes 

Value(text) 79785984 

56% 

Value 79785984 

56 


service 

Evaluation 

time 

Status 

Mars 

09:07:00 08- 

16-2001 

OK, Warning, 

Error 

A textual description of the performance counter 

The value of the performance counter. If the value is denoted with 

a suffix, the suffix is part of the displayed text. 

The "raw" value of the performance counter. This value should be 

used in comparisons to evaluate the criteria of a rule. 

The name of the computer that runs the MonitorMagic service 

which processes this monitor. 

The time and date when the value of the performance counter 

monitor was collected. 

The general status of the monitor. If not OK, the MonitorMagic 

service was not able to collect the performance counter value 

information. 

Object Memory The performance object of the performance counter. 

Counter 

Available 

bytes 

The name of the performance counter. 

Instance 0 The name of the performance counter instance if applicable. 

Value 79785984 The raw value of the performance counter. 

Suffix % The suffix used to represent the value of the performance counter. 

See also: 

74





Processes 

Process monitor 

The process monitor is used to check specific characteristics of a process. MonitorMagic will 

create a single process monitor for every process you choose to monitor. Creating multiple 

process monitors generates multiple monitored objects. They can be managed together or on an 

individual basis. 

When multiple instances are running of the same process, MonitorMagic will automatically create 

new monitors for each process instance. Example: Suppose you have a process monitor 

checking if process notepad is running. At a certain moment, the notepad process is not running. 

In this case, you have a single monitor and the monitor window looks like this: 

No suppose, that the notepad application is started for four times, e.g. four instances of the 

notepad process are running. When MonitorMagic updates the single process monitor, it will find 

all the instances and dynamically create new process monitors for all four instances as shown in 

the picture below. 

You can create process monitors directly or by using a monitor policy. It is recommended to 

create process monitors by using monitor policies. 

See also: 

Specify processes 

Select processes 

Process values 


This section describes how you specify process monitors for a monitor policy. The procedure to 

create a process monitor directly is very similar. To start, activate the monitor policies window, 

75


select the policy, right click the mouse and select the menu options Add monitor/Process. The 

Specify process monitor window is then shown. 

Use the Specify process monitor dialog box to define the process monitors that must be 

generated when the policy is applied. 

Monitor, Name 

For a monitor policy you need to specify the name of the monitor. This name is used only to refer 

to the monitor in the policy. A name is generated for you by default. You may change it to suit 

your needs. 

Add 

Use this button to bring up a dialog box which you can use to select what process(es) you would 

like to monitor. Processes can be added and deleted by using the corresponding buttons. Note, 

once a process has been added to a monitor the computer you selected the process from is not 

associated with it. When the policy is applied to a computer that isn't currently running the 

process the monitor will be generated anyway. The important thing to remember here is that 

certain rules, which relate to processes, will trigger if the process is not running on the machine 

that the monitor policy is applied to. Rules that will trigger when a process is not running, on a 

monitored machine, are rules which utilize the following values: Memory Usage, Process ID, 

Thread Count, and Time Running [sec]. 

Delete 

Use this button to delete the selected monitored process(es). Only processes listed in the 

monitored process(es) dialog box will be monitored. 

76


See also: 





The Select process(es) window is used to select one or more processes. You can select the 

processes from one or more computers. 

Computer 

The name of the computer currently used to find the processes shown in the Available 

process(es) list. 


Refresh 

Press to update the Available processes list with the processes found on the computer specified 

in the field Computer. 

Available processes 

The list of processes from which you can select processes to monitor. 

Add -> 

Press this button to add the selected processes from the list containing Available processes to 

the list containing the Selected processes. 

77



warning 

MonitorMagic service was not 

able to collect the process 

information (completely). 

Thread count 14 The total number of threads in 

use by the process (only 

available when the process is 

running). 

Time running (sec) 10335 The total time the process is 

running in seconds (only 

available when the process is 

running). 

See also: 




File 

File monitor - Overview 

You can use a file monitor to do the following: 

Check the content of a (log) file for certain words and phrases; 

Define any alarm action executed when the content of a file meets certain criteria; 

Check the existence of file; 

Check the total size of a group of files; 

View a log file in the MonitorMagic client window; 

View the content of any text file in a Internet browser, even on remote locations, 

secure and not secure. 

The file monitor is used to check specific characteristics or the contents of a specific file or group 

of files. The file monitor can very well be used to analyze log files. A file monitor can contain 

wildcard specifications to specify a group of files. Further you can use a file monitor to actually 

see the content of a (remote) log file. 

You can create file monitors directly or by using a monitor policy. It is recommended to create file 

monitors by using monitor policies. 

A file monitor can represent a single or multiple files. In the last case, the file path is specified 

using wildcards. If you want to monitor multiple files in different directories or with totally different 

names, you will need to create multiple file monitors. 

See also: 


File monitor - Specify file monitors 

File monitor - Path specification 

File monitor - File analysis 

File monitor - Existing content 

File monitor - View monitor 

File monitor - View file content 

File monitor - Show a file in an Internet browser window 

File monitor - File monitor values 

79



This section describes how you specify file monitors for a monitor policy. The procedure to create 

a file monitor directly is very similar. To start, activate the monitor policies window, select the 

policy, right click the mouse and select the menu options Add monitor, File. The Specify file 

monitor window is then shown. 

The window show the specified file monitors. Use the Add, Edit and Delete button to create new 

and manage existing file monitors. 

See also: 











80


To add a new file monitor, open the Specify file monitor window and press the Add button. 

In the window shown, you can specify the path specification of the file monitor. The window 

contains the following fields: 

File path 

The full path to the files you want to monitor. The file path can contain wildcards (* and ?). The file 

path can start with a logical drive or share specification: 

Logical drive path: Example: D:\Logs\SqlServer\*.*. In this case, the computer on 

which the files reside must run the MonitorMagic service. Thus file monitors 

specified using logical drives can only be local to the MonitorMagic service. 

Share path: Example: \\SERVER_A\Logs\SqlServer\*.*. In this case the specification 

start with a computer name (\\SERVER_A), followed by a share (Logs) and additional 

directory and file specification. In this case, the share must exist and you can monitor 

remote files. 

Keywords, Insert 

Use the list with keywords to ease the specification of the file path. The supported keywords are: 

 

 

 

 

%SystemRoot%: The Windows 2000/XP/NT operating system root directory of the target 


%SystemRoot%\System: The Windows 2000/XP/NT system directory of the target 


%SystemRoot%\System32: The Windows 2000/XP/NT system32 directory of the target 


\\TARGET_COMPUTER\: The computer name of the target computer. 

When a keyword is selected, press the Insert button to insert the selected keyword at the current 

File path specification position. 

Monitor all matching files 

81


If the file path contains wildcards, you can select this option to monitor all files that match the file 

path specification. 

Monitor most recent file only 

If the file path contains wildcards, you can select this option to monitor the most recent file only. 

In this case, MonitorMagic will find all matching files according to the file path specification and 

then select the file with the most recent modification date. 

See also: 











When monitoring files, MonitorMagic can either include monitoring the content of the monitored 

files or not. The option to monitor the content of a file is most often used to check if the file 

contains certain words or phrases. To specify this option, open the Specify file monitor window 

and press the Add button. Press button Analysis. You will be presented the following window: 

The window contains the following fields: 

Analyze file content 

82


Select this option if you want MonitorMagic to analyze the file content. If you do not select this 

option, you cannot use the file content data value as a criteria to specify rules. 

File position 

To keep track of the file content analyzed so far, and not include the same content on subsequent 

processing updates, select this option. 

Analyze complete file when modified 

Select this option if you want MonitorMagic to analyze the whole file content when the file is 

modified since the last update. 

Analyze complete file always 

Select this option if you want MonitorMagic to analyze the whole file on every update, regardless 

if the file has been changed or not. 

See also: 











When monitoring files for the first time, MonitorMagic can either include or discard the current file 

content. This option is only applicable if you have selected the option to analyze the file content. 

To specify this option, open the Specify file monitor window and press the Add button. Press 

button Existing content. You will be presented the following window: 

83


Select the desired option to include or discard the existing file content. 

See also: 











For a file monitor, you can see the names and characteristics of the files according to the file path 

specification of the monitor and the content of each file. To start, right click the file monitor and 

select the Properties menu option 

84


The window shows the Computer and File path specification of the selected file monitor. To see 

the details of the file monitor, press the Details button. To see what files are actually monitored, 

press the View button 

See also: 











For a file monitor, you can see the names and characteristics of the files according to the file path 

specification of the monitor and the content of each file. To start, right click the file monitor and 

select the Properties menu option. Press the View button. 

85


The window shows the names of the files found for the file monitor. To see the actual content of 

one of the files, select the file and press the Show button. This function will start the notepad 

application and load the selected file. Note that the file is copied from the Monitor service to the 

Monitor client application first. 

The window also shows if certain text searched for is found in a file. The window shows these text 

in the column Text found for a certain file if the text has been found in the file. The rules of the 

file monitor determine what text MonitorMagic is searching for. Once a searched text is found, 

MonitorMagic will not search the same text in subsequent files. 

See also: 











With the MonitorMagic Web Interface you can see the content of a text file. To use this function, 

perform the following steps: 

Define a file monitor in MonitorMagic that monitors the file(s) you want to see. You do not 

need to define any rules for the monitored files. 

Configure the MonitorMagic Web Interface, either secure or not secure. 

Start an Internet browser an connect to the computer running the MonitorMagic Web Service. In 

the tree on the left side, select the option MonitorMagic, [Computer name]. The browser will 

show all the monitors maintained by the MonitorMagic service. For the file monitors, a number of 

columns are shown. 

86


To see the rules and alarm actions, press the first column (Computer) of the monitor. In the 

example shown you would need to press on Autumn. To see the files of each monitor, press the 

column File(s) path. In the example shown, you would need to press on the text: 

\\Autumn\Logs\SqlServer7\*.*. The browser will show the actual monitored files, matching the 

file path of the monitor. 

87


Finally, to see the content of a particular file, click on the file name in the left column. This will 

load the complete content of the file into the browser window. 

See also: 

See also: 











Each file monitor has the following values: 

Monitor Value Example(s) Description 

Computer SUMMER The name computer on which 

the file(s) reside. 

Evaluation time 09:07:00 09-16-2001 The time and date when the 

file monitor was last updated. 

File(s) path \\AUTUMN\Logs\SqlServer\*.* The path specification of the 

file(s) to monitor. To specify 

multiple files, the path can 

contain wildcards. 

Content 

The content of the monitored 

file(s). The content field cannot 

be shown as a column, but you 

can search the file content for 

88


any search string an show the 

whole file with a separate 

function. 

File name(s) Log1.txt, Log2.txt, .Log3.txt The name(s) of all monitored 

files according to the file(s) 

path specification. 

File size (bytes) 53678762 The total size of the file 

monitor file(s). If the file path 

specification contains 

wildcards and multiple files are 

monitored, the value is the 

sum of all individual file sizes. 

File creation time 16:03:38 04/23/2002 The time specifies when the 

file was created. If the file path 

specification contains 


monitored, the time shown is 

the creation time of the oldest 

file. 

File access time 16:03:38 04/23/2002 The time specifies when the 

file was last accessed. If the 

file path specification contains 



the access time of the file with 

the most recent access time. 

File write time 16:03:38 04/23/2002 The time specifies when the 

file was last written to. If the 

file path specification contains 



the file write time of the file 

with the most recent file write 

time. 

File count 4 The number of monitored files 

according to the file path 

specification. If not file is 

found, the value is zero (0). If 

the file path specification does 

not contain wildcards, the 

value is either 1 (file found) or 

0 (file not found). 

File accessed 

File changed 

Yes 

No 

Yes 

No 

A flag indicating if the file has 

been accessed since the time 

the file monitor was processed. 

A flag indicating if the file has 

bee changed since the time 

the file monitor was processed. 

File attributes 53787 Additional file specification 

information (internal use only) 

Age most recent file (sec) 5 The age in seconds of the 

89


most recent file found. (Only 

files that matches the file 

monitor specification criteria 

are taken into account) 

Age oldest file (sec) 60968 The age in seconds of the 

oldest file found. (Only files 

that matches the file monitor 

specification criteria are taken 

into account) 

Modification elapsed time 

(sec) - minimum 

Modification elapsed time 

(sec) - maximum 

78 The elapsed time in seconds 

since the file was last modified 

for the most recently modified 

file. (Only files that matches 

the file monitor specification 

criteria are taken into account) 

9068 The elapsed time in seconds 

since the file was last modified 

for the file with the oldest 

modification time. (Only files 

that matches the file monitor 

specification criteria are taken 

into account) 

Matching text ERROR: Backup failed The line or paragraph 

containing the text searched 

for. 

Matching file BackupLog.txt The file containing the text 

searched for. 

Monitor flags 536 An internal value used to 

specify the method used by 

the MonitorMagic service to 

update file information (internal 

use only). 

MonitorMagic Service KRAKEN The name of the computer that 

runs the MonitorMagic service 


Status 

error 

OK 

warning 

See also: 









The general status of the 

monitor. If not OK, the 


able to collect the file monitor 

information (completely). 

90


Clusters 

Cluster resource monitor 

When using Microsoft clustering services you might want to monitor cluster specific object like 

cluster resources, groups and nodes. MonitorMagic supports Microsoft Clustering service for 

Windows NT 4.0 and Windows 2000. If you want to use this functionality, you must have at least 

one computer that runs Microsoft Clustering service. 

The cluster resource monitor is used to check specific characteristics of a cluster resource. 

MonitorMagic uses a monitor for each cluster resource you choose to monitor. They can be 

managed together or on an individual basis. 

You can create cluster resource monitors directly or by using a monitor policy. It is recommended 

to create cluster resource monitors by using monitor policies. 

See also: 

Specify cluster resources 

Add and select cluster resources 

Cluster resource values 


This section describes how you specify cluster resource monitors for a monitor policy. The 

procedure to create a cluster resource monitor directly is very similar. To start, activate the 

monitor policies window, select the policy, right click the mouse and select the menu options 

Add monitor, Cluster. You will be presented the Specify cluster monitor window: 

91



Name 

The name of the cluster resource monitor. 

Specified cluster resources, groups and nodes to monitor 

A specification of cluster resources, groups and nodes to be monitored by MonitorMagic. Note 

that each entry in this list corresponds with one or more cluster objects, generated from the listed 

object specification. 

Add, Edit, Delete 

Use the buttons to manage the list. 

See also: 





This section describes how you can add and change configured cluster objects to be monitored 

by MonitorMagic. To start, activate the monitor policies window, select the policy, right click the 

mouse and select the menu options Add monitor, Cluster. Press the Add button or select an 

entry from the list and prsss the Edit button. You will be presented the Cluster object 

specification window: 

92


You can use this window to specify cluster resources. Currently, monitoring individual cluster 

groups and cluster nodes is not supported. To make it easy to find the cluster object you want 

to monitor, the window contains a tree that can show the object maintained on a cluster. The 

window contains the following fields: 

Cluster 

Specify the name of a cluster or cluster node and press Refresh to show the cluster objects in 

the tree control. 

... (search button) 

Press the button to find a cluster or cluster node. 

Refresh 

Press the button to find the objects of the specified cluster. When ready, MonitorMagic will show 

the objects maintained on the cluster in the tree control on the left in the window. 

Type of cluster object - Cluster resource 

Currently the only valid option. Specifies that you want to monitor cluster resources. 

Monitor only resources of type 

When selected, MonitorMagic will only generate monitors for the specified type. 

Monitored objects - All objects of the specified type 

Select this option if you want MonitorMagic to generate monitors for each object that matched the 

type of object found. 

Monitored objects - Only objects with name(s) 

Select this option if you want to filter to found objects by name. MonitorMagic will create monitors 

only for the objects that match with the specified name or name template. Note that you can 

specify multiple individual names, separated by comma's. Names can contain wildcards (*) for 

instance User*. 

See also: 


93





Each cluster resource monitor has the following values: 


Cluster WINTER The name of the cluster. 

Evaluation time 09:07:00 09-16-2001 The time and date when the 

cluster resource information 

was last updated. 

Group UserData The name of cluster group that 

contains the cluster resource. 

Node WINTER_A The name of the cluster node 

that currently owns the group 

of the cluster resource. 

Resource UserDataShareA The name of the custer 

resource. 

Resource state The state of the cluster resource. One of: 

Failed - resource has failed 

Initializing - the resource is 

initializing 

Offline - not operational 

Offline pending - going offline 

Online - normal operation 

Online pending - coming online 

Pending - coming online or 

going offline 

Unknown - any other state 

Resource type 

The type of the resource. 

MonitorMagic Service KRAKEN The name of the computer that 

runs the MonitorMagic service 


Status 

error 

OK 

warning 

See also: 





The general status of the 

monitor. If not OK, the 


able to collect the cluster 

resource information 

(completely). 

Snmp trap 

94


Snmp trap monitor - Overview 

The Snmp trap monitor allows you to receive SNMP traps with the MonitorMagic service. These 

traps can be generated by any host that is capable of sending SNMP traps. Once a SNMP trap is 

received, the MonitorMagic service can apply rules and execute alarm actions. 

Each MonitorMagic service can only have a single Snmp trap monitor that processes the traps 

received. The monitor can have multiple rules and alarm actions defined. The rules defined for 

the Snmp trap monitor can be used to execute different alarm actions for SNMP traps 

originating from different hosts. 

The MonitorMagic service cooperates with the Microsoft's SNMP service and SNMP trap 

service and requires these components to be installed and running. See MonitorMagic SNMP 

requirements for more information. 

Principle of operation 

A host fires (sends) a SNMP trap to the computer that runs the MonitorMagic service. For 

the remote host, the computer that runs the MonitorMagic service is identifier by the 

(TCP/IP) address of the computer. 

The MonitorMagic service receives the trap and processes the trap according to the rules 

and alarm actions defined for the Snmp trap monitor 

Alarm actions can be executed by the MonitorMagic service, based on the content, 

originating host or other parameters of the trap. 

Scheduling 

For the Snmp trap monitor, the scheduling parameters are ignored. When the Snmp trap 

monitor is configured for the MonitorMagic service, the MonitorMagic service will process the 

monitor immediately when a new trap is received, regardless of the configured scheduling 

parameters. 

See also: 

MonitorMagic SNMP support 


Snmp trap monitor: Overview 

Snmp trap monitor: Specify monitor 

Snmp trap monitor - Snmp trap monitor values 

Snmp trap monitor - Specify monitor 

To enable receiving SNMP traps from SNMP hosts, you can define a single Snmp trap monitor. 

This section describes how you specify such a monitor for a monitor policy. The procedure to 

create a Snmp trap monitor directly is very similar. To start, activate the monitor policies window, 

select the policy, right click the mouse and select the menu options Add monitor, Snmp trap. 

The Specify Snmp trap monitor window is then shown. 

95


For the Snmp trap monitor you cannot specify any input parameters. The function to receive 

SNMP traps is simply enabled or not enabled. You can specify any number or rules and alarm 

actions to determine how receiced traps must be processed. See Snmp trap monitor - Snmp trap 

monitor values and Rules overview for more information. 

See also: 







The Snmp trap monitor has the following values: 


Agent address 192.168.195.206 The TCP/IP address of the SNMP agent that 

generated the trap (retrieved from the received 

SNMP packet). 

Enterprise 1.3.6.1.4.1.11392.1 The object identifier of the enterprise that 

generated the trap. 

96


Source address Enterprise specific Te address of the agent that generated the 

SNMP trap. This information is retrieved from 

the network transport 

Generic trap type Enterprise specific The generic type of the trap: 

Cold start 

Warm start 

Link down 

Lnk up 

Authentication failure 

EGP peer down 

Enterprise specific 

Specific trap type 4 The specific type of the trap, as defined by the 

SNMP agent that generates the SNMP trap 

Community public The community string of the generated SNMP 

trap. 

Trap agent time 

reference 

01:12:45:67 

(hour:minute:second:100th 

of second) 

The trap time in 100th's of seconds since the 

SNMP agent was started. 

Trap data count 2 The number of data 'objects' received for the 

trap. 

Trap data object 1 System error occured The value of trap data object 1. 

Trap data object 2 Service crashed The value of trap data object 2. 

Trap data object 3 The value of trap data object 3. 






Trap data oid 1 .1.3.6.1.4.1.11392.1.1.2.0 The object identifier of trap data object 1. 

Trap data oid 2 .1.3.6.1.4.1.11392.1.1.3.0 The object identifier of trap data object 2. 

Trap data oid 3 The object identifier of trap data object 3. 






Trap text data 

System error occured, 

Service crashed 

The value of all trap data objects represented as 

a single text string. 

Last trap time 11:03:18 06/12/2002 The time and date when the last trap was 

received by the MonitorMagic service 

Evaluation time 11:08:42 06/12/2002 The time and date when the file monitor was last 

updated. 


Service 

SUMMER 

The name of the computer that runs the 

MonitorMagic service which processes this 

monitor. 

97


Status 

error 

OK 

warning 

The general status of the monitor. If not OK, the 

MonitorMagic service was not able to collect the 

Snmp trap monitor information (completely). 

See also: 






Snmp get 

Snmp get monitor - Overview 

Tasks of the Snmp get monitor 

MonitorMagic uses the Snmp get monitor to collect and process SNMP information from any 

host that supports SNMP version 1. With the Snmp get monitor you can perform the following 

tasks: 

 

 

 

 

 

 

Collect SNMP information from any host that supports SNMP. 

Show the collected information in the MonitorMagic user interface application. 

Process the collected information and apply rules and execute alarm actions depending 

on the values of the collection information. 

Show and print graphs of data collected from SNMP hosts. 

Store SNMP data in a database for trend analysis, graphing etc. 

Show the collected information in the MonitorMagic web interface. 

Besides the tasks accomplished by the Snmp get monitor, MonitorMagic can also receive 

SNMP traps and send SNMP traps 

Principle of operation 

To use the Snmp get monitor you should be familiar with the basic concepts of SNMP. When 

using Snmp get monitors, each monitor represents one or more data values obtained from a 

host that supports SNMP. The monitor specification includes the specification of the host, SNMP 

community and object identifiers that must be obtained. The SNMP information is obtained 

according to the specified scheduler. As with all other monitors, you can define rules and alarm 

actions for the Snmp get monitor. When the data is received, the rules are evaluated and alarm 

actions can be executed. 

Each Snmp get monitor can collect information for up to 8 object identifiers. Since a lot of SNMP 

object identifiers represent cumulative values, MonitorMagic can apply some basic formulas to 

calculate more representative information. The calculated data value can be stored in the 

database for trending and graphs. 

Note that you need to have the Microsoft SNMP service installed and running to use the 

Snmp get monitor. 

See also: 



Snmp get monitor - Tables 

98


Snmp get monitor - Object identifiers and MIB's 

A Snmp get monitor contains the specification of a SNMP host, community and up to 8 object 

identifiers. The object identifiers specify the data that must be collected from the SNMP host. The 

object identifiers can be found in the Management Information Base (MIB) that is supported by 

the SNMP host. Note that the MIB is specific for the SNMP host and that the MIB complies to the 

SNMP standard. 

In order to be able to specify a Snmp get monitor, you need to know the object identifier(s) you 

want to collect data for. To know the object identifier, you need to have the MIB file in text format 

available, or you can examine the SNMP host by querying all the data with MonitorMagic. Note 

that with MonitorMagic you cannot import the MIB file. If you would like to see this feature 

implemented, please send an E-mail message to support@tools4ever.com. 

For each Snmp get monitor 8 object identifiers can be specified. Since an object identifier is not 

very descriptive, you can specify an description for each object identifier. The description can be 

shown in the various windows of MonitorMagic. For each object identifier, the Snmp get monitor 

has a data field to contain the actual data. 

To learn more about SNMP, you can read the following book: 

The Simple Book 

An Introduction to Internet Management 

by Marshall T. Rose, ISBN 0-13-177254-6, Prentice-Hall, Inc. 

or you can get more information from a number of web sites, for instance 

http://www.wtcs.org/snmp4tp. 

See also: 




Snmp get monitor - Guidelines 

To specify a Snmp get monitor, you can use the following guidelines to minimize the effort 

involved: 

Required information 

TCP/IP address of SNMP host and community name (public?) of the SNMP agent 

supported by the SNMP host 

Object identifier(s) of the information you want to collect, example 1.3.6.2.1.3.2.4.5. 

Note that you need to have the Microsoft SNMP service installed and running to 

use the Snmp get monitor. 

Object identifiers 

If you don't know the object identifier, you can use MonitorMagic to find the object 

identifier by querying all information from the SNMP agent. See Snmp get monitor - 

Getting all data for more information. 

Object identifiers are described in the Management Information Base that is supported by 

the SNMP agent. If you have a (printed) text file of the MIB, you can find the object 

identifier and test it with MonitorMagic. See Snmp get monitor - object identifier 

specification for more information. 

You can use the Internet to find a mib file of a certain device. For example, the Internet 

site http://www.mibcentral.com contains a library of mib files for many systems of various 

manufactures. 

99


Tables 

MonitorMagic fully supports the ability to monitor table rows. See Snmp get monitor - 

Tables for more information 

Calculated values 

It is very well possible that the data obtained from a SNMP agent cannot be used directly 

to specify rules and criteria. This might be caused by the fact that most values are 

cumulative. MonitorMagic support basic formulas to solve this problem. 

MonitorMagic policy 

You can create Snmp get monitors directly or by using a policy. It is advised to use a 

policy and then apply the policy to a computer that runs the MonitorMagic service. By 

using a policy, you only have to specify the Snmp get monitor once. 

See also: 




Snmp get monitor - Specify monitor 

This section describes how you can specify Snmp get monitors for a monitor policy. The 

procedure to create a Snmp get monitor directly is very similar. To start, activate the monitor 

policies window, select the policy, right click the mouse, and select the menu option Add 

monitor, Snmp get. The Specify Snmp get monitor window is shown. 

100


The window shows the name of the monitor (AUTUMN - Number of bytes received by server) and 

a list with Snmp get monitors. For each entry in the list, the MonitorMagic service will create one 

or more Snmp get monitors when the policy is applied. 

Use the Add, Edit and Delete buttons to manage the Snmp get monitors. 

See also: 




Snmp get monitor - object identifier specification 

For each Snmp get monitor, you need to specify the object identifier(s) of the data that must be 

collected for the monitor. To start, activate the monitor policies window, select the policy, right 

click the mouse, and select the menu option Add monitor, Snmp get. Press the Add button. You 

will be shown the Snmp object identifier specification window: 

101



Host address 

The TCP/IP address of the host. Example: 192.168.195.206 or www.tools4ever.com. 

Host community 

The community used to access the SNMP host. This textual value is configured for the SNMP 

host. 

Object identifier(s) 

The object identifiers that must be collected for this Snmp get monitor. Multiple object identifiers 

must be separated by comma's (,), but it is advised to use the Advanced button to specify 

multiple object identifiers. 

Advanced 

Press this button to specify multiple object identifiers for a single Snmp get monitor, to specify 

table row entries and formulas. 

Get 

Press this button to issue a SNMP GET request for the specified host, community and object 

identifier. You can do this to test the SNMP functionality and check the specification. Results are 

written to the fields Object identifier and Result data in the bottom of the window. 

GetNext 

Press this button to issue a SNMP GETNEXT request for the specified host, community and 

object identifier. You can do this to the SNMP functionality and find the next object identifier 

supported by the specified SNMP host. Example: to find the first object identifier supported by the 

SNMP agent, specify the host address, host community and specify 1 as the object identifier. 

Press GetNext and check the resulting object identifier and result data fields. 

102


Get All... 

Press this button to show the window that allows you to query all values of the SNMP host. Use 

this feature to examine the SNMP agent in detail. See Snmp get monitor - Getting all data for 

more information. 

See also: 




Snmp get monitor - Getting all data 

With MonitorMagic you can query all data from a SNMP agent to find all object identifiers and 

their values. The function is implemented in a robust multi threaded environment that allows you 

to intercept the operation when it lasts to long to retrieve all data. You can use this function for the 

following purposes: 

 

 

 

 

When you are specifying Snmp get monitors and do not know the object identifier(s) 

exactly 

To examine the SNMP agent supported by the host 

To check if a SNMP agent supports a certain Management Information Base (MIB). 

To test the SNMP functionality of MonitorMagic. 

To access this function, activate the monitor policies window, select a policy, right click the 

mouse, and select the menu option Add monitor, Snmp get. Press the Add button. You will be 

shown the Snmp object identifier specification window. Press the Get All... button. This opens 

the Snmp get all window: 

103


Specify the Host address, Host community and a object identifier to start with. Press the Start 

button. MonitorMagic will then issue SNMP GETNEXT requests and show the retrieved object 

identifier and corresponding value in the list Agent data. While retrieving the data, you can press 

the Stop button to stop querying the SNMP agent. Note that once all data is collected it may take 

some time to write the data to the window. 

See also: 




Snmp get monitor - Specifying multiple object identifiers 

For a Snmp get monitor, you can specify a single object identifier of multiple object identifier. In 

most circumstances, Instead of multiple object identifiers for a single Snmp get monitor, you can 

also create multiple Snmp get monitors with a single object identifier. You should use multiple 

object identifiers for the following situations: 

When you want to perform a calculation on multiple object identifiers. You can calculate 

formulas only on object identifiers values of the same Snmp get monitor. 

When you want to monitor multiple values of table rows and see the results in a single 

line. 

To specify multiple object identifiers, activate the monitor policies window, select the policy, 

right click the mouse, and select the menu option Add monitor, Snmp get. Press the Add button. 

You will be shown the Snmp object identifier specification window. Press the Advanced 

button. 

104


First select the Data type specification. For more information on tables, see Snmp get monitor - 

Tables. Next, use the Add, Edit and Delete button to manage the object identifiers of this Snmp 

get monitor. Every entry has 3 fields: 

Field Example Description 

Entry Oid1 The internal name of the object identifier used in formula's. 

The name is generated by MonitorMagic automatically. 

Object 

identifier 

.1.3.6.1.4.1.77.1.2.12.0 (One of ) the object identifiers of the Snmp get monitor. 

The value identifies an instance of some parameter 

maintained by a SNMP agent. 

Description The number of bytes 

sent by the server 

A user defined description of the object identifier used for 

displaying purposes (only). 

105


Note that the maximum number of object identifiers you can specify for a single monitor is 8. For 

most circumstances, you will only use one or two object identifiers for a single Snmp get monitor 

See also: 





SNMP agents support tables with multiple table rows and columns. Because of the tabular nature, 

this kind of information is substantially different compared to non-tabular information and needs 

special processing to take care of. With MonitorMagic, SNMP tables are fully supported and you 

can monitor all values of a tables. 

The support of SNMP tables in MonitorMagic is best described by an example. Suppose we want 

to monitor the average amount traffic received on all interfaces of a system. This information is 

part MIB-II, supported by most TCP/IP hosts that support SNMP. 

According to mib-ii, RFC1213, the interface table is identified by iso (1) .org (3) . dod (6) . 

internet (1) . mgmt (2) . mib-2 (1) . interfaces (2) . ifTable (2) and the interface entries start at 

1.3.6.1.2.1.2.2.1. To read all table rows and columns and examine the table in detail directly, see 

Snmp get monitor - Read a table. 

In MonitorMagic, each table row corresponds with a single Snmp get monitor. For a single 

monitor, you might want to read multiple object identifiers for each row, for instance the total 

number of bytes in and out for an particular interface. For this example you need to specify the 2 

object identifiers, excluding the ending index (row) of table entry: 

1.3.6.1.2.1.2.2.1.10 (iso.org.dod.internet.mgmt.mib-2.interfaces.ifTable.ifEntry.ifInOctets) 

1.3.6.1.2.1.2.2.1.16 (iso.org.dod.internet.mgmt.mib-2.interfaces.ifTable.ifEntry.ifOutOctets) 

Next you need to specify what rows you want to monitor. See Snmp get monitor - All rows versus 

specific rows for more information. 

See also: 




Snmp get monitor - Read a table 

(This topic is part of a sequence of topics that start with Snmp get monitor - Tables 

To view the interface table of a SNMP agent that supports MIB-II, activate the monitor policies 

window, select the policy, right click the mouse, and select the menu option Add monitor, Snmp 

get. Press the Add button. You will be shown the Snmp object identifier specification window. 

Press the Advanced button and select options Object identifier(s) are entries in a table and 

Generate monitors for the following specific table entries. Press the Add button at the 

bottom of the window. 

106


To collect the data from the table, specify the Host address, Host community and the Table 

object identifier. Note that the Table Object Identifier must include the entry identifier. 

Example: for the MIB-II interface table the Table Object Identifier is 1.3.6.1.2.1.2.2.1 which 

corresponds with iso.org.dod.internet.mgmt.mib-2.interfaces.ifTable.ifEntry. Press GET 

DATA to collect the SNMP table information. 

According to the SNMP protocol, the identifier directly following the table entry identifier specifies 

the entry field (column) of the table and the rest of the object identifier contains the index (row) of 

the SNMP table. (By subsequent calls of the GETNEXT request, you will get all table values for 

column 1 for all rows, then all table values for column 2 for all rows and so on) 

Thus, an object identifier of an entry in a SNMP table contains the following three fields: 

[table entry identification] . [column] . [table column] 

Examples: 

iso.org.dod.internet.mgmt.mib-2.interfaces.ifTable.ifEntry . ifDescr . 1 (value is MS TCP 

Loopback interface) 

1.3.6.1.2.1.2.2.1 . 2 . 1 (value is MS TCP Loopback interface) 

See also: 




Snmp get monitor - All rows versus specific rows 


A SNMP table contains a number of rows and columns. Each row corresponds with a certain 

entity (for instance interface card). For each row, you can obtain the same type of information, 

corresponding with the different columns in the table. When monitoring the data from a table with 

MonitorMagic, each row of the table corresponds with a single Snmp get monitor. When 

specifying Snmp get monitors, you can either generate monitors for all table rows or create 

107


monitors for specific table rows. To specify these settings, activate the monitor policies window, 

select the policy, right click the mouse, and select the menu option Add monitor, Snmp get. 

Press the Add button. You will be shown the Snmp object identifier specification window. 

Press the Advanced button. 

Generate Snmp get monitor for all rows 

To let MonitorMagic generate Snmp get monitors for every table row, select the options Object 

identifier(s) are entries in a table and Generate monitors for all table rows. In the section 

Object identifier specification, specify the table column identifier. See Snmp get monitor - Read 

a table for more information. 

Generate Snmp get monitors for specific rows 

To generate Snmp get monitors for specific rows only, select the options Object identifier(s) 

are entries in a table and Generate monitors for the following specific table rows. Use the 

Add and Delete button to manage the included table rows. When pressing the Add button, you 

will be able to read the complete SNMP table and select the rows that must be included. See 

Snmp get monitor - Read a table 

108


Next topic in sequence: Snmp get monitor - Formula calculation 

See also: 




Snmp get monitor - Formula calculation 


When collecting SNMP data, it is very well possible that you want to perform some data 

calculation before you evaluate the rules. Example: Suppose you want to create a rule that 

should be triggered if the average number of bytes received per second on an interface card 

exceeds a threshold. This type of information is available from MIB-II, the interface table. Table 

entry 1.3.6.1.2.1.2.2.1.10 (iso.org.dod.internet.mgmt.mib-2.interfaces.ifTable.ifEntry.ifInOctets) 

identifies the total number of bytes received on each interface card. But, this is a cumulative value 

that will increase in time only. By itself, this value will not show the average number of bytes 

received per second. What we really need is the result of a formula that calculates the 

difference of two samples of the cumulative value, divided by the time in seconds of these two 

samples: 

In formula: 

ValueOld:The total number of bytes received at time Told. 

ValueNew: The total number of bytes received at time Tnew: 

Average number of bytes per second = (ValueNew - ValueOld) / (Tnew - Told) 

MonitorMagic support a number of formulas by default. To specify the formula activate the 

monitor policies window, select the policy, right click the mouse, and select the menu option 

Add monitor, Snmp get. Press the Add button. You will be shown the Snmp object identifier 

specification window. Press the Advanced button. The formula's can be selected from the 

bottom list. 

Formula's can be calculated over the first 2 object identifiers of the list Object identifier 

specification only. These object identifiers are referred to as Oid1 and Oid2. For these object 

identifiers, MonitorMagic also stores the previous value and elapsed time since the previous 

value. Note that the result of the formula calculation can be stored in the database and can be 

used for rule criteria evaluations. 

Available formula's: 

Standard (value of Oid1) 

No formula calculated, result equals the value of the first object identifier. 

Oid1 difference in time (ValueNew-ValueOld) 

Result equals the difference between current and previous value of the first object identifier. 

Oid1 change per second (Vnew-Vold)/(Elapsed time) 

Rate calculation, the result is the change per second of the first object identifier in units per 

second. 

Oid2 difference in time (ValueNew-ValueOld) 

Result equals the difference between current and previous value of the second object identifier. 

109


Oid2 change per second (Vnew-Vold)/(Elapsed time) 

Rate calculation, the result is the change per second of the first object identifier in units per 

second. 

Oid1 plus Oid2 (V1+V2) 

Result equals the sum of the first two object identifiers. 

Oid1 plus Oid2 difference (V1new+V2new)-(V1old+V2old) 

Result equals the difference between current sum and previous sum value of the first two object 

identifiers. 

Oid1 plus Oid2 per second {(V1new+V2new)-(V1old+V2old)}/{Elapsed time} 

Rate calculation, the result is the change per second of the sum of first two object identifiers in 

units per second. 

Oid1 minus Oid2 (V1-V2) 

Result equals the difference between the first two object identifiers. 

Oid1 minus Oid2 difference (V1new-V2new)-(V1old-V2old) 

Result equals the difference between current difference and previous difference value of the first 

two object identifiers. 

Oid1 minus Oid2 change per second {(V1new-V2new)-(V1old-V2old)}/{Elapsed time} 

Rate calculation, the result is the change per second of the difference of the first two object 

identifiers in units per second. 

Oid1 divided by Oid2 (V1/V2) 

The value of object identifier 1 divided bu\y the value of object identifier 2. If the value of object 

identifier 2 equals zero, the result is zero. 

Oid1 times Oid2 (V1 * V2) 

The result of the value of object identifier 1 times object identifier 2. 

See also: 




Snmp get monitor - Database support 

You can store the data obtained from Snmp get monitors in the MonitorMagic database. To 

specify the database storage parameters for the Snmp get monitor, see Database - Monitor 

data and Database - Changing database storage for multiple items for more information. 

For each Snmp get monitor, MonitorMagic can only store the result of the specified formula. By 

default, the result of the formula equals the value of the first specified object identifier. See Snmp 

get monitor - Formula calculation for more information. 

See also: 




110


Snmp get monitor - Web interface support 

As with all other monitors, the data values obtained for the Snmp get monitor can be shown in 

MonitorMagic Web Interface. 

For each Snmp get monitor, the MonitorMagic Web Interface shows the following columns: 

Host agent 

Description object 1 

Data object 1 

Data calculated value 

Evaluation time 

Status 

See also: 




Snmp get monitor - Monitor values 

The following values exist for each Snmp get monitor: 

Monitor 

value 

Host agent 

SNMP 

Community 

Time-out 

(ms) 

Example(s) 


192.168.195.201 

public 

Description 

The specification of the host that runs the SNMP agent 

for which data must be collected. 

The SNMP community of the host 

10000 The time out value in milliseconds (ms) used to obtain 

data from the SNMP host agent. 

Retry count 5 The maximum number of retries used to retrieve the 

111


Object count 2 

Object 

identifier 1 

Object 

identifier 2 

Object 

identifier 3 

Object 

identifier 4 

Object 

identifier 5 

Object 

identifier 6 

Object 

identifier 7 

Object 

identifier 8 

Description 

object 1 

Description 

object 2 

Description 

object 3 

Description 

object 4 

Description 

object 5 

Description 

object 6 

Description 

object 7 

Description 

object 8 

requested data. 

The number of object identifiers (1,...,8) for which data 

is collected with this 'Snmp get' monitor. 

.1.3.6.1.2.1.1.1.0 The object identifier of object 1 for which data is 

collected with this 'Snmp get' monitor. 















System description 

Object id 

System up time 

Contact person 

System name 

System location 

Type of services 

Number of interfaces 

Data object 1 Hardware: x86 Family 6 

Model 2 Stepping 1 

AT/AT COMPATIBLE - 

Software: Windows 2000 

Version 5.0 (Build 2195 

Uniprocessor Free) 

The description of object 1 for which data is collected 

with this 'Snmp get' monitor. 















The data collected for object 1. 

Data object 2 .1.3.6.1.4.1.311.1.1.3.1.2 The data collected for object 2. 

Data object 3 492201 The data collected for object 3. 

Data object 4 The data collected for object 4. 

Data object 5 AUTUMN The data collected for object 5. 

Data object 6 The data collected for object 6. 

112




Data 

calculation 

mode 

Data 

calculated 

value 

Data 

calculated 

interval 

Database 

storage 

Evaluation 

time 

1 The calculation method used to calculate the resulting 

data value of the 'Snmp get' monitor. The calculation 

method can include multiple oid's and previous values 

of oid's. 

2 The calculated result of the data value of the SNMP 

object. The calculation method can include multiple 

oid's and previous values of oid's. When the monitor 

data is stored in the database, this is the value stored in 

the database. 

60 The interval time in seconds that can be used when 

calculating the resulting 'Snmp get' monitor data value. 

The calculated result of the data value of the SNMP 

object. The calculation method can include multiple 

oid's and previous values of oid's. 

The specification if monitor data must be stored in the 

database. 

09:07:00 08-16-2001 The time and date of the last ping sent to the host 

Status OK, Warning, Error The general status of the monitor. If not OK, there was 

no response from the remote host. 


service 

Tulip 

See also: 






Command 

Command monitor - Overview 

The Command monitor can be used to execute any program, command, executable, batch or 

script and analyze the output of it. The program executed by the command monitor is always 

executed by the machine that runs the MonitorMagic service. 

The command monitor is also used to activate MonitorMagic Plugins. The MonitorMagic 

Plugins are a set of command line utilities that can be used for monitoring purposes. 

To create a command monitor, activate the monitor policies window, select the policy, right 

click the mouse, and select the menu option Add monitor, Command. The Specify Command 

monitor window is shown. Press the Edit button to continue. 

See also: 

Command monitor - Specify monitor 

Command monitor - Monitor values 


MonitorMagic Plugins 

113



To create a command monitor, activate the monitor policies window, select the policy, right 

click the mouse, and select the menu option Add monitor, Command. The Specify Command 

monitor window is shown. Press the Edit button. You will be shown the Command monitor 

specification window: 


MonitorMagic plugin 

If the command you want to specify is a MonitorMagic plugin, simply select the name of the plugin. 

All fields in the window will be filled in with the default parameters for the plugin. You will probably 

need to change the Command arguments field only. 

Command 

The full command line of the command, program, executable, script or batch file that must be 

executed by the MonitorMagic service when processing this monitor. 

Start in 

114


The path of the directory where the command line must be executed. When processing this 

command monitor, the MonitorMagic service will execute the command line composed of the 

text specified in this field and append the command specified in the Command field. 

If the command monitor is part of a policy, you might not exactly know the full path of the 

command when applied an executed by a MonitorMagic service. Therefor, the following keywords 

can be selected: 

Start in Example Description 

any text C:\OtherUtils The path where the Command can be found. Note that as an alternative, the 

Command field itself can also contain this information. 

[Windows 

directory] 

[Windows 

System32 

directory] 

[MonitorMagic 

service plugins 

directory] 

[Windows 

directory] 

[Windows 

System32 

directory] 

[MonitorMagic 

service plugins 

directory] 

When applied to a MonitorMagic service, this field is expanded to the actual 

Windows directory of the computer that runs the MonitorMagic service. 

When applied to a MonitorMagic service, this field is expanded to the actual 

Windows System32 directory of the computer that runs the MonitorMagic service. 

When applied to a MonitorMagic service, this field is expanded to the Plugins 

subdirectory of the MonitorMagic service program directory. This is the default 

location of the MonitorMagic service plugins. 

Wait until command is completed 

Specify this option if you want the MonitorMagic service to wait until the command is completed 

when executing the command line. If for whatever reason the command will never end, this will 

cause the thread evaluating the monitor to hang. 

Terminate process after ... seconds 

Specify this option if you want the MonitorMagic to terminate the command when it is not 

completed in reasonable time. This is the recommended option. 

Limit the number of output characters for displaying purposes to ... characters 

A number of commands can generate a large amount of output data. To be able to display this 

data in a column or alert message, you can limit the number of characters displayed. Note the 

complete output text is also available. 

Analyze command output. Find output word ... 

Select this option if you want the MonitorMagic service to find specific text in the command output. 

... starting at character output position ... 

Select this option if the command output text you want to analyze can be found on a fixed position. 

For this option, you need the specify the position as well. 

... positions after word ... 

Select this option if the command output text can be found a fixed number of characters after the 

specified word. For this option you need to specify the offset position and reference word as well. 

If word not found, use word ... 

You can specify a default word that will be used by the MonitorMagic service for analyzing 

purposes when the specified word cannot be found. 

Word represents a number 

Select this option if the word found represents a number. Note that you must select this option 

if you want to store the results of the command in a database. 

Test 

Press this button to test the command on a connected MonitorMagic service. By default, a timeout 

value of 300 seconds will be used. 

See also: 


115





The following values exist for each Command monitor: 

Monitor 

value 

Command 

Example(s) 

T4eWebPing 

http://www.tools4ever.com 

Description 

The full command specification of the command, 

script, batch file or executable. 

Start in public Directory specification where to start the command. If 

the Command field already contains this information, 

the field should be blank. 

Timeout 

(seconds) 

300 Command termination time-out value in seconds 

(valid only when option specified) 

Computer Tulip The name of the computer on which the command is 

executed. 

Exit code 0 Command exit code. 

Runtime (ms) 1800 

Runtime 

(sec) 

Output 

Output 

(limited) 

Output value 

(text) 

Output value 

(number) 

Text position 8 

Reference 

text 

Reference 

text offset 

position 

Command run time in milli seconds. 

1 Command run time in seconds. 

Response time: 1840ms 

Error value: 0 

Byte count: 3426 

Response time: 1840 ms 

1840ms 

Command output text. (limited to 10240 characters) 

Limited command output text. (limited to specified 

number of output positions) 

Searched resulting output text. 

1840 Searched resulting output number. 

Response time: 

Output text position specification (valid only when 

option specified). 

Reference text searched for (valid only when option 

specified). 

2 Reference text offset position (valid only when option 

specified). 

Default text 0 Default text used when searched text not found in 

output. 

Output 

character 

count limit 

Start in 

(option) 

Command 

execution 

64 Output character count limit. (used for value Output 

(limited)) 

0 Start in option (internal use only) 

0 Command execution flags (internal use only) 

116


flags 

Output 

analysis flags 

Database 

storage 

Evaluation 

time 

0 Output analysis flags 

The specification if monitor data must be stored in the 

database. 

09:07:00 08-16-2001 The time and date of the last ping sent to the host 

Status OK, Warning, Error The general status of the monitor. If not OK, there was 

no response from the remote host. 


service 

Tulip 

See also: 






Scheduling 

Scheduling overview 

MonitorMagic supports a number of methods to schedule the processing of monitors. The 

scheduling controls how often and when the monitors must be processed. In most circumstances, 

monitors will be processed on an interval basis. But there are a number of different scenario's 

possible. 

The scheduling parameters can be specified for each individual monitor. So each monitor can 

have its own scheduling schema. Normally you specify the scheduling parameters as part of the 

policy. When the policy is applied and the monitors are generated the scheduling parameters are 

copied to each monitor. 

To configure the scheduling parameters, select the monitor of the policy or a monitor from the 

monitor window. Right click the mouse and select menu option Properties. In the window shown, 

select the tab Scheduling. 

117


MonitorMagic supports 4 basic scheduling methods: Every interval, Hourly, Daily and Not 

scheduled. 

Every ... seconds 

Select this option to process the monitors on an interval basis. For this option, you need to 

specify the interval period in seconds as well. You can define additional exception intervals (see 

Exceptions) to exclude certain periods. 

Hourly 

Select this option if you want to process the monitors once every hour on a fixed moment, for 

instance at 1:30, 2:30, 3:30, 4:30 and so on. You can define additional exception intervals (see 

Exceptions) to exclude certain hours. 

Daily 

Select this option if you want to process the monitors once every day on a fixed moment, for 

instance at 10:45. You can define additional exception intervals (see Exceptions) to exclude 

certain periods. 

Not scheduled 

Select this option if you do not want to schedule the processing of the monitor automatically. If a 

day is not checked, the monitor will not be processed on that day. 

Include these days 

Check the days of the week that should be included for the specified scheduling method. 

Exceptions 

You can specify additional intervals that are included or excluded. Use the Add, Edit and Delete 

buttons to manage the intervals. Select one of the options Exclude intervals or Include 

specified intervals only. This selection affects all specified intervals. Note that the specified 

118


intervals can overlap with the specified days in section Include these days. If both specifications 

contradict, the included days specification takes precedence. See Scheduling exceptions 

intervals for more information. 

Test 

Once you have specified the scheduling parameters you can press the Test button to see the 

results. A window appears showing the next 20 times that monitors will be processed according 

to the scheduling specification. See Scheduler test for more information. 

See also: 


Scheduling exceptions intervals 

Scheduler test 




For each scheduling method you can define exception intervals. The intervals can either be 

included or excluded. See Scheduling overview for more information. MonitorMagic supports 3 

types of exception intervals: 

Hourly repeated interval 

The interval is repeated every hour. Specify the (included) first minute and (included) last 

minute of the interval. If the specified first minute exceeds the specified last minute, the interval 

includes the full hour minute moment. E.g.: first minute=50, last minute=10, includeds times 

around 9:00 AM: 8:50,8:51,...,8:59,9:00,9:01,...,9:10. 

Daily repeated interval 

The interval is repeated every day. Use the HH:MM format to specify the included First time and 

Last time where HH ranges from 0 to 23 and MM ranges from 0 to 59. Do not use the AM and 

PM abbreviations. When the First time moment is later then the Last time, the Last time is 

assumed to be in the next day. 

Non repeating interval 

Select the Start time and End time to specify a fixed, non repeating, interval. 

See also: 


119







You can test the parameters of a configured scheduling method. To configure the scheduling 

parameters, select the monitor of the policy or a monitor from the monitor window. Right click the 

mouse and select menu option Properties. In the window that appears, select the tab 

Scheduling. Enter the scheduling parameters and press the Test button. 

The window shows the first 20 scheduling time and dates. By changing the Start date, you can 

run the test to generate the scheduling times from any moment. 

120


Generate 

Generates and displays the next 20 scheduling times. Note that scheduling times will only be 

evaluated for a period of approximatekly 2 years from the specified Start date. 

Clear 

Deletes the selected entries from the list Scheduled date and times. If no entries are selected, 

all entries will be removed. 

Close 

End the test. 

See also: 






Rules 


Rules are an essential component in MonitorMagic. To get a basic understanding of policies, 

monitors, rules and alarm actions read the topic Policies, Monitors, Rules and Alarm actions first. 

Rules and monitors 

A rule is part of a monitor. You use a rule to detect certain events that relate to the values of the 

monitor. A rule is either triggered or not triggered. A rule contains one or more criteria which are 

comparisons that refer to monitor values. The results of the criteria evaluation determines if a rule 

is triggered. An example of a disk monitor rule is: "Available disk space is less then 10%". 

Rule processing 

When a monitor is processed by the MonitorMagic service, the monitor values are updated 

(example: the disk monitor for logical disk C:\ of server TULIP has the following monitor value: 

available disk space is 8%). Next, MonitorMagic will process all the rules associated with the 

monitor. For each rule all criteria are evaluated. As a result, each rule now has a certain state: 

TRUE (criteria met) or FALSE (criteria not met). The rule state is used to determine if a rule is 

triggered or not. 

Rule triggering 

Rules where the criteria are met (rule state is TRUE) can become triggered. When the rule 

criteria are met the rule is triggered immediately or after some specified period of time. If a rule is 

triggered, alarm actions are initiated. 

Alarm actions 

121


Alarm actions are part of a rule. Alarm actions are initiated when a rule is triggered. See Alarm 

actions overview for more information. 

See also: 

Adding a rule to a policy monitor 

Adding a rule to an existing monitor 

Rule name 

Rule specification 

Adding a criteria to a rule 

Specifying rule criteria 

Delayed rule triggering 

Acknowledge rule 


Rules are contained within monitors: policy monitors or real monitors. The way rules are added to 

monitor policies or real monitors is very similar. This topic shows how to add a rule to a monitor 

policy. To start, activate the monitor policy window by clicking the policies tab, open the policy 

and select a policy monitor. Right click the mouse and select the menu option Add rule. 

The Manage rule window shows up. See Rule specification to continue. 

See also: 



Rule name 




122





Rules are contained within monitors: policy monitors or real monitors. The way rules are added to 

monitor policies is very similar. This topic shows how to add a rule to a real monitor. To start, 

open the monitor window, by double clicking a machine in the network view, and select the 

monitor you want to add a rule to. Right click the mouse and select menu option Properties. 

The Manage monitor window shows up. Select tab Rules and press button Add. 

123


The Manage rule window shows up. See Rule specification to continue. 

See also: 



Rule name 






Rule name 

A rule needs to have name. The name of the rule is used to refer to the rule and, for instance, is 

shown in the monitor policy window. You can specify the name of a rule yourself or let 

MonitorMagic do it. To edit the name of a rule, activate the Manage rule or Edit rule window and 

select tab Rule name. See Adding a rule to a policy monitor and Adding a criteria to a rule for 


124


Generate rule name automatically 

By default, this option is selected and the name of the rule is generated automatically. Once you 

have edited the name of a rule, MonitorMagic will not change the name and the option appears 

grayed out. 

Use this name 

If you select this option, you need to specify the name of the rule. 

Rule description 

Enter a description for the rule. The description can be used in an alarm actions messages. 

See also: 










The most important part of a rule is the rule specification. The rule specification contains the 

criteria of the rule and trigger conditions. The rule is specified from the Rule spec window. See 

Adding a rule to a policy monitor and Adding a criteria to a rule for more information. 

125


The window contains two sections: Criteria specification and Trigger timing. The criteria of the 

rule are listed in the Criteria list. Each line corresponds with one criteria. Use the arrow, Add, 

Edit and Delete buttons to manage the criteria and change the order of the criteria. 

Trigger timing 

Rule triggered immediately when criteria met 

Select this option if the rule must be triggered immediately when the rule criteria are met. See 

Delayed rule triggering for more information. 

Rule triggered when criteria met for ... seconds 

Select this option if you want to enable delayed rule triggering. 

See also: 




Rule name 





Adding criterium to a rule 

A rule contains one or more criteria. To add criteria to a rule or to edit existing criteria, activate the 

Manage rule window, and select the tab Rule spec. Press the Add button or select a rule criteria 

first and press the Edit button. See Rule specification for more information. 

126


See also: 




Rule name 






A rule can have one or more criteria. The criteria are combined in a logical expression to 

determine if the rule state is TRUE or FALSE. You can specify a rule criteria with the Specify 

rule criteria window. To activate the window, see Rule specification for more information 

Most rule criteria consist of three parts: the value to compare (1), the operator (2), and a 

reference value (3). The value to compare is always a monitor value. For different types of 

monitors different values exist. The operator and reference values depends on the type of monitor 

value, e.g. text and numeric values are compared in different ways. 

The window contains 3 parts: 

Specify the three components to setup the criteria 

Value to compare 

Select the monitor value from this list. The list contains all possible monitor values that apply to 

this rule. 

127


The list will be different for different types of monitors. The 

figure, to the left, shows how the list looks like when creating 

a rule for a disk monitor. While you change the selected 

value in the list, the field, Value description will update and 

show a description of the currently selected value. 

Once you have selected a value the contents of the fields Operator and Limit/Reference value 

can be specified. 

Operator 

The operator specifies how MonitorMagic should evaluate the Value to compare and the 

Limit/Reference value. For different types of values different operators apply. When you have 

selected the Value to compare the operator list will contain the applicable values. As an 

example, the following figures show the operator values for numeric and textual monitor values. 

 

Limit/Reference value 

The Limit/Reference value depends on the Value to compare and the Operator. For some 

monitor values the number of possible values is limited and well described. This is the case, for 

instance, with the monitor value Service state of a Service monitor. In these cases, 

MonitorMagic will show the possible values in the list. For other monitor values, you can specify 

any value. When specifying numeric values only use numbers, no suffixes. 

Additional rule criteria settings 

Use the specified components 

Select this option for normal criteria. 

Use a criteria that is always true (no criteria evaluation takes place) 

Select this option if the alarm actions associated with this rule must be initiated each time the 

monitor is processed. As an example: suppose you want to receive the actual CPU load of a 

machine in a popup message (alarm action) every 10 minutes. In this case, the performance 

counter monitor has a rule which should be triggered always (you want to receive the CPU load 

popup message regardless of the actual value of it). 

Instead of a normal criteria, insert an OR operator 

Select this option if you want to combine multiple criteria with the logical OR operator. Normally, if 

you specify multiple criteria the rule state is TRUE if ALL criteria are met; with this option you can 

specify that the rule state is TRUE if the criteria preceding or following the OR operator is TRUE. 

Value description 

This field describes the selected Value to compare. If no Value to compare is selected, no 

description is shown. 

128


See also: 




Rule name 






Delayed rule triggering is a mechanism used to initiate alarm actions only when certain 

conditions are met for a specified period of time. Suppose you don't want your systems to be 

overloaded. To do so, you need to check the CPU-load of the computer. If the CPU-load is too 

high, you want to be informed, for instance by E-mail. But how do you specify too high? 

In this case, too high means that the value should exceed some reference value for some period 

of time. For instance, exceed 90% for at least 5 minutes. To support this with MonitorMagic, you 

must configure a performance counter monitor that watches the % Processor Time. This monitor 

value should not exceed 90 for over 300 seconds. 

In the Rule spec tab, you can do this by selecting the option Rule triggered when criteria met 

for ... seconds. Once the rule is triggered, alarm actions will be initiated. 

See also: 

129





Rule name 






Each rule is contained by a monitor. When a rule is triggered, alarm actions are initiated. The 

execution of alarm actions can be made dependent on the fact of whether or not an administrator 

takes care of the problem causing the monitor to become triggered. If this is the case, the 

administrator can acknowledge the rule causing the execution of alarm actions to be changed. To 

acknowledge a rule, select the monitor of the rule in the monitor window. Right click the mouse on 

the triggered rule in the bottom area of the monitor window and select menu option 

Acknowledge. See Escalation for more information. 

See also: 


Escalation 



Rule name 





Alarm actions 

Alarm actions overview 

Alarm actions are used for notification and execution of several recovery actions. MonitorMagic 

supports all major notification methods (popup, E-mail, pager-SMS messaging, SNMP trap) and a 

number of other actions such as command line execution, service control and system reboot. 

Alarm actions are configured as part of a monitor's rules. See Policies, Monitors, Rules and Alarm 

actions for more information. Alarm actions are initiated when a rule is triggered. MonitorMagic 

supports a number of features regarding the execution of alarm actions, for instance repeated 

alarm action execution and escalation. 

Alarm actions are triggered, executed, and based on rules; hence, you must have a configured 

rule before you can create an alarm action. 

See also: 


Alarm action name 

Managing alarm action execution 

Escalation 

Keywords overview 

130


Adding a new alarm action 

Alarm actions are always added to rules. The rule can be part of a monitor policy or a real monitor. 

Both procedures are very similar. To start, activate the Manage rule, Add rule or Edit rule 

window. See Rule specification for more information. Select the tab Alarm actions. 

The list of Alarm actions shows the alarm actions currently defined for a rule. Use the Add, Edit 

and Delete button to manage the alarm actions. To add a rule, press the Add button. Next, the 

Type of alarm action window is shown. From this window, you need to select the type of alarm 

action you would like to use. 

131


Once you have selected an alarm action, press the OK button. A window used to manage and 

configure the selected type of alarm action pops up. 

See also: 



Activating the manage alarm action window 



Escalation 



There are several ways to manage alarm actions in MonitorMagic. You can manage alarm 

actions while creating them or edit existing alarm action. Further, you can edit the alarm actions 

based on rules of monitor policies or the alarm actions based on rules of real monitors. To 

activate the alarm action window for new alarm action, see Adding a new alarm action for more 

information. 

Activating the manage alarm action window for an existing alarm action in 

a policy 

Activate the monitor policy window. Expand the policy and find the alarm action in the rule of a 

policy monitor. Right click the mouse and select the menu option Configure. 

132


The same window can be activated by selecting the Properties from the rule. Now, select the tab 

Alarm actions, select the alarm action and press the Edit button. With a similar procedure, you 

can activate the same window directly from the monitor. 

Activating the manage alarm action window for an existing alarm action in 

a real monitor 

Activate the monitor window. Select the monitor containing the rule and alarm action. Right click 

the mouse and select the menu option Properties. Choose the Rules tab and select the 

appropriate rule and press the Edit button. Select the Alarm actions tab and choose the alarm 

action from the list. Press the Edit button. 

See also: 





Escalation 



133


Each alarm action has a name. The name is referred to in several windows of MonitorMagic to 

reference the alarm action. By default, MonitorMagic creates a name for the alarm action for you, 

you can also specify your own alarm action name. To activate the tab that specifies an alarm 

actions' name, select the main window to manage an alarm action and select the tab Name. 

The window contains the following options: 

Generate alarm action name automatically 

This is the default option. MonitorMagic will automatically generate a name for the alarm action. 

Use this name 

Select this option if you want to specify the alarm action name yourself. 

See also: 






Escalation 


134



For each type of alarm action, a tabbed manage alarm action window is available. Several tabs 

are the same for all alarm actions. The When tab is used to configure when the alarm action must 

be executed. There are several ways to activate this window. See Activating the manage alarm 

action window for more information. 

Use the When tab of the window to specify when the alarm action must be executed. 

Rule triggered 

Select this option if the action must be executed when the rule is triggered. Besides the rule being 

triggered, other additional conditions can be specified as well. Continue reading for more 

information. For more information on rule triggering, see Rule specification. 

... immediately 

This is the default option and specifies that the alarm action must be executed immediately when 

the rule is triggered. 

... and not acknowledges within ... minutes 

This option is used for escalation. When you select this option, the alarm action is executed only 

when the following conditions are met: 

135


The rule is triggered for a period of time that exceeds the specified period. 

The rule is not acknowledged. 

See the topic on Escalation for more information. 

... and the execution of action .... failed/succeeded 

This option is used to execute an alarm action that is dependent on the result of the execution of 

another alarm action. For instance, you might want to send an E-mail if a service is stopped and it 

was not possible to start the service first. You can select the action for which this action is 

dependent on from a list. The list shows all the names of alarm actions preceding this action. 

Repeat action every ... minutes for ... times maximum. 

Select this option if you want MonitorMagic to repeat this action. You can specify the frequency 

and maximum number of times. Before MonitorMagic repeats the action it will check if the 

rule is still triggered by re-evaluating the monitor values. 

Rule no longer triggered 

Select this option if the action must be executed when the rule was triggered but is no longer 

triggered. The alarm action is executed only once when the rule is no longer triggered. 

Rule not triggered 

Select this option if the action must be executed when the rule is not triggered. The alarm action 

will be executed each time the monitor is processed and the rule is not triggered, regardless of 

the previous rule state. 

Action disabled 

Select this option to disable the action. MonitorMagic will not execute the action when this option 

is selected. 

See also: 






Escalation 


Escalation 

Escalation is a mechanism used for alarm actions: In MonitorMagic, escalation is supported by 

means of un-acknowledged rules and specific alarm action settings. With MonitorMagic, detected 

problems can be escalated when they are not solved or taken care of. The procedure is best 

described by an example: Suppose you want to monitor a critical system. When the system is 

overloaded, (CPU-load too high) a monitor rule is triggered. Notifications will be sent to the local 

Administrator of the system. If within 60 minutes, the problem still exists and no one has taken 

care of the problem, you want to escalate the problem and send an E-mail to your own E-mail 

account. 

To configure this scenario, you first create a performance counter monitor. For this monitor, you 

create a rule that checks a value against some reference value. For this rule, you specify 2 alarm 

actions: 

The popup notification message. The alarm actions is configured to be executed 

immediately when the rule is triggered. 

136


 

The E-mail message. For this alarm action you specify that the action must be executed 

when the rule is triggered and not acknowledged within 60 minutes, as shown in the 

figure below. 

Now, suppose the rule is triggered and the popup alarm action is executed. The local 

administrator either receives the message and takes action or does nothing (or he receives the 

notification message and does nothing). When he (or she) takes action, the rule should be 

acknowledged first. He or she can do this by using the MonitorMagic client. Next, MonitorMagic 

will recognize that the rule is acknowledged and no further actions will be executed. If the rule is 

not acknowledged, after 60 minutes, MonitorMagic will send the escalation E-mail. 

See also: 






Escalation 


137


Popup message 

Popup message destination 

To specify the destination(s) of a popup message, edit an existing popup alarm action or create a 

new popup alarm action. You can specify the destination of a popup message as Windows user 

account name (e.g. Administrator) or a machine account name (e.g. Tulip). 

You can enter as many destinations as you want. They should be separated by comma's or start 

on new lines. Keywords can be used as part of a popups' destination. 

See also: 





Escalation 


Popup message 

138


To specify the contents of a popup message, edit an existing popup alarm action or create a new 

popup alarm action. The contents of the message can contain any text, including keywords. The 

value is generated at runtime. 

To add a keyword, select the keyword from the list and press the Insert button. 

See also: 





Escalation 


Send popup test message 

To confirm that the popup messages arrive at their destination, you can send a test popup 

message. Click on the Send test message button to display the dialog as shown below. 

139


When sending test popup messages, you need to specify the destination. Use the Browse button 

to select a computer in your network. You can also specify which MonitorMagic service should 

perform the sending of the message. Click the Send test message to send the message. 

MonitorMagic will display a dialog which presents the status of the sent message. 

See also: 





Escalation 


E-mail message 

E-mail message destination 

To specify the destination(s) of an E-mail message, edit an existing E-mail alarm action or create 

a new E-mail alarm action. You can specify the destination of an E-mail message as Windows 

user account name (E.g. Administrator) or a machine account name (E.g. Tulip). 

140


See also: 





Escalation 


SMTP E-mail setup 

E-mail message contents 

To specify the contents of an E-mail message, edit an existing e-mail alarm action or create a 

new e-mail alarm action. You can specify the subject and message of the E-mail message. Both 

can contain text of any type, including keywords of which the value is generated at runtime. 

141


See also: 





Escalation 




In order to use SMTP E-mail, you must configure the MonitorMagic service to send E-mail 

messages. To accomplish this you need to know the TCP/IP address or DNS name of the E-mail 

server and SMTP authentication method that can be used by the MonitorMagic service. To 

configure these settings start the MonitorMagic client. In the Network view window browse to find 

the computer running the MonitorMagic service. Right click the computer name and select the 

menu option Configure service. 

142


Select the tab SMTP E-mail. Specify the following fields: 

SMTP server 

Enter the address of the SMTP E-mail server. If you do not specify a valid address the 

MonitorMagic service will not be able to send SMTP E-mail messages. You can enter the address 

in DNS format or dotted notation (E.g. mailserver.tools4ever.com or 192.168.195.67). 

MonitorMagic E-mail address 

Enter the E-mail account the MonitorMagic service should use. Depending on your E-mail server 

it might be required to specify a valid E-mail account. Some E-mail servers don't care about the 

E-mail account specified. The account shows up as the 'From' field in messages sent. 

Authentication method 

None 

Select this option If the selected SNMP service does not require authentication for outgoing mail 

messages. The username and password specified are ignored 

Login 

If the selected SNMP service requires basic authentication by means of the SMTP "LOGIN" 

protocol, select this option. This is for instance the method used by Exchange 2000 when the 

required authentication method on the server is set to "Basic Authentication". This is the most 

commonly used simple username/password authentication method. Note that although the 

password is not send in readable format, it is not encrypted 

Plain 

This is an alternative method for sending username/password authentication in plain text. It is 

recommended to use this only if the login method is not supported by your SMTP server 

SMTP account 

143


Username 

Specify the SMTP user account name for the Login or Plain authentication methods. 

Password 

Specify the SMTP user account password for the Login or Plain authentication methods. 

See also: 





Escalation 


Send SMTP test E-mail message 

To make sure that SMTP support has been correctly configured, you can send test messages 

using MonitorMagic. When adding an e-mail alarm action, use the Send test message button to 

display the dialog as shown below. 

When sending e-mail test messages, specify the receiver's e-mail address, the subject and the 

message body. You can also specify which MonitorMagic service should perform the sending of 

the message. Click the Send test message to send the message. MonitorMagic will display a 

dialog which presents the status of the sent message. 

See also: 




144



Escalation 


Pager - SMS message 


As an alarm action, MonitorMagic can send a message to an pager or mobile telephone (SMS). 

This is done by using a modem, connected to the server that runs the MonitorMagic service. The 

pager - SMS messages are sent by the MonitorMagic service depending on the configured alarm 

actions. See Alarm actions overview for more information. To use pager and SMS messaging, 

you need to install and configure the modem and specify some settings in MonitorMagic. See 

Introduction to pager - SMS and subsequent topics for more information. To configure an pager - 

SMS alarm action, continue reading. 

For an pager -SMS alarm action you need to specify at least the recipient number and message. 


145


Recipient 

The number of the pager - mobile telephone called by the pager - SMS provider. Note that for 

most configurations, this number is not called by the MonitorMagic service directly. 

Sender 

The sender number. Most provider show this number as part of the pager - SMS message. Note 

that you don't have to specify this number. 

Message 

The message sent to the pager - mobile telephone. You can use keywords as part of the 

message. 

Keyword - Insert 

Use these fields to insert keywords into the message contents. 

Generate log file when sending message 

For troubleshooting purposes, you can check this option to let the MonitorMagic service write log 

information to a file when executing the alarm action. The file is called PagerSms.log and can be 

found in the MonitorMagic service data directory. 

See also: 





Escalation 


Introduction to pager - SMS 

Pager - SMS installation and configuration overview 

Pager - SMS modem installation and configuration 

Pager - SMS provider selection 

Pager - SMS managing provider configuration settings 

Pager - SMS adding provider configuration settings 


Pager - SMS script 

Log events 

Log events 

The message specified here will be logged in the Application event log on the computer running 

the MonotorMagic Service. 

146


See also: 





Escalation 


Execute command line 

Command line specification 

To specify the command line, edit an existing command line alarm action or create a new 

command line alarm action. 

147


In the field Command, specify the command line. Note that the command is issued by the 

MonitorMagic service. To make sure that the service is able to find the command file, include the 

full path. The command can contain keyword(s), generated at runtime. 

When command issued, wait until completed 

Select this option if you want the MonitorMagic service to wait until the command is completed 

before continuing with the next alarm action. Use this option if you want to use the resultant value 

of the command execution, or if you don't want to initiate multiple commands at the same time. 

See also: 





Escalation 


SNMP trap 

148


SNMP trap 

When a rule of a monitor is triggered, alarm actions are executed. See Alarm actions overview for 

more general information. One of the possible alarm actions is a SNMP trap. A SNMP trap is a 

special SNMP Message that is send from the MonitorMagic server to specific computers on your 

network that runs software (called an SNMP manager) that can interpret these messages, and 

act on them if required. See Introduction SNMP traps for more general info. 

In order for the SNMP traps to work, SNMP must be configured on the server that the policy 

containing this alarm action is applied. see Requirements SNMP traps and Configure 

MonitorMagic SNMP traps for more information. 

See also: 

Introduction SNMP traps 

Requirements SNMP traps 

Configure MonitorMagic SNMP traps 





Escalation 


SNMP trap message contents 

To specify the contents of the SNMP Trap message, edit an existing SNMP trap alarm action or 

create a new SNMP trap alarm action. You can specify in the message tab the exact descriptive 

message string that will be send as part of the SNMP trap. Use this message to explain/describe 

the reason for sending the trap. An SNMP manager application can display this message, or act 

on its contents. 

149


See also: 

SNMP Trap message detailed contents 





Escalation 



Start or stop service(s) 

Manage services 

You have several options to start, stop, and manage other services as an alarm action. The 

procedures are different when the rule is part of a service monitor and when it is not. To specify 

manage services alarm action, edit an existing 'Start or stop service(s)' alarm action or create a 

new 'Start or stop service(s)' alarm action. 

When the alarm action is part of a rule of a service monitor you have the option to manage the 

associated service or other services as shown in the figure below: 

150


Start service (and all dependent services) 

Select this option if you want to start the target service and all dependant services. If the alarm 

action is not part of a rule of a service monitor this option is not available, since there is no target 

service. 

Restart multiple services (specify services in list below) 

Use this option to stop and start all services listed in the field Service list. If the services are 

running, they will be stopped first. 

Stop service (and all dependent services) 

Select this option if you want to stop the target service and all dependant services. If the alarm 

action is not part of a rule of a service monitor this option is not available, since there is no target 

service in this case. 

Stop multiple services (specify services in list below) 

Select this option if you want to stop one or more services for this alarm action. Specify the 

services in the list Service list. 

Add, Delete 

Use the Add or Delete buttons to add or delete services from the list Service list. 

151


Options 

Wait for ... seconds between consecutive service actions 

If you start and/or stop multiple services you might want to wait some time between each service 

action. This is useful in ensuring that various groups of services (SQL, Exchange) operate 

properly. 

See also: 





Escalation 


Terminate process 

Terminate process 

There are three options you can use to terminate a process. The procedures are different when 

the rule is part of a process monitor and when it is not. To specify the terminate process alarm 

action, edit an existing terminate process alarm action or create a new terminate process alarm 

action. 

You will be shown the following window: 

152



Terminate target process - all process instances with process name 

The target of this action is taken from the process specified in a Process monitor. If the 

computer has multiple processes (instances) running with the same name as the process 

monitor, all the processes with this process name will be terminated. 

Terminate target process - target process instance only 

The target of this action is taken from the process specified in a Process monitor. The process 

monitor corresponds with exactly one process (if the process is running). This process is 

identified by the process name and process ID. Note that multiple processes with the same name 

but different process ID's can exist on the computer. If you select this option, only the target 

process will be terminated. 

Find out how to create a Process monitor: 





Terminate specified process of target computer: 

153


The target of this action is not taken from the process(es) specified in a Process monitor. A 

Process monitor can contain settings to monitor multiple processes and you may not want to 

terminate all the processes contained in a monitor when it becomes triggered, this is when you 

would select this option. It is also possible that you may want to terminate a process on a 

machine other than the one being monitored, you would use this option under those 

circumstances as well. 

To select the target computer, and process to terminate, select the radio button and click the 

button. You will then see the following: 

Computer 

The name of the computer currently used to find the processes shown in the Available 

processes list. 


Refresh 

Press to update the Available processes list with the processes found on the computer specified 

in the field Computer. 

Available processes 

The list of processes from which you can select processes. 

Add -> 

Press this button to add the selected processes from the list containing Available processes to 

the list containing the Selected processes. 


The list containing the currently selected processes. 

OK 

Press to accept the list containing the currently Selected processes. 

Cancel 

Press to ignore any changes made to the list containing the Selected processes. 

See also: 





Escalation 


Shutdown or reboot computer 

Shutdown or reboot computer 

There are two options you can use to specify the shutdown or reboot computer alarm action, the 

procedures are different when the rule is part of a monitor and when it is not. To specify the 

shutdown or reboot computer alarm action, edit an existing shutdown or reboot computer 

alarm action or create a new shutdown or reboot computer alarm action. 

There are a few different options you have as to how the target computer is shutdown or rebooted. 

They can all be seen in the figure below: 

155


Target Computer: 

Target computer of corresponding monitor: 

Selecting this option does exactly what it says it will do. When a monitor policy is applied to a 

machine and a rule is triggered that invokes this alarm action, the computer that the monitor 

policy has been applied to will be shutdown or rebooted. 

Specified computer(s): 

By selecting this option you can shutdown or reboot a computer other than the one that the 

monitor policy containing this alarm action has been applied to. To specify another computer to 

be shutdown or rebooted click the button. Once you have done that you will be presented 

with a browse network tree where you can navigate to, and select, the target machine. You may 

also specify the target by typing in the name of the machine, or you can type in multiple machines 

by separating the machine names with a comma. 

Shutdown computer timing: 

...immeadiately: 

If you selected this option the target machine will be shutdown or rebooted as soon as a rule is 

triggered that invokes the shutdown or reboot computer alarm action. 

156


...in XXX seconds: 

By selecting this option you can delay the shutdown or reboot of the machine for the number of 

XXX seconds specified. If you chose a value of 120 seconds the machine would be shutdown or 

rebooted 2 minutes after a rule is triggered that invokes the shutdown or reboot computer alarm 

action. If you check the "Show additional information at target computer" checkbox you can 

display a text message at the target machine before it is shutdown or rebooted. Specify the text 

you want displayed before shutdown or reboot in the "Info" field. 

Unsaved application data: 

...force shutdown: 

By forcing a computer to shutdown, a user who may be working on the machine, at the time of 

shutdown, can lose unsaved work in any open applications. This is because most applications 

only write changes in open files to disk when the user has selected save, otherwise the changes 

to open files reside in memory, whose contents are cleared upon shutdown. It is highly 

recommended that you use the "....in XXX seconds" or "ask the user to close applications" 

shutdown or reboot option on machines that users work on daily. 

...ask user to close the applications: 

By selecting this option the computer may not shut down at all because you are relying on your 

user(s) to save their work and close open programs. There is no guarantee that users will comply 

with this request. Especially if they are away from their desk. 

Reboot options: 

Restart after shutdown: 

By selecting this option the target computer will be rebooted when a rule is triggered that invokes 

the shutdown or reboot computer alarm action. 

Do not restart: 

By selecting this option the target computer will not be rebooted when a rule is triggered that 

invokes the shutdown or reboot computer alarm action. 

Test options: 

See Test computer shutdown for more information. 

See also: 





Escalation 


Test computer shutdown 

Before you rely on MonitorMagic to shutdown or reboot your machine it is a good idea to test this 

functionality first. The shutdown or reboot alarm action may not work for one of two reasons: you 

are trying to shutdown or reboot a machine with an AT power supply or the MonitorMagic service 

does not have the permission to successfully execute the alarm action. 

157


AT power supplies do not use the motherboard's logic to power on or shutdown a machine. This 

type of power supply uses a button or switch, directly connected to the power supply, that is 

snaked from the power supply to the front of the case. Once a machine with an AT power supply 

has been powered on the motherboard's logic can restart (reset) the machine. This means that if 

your machine has an AT power supply MonitorMagic should be able to restart it, but most likely 

will not be able to shut it down completely. 

MonitorMagic's ability to shutdown or reboot a machine is dependant on the machine that is 

processing the alarm action, and the MonitorMagic service account it is using. If you want your 

workstation to process the shutdown or reboot alarm action, the account the service is using must 

have administrative rights on the target machine, the MonitorMagic service does not need to be 

running or installed on the target machine. This means that if the account the MonitorMagic 

service is using is a local account, the service will not be able to shutdown or reboot a remote 

machine, only the local machine. 

To use the Test computer shutdown feature you must click the "Test..." button which is on the 

bottom of the Shutdown or reboot computer dialog box. Once the test button has been clicked 

you will see the following interface: 

Target computer: 

The machine specified here is the one that should be shutdown or rebooted. You can specify 

what machine this should be by typing in the name of the machine or by using the 

button. If 

you choose to use the button you will be presented with a browse network tree where you 

can navigate to, and select, the target machine. 

MonitorMagic service: 

Only a machine that runs the MonitorMagic service can be specified here. The MonitorMagic 

service, which runs on the specified machine, will process the shutdown or reboot alarm action. 

You can specify what machine this should be by typing in the name of the machine or by using 

158


the button. If you choose to use the button you will be presented with a browse 

network tree where you can navigate to, and select, the target machine. Remember, the account 

the MonitorMagic service is using must have administrative rights on the target machine, 

otherwise the MonitorMagic service will not be able to shut it down. 

See also: 





Escalation 


Pre-defined Policies 

Pre-defined Policies 

MonitorMagic ships with several pre-defined policies. These policies contain application-specific 

monitors and rules to enable monitoring at application level. Each pre-defined policy is built to 

monitor a specific application or event. For instance, pre-defined policies can be used to monitor 

Exchange 5.5/2000, network services or user logon events. 

Pre-defined policies are based on real-life situations and contain certain thresholds. These 

thresholds are chosen for average sized networks, and can be customized freely. 

Most pre-defined policies do not contain alarm actions, except in the case of application or 

system service failures. Pre-defined policies which contain service monitors, such as the World 

Wide Web Publishing Service in the case of Internet Information Services, include rules to 

automatically restart the service. 

You can add custom alarm actions to pre-defined policies by expanding a policy-tree to its rule, 

then right-click on the default alarm action and select Add alarm action. 

Pre-defined policies are available for the following applications and events: 

Microsoft Exchange Server 5.5 

Microsoft Exchange Server 2000 

Microsoft SQL Server 7.0 

Microsoft SQL Server 2000 

Microsoft Windows 2000 Terminal Services 

Microsoft Internet Information Services 5.0 

Windows Network Services (DNS, DHCP, WINS, TCP/IP, RAS) 

User logon failures (account disabled/expired/locked, netlogon errors, password 

expiration) 

Service logon failures 

CPU performance 

Internal memory performance 

Policy changes 

See also: 



159




Application specific policies 

Microsoft Exchange 5.5 

MonitorMagic contains a pre-defined policy for Microsoft Exchange 5.5. This policy contains 

monitors for Exchange-specific services, events and performance counters. Each monitor 

contains thresholds based on average sized networks. 

Service Rules: 

Microsoft Exchange Directory must be running (automatic) 

Microsoft Exchange Event Service must be running (automatic) 

Microsoft Exchange Information Store must be running (automatic) 

Microsoft Exchange Message Transfer Store must be running (automatic) 

Microsoft Exchange System Attendent must be running (automatic) 

These service monitors contain rules and alarm actions to make sure the service is restarted in 

case of failure. 

Event Rules: 

Application log events with Exchange errors 

This event monitor contains rules to filter the application log for Exchange errors. You can add a 

custom alarm actions to these rules. 

Performance Counter Rules: 

Average Delivery Time must be greater than 10 

Send Queue Size must be greater than 5 

Send Queue Size (private) must be greater than 10 

Work Queue Length must be greater than 5 

These performance counter monitors contain rules with thresholds. These thresholds can be 

used to determine a decrease in service and performance. You can add custom alarm actions to 

these rules. 

See also: 





Microsoft Exchange 2000 

MonitorMagic contains a pre-defined policy for Microsoft Exchange 2000. This policy contains 

monitors for Exchange-specific services, events and performance counters. Each monitor 



Microsoft Exchange Event must be running (automatic) 

Microsoft Exchange IMAP4 must be running (automatic) 

Microsoft Exchange Information Store must be running (automatic) 

Microsoft Exchange MTA Stacks must be running (automatic) 

Microsoft Exchange POP3 must be running (automatic) 

Microsoft Exchange Routing Engine must be running (automatic) 

160


Microsoft Exchange Site Replication Service must be running (automatic) 

Microsoft Exchange System Attendent must be running (automatic) 



Event Rules: 

Application log events with Exchange errors 

This event monitor contains rules to filter the application log for Exchange errors. You can add a 



Average Delivery Time must be greater than 10 

Send Queue Size (mailbox) must be greater than 10 

Send Queue Size (public) must be greater than 5 

Work Queue Length must be greater than 5 



these rules. 

See also: 





Microsoft SQL Server 7.0 

MonitorMagic contains a pre-defined policy for Microsoft SQL Server 7.0. This policy contains 

monitors for SQL Server-specific services, events and performance counters. Each monitor 



Distributed Transaction Coordinator must be running (automatic) 

MSSQLServer must be running (automatic) 

SQLServerAgent must be running (automatic) 



Event Rules: 

Application log events with SQL Server errors 

This event monitor contains rules to filter the application log for SQL Server errors. You can add a 



SQL Server Percent Log Space Used must be greater than 75% 

SQL Server Cache Ratio must be smaller than 80 

SQL Server Lock Memory must be greater than 160kB 

SQL Server User Connections must be greater than 255 



these rules. 

See also: 


161





Microsoft SQL Server 2000 

MonitorMagic contains a pre-defined policy for Microsoft SQL Server 2000. This policy contain 

monitors for SQL Server-specific services, events and performance counters. Each monitor 



Distributed Transaction Coordinator must be running (automatic) 

MSSQLServer must be running (automatic) 

SQLServerAgent must be running (automatic) 

Microsoft Search must be running (automatic) 

MSSQLServerADHelper must be running (automatic) 



Event Rules: 

Application log events with SQL Server errors 

This event monitor contains rules to filter the application log for SQL Server errors. You can add a 



SQL Server Percent Log Space Used must be greater than 75% 

SQL Server Cache Ratio must be smaller than 80 

SQL Server Lock Memory must be greater than 160kB 

SQL Server User Connections must be greater than 255 



these rules. 

See also: 





Windows 2000 Terminal Services 

MonitorMagic contains a pre-defined policy for Microsoft Windows 2000 Terminal Services. This 

policy contains monitors for Terminal Services-specific services and performance counters. Each 

monitor contains thresholds based on average sized networks. 


Terminal Services must be running (automatic) 

This service monitor contain rules and alarm actions to make sure the service is restarted in case 

of failure. 


Active Sessions must be greater than 100 

Inactive Sessions must be greater than 100 

Terminal Server Session % Processor Time must be greater than 90 

162


Terminal Server Session Errors must be greater than 99 

Terminal Server Session Frames must be greater than 90 

Terminal Server Session Output Errors must be greater than 99 

Terminal Server Session Private Bytes must be greater than 12MB 

Terminal Server Session Timeouts must be greater than 99 

Terminal Server Session Total Bytes must be greater than 90MB 

Terminal Server Session Transport Errors must be greater than 99 



these rules. 

See also: 






MonitorMagic contains a pre-defined policy for Microsoft Internet Information Service 5.0. This 

policy contains monitors for IIS-specific services, events and performance counters. Each monitor 



FTP Publishing Service must be running (automatic) 

IIS Admin Service must be running (automatic) 

Indexing Service must be running (automatic) 

World Wide Web Publishing Service must be running (automatic) 



Event Rules: 

Application log events with Internet Information Server errors 

This event monitor contains rules to filter the application log for Internet Information Server errors. 

You can add a custom alarm actions to these rules. 


ASP Request Queue must be greater than 30 

ASP Requests/sec must be greater than 180 

IIS % Processor Time must be greater than 95% for 2 minutes 

IIS Object Cache Flushes must be greater than 1000 

IIS Object Cache Hits must be less than 500 

IIS Object Cache Misses must be greater than 1000 

IIS Private Bytes must be greater than 32MB 

IIS Thread Count must be greater than 20 



these rules. 

See also: 





163


Windows Network Services 

MonitorMagic contains a pre-defined policy for monitoring Windows Network Services health. 

This policy contains monitors for specific services and events. Each monitor contains thresholds 

based on average sized networks. 


DNS Server must be running (automatic) 

This service monitor contain rules and alarm actions to make sure the service is restarted in case 

of failure. 

Event Rules: 

DHCP Event Errors 

RAS Event Errors 

TCP/IP Event Errors 

WINS Event Errors 

This event monitor contains rules to filter the event log for network services errors. You can add a 


See also: 





User Logon Failures 

MonitorMagic contains a pre-defined policy for monitoring user logon failures. This policy contains 

monitors for specific events. Each monitor contains thresholds based on average sized networks. 

Event Rules: 

Account disabled 

Account expired 

Account locked out 

Logon time restriction violation 

NETLOGON errors 

Password expiration 

Unknown username or bad password 

Workstation restriction 

This event monitor contains rules to filter the event log for user logon errors. You can add a 


See also: 





Service Logon Failures 

MonitorMagic contains a pre-defined policy for monitoring user logon failures. This policy contain 


164


Event Rules: 

Service Logon Failures 

This event monitor contains rules to filter the event log for specific service logon failures errors. 

You can add a custom alarm actions to these rules. 

See also: 





CPU Performance 

MonitorMagic contains a pre-defined policy for monitoring CPU performance. This policy contain 

monitors for specific performance counters. Each monitor contains thresholds based on average 

sized networks. 


CPU Load (all instances) must be greater than 90% 

This performance counter monitor contains rules with thresholds. These thresholds can be used 

to determine a decrease in service and performance. You can add custom alarm actions to these 

rules. 

See also: 





Internal Memory Performance 

MonitorMagic contains a pre-defined policy for monitoring internal memory performance. This 

policy contain monitors for specific performance counters. Each monitor contains thresholds 

based on average sized networks. 


Committed Bytes must be greater than 90MB 

Pages/sec must be greater than 95 



these rules. 

See also: 





Policy Changes 

MonitorMagic contains a pre-defined policy for monitoring policy changes. This policy contain 


Event Rules: 

165


Policy Change Event 

This event monitor contains rules to filter the event log for specific events. You can add a custom 

alarm actions to these rules. 

See also: 





Reporting 


With MonitorMagic you can create reports from the information that is stored into a database. You 

can present this information in any way you like. 

The reporting process is as follows: 

A. The MonitorMagic service collects the data from the computers according to a report profile (at 

a in the report profile defined time) 

B. The MonitorMagic service saves the data into the database tables. 

C. After that the information can be retrieved from the database to create the report. 

166


In the menu option Configure report data collection you can define which information is stored 

in the database and which information will be retrieved: history data, specific logs (application, 

system, security). 

The user can define when the information must be collected and how and when it must be stored 

in the database. 

You can create a report for the computers or types of computers (mail server, workstation, 

file&print server) in your network or domain. 

The basic steps to generate a report are: 

1. Install MonitorMagic (you probably already did that), see Setup MonitorMagic. 

2. Install and configure the MonitorMagic Service, see configuring the MonitorMagic service. 

3. Create and configure a database for storage. See Database - Introduction. 

3. Configure MonitorMagic so that data is stored in the database. 

4. Select menu item Report - Configure Report Data Collection from the menu. Create a report 

profile in which the data collection is defined. Specify the information you want to collect, the time 

you want to collect it and the computers you want to collect it for. 

5. In the report tree, on the left of your window, you will see the available report templates. Open 

one of the predefined report templates. Generate a report, select report - generate report from 

the menu. 

The report will be presented. 

See also: 


Reporting - Manage report profiles 

Reporting - Report profile data storage 

Reporting - Collecting log information 

Configure report E-mail distribution 

Report data collection 

Reporting - Report profiles 

MonitorMagic uses report profiles to collect report data. A report profile specifies the following: 

 

 

 

the type of report data that must be collected, e.g. event log, services status information, 

performance counters. 

the computer(s) for which the data must be collected according to the report profile. 

when the data must be collected. 

In a network often there are a number of computers with the same role, e.g. there are file and 

print servers, mail servers, workstations. For computers with the same role you would like to 

generate reports with the same contents and the same layout. Report profiles are created to do 

that. In report profiles the contents en layout of the report are defined. For Monitor data you can 

create a different type of report than for the event log data. 

Report profiles are maintained and stored by the MonitorMagic service. Each MonitorMagic 

service can have different report profiles. To manage a report profile, you must be connected to 

the MonitorMagic service that maintains the report profile. So a single MonitorMagic service can 

collect, maintain and store report data for many computers. The same MonitorMagic service can 

use different report profiles. To collect report data from a computer, you do not need to run the 

MonitorMagic service on that computer. So all reports can be managed from one computer 

and only on that computer you need to run the MonitorMagic service. 

167


Timing data collection and storage in MonitorMagic 

In MonitorMagic Reporting it is possible to define for what time or for what period the 

MonitorMagic service collects the report information and at what time the data is stored into the 

database. 

Example: the data can be collected every 5 minutes during working hours and delivered to the 

database at night. 

See also: 






To manage report profiles, connect to a MonitorMagic service and select menu option Report, 

Configure. Make sure you have selected a computer in the network browse window. You will be 

presented the following Report profiles window: 

Report profiles 

The list shows the report profiles maintained by the connected MonitorMagic service and the 

computers that are assigned to each report profile. 

Add - Edit - Delete 

Use these buttons to manage the report profile selected in the list Report profiles. See Reporting 

- Collecting report information for more information. 

Computers 

168


A report profile can contain one ore more computers. For these computers, the MonitorMagic 

service will collect report data according to the report profile. Note that you do not need to run 

the MonitorMagic service on each of these computers. If a report profile does not contain any 

computers, no data will be collected for the report profile. To manage the computers assigned to 

a report profile, select the profile and press the Computers button. 

In the example above in the report you will find information about EARTH - JUPITER according to 

profile definitions in "Exchange", AMSTERDAM according to profile definitions in "File & Print 

server" etcetera. 

Storage 

The MonitorMagic service normally stores the collected report information in the MonitorMagic 

database. See Database - Introduction how to setup the MonitorMagic database. For various 

reasons, you may want to store the collected report data in a local file first and deliver the data to 

the database on a scheduled basis. Press the Change button to specify these settings. Note that 

the storage settings apply to all report profiles maintained by the MonitorMagic service. 

See also: 






You can configure how and when the collected report data must be stored in the MonitorMagic 

database. For various reasons you might choose not to store the report data in the database 

immediately once it has been collected. To name a few: 

 

 

 

when the database is not available the data is stored in a temporary file and delivered to 

the database later on, at a time that is defined by the user; 

report data is collected during the day and you do not want to use the database 

connection during the day; 

to limit bandwidth usage during daytime, you might want to store the report data in the 

database at night time. 

MonitorMagic supports the following option: 

169


Store collected report data in the database immediately 

This is the default option. All collected report data will be stored in the database immediately. This 

option is commonly used when the database is always available. 

If the database is not available, try again according to the scheduler 

If you select this option, the collected report data will be stored in a temporary file when database 

storage fails, e.g. when the database is not available. The data in the file will be delivered to the 

database according to the Scheduler. Only when all file data is successfully stored, the file will 

be deleted. Otherwise, the MonitorMagic service will retry to store the file data in the database 

according to the scheduler, in the example at 03:15. 

Store collected report data in local files first. Deliver the data to the database according to 

the scheduler 

When the report data is collected, the data is not stored in the database immediately. Instead it is 

stored in a local file. The data in the file will be delivered to the database according to the 

Scheduler. Only when all file data is successfully stored, the file will be deleted. Otherwise, the 

MonitorMagic service will retry to store the file data in the database according to the scheduler, in 

the example at 03:15. 

See also: 





Reporting - Overview window 

The Report configuration overview window shows detailed information regarding the collection 

of report data. To open the window, select the main menu option Report, Overview report data 

collection. The window automatically synchronizes with connected MonitorMagic services. For 

each connected MonitorMagic service, the window contains a single line for every possible report 

profiles combination of 

computer for which report data is collected 

170


 

 

type of report data collected 

the report profile 

The window contains specific information that will be shown in the bottom half of the window. This 

information will be shown for the selected item only. For all systems the following information will 

be presented: 

general info about profiles, the service that executes the reporting, the type of reporting 

data and computer for which the report is generated. 

data collection status: last data collection starting point and completion time 

data storage status: if applicable the data storage starting point and completion time 

Different types of log information will be presented as well. The following logs will be presented: 

application log: the number of collected records (between brackets the total number of 

records in the computer log), starting point, completion time and the number of collection 

errors 

security log: the number of collected records, starting point, completion time and the 

number of collection errors 

system log: the number of collected records, starting point, completion time and the 

number of collection errors 

For a server the following extra information is presented: 

Directory Service log: the number of collected records, starting point, completion time 

and the number of collection errors 

DNS service log: the number of collected records, starting point, completion time and 

the number of collection errors 

File Replication log: the number of collected records, starting point, completion time and 

the number of collection errors 

171


The following functions are available for the window: 

print the content of the window. Right mouse click and select the menu option print. 

configure columns shown in the window, right mouse click and select the menu option 

columns, the available columns are presented, they can be put in any order you like and 

you can select any column to be presented in the configuration overview. 

172


See also: 





Reporting - Data collection 

Reporting - Collecting report information 

MonitorMagic can collect report information of the following types: 

 

 

 

 

 

event logs 

disk information 

performance information 

ping response times 

SNMP get information 

The event log information is collected according to a report profile. The other information about 

computers in the network is collected by use of monitors. For predefined monitors see the 

Policies tree of MonitorMagic. 

It is not mandatory to store monitor data into the database. However, if you want to use monitor 

data for reporting purposes, then you will have to store monitor data. See Database - Monitor 

data. Monitor data will be stored in the same database as the event log data. 

See also: 



173






To specify the type of information that must be collected for a report profile, press the Add or Edit 

button in the Manage report profile window. You will be presented the following window: 

No logs - All logs - Specific logs 

Specify the logs for which report data must be collected. If you select All logs, the MonitorMagic 

service will determine the event logs that exist on the computer each time the data is collected. If 

you select the option Specific logs, you must specify the logs by using the Add and Delete 

buttons. 

Old records - include old records 

Select this option if old events must be archived as well. If you select this option, all events found 

in the specified event logs will be archived when the data is collected according to the profile. 

From then on, only the new events will be archived. 

174


Log actions - Clear log when records read 

Select this option if the MonitorMagic service must empty the log on the computer once it has 

been archived. 

Scheduling 

Specify when the event logs must be archived according to this profile. If you want to archive 

immediately, select the option Get report log information now. This operation is done only once 

so if you want to do it again you have to select this option again. 

See Scheduling overview. 

See also: 






Report generation 

Reporting - Overview report templates 

A report template is a collection of definitions of what should be contained in a report and how it 

should be presented. An average report usually contains a title, some text to explain the contents 

of the report and one or more tables in which information from the databases is presented. 

When you want to create a template, select (mouse click) the folder you want to put the template 

in. You can add a new template to that folder in the following ways: 

select report - report builder - create report template from the menu. 

right click the mouse and select create report template. 

When the template is filled with the necessary information it can be executed by "generate 

report". The MonitorMagic service will generate the report and the report will be presented in a 

new window. 

In the Reports tree the available templates are presented. You will find predefined templates that 

are already in there. Your newly created templates will be added to this tree. By using copy and 

paste the existing templates can be copied and modified. 

See also: 




Reporting - Report template tree 

Reporting - Generate a report 


There are three trees presented in MonitorMagic: the network tree, the policies tree and the 

report tree. These trees are loaded when MonitorMagic is started. This section describes the 

report tree. 

The report tree is created so that the user can put types of reports in separate folders. 

175


All the available report templates are presented in the reports tree. These templates are saved in 

the templates folder. Default that is the Report Templates in the MonitorMagic folder of your 

installation. Use the menu option file - save as... to save the templates, file - save will save it in 

the default template folder. This tree will be loaded every time MonitorMagic is started. 

When a template is saved it is saved completely with all elements, items, variables and properties. 

The templates can be put into folders in MonitorMagic. In the menu reports - create report 

folder or by right mouse clicking in the report tree a new folder can be created. Putting folders 

into folders is also an option. Just select the folder you want to put your new folder in and create 

the new folder. 

To create a new template using an existing one is easy: just copy an existing template, paste it 

in the same or in another folder and modify it. When you save the newly created copy it will get a 

different name than the original. To create a template, check out the report builder. 

Besides creating templates it is also possible to import existing templates that are not already in 

the tree. Choose report - report builder - import report template from the menu. 

See also: 






176



The actual generation of the report is easy. There are three ways to do this: 

select the template in the reports tree and right click the mouse and select generate 

report. 

double click the template in the reports tree. 

open the report template and select report - generate report from the menu. 

In the report template the way the report is generated is stored. Everything else is embedded in 

the template as well, including pictures, fonts etcetera. 

The reports will be created by the service you selected. See the Service tab in the Report 

Template Properties. 

See also: 






Reporting - Importing report templates 

You can import a report template by selecting report - report builder - import report template 

from the menu. You will be presented with an ordinary "open" window. Find the template you 

want to add to the template directory. When you save this template it will become a part of the 

template directory and come up every time you start MonitorMagic. 

There is a distinct difference between open a report template and import a report template. 

Open a report template will make a certain template that is in your report tree available for 

modification and report generation. In other words: you can use it. 

Import a report template will get a template from disk that is not yet in your report tree. To be able 

to use this you will still have to open it. 

See also: 






Report builder 

Reporting - Building a report template 

With the report builder all the definitions of the report elements that will be stored into the report 

template are defined. 

177


If you start building a report from scratch than select report - report builder - create report 

template. You will get the following window in which you should define a name that describes the 

contents of the template and that can be recognized in the template tree where it will be placed. 

A report template contains the following elements: 

Report Items 

Report Variables 

Before you start creating an item or a variable open the template in which you want to place the 

item. Select the template in the report template tree and select from the menu report - report 

builder - open report template, or right click the mouse on the template and select open report 

template. 

In the next help pages we'll explain Items and Variables. 

See also: 





Reporting - Items and variables 


A report template contains the following elements: 

Report Items 

Report Variables 

In Report Items parts of the report are defined. The following items can be created: text, tables, 

graphic elements and subreports. The order in which the report items are put into the template 

will define the order in which it will be presented in the report. The report consists of several 

report items that will be shown in the order they are put into the template. The following types of 

report items can be created: 

Text, e.g. headers, copyright, various text 

Tables containing queries from database tables 

Graphic elements, e.g. pictures, logos, empty lines 

Subreports 

178


A Report Variable is a variable part of the report template and can be used in report items. 

Variables that are defined in the template can be used in any of the report items. These variables 

are global variables. You can also define local variables inside one of the report items. If you do 

that you can not use them in other report items. 

Variables can be: 

"user input variables" like time, date, period which can be defined by the user when the 

report is created 

queries which can be used in any of the report items but will mostly be used in the tables. 

Variables will only be used in the report when they are used in the report items. 

Variables can also be used (nested) inside other variables. This will give you innumerous 

variations in making the report. 

Elements that are often defined in variables: 

Computer name 

Date, time, period 

They can be "user input variables" like time, date, period which can be defined by the user when 

the report is generated and they can be queries which can be used in any of the report items, but 

will mostly be used in the tables. 

Each item and variable should have a distinctive name which can easily be recognized in the list 

that is shown in the template window. 

179


When you select a report item in the template window and right click and select Item Properties 

you will see the properties of the selected item 

See also: 






Reporting - Report item text 

The report item text can be used to show text in your report. You can start your report with a title, 

put in some explanations about the report, explain the tables and other parts of the report. 

Before you start creating an item open the template in which you want to place the item. Select 

the template in the report template tree and select from the menu report - report builder - open 

report template, or right click the mouse on the template and select open report template. 

To create a text item select report - report builder - add report item - text... from the menu. 

The Report item text window will pop up. 

180


Select a name for this item. Use a name that you will recognize later on and that someone else 

(e.g. your colleagues) will recognize later on. In the description default the text of the report item 

will be copied, but by deselecting "description equals text of item" you can put in your own 

description. 

In the text variables that are created variables can be used. In the 

example %DATE_TIME_NOW% is a time-date variable, see Reporting - Report variable timedate 

value specification 

For creating variables check out the report variables. 

The text can be presented using different font styles and colors. It can be aligned (left-centerright) 

and a left margin can be defined. 

See also: 






181


Reporting - Report item table 

The report item table can be used to present information that is stored in the database and that 

can be presented in a table using ordinary database queries. 




To create a table item select report - report builder - add report item - table... from the menu. 

The "Report item table" window will pop up. 

You can give the table a distinct name and the description can be either the query contents or a 

description of your own. 

If you want to present data from a large database you do not always want to see all the data in 

the table. At the bottom of this window the number of output rows can be limited. If you define a 

table limited to 200 rows, then only 200 rows from the database will be presented in the table. 

Which values will be presented (e.g. the first or the last 200) is defined in the query (see the 

"order by" line in the picture below). 

If you want to limit the size of the table presentation on the report then select table formatting. 

In this query example a couple of variables are used that were already defined, presented 

between %%. See also report variable query for an example of how the variable %COMPUTER% 

was created. 

The result of this query will be a table per computer with a list containing the number of log errors 

per source which were counted by count(*). 

See also: 





182



Reporting - Report item table formatting 

In report item table formatting, which could be selected in report item table, the layout of the 

table can be defined. 

The following options can be set: 

The size of the columns can be changed by autosizing, the width of the column is 

adjusted to the largest value in size in the column. 

The height of the table rows can be limited to show all table rows. This to avoid an empty 

space in the table if there are less data rows than table rows. 

If there is no data available a default text can be presented. 

The height of the table can be defined in number of rows. If the hight of the table is 

smaller than the number of rows in it (see report item table) then there will be a scrollbar 

at the right side of the table. 

The left margin of the table can be set in pixels. 

An image can be selected to put in front of each row. 

A font style can be selected, see also Report template properties - Font styles. 

183


Example: 

Suppose you defined a maximum number of output rows to 200 and now you define the number 

of rows that will be presented to 40, then a table of 40 rows high will be presented with a scroll 

bar you can use to see the other 160 values that are in the table. 

See also: 






Reporting - Report item subreport 

Before you start creating an subreport open the template in which you want to place the subreport. 

Select the template in the report template tree and select from the menu report - report builder - 

open report template, or right click the mouse on the template and select open report template. 

184


To create a subreport item select report - report builder - add report item - subreport... from 

the menu. The "Report item subreport" window will pop up in which you can specify a name and a 

description for this subreport. 

A subreport can be regarded as a folder within the template: a subreport template. A subreport 

can contain its own set of report items and variables. You can put in a title, a piece of text, a 

picture and a table as if it were a normal template. 

Subreports are useful to keep some order in the templates. You can create subreports in 

templates and put (nest) subreports into subreports, so you can organize your report as if it were 

a logical directory. This will result in a logical sequence of repeating parts. 

There is an extra feature regarding the use of variables: 

variables that are created in subreports can not be used in the rest of the template, but 

variables that are created in the (root of the) template can be used in the subreports !! 

This means that you can define global and local variables. How these can be used see 

Mulitivalue variables. 

The most important application of subreports is the possibility to repeat parts of the report for 

different variables. E.g. if you want to generate the same report for every computer in your 

network. This can be realized by defining the local variable %COMPUTER%. If you define this 

variable as "user input variable" then when you generate the report you will be asked for which 

computer you want to generate the report. If you define this variable as a "query input variable" 

then you can use this variable to generate a report for all computers in the network. See also the 

Multivalue Variables chapter. 

See also: 






Reporting - Multivalue Variables 

Reporting - Report item graphical element 




185


To create a graphical item select report - report builder - add report item - graphical element 

from the menu. The "Report item graphical element" window will pop up in which you can specify 

a name and a description for this subreport. 

You can give the graphical element a distinct name, e.g. "company logo" and a description. As a 

graphic element the following options can be selected: 

add a picture 

add a empty vertical space of ..... pixels 

create a page break (used for printing the report) 

At the bottom you will find the option start drawing next display item at the same position. 

When you want to make a header with a logo and the title beside it then: 

create a picture with start drawing next display element at same position, and 

create a text item with a big left margin or alignment center. 

See also: 






Reporting - Report item picture 

In the item specification of report item graphical element the picture option can be selected. 

This picture can be added by selecting the Add button. The following window will be presented: 

186


Find the picture on your computer and add it to the report. The picture will be embedded in the 

template, just like any other report item and variable. In the report picture screen a preview of the 

picture is shown. 

See also: 






Reporting - Report variable user input 

In MonitorMagic it is possible to define variables that the user can define, change or influence 

during report generation. The exact value of the variable will be defined by you, when you 

generate the report you will be asked to. 

187


In the predefined templates you can see some examples of how these variables can be used. 

There are three kinds of variable that can be created: 

 

 

 

Text: In a text variable you can define text that can be used anywhere in the report. See 

report text value specification. 

Time-period: In a time-period variable a period can be defined that can be used 

anywhere in the report. It can be used in report items and can be a welcome addition to 

queries, e.g. when you want to create a report for a certain period. You can also define a 

variable %COMPUTER% to define for which computers you get certain information in the 

report. See report variable period value specification. 

time-date: In a time-date variable a time can be defined. This is useful e.g. when you 

want to generate a report for a certain time, if you want to collect data for a certain time 

from the database or want to present the time the report is generated. See report variable 

time-date value specification. 

See also: 


188






Reporting - Report variable text value specification 

In MonitorMagic it is possible to define a text variable that can be used in report items. When you 

want to add comments to a report this is a handy option. This can be done in two ways: 

 

 

A specified value can be defined. Use of this text variable in one or more report items will 

result in presentation of that text at that location in the report that you defined. 

Ask user can be selected. Use of this text variable will result in the question "text 

variable?" during report generation. The description of the text variable will be the 

question during report generation. You can use this variable e.g. when you want to add 

comments to the report, which can be different every time you generate a report. Of 

course you can leave the field empty if you have no comment. You can also use text 

variables in tables, see Reporting - Report item table. 

It is also possible a text variable as a query, for that see report variable query. 

189


See also: 






Reporting - Report variable period value specification 

In period value variable a period can be defined. This is useful when you want to generate a 

report for a certain period of time or if you want to report database values over a certain period of 

time. 

This variable can be used in the following report items: 

in queries you can use them to define the period for which you want to present the data in 

the report 

in text items you can indicate for which period the report is generated, e.g. "This report 

was generated for %PERIOD%". 

190


This period variable can be defined in two ways: 

User specified values: if this option is selected the period has to be defined and will be 

used every time a report is generated. The same window report variable period 

specification will pop up. 

Ask user: if this option is selected the window report variable period specification will 

pop up when you generate the report. In this window the period can be defined. 

In the window "report variable period specification" the following options can be selected: 

fixed period: a calendar will pop up in which you can choose the starting and ending date. 

dynamic period: a list with period options will pop up (e.g. last hour, last day, last month). 

The MonitorMagic service will calculate the period from the moment now. 

See also: 






Reporting - Report variable time-date value specification 

In time-date value variable a time and date can be defined. This is useful when you want to 

generate a report for a certain time or if you want to report database values for a certain time. 

This variable can be used in the following report items: 

in text items you can indicate for which time the report is generated, e.g. "This report was 

generated at %TIME-DATE%". 

in queries you can use them to define the time for which you want to present the data in 

the report 

191


This time variable can be defined in two ways: 

Ask user: if this option is selected the window report variable date time value 

specification will pop up. In this window the time and date can be defined. 

User specified values: if this option is selected the time has to be defined and will be 

used every time a report is generated. The same window report variable date time 

value specification will pop up. 

192


In the window "report variable date time value specification" the following options can be 

selected: 

fixed period: a calendar will pop up in which you can choose the starting and ending date. 

dynamic period: a list with date-time options will pop up (e.g. now, one hour ago, a week 

ago). The MonitorMagic service will calculate the date-time from the moment now. 

See also: 






Reporting - Report variable query 

An important features of MonitorMagic is that information from a database can be presented in a 

report. Database queries are required to retrieve data from the database and put it in a report. In 

report item table is already shown how queries can be used to retrieve data from a database and 

put it in a report. 

It is possible to define queries as variables that can be used in report items. 

We will explain the use of the report variable query with a simple example. 

The next query will find all the computers for which information is stored in the table 

MonitorDiskDefinition. 

193


In the database the disk information is stored in the tables MonitorDiskData and 

MonitorDiskDefinitions. The query variable %COMPUTER% is now used to create a table in 

which the computers and their disks are presented. For that the following report item table is 

created: 

194


This table will result in a two lists with disks per computer. 

See also: 



195





Reporting - Multivalue variables - example 

An important feature in MonitorMagic is the use of multivalue variables. In this chapter we will 

show you how to make optimal use of variables. 

In MonitorMagic it is possible to use as many variables as you want within report templates, even 

within report items you can use more than one variable. This makes the reporting in MonitorMagic 

very flexible. You can create overviews per computer, per week, per resource, per processor, per 

error type, per whatever you want. 

We will explain the use of the multivalue variable with an example. For this example see the 

predefined template all systems overview per computer in the monthly overview folder in the 

template tree. For this example we copied and pasted this example to the computers overview 

folder and adjusted the contents to make the example simpler. 

In the example we want to create a report in which the disk space of the computers in the network 

for the months February and March will be presented. To get all the computers in the network we 

use the variable query %COMPUTER%. 

The next query will find all the computers for which information is stored in the table 

MonitorDiskDefinition. 

196


In the database the disk information is stored in the tables MonitorDiskData and 

MonitorDiskDefinitions. 

The query variable %COMPUTER% is now used in a report item table in which a query is used to 

get the correct disk information and put it in a table. We will not get into this query in detail, but 

this query will be repeated for every computer that will be found in the database using 

the %COMPUTER% variable. 

197


The result of the query will be two tables: one for computer EARTH and one for JUPITER for 

February and March. 

The announcement in the header is created by the following report item text: 

Report generation date: %INTERNAL_VALUE_REPORTGENERATIONDATE% 

Report includes information for 

months: %INTERNAL_VALUE_REPORTGENERATIONPERIOD% 

198


See also: 






Reporting - Report template properties - Name 

Open a report template. When you select View - Properties from the menu, or when you right 

click in the template and select report template properties you will get the properties of that 

specific template. 

On the name tab page the report template name, file name and file location are presented. The 

name can be changed. The file name and location can not be changed. 

199


See also: 






Reporting - Report template properties - Service 




The MonitorMagic service will perform the report generation. In this service tab page you can 

define which MonitorMagic service has to perform the report generation. 

These settings will be saved in the template when the template is saved by the menu option file 

save. 

200


There are three options: 

if a connection with one service exists use it, otherwise ask the user 

ask the user 

always use the same service: this can be any service in the network 

The first option is set default, when only one service is used the question "which service has to do 

it?" won't come up, it will pick the one that is up and running. If more than one service is running 

you can choose to ask for the service that has to perform the report generation or you can set a 

fixed service that will perform the report generation every time. 

See also: 






Reporting - Report template properties - Window margins 




The window margins tab page pretty much speaks for itself. The left and right side and top 

screen margins can be defined, in number of pixels. Also the vertical space between report items 

can be defined, again in pixels. 

201


See also: 






Reporting - Report template properties - Font styles 




In the Font styles tab page you can select a font style. In MonitorMagic a limited number of font 

styles are added, . In every report item one font style can be selected. The reason for this is to 

avoid a chaotic report layout with fonts that are not matching. 

A standard set of font styles is added which you can change. For most of the font styles Sans 

Serif is used. Select the font and press "edit" and you can select any font and any font size you 

want. If you want to restore the original set of font styles, just press "restore defaults". 

However, you can also use the 5 custom font styles and alter them to your own wishes. That 

way you would keep your font styles organized and keep the standard font styles in the same 

style, which is Sans Serif. If you choose to alter these anyway to your standard company font, 

then change all the font styles to the same font. 

202


See also: 






Reporting - Report template properties - Print header - footer 




On the Print header - footer tab page you can define the way the report will be printed, with a 

header and a footer in which you can use predefined variables. 

203


See also: 






Reporting - Event logs additions 

Reporting - Database tables for event logs 

Item Type Description 

TabIe: MmLog_EventRecord 

LogEventRecordId 

LogTimeGenerated 

LogTimeWritten 

int 

(primary 

key) 

Table stores all events, one row for each 

event. 

Identifies event, generated by MonitorMagic 

service. 

datetime Time when event was generated and submitted 

to the event log service. This time is measured 

in the number of seconds elapsed since 

00:00:00 January 1, 1970, Universal 

Coordinated Time. 

datetime Time when event was written to the event log. 

Time at which this entry was received by the 

service to be written to the logfile. This time is 

204


measured in the number of seconds elapsed 

since 00:00:00 January 1, 1970, Universal 

Coordinated Time 

LogEventId int Event identifier of the event. The value is 

specific to the event source for the event, and is 

used with the event Source to locate a 

description string in the message file for the 

event source. 

LogEventType int Type of event. This can be one of the following 

values 

0: Success 

1: Error 

2: Warning 

4: Information 

8: Audit success 

16: Audit failure 

LogEventCategory int Category for this event. The meaning of this 

value depends on the event source 

LogSourceId int Relates to MmLog_SourceName, SourceId. 

Text information that specifies the name of the 

event source. 

LogComputerId int Relates to MmGeneral_ComputerName, 

ComputerId. Text information that specifies the 

computer of the event message. 

LogUserId int Relates to MmLog_UserName, UserId. The 

name of the user account if applicable (e.g. not 

all event messages include a user account 

name). 

LogDescriptionId int Relates to MmLog_UserName, DescriptionId. 

Identifies the description of the event. 

LogLogId int Relates to MmLog_LogName, LogId. 

Identifies name of log of event message. 

LogMonitorMagicComputerId int Relates to 

MmGeneral_MonitorMagicComputer, 

MmComputerId. Identifies the computer 

running the MonitorMagic service that collected 

the event log message. 

Table: MmLog_SourceName 

SourceId 

SourceName 

int 

(primary 

key) 

nvarchar 

(64) 

Table stores all different sources found in 

all archived event logs 

Unique id of row, generated by MonitorMagic - 

database engine 

Relates to table MmLog_EventRecord, 

LogSourceId. Text information that specifies 

the name of the event source. 

Table: MmGeneral_ComputerName 

ComputerId 

int 

(primary 

Table stores all computer names that exist 

for all different report data tables 

Relates to MmLog_EventRecord, 

LogComputerId. Unique id of row, generated 

205


ComputerName 

key) 

nvarchar 

(64) 

by MonitorMagic - database engine 

Name of computer. 

Table: MmLog_UserName 

UserId 

UserName 

int 

(primary 

key) 

nvarchar 

(128) 

Table stores user account names that show 

up in event messages 

Relates to MmLog_EventRecord, LogUserId. 



Name of user account. 

Table: MmLog_Description 

DescriptionId 

Description 

int 

(primary 

key) 

nvarchar 

(255) 

Table stores all unique descriptions of all 

archived event logs 

Relates MmLog_EventRecord, 

LogDescriptionId. Unique id of row, generated 

by MonitorMagic - database engine 

Textual description (limited to 255 characters) 

Table: MmLog_LogName 

LogId 

LogName 

int 

(primary 

key) 

nvarchar 

(64) 

Table stores all log names of event logs that 

are archived 

Relates to MmLog_EventRecord, LogLogId. 



Name of event log 

Table: 

MmGeneral_MonitorMagicComputer 

MmComputerId 

MmComputerName 

int 

(primary 

key) 

nvarchar 

(64) 

Table stores names of computers running 

the MonitorMagic service/ 

Relates to MmLog_EventRecord, 

LogMonitorMagicComputerId. Unique id of 

row, generated by MonitorMagic - database 

engine 

Name of computer 

See also: 





Reporting - Sample queries for event logs 

Sample queries. These queries can be used in the report builder. 

206


Distribution of event types per machine shows how many errors, warning and info 

messages are in the eventlogs of various computers, ordered by eventlogtype. 

SELECT logeventtype,computername,count(*)As 'number of events' 

FROM mmgeneral_computername,mmlog_eventrecord,mmlog_description, 

mmlog_sourceName,mmlog_logname 

WHERE mmlog_eventrecord.logsourceid=mmlog_sourcename.sourceid 

AND mmlog_eventrecord.loglogid=mmlog_logname.logid 

AND mmlog_eventrecord.logdescriptionid=mmlog_description.descriptionid 

AND mmlog_logname.logid=mmlog_eventrecord.loglogid 

AND mmgeneral_computername.computerid=mmlog_eventrecord.logcomputerid 

group by ALL logeventtype, Computername 

order by logeventtype,computername 

Distribution of event types per machine and per eventsource 

SELECT sourcename,logeventtype,computername,count(*)As 'number of events' 

FROM 

mmgeneral_computername,mmlog_eventrecord,mmlog_description,mmlog_sourceName,mmlog 

_logname 


AND mmlog_eventrecord.loglogid=mmlog_logname.logid 




GROUP BY logeventtype,sourcename,Computername 

ORDER BY sourcename,logeventtype,computername 

Select all info of a certain computer from a certain time period, and a certain eventlog 

SELECT sourcename,logname,computername,description, 

LogEventRecordid,logtimeGenerated,logeventid,logeventtype,logeventcategory 

FROM mmlog_eventrecord,mmlog_Description,mmlog_sourceName, 

mmlog_logname,mmgeneral_computername 





AND mmgeneral_computername.computername='Pacific' 

AND mmLog_logname.logname='system' 

AND mmlog_eventrecord.LogTimeGenerated >'11/20/2002 9:00:00' 

AND mmlog_eventrecord.LogTimeGenerated


mechanism the reports can be send any time to any E-mail destination. The E-mail distribution of 

the reports is configured with 3 settings: 

The recipients of the report(s). All recipients will receive the same reports. 

The directory that contains the report templates of the reports that must be sent. Note 

that this directory must be accessible by the MonitorMagic service and that you need 

to copy the report templates you want to E-mail to this directory. 

The time(s) when the reports must be sent. 

Report E-mail distribution can be configured by selecting "Report", "Configure reports E-mail 

distribution...". The following window will be shown: 

To: 

Specify here the E-mail accounts (separated by comma's) to which the reports will be sent. 

Directory: 

Specify here the directory that contains the report templates from which the reports will be 

generated. The directory name must be relative to the MonitorMagic service. This means that the 

report templates must be copied to this directory on the computer that runs the MonitorMagic 

service. On the computer that runs the MonitorMagic user interface, the report templates can be 

found in :\Program Files\Tools4ever\MonitorMagic\ReportTemplates. You should not use 

the same directory for the MonitorMagic service. 

Scheduling: 

Specify here the time(s) when the MonitorMagic service will generate and send the report(s) by 

E-mail. See "Scheduling overview". 

Generate and send the reports now (test) 

Select this option to send the report immediately (when pressed OK). 

Note: 

E-mail(s) will only be sent when SMTP is configured correctly (see "SMTP E-mail setup") 

208


See also: 



MonitorMagic client 


The MonitorMagic client supports the following types of windows: 

Network browse window 


Control center 

Open a monitor window 

Graph window - Introduction 

3D Graphs - Introduction 


Global alarm window 


The network browse window is used to find computers in your network and you can select a 

number of menu options for these computers. The window is displayed in the tabbed network 

view window and the network window. To activate a browse window right click the mouse in the 

grey area of the MonitorMagic client application. Select menu option Network - policies to 

activate the tabbed window and Browse network to activate a browse window only. Note that 

you can access the same menu option from the main menu: View, Network - policies. 

209


You can customize the network browse window and create your own folders. These folders can 

contain computer and other folders. For more information, see Network browse window. 


The monitor policy window is used to create and manage monitor policies. To activate the 

monitor policy window, right click the mouse in he grey area of the MonitorMagic client application 

or activate the main menu option View. Select menu option Network - policies. The tabbed 

window contains a network browse window and the monitor policies window. At the bottom of the 

window, select the Policies tab. 

210


Monitor window 

A monitor window show the monitors maintained by the corresponding MonitorMagic service. 

To activate a monitor window, open the network browse window, select a computer that runs the 

MonitorMagic service. Right click the mouse and select menu option Open. The MonitorMagic 

client will connect to the MonitorMagic service running on the selected computer and show all the 

monitors in the window. 

See also: 





Window navigation 

211




You use the network browse window to find computers in domains, to access menu options, to 

open MonitorMagic monitor windows and for drag and drop operations. The network browse 

window shows a tree display similar to the tree used in the Windows Explorer and many other 

applicattions. By default, the network browse window allows you to search for domains and 

computers within domains. This is done by accessing the Network tree item in the network 

browse window. Within this tree item, the network domain and computer information is shown as 

obtained from various networking calls. Items that are contained in the Network tree item cannot 

be manipulated by users. 

In the network browse window, you can create your own folders. 

These folders can contain computers and other folders. By using 

drag and drop operations, you can build your own customized 

network browse tree. The tree structure is stored on disk. To start 

creating your own folder, right click the mouse outside the network 

tree item and select menu option New folder. 

You can use the following menu options to manage the network browse tree: 

New folder 

Create a new folder in the selected folder. If a computer item is selected, the new folder is 

inserted directly after the computer item. (not available in Network tree items) 

Add computer 

Add a computer item in the selected folder or directly after the selected computer item (not 

available in Network tree items) 

Add SNMP Host 

New in version 6.0 (1278) 

Adds an SNMP host to the tree. A SNMP host can be added in the new default folder "Manual 

SNMP Hosts". An SNMP host is defined by its IP-address and SNMP community string. When a 

SNMP policy is applied to such anSNMP host, the MonitorMagic service will use the IP address 

of the host for all SNMP queries in the policy, instead of the IP addresses specified in the policy 

itself. This way it is possible to make a single policy, without having to manually edit the policy for 

each host. 

Rename 

Rename the selected network browse tree folder. 

212


Refresh 

Reload the network data (available only in Network tree items) 

Delete 

Delete the currently selected items (not available in Network tree items). 

To copy computers from the Network tree items to custom folders you can use drag and drop 

operations. 

See also: 




Within the MonitorMagic client, you can display a number of different windows. Two different 

types of windows exist and they pertain to navigation and management. They are child and bar 

windows. 

Child window 

A child window is a window that can be place anywhere in the MonitorMagic client frame. The 

frame is the area of the screen within the MonitorMagic client application. The frame can cover 

the whole screen or part of the screen. You can apply the Tile and Cascade operations to the 

child windows. An example of a child window is the monitor window. Child windows cannot be 

docked and can never be positioned outside the MonitorMagic client frame. 

Bar window 

A bar window is a window with a smaller caption (title area). Bar windows can be docked. When 

you position a dockable window, it will automatically select a preferred location when you move 

the window. While you move the window a small border frame is shown. This makes it easy to 

position and move windows to desired locations. Examples of dockable bar windows are the 

network - policies window and the browse network window. 

213


To start docking a window, left click the mouse in the small title bar of the docking window and 

move the window with the mouse button pressed. While moving, a frame is shown. The 

appearance of the frame changes while you move the window. This reflects the way 

MonitorMagic will position the window if you release the mouse button. If you approach a border 

of the MonitorMagic client frame and release the mouse button, MonitorMagic will automatically 

dock the window at the border location. You can also position dockable windows outside the 

MonitorMagic client area. Note, you don't need to position (dock) a dockable window at a 

docked (border) location. See the figure below. 

214


See also: 






The MonitorMagic control center is shown (by default) at the bottom of the MonitorMagic frame 

window. The window shows the status of MonitorMagic services to which the MonitorMagic client 

is connected. From within the window you can control the MonitorMagic services. The entries in 

the window can be update automatically or manually. 

215


The control center window is shown by default. To hide or show the window select main menu 

option View, Control center. The control center window shows a single line for each 

MonitorMagic service it is connected. If the connection to a MonitorMagic service fails, the image 

at the beginning of the line turns red. When you setup a connection with a MonitorMagic service, 

a new line is added to the window automatically. 

Actions 

From the Control center you can execute a number of actions. You can execute most of these 

actions for a single or multiple computers. To start, select one or more computers and right click 

the mouse. From the menu select one of the following options: 

Action Description 

Open 

Setup 

service... 

Configure 

service... 

Open or activates the monitor window of the selected computer. 

Install, upgrade or delete the MonitorMagic service from the selected computers. 

Configure the MonitorMagic service on the selected computer. The configuration 

includes, service access rights, license code, SMTP E-mail, custom 

keywords, client update, SNMP traps, pager-SMS and database 

configuration. See Configuring the MonitorMagic service for more information. 

Configure Configure the MonitorMagic WebService. See Configure MonitorMagic 

WebService... WebService_General for more information. 

Delete Delete the MonitorMagic service from the selected computers. 

service... 

Refresh Refresh the information of the selected connected computers. Note that the 

information can be refreshed only if the MonitorMagic client is connected to 

the MonitorMagic service. If for whatever reason no connection exist, 

MonitorMagic will try to setup the connection. If succeeded, the information 

is refreshed. 

Disconnect 

Disconnect from the MonitorMagic service and remove this entry from the window. 

216


Properties 

If a monitor window is open for the computer, it will be closed. 

Specify how the information in for the selected computer(s) must be updated: on 

request or automatically. 

Columns 

You can configure the columns that are shown in the window. To add a column to the window, 

right click on the header of a column where you want to insert the new column. From the popup 

menu you can select the following columns: 

Column Description 

name 

Computer The name of the computer on which the MonitorMagic service runs and to which the 

MonitorMagic client is connected. The computer name is shown as a NETBIOS 

name. 

Status 

The status of the connection with the MonitorMagic service. This can be either 

Connected, Not connected, Connecting... 

Database The type and status of the database used by the MonitorMagic service. 

Database 

type 

Database 

status 

Web 

config 

Domain 

License 

status 

The type of the database used by the MonitorMagic service. 

The status of the (connection with the) database used by the MonitorMagic service. 

A description of the MonitorMagic WebService. Example: HTTP:81 means that the 

HTTP is enabled on port 81. 

The NETBIOS domain name of the connected MonitorMagic service. 

The status of the license code used by the MonitorMagic service. 

License A description of the license code used by the MonitorMagic service. 

# Monitors The number of monitors maintained by the MonitorMagic service. 

# alarm 

monitors 

# report 

profiles 

# report 

computers 

# E-mail 

report 

Update 

time 

Update 

mode 

The number of monitors that are in an alarm state (rule broken). 

The number of report profiles maintained by the MonitorMagic service. 

The number of computer for which the MonitorMagic service collects report data. 

The number of reports for which E-mail distribution is configured. 

The last time the information described in the current line was updated 

The mode used to update the information for this line. This can be either On 

request: The information if updated when the line is selected and refreshed (F5) or 

Interval: The information is updated automatically, every Interval seconds. 

Delete Delete the column at the current position. 

column 

To sort on a column, simply click the column header. 

See also: 





217




The Global alarm window presents summary information of alarm rules: The rules of monitors 

that are in an alarm state. The purpose of the window is to provide you with immediate and 

accurate information on alarm conditions of the computers that are monitored with MonitorMagic. 

Activating the Global alarm window 

The global alarm window is activated and de-activated with the main menu option View, Global 

alarm window. The window automatically updates the information of connected MonitorMagic 

services. 

Monitored computers 

The Global alarm window shows a single line for each computer that is monitored by 

MonitorMagic. A computer is monitored by MonitorMagic if at least one monitor maintained by a 

MonitorMagic service is monitoring something on the computer. Every computer, e.g. line can 

have one of two possible states: OK or Alarm. If the state is OK, no monitor with the computer 

being the target server has any rule that is in the alarm state. If the state is Alarm, one or more 

rules of monitors monitoring the computer are in an alarm state. 

Updating the Global alarm window 

The Global alarm window can be updated automatically, based on an interval refresh rate. To 

specify the update parameters, select the computer in the Network view window. Select menu 

option Computer, Configure service and select tab Client update. See Updating results for 

more information. Note that the updated information reflects the state of the monitors maintained 

by the MonitorMagic service, which does not necessarily correspond with the state of the 

monitored components: if you monitor a disk every hour and update the global alarm window 

every 5 seconds, the results will only change at most every hour and the information can be up to 

one hour old. 

Changing columns 

You can configure the columns that are shown in the alarm window by clicking the right mouse 

button on the header of the column you would like to change. The following columns are 

available: 

Status: 

The state of the monitored computer according to the defined monitors: 

OK: Not a single rule of a monitor monitoring the target computer is in an alarm state. 

Alarm: One (or more) rules of the monitors that monitor the target computer are in an alarm state 

Computer: 

The name of the target computer, e.g. the computer that is monitored. Note that this can be a 

different computer then the MonitorMagic computer. 

MonitorMagic server: 

The name of the computer that runs the MonitorMagic service and maintains and executes the 

monitors. Note that this can be a different computer then the target computer. 

Update time: 

The time the information in the global alarm window was last updated, e.g. refreshed and 

synchronized with the information of the MonitorMagic service. Note that this time is not the same 

time as the time the monitor was updated. 

Alarm count: 

The number of monitors that monitor the target computer and are in an alarm state. 

Monitor count: 

The number of monitors that monitor the target computer. 

218


Alarm description: 

The name of all rules (separated by comma's) that are in an alarm state. 

Sorting columns 

To sort on the displayed columns, simply click on the columns. Note that you can reverse the sort 

order by clicking on the same column. 

Note: If a computer is monitored by two MonitorMagic services and the application is connected 

to both of them, the Global alarm window will show two lines for the monitored computer, one for 

each MonitorMagic service. 

See also: 




Monitor window 


A monitor window shows the monitors maintained by the corresponding MonitorMagic service. 

To activate a monitor window, open the network browse window, select a computer that runs the 

MonitorMagic service. Right click the mouse and select menu option Open. 

219


The MonitorMagic client will connect to the MonitorMagic service running on the selected 

computer and show all the monitors in the window. 

See also: 


Monitor and rule area 

Columns of a monitor window 

Changing the columns of a monitor window 

Sorting the monitors in a monitor window 

Changing sort criteria and direction 

Highlighting new results 

Line display properties 

Updating results 

Logging information 



Each monitor window contains two areas, top and bottom. The top area shows the monitors. The 

bottom area shows the rules defined for the selected monitor. 

220


If you select another monitor in the top area of the window the rule area at the bottom is 

automatically updated. You can change the area reserved for monitors and rules by clicking and 

moving the left mouse button on the splitting border. 

In the monitor area the background color of a monitor can be changed to light red. This means 

that the monitor contains rules that are triggered. If you select such a monitor the rule area at the 

bottom will be updated. In the rule area the rules that are triggered will have a red instead of a 

green flag at the beginning of the line. 

See also: 











In a monitor window, you can display monitors of different types. Since the window contains 

columns and different monitor types have different columns, an additional header is shown if the 

next line show a monitor of a different type. When you select a monitor in the window, the 

headers at the top will change to reflect the columns of the selected type of monitor. 

To change the way the header lines are displayed, see Line display properties for more 

information. To change the columns that are displayed for each type of monitor, select the 

monitor window. Select the main menu option Edit, Display and select tab Columns. See 

Changing the columns of a monitor window for more information. 

See also: 




221









You can configure the columns that are displayed for each type of monitor by using the Display 

specification window. To activate this window, see Columns of a monitor window. Select the 

Columns tab in the window. 

This window shows the displayed columns for each type of monitor. 

Item type 

Use the drop-down box to select the type of monitor you want to configure the displayed columns 

for. When you change the selection the Available columns and Show columns lists will be 

updated. 

Available columns 

The list show the available columns of the currently selected type of monitor. 

Show columns 

222


The list contains the names of the columns currently shown for the currently selected type of 

monitor item. 

Use the Add and Remove arrow buttons to change the order and contents of the Show 

columns list. 

Automatically update column with 

If you select this option, the width of the columns will be automatically updated so that a columns 

contents can be shown completely. 

See also: 











You can sort the monitors displayed in the monitor window. You can sort all types of monitors and 

you can sort on multiple columns. To change the way the monitors are sorted, you can press the 

header of a column or use the Sorting tab of the Display specification window. 

Sort monitors by header 

The sorting of monitors is organized by the type of monitor. To change the way disk monitors are 

sorted, first select a disk monitor in the monitor window. The header texts of the monitor window 

will be updated to reflect the columns displayed for disk monitors. Left click the mouse on the 

header on which you want to sort. Click on the same header to change the sort direction from 

ascending to descending or vice-versa. If you click on another column header, this column will 

become the first sort criteria and the first clicked header column now is the next sort criteria. Note, 

you cannot sort on columns that are not displayed if you use this method. 

Sort monitors by window 

To change the sorting order and direction for each type of monitor use a configuration window, 

select the monitor window. Select main menu option Edit, Display, then select the tab Sorting. 

See Changing sort criteria and direction for more information. 

See also: 







223






You can configure the way the monitors are sorted for each type of monitor by using the Display 

specification window. To activate this window, see Sorting the monitors in a monitor window for 



Item type 

Select the type of monitor you want to configure the sorting order and direction for. When you 

change the selection, the lists Available data items and Sort on items will be updated 

automatically. 

Available data items 

The list shows the available values of the currently selected type of monitor. 

Sort on items 

The list shows the currently selected sort criteria. For each criteria the list show the name of the 

item and the sort order. The first item in the list represents the first sort criteria. If two monitors 

have equal values for this item, the next sort item applies. 

224


Use the Add, Delete, Up, Down, Arrow up, Arrow down buttons to change the sort criteria, 

sort order and sort direction. 

Automatically resort on update 

When you select this option, the monitors will be resorted each time the monitor data is updated. 

See also: 











In a monitor window you can highlight the most recent result. By using this feature you will find 

the most recent data values easily. Each time a monitor is updated the line corresponding with 

the monitor will be highlighted for a specified period of time. 

In the figure, the recent results are shown with a light blue background color. To change this 

option you can right the mouse in the monitor window and select the menu option display or 

select the Display menu option from the main menu, under edit. Select tab Line. 

See also: 







225






To change the fonts and colors of the lines displayed in a monitor window select the menu option 

Display from the main menu Edit. Select the tab Line, press the button Fonts and colors. 

The window shows a number of lines describing the type of line as shown in the currently 

configured settings. To change the font and colors of a certain type of line, select the line and 

press the Font, Background, Border color buttons to change the way the selected type of line 

is displayed. Press the Load default button to apply the default settings for all line types. 

See also: 











MonitorMagic can update monitors and monitor values automatically. When the MonitorMagic 

service obtains new monitor values, the values shown in the monitor windows of the 

MonitorMagic client become out of date. The MonitorMagic client can update the results on an 

interval basis. You can specify the interval rate. To configure the update settings, activate the 

Network view window and browse to find the computer running the MonitorMagic service. Right 

click the computer name and select menu option Configure service. 

226


Select tab Client update. Select one of the two options. For the first option you also need to 

specify the interval time in seconds. Note, if you specify a smaller interval period more network 

traffic will be generated. 

See also: 









Printing reports 

With MonitorMagic, you can print the details of a single monitor, multiple monitors or all monitors. 

The report can contain any combination of the following type of information: 

monitor specification data 

monitor output data 

monitor scheduling parameters 

rule criteria specification 

rule status 

alarm action specification 

alarm action execution status 

You can select the print function from the main menu, by selecting File, Print..... The Print... 

function is also available from the context sensitive menu activated with a right mouse button click 

in the monitor window. 

227


With this option, it is very easy to print out detailed information of the selected monitor(s). 

See also: 

Print - Detailed report 

Print - Various options 

Print - Page setup 


When printing a detailed report with MonitorMagic, you can choose what information you want to 

print. See Printing reports for more information. 

228


From the window you can specify what information must be printed for each monitors. Use the All, 

Spec's, Results and Clear buttons to select and deselect multiple options. 

See also: 





When printing reports, you can configure a number of printing options. To start, open a monitor 

window. Select menu option File, Print... and select the Various tab. You will be presented the 

following window: 

229



Include all objects in report 

Select this option if the report should include all objects. This is the default option when the print 

function is initiated from the main menu. 

Include selection only in report 

Select this option if the report should include selected objects only. This is the default option 

when the print function is initiated from a context sensitive menu. See Printing reports for more 

information. 

See also: 





A MonitorMagic printed report has a configurable layout. To change the layout, select menu 

option File, Page setup. You will be presented the following window: 

230



Header text 

Specify the text printed as a header on each printed page. The specified text fields are aligned to 

the left and right margins. See Footer text for possible keywords. 

Footer text 

Specify the text printed as a footer on each printed page. The specified text fields are aligned to 

the left and right margins. In both the header and footer text you can use the following keywords: 

Keyword Example Description 

%DATE% 03/10/2001 The date when the report is 

printed 

%TIME% 14:30:00 The time when the report is 

printed 

%PAGENUMBER% 4 The page number of the current 

page. 

Font - Regular 

Press the button to configure the font used by all normal printed text. 

Font - Header - Footer 

Press the button to configure the font used to print header and footer text. 

Font - Strong 

Press the button to configure the font used in headers. 

See also: 




Graphs 

231


2 dimensional graphs 


MonitorMagic can show graphs of data collected by monitors. You can show historical data and 

real time data in a graph. Historical data is always obtained from the MonitorMagic database. 

Real-time data is shown when new data from monitor is collected. If you want to show historical 

data in a graph, you must use a database. If you want to show real-time data only, you do not 

need to use a database. In most cases, graphs will show both historical and real-time data. 

Graph windows support the following features: 

Real-time and historical data display 

Time- and value zooming 

Drag- and drop of items 

Printing of graphs 

Save in file 

Highly configurable 

MonitorMagic both supports 2 and 3 dimensional graphs. For more information on 3 dimensional 

graphs, see 3D Graphs - Introduction. 

See also: 

Graph - Creating a new graph 

Graph - Adding items to a graph 

Graph - Creating a graph with an item 

Graph - Drag and drop multiple items 

Graph - Save and read from file 

Graph - Time range 

Graph - Colors 

Graph - Items 

232


Graph - Options 

Graph - Zoom operation 

Graph - Printing a graph 

Graph - Item display 

Graph - Item scale 

Graph - Creating a new graph 

You can create an empty graph that contains no items and data, or you create a graph directory 

from a monitor. To create an empty graph, select menu option Graph, Create graph. A new 

window is presented. The default time period of the graph is the last 24 hours. 

The graph window contains two sections, the upper and lower part of the window. In the upper 

part, the graph is drawn. On the left side, the default vertical scale from 0 to 100 is displayed. For 

new items, the scale will be adjusted automatically. Just below the graph, a horizontal time scale 

is drawn. The first time-date displayed always shows both the time and date. Depending on the 

time range, the other time-date entries that are displayed may be shown in a different manner. 

The lower part shows the legend of the graph. By default, the height of the legend is scaled 

automatically. 

See also: 


Graph - Adding items to a graph 

The items in a graph always show data that is collected by a monitor. So in order to show a graph 

of a specific item, there must be a monitor that collects data for the item. To add an item to a 

graph, connect to a MonitorMagic service and open a monitor window that contains some 

monitors. See Open a monitor window for more information. Now select menu option Graph, Add 

graph item.... The following window is presented: 

233


The window shows all monitors maintained by the connected MonitorMagic services of which you 

can show data in a graph. If you cannot find the item of which you want to show data in a graph, 

you should check the monitor window to see if a monitor is available for the item. 

To add items to the graph, select one or more items and press OK. 

MonitorMagic will try to collect historical information of the item by accessing the MonitorMagic 

database. If you are not using a database, or if the database does not contain a single item for an 

item, an error message is shown. In this case, only real-time data is available for the graph. 

See also: 


Graph - Creating a graph with an item 

From the monitor window, you can create a graph for selected items directly. To do so, open a 

monitor window and select one or more items. Right click the mouse and select menu option 

Show graph. 

234


MonitorMagic will try to collect historical information of the selected items by accessing the 

MonitorMagic database. By default, a time period of 1 day is used. If you are not using a 

database, or if the database does not contain a single item for an item, an error message is 

shown. In this case, only real-time data is available for the graph. 

When monitors collect data according to their scheduler, the graph will be updated automatically. 

See Graph - Time range for more information. 

See also: 

235



Graph - Drag and drop multiple items 

Once you have created a graph, you can add graph items to it with a drag- and drop operation: 

Make sure that both the monitor window and graph window are (partially) visible. 

Select one or more monitors in the monitor window. 

Keep the left mouse button down when selecting the last monitor in the monitor window. 

While keeping the left mouse button pressed, move the mouse to the graph window. 

When positioned on the graph release the left mouse button. 

MonitorMagic will try to collect historical information of the selected items by accessing the 

MonitorMagic database. If you are not using a database, or if the database does not contain a 

single item for an item, an error message is shown. In this case, only real-time data is available 

for the graph. 

See also: 


Graph - Save and read from file 

By default, MonitorMagic will save any graph shown on the desktop when exiting the 

MonitorMagic user interface application. The next time, you start the MonitorMagic application, 

the graph will be shown. You can also save and read graphs to a file. Note that only the graph 

settings, not the actual graph data is stored and read from the file. 

Save graph in file 

To save a graph, select the graph window and select menu option File, Save. If you previously 

saved the graph to a file and want to store the graph with a different file name select menu option 

File, Save as.... 

Read graph from file 

To read a graph from a previously saved file, select menu option File, Open graph.... Select the 

file and press OK. 

See also: 


Graph - Time range 

For each graph you can specify the time period for which data must be shown. When you create 

a graph, MonitorMagic always selects a time period representing the last 24 hours. To change the 

time period, make the graph window the active window and select menu option View, Properties. 

(You can also right click the mouse in the graph and select the right mouse menu option 

Properties). The following window is shown: 

236



Dynamic start time 

Select this option if you want a floating start time that changes while time expires. When you 

select this option, you also need to specify the time range. By default MonitorMagic selects this 

option. By selecting this option, MonitorMagic will remove old expired data from the graph. 

Fixed start time 

Select this option if you want to use a fixed start time for the graph. 

End time is current time 

Select this option if the end time of the graph must be the current time. In this case, the end time 

changes while time expires and real-time data can be shown in the graph. 

Fixed end time 

Select this option if you want to use a fixed time. If the end time is beyond the current time, the 

graph will be updated when new monitor data becomes available. 

See also: 


Graph - Colors 

You can change the colors of the graph background, grid and graph items. To change the color of 

graph items, see Graph - Item display. To change the background and grid color color, make the 

graph window the active window and select menu option View, Properties. A dialog window is 

shown. Select the tab Colors. You will be presented the following window: 

237


The Color items list shows the colors used by the different graph objects. To change a color, 

select the particular object (Background color, Grid color) and press the Color button. Change 

the color in the presented dialog. 

See also: 


Graph - Items 

You can configure a number of options for each individual item shown in the graph. To configure 

an individual graph item, you can: 

Double-click the left mouse button on the item shown in the graph legend; 

Select the item in the legend with the right mouse menu and select menu option 

Properties. 

Make the graph window the active window and select menu option View, Properties. A 

dialog window is shown. Select the tab Items. You will be presented the following 

window: 

238


Select the item you wish to configure and press the Edit button. See Graph - Item display and 

Graph - Item scale for more information. 

See also: 


Graph - Options 

You can configure a number of options for a graph. To do so, make the graph window the active 

window and select menu option View, Properties. A dialog window is shown. Select the tab 

Various. You will be presented the following window: 

239



Real-time update new results in the graph 

Select this option to update the graph when new data becomes available. Note that a graph is 

updated only if a monitor window is open containing the monitors of which data is shown 

in the graph. The rate at which data is updated depends on the scheduling configured for 

each monitor and can never exceed the rate at which the MonitorMagic client is updated. 

Show horizontal grid lines 

Select this option if the graph should display horizontal grid lines. 

Show vertical grid lines 

Select this option if the graph should display vertical grid lines. 

When the size of the graph window is changed, automatically size the legend area 

The lower part of the graph window shows the legend of the graph. If the graph contains more 

items, the height of the legend should be increased to show all items simultaneously in the legend. 

Select this option if this should be done automatically when the new items are added or when the 

window is resized. 

When selecting a rectangle, zoom in the X direction (time). 

Select this option if you want to be able to zoom into a closer time range. To zoom in, left click the 

mouse button in the graph window and keep the left mouse button pressed. Move the mouse and 

draw a rectangle that contains the desired time range. Release the left mouse button. 

When selecting a rectangle zoom in the Y direction (value). 

Select this option if you want to be able to zoom into a closer value range. 

See also: 


240


Graph - Zoom operation 

You can zoom into both the time (horizontal) and value (vertical) direction in a graph. To zoom in, 

you need to select a rectangle: 

Left click the mouse button on the position where the zoom area starts. 

While keeping the left mouse button down, move the mouse and draw a grey rectangle 

around the zoom area 

 

Release the left mouse button. MonitorMagic will redraw the graph, showing only the 

specified zoom area. 

241


To zoom out, select one of the following menu options from the main menu Graph or from the 

menu shown when you click the right mouse button in the graph: 

Zoom Out (1:2) 

Select this option to double the time range and value range. Note that with this method you 

cannot exceed the time range specified for the graph. See Graph - Time range for more 

information. 

Zoom Out (All) 

Select this option to redraw the graph, showing the full time range specified for the graph. 

See also: 


Graph - Printing a graph 

With MonitorMagic you can print a graph in full color or black and white. Depending on the printer 

capabilities, MonitorMagic will automatically select conversion options. To print a graph, right click 

the mouse in the graph window and select menu option Print.... You can also select the Print... 

menu option from the main File menu when the graph window in the active window. 

MonitorMagic will first ask you to select a printer and print layout settings. Press OK when ready. 

The following window will be presented: 

242


Use this window to specify how MonitorMagic must print the graph. The window contains the 

following fields: 

Color print 

Print the graph using the colors from the graph. This is recommended and automatically selected 

for color printers. 

Black and white print 

Convert all colors to black and white. This option is automatically selected for back and white 

printers. 

Automatically adjust line styles 

Select this option if you want MonitorMagic to change line styles so that different items look 

different (solid line, dashed line, dotted line etc.) when drawn with the same color. 

Fit graph to page 

Select this option if MonitorMagic should change the dimensions of the graph to maximize the 

printed graph size. With this option, the printed graph width and height ratio can differ from the 

graph shown on the screen. If you do not select this option, the printed graph width and height 

ratio will be equal to the ratio as shown on the screen. 

Center graph horizontally 

Select this option if the graph must be horizontally centered when printed on paper. 

Print graph 

Print the graph and all graph items 

Print description 

243


Print a description of the graph above the printed graph. The description will contain several lines, 

layout in a 2 column table. 

Print legend 

Print the legend of the graph below the graph. 

See also: 


Graph - Item display 

You can configure the way Monitor displays each item of a graph. To start, double click the item 

shown in the legend of the graph. See Graph - Items for more information on how to access this 

window. You will be presented the following window: 


Color 

Press the button to change the color of the item. 

Use line type ... with a line width of ... pixels 

Select the line style and line width in pixels. Note that only for a solid line, you can specify a 

line width different than 1. Note also that if you specify a line width of 0 pixels, no line will 

be drawn. 

Only connect data points with line segments 

Select this option if you do not want individual data points to be draw. 

Show data points with a radius of ... pixels 

Select this option it you want individual data points to be drawn. 

244


See also: 


Graph - Item scale 

You can configure the scale used by MonitorMagic to draw a graph item. To start, double click the 

item shown in the legend of the graph and select tab Vertical scale. See Graph - Items for more 

information on how to access this window. You will be presented the following window: 


Automatic scaling 

MonitorMagic will use a scaling factor so that all item values multiplied by the scaling factor fall in 

the range 0,...,100. 

Fixed scaling factor. Scale factor: ....... 

Select this option and specify the scaling factor if you want MonitorMagic to use a fixed scaling 

factor. Note that when drawing the item in the graph, MonitorMagic will multiply the data value 

with the scaling factor. 

See also: 


3 dimensional graphs 


245


MonitorMagic can show 3 dimensional (3D) graphs of data collected by monitors. You can show 

historical data and real time data in a graph. Historical data is always obtained from the 

MonitorMagic database. Real-time data is shown when new data from monitor is collected. If you 

want to show historical data in a graph, you must use a database. If you want to show real-time 

data only, you do not need to use a database. In most cases, graphs will show both historical and 

real-time data. 

3D graph windows support the following features: 

Real-time and historical data display 

Time- and value zooming 

Drag- and drop of items 

Printing of graphs (Q4-2002) 

Highly configurable (transparency, rotation, stretch) 

Hardware considerations 

The processing and rendering of 3D graphs uses considerably more CPU usage then 2 

dimensional graphs. Further, 3 dimensional graphs are rendered using the OpenGL libraries that 

are part of the Windows .NET/XP/2000/NT operating system. These graphical libraries interface 

directly with the hardware of the system. Depending on the system's video card, the rendering of 

3D graphs can take considerable time. Specially when anti-aliasing effects are enabled, the CPU 

usage and processing time increases considerably. 

See also: 

3D Graphs - Creating a new graph 

3D Graphs - Adding items to a graph 

3D Graphs - Time range 

3D Graphs - Colors 

3D Graphs - Color specification 

3D Graphs - Items 

3D Graphs - Items - Display 

3D Graphs - Items - Display - Bar 

3D Graphs - Items - Display - Line 

246


3D Graphs - Items - Vertical scale 

3D Graphs - Planes 

3D Graphs - Scale axis 

3D Graphs - Various 

3D Graphs - Orientation 

3D Graphs - Creating a new graph 

You can create an empty graph that contains no items and data, or you create a graph directory 

from a monitor. To create an empty graph, select menu option Graph, Create 3D graph. A new 

window is presented. The default time period of a 3 dimensional graph is the last 60 minutes. 

To create a 3D graph from a monitor directly, select the monitor, right click the mouse and select 

menu opion Show 3D graph. 

The 3D graph uses its 3 dimensions as follows: 

horizontal direction: time axis. The time increases from left to right. By default, 

MonitorMagic will draw time labels at the bottom, just in front of the graph. 

vertical direction: Value direction. By default, the values are scaled in a range from -100 

to 100. Since most items have positive values only, the defautl scale of the graph ranegs 

from 0 to 100. 

depth direction: Item direction. Each item shown in the graph will be drawn at a certain 

depth coordinate. When new items are added to the graph, MonitorMagic will 

automatically update the depth coordinates. 

Note: The windows direction of horizontal, vertical and depth direction changes when the graph is 

rotated or stretched. See 3D Graphs - Orientation for more information. 

See also: 


3D Graphs - Adding items to a graph 

You can use 2 methods to add new items to a 3D graph: 

 

 

Drag- and drop items from the monitor window into the 3D graph window. When the 

mouse button is released, the data will be collected from the database and shown in the 

graph. 

Select the main menu option: Graph, Add graph item... A dialog will be shown from 

which you can select available monitor items. 

See also: 


3D Graphs - Time range 

For each graph you can specify the time period for which data must be shown. When you create 

a 3D graph, MonitorMagic always selects a time period representing the last 60 minutes. To 

change the time period, make the graph window the active window and select menu option View, 

Properties. (You can also right click the mouse in the graph and select the right mouse menu 

option Properties). The following window is shown: 

247



Dynamic start time 

Select this option if you want a floating start time that changes while time expires. When you 

select this option, you also need to specify the time range. By default MonitorMagic selects this 

option. By selecting this option, MonitorMagic will remove old expired data from the graph. 

Fixed start time 

Select this option if you want to use a fixed start time for the graph. 

End time is current time 

Select this option if the end time of the graph must be the current time. In this case, the end time 

changes while time expires and real-time data can be shown in the graph. 

Fixed end time 

Select this option if you want to use a fixed time. If the end time is beyond the current time, the 

graph will be updated when new monitor data becomes available. 

See also: 


3D Graphs - Colors 

You can change the colors of the 3D graph background, grid and graph items. To change the 

color of graph items, see 3D Graphs - Items - Display. To change the background, grid and 

surface color color, make the graph window the active window and select menu option View, 

Properties. A dialog window is shown. Select the tab Colors. You will be presented the following 

window: 

248


To change the color of one of the shown object, select the object and press the button Color. To 

restore the default colors, press Defaults. 

Note: Because of 3 dimensional light effects and transparency of objects, the color of 

rendered objects may look considerably different compared to the selected colors. 

See also: 


3D Graphs - Color specification 

For 3D graphs, the color of an object is specified by it's three color components (red, green and 

blue) and the transparency of the color. 

249


To change the basic color, press the Change color button. The transparency is specified by a 

number between 0 and 1. A value of 0 correponds with a not transparent object. You can not see 

an object that is behind a not transparent object. A value of 1 corresponds with a completely 

transparent object. If an object is transparent, you can look through it and see other objects 

behind the object. 

Guidelines: 

For plane surfaces, use highly transparent colors (transparency fraction of 0.9). If you 

rotate the graph so that a surface is on the front side, you will still be able the items 

drawn in the graph. 

For scale axis, use not transparent colors (transparency fraction of 0.0). Since axis are 

thin lines, they should be as clear as possible. 

For items drawn in a graph, use a transparency fraction depending on the draw style of 

the item. For bar graphs, you can use any transparency fraction, for line graphs, it is 

advised to use not transparent colors. 

See also: 


3D Graphs - Items 

To change the characteristics of the items drawn the graph, activate the graph and select main 

menu option View, Properties. Select tab Items. From the list shown, select the item and press 

the Edit button. 

As an alternative, you can also double-click the item in the legend area of the graph window. 

See also: 


3D Graphs - Items - Display 

To change the characteristics of a graph item, double click the item the legend area of the 

window or select Properties, Items, select the item and press Edit. 

250


From the window, you can change the color of the item and the type of graph object drawn for the 

item, e.g. bar or line. 

See also: 


3D Graphs - Items - Display - Bar 

Press the Properties button next to the Bar option to open the following window, used to edit the 

bar graph characteristics. 

Bar width 

The width of the bars drawn in the graph. 

See also: 


251


3D Graphs - Items - Display - Line 

Press the Properties button next to the Line option to open the following window, used to edit 

the line graph characteristics. 


Line width 

The widht of the line used to draw the line (segments). 

Show line 

Check this option if the line should be drawn. 

Show item surface with transparency fraction ... 

Enable this option if you want a vertically oriented surface drawn at the depth position of the 

graph item. This option can be used to clarify the graph, specially when drawing multiple line 

items in th graph. The surface is drawn using the same color as the item but with a different 

transparency fraction. It is advised to specify a high transparency fraction (0.95). 

Show data points with radius ... and ... subdivisions 

Enable this option to draw spheres for each data point graph locations. For this option you need 

to specify the radius of each sphere and the number of subdivisions. For a larger number of 

subdivisions, the drawn object better approaches a sphere but requires more rendering effort, e.g. 

CPU usage. (Hint: number of subidivsion=1: poor quality, 5: OK quality, 10: good quality) 

See also: 


3D Graphs - Items - Vertical scale 

The vertical direction of a 3D graph corresponds with the values of the items displayed in the 

graph. The vertical scaling parameters are specified fro the graph and for each individual item. 

For the overall graph you can specify the scale range of the graph in the vertical direction. By 

default, the vertical scale range is set to the interval [0,...,100]. For all items, a scale factor can be 

calculated so that all values fall within this range. To change the vertical scale range, see 3D 

Graphs - Vertical scale. 

252


For each graph item, you can specify 2 scale methods: 


Fixed scaling 


When new values are added for the graph item, MonitorMagic will adjust the item scaling factor 

so that all values multiplied by the scaling factor fall within the range [-100,...,100]. Note that this 

is always possible. 

Fixed scaling 

The scale factor is specified by the user and will not be changed by MonitorMagic automatically. 

See also: 


3D Graphs - Vertical scale 

The vertical direction of a 3D graph corresponds with the values of the items displayed in the 

graph. The vertical scaling parameters are specified fro the graph and for each individual item. 

For the overall graph you can specify the scale range of the graph in the vertical direction. By 

default, the vertical scale range is set to the interval [0,...,100]. For all items, a scale factor can be 

calculated so that all values fall within this range. To change the scaling parameters for each 

individual item, see 3D Graphs - Items - Vertical scale. 

For the graph itself, you can scale range in the vertical direction: 

Graph minimum scale value 

The scale value that corresponds with the bottom of the graph. 

Graph maximum scale value 

The scale value that corresponds with the top of the graph. 

The format of the numbers displayed next to the vertical scaling axis can be changed by 

specifying the number of positions before and after the decimal point. 

See also: 


3D Graphs - Planes 

A 3-dimensional graph is drawn within a virtual rectangular 3 dimensional block object. The object 

has 6 surfaces: top, bottom, front, back, left and right. To clarify the graph, you can select which 

of these surfaces must be drawn. All surfaces are drawn with the same color. Normally a 

transparent color is used to draw these surfaces. 

See also: 


3D Graphs - Scale axis 

253


A 3-dimensional graph is drawn within a virtual rectangular 3 dimensional block object. The object 

has 6 surfaces and 12 axis. Each axis can be identified as the intersection of 2 surfaces. For 

each axis, you can specify the following items to be drawn: 

 

 

 

The axis itself 

Text labels next to the axis 

Perpendicular scale lines that intersect one of the two surfaces. 

All axes are drawn with the same color. 

See also: 


3D Graphs - Various 

For the 3D graph, the following additional parameters can be specified: 

Horizontal fill factor 

The fraction of graph in the horizontal direction that will be used to draw the items of the graph. 

When 100% is specified, all room in the horizontal direction will be used. The usage of this 

parameter depends on display method used to display each item. 

Depth fill factor 

The fraction of graph in the vertical direction that will be used to draw the items of the graph. 

When 100% is specified, all room in the depth direction will be used. 

Anti-aliasing mode 

By default, the lines drawn in the 3D graph will be drawn using anti-aliasing techniques. To 

enhance the graph further, you can enable anti-aliasing for all other objects drawn in the graph. 

The highest mode corresponds with the best result, but also requires most CPU time to render 

the graph into the window. Note that anti-aliasing can cause extreme CPU usage during 

rendering of the graph. 

Automatically size legend 

When new items are added to the graph, the legend area of the graph shown at the bottom of the 

graph window will be resized automatically when this option is enabled. 

Automatically update depth projection parameters 

When the graph is rotated and other orientation and projection parameters are changed, parts or 

the whole graph may become invisible. By setting this option, the depth projection parameters will 

be updated automatically so that the whole graph is shown. 

See also: 


3D Graphs - Orientation 

To change the orientation, e.g. projection of the 3D graph, right click the mouse in the graph and 

select menu option Orientation ... A small window will be shown. From the window, you can 

select an item that specifies a particular orientation parameter. When a parameter is selected, 

you can change the parameter with the slider shown in the window. While the slider is changed, 

the 3D graph will be updated automatically. 

254


Note: By adjusting the orientation parameters you can cause the graph not to be visible. 

To make the graph visible you need to adjust the closest distance and view distance 

parameters or select the option Restore default settings. 

Available parameters: 

Rotation (horizontal) 

Rotates the graph in the horizontal direction. If you think of the position where your eye is located, 

this operation corresponds with moving you eye in the horizontal direction. 

Rotation (vertical) 

Rotates the graph in the vertical direction. Moves your eye position up and down. Allows you to 

look at the top and and the bottom of the graph. 

Rotation (depth) 

Rotates the graph in the depth direction. Moves your eye to or from the object drawn. On a 

certain point, the depth eye location equals the depth coordinates of the object itself. At this point, 

the object rotates left or right in the window, or you move through the object, depending on the 

other projection parameters. When continuing, the eye is located on the other side of the object 

and you look at the graph object from the back. 

Position (horizontal) 

Moves the object in the horizontal direction. Since the object is drawn in perspective, the graph 

object rotates slightly as well. 

Position (vertical) 

Moves the object in the vertical direction. Since the object is drawn in perspective, the graph 

object rotates slightly as well. 

Position (depth) 

Moves the object in the depth direction. Since the object is drawn in perspective, the graph object 

rotates slightly as well. This operation can help you to understand what direction corresponds 

with the depth of the graph. 

255


Zooming (zoom factor) 

Determines the size of the object drawn. Corresponds with the angle (field of view) in the vertical 

direction used to look at the object. 

Zooming (closest distance) 

Specifes the closest visible depth coordinate. If the graph object is not completely visisble you 

should adjust this value and the view distance parameter. 

Zooming (view distance) 

Specifes the range in the depth direction that is visible in the graph. If the graph object is not 

completely visisble you should adjust this value and the closest distance parameter. 

Light - base intensity 

Light - spot intensity 

Light - spot angle 

Light - horizontal spot position 

Light - vertical spot position 

Light - depth spot position 

Light - horizontal spot direction 

Light - vertical spot direction 

Light - depth spot direction 

MonitorMagic uses light effects to draw the 3D graph. Light reflecting on the graph object makes 

the graph object visible. With the light parameters you can adjust the lighting effects. The graph 

object reflects light from 2 light sources: Light that comes from all directions (base intensity) and 

light from a spot light (all other parameters). 

Stretch (horizontal) 

Stretches the graph object in the horizontal direction. 

Stretch (vertical) 

Stretches the graph object in the vertical direction. 

Stretch (depth) 

Stretches the graph object in the depth direction. 

Restore default settings 

Restores all parameters to the default settings. 

See also: 


MonitorMagic service 

Installing and upgrading the MonitorMagic service 

The MonitorMagic service is the engine of MonitorMagic. The MonitorMagic service performs all 

networking calls, controls the monitors, evaluates the rules, and executes the alarm actions. The 

MonitorMagic service runs continuously as a service and is started automatically when a 

computer is started. To run MonitorMagic you need to have at least one MonitorMagic service 

installed, but you can also install the MonitorMagic service on multiple computers. For more 

information on this topic see Single versus multiple MonitorMagic services 

256


The MonitorMagic service can be installed on most computers running Microsoft Windows 

operating systems, including all version of Microsoft Windows 2000 and Microsoft Windows NT 

4.0. To check the exact requirements, see the topic Requirements. 

The MonitorMagic service can only be installed and upgraded with the MonitorMagic client 

application. To install the MonitorMagic client application, see the section Setup MonitorMagic. To 

install and upgrade the MonitorMagic service you need to be an administrator of the computer 

you installed or upgraded the service on. To start installing or upgrading the MonitorMagic service 

start the MonitorMagic client. In the Network view window browse to find the computer you want 

to install or upgrade the MonitorMagic service on. Right click the computer name and select the 

menu option Setup service. 

The MonitorMagic service setup dialog appears. This dialog is used to upgrade or install the 

service. 

See also: 

MonitorMagic service setup 



The MonitorMagic service setup dialog is used to install and upgrade the MonitorMagic service on 

the local and remote computers. See requirements to find what computer you can install the 

service on. To start the dialog, start the MonitorMagic client, browse in the network view to find 

the computer, right click the mouse, and select menu option Setup service. 

The MonitorMagic service setup dialog has two forms, normal and advanced. In the normal 

version only the Servername and Serial fields are visible. 

257


To switch between normal and advanced mode press the Advanced button. When running in 

(default) normal mode MonitorMagic will fill in defaults for all extra fields specified in the 

advanced section. If you are a member of the Domain Admins group of the domain you are 

logged on to all default settings will be fine. Otherwise, you need to change some of the fields. If 

you are upgrading instead of installing a MontiorMagic service most service options that can be 

specified in this dialog will not be changed (see below). Instead, MonitorMagic will continue to use 

the current settings. 

Server name(s) 

The name of the computer(s) you want to install or upgrade the service on. Note that this 

computer can run Windows NT 4.0 workstation and Windows 2000 Professional as well. You can 

specify multiple computers separated by comma's (,) as well. Example: Tulip,Rose. 

Service serial number 

The MonitorMagic license serial number. For test purposes, you can leave this field blank or 

specify the word DEMO. The license number is a 30-digit number you obtain from your 

MonitorMagic reseller. To upgrade from a demo version to a purchased version you need to fill in 

the license code serial number here. For more information on MonitorMagic licensing, see the 

section MonitorMagic license. 

User name 

258


The Windows 2000 or Windows NT user account name that will be used by the MonitorMagic 

service. If the account does not exist MonitorMagic will create it with the password specified in the 

next field. By default, MonitorMagic will create the account MonitorMagicSvcAccnt in the 

domain you are logged on to. If the account already exists the password specified in the next field 

must be correct. Otherwise, the MonitorMagic service will not start. The syntax of the service 

account specification is DOMAIN\ACCOUNTNAME. For Windows 2000 domains you must use 

the NETBIOS domain name. If you want to use a local machine account, e.g. not a domain 

account but an Windows NT 4.0 workstation or Windows 2000 Professional account name, you 

should use the syntax \\COMPUTERNAME\ACCOUNTNAME. When upgrading, this field is not 

used. 

Password 

The password of the service account specified in the field User name. If the specified User name 

already exists the password must be correct. If MonitorMagic creates the account, the password 

of the new account is specified in this field. When upgrading, this field is not used. 

Group (Service account group membership) 

The MonitorMagic service account will be added to this group. By default, the Domain Admins 

group is used. This setting is used to grant the MonitorMagic service sufficient access rights to 

retrieve information from all monitored objects and to execute alarm actions. If the MonitorMagic 

service account does not have sufficient access rights error messages will appear in the 

computer Application event log, and in the MonitorMagic client window. 

Group (MonitorMagic administrator group) 

This group is used to specify the user accounts that are allowed to configure the MonitorMagic 

service. By default, the group is set to the local administrators group. The way this is organized is 

comparable to the way you setup access control for files and directories. 

Directory 

This field contains the directory where MonitorMagic will install the MonitorMagic service software. 

Note that the specification is relative to the remote computer, e.g. C:\... means the directory 

C:\ on the computer where the MonitorMagic client is going to be installed. By default, 

MonitorMagic searches for a drive and directory with enough available free disk space which is 

accessible through an administrative share (e.g., \\COMPUTER\C$). 

Site 

Use this field only when you have a valid MonitorMagic site license. If this is the case, specify the 

name of the licensed 'site' in this field. 

Enable debug logging in application log of event viewer 

If you want the MonitorMagic service to generate more information regarding its operations you 

can enable this option. By default, the option is disabled. 

Close 

Press to close this dialog. 

Install/Upgrade 

Press this button to start installing or upgrading the MonitorMagic service. 

Delete 

Press this button to start deleting the MonitorMagic service from the specified computer(s). If you 

select this option, all input fields except the Server name(s) field are ignored. 

Advanced 

Use this button to switch the dialog between normal and advanced mode. 

See also: 

Installing and upgrading the MonitorMagic service 

259



Single versus multiple MonitorMagic services 

With MonitorMagic you can monitor network objects like disks, event logs, performance counters 

and so on. These objects are monitored by the MonitorMagic service. The MonitorMagic service 

resides on a computer and is able to monitor local and remote objects. 

Example: Suppose you have installed the MonitorMagic service on computer A. The 

MonitorMagic service on computer A is checking a number of monitors of computer A, for 

instance all the disks, event logs and some performance counters of computer A. Now you also 

want to monitor something of computer B. You now have the following options: 

Install the MonitorMagic service on computer B and let the new service maintain the 

monitors of computer B. 

Do not install the MonitorMagic service on computer B and let the MonitorMagic service 

on computer A monitor the objects of computer B. 

With MonitorMagic you can choose from various scenario's regarding the distribution and 

configuration of MonitorMagic services in your network environment: 

MonitoringMagic service scenario: Single service with remote monitoring 

In this scenario, only one MonitorMagic service is installed. The single MonitorMagic service 

monitors all objects on local and remote computers. Since the MonitorMagic service is installed 

only on one computer you don't need to install the MonitorMagic service on each monitored 

computer. A disadvantage of this method is network traffic: Since you are monitoring remote 

objects, all object information is transported over the network. This method is recommended if 

you monitor objects on moderate frequencies (every minute-hour) only, or when it is not possible 

or allowed to install and configure the MonitorMagic service on each computer. 

Advantages: 

Single MonitorMagic service installation and configuration. 

Simple planning, implementation and maintenance of monitoring software. 

Disadvantages: 

Single point of failure 

Monitoring may fail if network errors occur 

MonitorMagic service scenario: Multiple service with local monitoring 

In this scenario the MonitorMagic service is installed on each computer containing objects that 

must be monitored. With the MonitorMagic client it is possible to install multiple MonitorMagic 

services at one time. The biggest advantage of this method is the fact that monitoring takes place 

at the same location as the monitored object. This minimizes the network load: Since each 

monitored object is monitored by the MonitorMagic service running on the same computer, there 

is no network traffic involved. A disadvantage of this method is the required installation and 

configuration of the MonitorMagic service on each monitored computer. This method is 

recommended if you monitor objects at high frequencies (every minute). 

Advantages: 

No network traffic 

Accurate monitoring: Monitoring takes place at the same location as the objects 

260


Disadvantages 

Multiple MonitorMagic service installation, configuration and maintenance 

More complex monitoring architecture: multiple services 

MonitorMagic service scenario: Mixed model with local and remote 

monitoring 

In most circumstances the best way to configure MonitorMagic is a mix of both scenarios: Multiple 

MonitorMagic services monitoring local and remote objects. Objects that are monitored only on 

moderate frequencies (every minute-hour) can be monitored by remote services. Monitoring at 

high speed is accomplished by a local MonitorMagic service. 

See also: 


Deleting the MonitorMagic service 

To delete the MonitorMagic service from a computer, you need to run the MonitorMagic client. 

You can delete the MonitorMagic service from a remote computer with the MonitorMagic client as 

long as you are logged in as an administrator of that computer. If the MonitorMagic client is not 

installed on any machine, you need to install a MonitorMagic client in order to delete the 

MonitorMagic service. Note that in order to delete the MonitorMagic service with the 

MonitorMagic client, the MonitorMagic service and client don't need to have the same version. 

From the MonitorMagic client, browse to find the computer that runs the MonitorMagic service to 

delete. Select the computer, right click the mouse and select the menu option Delete service. 

261


In the MonitorMagic Service Setup dialog, the field Server name(s) is filled in automatically. To 

delete multiple MonitorMagic services, enter multiple computer names, separated by comma's (,). 

To delete the MonitorMagic service(s), press the Delete button. 

See also: 



The MonitorMagic user interface can write log information to a text file. Log information is 

generated for the following operations and situations: 

1. Installing, upgrading and deleting the MonitorMagic service 

2. Connecting to the MonitorMagic service 

3. Error situations 

To enable the logging function, select the main menu function File, Log options.... You will be 



Generate log information 

Select this option if the MonitorMagic user interface must generate log information. 

Log file 

Specify the name of the log file. 

OK 

Accept any changes made and exit this window. 

Cancel 

Discard any changes made and exit this window. 

262


Show 

Start the notepad editor and show the contents of the log file. 

See also: 


Checking the MonitorMagic service 

Checking the service setup 

Once installed and running the MonitorMagic service will run without problems in most cases. If 

you encounter any problems with the MonitorMagic service setup, or if you are interested in this 

subject, you can check the service installation and operation by several procedures. By 

evaluating the different topics in this chapter you will be able to find out what the problem is. 

The following sections describe the different procedures you can use to check the MonitorMagic 

service: 

Checking the service status (Windows NT 4.0) 

Checking the service status (Windows 2000) 

Checking the application log (Windows NT 4.0) 

Checking the service registry configuration (Windows NT 4.0, Windows 2000) 

Checking the service files (Windows NT 4.0, Windows 2000) 

See also: 



You can check the status of the MonitorMagic service from a local or remote computer. To start, 

log on to a Windows NT 4.0 domain controller as an administrator of the computer that runs the 

MonitorMagic service. Select menu option Start, Programs, Administrative Tools, Server 

Manager. This starts op the Microsoft Server Manager application. If the target computer is not 

shown in the list of computers, it is probably located in another domain. Select menu option 

Computer, Select domain and select the domain that contains the target computer. 

Next, select the target computer from the list and select menu option Computer, Services. This 

brings up the the Services window from the selected target computer. In the list, scroll down to 

find the MonitorMagic service. Normally, the service status is Started and the service startup 

mode is Automatic. If in the status column the word Started is missing, the service is not running. 

You can try to start the service by pressing the Start button. If this does not work, you can try to 

find the cause of the problem as described in the topics listed at the end of this section. 

263


To check other various settings, press the Startup button. In the displayed window, the service 

startup type and logon setting can be specified. Normally, the startup type should be set to 

Automatic. In the Log On As section, the account used by the MonitorMagic service and the 

password of this account are specified. If for some reason, the MonitorMagic service is not able to 

log on, you might need to change the password settings in this dialog. The specified password 

must correspond with the password specified with the User Manager for Domains application. 

If, for whatever reason, you want to change the account used by MonitorMagic service, you need 

to use this window to do so. 

The following sections describe other procedures you can use to check the MonitorMagic service: 




264



See also: 



To check the MonitorMagic service status of a remote or local computer, select Start, Programs, 

Administrative Tools, Computer Management. (On Windows 2000 Professional run Start, 

Control Panel, Administrative Tools, Computer Management.) The local computer is selected 

by default. To connect to a remote computer, right click the top left text (Computer 

Management) and select menu option Connect to another computer. Select the remote 

computer and press OK. When connected, expand the computer management tree: Computer 

Management, Services and Applications, Services. The right side of the window is updated to 

show the services of the selected computer. 

Scroll to find the MonitorMagic service and service status information. 






See also: 



When the MonitorMagic service starts, it will always write an information message to the 

Application log of the computer it is running on. If problems occur while the MonitorMagic 

service is running, the service will write other messages to the application log. By examining 

these messages, you can trace back to see when, and possibly why, the problem originated. 

265


To open the application log of the computer running the MonitorMagic service, log on as an 

administrator to a computer running Windows NT 4.0. Make sure you log on as an administrator 

of the computer that runs the MonitorMagic service. Select menu option Start, Programs, 

Administrative Tools, Event viewer. If the MonitorMagic service is not running on the local 

computer, select menu option Log, Select computer. Enter the name of the computer and press 

OK. The Event viewer will connect to the computer and open the log window. Select the 

application log with menu option Log, Application. In the log window, many messages can be 

displayed, originating from different sources. To find the messages that have to do with 

MonitorMagic, you must browse through the window to find messages that have MonitorMagic 

described as the source. 

To see the details of a message, double click it or select the message and select menu option 

View, Detail. The oldest message of MonitorMagic always reflects that the MonitorMagic is 

started. The message contains the version and build number of the MonitorMagic service. In the 

figure shown, an error message is shown because some MonitorMagic configuration file is 

missing. 

266


267


If there are many error message generated by the MonitorMagic service, you might want to save 

all these messages in a file and send the file to the support department of Tools4ever or your 

MonitorMagic reseller. To do so, select menu option, Log, Save as and specify the name of the 

file. Press Save to save the file. 

If there are no MonitorMagic service messages in the log file, the service is probably not started. 

In this case there might be something wrong with the service installation files, the service registry 

configuration, the service user account, or a more generic computer problem. 






See also: 


Checking the service registry configuration (Windows NT 4.0, Windows 

2000) 

If for some reason the MonitorMagic service installation failed, or the service cannot be started, 

you can check the registry of the computer on which the MonitorMagic service is installed. Note 

that the registry is a secure area of the computer. You should never change, create or 

update settings in the registry directly unless you are completely sure about what you are 

doing. Changing the registry may lead to unpredictable results and severe problems. If 

you only read the registry settings, no problems will occur. By examining the registry, you 

can convince yourself that the MonitorMagic service is actually installed, and you can find the 

location of the MonitorMagic service files. 

To startup the registry editor you need to be logged on as an administrator. Select menu option 

Start, Run. Enter the command regedit and press the OK button. If the MonitorMagic service is 

installed on a remote machine, connect to the registry of the remote machine: select menu option 

Registry, Connect Network Registry and enter the name of the remote computer and press OK. 

If you are not able to access the registry or parts of the registry on the remote computer you are 

probably best off by running the registry editor on the remote machine. 

The MonitorMagic service has two locations in the registry. The first is where installed services 

and processes configuration information is stored. These registry locations are controlled by 

Windows NT/2000. The other registry location is used only by the MonitorMagic service. At this 

location, the MonitorMagic service stores its own configuration information settings. To check 

these settings, see MonitorMagic service registry settings. 

To check if the service installation registry entries are properly installed, find the registry entry 

[COMPUTER]\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services. The window 

should look like the next figure: 

268


If you scroll down in this alphabetical list, you should be able to find the entry for the 

MonitorMagic service. If you select the MonitorMagic entry, the right side of the window shows 

the service configuration information of the MonitorMagic service. 

If the MonitorMagic entry is not available, the MonitorMagic service is not installed on the 

computer. To continue, start the MonitorMagic client and install the MonitorMagic service on the 

computer. If you do find the entry for the MonitorMagic service, you can find the location of the 

MonitorMagic service file at the entry ImagePath. The displayed file is the executable file of the 

MonitorMagic service. The directory of this file is the MonitorMagic service directory. To confirm 

the installation of the service you can check a directory in the registry, referenced in the example 

above, for the service files. See Checking the service files (Windows NT 4.0, Windows 2000) for 


269


Note: In exceptional cases, you can delete the MonitorMagic service by deleting the 

MonitorMagic registry key from the registry at location 

[COMPUTER]\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services. Before you do 

this, close all other applications and start the registry editor. At the selected registry key, select 

menu option Edit, Delete. Confirm any questions asked and reboot the computer. To complete 

the MonitorMagic service deletion operation, delete the service files and registry entries. 






See also: 



When the MonitorMagic service is not running, cannot be started, or might not have been 

installed properly, you can check the MonitorMagic service files. The service files are located in 

the MonitorMagic service directory, specified during the service setup. If you do not know the 

MonitorMagic service directory, you can check registry setting 

[COMPUTER]\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MonitorMagic\Im 

agePath. For more information, see Checking the service registry configuration (Windows NT 4.0, 

Windows 2000). 

In the MonitorMagic service directory, a number of files must be present. 

Table: MonitorMagic service files: 

Filename Description Average size (not exact) 

NM.EXE MonitorMagic service executable 1 MB 

NMMSG.DLL MonitorMagic service DLL 50 KB 

JVRLOG.DLL MonitorMagic service DLL 75 KB 

SSPALERT.DLL MonitorMagic service DLL 

175 KB 

SSPLCI.DLL MonitorMagic service DLL 100 KB 

If one of these files is missing, the service cannot run. To continue you should reinstall the 

MonitorMagic service. See Installing the MonitorMagic service for more information. Note, the 

directory can contain many files which are not listed in the table above. 






See also: 


270


Advanced 

MonitorMagic service registry settings 

The MonitorMagic service reads a number of parameters from the computer's local registry. This 

section summarizes these registry settings. Note that the registry is a secure area of the 

computer. You should never change, create, or update settings in the registry directly 

unless you are very sure about what you are doing. Changing the registry may lead to 

unpredictable results, severe problems, and may prevent the computer from properly. If 

you only read the registry settings, no problems will occur. 

The registry settings are located at various subkeys of the following registry key: 

HKEY_LOCAL_MACHINE\Tools4ever\MonitorMagic\Service 

Value Subkey Type of 

key 

TcpIpPort 

Description 

Communication DWORD Service TCP/IP communications port 

LogMsgDirectory Locations String Directory where MonitorMagic stores 

temporary log DLL's 

MonitorListFile Locations String Database containing monitor settings 

Administrators Operations String Specification of accounts and groups 

with administrative access to configure 

and manage the MonitorMagic service 

Operators Operations String Specification of accounts and groups 

with operational access to the 


Users Operations String Specification of accounts and groups 

with user access to the MonitorMagic 

service 

FromAddress Operations String SMTP E-mail address of the 

MonitorMagic service, used when 

sending E-mail messages 

SmtpServer Operations String Specification of E-mail server used by 

MonitorMagic service to send SMTP E- 

mail messages (xxx.xxx.xxx.xxx or DNS 

name) 

Keywords Operations Binary Keyword specification 

DatabaseMaintenanceDelay Operations 

DWORD The delay in seconds used by the 

MonitorMagic service to perform 

database maintenance on an interval 

basis. Maintenance is required only 

when using the MS Access database. At 

the specified intervals, the database is 

closed and re-opened to release 

memory in use by the Jet engine. By 

default (value not specified) 

MonitorMagic uses a value of 3600 

(every hour). The minimum value that 

271


can be specified is 60 seconds. 

Debug Operations DWORD Specifies debug log level. When debug 

logging is enabled, the MonitorMagic 

service will generate more logging 

messages written to the Application log 

of the computer. Possible values are: 

0: Debug logging not enabled (default, 

value used when key not specifed) 

1: Debug logging enabled. 

LicenseKey UserInfo String License code (purchased version) or 

"DEMO" 

For more information on service registry configuration settings, see checking the service registry 

configuration (Windows NT 4.0, Windows 2000). 

272

MonitorMagic topics 

Configuring the MonitorMagic service 

Most configuration settings in MonitorMagic are specified at the server level. To change 

configuration settings, you use the MonitorMagic user interface client application. To configure 

the MonitorMagic service, activate the Network view window and browse to find the computer 

running the MonitorMagic service. Right click the computer name and select menu option 

Configure service. A window with multiple tabs is shown. Each tab corresponds with a certain 

taks that can be configured. For Advanced configuration options, press the Advanced button. 

The tab shows buttons for each tasks you can access and configure. 

Note that you need to be an MonitorMagic administrator to access each of these options. 

See also: 




Access Rights 

Different types of access rights 

MonitorMagic uses Windows2000/NT security to secure its access and operations. The following 

MonitorMagic aspects relate to security: 

273


MonitorMagic service account 

The MonitorMagic service(s) use(s) a Windows 2000/NT user account to perform its tasks. This 

service account must have sufficient privileges to perform these tasks. Normally, if the service 

account is a member of the Administrators group, the service account has sufficient privileges. 

You can specify the name of the service account and the group to which the account must be 

made a member of during service setup. If the service account does not have sufficient access 

rights, to the MonitorMagic service, it will not be able to perform all of its tasks. If this happens, 

the MonitorMagic service will generate application log messages describing the situation. 

Managing and configuring MonitorMagic 

To use and manage MonitorMagic, you need to have sufficient MonitorMagic access rights. Three 

types of MonitorMagic users exist: 

MonitorMagic administrators 

MonitorMagic administrators have all access rights to the MonitorMagic service. 

MonitorMagic operators 

MonitorMagic operators have all access rights to the MonitorMagic service but they cannot 

change and configure the MonitorMagic access rights. Access rights include the rights to apply 

monitor policies, change monitor scheduling, rules and alarm actions. 

MonitorMagic users 

MonitorMagic users can only look at results but cannot change anything in MonitorMagic. 

See also: 


Specifying MonitorMagic access rights 


Specifying MonitorMagic access rights 

To specify the MonitorMagic access rights, start the MonitorMagic client. In the Network view 

window browse to find the computer running the MonitorMagic service. Right click the computer 

name and select menu option Configure service. 

274


Select tab Service access rights. In the window, you can enter the users and groups who 

should have MonitorMagic access rights. In each field you can enter any number of Windows 

NT/2000 user or group accounts, separated by comma's. Changes become effective when you 

press the OK button. 

See also: 


Different types of access rights 


Keywords 


Keywords can be used to specify text in various parts of MonitorMagic. The actual text is 

generated at runtime. Keywords can be used in alarm actions. For instance, you can configure an 

E-mail alarm action message to contain the actual value of a performance counter by specifying a 

keyword. At the moment you define the contents of the message, the actual value of the 

performance counter (when the alarm action is executed) is not known. So you cannot specify the 

value. Instead, you specify a keyword, representing the performance counter value. 

Further, you might want to use keywords to specify text values that change on a regular basis. 

Instead of changing the text values themselves, you only need to change the keyword contents. 

Example: suppose you want MonitorMagic to send popup messages whenever a rule is triggered. 

The destination of these messages is the computer account of the Administrator on duty. This 

implies that the actual popup message destination can differ from time to time. Instead of 

changing the destination of the popup message alarm actions, specify a keyword s the 

destination; for instance, %ADMIN_ON_DUTY_SYSTEM%. Now you only need to change the 

contents of the keyword to redirect the popup messages to the right machine. 

275


Keywords have a Keyword name and a Keyword value. The Keyword name identifies the 

keyword. Normally, the keyword is written in uppercase characters and starts and ends with 

an %-character. The Keyword value is the contents of the keyword. For monitor values, the 

keyword contents are retrieved at runtime. For other keywords, the keyword value can be 

specified by using the MonitorMagic client. 

See also: 

Monitor keywords 

Custom keywords 


All monitor values can be used as keywords. Monitor keywords are generated automatically by 

MonitorMagic and can be selected in various windows. All monitor value keywords have the 

form %RESULT_DATA_name%, where name is the name of the monitor value. For a disk 

monitor the name of the disk is represented by the keyword: %RESULT_DATA_DISK_NAME%. 

See also: 

E-mail message contents 




Custom keywords are stored by each MonitorMagic service. To find the custom keywords and 

configure them, start the MonitorMagic client. In the Network view window browse to find the 

computer running the MonitorMagic service. Right click the computer name and select menu 

option Configure service. Select tab Custom keywords. 

276


Use the Add, Edit, and Delete buttons to change or define custom keywords. Changes become 

effective when you press the OK button. 

See also: 



SNMP 


MonitorMagic supports SNMP in the following three ways: 

SNMP trap alarm action: When a rule of a monitor is triggered, MonitorMagic can 

execute an alarm action by sending a user defined SNMP trap. Normally the trap 

destination is another monitoring - management package. The MonitorMagic service 

sends the trap as defined by the monitor specification. See Introduction SNMP traps for 


SNMP trap monitor: The MonitorMagic service can receive SNMP traps that are send 

by other systems or processes. This is done by using a Snmp trap monitor. In this case, 

somewhere in the network, a device, system or process generates and sends a SNMP 

trap. The MonitorMagic service is the destination of the trap. MonitorMagic uses the 

Snmp trap monitor to process the received trap. Once the trap is received by the 

MonitorMagic service, rules can be applied and the MonitorMagic service can take further 

action. See Snmp trap monitor: Overview for more information. 

SNMP get monitor: MonitorMagic can retrieve information from any other device that 

supports SNMP. MonitorMagic uses the Snmp get monitor to accomplish this task. In 

this case, MonitorMagic has one or more Snmp get monitors defined. Each monitor 

collects information from the SNMP host. This information is then used for further 

processing by the MonitorMagic service. See Snmp get monitor - Overview for more 

information. 

SNMP Version support 

Two version of SNMP exist: SNMP version 1 and SNMP version 2. MonitorMagic support SNMP 

version 1. 

See also: 







MonitorMagic support SNMP in three ways: sending SNMP traps (1), receiving SNMP traps (2) 

and collecting SNMP information (3). See MonitorMagic SNMP support for more information. This 

topic describes the requirements to support each of these functions. 

The following components can be part of the MonitorMagic SNMP installation: 

MonitorMagic service: The MonitorMagic service can send and receive traps and collect 

SNMP information from any host that supports SNMP. This service is required for all 

functions. 

277


 

 

Microsoft's SNMP service: This service enables SNMP support for the computer it runs 

on. The service is part of Windows XP/2000/NT but not installed by default. When 

required, the service must be installed on the computer that runs the MonitorMagic 

service. 

Microsoft's SNMP trap service: The service captures all SNMP traps send to the 

machine it runs on and requires the Microsoft's SNMP service to run. 

MonitorMagic function - Component 

Microsoft's SNMP 

service 

Microsoft's SNMP trap 

service 

Send SNMP traps (SNMP trap alarm 

action) 

Required, running 

Not required 

Receive SNMP traps (Snmp trap monitor) Required, running Required, running 

Collect SNMP data (Snmp get monitor) on 

Windows XP/2000 

Collect SNMP data (Snmp get monitor) on 

Windows NT 

Not required 

Installed, running or not 

running 

Not required 

Not required 

To install the Microsoft's SNMP service and Microsoft's SNMP trap service, see Installing the 

SNMP service for more information. 

MonitorMagic client 

To ease the configuration of SNMP, the MonitorMagic user interface application also supports 

some functions to collect SNMP information. See Snmp get monitor - Overview for more 

information. When running on Windows XP/2000, no special requirements apply. When running 

on Windows NT, the Microsoft's SNMP service must be installed in order to use these functions. 

See also: 

Installing the SNMP service 





SNMP traps 

Introduction to SNMP traps 

Explanation of SNMP Traps 

SNMP provides the ability to send traps, or notifications, to advise an administration application 

when one or more conditions have been met. Traps are network packets that contain data 

relating to a component of the system sending the trap. Traps are generated when a condition 

has been met on the SNMP agent. After the condition has been met, the SNMP agent then forms 

an SNMP packet and sends it to UDP port 162. On Windows 2000/NT, MonitorMagic, in 

combination with the standard SNMP service of Microsoft, is such an agent. 

SNMP manager applications are able to receive and interpret these messages, and optionally 

perform actions as a result. Examples of such products are: MonitorMagic (tools4ever), HP 

Openview (Hewlett Packard), NMC4000 (DEVELCON), Compaq Insight Manager (Compaq), and 

many more. 

278


MonitorMagic SNMP traps as an alarm action 

When a rule of a monitor in MonitorMagic is triggered, MonitorMagic will execute the alarm 

actions that are configured in the rule. In addition to for example the possibility to send a 

notification in the form of email message, MonitorMagic is able to send a notification in the form of 

an SNMP trap message. MonitorMagic will contact the Microsoft SNMP Service, and instruct it to 

create a SNMP trap containing as information a message string provided by MonitorMagic. An 

SNMP manager application will be able to receive this message, and act on its contents. See 

SNMP Trap message detailed contents for details. 

See also: 

MonitorMagic and SNMP traps 

Architecture SNMP traps 



SNMP trap as alarm action 

MonitorMagic and SNMP traps 

MonitorMagic uses the SNMP service from Microsoft for SNMP traps. The SNMP service is part 

of Windows 2000/NT but not installed by default. See Installing the SNMP service for more 

information. The following table shows the services and network resources that are used for 

SNMP traps: 

Service - network 

resource 


SNMP service 

SNMP Trap service 

SNMP Manager 

Location 

Description 

Computer A Required - When the MonitorMagic service wants to 

send a trap, it creates the contents of the trap and 

starts communicating with the SNMP service. 

Computer A Required - The SNMP service running on the same 

computer as the MonitorMagic service receives 

information from the MonitorMagic service and send the 

trap to one or more destinations in the network. 

Computer B Optional - The SNMP Trap service captures all SNMP 

traps that are send to the computer it runs on. No other 

service or application running on the same computer 

will be able to receive SNMP traps directly. Instead, 

other services and applications can communicate with 

the SNMP trap service to receive traps. 

Computer B Optional - The SNMP manager is the end point of the 

SNMP trap and presents the trap information to the end 

user or processes the trap for future use. The SNMP 

Manager can operatie ins two ways: 

1. Interface with the SNMP Trap service. In this case, 

the SNMP Trap service receives the traps. The SNMP 

Trap service must be installed and running. 

2. Receive the trap directly. In this case, the SNMP 

Trap service must not be running on the computer. 

(if the SNMP Trap service would run, the trap will be 

intercepted by the trap service and never reach the 

279


SNMP Manager application. 

See also: 







The following criteria must be met in order to use SNMP traps with MonitorMagic. 

In order for MonitorMagic to be able to send SNMP traps, the Microsoft SNMP service 

must be installed and configured on the machine that runs the MonitorMagic service and 

issues the trap. The Microsoft SNMP service is a standard service of Windows 2000/NT, 

but is not been installed by default. See Installing the SNMP service for more information. 

Depending on how you want to use a SNMP Manager application, the SNMP Trap 

service must be either started or stopped. See MonitorMagic and SNMP traps for more 

information. 

The MonitorMagic service must be configured to support sending SNMP traps. See 

Configure MonitorMagic SNMP traps for more information. 

If your SNMP management application does not receive the trap message, you may want to try 

starting or stopping the SNMP Trap Service on the computer that runs your Management 

application. It depends on the implementation of your SNMP management software if this service 

should be running or not on that computer. 

See also: 




Testing MonitorMagic SNMP traps software 

Troubleshooting MonitorMagic SNMP traps 




Installing the SNMP service 

In order for MonitorMagic to be able to send SNMP traps, the Microsoft SNMP service must be 

installed and configured on the machine that runs the MonitorMagic service. This section 

descibes hot to install the SNMP service. The installation will automatically install the SNMP 

Trap service. The installation is different for Windows NT and Window 2000: 

Windows NT: 

To install the SNMP service, select the network applet from the control panel, select the 

services tab, and click on add. From the list choose the SNMP service. Follow the instructions. 

Windows 2000: 

280


To install the SNMP service, choose the Add/Remove Programs applet from the control panel, 

and then click Add/Remove Windows Components. Click Management and Monitoring tools, 

but do not select or clear its check box. Click Details. Select the "Simple Network Management 

Protocol check box, and click OK. Then click Next. and follow the instructions. 

In order for a SNMP Management application to receive trap data sent by the SNMP Service, The 

SNMP Service must be configured to forward the trap to the specific computer. To configure 

these destinations do the following: 

Windows NT: 

Select the network applet from the control panel, select the services tab From the list choose 

the SNMP service, and select Properties. Select the Traps tab, and list the machine that runs 

your SNMP management application. 

Windows 2000: 

Open the control panel, select services, select the SNMP Service, and select properties. Follow 

the instructions. 

When the SNMP service on the machine running the MonitorMagic service is started, it will 

generate a general trap indicating that the SNMP node has started. If your SNMP Management 

application receives this trap then the Microsoft SNMP service is configured correctly, and you 

can start with Configure MonitorMagic SNMP traps. 

If your SNMP management application does not receive the trap message, you may want to try 

starting or stopping the SNMP Trap Service on the computer that runs your Management 

281


application. It depends on the implementation of your SNMP management software if this service 

should be running or not on that computer. 


In order to be able to use SNNP traps as alarm actions, you must do a one-time configuration 

action on the specific MonitorMagic service, to let it integrate with Microsoft's SNMP Service. See 

Requirements SNMP traps for information how to install and configure that service first. 

To configure MonitorMagic for SNMP traps, open the Network view window and browse to find 

the computer running the MonitorMagic service. Right click the computer name and select the 

menu option Configure service. In the configuration window, select the advanced tab, and click 

the button "SNMP traps". You will be presented the following window: 

When the current status is "not configured", as above, press "configure SNMP". 

When the configuration was successful the status will change in OK. During the configuration 

some registry settings of the SNMP service will be modified, and the SNMP service will be 

restarted. 

To send a test SNMP trap, press the Test SNMP trap button, and a SNMP trap with a standard 

message will be send. When this succeeds the configuration is ready and you can start using 

SNMP traps as alarm actions. Note that you can also test SNMP messages from the 

corresponding tab in the Alarm action in the rule, see Testing MonitorMagic SNMP traps software. 

Note: If you press Test SNMP trap and get a succesfull response, this means that the 

MonitorMagic service was able to generate a SNMP trap and deliver the trap to the Microsoft 

SNMP service running on the same computer. This does not guarantee that the trap is receievd 

by another SNMP management application. 

See also: 

282











When you have created a SNMP alarm action, either by editing an existing SNMP trap alarm 

action or creating a new SNMP trap alarm action, you can test that your SNMP configuration is ok 

by selecting the tab Test SNMP trap. You can here send a test trap to verify that all is working 

correct. See Troubleshooting MonitorMagic SNMP traps for more info. Alternatively you can send 

a test message when you Configure MonitorMagic SNMP traps. 

Trap message 

The descriptive test message that is send as a part of the SNMP trap. 

283



The MonitorMagic service that will generate the trap. 

Note: If you press Send SNMP trap and get a succesfull response, this means that the 

MonitorMagic service was able to generate a SNMP trap and deliver the trap to the Microsoft 

SNMP service running on the same computer. This does not guarantee that the trap is receievd 

by another SNMP management application. 

See also: 










Checklist MonitorMagic SNMP traps. 

 

 

 

 

Verify that the Microsoft's SNMP service is installed and running on the machine ( see 

Requirements SNMP traps) before configuring MonitorMagic. 

Verify that in the SNMP service configuration, the computer that runs your SNMP 

management application is configured as destination for the traps. ( see Requirements 

SNMP traps) Test this by stopping and starting the SNMP Service on the computer 

running the MonitorMagic service. On startup the SNMP service will generate a trap that 

indicates its startup, and this should be detected by your SNMP manager. 

Note that for your SNMP management program to receive traps, it may be required that 

the SNMP trap service is running on the computer that runs the SNMP management 

program. See the documentation with your SNMP management program if this service 

must or must not be running. The SNMP trap service is installed automatically when you 

install the SNMP service, but can be run independently. The SNMP trap service is not 

required for MonitorMagic to generate traps. 

Make sure you have once configured the MonitorMagic service to use SNMP (see 

Configure MonitorMagic SNMP traps). During this process, the MonitorMagic service will 

automatically create a registry value, and stop and restart the SNMP service. 

Key:HEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SNMP\Parameters\E 

xtensionAgents 

Valuename: 

Value: SOFTWARE\Tools4ever\MonitorMagic\Service\SnmpTrap 

This value refers to another registry key in which the location of an Extension dll is 

located: 

Key : 

HKEY_LOCAL_MACHINE\SOFTWARE\Tools4ever\MonitorMagic\Service\SnmpTrap 

284


Valuename: Path 

Value: 

This dll is loaded by the SNMP service on startup. 

 

 

Check that these variables are set OK. In order to set the registry variable correctly, the 

account that the MonitorMagic service runs with should have full access rights to this key. 

If the account does not have sufficient rights, this will be logged in the application 

eventlog. Usually if the MonitorMagic service account is a member of the local 

administrators, is has sufficient rights . It is however possible that specific security 

restrictions have been applied to the key by a system administrator. To check this, start 

"regedt32" from the command line, and choose "security" from the menu to see the 

security settings of the selected keys. 

Check that the mentioned dll is in the location that is listed. If this is not the case it may 

have been deleted. You should then reinstall the MonitorMagic service. 

Removal of the SNMP trap integration of MonitorMagic 

If for any reason you want to undo the integration of MonitorMagic with the SNMP service of 

Microsoft manually, this can be done as follows: 

Delete from the registry the "valuename" with that contains the listed value. Do not delete 

entries with a different value. 

Key: 

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SNMP\Parameters\Exte 

nsionAgents 

Valuename: 

Value: SOFTWARE\Tools4ever\MonitorMagic\Service\SnmpTrap 

 

Next restart the SNMP service. 

See also: 








SNMP trap 

When a rule of a monitor is triggered, alarm actions are executed. See Alarm actions overview for 

more general information. One of the possible alarm actions is a SNMP trap. A SNMP trap is a 

special SNMP Message that is send from the MonitorMagic server to specific computers on your 

network that runs software (called an SNMP manager) that can interpret these messages, and 

act on them if required. See Introduction SNMP traps for more general info. 

In order for the SNMP traps to work, SNMP must be configured on the server that the policy 

containing this alarm action is applied. see Requirements SNMP traps and Configure 

MonitorMagic SNMP traps for more information. 

See also: 


285








Escalation 



SNMP traps in MonitorMagic are implemented by means of an extension dll for the SNMP service 

of Microsoft. When the Microsoft SNMP service starts, it will locate the dll, and run it as part of the 

SNMP service process. On startup, the dll will create one "event" and one "mailslot" object for 

communication with the MonitorMagic service. 

When the MonitorMagic service decides it must initiate a SNMP trap (for instance as a result of 

configured alarm action), it will write the specific information to the "mailslot" object on the server 

and set an "Event". The SNMP service detects this and will activate the Extension dll. The 

extension dll will then read the information from the "mailslot" object, and instruct the SNMP 

service to create the requested SNMP trap(s). 

This all happens locally on the computer where the MonitorMagic service runs. The SNMP 

Service can be configured to forward the trap to the computers where your SNMP Management 

Program runs. 

See also: 





The following information is meant only for administrators of SNMP management applications that 

want to know the detailed contents of the SNMP trap sent by monitor magic. It describes the 

detailed contents. General knowledge of SNMP traps is assumed. This information is not required 

for configuring MonitorMagic. 

The SNMP Trap event that MonitorMagic generates will have following fields: 

SNMP Version: v1 

Community: Community name of the SNMP agent (defined in Microsoft's SNMP Service) 

PDU TYPE: SNMPvX Trap (4) 

Enterprise: Corporation or organization that originated the trap. This is the Oid: 

1.3.6.1.4.1.11392.1(iso.3.6.internet.private.enterprises.tools4ever.monitormagic) 

Agent Address: IP address of the SNMP agent 

Generic Trap Type: Enterprise. 

Specific Trap Type: 1 

Timestamp: the value of object sysUpTime when the event occurred. this is the startup time since 

the start of the Microsoft SNMP service 

Variable argument list. This is a list of parameter definitions and values. This list contains detailed 

specific information about the event that caused the trap to be send. In this case it is only one 

variable, that contains the exact message string that can be specified in the SNMP trap alarm 

action in MonitorMagic. The variable is the following: 

286


ObjectOid : 1.3.6.1.4.1.11392.1.1.2.0 

(iso.3.6.internet.private.enterprises.tools4ever.monitormagic.1.2.0) 

type: Octet string. 

value: 

Note that since this is the only string variable it is normally automatically correct interpreted and 

displayed by a SNMP management application. 

For more information see the documentation with your specific SNMP management Application. 

See Also: 





SNMP trap 

Pager - SMS 






you need to install and configure the modem and specify some settings in MonitorMagic. 

General operation 

The following list describe the actions executed by MonitorMagic service and provider when 

sending a pager - SMS message: 

A monitor is checked by the MonitorMagic service. A monitor rule is triggered and and 

pager - SMS alarm action must be executed. 

The MonitorMagic service queues the pager - SMS alarm action. 

The MonitorMagic initializes the connected modem and calls the configured pager - SMS 

provider. 

When the connection is setup, the MonitorMagic service instructs the provider to send a 

message to the specified pager - mobile telephone number. 

MonitorMagic terminates the call with the pager - SMS provider and is ready to send the 

next pager - SMS message. 

The pager - SMS provider sends the message and the pager or mobile telephone 

receives the message. 

Note: Many mobile telephones and pagers can receive E-mail messages. If your mobile 

telephone or pager can receive E-mail messages you can also use this feature with MonitorMagic. 

In this case, you need to configure E-mail alarms. Contact your pager - mobile telephone provider 

to find out if your mobile telephone - pager is able to receive E-mail messages. 

See also: 







287





The installation and configuration procedure to use pager - SMS message is simple and 

straightforward. To ease the installation and configuration procedure, MonitorMagic is capable of 

sending a test message to the pager - mobile telephone. 

Requirements 

You need to have a modem connected to the server or the server must have a built-in 

modem card. In case the modem is not already installed, you need to have the software 

to install the modem. 

The modem must be connected to a telephone line that is capable of calling an outside 

line. 

The MonitorMagic service must be running on the server. 

Installation and configuration procedure 

The following list summarizes the installation and configuration procedure to send pager - SMS 

messages. 

Install and configure the modem on the server. Note that you can also install the modem 

to a workstation. 

Configure the MonitorMagic service to use a provider to send pager - SMS messages. 

Note that MonitorMagic contains predefined configuration settings for many providers 

world-wide. 

If necessary, adjust the configuration settings of the provider. 

If necessary, configure the settings for your provider. This step is only required when 

MonitorMagic does not already contains the settings for your provider. 

Send a test message to your pager - mobile telephone. 

Configure alarm actions to send pager -SMS messages. 

See also: 










To start the installation and configuration of pager - SMS messaging, you need to install the 

modem on the computer that runs the MonitorMagic service. The modem must be connected to 

the computer that runs the MonitorMagic service and the modem must be connected to a 

telephone line. 

The installation and configuration and the modem depends on the modem. For most modems, 

you can simply connect the modem to the computer and use the operating system software to 

detect and configure the modem. Some specific modems require special modem software to 

install and configure the modem. In this case, the required modem software is available from the 

modem manufacturer. 

288


As an example, the configuration is described for a computer running Microsoft Windows NT 4.0. 

For Windows 2000 and Windows XP the procedure is similar. Open the Control panel and 

double click Modems. Follow the procedure to detect the modem. The result is shown in the 

following picture. 

The Dialing properties are not used by MonitorMagic and do not need to be configured. Press 

the Properties button to specify the modem communication settings. 

Important: The modem communication settings depend on the provider used to 

send pager - SMS messages. MonitorMagic contains these communication 

settings for many providers. In case your provider is not listed, you should try the 

most common settings or contact your provider for more information. 

Select the speed to be used for the communication. As a general rule, 9600 baud is a good 

choice and works for most providers. But some providers require other speeds. 

289


Next, select the Connection tab. The following window is shown. Use the window to specify the 

modem communication settings. 

290


The connection settings depend on the provider. As a general rule you can use the following 

settings: 

USA: Data bits: 7, Parity: Even, Stop bits: 1 (7,e,1) 

Non-USA: Data bits: 8, Parity: None, Stop bits: 1 (8,None,1) 

MonitorMagic contains these communication settings for many providers. In case your provider is 

not listed, you should try the most common settings or contact your provider for more information. 

When ready, press OK. 

See also: 











Once the modem is installed and configured, you need to configure the MonitorMagic service to 

use the modem and a pager - SMS provider. Start the MonitorMagic client. Open the Network 

view window and browse to find the computer running the MonitorMagic service. Right click the 

291


computer name and select the menu option Configure service. In the configuration window, 

select the advanced tab, and click the button "Pager - SMS". You will be presented the following 

window: 

From the window you can select the pager - SMS provider and modem. The dialog contains the 

following fields: 

Available provider configuration settings 

The list with provider known by the MonitorMagic service. MonitorMagic ships with a number of 

predefined provider configuration settings. If your provider is not listed, you can add an extra 

entry. When shown, the dialog shows the provider currently used by the MonitorMagic service. To 

see the configuration settings for the selected provider, press the Manage button. 

Configure modems 

The list with modems installed on the computer running the MonitorMagic service. If the list 

contains no entries, there are no modems installed on the computer. See Pager - SMS 

installation and configuration overview for more information. From the list, select the modem that 

must be used by the MonitorMagic service when sending pager - SMS messages. 

Note: If you computer is equipped with a ServerSMS GSM Device from Anrich Systems, 

and the software for the device has been installed, the list Configured modems contains 

the entry ServerSMS GSM Device. When you select this entry, the MonitorMagic service 

will send SMS messages using the ServerSMS GSM Device. 

OK 

Accept any changes made and exit the dialog. 

Cancel 

Discard any changes made and exit the dialog. 

Manage 

Add, change or view the available pager - SMS provider configuration settings. 

Test 

Send a test message using the selected provider and modem. When the button is pressed, 

MonitorMagic will ask for the number of the pager - mobile telephone to be called. While sending 

the test message, the MonitorMagic service will append log information to the file PagerSms.log 

that can be found in the MonitorMagic data directory. 

See also: 


292











MonitorMagic ships with a number of predefined configuration setting for many pager - SMS 

providers. You can view and change these configuration settings and add settings for other 

providers. Start the MonitorMagic client. Open the Network view window and browse to find the 

computer running the MonitorMagic service. Right click the computer name and select the menu 

option Configure service. In the configuration window, select the advanced tab, and click the 

button Pager - SMS. Press the Manage button. You will be presented the following window: 

The window contains all provider settings known by the MonitorMagic service. You can add and 

change provider configuration settings from this list. To ease selecting a provider, the providers 

are sorted by name of country first. For a description of the different fields shown for each 

provider, see Pager - SMS adding provider configuration settings 

Important: The provider number is the phone number called by the MonitorMagic 

service when sending a pager - SMS message. If the MonitorMagic needs to dial a 

certain number to call an outside line, you will need to change the provider 

number. The MonitorMagic service will only 'dial' the provider number. 


Add 

Press to add the configuration settings for a provider that is not in the list. 

Edit 

Press to change the configuration settings of the provider that is currently selected in the list. 

293


Delete 

Delete the selected entries from the list. 

OK 

Accept any changes made and exit this window. 

Cancel 

Discard any changes made and exit this window. 

See also: 











MonitorMagic ships with a number of predefined configuration setting for many pager - SMS 

providers but you can also add your own configuration settings or change existing settings. To do 

so, start the MonitorMagic client. Open the Network view window and browse to find the computer 

running the MonitorMagic service. Right click the computer name and select the menu option 

Configure service. In the configuration window, select the advanced tab, and click the button 

Pager - SMS. Press the Manage button. To create a new entry for a provider press the Add 

button. To change the settings for an existing entry, select the entry and press the Edit button. 

See Pager - SMS managing provider configuration settings for more information. You will be 


The window contains all relevant settings for a single pager - SMS provider in the following fields: 

Provider name 

294


Name of the provider as shown in the list. The field is only used by MonitorMagic to reference the 

provider. You can specify any name, for instance: SMS-provider. 

Provider number 

The phone number of the provider. The number can contain blanks to wait a little time before 

dialing the next number. 

Important: The provider number is the phone number called by the MonitorMagic 

service when sending a pager - SMS message. If the MonitorMagic needs to dial a 

certain number to call an outside line, you will need to change the provider 

number. The MonitorMagic service will only 'dial' the provider number. 

Provider password 

The password used by the provider when a call is setup. This field is rarely used. 

Modem configuration 

This modem configuration field specifies the modem communication settings. 

Important: You should enter these settings in the Connection tab described in 

Pager - SMS modem installation and configuration. By convention the following 

notation is used: [Number of data bits],[Parity specification],[Stop bits]. Example: 

7,e,1. 

Protocol 

Select the protocol to be used. This should be either UCP, TAP or Text. The protocol defines the 

rules used by the MonitorMagic service to communicate with the pager - SMS provider. 

General rules 

If you do not know the exact provider settings, you can use the following guidelines: 

USA: Modem configuration: 7,E,1, protocol: TAP 

Europe: Modem configuration: 8,N,!, protocol: UCP or TAP. 

Vodaphone, used in Australia and some counties in Europe: Protocol: Text. 

See also: 















you need to install and configure the modem and specify some settings in MonitorMagic. See 

Introduction to pager - SMS and subsequent topics for more information. To configure an pager - 

SMS alarm action, continue reading. 

For an pager -SMS alarm action you need to specify at least the recipient number and message. 

295



Recipient 

The number of the pager - mobile telephone called by the pager - SMS provider. Note that for 

most configurations, this number is not called by the MonitorMagic service directly. 

Sender 

The sender number. Most provider show this number as part of the pager - SMS message. Note 

that you don't have to specify this number. 

Message 

The message sent to the pager - mobile telephone. You can use keywords as part of the 

message. 

Keyword - Insert 

Use these fields to insert keywords into the message contents. 

Generate log file when sending message 

296


For troubleshooting purposes, you can check this option to let the MonitorMagic service write log 

information to a file when executing the alarm action. The file is called PagerSms.log and can be 

found in the MonitorMagic service data directory. 

See also: 





Escalation 











For the TAP protocol, MonitorMagic uses a script that describe how the computer and the 

provider communicate. The script is stored in a file shipped with MonitorMagic. If your provider 

uses the TAP protocol and the default script does not work, you can edit the script. In this case, 

for most circumstances, you will need to make minor adjustments to make the script work. If you 

need help in this matter, please contact your MonitorMagic reseller or Tools4ever: 

support@tools4ever.com. 

The MonitorMagic pager - SMS script file is called: TapScript.sci and can be found in the 

MonitorMagic service directory. To edit the script file, use a standard ASCII editor, for instance 

notepad.exe. Warning: Do not open the script file in advanced Word processing 

applications like Microsoft Word etc. 

When MonitorMagic calls the provider, the script is executed. The script contains two sections: 

Parameter initialization section 

Script execution section. 

Parameter initialization section 

This section defines the mapping of characters and corresponding ASCII codes as sent and 

received by the provider. If these mappings are not standard, they should be defined in this 

section. Each mapping should be specified in braces on a single line as shown in the following 

example: 

{CR=0x0D} 

{ACK=0x06} 

Script execution section 

The script execution section contains a number of commands. Each command normally consists 

of three lines: 

Command ID, an integral number followed by a colon. The line is used in goto 

statements. Example: 14: 

Command. A command is a single word and must be specified in brackets. See the next 

table for all possible commands. 

A parameter associated with the specified command. See the next table for possible 

parameters. 

297


Script execution command table: 

Command Parameter Example (parameter) Description 

[wait] 

[receive] 

[repeat] 

[success] 

[fail] 

[send] 

Number of 2000 Wait the specified time in 

milliseconds to wait 

milliseconds. 

The characters that 

should be received 

The number of 

retries 

goto [Command 

ID] 

goto [Command 

ID] 

: receive any character 

ID= 

 

Wait for characters to be 

received. You can wait for any 

character of specific characters 

to be received. 

3 Repeat the [receive] command 

that follows in one of the next 

lines the specified number of 

times. The [receive] command 

is repeated only, if the receive 

action fails. 

goto 19 

If the [receive] command that 

follows in one of the next 

lines is executed successfully, 

jump to the specified location in 

the script. 

The [success] command must 

also be used after the 

[or_receive] command. 

goto 19 

If the [receive] command that 

follows in one of the next 

lines fails, jump to the specified 

location in the script. 

The [fail] command must also 

be used after the [or_receive] 

command. 

The characters that 

Send the specified characters. 

must be sent to the PG1%password% 

provider. 

[or_receive] The characters that 

can be received 

instead of the 

characters 

specified in the 

previous [receive] 

command. If these 

characters are 

received, the 

preceding [receive] 

command and this 

[or_receive] 

command are 

executed 

successfully. 

[p 

Accept the specified characters 

as valid characters to be 

received instead of the 

character specified for the 

previous [receive] command. 

Note: The [or_receive] 

command must be followed 

by a [success] and [fail] 

command. 

When using the [send] command, additional keywords can be used. The corresponding ASCII 

characters for these keywords are calculated at runtime. 

Keyword Example Description 

%password% [send] The passwo 

298


%number% 

%message% 

PG1%password% 

[send] 

%number% 

[send] 

%message% 

the provider 

specified. No 

Most provide 

not use 

passwords. 

The number 

the pager or 

mobile phon 

want to send 

message to. 

The messag 

want to send 

, [send] 

Send the 

%number%%message% contents bet 

the 


5: 

[fail] 

goto 6 

6: 

[send] 

 

7: 

[receive] 

ID= 

8: 

[repeat] 

3 

9: 

[success] 

goto 16 

10: 

[fail] 

goto 4 

11: 

[send] 

PG1%password% 

12: 

[receive] 

 

13: 

[or_receive] 

[p 

14: 

[success] 

goto 19 

15: 

[fail] 

goto 4 

16: 

[success] 

goto 19 

17: 

[fail] 

goto 9 

18: 

[receive] 

[p 

300


19; 

[send] 

%number%%message% 

20: 

[success] 

goto 23 

21: 

[fail] 

goto end 

22: 

[receive] 


 

 

Check if the COM-port is configured correctly. 

Check if the modem has been configured in MonitorMagic. See Pager - SMS installation 

and configuration overview for more information. 

When there is some activity but no message is received: 

Check the Eventviewer, Application log for error messages. 

Enable the option to generate a log file when sending pager - SMS messages and try 

again. 

Try some other modem connection settings. See General rules in topic Pager - SMS 

adding provider configuration settings for more information. 

When using the TAP protocol, check the log file and the script. See Pager - SMS script 

for more information. 

See also: 










Database 


MonitorMagic can use a database for different purposes: graphs, historical data, reports and so 

on. You can run MonitorMagic with an without using a database. A database is required when 

you want to use the following functionality of MonitorMagic: 

Graphs showing historical data. 

Most reporting functionality 

Trending and analysis. 

MonitorMagic supports different types of databases: MS Access (Jet-engine), SQL Server and 

most other ODBC compliant databases. The database can reside on the same computer as the 

MonitorMagic service or it can be installed on a remote computer. MonitorMagic always uses a 

system data source to access the database. The system data source is created by 

MonitorMagic automatically. The database setup procedure is simple and straightforward. During 

the database setup, MonitorMagic can create the database or connect to an existing database. 

The database software needs to be installed on the computer before MonitorMagic can create 

and use the database. 

See also: 










302




MonitorMagic supports the following database types: 

SQL Server 2000 

SQL Server 7.0 

SQL Server 6.5 

MS Access 2000 

MS Access 97 

Microsoft Jet Engine (free) 

Most ODBC compliant database. 

Microsoft Jet Engine 

The Microsoft Jet Engine is part of the MDAC (Microsoft Database Access Components) which is 

available for free from the Microsoft web site: www.microsoft.com. If you do not have a license for 

SQL Server or MS Access you can still use a database with MonitorMagic by installing the MDAC 

software. Note that the listed MS Access database types also use the Microsoft Jet Engine. If you 

have MS Access installed, the Microsoft Jet Engine is automatically installed as well. In 

subsequent topics the Microsoft Jet Engine is referred to as MS Access. 

Note: With Windows 2000 and Windows XP, the Microsoft JET Engine is automatically 

installed. You do not need to install any additional software for these operating systems if 

you want to use the MS Access database. For Windows NT 4.0, you need to install the 

MDAC software. For MDAC versions 2.6 and higher you also need to install the Jet engine 

software. See the Microsoft web site for more information. 

See also: 



MonitorMagic fully supports the usage of the MS Access database. Using the MS Access 

database is recommended for small installations although you can also use the MS Access 

database in a larger environment. To setup and start using the MS Access database you need to 

have MS Access installed on the computer running the MonitorMagic service. If you are using 

multiple MonitorMagic services with database support, you need to have the MS Access software 

installed on each computer. 

Note that MS Access uses the Microsoft Jet Engine as the underlying database. You can obtain 

the Microsoft Jet Engine for free from the Microsoft web site. The Jet Engine is part of the 

Microsoft Data Access Components (MDAC) software. Visit www.microsoft.com for more 

information. Once downloaded, you can install the MDAC software an then configure 

MonitorMagic to use the database. 

When using the Microsoft Jet engine database, the database engine can use a considerable 

amount of memory. To release this memory, the MonitorMagic service from time to time closes 

and re-opens the connection with the database. This procedure is repeated every hour by default. 

To change the interval delay, you need to edit the registry. See MonitorMagic service registry 

settings and please Microsoft's knowledgebase article Q154384 for more information. 

See also: 


303



SQL Server is the recommended database for larger installations. MonitorMagic supports 

versions 6.5 and higher of SQL Server, including version 7.0 and version SQL Server 2000. 

Before you configure MonitorMagic to use SQL Server, SQL Server must be installed. SQL 

Server can be installed on the computer running the MonitorMagic service or on any other 

accessible computer. 

If you are using multiple MonitorMagic services, you can use a single SQL Server database. The 

MonitorMagic services can be configured to store all data in the same SQL Server database. For 

various reasons, for instance network infrastructure and network traffic, you might want to use 

multiple SQL Server databases as well. 

See also: 



To view the status of the database used by a specific MonitorMagic service, open the Network 

view window and browse to find the computer running the MonitorMagic service. Right click the 

computer name and select the menu option Configure service. In the configuration window, 

select the advanced tab, and click the button Configure database. You will be presented the 

following window: 

The Database status tab shows the current settings of the database used by the MonitorMagic 

service. The window contains the following fields: 

MonitorMagic service computer 

The name of the computer running the MonitorMagic service using the database. 

Database status 

The status of the database. The status is one of the following: 

No database used 

Error 

304


 

OK 

Database type 

The type of the database used. If no database is used, this field is empty. Otherwise it contains 

one of the following descriptions: 

MS Access database 

SQL Server 

ODBC database 

Note: the description MS Access database is used for both the MS Access database and the 

(underlying) Microsoft Jet Engine database. 

Datasource 

The name of the system data source. The system data source is the mechanism used by the 

MonitorMagic service to access the database. 

Database 

The name of the database. For different database types, the name has a different meaning. For 

MS Access databases, the name is the name of the database file without the .mdb extension. For 

SQL Server, it is the name of the database. 

See also: 


Create a new database 


Before you can create the MonitorMagic database, you need to have the database software 

installed. See Database - Supported databases for more information. To create the database, 

open the Network view window and browse to find the computer running the MonitorMagic 

service. Right click the computer name and select the menu option Configure service. In the 

configuration window, select the advanced tab, and click the button Configure database. Select 

tab Manage database. You will be presented the following window: 

305


From this window you can execute the following functions: 

Create 

Create a new database, to be used by one or more of the MonitorMagic services. To start 

creating a database press the Create button. 

Configure 

Configure the MonitorMagic service to use an existing database. 

Stop 

Instruct the MonitorMagic service to stop using the database. Note that when the MonitorMagic 

service is not using a database, it will not store the monitor data. 

See also: 



Database - Check database types 

To use a particular type of database, the database software must be installed. On the computer 

running the MonitorMagic service, the ODBC database drivers must be installed in order for the 

MonitorMagic service to use the database. Before you can select the type of database, 

MonitorMagic will check the availability of the ODBC driver software installed on the computer. 

Press Next to find the types of supported ODBC database drivers. 

When the the computer running the MonitorMagic service does not support any ODBC driver, an 

error message is shown. In this case, you must install the ODBC driver software for the database 

of your choice. See Database - Supported databases for more information. 

See also: 



306


Database - Select the database type 

When creating the database, MonitorMagic automatically shows the types of database supported 

by the computer running the MonitorMagic service. 


MS Access database 

Select this option if you want to create an MS Access database, to be used by the MonitorMagic 

service. 

SQL Server 

Select this option if you want to create an SQL Server database, to be used by the MonitorMagic 

service. 

ODBC database 

Select this option if you want to create an ODBC compliant database, to be used by the 

MonitorMagic service. 

If an option is grayed out, the MonitorMagic service did not find the ODBC drivers for the specific 

database. To continue creating the database, select the database type and press Next. 

See also: 



Database - MS Access: Specify the database file 

When you select to create an MS Access database, MonitorMagic will use a single database file 

as the database. You can select the location of the database file. If you want multiple 

MonitorMagic services to share the database, you should place the database file on a shared 

location (\\COMPUTER\Share\MonitorMagic.mdb). By default, MonitorMagic suggests to store 

the database file in the MonitorMagic service data directory. 

307


Select the option of your choice and press Finish to create the database at the specified location. 

When ready, a window will be shown describing the result of the operation: 

See also: 



Database - SQL Server: Specify server and database 

If you are using SQL Server for the MonitorMagic database, you can have the MonitorMagic 

service and the SQL Server database run on the same or different computers. The computer that 

runs the SQL Server database must have the SQL Server software installed. See Database - 

SQL Server for more information. If you are running the MonitorMagic service and the SQL 

Server database on different computers, the computer running the MonitorMagic service must 

have the SQL Server ODBC drivers installed. On Windows 2000 and Windows XP these ODBC 

drivers are automatically installed. On Windows NT 4.0, the ODBC drivers are installed when you 

install the MDAC software, Microsoft Office software or the SQL Server client software. 

When you create the SQL Server database, you need to specify the name of the computer 

running SQL Server and the preferred name of the database. 

308



Server 

The name of the computer (server or workstation) that runs SQL Server. 

Database name 

The preferred name of the SQL Server database used by the MonitorMagic service. 

MonitorMagic will make the database name unique by adding a number to the specified name 

when a database with the same name already exists. 

Specify the values for Server and Database name and press Next to continue. 

See also: 



Database - SQL Server: Specify logon 

When using a SQL Server database, you need to specify how the MonitorMagic service must log 

on to the database. 

309



Use Windows 2000/NT authentication and logon with the MonitorMagic service account 

This is the recommended method to access the database. In this case, the MonitorMagic service 

account needs to have sufficient rights to access the SQL Server database. 

Use SQL Server authentication with the following logon ID and password: 

As an alternative, you can specify the Logon ID and Password to logon to the SQL Server 

database. 

Select the appropriate option and press Next to continue. 

See also: 



Database - SQL Server: Data source setup 

When using SQL Server, you can specify a number of attributes to access the database. 

Depending on your SQL Server installation you might want to change the default attributes used 

by the MonitorMagic service when connecting to the database. 

Each attribute has the form keyword=value. Different versions of SQL Server support different 

attributes. The following picture shows the default attributes, used by MonitorMagic to configure 

the system data source that connects to SQL Server. 

310


The attribute values can contain variables that are calculated and filled in at run time. Variables 

are always enclosed in brackets []. The following variables are supported: 

Variable Example Description 

[DSN] MonitorMagicDataSource The name of the data source, 

created or used by the 


[LOGON_ID] sa The logon ID used to access 

the SQL Server database 

[PASSWORD] password The password used to logon to 

the SQL Server database 

By default, you do not need to change the attribute settings shown. Press Finish to create the 

system data source and the SQL Server database. 

See also: 



Use an existing database 


When the MonitorMagic database already exists you can instruct the MonitorMagic service to use 

the existing database. This can be a database of any of the supported types, running on the 

same or a different computer as the MonitorMagic service. To use an existing database, the 

MonitorMagic service needs a system data source that connects to the database. MonitorMagic 

can create the system data source or you can choose a system data source that as already 

been configured. In both cases, MonitorMagic will not create the database, but assume that the 

database exists. 

311


To start using an existing database, open the Network view window and browse to find the 

computer running the MonitorMagic service. Right click the computer name and select the menu 

option Configure service. In the configuration window, select the advanced tab, and click the 

button Configure database. Select tab Manage database and press the Configure button. You 

will be presented the following window: 

Important: You must know the type of the existing database you want to use. In case you 

are using the Microsoft Jet Engine (MDAC) select MS Access database. (Different database 

engines, like SQL Server, Microsoft Jet Engine, MS Access, use different SQL dialects. 

MonitorMagic supports multiple SQL dialects but needs to know what type of SQL dialect to use.) 

To continue, select the database type and press Next. 

See also: 



Database - Specify the data source 

To access an existing database, MonitorMagic uses a system data source to access the 

database. MonitorMagic can create the system data source or use an existing system data 

source. 

312


If you select an exisitng data source, the type of the database as specified in the system data 

source must correspond with the type of the database you have selected in the previous step. 

Select the system data source and press Finish to configure the MonitorMagic service to use the 

existing database. 

Important: If you select the option Use system data source, the data source must contain 

the specification of a valid MonitorMagic database. The database specified in the data 

source must be created with MonitorMagic and the data source must connect to the 

database. 

See also: 


Database - Delete old data 

To limit the size of the databae, you can delete old data. The deletion of the data can be 

configured as an automatic process and is executed by the MonitorMagic service. You can define 

of the age of the data that must be deleted and when the deletion must take place. To configure 

the data deletion procedure, select the Network view window and browse to find the computer 



Configure database. Select tab Delete old data. You will be presented the following window: 

313


Save all data, never delete any data 

Select this option if data should not be deleted from the MonitorMagic database. 

Delete data older than ... days 

Select this option if data must be deleted. You also need to specify the age of the data that must 

be deleted by specifying the number of days. Press the Edit button to specify when the 

MonitorMagic service must start the process to delete the data. 

Status 

The field shows the time and data of the currently scheduled action to delete the data. Note that 

the information shown in this field shows the time and date currently configued by the 

MonitorMagic service dis not updated if you change the deletion settings in the window. Instead, 

the time and data is obtained from the MonitorMagic service when the window is opened. To 

check the new specification settings, you need to change the settings, press the OK button and 

re-open the window. 

Note that the deletion of old data can take considerable time, depending on the amount of data 

that must be deleted. Normally, this times varies between 1 second and 1 hour, and typically 

equals a few seconds. 

See also: 











314



When you do not want to store data in the database you can instruct the MonitorMagic service to 

stop using the database. Open the Network view window and browse to find the computer 



Configure database. Select tab Manage database. Press the Stop button and follow the 

instructions. Note that MonitorMagic will not delete any system data source created to access the 

database. 

See also: 


Database - System Data Sources 

MonitorMagic uses a system data source to access the MonitorMagic database. The system 

data source is a set of instructions specifying how to access and connect to a specific database 

(data source). The system data source contains information like the type of database, the 

ODBC driver that must be used to access the data source, information how to log on to the 

database and so on. 

The MonitorMagic service uses the system data source to access the database. Therefore, the 

system data source must be configured on the computer running the MonitorMagic service. The 

MonitorMagic client application does not use the system data source. Instead, the MonitorMagic 

clients always accesses the MonitorMagic service to obtain database information. So you do not 

need a system data source for the MonitorMagic client application. 

MonitorMagic is able to manage the system data source used by the MonitorMagic service. You 

can also manage the system data source by using the operating system software. You can do 

this to see the configuration and test the system data source. 

The software to access the system data source is similar on the operating systems Windows NT 

4.0, Windows 2000, Windows XP. On Windows 2000, you select Start, Programs, 

Administrative Tools, Data source (ODBC). On Windows NT 4.0 you use the Control Panel to 

access the application to manage data sources. 

See also: 



When you experience any problems using a database with MonitorMagic, you can use the 

following checklist to locate the problem an try to solve it. 

Check if MonitorMagic is configured to use the database. See Database - Viewing the 

database status for more information. 

Check the ODBC data source. Confirm that the database type is correct and that the 

database exists. See Database - system data sources for more information. 

Check the MonitorMagic service application log for problem related to database usage. 

See also: 



315



The MonitorMagic Plugins are a set of command line utilities that can be used for monitoring 

purposes. Each plugin is a separate command line based application. A MonitorMagic plugin can 

be started from a command line but MonitorMagic plugins can also be started by the 

MonitorMagic service. In this case a command monitor is used to specify the settings and 

arguments used to process the plugin. The MonitorMagic service will capture the output of the 

plugin and rules and alarm actions can be executed according the output of the plugin. 

All MonitorMagic plugins are automatically installed on both the MonitorMagic service and client 

directory locations. 




Plugin - T4eWebPing 

Plugin - T4ePortPing 

Plugin - T4eDirSize 

Plugin - T4eSql 

v Plugin - T4eRexec 

Plugin - T4eSsh 

Plugin - T4eUnixInfo 

Plugin - T4eSSHUnixInfo 


The T4eWebPing command line application is a MonitorMagic plugin. It can be used to 'ping' a 

web-page, e.g. check availability and response time of any web page. 

Usage 

Tools4ever Web Ping Utility. Version 2.43 

Copyright (c) 2002 Tools4ever bv. All rights reserved. 


Usage: 

T4eWebPing url [-f:filename]Options: 

-f:filename Write response to filename. 

Examples:T4eWebPing http://www.tools4ever.com 

T4eWebPing http://www.tools4ever.com -f:C:\TempData\Tools4ever.txt 

Example 

Tools4ever Web Ping Utility. Version 2.43 



Page: http://www.tools4ever.com 

Status code: 200 

Page byte count: 27176 bytes 

Response time: 2134 ms 







316



Plugin - T4eRexec 





The T4ePortPing command line application is a MonitorMagic plugin. It can be used to 'ping' a 

specific port on any TCP/IP host. 

Usage 

Tools4ever Port Ping Utility. Version 2.05 



Usage 

T4ePortPing host portnumber [TCP|UDP] 

Examples: 

T4ePortPing www.tools4ever.com 80 

T4ePortPing www.tools4ever.com 5398 TCP 

T4ePortPing www.tools4ever.com 5398 UDP 

T4ePortPing 192.168.195.201 81 

Example 

T4ePortPing www.tools4ever.com 60339 TCP 

Tools4ever Port Ping Utility. Version 2.05 



Host: www.tools4ever.com 

Connection time: 110 ms 

Connected host: 206.204.218.25 

Connected port: 80 

Error code: 0 

Error text: - 













317


The T4eDirSize plugin is a MonitorMagic plugin. It is used to determine the size of directories, 

shares and all subdirectories and files. You can trigger rules when the size exceeds certain limits 

etc. The ouput of the plugin contains detailed information on the contents of the directory or share. 

Syntax 

Usage: 

T4eDirSize directory 

Examples: 

T4eDirSize D:\Users 

T4eDirSize \\COMPUTER\SHARE\DIR 

Output: 

Tools4ever Directory Size Utility. Version 2.45 



Total file size (bytes): 31017622 bytes 

Total file size (KB): 30290 KB 

Total file size (MB): 29 MB 

Total number of files: 41 

Total number of directories: 2 

Total disk size (bytes): 31453437952 bytes 

Total disk size (MB): 29996 MB 

Total disk free size (bytes): 29620826112 bytes 

Total disk free size (MB): 28248 MB 

Archive file/directory count: 41 

Compressed file/directory count: 0 

Encrypted file/directory count: 0 

Hidden file/directory count: 0 

Offline file/directory count: 0 

Read-only file/directory count: 0 

System file/directory count: 0 

Temporary file/directory count: 0 

Search time: 0 ms 

Error count: 0 













318


The T4eSql plugin is a MonitorMagic plugin. It is used to execute an SQL query. The results of 

the SQL query can be used as an criteria to trigger rules of the MonitorMagic command monitor. 

The T4eSql plugin uses an ODBC connection to execute the query. The ODBC datasource must 

exist in order for the query to succeed. 

Syntax: 

Tools4ever Sql Utility Version 3.48 



Usage: 

T4eSql 

options: 

-c:command file 

-d:odbc-string 

Read specification from command file. (Ignores all other command line 

options). 

Database ODBC connection string. 

-q:sql-query SQL Query to execute. 

-f:sql query file 

-o:output file 

-s:separator 

Read SQL query from specified file. 

Write output to specified file. 

Use separator, specify one of SPACE, COMMA, COLON,SEMICOLON,TAB 

noheaders 

nostats 

quotes 

singlequotes 

rownumbers 

nolog 

helpodbc 

Do not show header information. 

Do not show search result statistics. 

Use double quotes. 

Use single quotes. 

Preceed results with rownumbers. 

Supress log output on errors. 

Show help on ODBC connection string. 

Additional information: 

When the -c option is used, not other options should be specified on the command line. Instead, 

all option should be specified in the command file. In the command file, each option should be 

specified on a separate line. When specifying file names, use the .\filename notation to specify 

the current directory. You can also use full path file name specification. For any question or 

additional information contact www.tools4ever.com. 













319


The T4eRexec plugin 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. 

Tools4ever Rexec Utility. 2.3.1 US/UK 



Syntax 

T4erexec [options] hostname command 

Hostname: dns name of target computer, or alternatively the IP address of the target computer. 

command: The UNIX command that is to be executed on the remote computer. 

Options: 

-c: Combine stdout and stderr together 

-l user: Run command as 'user' on remote host 

-p password: Use 'password' at remote host 

-P remoteport: The port the server is running at. 

-L localport: The port at wich the client listens to the response from the server. 

-a timeout: The time to wait for a connection from the server in seconds (default 30secs) 

-r file: Send standard output to 'file' instead of stdout (same as >) 

-s file: Send standard error to 'file' instead of stderr (same as 2>) 

-t file: Send standard output to 'file' in addition to stdout 

-u file: Send standard error to 'file' in addition to stderr 

-v: Display version number 

-w: Prompt and wait for Enter key after commanderr 

Example 

t4erexec -c -a 60 -l rexectest -p rexectest -t d:\test\testrexecoutput.txt 80.127.205.180 "echo 

ls ../.. ;ls ../.. " 

Special Requirements 

The Rexec protocol must be enabled on the target machine, on Unix systems this means that the 

Rexec deamon must be running. 

Remarks 

If the remote host is on the other side of a firewall, it may be required to specify the -c option, 

depending on the configuration of the firewall. 

The plugin uses the standard rexec protocol to communicate with the target computer. 

Authentication is based on the existence of a valid client host and username combination as 

command parameters. Because this information is revealed, these commands can present a 

security risk. 

For a secure alternative, please see Plugin - T4eSsh 











320




The T4eUnixInfo plugin 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 

Tools4ever Rexec Utility. 2.3.2 US/UK 



Syntax 

t4eunixinfo [options] hostname scriptname 

options: 

Please note, that all specifications are potentially case sensitive. 

-c: Combine stdout and stderr together 

-l user: Run command as 'user' on remote host 

-p password: Use 'password' at remote host 

-P remoteport: The port the server is running at. 

-L localport: The port the server can connect to. 

-a timeout: The time to wait for a connection from the server. Default 30secs 

-r file: Send standard output to 'file' instead of stdout (same as >) 

-s file: Send standard error to 'file' instead of stderr (same as 2>) 

-t file: Send standard output to 'file' in addition to stdout 

-u file: Send standard error to 'file' in addition to stderr 

-v: Display version number 

-w: Prompt and wait for Enter key after command 

Note, user and password options are required. 

hostname : 

The dns name of the remote host, or the IP address of the remote host 

scriptname: 

can be of the following values: 

DISK [disk device] - gets disk information. 

disk device - The device to get the information from. mostly someting like /dev/hda1 

Use DISK without paremeters to get info for all disks, including there names. Which can be used 

as parameter. also the unique part of the name can be used as parameter. for example 

only: hda1 or hda2 

MEM - gets memory information. 

CPU - gets cpu information. 

SWAP [disk device] - gets swap information. 

disk device - The device to get the information from. 

321


Example 

t4eunixinfo -c -a 60 -l rexectest -p rexectest -t D:\test\unixinfooutput.txt 80.127.205.180 DISK 

Special Requirements 

The Rexec protocol must be enabled on the target machine, on Unix systems this means that the 

Rexec deamon must be running. 

Remarks 

If the remote host is on the other side of a firewall, it may be required to specify the -c option, 

depending on the configuration of the firewall. 

The plugin uses the standard rexec protocol to communicate with the target computer. 

Authentication is based on the existence of a valid client host and username combination as 

command parameters. Because this information is revealed, these commands can present a 

security risk. 

For a secure version of T4eUnixInfo, see Plugin - T4eSSHUnixInfo 












322

MonitorMagic Web Interface 

Introduction to the MonitorMagic Web Interface 

Welcome to MonitorMagic's web interface! This addition to MonitorMagic makes it a complete 

solution for local and remote enterprise network management. MonitorMagic's web interface can 

be seen below: 

Harness the power of MonitorMagic by using its' web interface. MonitorMagic's web interface 

gives you a complete view of your network and the ability to manage it from anywhere in the 

world. Most products that offer this functionality make network management via a web interface 

very complex to implement, and they often rely on a web server that isn't included with the 

product. This is not the case with MonitorMagic. Configuration is easy, a few clicks will have you 

up and running. The web server that the interface relies on is built into MonitorMagic. What's 

more is that MonitorMagic's web interface is completely secure. It implements secure socket layer 

(SSL) to ensure that your production network is not compromised. 

Start use the MonitorMagic's web interface now. 

See also: 

MonitorMagic Web Interface scenarios 

Configure MonitorMagic WebService: General 

Configure MonitorMagic WebService: HTTP 

Configure MonitorMagic WebService: HTTPS 

Configure MonitorMagic WebService: Configure Certificate 

Configure MonitorMagic WebService: Save Certificate 

323


Configure MonitorMagic WebService: Access Rights 

WebService Access Rights (per computer) 

Specify computer web access 

WebService Access Rights (per account) 


Installing and configuring the MonitorMagic Web Interface 


Your use of MonitorMagic's web interface will fall into one, or more, of three scenarios. For each 

of these scenarios the recommended setup differs in varying degrees. The scenarios and their 

corresponding recommended setup is as follows: 

Test only: 

The test only scenario is almost always the first phase of implementing MonitorMagic, or any 

software for that matter. Before most software is introduced onto a production network, it is first 

implemented in a lab environment. The lab is usually a network of its' own, but is not connected 

to the production network, or is segmented by some hardware or software device. MonitorMagic 

is easiest to implement in this scenario because there are no special requirements. At this stage 

most users only want to get a basic understanding of the web interface, so access rights and 

secure socket layer (SSL) are not concerns. Utilizing only HTTP is fine in this environment. 

Implementing MonitorMagic in a test environment using only HTTP should take about only 1 

minute. 

Intranet usage: 

After the testing phase has been completed users of MonitorMagic are ready to implement the 

product on their intranet (production network). Security now becomes a concern. At this stage a 

few decisions need to be made. Who should be allowed to use the MonitorMagic web interface? 

Should the users of the web interface be allowed to manage any machine? Is the potential threat 

of a hacker compromising security and entering the production environment a big concern? 

MonitorMagic has varying levels of security that address all of these issues. Users can have no 

access, read only access, or manage access through the web interface to computers on the 

network. It is recommended that typical users should not be given manage access since this will 

allow them to perform some administrative functions. If you want typical users to have access to 

the network through the web interface it should be read only. When company security is tight 

between the intranet and the Internet, it is OK to use MonitorMagic's web interface over HTTP, 

but we recommend using HTTPS. Implementing MonitorMagic's web interface in this scenario 

should take about 15 minutes. 

Internet usage: 

Once MonitorMagic has been readied for use on your intranet the product can be implemented 

for use over the Internet. Security is now major concern because you are communicating with 

your network through the public Internet domain. Using MonitorMagic's web interface over HTTP 

in this scenario is VERY UNWISE. It is HIGHLY recommended that MonitorMagic's web interface 

is only used over HTTPS. The secure socket layer (SSL) method of encryption has been tried an 

true, it is used to transmit credit card information over the web by every major on-line vendor. 

Banks that offer account management via the web use secure socket layer as well. Before you 

begin to use MonitorMagic's web interface over the web you should apply account restrictions 

similar to the ones mentioned in the Intranet usage section. Once account restrictions are in place 

you will most likely have to open a port on your firewall and route the port to the machine that 

runs the MonitorMagic WebService. By default secure socket layer uses port 443, but you can 

change what port MonitorMagic's web interface should use for secure socket layer. Implementing 

MonitorMagic's web interface in the scenario should take about 15 minutes. 

324


See also: 













MonitorMagic client: 

Before MonitorMagic's web interface can be used the MonitorMagic client must be installed. The 

web interface's Installation, configuration, and the specification of access rights are all done 

through the MonitorMagic client. Installing the MonitorMagic client is simple and straightforward, 

you can find out more about this procedure here: Setup MonitorMagic. 

MonitorMagic service: 

Once the MonitorMagic client has been installed you must install the MonitorMagic service on the 

machine that will be the MonitorMagic web server. The MonitorMagic service and the 

MonitorMagic WebService are different. When you install the MonitorMagic service you are not 

activating the WebService, activating the WebService is done using a different procedure. 

Installing the MonitorMagic service is not difficult and you can find out more about the procedure 

here: Installing and upgrading the MonitorMagic service. 

Activate the MonitorMagic WebService: 

Now that the MonitorMagic service has been installed the WebService can be activated. The 

machine that the WebService is activated on will act as the web server. Usually one web server is 

sufficient for an organization, but you can have more than one if you desire. Activating the 

WebService is easy and you can find out how to do it here: Configure MonitorMagic WebService: 

General. 

See also: 












325


To begin the activation of the MonitorMagic web service you must select a machine in 

MonitorMagic's network browse window. The machine you select must have the MonitorMagic 

service installed. Once the machine is selected right click it and select the option "Configure 

WebService." You will presented with the following dialog box: 

The general tab of the "Configure MonitorMagic WebService" dialog box gives some information 

on the status of the MonitorMagic web service. The figure above shows that the MonitorMagic 

web service is running on computer Kraken with the HTTP service running on port 81 and the 

HTTPS service running on port 443, these are the defaults. When you first see this dialog box the 

HTTP and HTTPS service status will be "not running," and the MonitorMagic computer field will 

show the name of the machine that you are configuring the web service for. 

Port numbers: 

Every piece of software or hardware that uses TCP/IP (transfer control protocol/Internet protocol) 

connects to its' destination target via a port number. There are 65,535 TCP/IP ports and you can 

use a web browser to connect to the MonitorMagic web service on almost any one you desire. 

The two stipulations are that the MonitorMagic web service must be listening on the same port 

number that you're connecting to and you can't use a port number that is in use by something 

else. For example SMTP email is sent over port 25 and pop3 email is received over port 110. 

Check the Internet for a listing of commonly used ports. 

How to connect to the MonitorMagic web service: 

Connecting to the MonitorMagic web service is easy. This is done by entering a URL into the 

address bar of a web browser. The figure above will serve as an example. The name of the 

machine that runs the web service is Kraken and it is listening for HTTP on port 81 and for 

HTTPS on port 443. The machine Kraken has an IP address of 192.168.1.53. If you do not know 

the IP address of a machine you can find it out by executing the following command from a 

command prompt: "ping machine name". By pinging the name of the machine you will see the 

machine name resolve to an IP address. Knowing the name of the machine that runs the 

326


MonitorMagic WebService is necessary in order to connect to it, but you can also connect to the 

MonitorMagic WebService using the IP address. The syntax used to connect to the WebService 

is protocol://machine name or IP address:port number. The following examples are all valid ways 

to connect to the MonitorMagic WebService: 

HTTP: 

http://KRAKEN:81 

http://192.168.1.53:81 

HTTPS: 

https://KRAKEN:443 

https://192.168.1.53:443 

Choose a WebService to enable: 

At this point in time the MonitorMagic WebService is not activated. You must choose which 

service you want to activate, as seen in the example above you can choose to activate both. 

To activate the HTTP service see the following: Configure MonitorMagic WebService: HTTP. 

To activate the HTTPS service see the following: Configure MonitorMagic WebService: HTTPS. 

See also: 










Configure MonitorMagic WebService: Proxy MonitorMagic service 


It is not difficult to configure the MonitorMagic web service to run HTTP. Although, for security 

reasons, it is strongly recommended that you use HTTPS. Implementing HTTPS is not 

complicated so there is no reason not to use it. It is best to run HTTP in test environments only. 

To begin the activation of the MonitorMagic web service, over HTTP, you must select a machine 

in MonitorMagics' network browse window. The machine you select must have the MonitorMagic 


WebService," then click the tab titled HTTP. You will be presented with the following dialog box: 

327


MonitorMagic WebService HTTP configuration: 

To enable the MonitorMagic service over HTTP check the bo,x in the figure above, next to 

"Enabled." Now decide what port number you want the MonitorMagic web service to listen for 

connections on. The default is 81. Before you choose a port number different from 81 check the 

Internet for commonly used port numbers. 

The option "Ask for Windows 2000/NT username and password" is not mandatory but it is 

recommended that you use it. It gives you an extra layer of security. By choosing the "Ask for 

Windows 2000/NT username and password" option you are forcing users of the MonitorMagic 

web interface to enter the username and password they use to logon to Windows NT. Just 

because a user correctly enters his/her username and password doesn't mean that they will be 

able to use the MonitorMagic web interface. The user must have read-only or manage rights 

which are specified in the Access rights tab, seen on the figure above. If a user logs into the 

MonitorMagic WebService and has no access rights, or their access rights are unspecified, they 

will not see any domains listed on the left hand side of the interface. If you do not specify this 

option,any user connecting will have read-only access. 

Port numbers: 



use a web browser to connect to the MonitorMagic WebService on almost any one you desire. 

The two stipulations are that the MonitorMagic WebService must be listening on the same port 

number that you're connecting to, and you can't use a port number that is in use by something 



See also: 



328



Configure MonitorMagic WebService: HTTPS. 









It is not difficult to configure the MonitorMagic web service to run HTTPS. For security reasons it 

is strongly recommended that you do not use HTTP. Implementing HTTPS is not complicated so 

there is no reason not to use it. It is best to run HTTP in test environments only. 

To begin the activation of the MonitorMagic web service over HTTPS you must select a machine 

in MonitorMagic's network browse window. The machine you select must have the MonitorMagic 


WebService," then click the tab titled HTTPS. You will presented with the following dialog box: 

MonitorMagic WebService HTTPS configuration: 

To enable the MonitorMagic service over HTTPS check the box in the figure above next to 

"Enabled." Now decide what port number you want the MonitorMagic web service to listen for 

connections on. The default is 443. Before you choose a port number different from 443 check 

the Internet for commonly used port numbers. 

329


The option "Ask for Windows 2000/NT username and password" is not mandatory but it is 

recommended that you use it. It gives you an extra layer of security. By choosing the "Ask for 

Windows 2000/NT username and password" option you are forcing users of the MonitorMagic 

web interface to enter the username and password they use to logon to windows NT. Just 

because a user correctly enters his/her username and password doesn't mean that they will be 

able to use the MonitorMagic web interface. The must have read-only or manage rights which are 

specified in the Access rights tab, seen on the figure above. If a user logs into the MonitorMagic 

web service and has no access rights, or their access rights are unspecified, they will not see any 

domains listed on the left hand side of the interface. If you do not specify this option, any user 

connecting will have read-only access. 

MonitorMagic WebService certificate configuration: 

Before you can use MonitorMagic over HTTPS you must configure a certificate, save it to disk, 

and install it on the web browser you will be accessing the web service with. Configuring and 

installing a certificate is not difficult. Please see the following for more information: 



Port numbers: 



use a web browser to connect to the MonitorMagic web service on almost any one you desire. 

The two stipulations are that the MonitorMagic web service must be listening on the same port 

number that you're connecting to, and you can't use a port number that is in use by something 



See also: 











In order to enable access to the MonitorMagic web service over HTTPS a digital certificate must 

be used. The purpose of a digital certificate is to verify that a user sending a message is who he 

or she claims to be. Digital certificates are most often issued by a certificate authority such as 

VeriSign. MonitorMagic is capable of generating its' own digital certificates. You do not have to 

use the digital certificate that MonitorMagic generates, if you have one from a certificate authority 

you can use that. To tell the MonitorMagic web service what certificate it should use you must 

click the "configure" button under the "MonitorMagic WebService certificate configuration" section 

of the figure seen below: 

330


Once you click the "configure" button you will be presented with the following dialog box: 

Create new certificate: 

If you want to use a certificate that the MonitorMagic web service generates select the "Create 

new certificate" radio button. Once selected fill out the information in every field and click the "OK" 

331


button. The information you entered will be used to generate the certificate and the certificate 

information will be saved to the MonitorMagic web service. 

Import existing certificate: 

If you want to use a certificate that was generated by a certificate authority, such as VeriSign, 

select the "Import existing certificate" radio button. Once selected click the button. A dialog 

box will appear that allows you to navigate to the location of your certificate. When you have 

found the location of your certificate, select it and click "OK." You will be brought back to the 

"MonitorMagic Web service certificate configuration" dialog box. Click "OK" again, the certificate 

information will be saved to the MonitorMagic service. 

Now that you have generated, or specified, a digital certificate for use with MonitorMagic's 

HTTPS web service, you are almost ready to connect to the WebService over an encrypted 

connection. All you have to do is install the certificate on the web browser you're going to use to 

access the MonitorMagic WebService over HTTPS. The certificate must be saved to a location 

before it can be installed. Please see the following for details on this procedure: Configure 

MonitorMagic WebService: Save Certificate. 

See also: 












Digital certificates are what allow you to use secure socket layer (SSL). Once you have created a 

digital certificate for use with the MonitorMagic WebService, or imported one, you must install the 

certificate on the web browser you're going to use with the MonitorMagic WebService. To save 

the certificate to a location you must use the "Save" button located on the HTTPS tab of the 

"Configure MonitorMagic WebService" dialog box seen below: 

332


By clicking the save button, as seen above, you will open a "Save as" dialog box. Navigate to the 

location where you would like the certificate saved and click save. 

Saving the certificate for use on an Intranet: 

If you are going to use MonitorMagic's web interface on an Intranet you can save the certificate in 

a secured folder. Once the certificate has been saved you can install it on a web browser by 

double clicking it, then answer the series of dialog boxes that follow. Once the digital certificate 

has been installed you can delete it from the location you saved it to. If someone else makes a 

copy of your digital certificate they will be able to use the MonitorMagic WebService, if you did not 

enable access rights, and security can be compromised. 

Saving the certificate for use over the Internet: 

If you are going to use MonitorMagic's web interface over the Internet it is highly recommended 

that you save the certificate to a floppy disk. Do not email the certificate to yourself. Email 

attachments can be intercepted easily. Once the certificate has been saved to floppy you can 

install it on any web browser by double clicking it, then answer the series of dialog boxes that 

follow. After the certificate has been installed store the floppy disk in a safe location or format it, 

you can always use MonitorMagic to generate, or save, another certificate. 

See also: 










333





Access rights are a very important part of the MonitorMagic WebService. You will probably want 

to limit what machines a user of the web interface has access to, and what they can do on each 

machine. MonitorMagic provides you with a versatile method for making these specifications. 

Access rights are specified using the "Access rights" tab of the "Configure MonitorMagic 

WebService" dialog box, as seen below: 

MonitorMagic WebService access rights: 

Specify here the access rights that users of the web interface have to specific machines. This is 

done by using the configure button. Clicking the configure button will open up a new dialog box 

titled "WebService access rights per computer." To find out how to use this dialog box see the 

following: WebService Access Rights (per computer). 

See also: 











334


Configure MonitorMagic WebService: Proxy MonitorMagic service 

If you are running multiple MonitorMagic services, you can use a single MonitorMagic service to 

provide WebService capabilities for all MonitorMagic services. In this case the MonitorMagic 

WebService is a proxy service for the other MonitorMagic services not running the MonitorMagic 

WebService. 

Example: You have installed and configured the MonitorMagic service and WebService on 

computer SUMMER. The firewall is configured to allow HTTPS communications on port 449 with 

the static IP address of the SUMMER server. So from the outside world, SUMMER is accessible 

and able to communicate over port 449 using HTTPS. Next, you have another server, AUTUMN. 

This computer is running the MonitorMagic service, but you do not want to enable MonitorMagic 

WebService on this machine. In order now to use the MonitorMagic WebInterface to access the 

monitors of the MonitorMagic service on AUTUMN you configure SUMMER to be a MonitorMagic 

proxy server for computer AUTUMN. 

To configure the proxy settings, right click the computer that runs the MonitorMagic service and 

WebService. Select menu option Configure WebService and select tab Proxy. You will be 


Use the Add and Delete buttons to add and remove computers. These computer must run the 

MonitorMagic service but do not need to have the WebService enabled. Instead, this 

MonitorMagic WebService will serve requests from browsers for the listed computer. 

In the example shown below, two computers are running the MonitorMagic service: SUMMER 

and AUTUMN. For computer SUMMER, the MonitorMagic WebService is enabled. SUMMER is 

the proxy server for server AUTUMN. In a browser, connecting to SUMMER, you can see and 

manage the monitors of server AUTUMN. 

335


See also: 












Specifying the access rights a user has to machines through the MonitorMagic web interface 

follows an order of operations. First the name of a machine is added to the "Access rights per 

computer" list. Once a machine is in the the list it is selected, a user is added to that machine and 

his/her access rights are specified. This is all done through the "Web service access right per 

computer" dialog box, seen below, which can be opened by clicking "Configure" under the 

Access rights tab of the "Configure MonitorMagic web service" dialog box. 

336


The figure above shows that the group BUILTIN\Administrators have manage access to other 

computers. Other computers means any computer that is not in the "Access rights per computer 

list." You can also see that the user Elmo in the TOOLS4EVER domain has no access to to the 

machine Kraken and that the user Mike in the TOOLS4EVER domain has manage access. 

This button is used to Add a computer to the "Access rights per computer" list. Once a machine 

has been added to the list a user can be assigned rights to it. To find out more about adding 

machines to the "Access rights per computer list" see the following: Specify computer web access. 

This button is used to Add a user and specify his/her access rights to a machine that is already in 

the "Access rights per computer" list. You must add a machine to the list before you can assign a 

user's access rights to it. To find out more about adding users to the "Access rights per computer 

list" see the following: Specify computer web access. 

337


This button deletes a machine from the "Access rights per computer" list, if a machine has been 

deleted from the list the access rights a user has to it come from the [other computers] object. 

The button also deletes a specific user's access rights from the machine his/her account is listed 

under. 

This button will create, but not save, and open a text file that gives you a report of all machines 

specified in the "Access rights per computer" list. The report lists who has manage access, no 

access, and read access on each machine. 

This button invokes the help file. 

This button will bring up an interface where you can manage a user's rights only if he/she has 

already been added to the list above. Example, if I want to manage user Trent's rights who is in 

the TOOLS4EVER domain and he has not yet been added to the "Access rights per computer" 

list, you cannot use this interface to manage his rights. To find out more about managing user's 

access rights through this interface see the following: WebService Access Rights (per account). 

See also: 













Specifying what users have what type of access to a certain machine is not difficult. Although this 

procedure follows an order of operations. A machine that you want to give users of the web 

interface access to must be selected, then the access for the user is specified. This procedure 

starts and ends with the following dialog box: 

338


As stated previously a machine must be added to the list before a user can be given access to it. 

Of course if a machine is already in the list you do not have to add it again. Please note again 

that the object [other computers] specifies the access users have to any machine that is not in the 

list. 

To add a computer to the list use the 

button. Once you click this button you will 

presented with a "Browse network" dialog box where you can navigate to a domain then to the 

machine that you want to give users of the web interface access to. Once you have selected the 

machine click "OK." 

Now that you have added a machine to the list you can specify a web interface user's access to it. 

To do so select the machine, in the list, you want to add or change a user's access for. Now click 

the 

box: 

button. Once you have done that you will be presented with the following dialog 

339


Account name: 

In the "User/Group" field you can type in the name of the user or group you want to give access 

to. If you choose to type in the name of the user or group you must use the following syntax: 

DOMAIN NAME\USER OR GROUP. Alternatively, you can use the button to activate a 

dialog box where you can choose a user or group from a list. Once you are done making your 

selection click "OK." 

Type of web interface access: 

This is where you specify what access the user or group listed in the "Account name" section will 

have. No access means the user or group will be able to log into the MonitorMagic WebService, 

but when the web interface opens the user or group will not see any domain or machine entries in 

the network pane, which is on the left side of the MonitorMagic web interface. Read access 

means the user or group will be able to look at all aspects of the specified machine but, they will 

not be able to change anything. Manage access means that the specified user or group will be 

able to shutdown, reboot, start/stop services, and clear the event logs of the specified machine. 

Once you are done making your selection click "OK." 

See also: 













MonitorMagic provides you with an interface for managing the access rights of users or groups 

who have been given rights to a machine through the MonitorMagic web interface. This feature 

provides you with an easy way to quickly view and change the access rights a user or group has 

340


to machines. This interface must be invoked through the "Web service access rights per 

computer" dialog box, as seen below: 

Once you have opened the dialog box seen above you can invoke the "Web service access rights 

per user" dialog box by clicking the 

presented with the following dialog box: 

button. Once you click this button you will be 

341


Account (user or group): 

You can use the drop down box in this section of the dialog box to select the user or group you 

want to view the access rights for. The button can also be used to select a user or group 

you want to view or change access for, it will bring up a dialog box where you can select a user or 

group by navigating to a domain, then to the user or group. Once a user or group has been 

selected the No access, Read access, and Manage access columns will populate. The access 

rights a user or group has on a certain machine corresponds to what column the name of the 

machine appears in. 

Computer access overview: 

As stated before the No access, Read access, and Manage access columns will show what rights 

the selected user has to a machine, this corresponds with the column name the machine appears 

in. This part of the dialog box can be used to change a user's or group's access level to a 

particular machine; you can also give users rights to machines for which they currently have none 

and can take away their rights as well. To change the selected user's or group's access rights to 

a particular machine all you have to do is left click the machine you want to change the access 

rights for and drag it to a new column, then let go of the left mouse button. If you want to give, or 

deny, the selected user or group rights to a machine that is currently unspecified click the add 

button in the appropriate column. This will bring up a browse network window where you can 

select the domain and then the name of machine you want to specify. To delete the rights a user 

has to a machine, select the name of the machine and click the delete button in the appropriate 

column. 

See also: 







342








The MonitorMagic web interface if part and parcel of the MonitorMagic product. It is not a 

separate software package; hence, it is not licensed separately. If you purchase, or have 

purchased, MonitorMagic you get the web interface at no extra cost. However, the web interface 

does comply with the restrictions of your license code. Every server license for MonitorMagic 

comes with ten workstation licenses. If you purchased a five server license for MonitorMagic you 

are able to monitor five servers and fifty workstations. The same rules apply to the web interface, 

with a five server license you will be able to view/manage five servers and fifty workstations. If 

you have further questions regarding licensing please contact your Tools4ever reseller. If you do 

not know who your reseller is please see the following: Tools4ever partners. 

Security and the MonitorMagic Web Interface 

HTTP is not safe and secure 

MonitorMagic can use the HTTP or HTTPS protocol to give web interface users the ability to 

monitor and manage their network from a remote location. This means that a user of the web 

interface can monitor and manage his/her network over the corporate Intranet or over the Internet. 

Although it is recommended that users of the web interface use HTTPS over their corporate 

Intranet, HTTP can be used if security is not a concern. When a MonitorMagic web interface user 

accesses his/her network over the Internet it is highly recommended that nothing but HTTPS is 

used. Even better, using HTTPS over the Internet to access your network should be viewed as a 

requirement, not an option. 

If a MonitorMagic web interface user were to use HTTP over the Internet to access his/her 

network, all of the information that passes between the MonitorMagic web server and the users 

web browser can be easily intercepted. Before a user can gain access to the MonitorMagic 

WebService he/she will most likely have to enter his/her Windows NT username/password, this 

means that anyone with the know how can intercept the Windows NT username/password, and 

can then gain access to your corporate network. To repeat, using HTTPS to gain access to your 

network through the MonitorMagic web interface should be viewed as a requirement. 

See also: 



HTTPS is safe and secure 

Certificates 

Man in the middle attack 


343


MonitorMagic can use the HTTP or HTTPS protocol to give web interface users the ability to 

monitor and manage their network from a remote location. This means that a user of the web 

interface can monitor and manage his/her network over the corporate Intranet or over the Internet. 

Although it is recommended that users of the web interface use HTTPS over their corporate 

Intranet, HTTP can be used if security is not a concern. When a MonitorMagic web interface user 

accesses his/her network over the Internet it is highly recommended that nothing but HTTPS is 

used. Even better, using HTTPS over the Internet to access your network should be viewed as a 

requirement, not an option. 

When a MonitorMagic web interface user employs the use of HTTPS (secure socket layer) they 

are using 128 bit encryption, achieved through the use of digital certificates; this is the highest 

level of encryption available for HTTPS (secure socket layer). When a MonitorMagic web 

interface user logs into the MonitorMagic WebService with his/her Windows NT 

username/password the information is transmitted between the MonitorMagic web server and the 

clients web browser. When using HTTP the username/password transmission becomes a big 

security issue, this is not the case when using HTTPS (secure socket layer). When the Windows 

NT username/password is sent over the line using HTTPS it is encrypted, and not readable by 

others. Many on-line vendors and on-line banking programs employ the use of HTTPS (secure 

socket layer) to make transactions. The use of the MonitorMagic web interface with HTTPS 

(secure socket layer) is just as safe as making transactions with on-line vendors or on-line 

banking programs. 

It is possible that some system administrators may feel that using the MonitorMagic web interface 

over HTTPS (secure socket layer) is not a viable option. This is a matter of opinion and 

preference. If you feel apprehensive about transmitting administrative passwords over HTTPS 

(secure socket layer) preventive measures can be taken. Administrators can build a user account 

only for use with the MonitorMagic web interface. This web interface only account should have 

limited access rights everywhere on the network. MonitorMagic web interface access rights and 

Windows NT access rights are, when using the default settings, completely independent of each 

other. 

See also: 




Certificates 


Certificates 

What are Digital Certificates? 

Digital certificates serve a similar purpose as your drivers license or company ID. They provide 

you with a way to electronically identify yourself. A digital certificate is associated with a pair of 

keys, a public key and private key. Public and private keys are used to decrypt, encrypt, and 

digitally sign information. Your digital certificate is what makes it possible for you to gain the right 

to use someone elses public key, a public key will not be sent to you if you cannot identify 

344


yourself with a digital certificate. The use of someone elses public key is what allows you to 

decrypt data that has been encrypted with their private key. As seen partly in the Configure 

MonitorMagic WebService: Configure Certificate section, the following is the information that is 

included in a digital certificate: 

 

 

 

 

 

 

Owner's public key 

Owner's name 

Expiration date of the public key 

Name of the issuer 

Serial number of the digital certificate 

Digital signature of the issuer 

How does encrypted communication actually commence? 

Without getting too complicated, encrypted communication begins with the exchange of public 

keys. As stated before you need the senders public key to decrypt information sent with the 

senders private key. Once keys have been exchanged the sender creates a message and passes 

it through a special algorithm which creates a message, the message is then encrypted with the 

private key. The sender then transmits the message to the recipient. Once the recipient receives 

the message it passed through the same special algorithm to re-create the message. The 

message is then decrypted using the senders public key. If the re-created message is the same 

as the message originally created encrypted communication can truly commence. 

Digital certificates for use with MonitorMagic: 

As mentioned in the Configure MonitorMagic WebService: Configure Certificate section 

MonitorMagic can create its' own digital certificate for use with the MonitorMagic web service. 

Creating digital certificates for use with the MonitorMagic web service is simple and 

straightforward. All you need to do is fill out a few fields and click "OK." MonitorMagic can also 

import digital certificates, for use with the MonitorMagic web service, from certificate authorities 

such as VeriSign. 

See also: 






Although HTTPS (secure socket layer) is a very safe and secure form of encryption it is 

susceptible to one type of interception known as the man in the middle attack. If you want to use 

the MonitorMagic web interface over the Internet there is a way you can avoid being susceptible 

to this type of attack. After MonitorMagic generates a digital certificate for you, save it to floppy 

disk. If you want to use the MonitorMagic web interface from home bring the floppy disk 

containing your digital certificate home with you. Install the digital certificate on your web browser 

at home off the floppy disk. Your susceptibility to the man in the middle attack has now been 

circumvented, the attack can only take place during the initial exchange of digital certificates and 

keys. 

345


How the man in the middle attack works: 

There are always three parties involved in the man in the middle attack. The sender, the recipient, 

and the man in the middle. For the sake of this example we will say that Mike is the sender, John 

is the recipient, and Elmo is the man in the middle. Mike wants to communicate over HTTPS with 

John. Unknown to both Mike and John, Elmo is waiting for them to communicate so he can 

intercept. Mike attempts to initiate communication with John, but the communication is 

intercepted by Elmo who authenticates himself as John. Elmo, who now has everything he 

needs to impersonate Mike, initiates communication with John and authenticates as Mike. There 

are now actually two sessions in place. One between Mike and Elmo and another between Elmo 

and John. Mike and John do not know anything is wrong because the communication between 

them seems normal. In actuality all the information Mike and John are exchanging is passing 

through Elmo in clear text form. 

See also: 




Certificates 

Web site pages of the MonitorMagic Web Interface 

Web interface navigation 

This section details using the navigation tree of the MonitorMagic web interface. The web 

interface can be accessed by specifying a URL that contains the name or IP address, plus port 

number, of the computer running the MonitorMagic web service. Examples: http://kraken:81, 

https://kraken:443, http://192.168.1.53:81, or https://192.168.1.53:443. In the browser, on the left 

side, the MonitorMagic Web Interface shows a tree used to navigate though the various pages of 

the MonitorMagic web interface. 

The tree contains 3 main items at the root level: 

NetWork: The network tree section. This section contains all domains, and for each 

domain all computer running Windows 2000/NT/XP. If the information in this section is 

not up-to-date, see Commands for more information. 

346


 

 

MonitorMagic: The section showing the computers running the MonitorMagic service. 

From these comptuers, you can access and view the monitors, rules and alarm actions. 

Commands: A separate page used to issue commands to the MonitorMagic service. 

System Info 

This section details using the system info section of the MonitorMagic web interface. The web 



https://kraken:443, http://192.168.1.53:81, or https://192.168.1.53:443. To access the system 

information for a machine you must navigate to the name of the machine, on the left hand pane of 

the browser, and click the system info section which is seen in the following example: 

Once you click on the system info section you will see the following appear in the right hand pane 

of the browser window: 

As seen above the system info section gives you some basic information about your machine. 

The system info section includes the same type of information for every machine you access. If 

you have manage rights to a machine and you click the system info section you will also be 

presented with a manage button, as seen above. By clicking on the manage button you can 

perform shutdown and reboot operations on the machine as seen below: 

347


If you click on any of the reboot or shutdown buttons you will perform the associated function. To 

access another aspect of the machine choose another section in the left hand pane of the 

browser. 

See Also: 

Services 

Event logs 

Processes 

Monitors 





Services 

This section details using the services section of the MonitorMagic web interface. The web 



https://kraken:443, http://192.168.1.53:81, or https://192.168.1.53:443. To access the service 


the browser, and click the services section which is seen in the following example: 

Once you click on the services section you will see the following appear in the right hand pane of 

the browser window: 

348


As seen above the services section gives you some basic information about the state of all the 

services installed on your machine. The information contained in the services section will change 

depending on the machine you're accessing. If you have manage rights to a machine and you 

click the services section you will also be presented with a manage button, as seen above, for 

every service listed. By clicking on the manage button you can start or stop the service on the 

machine, as well as view dependant services, as seen below: 

If you click on either of the buttons in the figure above you will perform the associated function. To 


browser. 

See Also: 

System info 

Event logs 

Processes 

Monitors 





349


Event logs 

This section details using the application log, security log, system log, and all logs... sections of 

the MonitorMagic web interface. The web interface can be accessed by specifying a URL that 

contains the name or IP address, plus port number, of the computer running the MonitorMagic 

web service. Examples: http://kraken:81, https://kraken:443, http://192.168.1.53:81, or 

https://192.168.1.53:443. To access the event log information for a machine you must navigate to 

the name of the machine, on the left hand pane of the browser, and click one of the event log 

sections which is seen in the following example: 

The screen and all of the options for the the application log, security log, and system log are the 

same. For this reason only the system log will be detailed out of the three logs previously 

mentioned. 

Once you click on one of the event log sections you will see the following appear in the right hand 

pane of the browser window: 

As seen above the system log section gives you some basic information about all of the events 

that have taken place on your machine. The information contained in the system log section will 

change depending on the machine you're accessing. Even if you do not have manage rights to 

350


the machine you're looking at the event log, for you can still use the three buttons seen in the 

figure above. Clicking on one of them will perform the corresponding action. 

The "All logs..." section of the web interface is a little different than the application, security, and 

system event log section. If you click on the "All logs..." section you will see the following: 

Clicking on any of the buttons under the "SHOW EVENT LOGS" section will bring up the 

corresponding event log. You do not need to have manage access to use the buttons in this 

section of the page. The buttons under the "CLEAR EVENT LOGS" section will clear the 

corresponding event log, you must have manage access to perform these actions. If you attempt 

to clear one of the event logs and you do not have manage access an error page will appear. To 


browser. 

See Also: 

System info 

Services 

Processes 

Monitors 





Processes 

This section details using the processes section of the MonitorMagic web interface. The web 



https://kraken:443, http://192.168.1.53:81, or https://192.168.1.53:443. To access the processes 


the browser, and click the Processes section which is seen in the following example: 

351


Once you click on the Processes section you will see the following appear in the right hand pane 

of the browser window: 

As seen above the processes section gives you some basic information about all of the 

processes running on your machine. The information contained in the processes section will 

change depending on the machine you're accessing. There are no special management functions 

associated with processes. Users who have manage rights or read only rights can view all the 

same information concerning processes. To access another aspect of the machine choose 

another section in the left hand pane of the browser. 

See Also: 

System info 

Services 

Event logs 

Monitors 





352


Monitors 

This section details using the MonitorMagic section of the web interface. The web interface can 

be accessed by specifying a URL that contains the name or IP address, plus port number, of the 

computer running the MonitorMagic web service. Examples: http://kraken:81, https://kraken:443, 

http://192.168.1.53:81, or https://192.168.1.53:443. To access the MonitorMagic service 

information for a machine you must navigate to the name of the machine, under the MonitorMagic 

section on the left hand pane of the browser, and click it. Note that you need to have at least 

read access for the computer running the MonitorMagic service in order to use this feature. 

Once you click on the name of a machine, under the MonitorMagic section, you will see the 

following appear in the right hand pane of the browser window: 

As seen above, the machine selected under the MonitorMagic section gives you some 

information about all of the monitors and monitor policies that the service, running on the machine, 

is processing. The information contained in this section will change depending on the machine 

you're accessing, not all machines are processing the same monitors and monitor policies. There 

are no special management functions associated with this section. Users who have manage 

rights or read only rights can view all the same information concerning the monitors and monitor 

policies that are in effect. To access another aspect of a machine choose another section in the 

left hand pane of the browser. 

353


See Also: 

System info 

Services 

Event logs 

Processes 






Commands 

This section details using the Commands section of the web interface. The web interface can be 

accessed by specifying a URL that contains the name or IP address, plus port number, of the 

computer running the MonitorMagic web service. Examples: http://kraken:81, https://kraken:443, 

http://192.168.1.53:81, or https://192.168.1.53:443. To access the Commands page, press the 

Commands item in the MonitorMagic web interface navigation tree. 

Reload network data: With this command you instruct the MonitorMagic service to update its 

domain and computer information. You should use this command if you cannot find certain 

computers in the NetWork section of the navigation tree although you do have sufficient access 

rights. 

See also: 

Web interface navigation 

354

Examples 

Quick start guide (15 minutes) 

This section describes how to start using MonitorMagic immediately. It will take you only 15 

minutes to setup a MonitorMagic service and configure some monitors, rules and alarm actions. 

reports. 

Prerequisites 

Make sure you have the latest version of MonitorMagic installed. The software is 

available from www.tools4ever.com. 

Log on as an administrator to a computer of one of the following types: Windows NT 4 

workstation or server, any Windows 2000 version including: Windows 2000 Professional, 

Windows 2000 Server, or Windows 2000 Advanced server. 

MonitorMagic client Installation 

 

Install the MonitorMagic software on the computer. The MonitorMagic software is 

contained in the software package SetupMonitorMagic.exe. This package contains all of 

MonitorMagics' software components. 

MonitorMagic service installation 

 

 

Start the MonitorMagic client. When you run the MonitorMagic client for the 1st time a 

wizard will start which introduces the package. Run the wizard to start the introduction or 

continue by using the procedure described in this section to skip it. To skip the wizard 

answer no to the wizards' 1st question. 

The MonitorMagic client shows up with a screen that is mostly empty and a network 

browse window on the left. To run MonitorMagic you need to have at least one 

MonitorMagic service installed. To start installing the MonitorMagic service, browse to the 

machine you are working on, right click the machine name and select the menu option 

Setup service. 

355


 

The MonitorMagic Service Setup dialog appears. The dialog is used to specify all the 

parameters needed to install the MonitorMagic service. By default, MonitorMagic fills in 

the Server name(s) section. If you are a member of the Domain Admins group of the 

domain you are logged on to, you don't need to specify any other parameters. Leave the 

Serial number blank and press the button Install/Upgrade. 

 

 

When the service has been successfully installed, MonitorMagic will open a monitor 

window that connects to the MonitorMagic service just installed. The new monitor window 

will show a single line of text, informing you that there is nothing to show ("Connection 

established with computer xxx. No monitors configured, nothing to show here ..."). 

To start monitoring you must apply a monitor policy to the computer. Select the name of 

the local computer in the network browse window, right click the mouse, and select the 

menu options Apply policy, then Disks standard control. MonitorMagic will find and start 

monitoring the disks on the computer according to the applied policy. Some rules and 

alarm actions will be created and executed. The rules of the monitors will check if the 

available disk space is less than 10%. When this occurs, a popup message is sent to the 

current machine. 

356

Examples 

 

The results are shown in the new monitor window. If a rule is violated and triggered, the 

color of the monitored object will change. In the top part of the monitor window you can 

see the monitored objects (monitors). When a monitor is selected, you can see the 

associated rules in the bottom part of the monitor window. 

To summarize the previous steps: The MonitorMagic service is now installed on the local 

computer. From the MonitorMagic client a policy is applied. The policy contains disk monitors. 

Each disk monitor has a rule which checkins for available disk space. If the rule is violated, a 

popup message is sent to the local machine. You can now continue applying other policies to the 

same machine, or apply this policy to other machines. Next, you can configure your own policies 

and apply them to various systems. 

Generate your first Report 

357


To get an idea of how reporting works generate a report from one of our templates. First select a 

computer in the "Network" tab. Now select the "Reports" tab and click on the template you want 

to use, right click the mouse and select "open report template". You will now see what this 

template looks like. Select "generate report" from the menu bar or by right clicking your mouse 

and you will be presented with the report. 

If you want to create your own Reports, check out the Reporting part of the Help. 





358

FAQ's 

How can I open the network browse window? 

To open the network browse window, right click the mouse in the gray area. Select the menu 

option Network - Policies to open the tabbed Network - policies window. To open a browse 

window only, select the option Browse network. 

See the section different types of windows for more information. 

Do I need to install the MonitorMagic service on each monitored computer? 

No, to monitor objects on computers you have the choice of using a local or remote MonitorMagic 

service. See Single versus multiple MonitorMagic services for more information. 

Why do I get all these application event log messages? 

When monitoring performance counters, events can be reported to the application log of the 

monitored computer. In case you configure MonitorMagic to monitor these performance counter 

on a regular basis, many event log message will be generated, filling up the log. 

The events are generated by Windows NT/2000/XP when the performance counters are 

monitored by the MonitorMagic service. In most cases, the events are generated because of 

issues that deal with the configuration of system components that are mentioned in the event 

message. An example of a possible event message is: 

"The configuration information of the performance library (DLL name) for the (service 

name) service does not match the trusted performance library information stored in the 

registry. The functions in this library will not be treated as trusted." 

To prevent the generation of these events, you can specify the registry key value EventLogLevel 

at the following location: 

HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft\Windows NT \ CurrentVersion \ Perflib 

The registry key value value must be a DWORD value and can have the following values: 

Value Description 

0 no errors are reported 

1 user event log error messages (1000-1013) 

359


2 warnings and errors used for debugging (1000-2002) 

3 verbose, all information (1000-3000) 

More information on this subject can be found on the Microsoft web site, www.microsoft.com, 

search for knowledge base article Q226494. 

See also: 

Why do I get all these application event log messages (2)? 

Why do I get all these application event log messages (2) - (error 2003)? 

After you install Windows 2000 on a drive that uses the FAT or FAT32 file system (that was 

formatted during the installation process) and install Internet Information Services (IIS) in the 

same Setup process, event ID 2003 warning messages may appear in the Application event log 

when the MonitorMagic service starts reading performance counters. This issues does not occur 

with NTFS drives, if the FAT or FAT32 drive is formatted before you run Windows 2000 Setup, or 

if you add IIS later. The event ID 2003 warning message has the following text: 

The configuration information of the performance library "C:\WINNT\system32\w3ctrs.dll" 

for the "W3SVC" service does not match the trusted performance library information 

stored in the registry. The functions in this library will not be treated as trusted. 

The configuration information of the performance library "C:\WINNT\system32\infoctrs.dll" 

for the "InetInfo" service does not match the trusted performance library information 

stored in the registry. The functions in this library will not be treated as trusted. 

The configuration information of the performance library "C:\WINNT\system32\aspperf.dll" 

for the "ASP" service does not match the trusted performance library information stored in 

the registry. The functions in this library will not be treated as trusted. 

To work around this problem, run the following commands at a command prompt in 

the %SystemRoot%\System32 folder to unload and reload the IIS performance dynamic-link 

libraries (DLLs). After you run these commands, the warning messages are not logged: 

unlodctr w3svc 

unlodctr msftpsvc 

unlodctr asp 

unlodctr inetinfo 

lodctr w3ctrs.in 

lodctr ftpctrs.ini 

lodctr axperf.ini 

lodctr infoctrs.ini 

Microsoft has confirmed this to be a problem in older version of Windows 2000. The problem was 

first corrected in Windows 2000 Service Pack 2. This problem is described in Microsoft's 

Knowledge Base article Q267831, Event ID 2003 Warning Message Logged When Loading 

Performance Counters. 

See also: 

Why do I get all these application event log messages? 

Why do I get all these application event log messages (3) - (error 1008)? 

360

FAQ's 

When performance counters are monitored, application event log messages with event ID 1008 

can be generated. The event is always related to a specific service and the description has the 

following contents: 

The Open Procedure for service "InetInfo" in DLL "D:\WINNT\system32\infoctrs.dll" failed. 

Performance data for this service will not be available. Status code returned is data 

DWORD 0 

In this example, the service is InetInfo. The problem that has to do with the installation of the 

operating system or other applications as described below. 

The event may occur for various applications. When the performance monitor reads all counters 

for the first time, the extension's Open procedure is called. A typical task for the Open procedure 

is to read what range of object indexes it supports from the registry. These index values are 

stored in the First Counter, First Help, Last Counter, and Last Help registry values under the 

application's performance key. If this Open procedure fails to read the data (i.e. those entries 

don’t exist or have been deleted by an uninstall procedure) the 1008 event is recorded in the 

event log (see Microsoft's knowledgebase article Q247226 for more details). 

In order to remove such orphaned entries typically one has to follow these steps. 

Start Registry Editor (Regedt32.exe or Regedit.exe)and go to the following subkey: 

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\:\Performance 

Delete the value Open. 

Restart the remote registry service 

361

Index 

0 

0 correponds 

value 249 

0 correponds 249 

0X02 297 

0x03 297 

0x04 297 

0x06 297 

0x0A 297 

0x0D 297 

0x15 297 

0x1B 297 

0x1E 297 

1 

100th 96 

120 

value 155 

12MB 162 

133 MHz 21 

160kB 161, 162 

1840ms 116 

1st 1, 355 

2 

200 

rows 183 

2000/NT 11 

2D 8 

3 

300 

value 114 

30-day 22 

30-digit 257 

32MB 163 

3600 

value 271 

3D 

create 247 

draw 254 

rendering 245 

3D 12 

3D 245 

3D 247 

3D 247 

3D 247 

3D 248 

3D 249 

3D 252 

3D 253 

3D 254 

3D 254 

3D Graphs 245, 247, 248, 249, 250, 251, 

252, 253, 254 

3-dimensional 11, 253 

4 

40 

table 183 

5 

5PM 

9AM 10 

5PM 10 

6 

60 

set 12 

7 

7,e,1 288, 294 

8 

8,N 294 

8,None,1 288 

9 

90MB 162, 165 

999999 

value 12 

9AM 

5PM 10 

9AM 10 

A 

ABC 35 

Access 

Commands 354 

MonitorMagic 233, 234, 236, 271, 315, 

330, 353 

MonitorMagic WebService 343 

Network 212 

SNMP 101 


Access 101 

Access 212 

Access 233 

Access 234 

Access 236 

Access 271 

Access 310 

Access 315 

Access 330 

Access 334 

Access 336 

Access 343 

Access 353 

Access 354 

Access rights 

Different types 273 

Access rights 273 

Access rights 334 

According 

363


Scheduler 169 

SNMP 106 

According 106 

According 169 

Account 

Administrator 275 

MonitorMagic 157 

Account 157 

Account 275 

Account 338 

ACK 297 

Acknowledge 130 

Acknowledge rule 130 

Activate 

Extension dll 286 

Global 218 

HTTP 325 

HTTPS 325 

Manage 124, 126, 131 

manage alarm action window 132 


WebService 325 

Activate 124 

Activate 126 

Activate 131 

Activate 132 

Activate 218 

Activate 286 

Activate 325 

Activate 325 

Active Directory Users 

start 26 

Active Directory Users 26 

Active Sessions 162 

Add 

criterium 126 

new alarm action 131 

press 174 

rule 122, 123 

Use 80, 100, 104, 107, 117, 131, 150, 222, 

224, 276, 335 

Add 51, 53, 57, 60, 62, 66, 71 

Add 80 

Add 91 

Add 92 

Add 95 

Add 100 

Add 101 

Add 103 

Add 104 

Add 106 

Add 107 

Add 109 

Add 113 

Add 114 

Add 117 

Add 122 

Add 123 

Add 126 

Add 131 

Add 150 

Add 159 

Add 174 

Add 222 

Add 224 

Add 233 

Add 276 

Add 335 

Add 336 

Add button 

press 72, 80, 82, 83, 92, 101, 103, 104, 

106, 107, 109, 126, 131, 294 

pressing 107 

selecting 186 

Add button 72 

Add button 80 

Add button 82 

Add button 83 

Add button 92 

Add button 101 










Add monitor/Process 75 

Add, Delete 150 

Add, Edit 91, 168 

Add/Remove Programs applet 

choose 280 

Add/Remove Programs applet 280 

Add/Remove Windows Components 280 

Adding items 

graph 233, 247 

Adding items 233 

Adding items 247 

Address 


TCP/IP 59 

Address 59 

Address 142 

ADMIN_ON_DUTY_SYSTEM 275 

Administrative Tools 24, 26, 263, 265, 315 

Administrator 

account 275 

Administrator 136, 273 

Administrator 275 

Advanced 21, 273 

364

Index 

Advanced button 

press 69, 104, 106, 107, 109, 257, 273 

Advanced button 69 








After 30-days 22 

After MonitorMagic 345 

Agent 103 

Agent Address 286 

Alarm 

Select 132 

Alarm 131 

Alarm 132 

Alarm 218 

Alarm 282 

Alarm action execution 

Managing 135 

Alarm action execution 135 

Alarm action name 133 

Alarm actions overview 130 

Alerting 5 

All 

Use 228 

All 35, 72, 92, 127, 174 

All 228 

All 350 

ALL logeventtype 206 

All MonitorMagic plugins 316 

All rows versus specific rows 107 

Although HTTPS 345 

Always 12 

AM 

use 119 

AM 119 

AMSTERDAM 168 

Analysis 82 

AND 

mmgeneral_computername.computerid 

206 

AND 

mmgeneral_computername.computernam 

e 206 

AND mmlog_eventrecord.logdescriptionid 

206 

AND mmlog_eventrecord.loglogid 206 

AND 

mmlog_eventrecord.LogTimeGenerated 

206 

AND mmlog_logname.logid 206 

AND mmLog_logname.logname 206 

Anrich Systems 11, 291 

Applet 280 

Applications 146, 265, 271, 286, 301, 360 

Application-specific 159 

Applicattions 212 

Applictions 35 

Apply 

policy 45, 47 

Apply 1, 12, 15 

Apply 45 

Apply 47 

Apply 355 

Approximatekly 120 

Architecture SNMP traps 286 

Arrow 224 

ASCII 

corresponding 297 

ASCII 297 

Ask 

Windows 2000/NT username 327, 329 

Ask 41 

Ask 327 

Ask 329 

ASP 360 

ASP Request Queue 163 

ASP Requests/sec 163 

AT 157 

AT/AT COMPATIBLE 111 

Australia 294 

Automatic 

set 263 

Automatic 263 

Autosizing 183 

Autumn 86, 100, 111, 335 

AUTUMN/Logs/SqlServer 88 

Autumn/Logs/SqlServer7 86 

Available 

containing 77, 152 

Available 64, 68, 72 

Available 77 

Available 152 

Available 222 

Available 224 

Average Delivery Time 160 

B 

B 41, 166, 260 

Back button 15 

Background 226 

BackupLog.txt 88 

Basic Authentication 142 

Before MonitorMagic's 135, 325 

Border 226 

Browse 209, 338, 359 

Browse button 

Use 139 

Browse button 139 

Browser.1060 17 

365


Build 2195 Uniprocessor Free 111 

Building 

report template 177 

Building 177 

BUILTIN/Administrators 336 

C 

C 12, 60, 61, 65, 114, 121, 166, 257, 316, 

317, 318, 360 

Calls 

GETNEXT 106 

SNMP 149, 285 

Calls 106 

Calls 149 

Calls 285 

Cancel 29, 55 

Cascade 213 

Caused 

MonitorMagic 8, 11, 12, 15 

Caused 8 

Caused 11 

Caused 12 

Caused 15 

Central 15, 35, 37 

Central monitor policies 49 

Certificates 344 

Change 

characteristics 250 

columns 222 

plugin 12 

press 249 

sort criteria 224 

Start 120 

Change 12 

Change 120 

Change 222 

Change 224 

Change 249 

Change 250 

Change 250 

Changing database storage 

multiple items 55 

Changing database storage 55 

Characteristics 

change 250 

Characteristics 62, 65, 75, 79, 84, 85, 91 

Characteristics 250 




Check database types 306 

Checkbox 155 

Checking 

Eventviewer 301 

Internet 325, 327, 329 

MonitorMagic 265, 270, 315 

ODBC 315 

service files 270 

service registry configuration 268 

service setup 263 

service status 263, 265 

Checking 263 

Checking 263 

Checking 265 

Checking 268 

Checking 270 

Checking 301 

Checking 315 

Checking 325 

Checking 327 

Checking 329 

Checkins 1, 355 

Checklist MonitorMagic SNMP 284 

CHECKSUM 297 

CHECKSUM>%number%%me 

ssage%

Index 

COMMA 318 

Command 

access 354 


Command 113, 114, 116, 147 

Command 346 

Command 354 

Command ID 297 

Command line specification 147 

Command monitor 113, 114, 116 

Commands item 

press 354 

Commands item 354 

Committed Bytes 165 

Compaq 278 

Compaq Insight Manager 278 

Complete 


Complete 268 

Component 277 

COM-port 301 

Comptuers 346 

COMPUTER 15, 24, 26, 45, 77, 182, 184, 

187, 193, 196, 218, 263, 268, 270 

Computer B 279 

Computer Management 265 

Computer menu 12 

Computer, Apply 45 

COMPUTER/C 257 

COMPUTER/SHARE/DIR 317 

COMPUTER/Share/MonitorMagic.mdb 307 

ComputerId 204 

ComputerName 204, 206 

COMPUTERNAME/ACCOUNTNAME 257 

Computers 

shows 84 

Computers 84 

Computers 152 

Computers application 26 

Computers button 

press 168 

Computers button 168 

Computers/devices 23 

Configued 313 

Configuration 288 

Configuration overview 288 

Configuration procedure 325 

Configure 


MonitorMagic service 273 


webservice 17 

Configure 17 

Configure 29 

Configure 132 

Configure 142 

Configure 166 

Configure 168 

Configure 207 

Configure 215 

Configure 218 

Configure 226 

Configure 273 

Configure 273 

Configure 274 

Configure 276 

Configure 282 

Configure 284 

Configure 286 

Configure 291 

Configure 293 

Configure 294 

Configure 304 

Configure 305 

Configure 311 

Configure 313 

Configure 315 

Configure 336 

Configure button 

press 311 

Configure button 311 

Configure Certificate 330 

Configure MonitorMagic 29, 166, 336 

Configure MonitorMagic SNMP traps 282 

Configure MonitorMagic WebService 325, 

327, 329, 330, 332, 334, 335 

Configure Report Data Collection 166 

Configure report E-mail distribution 207 

Configure WebService 215, 325, 327, 329, 

335 

Connect Network Registry 268 

Connection 

select 288 

Connection 288 


Connects 

MonitorMagic 1, 8, 45, 168, 209, 219, 233, 

262, 325, 329, 355 

MonitorMagic WebService 325, 327 


SUMMER 335 


Connects 1 

Connects 8 

Connects 45 

Connects 168 

Connects 209 

Connects 215 

Connects 219 

Connects 233 

Connects 262 

Connects 265 

367


Connects 310 

Connects 325 

Connects 327 

Connects 329 

Connects 335 

Connects 355 

Contact 

Microsoft SNMP Service 278 

Contact 278 

Containing 

Available 77, 152 


Selected 64, 68, 77, 152 

TCP/IP 56 

Containing 21 

Containing 56 

Containing 64 

Containing 68 

Containing 77 

Containing 152 

Control 


Open 288 

Control 215 

Control 288 

Control center 215 

Control Panel 

Start 24, 26 

use 315 

Control Panel 24 




Copying 

policy 44 

Copying 44 

Corresponding 

ASCII 297 


Corresponding 8 




Count 


Count 23 

CPU 

monitoring 165 

CPU 72, 127 

CPU 165 

CPU 245 

CPU 252 

CPU 254 

CPU Load 165 

CPU Performance 165 

CPU-load 129, 136 

CR 297 

CR>%message%%number%

Index 

Data 315 

Data source 

Specify 312 

Data source 312 

Databae 313 

Database 

Stop using 315 

Database 15, 54, 55, 215, 302, 303, 304, 

305, 306, 307, 308, 309, 310, 311, 312, 

313 

Database 315 

Database 315 

Database 315 

Database ODBC 318 

Database status 

Viewing 304 

Database status 304 

Database support 110 

Database tables 

event logs 204 

Database tables 204 

Database type 

Select 307 

Database type 307 

DatabaseMaintenanceDelay 271 

Datacenter 21 

Datasource 304 

DATE 230 

DATE_TIME_NOW 180 

Datetime 204 

Decrypted 344 

Defaults 248 

Defautl 247 

Defined 

Snmp 95 

Defined 95 

Delayed rule 129 

Delete button 

press 261 

Delete button 80, 104, 107, 131 

Delete button 261 

Delete old data 313 

Deleting 

MonitorMagic 15, 215, 257, 261, 262, 268 


MonitorMagic service.1060 17 

Deleting 15 

Deleting 17 

Deleting 71 

Deleting 91 

Deleting 100 

Deleting 117 

Deleting 125 

Deleting 150 

Deleting 168 

Deleting 174 

Deleting 215 

Deleting 224 

Deleting 257 

Deleting 261 

Deleting 262 

Deleting 268 

Deleting 276 

Deleting 313 

Deleting 335 

Demo 22, 257, 271 

Descibes 280 

DescriptionId 204 

Design 

MS Access Jet 15 

Design 15 

Detailed report 228 

Details 265, 280 

Details button 

press 84 

Details button 84 

DEVELCON 278 

DHCP Event Errors 164 

Dialing 288 

Different types 

access rights 273 

windows 209 



Digital Certificates 344 

Direction 224 

Directory 7 

Directory Service 170 

Disk monitor 

Creating 60 

Disk monitor 60 

Disk monitor 60 

Disk monitor values 61 

Disks 1, 60, 355 

Diskspace 7, 50 

Display 221, 222, 223, 224, 226, 250, 251, 

252 

Display menu 

select 225 

Display menu 225 

Distributed Transaction Coordinator 161, 

162 

Divide W 31 

Dll 

locate 286 

SNMP 286 

Dll 284 

Dll 286 

DLL's 270, 271, 359, 360 

DNS 

shows 26 

specify 58 

369


DNS 26 

DNS 58 

DNS 59 

DNS 142 

DNS 170 

DNS 271 

DNS Server 164 

DNS-name 59 

Dockable 213 

Dockable bar 213 

Dockable window 

position 213 

Dockable window 213 

Domain 26, 31 

Domain Admins 1, 257, 355 

DOMAIN NAME/USER OR GROUP 338 

DOMAIN/ACCOUNTNAME 257 

Domains application 

User Manager 263 

Domains application 263 

Down 224 

Downgrade 


Downgrade 15 

Drag 47, 236 

Draw 

3D 254 

grey 241 

Draw 241 

Draw 254 

Drop 47 

Drop multiple items 236 

DSN 310 

DWORD 271, 359 

DWORD 0 360 

E 

EARTH 31, 168, 196 

Edit 15, 80, 100, 104, 117, 124, 131, 221, 

223, 226, 250, 268, 276 

Edit button 

Press 113, 114, 126, 132, 238, 250, 294, 

313 

prsss 92 

Edit button 92 










EGP 96 

Elmo 336, 345 

Elses 344 

E-mail 

Enter 142 

send 99, 136, 271 

want 207 

E-mail 8, 10, 11, 12, 15 

E-mail 99 

E-mail 129 

E-mail 130 

E-mail 135 

E-mail 136 

E-mail 140 

E-mail 141 

E-mail 142 

E-mail 207 

E-mail 215 

E-mail 271 

E-mail 275 

E-mail 287 

E-mail message contents 141 

E-mail message destination 140 

Enable 

MonitorMagic 327, 329 

Enable 252 

Enable 327 

Enable 329 

Enabled. 329 

End 119 

Enter 

E-mail 142 

URL 325 

username 327, 329 

Enter 142 

Enter 325 

Enter 327 

Enter 329 

Enterprise-class 5 

EOT 297 

EOT>PG1%password%

Index 

Event 69 

Event 265 

Event 286 

Event ID 2003 Warning Message Logged 

When Loading Performance Counters 360 

Event log advanced settings 69 

Event log monitor values 70 

Event log specification 68 

Event logs 

Database tables 204 

Sample queries 206 

Event logs 204 



Event Rules 160, 161, 162, 163, 164, 165 

Eventlog 12, 18, 206, 284 

EventLogLevel 359 

Eventlogs 206 

Eventlogtype 206 

Events monitor 66 

Eventsource 206 

Eventviewer 

Check 301 

Eventviewer 301 

Examine 

SNMP 99, 101, 103 

Examine 99 

Examine 101 

Examine 103 

Example 196 

Except 

Server 257 

Except 257 

Exceptions 117 

Exceptions intervals 

Scheduling 119 

Exceptions intervals 119 

Exchange 

log 160 

Exchange 150 

Exchange 160 

Exchange 160 

Exchange 168 

Exchange 2000 142 

Exchange 5.5/2000 159 

Exchange-specific 160 

Exclude 117 

EXE 65 

Exected 15 

Execute 

SQL 318 

Execute 318 

Exisitng 

select 312 

Exisitng 312 

Existance 14 

Existing 

monitor 123 

Existing 83 

Existing 123 

Existing content 83 

Exiting 


Exiting 236 

Explain/describe 149 

Export 15 

Extension dll 

activate 286 



F 

F 316, 318 

F1 15 

F5 215 

Failed/succeeded 135 

FALSE 121, 127 

FAT 

uses 360 

FAT 360 

FAT32 360 

FAT32 file 360 

Features 18 

Features MonitorMagic version 7, 10 

Features MonitorMagic version 2.0 17 



February 

JUPITER 196 

February 17 

February 196 

Fiel Pings 10 

File 

selecting 227, 236 

Show 86 

File analysis 82 

File menu 242 

File monitor values 88 

Find 

mib file 99 


NETBIOS 26 

NETBIOS domain name 24, 26 

ODBC 307 

TCP/IP 10 

Find 10 

Find 24 

Find 26 

Find 99 

Find 263 

Find 265 

Find 307 

Finish 15, 307, 312 

371


First 119 

First Counter 360 

First Help 360 

FISH 26 

Fish.tools4ever.internal 26 

Fixes MonitorMagic version 8, 10 

Fixes MonitorMagic version 1.0 18 




FLOWERS 24, 31 

FLOWERS/MonitorMagicSvcAccnt 65 

Following 


OR 127 

Report 168 

subkey 360 

Following 127 

Following 168 

Following 273 

Following 360 

Font - Header 230 

Font - Regular 230 

Font - Strong 230 

Font styles 202 

Fonts 

press 226 

Fonts 202 

Fonts 226 

Footer 203, 230 

Forms 

SNMP 278 

Forms 278 

Formula calculation 109 

From 

list 280 

FROM 

mmgeneral_computername,mmlog_event 

record,mmlog_description 206 

FROM 

mmgeneral_computername,mmlog_event 

record,mmlog_description,mmlog_source 

Name,mmlog_logname 206 

FROM 

mmlog_eventrecord,mmlog_Description,m 

mlog_sourceName 206 

FromAddress 271 

FTP Publishing Service 163 

G 

Generate 

report 177 

SNMP 96, 282, 283 

Generate 96 

Generate 106 

Generate 107 

Generate 177 

Generate 282 

Generate 283 

Generate Snmp 107 

Generic Trap Type 286 

Get 

succesfull 282, 283 

Get 174 

Get 282 

Get 283 

Get All 

Press 103 

Get All 101 

Get All 103 

Get all these application event log 

messages 359, 360 

GETNEXT 

calls 106 

GETNEXT 101 

GETNEXT 106 

Getting all data 103 

Global 

Activating 218 

Updating 218 

Global 7 

Global 218 

Global alarm window 218 

Grant 


Grant 257 

Graph 

Adding items 233, 247 

Creating 234 

Printing 242 

Graph 233 

Graph 233 

Graph 234 

Graph 236 

Graph 236 

Graph 236 

Graph 237 

Graph 238 

Graph 239 

Graph 241 

Graph 242 

Graph 244 

Graph 245 

Graph 247 

Graph 247 

Graph window 232 

Graph, Add 247 

Grey 

draw 241 

Grey 35, 209 

Grey 241 

Grid 237 

372

Index 

GROUP BY 

logeventtype,sourcename,Computername 

206 

GUI 17 

Guidelines 99 

H 

Help 

part 1, 355 

Help 1 

Help 355 

Help button 

pressing 15 

Help button 15 

Help window 

place 14 

Help window 14 

Helpodbc 318 

Hewlett Packard 278 

HEY_LOCAL_MACHINE/SYSTEM/CurrentC 

ontrolSet/Services/SNMP/Parameters/Ext 

ensionAgents 284 

HH 

Use 119 

HH 119 

Highlighting 

new results 225 

Highlighting 225 

HIGHLY 324 

Hight 183 

HKEY_LOCAL_MACHINE 359 

HKEY_LOCAL_MACHINE/SOFTWARE/Too 

ls4ever/MonitorMagic/Service/SnmpTrap 

284 

HKEY_LOCAL_MACHINE/SYSTEM/Current 

ControlSet/Services 268 

HKEY_LOCAL_MACHINE/SYSTEM/Current 

ControlSet/Services/


Implementing 

HTTPS 327, 329 


Implementing 324 



Import 15, 330 

Importing report templates 177 

Inactive Sessions 162 

Inc 99 

Include 117 

Includeds 119 

Indexing 

Service 163 

Indexing 163 

InetInfo 360 

Info 155 

Information 

Logging 262 

Information 262 

Initiate 

SNMP 286 

Initiate 286 

Innumerous 178 

Insert 

OR 127 

Insert 127 

Insert button 

press 80, 138 

Insert button 80 

Insert button 138 

Install 

MDAC 303, 308 

Microsoft's SNMP 277 


257, 260, 325, 355 

MontiorMagic 257 

ODBC 306 

SNMP 280, 284 

SNMP service 280 

SNMP Trap 280 


Install 1 

Install 12 

Install 21 

Install 21 

Install 22 

Install 31 

Install 41 

Install 215 

Install 256 

Install 257 

Install 260 

Install 277 

Install 280 

Install 284 

Install 303 

Install 303 

Install 306 

Install 308 

Install 325 

Install 355 

Install MonitorMagic 166 

Install/Upgrade 1, 257, 355 

Installation 1, 325, 355 

Instruct 


SNMP 286 

Instruct 286 

Instruct 305 

Instruct 311 

Instruct 315 

Instruct 354 

Interface.1060 17 

Internal Memory Performance 165 

INTERNAL_VALUE_REPORTGENERATIO 

NDATE 196 

INTERNAL_VALUE_REPORTGENERATIO 

NPERIOD 196 

Internet 

check 325, 327, 329 

Start 86 

use 99 

Internet 79 

Internet 86 

Internet 99 

Internet 324 

Internet 325 

Internet 327 

Internet 329 

Internet 332 

Internet 343 

Internet 343 

Internet 345 

Internet browser window 86 

Internet Information Server 

log 163 

Internet Information Server 163 

Internet Information Services 159, 360 

Internet Management 

Introduction 99 

Internet Management 99 

Internet site 99 

Interval 215 

Intranet 324, 332, 343 

Introduction 

Internet Management 99 

MonitorMagic Web Interface 323 

pager 287 

SNMP traps 278 



374

Index 







IP 

know 325 

resolve 325 

IP 59, 286 

IP 325 

IP 335 

IP 346 

IP 347 

IP 348 

IP 350 

IP 351 

IP 353 

IP 354 

Iso.3.6.internet.private.enterprises.tools4eve 

r.monitormagic 286 

Iso.3.6.internet.private.enterprises.tools4eve 

r.monitormagic.1.2.0 286 

Iso.org.dod.internet.mgmt.mib- 

2.interfaces.ifTable.ifEntry 106 


2.interfaces.ifTable.ifEntry.ifInOctets 106, 

109 


2.interfaces.ifTable.ifEntry.ifOutOctets 106 

Issue 

SNMP GET 101 

SNMP GETNEXT 101 

Issue 101 

Item display 244 

Item Properties 178 

Item scale 245 

Items 178, 238, 250, 251, 252 

J 

January 7, 8, 204 

Jet 271, 303 

Jet Engine 303 

John 345 

July 10 

JUPITER 

February 196 

JUPITER 168 

JUPITER 196 

JVRLOG.DLL 270 

K 

KB 78, 270, 317 

Keyword 275 

Keywords overview 275 

Keywords, Insert 80, 145, 295 

Know 

IP 325 


NETBIOS 23 

Know 23 

Know 270 

Know 325 

KRAKEN 78, 88, 94, 325, 336, 346, 347, 

348, 350, 351, 353, 354 

L 

Last 119 

Last Counter 360 

Last Help 360 

Leave 

Serial 1, 355 

Leave 1 

Leave 355 

Left-center-right 180 

Let 

MonitorMagic 10, 41, 145, 260, 295 

Let 10 

Let 41 

Let 145 

Let 260 

Let 295 

LF 297 

Licence 17 

License 



License 23, 29 

License 32 

License 303 

License 343 

LicenseKey 271 

Limit/Reference 127 

Line 225, 226, 252 

Line display properties 226 

Link 

Tools4ever 12 

Link 12 

List 

From 280 

Listening 

HTTP 325 

Listening 325 

Lnk 96 

Load 

Press 226 

Load 226 

Local 

open 35 

Local 15 

Local 35 

Local 37 

Local 49 

LocalSystem 65 

Locate 

375


dll 286 

Locate 286 

Lodctr 360 

Lodctr w3ctrs.in 360 

Log 

Exchange 160 

information 262 

Internet Information Server 163 

SQL Server 161, 162 

Log 68 

Log 160 

Log 160 

Log 161 

Log 162 

Log 163 

Log 262 

Log 265 

Log events 146 

Log On As 263 

Log1.txt 88 

Log2.txt 88 

Log3.txt 88 

LogComputerId 204 

LogDescriptionId 204 

LogEventCategory 204 

LogEventId 204 

LogEventRecordId 204 

LogEventRecordid,logtimeGenerated,logeve 

ntid,logeventtype,logeventcategory 206 

LogEventType 204 

Logeventtype,computername 206 

Logfile 204 

LogId 204 

LOGIN 

name 142 

LOGIN 142 

LogLogId 204 

LogMonitorMagicComputerId 12, 204 

LogMsgDirectory 271 

LogName 204 

Logon ID 

specify 309 

Logon ID 309 

LOGON_ID 310 

Logs/SqlServer 80 

LogSourceId 204 

LogTimeGenerated 204 

LogTimeWritten 204 

LogUserId 204 

LSASS.EXE 78 

M 

Mailserver.tools4ever.com 142 

Mailslot 286 

Maintainenance 12 

Man 345 

Manage 

activate 124, 126, 131 

alarm action execution 135 


Snmp 100 

Manage 39, 41 

Manage 100 

Manage 122 

Manage 123 

Manage 124 

Manage 126 

Manage 131 

Manage 135 

Manage 271 

Manage 305 

Manage 311 

Manage 315 

Manage 340 

Manage alarm action window 

Activating 132 

Manage alarm action window 132 

Manage button 

Press 291, 293, 294 

Manage button 291 



Manage report profiles 168 

Manage services 150 

Management 280 

Management application 280 

Management Information Base 99, 103 

Mappings 297 

March 196 

Mars 31, 61, 65, 70, 74 

Marshall T 99 

Matching file 7 

May 24 14, 15 

MB 21, 61, 270, 317 

MDAC 

install 303, 308 

part 303 

MDAC 303 

MDAC 303 

MDAC 308 

MDAC 311 

Mdb 304 

Mega 61 

Memory 72 

Memory Usage 75, 78 

Memory, Available 74 

Mgmt 106 

MHz 21 

MIB 99, 103 

Mib file 

find 99 

Mib file 99 

Mib file 99 

376

Index 

Mib-2 106 

MIB-II 106, 109 

Microsoft 

See 303 

SNMP 279 

Microsoft 91, 278 

Microsoft 279 

Microsoft 284 

Microsoft 286 

Microsoft 303 

Microsoft 303 

Microsoft 359 

Microsoft Clustering 91 

Microsoft Data Access Components 

part 303 

Microsoft Data Access Components 303 

Microsoft Database Access Components 

303 

Microsoft Exchange 2000 160 

Microsoft Exchange 5.5 160 

Microsoft Exchange 5.5. 160 

Microsoft Exchange Directory 160 

Microsoft Exchange Event 160 

Microsoft Exchange Event Service 160 

Microsoft Exchange IMAP4 160 

Microsoft Exchange Information Store 160 

Microsoft Exchange Message Transfer Store 

160 

Microsoft Exchange MTA Stacks 160 

Microsoft Exchange POP3 160 

Microsoft Exchange Routing Engine 160 

Microsoft Exchange Site Replication Service 

160 

Microsoft Exchange System Attendent 160 

Microsoft Internet Information Service 5.0. 

163 


163 

Microsoft Jet 303 

Microsoft Jet Engine 

obtain 303 

use 303 

Microsoft Jet Engine 303 




Microsoft Office 308 

Microsoft Search 162 

Microsoft Server Manager application 

op 263 

Microsoft Server Manager application 263 

Microsoft SNMP 

install 277 

requires 277 

start 286 

Microsoft SNMP 95, 98, 99 

Microsoft SNMP 277 








Microsoft SQL Server 2000 162 

Microsoft SQL Server 7.0 161 

Microsoft SQL Server 7.0. 161 

Microsoft Windows 

running 256 

Microsoft Windows 21 


Microsoft Windows 2000 21, 256 

Microsoft Windows 2000 Terminal Services 

162 

Microsoft Windows Installer 

uses 22 

Microsoft Windows Installer 22 

Microsoft Windows NT 4.0 21 

Microsoft Windows NT 4.0. 

running 288 

Microsoft Windows NT 4.0. 256 


Microsoft Word 297 

Microsoft/Windows NT 359 

Microsoft's Knowledge Base 360 

Microsoft's knowledgebase 

refer 15 

Microsoft's knowledgebase 15 



Microsoft's SNMP Service 

contact 278 

Microsoft's SNMP Service 278 



Middle attack 345 

Mike 336, 345 

Milli 59, 116 

MM 119 

MmComputerId 204 

MmComputerName 204 

MmGeneral_ComputerName 

Relates 204 

MmGeneral_ComputerName 204 

MmGeneral_MonitorMagicComputer 

Relates 204 

MmGeneral_MonitorMagicComputer 204 

MmLog_Description 204 

Mmlog_description.descriptionid 206 

MmLog_EventRecord 

Relates 204 

MmLog_EventRecord 12 

377



Mmlog_eventrecord.logcomputerid 206 

Mmlog_eventrecord.loglogid 206 

MmLog_LogName 

Relates 204 

MmLog_LogName 204 

Mmlog_logname,mmgeneral_computernam 

e 206 

Mmlog_logname.logid 206 

MmLog_SourceName 

Relates 204 

MmLog_SourceName 204 

Mmlog_sourceName,mmlog_logname 206 

Mmlog_sourcename.sourceid 206 

MmLog_UserName 

Relates 204 

MmLog_UserName 204 

MmSvcDir/NM.EXE 65 

Model 111 

Modems 288 

Monitor 

CPU 165 

Create 53 

existing 123 

Sorting 223 

Windows Network Services 164 

Monitor 53 

Monitor 79 

Monitor 80 

Monitor 80 

Monitor 82 

Monitor 83 

Monitor 84 

Monitor 85 

Monitor 86 

Monitor 88 

Monitor 123 

Monitor 164 

Monitor 165 

Monitor 167 

Monitor 220 

Monitor 223 

Monitor 244 

Monitor 280 

Monitor 353 

Monitor data 54 

Monitor keywords 276 

Monitor Magic 1 

Monitor Magic 5.0 1 

Monitor policy window 35 

Monitor Value 78, 88, 94, 96, 111, 116 

Monitor Window 

Columns 221 

Open 219 

Monitor Window 17 





Monitor, Name 62, 66, 71, 75 

MonitorDiskData 193, 196 

MonitorDiskDefinition 193, 196 

Monitored computer 359 

MonitoringMagic 260 

MonitorListFile 271 


access 271, 330 

accessing 233, 234, 236, 315, 353 

account 157 

address 142 

cause 8, 11, 12 

caused 15 

check 265, 270, 315 

commands 346 

complete 268 

Configure 215, 286 

configuring 273, 284 

connects 1, 8, 45, 168, 209, 219, 233, 262, 

325, 329, 355 

contains 21 

control 215 

corresponding 8, 209, 219 

count 23 

create 305 

delete 215, 261, 262, 268 

deleting 15, 257 

downgrade 15 

enable 327, 329 

exiting 236 

find 263, 265 

following 273 

grant 257 

implementing 324 

install 1, 12, 21, 22, 31, 41, 256, 257, 260, 

325, 355 

instruct 305, 311, 315, 354 

know 270 

let 10, 41, 145, 260, 295 

license 32, 343 

manage 271 

number 23, 265 

obtain 23 

order 280, 306 

parcel 32, 343 

parts 11, 21, 275 

reason 268 

represents 31 

Required - When 279 

rights 273 

rules 318 

running 282 

378

Index 

runs 1, 8, 10, 12, 15, 21, 23, 29, 41, 45, 

49, 56, 59, 61, 65, 70, 74, 78, 80, 88, 94, 

95, 96, 99, 111, 113, 114, 116, 142, 145, 

157, 204, 207, 209, 218, 219, 226, 261, 

263, 265, 273, 274, 276, 277, 280, 284, 

287, 288, 291, 293, 294, 295, 303, 304, 

305, 306, 307, 308, 311, 313, 315, 335, 

346, 347, 348, 350, 351, 353, 354, 355 

select 41, 268 

SNMP 282 

specify 29, 41, 274 


start 1, 15, 29, 37, 41, 142, 256, 257, 268, 

274, 276, 291, 293, 294, 355 

suppose 50 

tell 330 

types 273 

understanding 50 

upgrade 15, 22, 256, 257 

use 41, 273, 323, 324, 327, 329, 343 

want 114, 147, 257, 327, 329 

Welcome 1 



























































































379


















































































































380

Index 




































MonitorMagic About 15 

MonitorMagic access rights 

Specifying 274 

MonitorMagic access rights 274 

MonitorMagic application 

start 236 

MonitorMagic application 35 


MonitorMagic E-mail 142 

MonitorMagic license 23 

MonitorMagic license codes 

multiple services 31 

MonitorMagic license codes 31 

MonitorMagic plugin 114, 316 

MonitorMagic Plugins 8, 11, 113, 316 

MonitorMagic Reporting 167 

MonitorMagic reseller 22, 31, 257, 265, 297, 

301 

MonitorMagic Service 

Configuring 273 

Deleting 261 

upgrading 256 

MonitorMagic Service 24, 26, 78, 88, 94, 96, 

166 

MonitorMagic Service 256 




MonitorMagic service license code 

Specifying 29 

MonitorMagic service license code 29 

MonitorMagic service registry settings 271 

MonitorMagic service setup 257 

MonitorMagic Service Setup dialog 1, 261, 

355 

MonitorMagic service.1060 

deleting 17 

MonitorMagic service.1060 17 

MonitorMagic site 29, 257 

MonitorMagic SNMP 

part 277 

MonitorMagic SNMP 277 

MonitorMagic SNMP 278 

MonitorMagic SNMP requirements 277 

MonitorMagic SNMP support 277 

MonitorMagic SNMP traps 

Troubleshooting 284 

MonitorMagic SNMP traps 284 

MonitorMagic SNMP traps software 

Testing 283 

MonitorMagic SNMP traps software 283 

MonitorMagic Web 

supports 17 

MonitorMagic Web 17 




MonitorMagic Web Interface 14, 86, 111 



MonitorMagic Web Interface license 32, 343 

MonitorMagic Web Interface scenarios 324 

MonitorMagic Web Service 

running 86 

runs 12 

MonitorMagic Web Service 12 

MonitorMagic Web Service 86 

MonitorMagic WebInterface 

use 335 

MonitorMagic WebInterface 335 

MonitorMagic WebService 

access 343 

Activate 325 

Configure 215 

connect 325, 327 

part 334 

runs 324, 325, 335 

381


use 332 














MonitorMagic WebService HTTP 327 

MonitorMagic WebService HTTPS 329 

MonitorMagicDataSource 310 

MonitorMagic's HTTPS 330 

MonitorMagicSvcAccnt 257 

MonotorMagic Service 

running 146 

MonotorMagic Service 146 

MontiorMagic 

installing 257 

MontiorMagic 257 

Most ODBC 303 

Ms 111, 116, 316, 317 

MS Access 

use 303 

MS Access 8, 14, 15, 271, 302, 303 

MS Access 303 

MS Access 304 

MS Access 307 

MS Access 307 

MS Access 311 

MS Access 2000 303 

MS Access 97 303 

MS Access Jet 

design 15 

MS Access Jet 15 

MS TCP Loopback 106 

MSSQLServer 161, 162 

MSSQLServerADHelper 162 

Multiple items 

Changing database storage 55 

Multiple items 55 

Multiple MonitorMagic 260 

Multiple services 

MonitorMagic license codes 31 

Multiple services 31 

Multivalue 

use 196 

Multivalue 196 

Multivalue variables 196 

N 

N 23, 31 

NAK 297 

Name 

custer 94 

Login 142 

SNMP 286 


TCP/IP 59 

Name 59 

Name 94 

Name 133 

Name 142 

Name 199 

Name 286 

Name 308 

Name.1060 17 

Navigation 213 

Need 

uninstall 22 

Need 22 

Need 359 

NET/XP 11 

NET/XP/2000/NT 245 

NETBIOS 

equal 26 

find 26 

know 23 

shows 26 

use 257 

NETBIOS 23 

NETBIOS 24 

NETBIOS 26 

NETBIOS 59 

NETBIOS 215 

NETBIOS 257 

NETBIOS domain name 

find 24, 26 

NETBIOS domain name 24 

NETBIOS domain name 26 

NETLOGON 164 

Network 

accessing 212 

Network 1, 35, 209 

Network 212 

Network 218 

Network 256 

Network 346 

Network 354 

Network 355 

Network 359 

Network applet 

start 24 

Network applet 24 


open 359 

Network browse window 212 

Network browse window 359 

382

Index 

Network Identification 

Select 26 

Network Identification 26 

New 212 

New alarm action 

Adding 131 

New alarm action 131 

New database 

Create 305 

New database 305 

New graph 

Creating 233, 247 

New graph 233 

New graph 247 

New policy 

Creating 37 

New policy 37 

New results 

Highlighting 225 

New results 225 

Next 15, 280, 307, 308, 309, 311 

Next, MonitorMagic 121, 136 

NIC's 8 

NM.EXE 270 

NMC4000 278 

NmDesktop.cfg 8 

NmMonPol.cfg 49 

NMMSG.DLL 270 

No 

selected 340 

Noheaders 318 

Nolog 318 

None, Stop 288 

Non-USA 288 

Normal Windows 2000 Professional 

Computer 37 

Nostats 318 

Novell 11 

November 29 11, 12 

Now 327 

Now XP 17 

NSVCSETUP 12 

NT 5, 329 

NTFS 360 

Number 

ICMP Echo Requests 59 


SNMP 23 

subidivsion 252 

Windows NT/2000 274 

XXX 155 

Number 23 

Number 59 

Number 100 

Number 155 

Number 252 

Number 265 

Number 274 

Nvarchar 204 

O 

O 318 

Obeys 

RFC's 8 

Obeys 8 

Object 101, 106, 107, 109 

Object identifier specification 101 

Object identifiers 99 

Object-counter-instance 74 

ObjectOid 286 

Obtain 



Snmp 111 

Obtain 23 

Obtain 111 

Obtain 303 

Occured 96 

ODBC 

Check 315 

find 307 

install 306 

ODBC 14, 302, 304 

ODBC 306 

ODBC 307 

ODBC 308 

ODBC 315 

ODBC 315 

ODBC 318 

ODBC datasource 318 

Oid 

values 111 

Oid 96 

Oid 111 

Oid 286 

Oid1 

value 109 

Oid1 104 

Oid1 109 

Oid2 109 

OK 12, 55, 59, 61, 64, 65, 68, 70, 74, 77, 78, 

88, 94, 96, 111, 116, 152, 207, 218, 233, 

236, 252, 262, 265, 268, 280, 282, 284, 

288, 291, 293, 304, 324, 330, 338, 344 

OK button 

press 24, 37, 131, 268, 274, 276, 313 

OK button 15 

OK button 24 

OK button 37 

OK button 131 

OK button 268 

OK button 274 

OK button 276 

383


OK button 313 

Only 92 

Op 

Microsoft Server Manager application 263 

Op 263 

Open 

Control 288 

Local 35 

monitor window 219 

network browse window 359 

Snmp 103 

Open 35 

Open 103 

Open 209 

Open 219 

Open 236 

Open 288 

Open 359 

Open 360 

Open Procedure 360 

OpenGL 245 

Operatie 279 

Operator 127 

Opion Show 3D 247 

Optional - The SNMP 279 

Optional - The SNMP Trap 279 

Options 239 

OR 

following 127 

insert 127 

OR 127 

Order 


SNMP 149, 285 

SNMP Management application 280 

Order 149 

Order 280 

Order 280 

Order 285 

Order 306 

ORDER BY logtimegenerated DESC 206 

ORDER BY 

sourcename,logeventtype,computername 

206 

Org 106 

Orientation 254 

OtherUtils 114 

Ouput 

plugin 317 

Ouput 317 

Output 116 

Overview 


Overview 79, 95, 98, 113 

Overview 117 

Overview 166 

Overview 170 

Overview report templates 175 

Overview window 170 

P 

P

Index 

Part 334 

Part 355 

PASSWORD 309, 310 

Paste 44 

Path specification 80 

PDU TYPE 286 

Pentium 21 

Pentium III 21 

Perflib 359 

Performance 

Use 72 

Performance 71 


Performance counter monitor 71 

Performance Counter Rules 160, 161, 162, 

163, 165 

Performance counter specification 72 

Performance counter values 74 

PERIOD 190 

Ping monitor 

Creating 57 

Ping monitor 56 

Ping monitor 57 

Ping monitor values 59 

Pings 10, 57 

Place 

Help window 14 

Place 14 

Plain 142 

Planes 253 

PLANETS 31 

Plugin 

changing 12 

ouput 317 

Plugin 7 

Plugin 12 

Plugin 114 

Plugin 316 

Plugin 316 

Plugin 317 

Plugin 317 

Plugin 318 

Plugins 8, 11, 114 

PM 119 

Point 

SNMP 279 

Point 279 

Policy 

Applying 45, 47 

Copying 44 

select 35, 209 

Policy 15 

Policy 35 

Policy 39 

Policy 44 

Policy 45 

Policy 47 

Policy 49 

Policy 53 

Policy 209 

Policy 359 

Policy Change Event 165 

Policy Changes 165 

Policy monitor 51, 122 

Policy options 

Specifying 39 

Policy options 39 

Policy service selection 

Specifying 41 

Policy service selection 41 

Policy.1222 8 

Pop3 325, 327, 329 

Popup 

sending 17 

Popup 1, 5, 15 

Popup 17 

Popup 127 

Popup 130 

Popup 136 

Popup 138 

Popup 138 

Popup 139 

Popup 275 

Popup 355 

Popup menu 215 

Popup menu Policy 37 

Popup message 138 

Popup message destination 138 

Popups 

part 138 

Popups 138 

Portnumber 317 

Position 

dockable window 213 

Position 213 

Preceed 318 

Pre-defined Policies 159 

Prentice-Hall 99 

Press 

Add 174 

Add button 72, 80, 82, 83, 92, 101, 103, 

104, 106, 107, 109, 126, 131, 294 

Advanced button 69, 104, 106, 107, 109, 

257, 273 

Change 249 

Color button 237 

Commands item 354 

Computers button 168 

Configure button 311 

Create button 305 

Delete button 261 

Details button 84 

385


Edit button 113, 114, 126, 132, 238, 250, 

294, 313 

Font 226 

Get All 103 

Insert button 80, 138 

Load 226 

Manage button 291, 293, 294 

OK button 24, 37, 131, 268, 274, 276, 313 

Properties button 251, 252, 288 

Refresh button 72 

Show button 85 

Start button 103, 263 

Startup button 263 

Stop button 103, 315 

Test button 117, 120 

Test SNMP 282 

View button 84, 85 

Press 24 

Press 37 

Press 69 

Press 72 

Press 80 

Press 82 

Press 83 

Press 84 

Press 85 

Press 92 

Press 101 

Press 103 

Press 104 

Press 106 

Press 107 

Press 109 

Press 113 

Press 114 

Press 117 

Press 120 

Press 126 

Press 131 

Press 132 

Press 138 

Press 168 

Press 174 

Press 226 

Press 237 

Press 238 

Press 249 

Press 250 

Press 251 

Press 252 

Press 257 

Press 261 

Press 263 

Press 268 

Press 273 

Press 274 

Press 276 

Press 282 

Press 288 

Press 291 

Press 293 

Press 294 

Press 305 

Press 311 

Press 313 

Press 315 

Press 354 

Press Finish 310 

Press GET DATA 106 

Press GetNext 101 

Press Next 306 

Press OK 29, 242 

Press Save 265 

Pressing 

Help button 15 

Verify button 29 

Pressing 15 

Pressing 29 

Pressing 107 

Pressing 263 

Pre-Windows 2000 26 

Print 

graph 242 

reports 227 

select 242 

Print 8, 168, 203 

Print 227 

Print 228 

Print 229 

Print 230 

Print 242 

Print header 203 

Process ID 75, 78 

Process monitor 75 

Process values 78 

Processes 

create 152 

Processes 152 

Processes 351 

Processor 72 

Processor Time 129, 162, 163 

Professional, Server 21 

Program 

Files/MonitorMagic/NSVCSETUP/NM.EX 

12 

Program 

Files/Tools4ever/MonitorMagic/ReportTe 

mplates 207 

Programs 21, 24, 263, 265, 315 

Properties 

selecting 132 

Properties 15, 26, 39, 41, 55, 117, 120, 123 

386

Index 

Properties 132 















Properties button 

Press 251, 252, 288 

Properties button 251 



Properties menu 

select 84, 85 

Properties menu 84 

Properties menu 85 

Protocol/Internet 325, 327, 329 

Provider configuration settings 293, 294 

Proxy 335 

Proxy MonitorMagic 335 

Prsss 


Prsss 92 

Purchased version 22 

Q 

Q 318 

Q154384 15, 303 

Q226494 359 

Q247226 360 

Q267831 360 

Q4-2002 245 

Querying 

SNMP 103 

Querying 103 

Quick start guide 1, 355 

R 

RAM 8, 21 

Ranegs 247 

RAS Event Errors 164 

Read 

table 106 

Read 106 

Read 236 

Read 340 

Read SQL 318 

Real monitors 51 

Reason 


Reason 268 

Reboot computer 155 

Rebooted 8, 12, 155, 157 

Receiced 95 

Receievd 282, 283 

Receiving 

ICMP 59 

SNMP 95, 277 

Receiving 59 

Receiving 95 

Receiving 277 

Recommened 49 

Refer 


Refer 15 

Refresh 92 

Refresh button 

Press 72 

Refresh button 72 

Regedit 268 

Regedit.exe 360 

Regedt32 284 

Regedt32.exe 360 

Registry 268 

Relates 

MmGeneral_ComputerName 204 

MmGeneral_MonitorMagicComputer 204 


MmLog_LogName 204 

MmLog_SourceName 204 

MmLog_UserName 204 

Relates 204 

Relates MmLog_EventRecord 204 

Release 15 

Remove 222 

Removed.1060 17 

Rename menu 12 

Renames.1060 17 

Rendering 

3D 245 

Rendering 245 

Replication 170 

Report 

following 168 

Generate 177 

Printing 227 

Stopped 15 

Report 1 

Report 15 

Report 166 

Report 168 

Report 170 

Report 175 

Report 177 

Report 207 

Report 227 

387


Report 355 

Report E-mail 7, 207 

Report item graphical element 185 

Report item picture 186 

Report item subreport 184 

Report item table 182, 183 

Report item text 180 

Report Items 178, 180, 182, 185 

Report profile data storage 169 

Report profiles 167 

Report template 

Building 177 

Report template 175 

Report template 177 

Report template properties 199, 200, 201, 

202, 203 

Report template tree 175 

Report Variable 178 

Report variable period value specification 

190 

Report variable query 193 

Report variable text value specification 189 

Report variable time-date value specification 

191 

Report variable user input 187 

Represents 


Represents 31 

Required - The SNMP 279 

Required - When 


Required - When 279 

Requirements 21 

Requirements SNMP traps 280 

Requires 

Microsoft's SNMP 277 

Requires 277 

Reseller 32, 343 

Resolve 

IP 325 

Resolve 325 

Respond 

ICMP 58 

TCP/IP 10 

Respond 10 

Respond 58 

Restore 254 

RESULT_DATA_DISK_NAME 276 

RESULT_DATA_name 276 

RESULT_DATA_TIME 18 

Results 

SQL 318 

Updating 226 

Results 101 

Results 226 

Results 228 

Results 318 

RFC1213 106 

RFC's 

obeys 8 

RFC's 8 

RFC's 821 8 

RID 12 

Rights 


Rights 273 

Rights.1060 17 

Rose, ISBN 0-13-177254-6 99 

Rownumbers 318 

Rows 

200 183 

Rows 183 

RS 297 

Rule 

Adding 122, 123 

Choose 132 


Rule 122 

Rule 123 

Rule 124 

Rule 125 

Rule 126 

Rule 129 

Rule 132 

Rule 318 

Rule area 220 

Rule criteria 


Rule criteria 127 

Rule name 124 

Rule specification 125 

Rules overview 121 

Running 



MonitorMagic 1, 8, 10, 12, 15, 21, 23, 29, 

41, 45, 49, 56, 59, 61, 65, 70, 74, 78, 80, 

88, 94, 95, 96, 99, 111, 113, 114, 116, 

142, 145, 157, 204, 207, 209, 218, 219, 

226, 261, 263, 265, 273, 274, 276, 277, 

280, 282, 284, 287, 288, 291, 293, 294, 

295, 303, 304, 305, 306, 307, 308, 311, 

313, 315, 335, 346, 347, 348, 350, 351, 

353, 354, 355 

MonitorMagic Web Service 12, 86 

MonitorMagic WebService 324, 325, 335 

MonotorMagic Service 146 

SNMP 111, 284 


Windows 2000 26, 60 

Windows 2000 Professional 37 

Windows 2000/NT/XP 346 

388

Index 

Windows NT 12 

Windows NT 4.0 22 

Windows NT 4.0. 265 

Running 1 

Running 8 

Running 10 

Running 12 

Running 15 

Running 21 

Running 22 

Running 23 

Running 26 

Running 29 

Running 37 

Running 41 

Running 45 

Running 49 

Running 56 

Running 59 

Running 60 

Running 61 

Running 65 

Running 70 

Running 74 

Running 78 

Running 80 

Running 86 

Running 88 

Running 94 

Running 95 

Running 96 

Running 99 

Running 111 

Running 113 

Running 114 

Running 116 

Running 142 

Running 145 

Running 146 

Running 157 

Running 204 

Running 207 

Running 209 

Running 218 

Running 219 

Running 226 

Running 256 

Running 261 

Running 263 

Running 263 

Running 265 

Running 268 

Running 273 

Running 274 

Running 276 

Running 277 

Running 280 

Running 280 

Running 282 

Running 284 

Running 287 

Running 288 

Running 291 

Running 293 

Running 294 

Running 295 

Running 303 

Running 304 

Running 304 

Running 305 

Running 306 

Running 307 

Running 308 

Running 311 

Running 313 

Running 315 

Running 315 

Running 324 

Running 325 

Running 335 

Running 346 

Running 347 

Running 348 

Running 350 

Running 351 

Running 353 

Running 354 

Running 355 

S 

S 1, 31, 45, 51, 58, 59, 60, 61, 65, 68, 70, 

74, 78, 86, 88, 92, 94, 96, 99, 101, 103, 

106, 107, 111, 116, 138, 140, 147, 155, 

167, 207, 215, 227, 257, 261, 273, 275, 

286, 318, 355 

Safe 343 

Sample queries 

event logs 206 

Sample queries 206 

Sans Serif 202 

Save 236, 265, 332 

Save Certificate 332 

Scale axis 253 

Scheduler 

according 169 

Scheduler 169 

Scheduler test 120 

Scheduling 

exceptions intervals 119 

overview 117 




389


Scrollbar 183 

Secure 343 

See 

Microsoft 303 

See 303 

See Also 286, 347, 348, 350, 351, 353 

See Footer 230 

See General 301 

SEEFISH 26 

Select 


Alarm 132 

Columns 222 


containing 64, 68, 77, 152 

Data 104 

database type 307 

Display menu 225 

exisitng 312 

File 227, 236 


Network Identification 26 

No 340 

Policies 35, 209 

Print 242 


Properties menu 84, 85 

SNMP Service 280 

Start 119 

System applet 26 

Traps 280 

Value 127 

Various 229 

Select 26 

Select 35 

Select 41 

Select 49 

Select 64 

Select 68 

Select 77 

Select 84 

Select 85 

Select 104 

Select 114 

Select 119 

Select 127 

Select 132 

Select 152 

Select 186 

Select 209 

Select 222 

Select 225 

Select 227 

Select 229 

Select 236 

Select 242 

Select 263 

Select 265 

Select 268 

Select 280 

Select 288 

Select 307 

Select 312 

Select 340 

Select cluster resources 92 

Select Domain 24 

SELECT logeventtype,computername,count 

206 

Select processes 77 

Select services 64 

SELECT 

sourcename,logeventtype,computername, 

count 206 

SELECT 

sourcename,logname,computername,des 

cription 206 

Send popup test message 139 

Send Queue Size 160 

Send SMTP test E-mail message 144 

Send SNMP 283 

Sending 

E-mail 99, 136, 271 

popup 17 

SMTP E-mail 12 

SNMP 15, 95, 277, 280 

use 144 

username/password 142 

Sending 12 

Sending 15 

Sending 17 

Sending 95 

Sending 99 

Sending 136 

Sending 139 

Sending 142 

Sending 144 

Sending 271 

Sending 277 

Sending 277 

Sending 280 

Serial 

Leave 1, 355 

Serial 1 

Serial 257 

Serial 355 

Server 

except 257 

Server 1, 64 

Server 257 

Server 261 

Server 308 

Server 355 

390

Index 

Server Manager 24, 263 

Server Manager application 

Start 24 

Server Manager application 24 

SERVER_A 80 

SERVER_A/Logs/SqlServer 80 

Servername 257 

ServerSMS GSM Device 

supports 11 

ServerSMS GSM Device 11 


Service 

Indexing 163 

use 17 

Service 17 

Service 41 

Service 62 

Service 96 

Service 127 

Service 163 

Service 200 

Service 263 

Service 265 

Service 274 

Service 348 

Service files 

Checking 270 

Service files 270 

Service list 150 

Service Logon Failures 164 

Service monitor 62 

Service monitor values 65 

Service registry configuration 

Checking 268 

Service registry configuration 268 

Service Rules 160, 161, 162, 163, 164 

Service setup 

Checking 263 

Service setup 263 

Service status 

Checking 263, 265 

Service status 263 

Service status 265 

Service TCP/IP 271 

Services window 263 

Set 

60 12 

Automatic 263 

Set 12 

Set 263 

Settings 24 

Setup 1, 37, 256, 257, 355, 360 

Setup MonitorMagic 21 

SetupMonitorMagic.exe 1, 21, 22, 355 

Show 

Computer 84 

DNS 26 

file 86 

NETBIOS 26 

Show 26 

Show 84 

Show 86 

Show 155 

Show 222 

Show 234 

Show button 

press 85 

Show button 85 

SHOW EVENT LOGS 350 

Shutdown 155 

SID 12 

Simple Book 99 

Simple Network Management Protocol 280 

Since MonitorMagic 35 

Single MonitorMagic 260 

Single versus multiple MonitorMagic 

services 260 

Singlequotes 318 

SMS 5, 10, 145, 287, 288, 291, 293, 294, 

295, 297, 301 

SMS installation 288 

SMS messaging 145, 287, 288, 295 

SMS modem installation 288 

SMS provider selection 291 

SMS script 297 

SMS-provider 294 

SMTP 

Specify 142 

SMTP 8 

SMTP 142 

SMTP 144 

SMTP 207 

SMTP 325 

SMTP 327 

SMTP 329 

SMTP E-mail 

sending 12 

SMTP E-mail 8, 11 





SMTP E-mail setup 142 

SmtpServer 271 

SNMP 

access 101 

According 106 

called 149, 285 

choose 280 

collect 96, 109, 277 

collecting 21 

create 278, 283 

391


defined 95 

dll 286 

examine 99, 101, 103 

forms 278 

generate 96, 282, 283 

initiate 286 

install 280, 284 

instruct 286 

manage 100 

Microsoft 279 


name 286 

number 23 

obtained 111 

opens 103 

order 149, 285 

part 149, 283, 286 

point 279 

querying 103 

receiving 95, 277 

runs 111, 284 

sending 15, 95, 277, 280 

specify 99 

specifying 103, 107 

support 106 

table 106 

test 101, 103 

use 98 

value 101, 111 

SNMP 5, 10, 12 

SNMP 15 

SNMP 21 

SNMP 23 

SNMP 95 

SNMP 95 

SNMP 96 

SNMP 98 

SNMP 99 

SNMP 99 

SNMP 100 

SNMP 101 

SNMP 103 

SNMP 104 

SNMP 106 

SNMP 106 

SNMP 107 

SNMP 109 

SNMP 110 

SNMP 111 

SNMP 111 

SNMP 130 

SNMP 142 

SNMP 149 

SNMP 149 

SNMP 173 

SNMP 215 

SNMP 277 

SNMP 277 

SNMP 278 

SNMP 279 

SNMP 280 

SNMP 280 

SNMP 282 

SNMP 283 

SNMP 284 

SNMP 285 

SNMP 286 

SNMP 286 

SNMP Community 111 

SNMP GET 

issue 101 

SNMP GET 101 

Snmp get monitor 98, 99, 100, 101, 103, 

104, 106, 107, 109, 110, 111 

SNMP GETNEXT 

issue 101 



SNMP Management application 

order 280 

SNMP Management application 280 

SNMP Management Program 286 

SNMP Manager 279 

SNMP Manager application 279, 280 

SNMP Message 149, 285 

SNMP Service 

Installing 280 

select 280 

starting 284 




SNMP trap message contents 149 

SNMP Trap message detailed contents 286 

Snmp trap monitor 95, 96 

Snmp trap monitor values 96 

SNMP Trap Service 

stopping 280 

SNMP Trap Service 280 


SNMP traps 

install 280 









SNMP Version 277, 286 

SNMPvX Trap 286 

392

Index 

SNNP 282 

Software 111, 359 

SOFTWARE/Tools4ever/MonitorMagic/Servi 

ce/SnmpTrap 284 

Sort 

monitors 223 

use 223 

Sort 223 

Sort 224 

Sort criteria 

Changing 224 

Sort criteria 224 

Source 204 

SourceId 204 

SourceName 204 

SPACE 318 

Specifc 21 

Specifed 271 

Specifes 254 

Specific 174 

Specific Trap Type 286 

Specify cluster resources 91 

Specify Command 113, 114 

Specify computer web access 338 

Specify event log monitors 66 

Specify file 80 

Specify file monitors 80 

Specify monitor 95, 100, 114 

Specify performance counter monitor 71 

Specify ping devices 58 

Specify processes 75 

Specify service monitors 62 

Specify Snmp 95, 100 

Specifying 

data source 312 

DNS 58 

Host 103, 106 

Logon ID 309 


MonitorMagic access rights 274 

MonitorMagic service license code 29 

policy options 39 

policy service selection 41 

rule criteria 127 

SMTP 142 

Snmp 99, 103, 107 

URL 346, 347, 348, 350, 351, 353, 354 

Use 58, 62, 66, 75 

Specifying 29 

Specifying 39 

Specifying 41 

Specifying 57 

Specifying 58 

Specifying 62 

Specifying 66 

Specifying 71 

Specifying 75 

Specifying 91 

Specifying 99 

Specifying 99 
















Specifying multiple object identifiers 104 

Spec's 228 

SQL 

execute 318 

results 318 

type 311 

SQL 7, 150 

SQL 311 

SQL 318 

SQL Server 

access 310 

connects 310 

create 308 

license 303 

log 161, 162 


name 308 

runs 308 

support 14 

SQL Server 8, 10 

SQL Server 14 












SQL Server 2000 303, 304 

SQL Server 6.5 303 

SQL Server 7.0 303 

SQL Server Cache Ratio 161, 162 

SQL Server Lock Memory 161, 162 

393


SQL Server ODBC 308 

SQL Server Percent Log Space Used 161, 

162 

SQL Server User Connections 161, 162 

SQL Server-specific 161, 162 

SQLServerAgent 161, 162 

SSL 17, 323, 324, 332 

SSPALERT.DLL 270 

SSPLCI.DLL 270 

Start 

Active Directory Users 26 

changing 120 

Control Panel 24, 26 

Internet 86 



257, 268, 274, 276, 291, 293, 294, 355 


Network applet 24 

Select 119 

Server Manager application 24 


Start 1 

Start 15 

Start 21 

Start 24 

Start 26 

Start 29 

Start 37 

Start 41 

Start 86 

Start 119 

Start 120 

Start 142 

Start 236 

Start 256 

Start 257 

Start 263 

Start 265 

Start 265 

Start 268 

Start 274 

Start 276 

Start 284 

Start 286 

Start 291 

Start 293 

Start 294 

Start 315 

Start 355 

Start button 

Press 103 

pressing 263 

Start button 103 

Start button 263 

Start Registry Editor 360 

Start, Programs 26 

Start, Settings 26 

Startup button 

press 263 

Startup button 263 

Stepping 111 

Stop button 

Press 103, 315 

Stop button 103 

Stop button 315 

Stop using 

database 315 

Stop using 315 

Stopped 

reports 15 


Stopped 15 

Stopped 280 

Stopped 280 

Storage 49 

Storaget 55 

Store SNMP 98 

Straightforward 21, 288, 302, 325, 344 

STX 297 

Subidivsion 

number 252 

Subidivsion 252 

Subject 18 

Subkey 

following 360 

Subkey 271 

Subkey 360 

Subkeys 271 

Subreport 

creating 184 

Subreport 184 

Subreport 185 

Subreport item 

create 184 

Subreport item 184 

Subreports 178, 184 

Succesfull 

get 282, 283 

Succesfull 282 

Succesfull 283 

SUMMER 

connecting 335 

SUMMER 88, 96 

SUMMER 335 

Support SNMP 5, 17 

Support@tools4ever.com 99 

Supported databases 303 

Supports 



SNMP 106 

394

Index 

SQL Server 14 

Supports 11 

Supports 14 

Supports 17 

Supports 106 

Supports Windows NT/2000 5 

Suppose 


Suppose 50 

Supress 318 

System applet 

select 26 

System applet 26 

System Data Sources 315 

System Info 347 

System Properties window 26 

System.1060 17 

SystemRoot 80 

SystemRoot%/System 80 

SystemRoot%/System32 80, 360 

SysUpTime 286 

T 

T4eDirSize 317 

T4eDirSize D 317 

T4eDirSize plugin 317 

T4ePortPing 317 

T4ePortPing 192.168.195.201 81 317 


TCP 317 


UDP 317 


TCP 317 

T4ePortPing www.tools4ever.com 80 317 

T4eSql 318 

T4eSql plugin 318 

T4eWebPing 116, 316 

T4eWebPing url 316 

TabIe 204 

Table Object Identifier 

table 106 

Table Object Identifier 106 

Tables 

40 183 

Read 106 

SNMP 106 

Table Object Identifier 106 

Tables 106 

Tables 106 

Tables 183 

Taks 273 

TAP 

uses 297 

TAP 294 

TAP 297 

TAP 301 

TapScript.sci 297 

Target Computer 155 

TARGET_COMPUTER 80 

TCP/IP 

address 59 

containing 56 

find 10 

name 59 

responding 10 

wait 58 

TCP/IP 5 

TCP/IP 10 

TCP/IP 56 

TCP/IP 58 

TCP/IP 59 

TCP/IP 95 

TCP/IP 96 

TCP/IP 99 

TCP/IP 101 

TCP/IP 106 

TCP/IP 142 

TCP/IP 317 

TCP/IP 325 

TCP/IP 327 

TCP/IP 329 

TCP/IP Event Errors 164 

TCP|UDP 317 

TcpIpPort 271 

Te 96 

Tell 


Tell 330 

TempData/Tools4ever.txt 316 

Terminal Server Session 162 

Terminal Server Session Errors 162 

Terminal Server Session Frames 162 

Terminal Server Session Output Errors 162 

Terminal Server Session Private Bytes 162 

Terminal Server Session Timeouts 162 

Terminal Server Session Total Bytes 162 

Terminal Server Session Transport Errors 

162 

Terminal Services 162 

Terminal Services-specific 162 

Terminate process 152 

Test 

MonitorMagic SNMP traps software 283 

SNMP 101, 103 

use 157 

Test 101 

Test 103 

Test 157 

Test 283 

Test button 

press 117, 120 

Test button 117 

395


Test button 120 

Test computer shutdown 157 

Test SNMP 

press 282 

Test SNMP 282 

Test SNMP 283 

Text 85, 294 

The file 80 

The Print 227 

The SNMP Service 280 

Thread Count 75 

Tile 213 

TIME 17, 230 

Time range 236, 247 

Time Running 75 

TIME-DATE 191 

Timestamp 286 

Tnew 109 

Told 109 

Tools4ever 

link 12 

Tools4ever 12 

Tools4ever 265 





Tools4ever bv 316, 317, 318 

Tools4ever Directory Size Utility 317 

Tools4ever Port Ping Utility 317 

Tools4ever reseller 32, 343 

Tools4ever Sql Utility Version 3.48 318 

Tools4ever Web Ping Utility 316 

Total 10 

Traps 

Select 280 

Traps 280 

Trending 5, 98, 302 

Trent's 336 

Trigger 125 

Triggered.1060 17 

Troubleshooting 

MonitorMagic SNMP traps 284 



TRUE 121, 127 

TULIP 31, 45, 59, 121 

Tulip,Rose 257 

Type 


SQL 311 

Type 131 

Type 273 

Type 311 

U 

UCP 294 

UDP 278 

Un-acknowledged 136 

Understanding 


Understanding 50 

Uninstall 

need 22 

Uninstall 22 

Uninstall 360 

Universal Coordinated Time 204 

Unix, Linux 11 

Unknown username 164 

Unlodctr 360 

Unlodctr inetinfo 360 

Unlodctr msftpsvc 360 

Unlodctr w3svc 360 

Updating 

Global 218 

results 226 

Updating 218 

Updating 226 

Upgrading 



Upgrading 15 

Upgrading 22 

Upgrading 256 

Upgrading 257 

URL 

entering 325 

specifying 346, 347, 348, 350, 351, 353, 

354 

URL 325 

URL 346 

URL 347 

URL 348 

URL 350 

URL 351 

URL 353 

URL 354 

USA 288, 294 

Use 

Add 80, 100, 104, 107, 117, 131, 150, 222, 

224, 276, 335 

All 228 

AM 119 

Browse button 139 


Event 68, 69 

FAT 360 

HH 119 

HTTP 343 

Internet 99 


Microsoft Windows Installer 22 

MonitorMagic WebInterface 335 

396

Index 


MonitorMagic's 41, 273, 323, 324, 327, 

329, 343 

MS Access 303 

multivalue 196 

NETBIOS 257 


Send 144 

Service 17 

Snmp 98 

Sorting 223 

Specify 58, 62, 66, 75 

TAP 297 

Test 157 

When 135 

Use 17 

Use 22 

Use 41 

Use 58 

Use 62 

Use 66 

Use 68 

Use 69 

Use 72 

Use 75 

Use 80 

Use 98 

Use 99 

Use 100 

Use 104 

Use 107 

Use 117 

Use 119 

Use 131 

Use 135 

Use 139 

Use 144 

Use 150 

Use 157 

Use 196 

Use 222 

Use 223 

Use 224 

Use 228 

Use 257 

Use 273 

Use 276 

Use 297 

Use 303 

Use 303 

Use 311 

Use 312 

Use 315 

Use 323 

Use 324 

Use 327 

Use 329 

Use 332 

Use 335 

Use 343 

Use 343 

Use 360 

Use SQL Server 309 

Use Windows 2000/NT 309 

User 92, 257 

User Logon Failures 164 

User Manager 

Domains application 263 

User Manager 263 

User/Group 338 

UserData 94 

UserDataShareA 94 

UserId 204 

UserInfo 271 

Username 

enter 327, 329 

Username 142, 204 

Username 327 

Username 329 

Username/password 

HTTP 343 

sending 142 

Username/password 142 

Username/password 343 

Using MonitorMagic's 324 

V 

V1 109, 286 

V1/V2 109 

V1+V2 109 

V1new+V2new 109 

V1new-V2new 109 

V1old+V2old 109 

V1old-V2old 109 

V1-V2 109 

V2 109 

Value 

0 correponds 249 

120 155 

300 114 

3600 271 

999999 12 

evaluate 127 

Oid1 109 

oid's 111 

selected 127 

SNMP 101, 111 

Value 12 

Value 101 

Value 109 

Value 111 

Value 114 

Value 127 

397


Value 155 

Value 249 

Value 271 

Valuename 284 

ValueNew 109 

ValueNew-ValueOld 109 

ValueOld 109 

Variables 178 

Various 

select 229 

Various 229 

Various 239 

Various 254 

Various options 229 

Verify button 

pressing 29 

Verify button 29 

VeriSign 330, 344 

Vertical 245 

Vertical scale 252, 253 

VERY UNWISE 324 

View 

database status 304 

View 15, 35, 199, 200, 201, 202, 203, 209, 

215, 218, 236, 237, 238, 239, 247, 248, 

250, 265 

View 304 

View button 

Press 84, 85 

View button 84 

View button 85 

View file content 85 

View monitor 84 

View, Network 209 

Visisble 254 

Vnew-Vold 109 

Vodaphone 294 

W 

W 31 

W+D 31 

W3SVC 360 

Wait 

TCP/IP 58 

Wait 58 

Want 

E-mail 207 

MonitorMagic 114, 147, 257, 327, 329 

Want 114 

Want 147 

Want 207 

Want 257 

Want 327 

Want 329 

Warning 59, 61, 65, 70, 74, 111, 116 

Web 336, 340 

Web config 215 

Web Interface 14 

Web interface navigation 346 

Web interface support 111 

WebService 

activating 325 

Choose 325 

configuring 17 

connect 325 

installed 325 

WebService 17 






WebService Access Rights 336, 340 

Welcome 


Welcome 1 

When 

Use 135 

WHERE mmlog_eventrecord.logsourceid 

206 

Why 359, 360 

Widht 252 

Window margins 201 

Window.1060 17 

Windows 


part 245 

Windows 15, 114, 138, 140, 184 

Windows 209 

Windows 245 

Windows 2000 

running 26, 60 

Windows 2000 1, 5, 21 

Windows 2000 26 













Windows 2000 Advanced 1, 355 

Windows 2000 Advanced Server 23 

Windows 2000 Datacenter 23 

Windows 2000 DNS 

part 26 

Windows 2000 DNS 26 

Windows 2000 Professional 

398

Index 

running 37 

Windows 2000 Professional 1, 23 





Windows 2000 Server 1, 23, 355 

Windows 2000 Service Pack 360 

Windows 2000 Setup 360 

Windows 2000 Terminal Services 162 

Windows 2000 Version 5.0 111 

Windows 2000/NT 

part 279 

Windows 2000/NT 15, 273, 278 

Windows 2000/NT 279 

Windows 2000/NT 280 

Windows 2000/NT Authentication 10 

Windows 2000/NT username 

Ask 327, 329 

Windows 2000/NT username 327 

Windows 2000/NT username 329 

Windows 2000/NT/XP 

running 346 

Windows 2000/NT/XP 346 

Windows 2000/XP/NT 80 

Windows 2000/XP/NT system32 80 

Windows 98, Windows ME 21 

Windows Explorer 212 

Windows Installer 22 

Windows Network Services 

monitoring 164 

Windows Network Services 164 

Windows NT 

running 12 

Windows NT 1 

Windows NT 12 

Windows NT 257 







running 22 














Windows NT 4.0 Enterprise Edition 23 

Windows NT 4.0 Server 23 

Windows NT 4.0 Terminal Server Edition 23 

Windows NT 4.0 Workstation 23 

Windows NT 4.0. 

running 265 



Windows NT username/password 343 

Windows NT/2000 

number 274 

Windows NT/2000 56, 268 

Windows NT/2000 274 

Windows NT/2000/XP 359 

Windows System32 114 

Windows XP 17, 21, 288, 303, 308, 315 

Windows XP Server 23 

Windows XP/2000 277 

Windows XP/2000/NT 

part 277 

Windows XP/2000/NT 277 

Windows2000/NT 273 

WINNT/system32/aspperf.dll 360 

WINNT/system32/infoctrs.dll 360 

WINNT/system32/w3ctrs.dll 360 

WINS Event Errors 164 

WINTER 94 

WINTER_A 94 

Word 297 

Work Queue Length 160 

Workaround 15 

Workstation 11, 12 

World Wide Web Publishing Service 159, 

163 

Write 316 

Www.tools4ever.com 1, 58, 59, 101, 111, 

116, 316, 317, 318, 355 

X 

X N 23 

X86 Family 111 

Xxx 

number 155 

Xxx 1 

Xxx 155 

Xxx 355 

Xxx.xxx.xxx.xxx 58, 271 

Y 

Y 239 

Z 

Zoom operation 241 

Zoom Out 241 

399

MonitorMagic - Tools4Ever.com

Create successful ePaper yourself

Delete template?

Save as template?