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 run monitors with WINDOWS and FILE sensors "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 sensors working over TCP protocol executed simultaneously, there may be issues with reliability of these sensors 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 an IP address.
2. Monitor: enables control over various aspects of device operation and execution of actions. It consists of:
2.1 Sensor: an integral part of the monitor; it directly checks the devices. There are 3 groups of sensors (Internet sensors, Windows sensors, File sensors).
2.2 Action(s): enables alerting and taking certain measures according to user-set parameters.
See the program operation scheme below:
A: A monitor belongs to a device, which in turn belongs to a group. That is why at first it is necessary to create a group and a device.
More details about operations with monitors here...
A: During its work the monitor is able to assume three colors: black, red and green. Black color means that an error has occurred during the sensor operation (e.g. failure to receive authorization on the remote Windows PC). The other two colors display the logical result of a check. For file sensors you can set the rules of color change yourself.
A: TNM maintains four logs:
In All monitors log the records on all monitors are displayed. A record is logged only in case of a monitor changing its color.
Current monitor's log only displays the records belonging to the monitor selected in the list.
Records on all executed actions are logged in Executed actions. If an action has been executed with an error, an appropriate record will be highlighted red, and error data will be shown.
Statistical information about the monitor selected in the list is shown in Current monitor's activity.
More details about journalization here...
A: An Activity diagram shows all color states the selected monitor has been in during its run. Each check is designated by a square, color of which is defined by the result of the check. A multitude of squares of the same color form a block.
A: In the main menu choose Help (?) -> Check for updates. In case there is a new update press Download. The update will be installed right after TNM closure.
A: If a device obtained a static IP it will be always used in monitoring. Otherwise, TNM will try to resolve the host name each time and receive the current IP address.
A: Yes. Select the log. Right-click on it and select one of the export formats.