<%NUMBERING1%>.<%NUMBERING2%>.<%NUMBERING3%> PRTG Manual: PRTG Administrator on Core Server System

With the PRTG Administrator program you can define various system-oriented settings that affect your PRTG installation, as well as restart services and view log information. You can change many of these settings also via the system administration in the PRTG web interface.

Note: To get familiar with the different components of PRTG, we recommend you to read the Architecture section.

Note: All settings you define here are only valid for the local installation running on the computer you open the program on. In order to change settings for another installation, for example, another cluster node installation, please log in to this computer and open the program there.

Note: This section describes the available settings in the PRTG Administrator when you open the tool on the PRTG core server system (core resp. web server and local probe related). If you open this program on a remote probe machine, only probe related settings are available.

From the PRTG Network Monitor group in Windows start menu, please select PRTG Administrator to open the application. You can choose from these options in different tabs:

When you close the program with the Ok button after changing settings, you are asked to restart the core server Windows service and/or probe service in order to save the settings. Please confirm by clicking the OK button. Otherwise the changes are ignored.

PRTG Administrator: Restart Services

PRTG Administrator: Restart Services

Web Server

Edit IPs, ports, access methods, and language for the Ajax and Mobile Web GUI web interfaces.

Note: You can change all settings which are on the Web Server tab also via the PRTG web interface in the User Interface settings.

PRTG Administrator: Web Server

PRTG Administrator: Web Server

Web Server

Select TCP Port for PRTG's Web Server

PRTG is running a web server in order to provide the web and Windows interface. Please specify on which port this web server will run. Choose between:

  • Secure HTTPS server (recommended, mandatory for internet access): This is the recommended setting and needed to access the PRTG server via the internet. Use a secure HTTPS connection that is encrypted via SSL on port 443.
    Note: Although the connection is secure, you will see an SSL Certificate Warning in your browser when logging in to the PRTG web interface, because the default certificate is unknown to your browser. You can install another SSL certificate for PRTG later. Please see Using Your Own SSL Certificate.
    Note: If port 80 is free, PRTG will reserve it as well. When users try to connect on port 80 via HTTP, they will then be redirected to port 443 via HTTPS. You can change this behavior using a registry setting.
  • Insecure HTTP server (standard port 80, not recommended): Use a standard web server without SSL encryption on port 80. This setting is not recommended for WAN connections.
    Note: If used on the internet, attackers could potentially spy on credentials you enter into PRTG. We strongly recommend using this option in a LAN only.
  • Expert configuration: This setting allows you to specify a custom web server port and the security of the connection. This option is intended for systems with an existing web server on the standard port. Define port and encryption below.

Expert Configuration: SSL Encryption

This setting is only visible if the expert configuration is selected above. Specify if you want to use an SSL encryption. Choose between:

  • Use SSL encryption (HTTPS): Use a secure HTTPS connection that is encrypted via SSL on a custom port as defined above.
    Note: Although the connection is secure, you will see an SSL Certificate Warning in your browser when logging in to the PRTG web interface, because the default certificate is unknown to your browser. You can install another SSL certificate for PRTG later. Please see Using Your Own SSL Certificate.
  • Don't use encryption (not recommended): This setting is not recommended for WAN connections. Use a standard web server without SSL encryption on a custom port as defined above.
    Note: If used on the internet, attackers could potentially spy on credentials you enter into PRTG. We strongly recommend using this option in a LAN only.

Expert Configuration: Web Server Port

This setting is only visible if the expert configuration is selected above. Enter the desired TCP port number you want the PRTG web server to run on. Please enter an integer value.

Note: If you use a secure connection and port 80 is free, PRTG will reserve it as well. When users try to connect on port 80 via HTTP, they will then be redirected to the custom port via HTTPS. You can change this behavior using a registry setting.

Select IP Address for PRTG's Web Server

PRTG is running a web server in order to provide access via the web and Windows interface. Please specify which IP address this web server will run on. Note: Later, you can log into PRTG by simply pointing your browser to the specified IP address.

