ERA installation | Supported hypervisors | Active Directory | Which virtualization solution to use | Troubleshooting ERA OVA
The following three solutions are available for virtual environments:
Virtual environment | Recommended ESET solution |
Physical endpoints/servers | ESET Endpoint Antivirus/Security (endpoints)/ESET File Security (servers) |
Physical and virtual machines (hypervisor agnostic) |
|
Virtual machines using ESX hypervisor (vSphere/vShield) | ESET Virtualization Security |
Virtual servers in Microsoft Azure | ESET File Security for MS Windows Server for Azure |
VDI (persistent-state VMs) |
|
VDI (non-persistent-state VMs using ESX hypervisor) | ESET Virtualization Security |
For answers to questions regarding which product is recommended for your virtual environment, see below:
The following video animations demonstrate the system architectures of ESET Shared Local Cache and ESET Virtualization Security and how they use system resources.
ESET Virtualization Security—System Architecture and Resource Allocation
ESET Shared Local Cache System—System Architecture and Resource Allocation
Which log files can I access for troubleshooting the ERA Virtual Appliance?
The following log files can be used to troubleshoot the ERA Virtual Appliance:
If ERA VA deployment fails, do not restart the appliance but first check this log file:/root/appliance-configuration-log.txt
ERA Server installation log:/var/log/eset/RemoteAdministrator/EraServerInstaller.log
ERA Server trace logs:
trace.log, status.html and last-error.html located in /var/log/eset/RemoteAdministrator/Server/
ERA Server dumps:/var/opt/eset/RemoteAdministrator/Server/Dumps/