Local, Remote and Web Access to the Program

The Enterprise edition of the program has a client-server architecture. The server part works as a Windows service and performs hosts monitoring, sends notifications and generates reports. The client part is a Windows application with a user interface that allows a user to manage monitored hosts, to see the collected statistics, etc. While installing the program, you can select to install the server, the client, or both. Thus, you can install the client and the server on the same PC or different ones.

It is recommended to install the server on a Windows server or another PC that is always turned on, so the server can continuously monitor the specified hosts. The client can be installed on the same computer or on any remote PC since the program allows clients to connect remotely to the server over a LAN/WAN/VPN connection. You can install multiple clients that can connect to the same server and work concurrently. To be able to connect to the server remotely, you need to open ports 48008 and 48009 in the firewall on the computer where the server is installed.

When running the client, you need to specify if you would like to connect to the server installed locally or remotely Pic 1. If you wish to connect to a remote server, you should enter its host name or IP address. The server requires user authentication, so when using the default settings, you need to specify a Windows account that is a member of the Administrators group on the PC where the server is installed. If your account satisfies this condition, you can enable the Use Windows session Credentials option and skip entering the username and password.

The server connection dialog

Pic 1. The server connection dialog

When using the default settings of the program, you should use a Windows account that is a member of the Administrators group to connect to the server. If required, you can change the access permissions in the Access Control view of the program Pic 2. There you can manage roles and their privileges and assign those roles to Windows users and groups. This allows you to organize flexible management of permissions. For example, using roles, you can provide an administrative access with all permissions to some users, a read-only access to other users, and an access to the reporting functionality only for certain users. Learn more about using roles and permissions in the Access Control chapter.

Configuring roles and permissions

Pic 2. Configuring roles and permissions

The program uses secure communication between the client and the server, so all the data traffic is encrypted. By default, the program uses a self-signed SSL certificate, and you get a warning that the used certificate isn't trusted when you connect to the server. If you have a SSL certificate, it's recommended to specify it in the program's Preferences to validate the identity of the server when you connect to it remotely.

The Enterprise edition of the program also offers web reports. You can use web reports to check the status and statistics of the monitored hosts from any computer. The program uses Microsoft IIS to deploy web reports. If you choose to deploy web reports, the program installation automatically configures Microsoft IIS, so you can access web reports in a browser.

Web reports

Pic 3. Web reports

In web reports, you can see the list of monitored servers and their statistics, i.e. the same information you can see in the GUI client. If required, you can filter the displayed hosts. For a host, you can see the detailed monitoring statistics, charts and the list of outages for the selected time period. Note that web reports don't allow you to manage monitored hosts or start/stop monitoring. These operations should be performed in the GUI client.