Abiquo 5.2

Skip to end of metadata
Go to start of metadata

This page describes how to enabled WebMKS for vCenter in environments that are using VNC.

Before you begin:

  1. Install WebMKS proxy
  2. Brand the WebMKS interface as required. See Branding WMKS.

Upgrade notes

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.

  • Do not modify remote access or VNC configurations when WebMKS is activated because this will cause an error
  • VMs with WebMKS active will always have remote access and you cannot enable it or disable it in the VM

To enable the WebMKS functionality for remote access to vCenter VMs, edit the abiquo.properties file:

  1. Enable WebMKS for all VMs with no VNC configuration. 

    com.abiquo.esxi.webmks = true
    1. You cannot disable remote access for VMs using WebMKS 

    2. VMs with existing VNC configuration will still use VNC

    3. If you change the remote access configuration or the VNC configuration because this will cause an error

  2. Optionally force the use of WebMKS for VMs that are currently using VNC

    com.abiquo.esxi.webmks.force = true
    1. To enable WebMKS, disable the remote access configuration (to disable the VNC configuration)
    2. Do not make changes to the VNC configuration, such as the password because this will trigger an error 
    Now remote access will be via WebMKS and it will always be enabled

  3. Define the WebMKS proxy path

    com.abiquo.esxi.webmks.proxypath = api.cloud.example.com/wsdata

    The value of the proxy path property is the FQDN and Location of the proxy in Apache on the Abiquo Server (without the protocol). 

  4. Optionally set or check the remote access properties.

    com.abiquo.esxi.discovery.networkinterface.networks =,

    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:

  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

  • No labels