Choose between:

  • Localhost, 127.0.0.1 (PRTG will not be accessible from other computers): Use 127.0.0.1 only. PRTG's web and Windows interface will only be accessible from the computer PRTG is installed on.
    Note: Either the selected port or at least one port in the range from 8080 to 8089 has to be available on 127.0.0.1.
     

Note: If you run PRTG on localhost, please do not use the DNS name http://localhost to log in to the web server, as this may considerably slow down PRTG's web interface. Please use your local IP address or http://127.0.0.1 instead.

  • All IPs available on this computer: Use all IP addresses available on this computer and enable access to the web server for all of these addresses. Note: The TCP port selected below must be free on every available IP address.
  • Specify IPs: Select specific IP addresses on which the PRTG Web server will run on. A list specific to your system is shown. Add a check mark in front of every IP address you want the PRTG web server to be available at. You can also select and deselect all addresses by clicking on the check box in the table header.
    Note: Either the selected port or at least one port in the range from 8080 to 8089 has to be available on the specified IP address.

Note: Regardless of the selected setting above, one port in the range from 8080 to 8180 has to be available on the specified IP address so PRTG can create reports. The report engine will try to connect to the core server on one of these ports.

Note: If PRTG does not find a network card on startup it will switch the IP setting to Localhost. This setting will remain, even if a network card is available later on. If you disabled or removed the network card on the machine running the PRTG core server, please re-check this setting.

Select System Language

Choose the system language from the drop down list. Default is English. Depending on your installation, you may be able to choose other languages here. This setting will influence the language of the Ajax and the Mobile Web GUI web interfaces, as well as of the PRTG Administrator Tool.

Core Server

Define settings for the core server.

PRTG Administrator: Core Server

PRTG Administrator: Core Server

Core Server

Probe Connection Management

Define how PRTG will handle incoming connections from probes. Choose between the following options:

  • Accept connections from the Local Probe only (default setting, does not allow remote probes): This is the default setting. Only local probe connections will be accepted by the PRTG core server. You cannot use remote probes with this setting enabled.
  • Accept connections from remote probes on all IPs: Incoming connections from remote probes will always be accepted, no matter on which IP address of the core server they come in.
  • Accept connections from remote probes on selected IPs only: Incoming connections from remote probes will only be accepted on the selected IP address(es) of the core server. In the list, select the IP addresses by adding a check mark in front of the desired IPs.

Probe Connections Port

Define on which TCP port number PRTG listens to for incoming probe connections. Enter a port number. We recommend using the default value.

Local Storage of Data Files and Monitoring Database

Define the data folder to which PRTG will store configuration and monitoring data. Click on the ... button to choose another folder on your system.

Note: Before changing the path, make sure you stop both services and copy all data to the new location.

Click on the Revert to default folder to reset to default.

Cluster

On the Cluster tab you can manually change how the current core installation will behave in a cluster. Before changing settings here, please read Failover Cluster Configuration section.

PRTG Administrator: Cluster

PRTG Administrator: Cluster

Cluster

Cluster Settings

Depending on the current cluster settings you will see different information here.

  • Cluster Mode: Shows which cluster mode the current installation is running. This setting is shown for your information only and cannot be changed here. Possible values are Standalone (no cluster mode), Cluster Mode: Master Node, or Cluster Mode: Failover Node.
  • Cluster Port: This field is only shown when PRTG is running in a cluster mode. This setting is shown for your information only and cannot be changed here.
  • Cluster Access Key: This field is only shown when PRTG is running in a cluster mode. This setting is shown for your information only and cannot be changed here.
  • Own Node ID: This field is only shown when PRTG is running in a cluster mode. This setting is shown for your information only and cannot be changed here.

Cluster Mode Actions

Depending on the current cluster settings, you see different active buttons here. For details, see below.

Follow these instructions to create or join a cluster, or to change its settings:

