This page describes how to enabled WebMKS for vCenter in environments that are using VNC.
Before you begin:
For VMs captured in a powered on state from vCenter 6.5+, the administrator can manually remove the VNC configuration from the VM definition file on the hypervisor to allow remote access without reconfiguring the VM.
To enable the WebMKS functionality for remote access to vCenter VMs, edit the abiquo.properties file:
Enable WebMKS for all VMs with no VNC configuration.
You cannot disable remote access for VMs using WebMKS
VMs with existing VNC configuration will still use VNC
If you change the remote access configuration or the VNC configuration because this will cause an error
Optionally force the use of WebMKS for VMs that are currently using VNC
Define the WebMKS proxy path
The value of the proxy path property is the FQDN and Location of the proxy in Apache on the Abiquo Server (without the protocol).
Optionally set or check the remote access properties.
List the interfaces of the hosts of the DC that Abiquo will use for remote access.
This is part of the remote access configuration for VMware. For more details, see Detect vCenter management IPs
After you capture VMs, you can now use hot reconfigure to enable remote access.
Users will now be able to access VM console via WebMKS when:
The VNC user and password are not valid for WebMKS
For more details of the WebMKS properties, see Abiquo Configuration Properties#esxi.