1.2 Guardpot Manager Installation | Guardpot Documentation

Prerequisites

Before proceeding with the initial Guardpot software installation, ensure that the virtual machine deployment has been successfully completed and that console access to the deployed system is available.

1.2.1 Linux Console Login

When the Guardpot Manager virtual machine first boots, you will be presented with a Linux terminal login prompt. Enter the following default credentials to access the system, as shown in Figure 1.2.1-1.

prientesoftware login: prientesoftware
Password: PrienteSoftware.123
Last login: Wed May 20 10:15:32 UTC 2026 on tty1
prientesoftware@guardpot:~$ █

Figure 1.2.1-1 – Guardpot Manager Linux Console Login

Default Credentials:

Field	Value
Username	`prientesoftware`
Password	`PrienteSoftware.123`

Note: It is strongly recommended to change the default password after the initial setup is complete for security purposes.

1.2.2 Initiating Guardpot Manager Installation

From the installation menu, select option 2 to initiate the deployment and configuration process for Priente Software's Guardpot product, as shown in Figure 1.2.2-1.

Figure 1.2.2-1 – Guardpot Manager Installation Menu Selection

1.2.3 Network Interface Configuration

Select the appropriate network interface for the Guardpot Manager installation, as shown in Figure 1.2.3-1, then proceed to the next configuration step.

Figure 1.2.3-1 – Guardpot Network Interface Selection

1.2.4 Static IP Assignment

Assign an available static IP address to the IP Address field, as shown in Figure 1.2.4-1. Before proceeding, it is strongly recommended to verify that the selected IP address is not currently in use and will not cause network conflicts by performing a ping test or consulting your system administrator.

Figure 1.2.4-1 – Guardpot Static IP Address Configuration

1.2.5 Applying Network Configuration

To apply the network configuration changes, confirm the displayed prompts by entering Y followed by YES when requested, as shown in Figure 1.2.5-1. This will validate and apply the updated Guardpot network settings.

Figure 1.2.5-1 – Guardpot Manager Network Configuration Confirmation

1.2.6 DNS Record Requirements

During system startup, a DNS Records notification will be displayed, as shown in Figure 1.2.6-1. Configuring the required DNS record is mandatory for proper system accessibility. Without this configuration, attempting to access the Guardpot Manager web interface directly via its assigned IP address (for example, 172.16.61.222) may result in an HTTP 404 error, as illustrated in Figure 1.2.6-2.

Figure 1.2.6-1 – Guardpot Manager DNS Record Requirement Notification

Figure 1.2.6-2 – Guardpot Manager Web Interface 404 Error Without DNS Configuration

1.2.6.1 Windows Hosts File Configuration

Open the following file using any text editor running with administrator privileges: C:\Windows\System32\drivers\etc\hosts

Add the required DNS record, then save the file.

Figure 1.2.6.1-1 – Windows Hosts File

#hosts - Notepad
File   Edit   Format   View   Help
# Copyright (c) 1993-2009 Microsoft Corp. # This is a sample HOSTS file used by Microsoft TCP/IP for Windows. # This file contains the mappings of IP addresses to host names. # Each entry should be kept on an individual line. The IP address # should be placed in the first column followed by the corresponding # host name. # The IP address and the host name should be separated by at least one # space. # Additionally, comments (such as these) may be inserted on individual # lines or following the machine name denoted by a '#' symbol. # For example: # 102.54.94.97 rhino.acme.com # source server # 38.25.63.10 x.acme.com # x client host # localhost name resolution is handled within DNS itself. # 127.0.0.1 localhost # ::1 localhost 172.16.61.222 guardpot.local
Ln 22, Col 1     100%     Windows (CRLF)     UTF-8

1.2.6.2 Linux Hosts File Configuration

Open the hosts file with sudo privileges using nano or any preferred text editor:

sudo nano /etc/hosts