Create a PRTG Cluster...

  • Start creating a cluster by clicking this button. The current PRTG core server will then be the Master Node of your cluster.
  • After you click this button, please confirm converting this installation into a master node by clicking on the Yes button.
Converting an Installation into a Cluster Master Node

Converting an Installation into a Cluster Master Node

  • A new dialog box will appear.
     
PRTG Administrator: Creating a Cluster Master

PRTG Administrator: Creating a Cluster Master

  • Enter a Cluster Port. This is the port on which the internal communication between the different cluster nodes is sent. Make sure connections between cluster nodes are possible on the selected port.
  • Enter or paste a Cluster Access Key. This is a unique access key. All nodes in a cluster have to be configured with the same cluster access key in order to join the cluster. Connection attempts with the wrong access key will be rejected.
  • We recommend using the default value.
  • Save the Cluster Access Key so you have it at hand when configuring your Failover Node(s).
  • After confirming your settings you will be asked to restart Windows services. Please do so in order for your changes to take effect.
     

Join a PRTG Cluster...

  • Add this installation to an existing cluster which already has a Master Node, by clicking this button. The current PRTG core server will then be a Failover Node in the cluster.
  • Note: This button is also available if you are currently running your PRTG installation in Cluster Mode: Master Node. This option will then change your master node to a failover node!
  • After you click this button, confirm converting this installation into a failover node by clicking on the Yes button.
Converting an Installation into a Cluster Failover Node

Converting an Installation into a Cluster Failover Node

  • A dialog box will appear.
PRTG Server Administrator

PRTG Server Administrator

  • Enter the cluster's Master IP address/DNS name. It must be reachable from the machine running the failover node.
  • Enter the other settings as defined in your Master Node's settings. Please make sure you use the same settings on all nodes in your cluster.
  • Enter a Cluster Port. This is the port on which the internal communication between the different cluster nodes is sent. Make sure connections between cluster nodes are possible on the selected port.
  • Enter or paste a Cluster Access Key. This is a unique access key. All nodes in a cluster have to be configured with the same cluster access key in order to join the cluster. Connection attempts with the wrong access key will be rejected.
  • After confirming your settings you will be asked to restart Windows services. Please do so in order for your changes to take effect.
     

Change PRTG Cluster Settings...

PRTG Server Administrator

PRTG Server Administrator

  • If you are running your PRTG installation in cluster mode, you can change the settings here. A new window will appear.
  • Enter a Cluster Port. This is the port on which the internal communication between the different cluster nodes is sent. Make sure connections between cluster nodes are possible on the selected port.
  • Enter or paste a Cluster Access Key. This is a unique access key. All nodes in a cluster have to be configured with the same cluster access key in order to join the cluster. Connection attempts with the wrong access key will be rejected.
  • Please make sure you use the same settings on all nodes in your cluster.
  • After confirming your settings you will be asked to restart Windows services. Please do so in order for your changes to take effect.
     

Revert to Standalone...

  • If you are currently running your PRTG installation in cluster mode, you can change it to Standalone mode. If you do so, this node will no longer be part of a cluster.
  • After confirming your settings you will be asked to restart Windows services. Please do so in order for your changes to take effect.
     

Master Heartbeat

This section is only visible if you are running your PRTG installation in cluster mode. The current master can execute an external executable file on a regular basis. We call this a "heartbeat".

You can use this, for example, to report the IP address of the current master node to a dynamic DNS provider, so a DNS name is always redirected to the current PRTG master node in case the original master node fails and a failover node (running at a different IP address) takes over the master role.

Choose between:

  • No heartbeat: Do not execute a file on a regular basis.
  • Run the following external executable file every 5 minutes: Click on the ... button to choose a file you want to execute. This can be, for example, a command line tool, or a batch file. It will be executed on the current master node only, with a fixed interval of five minutes. The interval cannot be changed.

Note: Please make sure the selected file is available under the same (local) path on all failover nodes. In case one of your failover nodes becomes current master, the heartbeat can only be executed reliably if the respective executable file exists on all of your failover nodes.

Administrator

