Install the ESMC Server

The ESMC All-in-one installer is available for Windows operating systems only. The All-in-one installer allows you to install all ESMC components using the ESMC 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 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 applicable components to install and click Next.

hmtoggle_plus0Microsoft SQL Server Express
hmtoggle_plus0Add custom HTTPS certificate for Webconsole
hmtoggle_plus0Apache 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 certificate will be installed on your Tomcat server and used for Web Console access. 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.

hmtoggle_plus0.NET v3.5 is not installed/.NET v2.0 SP2 is not installed
hmtoggle_plus0No Java found / Java (64-bit) detected
hmtoggle_plus0There is only 32 MB free on system disk

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

Note

When installation is in progress, the ESMC installation Wizard is unresponsive.

package_installation_progress

8.If you chose to install Microsoft SQL Server Express in step 4, a database connection check will be performed and you should skip to Web Console user & server connection. If you have an existing database server, you will be prompted to enter your database connection details in the next step.

9.If you are using an existing SQL Server or MySQL, configure your connection settings accordingly. Enter your Database name, Hostname, Port number (you can find this information in Microsoft SQL Server Configuration Manager), and Database account details (Username and Password) into the appropriate fields and then click Next. The connection to the database will be verified. If you have an existing ESMC database (from a previous ERA v.6 installation) on your database server, it will be detected. You can choose to Use existing database and apply upgrade or Remove existing database and install new version.

Use Named Instance - If you are using MS SQL database, you can also select the Use Named Instance check box. This will allow you to use custom database instance, you can set it in the Hostname filed in the form HOSTNAME\DB_INSTANCE for example: 192.168.0.10\ESMC7SQL . For clustered database use only the clustername. If this option is selected, you cannot change which port will be used, system will use default ports determined by Microsoft.

note

Note

When you select the Use Named Instance check box, you can connect the ESMC Server also to MS SQL database that is installed in a Failover Cluster. In Hostname field, enter the cluster name.

note

Note

There are two options when entering Database account information. You can use a dedicated database user account that will have access to the ESMC database only, or you can use an SA account (MS SQL) or root account (MySQL). If you decide to use a dedicated user account, you need to create the account with specific privileges. For details, see Dedicated database user account. If you do not intend to use a dedicated user account, enter your administrator account (SA or root).

package_installation_db_connection

If you entered SA account or root account in the previous window, click Yes to continue using the SA/root account as the database user for ESET Security Management Center.

package_installation_db_user_root

If you click No, you must select Create new user (if you have not already created one) or Use existing user (if you have a dedicated database user account as mentioned here).

package_installation_db_user_create_use

10. You will be prompted to enter a password for the Web Console Administrator account. This password is important–you will use it to log into the ESMC Web Console. Click Next.

package_installation_webconsole

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

package_installation_certificate

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

package_installation_activation

13. The installation progress will be displayed.

package_installation_progress_2

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

15. When the installation is complete, "ESET Security Management Center components were installed successfully" will be displayed in addition to your ESMC 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.