Issue

This article provides information about the ESET Virtualization Security solution for VMware vShield.

Disclaimer: The product referenced in this article is a software module that is developed and supported by ESET. Use of this product is also governed by the end user license agreement of the ESET. You must obtain from the ESET the application, support, licensing for using this product.

Solution

• VMware vShield Endpoint installed into VMware environment
• VMware Tools installed on each virtual machine
• ESET Remote Administrator 6 management server installed
• ESET Remote Administrator vAgent Host
• deployed ESET Virtualization Security that integrates component from VMware (vShield library) and ESET Scanning Engine

• check if network allows communication via port 443 with vShield Manager
• restart vShield Manager VM
• reinstall vShield Endpoint module on ESXi (via VShield Manager Web UI)

ESET Virtualization Security shows zero number of connected/protected VMs

• make sure Guest VMs are running and have installed VMware tools with Endpoint module
• make sure network allows communication via port 48651 to/from EVS
• recheck vShield registration or re-register with vShield (enter management mode - vShield registration)

Errors in trace log:

Error: error[582a0000]: ESET Mdm client: CURL: Error in call easy perform: 3

Possible cause: The hostname/IP address is not configured properly in the ERA policy for EVS machine.

Possible Solution: Make sure there is only one policy for ESET Virtualization Security - Security Appliance with proper settings in the Hostname field under VIRTUAL AGENT HOST