Change PRTG System Administrator specific settings.

Note: You can change these settings also in the account settings of the PRTG System Administrator user in the PRTG web interface.

PRTG Administrator: Administrator

PRTG Administrator: Administrator

Login Credentials for the Administrator Account

Email Address

Enter a valid administrator's email address. By default, PRTG will send notifications and important messages to this address.

Login Name

Enter a name for the PRTG System Administrator login; this is your default login. You use it when you log into the PRTG web interface or Windows Enterprise Console.

Note: The default login name is prtgadmin

Password

Enter a password for the PRTG System Administrator login; this is your default login. You use it when you log into the PRTG Web- or  Windows Enterprise Console.

Note: The default password is prtgadmin

Confirm Password

If you change your password, re-enter the password for the PRTG System Administrator login to confirm it.

License

To use a PRTG license with this installation of PRTG, please enter the license information you have received from Paessler via email. To avoid typing errors, please copy and paste both the License Name and the License Key from the email. Both must be transferred exactly as shown in the email.

PRTG Administrator: License

PRTG Administrator: License

To make sure your key has been entered correctly please click on the Check Key button. A popup box will either show success or denial of your license information. License information is also checked if you change tabs.

In the Licensed Edition field you will see an accepted license key.

Note: You have to use the right edition for your license key. For example, the installer for trial and Freeware edition does not accept any commercial keys. For more information, please see Enter a License Key section.
 

Probe Settings for Core Connection

Define general settings regarding the probe and probe connections.

PRTG Administrator: Probe Settings for Core Connection

PRTG Administrator: Probe Settings for Core Connection

Probe Settings

Name of Probe

Enter a meaningful name to identify the probe. PRTG shows this name, for example, in the device tree, and in all alarms by default. Please enter a string.

Reconnect Time

Define the time that PRTG will wait until the probe tries to reconnect to the core server if the connection fails. Please enter an integer value.

Connection to PRTG Core Server

These settings will affect how the probe will connect to the core server. A probe is either a local probe or a remote probe. PRTG will automatically detect the type of probe and show the correct setting options.

Server (IPv4 address or DNS name)

If this probe is configured as the Local Probe of the PRTG core installation, it will connect to the core via 127.0.0.1 which you cannot change.

If this probe is configured as a Remote Probe, enter the IP address or DNS name of the core server.

Port

Define the Port number under which probe and core server will communicate. Please enter an integer value. We recommend using the default value.

Probe GID

The Probe GID is a unique identifier for the probe. We recommend you to not change it.

Exception: Only if you substitute an existing probe from a different computer, you have to copy the GID from the old probe to the new probe. To do so, click on the Edit GID... button and confirm the warning with Yes. You can then change the value.

Note: You can deny GIDs under System Administration—Core & Probes in the PRTG web interface.

Probe Access Key

You do not need an access key for Local Probe connections.

On a Remote Probe, the Probe Access Key must match one of the access keys configured in your PRTG core server installation. If it does not match, the remote probe will not be able to connect to the core server. Please see System Administration—Core & Probes section for more information.

Note: Also check allowed and denied IPs there to ensure that the core server accepts the IP address of the remote probe.

Confirm Access Key

If you enter an access key for a remote probe, enter it in this field again to assure correctness.

Path for Probe Data Storage

Path

Define the data folder to which PRTG will store configuration and monitoring data. Click on the ... button to choose another folder on your system.

Note: Before changing the path, make sure you stop both services and copy all data to the new location.

Probe Settings for Monitoring

Administrative Probe Settings / Probe Settings for Monitoring

Define the IP address used for outgoing monitoring requests.

  • If there is more than one IP on the current system available, you can specify the IP address that will be used for outgoing monitoring requests of certain sensor types.
  • The setting is valid for all monitoring requests sent from this PRTG probe.
  • This setting will be used for sensors using the following connection types: HTTP, DNS, FTP, IMAP, POP3, Port, Remote Desktop, SMTP, and SNMP. Note: This feature does not support all sensor types for technical reasons.
  • This is useful for devices that expect a certain IP address when queried.
  • Default setting is auto. PRTG will select an IP address automatically.

