All-in-one installation of ESET PROTECT Server


note

Another alternative is to deploy a pre-configured ESET PROTECT Virtual Appliance (if you use a hypervisor).

If you are upgrading from a previous version of ESET PROTECT or ESMC 7.x, follow these instructions.

The ESET PROTECT All-in-one installer is available for Windows operating systems only. The All-in-one installer allows you to install all ESET PROTECT components using the ESET PROTECT installation Wizard.

1.Open the installation package. On the Welcome screen, use the Language drop-down menu to adjust the language settings. Click Next to proceed.

welcome

2.Select Install and click Next.

package_installation_select

3.Deselect the check box next to Participate in product improvement program if you do not agree to send crash reports and anonymous telemetry data to ESET. If the check box is left selected, telemetry data and crash reports will be sent to ESET. After accepting the EULA, click Next.

4.Select the components to install and click Next.

arrow_down_business Microsoft SQL Server Express

arrow_down_business Add custom HTTPS certificate for Webconsole

arrow_down_business Apache HTTP Proxy

package_installation_components

5.If you have selected Add custom HTTPS certificate for Webconsole, click Browse and select a valid Certificate (.pfx or .p12 file) and type its Passphrase (or leave the field blank if there is no passphrase). The installer will install the certificate for Web Console access on your Tomcat server. Click Next to continue.

package_installation_import_https_certificate

6.If errors are found during the prerequisites check, address them accordingly. Make sure your system meets all prerequisites.

arrow_down_business .NET v4 is not installed

arrow_down_business No Java found / Java (64-bit) detected

arrow_down_business There is only 32 MB free on a system disk

arrow_down_business ESET Remote Administrator 5.x or older is installed on the machine

7.When the prerequisites check is complete and your environment meets all requirements, the installation will begin. Be aware that installation can take over an hour, depending on your system and network configuration.


note

When the installation is in progress, the ESET PROTECT installation Wizard is unresponsive.

package_installation_progress

8.If you chose to install Microsoft SQL Server Express in step 4, the installer will perform a database connection check. If you have an existing database server, the installer will prompt you to enter your database connection details:

arrow_down_business Configure the connection to SQL/MySQL Server

9.The installer will prompt you to enter a password for the Web Console Administrator account. This password is important – you will use it to log into the ESET PROTECT Web Console. Click Next.

package_installation_webconsole

10. Leave the fields as they are or type in your corporate information to appear in the details of the ESET Management Agent and the ESET PROTECT Server certificates. If you choose to enter a password in the Authority password field, be sure to remember it. Click Next.

package_installation_certificate

11. Enter the valid License Key (included in the new purchase email you received from ESET) and click Next. If you use legacy license credentials (Username and Password), convert the credentials to a License Key. Alternatively, you can choose to Activate later (see the Activation chapter for additional instructions).

package_installation_activation

12. You will see the installation progress.

package_installation_progress_2

13. If you selected to install the Rogue Detection Sensor, you will see the installation windows for the WinPcap driver. Make sure to select the check box Automatically start the WinPcap driver at boot time.

14. When the installation is complete, "ESET PROTECT components were installed successfully" will be displayed in addition to your ESET PROTECT Web Console URL address. Click the URL to open the Web Console, or click Finish.

package_installation_successful

If the installation is not successful:

Review the installation log files in the All-in-one installation package. The logs directory is the same as the directory for the All-in-one installer, for example:
C:\Users\Administrator\Downloads\x64\logs\

See Troubleshooting for additional steps to resolve your issue.