A: Either server or workstation can run Total Network Monitor. It is just a matter of usage convenience, because it's not a client-server application and you need to have access to the graphical console of the computer you install it on, either directly or using some remote desktop utility. Besides, if you run it under domain admin account, you will be able to perform WINDOWS and FILE probes "as current user", otherwise you would need to specify appropriate credentials explicitly (for example those of domain administrator).
However take note that if you install the program on Windows XP (starting with SP2), Windows Vista or Windows 7, and if there are many probes working over TCP protocol executed simultaneously, there may be issues with reliability of these probes results. This is due to a restriction on the maximum number of TCP half-open connections (connection attempts, SYN_SENT socket state) existing in the mentioned Windows versions, which doesn't allow more than 10 outbound connections to be in this state at a time. After reaching this limit, all other connections in the system (including those executed by this program) are queued and may reach their timeout, thus producing inconsistent results. This issue is also known as "Event 4226 issue", because reaching the limitation produces a record in the System Event Log with EventID 4226. Windows XP SP0/SP1, Windows 2000 Professional and all Windows Server systems don't have such limitation. So in general case we suggest installing the program on a server operating system.
A: The program uses four main notions (in logical order):
1. Device: any device in the network with IP address.
2. Monitor: allows controlling various aspects of certain device performance and execute actions. It consists of:
2.1 Probe: an integral part of monitor, directly checks the devices. There are 3 probe groups (Internet probes, Windows probes, File probes).
2.2 Action(s): allow alerting and taking some measures according to user-set parameters.
See the program operation scheme below:
A: Monitor belongs to a device and the device in its turn to a group. That is why at first it is necessary to create group and device.
More details about operations with monitors here...
A: During its work the monitor is able to get three colors: black, red and green. Black color means that there was an error during probe (e.g. failed to get authorized on the remote Windows PC). The rest two colors display logic result of the probe. For file probes you can set rules of color change.
A: TNM maintains four logs:
In All monitors log records on all monitors are displayed. Record is added into log only in case if monitor has changed its color.
This monitor log displays only the records belonging to the monitor selected in the list.
Into Executed actions log the records on all executed actions are added. If the action was executed with an error the appropriate record will be lighted with red color and error data will be shown.
In This monitor activity statistic information about the monitor selected in the list is shown.
More details about journalization here...
A: Activity diagram shows all state colors the selected monitor has been in during its work. After each check there comes a square which color is defined by the result of the check. A number of squares with the same color makes a block.
A: In main menu choose Help -> Check for updates. In case if there is new update press Download. The update will be installed right after TNM close.
A: If a device obtained static IP it will be always used in monitoring. Otherwise TNM will try to resolve host name each time and get current IP address.
A: Yes. Choose necessary log. Right-click it and choose one of the export formats.
A: The eye blinks when the new record is added to the log.