[KB5900] ESET PROTECT VM for Microsoft Azure FAQ

Solution

FAQ | Support Resources and Known Issues

ESET PROTECT is available for users who do not want to run the solution on a Windows Server instance and prefer to run ESET PROTECT in a Windows virtualized environment. This Azure cloud-based solution offers the same remote management capabilities for ESET users as running ESET PROTECT on a local server.

Microsoft Azure is a cloud computing platform that enables users to quickly and easily install a virtual machine (VM) running Windows and/or Linux as well as other software.


FAQ

  1. After deploying the ESET PROTECT, does ESET PROTECT install automatically?
    No, the simplest way to begin using ESET PROTECT on Azure is to deploy ESET PROTECT from the Azure marketplace.

    As an alternative, you can manually install ESET PROTECT on an existing Azure virtual machine.

  2. Can ESET users use an existing license to activate ESET PROTECT on Microsoft Azure?
    Yes, users with a valid license can use it to activate ESET PROTECT. This is a standard part of the installation process. See our licensing FAQ for answers to other licensing questions.

  3. Can I migrate my on-premises ESET PROTECT installation to Azure?
    Yes, migration from an on-premises server to Azure can be performed using the same steps as migrating between two servers with different IP addresses. See our Online Help topic for step-by-step instructions.

  4. Which database is installed with ESET PROTECT?
    By default, ESET PROTECT installs Microsoft SQL Server Express 2019. This database is sufficient to manage up to 5,000 endpoints. See our Online Help for database requirements and hardware sizing.

    To use Microsoft SQL Server, use or deploy a new SQL Server VM on Azure, or order a new Microsoft SQL Server database on Azure for this reason. SQL Server Management Studio is also available as a part of the ESET PROTECT VM.

  5. Are there any other software prerequisites to install ESET PROTECT on Microsoft Azure?
    Apache Tomcat is required to run the ESET PROTECT Web Console. See our Online Help topic for supported versions of Apache Tomcat.

  6. How do I install the ESET PROTECT VM in the Microsoft Azure portal?
    Visit deploy and install ESET PROTECT VM for Microsoft Azure
     
  7. How can I keep ESET PROTECT and VM up-to-date?
    If a new version is available, use a component upgrade task to upgrade ESET PROTECT and other ESET components.

    Additionally, we recommend that you regularly update the operating system of your VMs, Apache Tomcat and Java.
     
  8. Which ports are allowed for ESET PROTECT VM in its default settings?
    The following ports are allowed:
  • 443 for HTTPS connection to ESET PROTECT Web Console
  • 2222 and 2223 for connecting endpoints to ESET PROTECT Server
  • 3389 for RDP connection to VM
ESET PROTECT Wake up calls cannot be used in Microsoft Azure

The Wake up call feature, which typically functions to accelerate communication between ESET PROTECT and client computers, is blocked outside of the Azure Virtual network unless a VPN tunnel is established to extend L2 communication.

  1. Which languages does ESET currently offer for the ESET PROTECT VM?
    ESET PROTECT for the Azure platform is available in English and several other languages. You can set the language used by ESET PROTECT Web Console during installation, or later in the ESET PROTECT Web Console settings.

  2. Can I upgrade the size of my already created VM, for example from A1 Standard to A3 Standard to increase the number of CPU cores?
    Yes. To do so from the Azure platform, navigate to your VM → Settings General→ Size and select your desired sizing plan. A restart of your ESET PROTECT VM will be required to apply the sizing changes. Then you can continue using your ESET PROTECT VM without any data loss.

Support Resources and Known Issues

  1. What information is available in the Azure Marketplace about ESET PROTECT?
    No information is currently available.

  2. Can I perform a remote installation of ESET PROTECT Agent?
    Users are unable to install ESET PROTECT Agent remotely to endpoints behind a firewall or to endpoints in your company's local network. You can still use the Agent Live Installers method or deploy an Agent locally. This does not apply if you set up in your ESET PROTECT VM a VPN to your company's network.

  3. VM is vulnerable while RDP is allowed from anywhere
    From the Azure platform, navigate to Settings Endpoints Remote Desktop where you can allow a set of specific IP addresses.
    Alternatively, you can create a VPN connection to your VM and hide the remaining ports from the public.

  4. How can I contact my local ESET partner for support?
    ESET offers local technical support for ESET PROTECT and ESET-related problems. Click Support in the ESET PROTECT VM for answers to questions about the Azure platform and virtual machines.