Installation of ESET Protect server on Proxmox

Installation of ESET Protect server on Proxmox

ESET is a leading antivirus program. The manufacturer suggests that in small and medium-sized companies and environments with small networks, install ESET PROTECT for Linux instead of for Windows. We will show you how to successfully install it on the Proxmox virtualization environment. If you are wondering how to do this and reduce implementation costs, this article is for you.

Table of Contents

1) Creating a virtual machine

We will use our Proxmox environment to create a virtual machine. We encourage you to read the article devoted to the installation and configuration of this free virtualization environment. Click the Create VM icon and create a machine without a hard drive for now. In the OS tab, do not create or load any image disc (do not use any media). We leave the default version of the Linux operating system.
In the following tabs we can suggest the following configuration: System – leave the default configuration; Disks – remove the suggested disk; CPU – leave one processor and set 4 cores, this will change it to the host; Memory – 4GB; Network – we don’t change anything. After confirming with the “Finish” key, on the last tab we have a ready machine skeleton. It is important to remember the VM ID number assigned to it in the first “General” tab. In our example it is501.

2) Software preparation

ESET Protect server software can be downloaded directly from the manufacturer’s website. The link below takes us to the “Virtual Appliances” section, where you should copy the link to the file protect_appliance.ova (file size approximately 2 GB). Then we log in to the console of our Proxmox environment. To work in an orderly manner, we go to the /usr/src directory where we should keep the software sources. Then we download the file from the manufacturer’s website using the copied link and change its name to a more practical one, e.g. protect.ova.

					cd /usr/src
wget substitute_copied_link -O protect.ova 
Plik OVA to szablon zawierający funkcjonalny system operacyjny CentOS 7 wraz ze źródłami oprogramowania serwera ESET Protect. Plik OVA jest zapisywany w formacie Open Virtualization Format (OVF), który jest standardowym formatem używanym do pakowania i dystrybucji oprogramowania uruchamianego na maszynach wirtualnych. Pliki OVA to po prostu katalog OVF zapisany w jednym archiwum przy użyciu pakietu TAR do celów dystrybucji. Zatem w kolejnym kroku rozpakujemy archiwum TAR. Następnie zaimportujemy obraz dysku na nasz lokalny zasób dyskowy local-lvm dla stworzonej przez nas maszyny numer 501 używając formatu qcow2.
					tar -xvf protect.ova
qm importdisk 501 Protect_Appliance-disk1.vmdk local-lvm --format qcow2


The qcow2 format is a disk image file saved in the second version of the QemU Copy On Write format. It is used by the QEMU virtualization software and stores the contents of the virtual machine’s hard drive. The QEMU disk allocation strategy allows for smaller file sizes because it delays memory allocation until disk space is needed. This differs from other policies that allocate specific amounts of space, in which case some empty space may go unused. After a dozen or so seconds, we receive valuable information about the successful completion of the import and the appearance of the unused0 disk prepared for the 501 machine.

3) Installation and configuration of ESET Protect server

In the Proxmox console, we select our 501 machine and in the Hardware section we see our imported disk. Click on it and select “Attach” from the menu. Then we go to the Options section and the Boot Order item. By clicking “Edit” we will be able to move our disk with the imported image to the first position. Uncheck the remaining devices.
Now we can start our machine by clicking Start. The virtual console will ask us to enter a temporary IP address in the browser for initial configuration.
From the browser level, we set the server name, IP address and Administrator password.

ATTENTION!!! The password is entered only once. There is no request for it to be repeated. Enter them carefully and remember.

At this step, we can also enter access data to connect to the domain controller and select a system update during installation.
After entering the network configuration and confirming it, we will receive a message asking us to follow the further installation process on the console.
After some time, the installation process will be completed and our server will be ready for operation. We will receive another request to log in via the website. This time it will be on the IP address we have set with the administrator login and password that we set earlier.
After logging in, we can proceed to configuring protection in our company, but this is a topic for another post.
Share this post

Do you have questions or you need an offer?

Contact us!

Most popular

Related Posts

We Have Launched

Monitoring & Reporting of Your VoIP Server