Abiquo Documentation Cookies Policy

Our Documentation website uses cookies to improve your experience. Please visit our Cookie Policy page for more information about cookies and how we use them.


Abiquo 4.7

Skip to end of metadata
Go to start of metadata

Abiquo 4.7.0 introduces optional support for VMware’s native HTML5 console (WebMKS) to provide remote access to VMs running on vCenter 6.0+. This feature will be especially helpful on vCenter 6.5+ to enable a remote access configuration for a VM captured in a powered on state.

Abiquo already uses the WebMKS console for remote access to vCloud. For details of how to white-label the WebMKS console window, see Branding WMKS.

To use the WebMKS console from Abiquo, the user must be the VM owner or have the privileges to Access virtual datacenters view and Manage virtual appliances. The URL for remote access contains a one-time access token. You cannot access the same VM with both WebMKS and VNC. Deployed VMs with VNC configuration will still be accessible using VNC after you enable WebMKS. The VNC user and password are not valid for WebMKS. When using WebMKS, if you make changes to the VM's VNC configuration, this will trigger an error.

Enable WebMKS

Before you begin, brand the WebMKS interface as required. See Branding WMKS.

Upgrade notes

For VMs captured in a powered on state with Abiquo 4.6.3+ and 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 activate the WebMKS functionality for remote access to vCenter VMs:

  1. Edit the abiquo.properties file. See Abiquo Configuration Properties
  2. Set the com.abiquo.esxi.webmks property to "true".
    1. This will automatically enable remote access to all VMs on vCenter via WebMKS, except for VMs with existing VNC configuration, which can still use VNC
      1. Do not modify VNC configurations when WebMKS is activated because this will trigger an error
  3. To force the use of WebMKS, which will delete existing VNC configurations from VMs, set the com.abiquo.esxi.webmks.force property to "true".
  4. After you capture VMs, you can now hot reconfigure them to enable remote access 
  5. Users will now be able to access VM console via WebMKS when:
    1. They are the VM owner
    2. They have the privileges to Access virtual datacenters view and Manage virtual appliances. By default the standard user has these privileges 
    The VNC user and password are not valid for WebMKS

For more details of the WebMKS properties, see Abiquo Configuration Properties#esxi