Note: If you change this setting, some sensors might stop working. For example, sensors might show a Down status if the selected IP address is blocked on the way to or directly on the monitored device.

Outgoing IPv4

Define the IP address for outgoing requests using the IPv4 protocol. The list shows all IP addresses available on the current system. Choose a specific IP address or select auto.

Outgoing IPv6

Define the IP address for outgoing requests using the IPv6 protocol. The list shows all IP addresses available on the current system. Choose a specific IP address or select auto. For details about the basic concept of IPv6 in PRTG, please see IPv6 section.

Service Start/Stop

You can stop and start PRTG Windows service manually. Click the Stop Core Server resp. Stop Probe Service button to stop a service, and Start Core Server resp. Start Probe Service to start it again. Both actions usually take from a few seconds up to several minutes to complete. You can also restart the core server and probes via the PRTG web interface under Administrative Tools.

Note: If you want to schedule an automatic restart of Windows services for both core server and probe service, define a schedule on the Settings tab of a probe, section Administrative Probe Settings, in the PRTG web interface.

Logs and Infos

Log Files

Open Log Folder...

Open the PRTG Network Monitor data directory on your hard disk drive to access all log files which PRTG creates.

Send Logs to Paessler...

Open an assistant to send log files to the Paessler support team. Please see below for details.

Note: You can send log files more easily with the support bundle via Contact Support in the PRTG web interface.

Open Support Ticket...

This will open the support form on Paessler's webpage in a browser window. Note: If you need help, we recommend you to use the Contact Support option in the PRTG web interface instead.

The About section shows information about the version of installed PRTG programs and copyright.

Send Logs to Paessler

Note: You can send log files more easily with the support bundle via Contact Support in the PRTG web interface.

Send Logs to Paessler

Send Logs to Paessler

If you open a support ticket, Paessler support might ask you to send log files for further analysis. With the Send Logs to Paessler... button, PRTG will automatically collect, compress, and send your log files.

Send Logs to Paessler

Name

Enter your name.

Email

Enter your valid email address. You can provide any of your addresses; however, recommended and default is the email address of your PRTG account.

Ticket No.

This field is optional. If you have already opened a ticket at Paessler support, please provide the ticket number you received. Your files will then be associated with your ticket automatically.

Please enter the ticket number starting with PAE followed by four or more digits, for example, PAE12345. If you do not have a ticket number, leave this field empty.

Configuration

Define if your configuration file will be included in the data. PRTG will remove all passwords from the config file before sending it to our support team.

Click on the Send button to start data upload. Ensure that FTP and HTTP connections are allowed on this machine.

Probe Settings

Name of Probe

Enter a meaningful name to identify the probe. PRTG shows this name, for example, in the device tree, and in all alarms by default. Please enter a string.

Reconnect Time

Define the time that PRTG will wait until the probe tries to reconnect to the core server if the connection fails. Please enter an integer value.

Connection to PRTG Core Server

These settings will affect how the probe will connect to the core server. A probe is either a local probe or a remote probe. PRTG will automatically detect the type of probe and show the correct setting options.

Server (IPv4 address or DNS name)

If this probe is configured as the Local Probe of the PRTG core installation, it will connect to the core via 127.0.0.1 which you cannot change.

If this probe is configured as a Remote Probe, enter the IP address or DNS name of the core server.

Port

Define the Port number under which probe and core server will communicate. Please enter an integer value. We recommend using the default value.

Probe GID

The Probe GID is a unique identifier for the probe. We recommend you to not change it.

Exception: Only if you substitute an existing probe from a different computer, you have to copy the GID from the old probe to the new probe. To do so, click on the Edit GID... button and confirm the warning with Yes. You can then change the value.

Note: You can deny GIDs under System Administration—Core & Probes in the PRTG web interface.

Probe Access Key

You do not need an access key for Local Probe connections.

