The following prerequisites must be met before ERA Virtual Appliance deployment:

You must use a supported hypervisor.

Verify that the guest operating system (if a hosted hypervisor, such as VMware Workstation/Player or Oracle VirtualBox is used) is supported.

VT must be enabled in the host system BIOS. This feature may be named VT, Vanderpool Technology, Virtualization Technology, VMX, or Virtual Machine Extensions. This setting is commonly located in the security screen of the BIOS. The location of this setting varies depending on the system vendor.

Make sure the connection for the network adapter on your Virtual Machine is set to Bridged (or, alternatively NAT). During ERA VA configuration, you can specify network settings including domain details so that the Static Group Synchronization task will run properly.

If you are using NAT mode, port forwarding must be configured on your virtual machine for ERA to be accessible from the network. Ports that need forwarding are displayed in the console window of your ERA VA after you've deployed and configured it.

ERA Virtual Appliance only supports IPv4 environments. It is possible to set up an IPv6 environment manually, however, such an environment is not supported.

validation-status-icon-warning IMPORTANT

We recommend that you create a snapshot of your newly deployed and configured ERA VA and synchronize it with Active Directory. We also recommend that you create snapshot prior to deploying the ERA Agent on client computers.

ERA certificates are required to deploy ERA Proxy and ERA MDM or ERA VAgentHost. You must have an ERA Server instance running to generate these certificates, which encrypt communication between ERA components.