On a Remote Probe, the Probe Access Key must match one of the access keys configured in your PRTG core server installation. If it does not match, the remote probe will not be able to connect to the core server. Please see System Administration—Core & Probes section for more information.

Note: Also check allowed and denied IPs there to ensure that the core server accepts the IP address of the remote probe.

Confirm Access Key

If you enter an access key for a remote probe, enter it in this field again to assure correctness.

Path for Probe Data Storage

Path

Define the data folder to which PRTG will store configuration and monitoring data. Click on the ... button to choose another folder on your system.

Note: Before changing the path, make sure you stop both services and copy all data to the new location.

Probe Settings for Monitoring

Administrative Probe Settings / Probe Settings for Monitoring

Define the IP address used for outgoing monitoring requests.

  • If there is more than one IP on the current system available, you can specify the IP address that will be used for outgoing monitoring requests of certain sensor types.
  • The setting is valid for all monitoring requests sent from this PRTG probe.
  • This setting will be used for sensors using the following connection types: HTTP, DNS, FTP, IMAP, POP3, Port, Remote Desktop, SMTP, and SNMP. Note: This feature does not support all sensor types for technical reasons.
  • This is useful for devices that expect a certain IP address when queried.
  • Default setting is auto. PRTG will select an IP address automatically.

Note: If you change this setting, some sensors might stop working. For example, sensors might show a Down status if the selected IP address is blocked on the way to or directly on the monitored device.

Outgoing IPv4

Define the IP address for outgoing requests using the IPv4 protocol. The list shows all IP addresses available on the current system. Choose a specific IP address or select auto.

Outgoing IPv6

Define the IP address for outgoing requests using the IPv6 protocol. The list shows all IP addresses available on the current system. Choose a specific IP address or select auto. For details about the basic concept of IPv6 in PRTG, please see IPv6 section.

Service Start/Stop

You can stop and start PRTG Windows service manually. Click the Stop Core Server resp. Stop Probe Service button to stop a service, and Start Core Server resp. Start Probe Service to start it again. Both actions usually take from a few seconds up to several minutes to complete. You can also restart the core server and probes via the PRTG web interface under Administrative Tools.

Note: If you want to schedule an automatic restart of Windows services for both core server and probe service, define a schedule on the Settings tab of a probe, section Administrative Probe Settings, in the PRTG web interface.

Logs and Infos

Log Files

Open Log Folder...

Open the PRTG Network Monitor data directory on your hard disk drive to access all log files which PRTG creates.

Send Logs to Paessler...

Open an assistant to send log files to the Paessler support team. Please see below for details.

Note: You can send log files more easily with the support bundle via Contact Support in the PRTG web interface.

Open Support Ticket...

This will open the support form on Paessler's webpage in a browser window. Note: If you need help, we recommend you to use the Contact Support option in the PRTG web interface instead.

The About section shows information about the version of installed PRTG programs and copyright.

Send Logs to Paessler

Note: You can send log files more easily with the support bundle via Contact Support in the PRTG web interface.

Send Logs to Paessler

Send Logs to Paessler

If you open a support ticket, Paessler support might ask you to send log files for further analysis. With the Send Logs to Paessler... button, PRTG will automatically collect, compress, and send your log files.

Send Logs to Paessler

Name

Enter your name.

Email

Enter your valid email address. You can provide any of your addresses; however, recommended and default is the email address of your PRTG account.

Ticket No.

This field is optional. If you have already opened a ticket at Paessler support, please provide the ticket number you received. Your files will then be associated with your ticket automatically.

Please enter the ticket number starting with PAE followed by four or more digits, for example, PAE12345. If you do not have a ticket number, leave this field empty.

Configuration

Define if your configuration file will be included in the data. PRTG will remove all passwords from the config file before sending it to our support team.

Click on the Send button to start data upload. Ensure that FTP and HTTP connections are allowed on this machine.

 

PRTG System Administrator—Topics

Related Topics

Keywords: Configure,Configure PRTG Server,Server Administrator