Updated on: 23 JUNE 2016

VMware Host Client 1.0.0 | 15 MAR 2016 | 3617585

Check for additions and updates to these release notes.

What's in the Release Notes

The release notes cover the following topics:

VMware Host Client Overview

The VMware Host Client is an HTML5-based client that is used to connect to and manage single ESXi hosts. It can be used to perform administrative tasks to manage host resources such as virtual machines, networking, and storage. The VMware Host Client can also be helpful for troubleshooting individual virtual machines or hosts if vCenter Server and the vSphere Web Client are unavailable.

In vSphere 6.0 Update 2, VMware continues to support the Windows C# Client, also known as vSphere Client, but you now have the option of using the VMware Host Client instead of the Windows C# Client to perform similar host-based operations.

For more information, see the vSphere 6.0 Documentation Center

VMware Host Client Features

The VMware Host Client 1.0.0 functions include, but are not limited to the following operations:

  • Support for the latest hardware version.
  • Basic virtualization operations, such as deploying, configuring, and editing virtual machines of various complexity, including console access to the virtual machines.
  • Creating and managing network and datastore resources.
  • Displaying current host and resource settings, including graphs of performance and utilization, and logs of host components to help troubleshooting.
  • Advanced tuning of host level options to improve performance.

Updating the VMware Host Client

Newer versions of the VMware Host Client might become available outside of the vSphere release. To evaluate whether the host contains the latest version of the VMware Host Client, check what VIBs are installed to your environment and examine the VIBs version information.

You can update your VMware Host Client environment by entering a URL to a VIB. If you provide a VIB, the existing VIB that is installed to your VMware Host Client environment is updated to the new VIB.

Known Issues

  • The Guest operating system screen resolution might not change automatically
    When you enter full screen mode for a console, the guest operating system screen resolution might not change automatically to fill the screen without scaling, even when VMware Tools is installed.
    Workaround: Ensure that the guest operating system has enough video memory assigned to be able to handle the new resolution. You can edit the settings of the virtual machine to assign enough video memory.

  • Nonadministrative users are not supported
    VMware does not offer support for nonadministrative users. If you attempt to use the VMware Host Client as a nonadministrative user, the VMware Host Client might not work properly.
    Workaround: None.

  • You cannot remove a PCI device from a virtual machine
    When editing a virtual machine, attempting to remove a PCI passthrough device is silently ignored. The PCI passthrough device continues to be attached to the virtual machine.
    Workaround: There are two ways to remove a PCI device from a virtual machine. You can manually edit the .vmx file for the virtual machine to remove the entries that configure the PCI passthrough device. Alternatively, you can use the vSphere Web Client to log in to your target ESXi host and remove the PCI device from the virtual machine.

  • The mouse might not work for some Windows guest operating systems until VMware Tools is installed
    When you use a Web browser to access a console on an ESXi 6.0 or later host, the mouse might be unavailable when you install a new Windows guest operating system.
    Workaround: Use the keyboard to install VMware Tools. After Windows is booted, mount the VMware Tools ISO, and then use the keyboard to start the VMware Tools installer.

  • Remote CD and floppy devices are not supported
    Virtual machines can be configured to use the local CD and floppy devices of your system. The VMware Host Client does not support such configurations. CD and floppy drives configured to use the devices on your local system will not work.
    Workaround: To use your local system devices, you must use VMRC, the vSphere Web Client, or the vSphere Windows client. Alternatively, use a file-backed CD or floppy by using an ISO or floppy image file from a datastore.

  • Issues occur if you connect the VMware Host Client to hosts using IPv6 addresses
    If you connect the VMware Host Client to hosts using an IPv6 address, the VMware Host Client does not function properly. Virtual machine screen shots and consoles fail to load.
    Workaround: If possible, use the host's Fully Qualified Domain Name, or FQDN, or use an IPv4 address.

  • Export virtual machine might appear to miss downloading disks
    To support downloading multiple disks, the VMware Host Client attempts to open separate windows for each VMDK disk file to start the downloads. If your browser is configured to block popups, it might seem that the disks are not downloaded because you don’t see any notifications for the downloads.
    Workaround: Disable the popup blocker of your browser.

  • Installing a VIB update fails with a failure notification but appears successful in the Recent Task pane
    When performing a VIB update, the task result might appear to be successful, but an error notification is displayed.
    Workaround: If the reason for the failure is unclear, see the esxupdate.log file from the host to ascertain the reason for the failed VIB update.

  • When viewing the summary page of a virtual machine that is powered on or suspended, a browser login dialog box might prompt you to log in.
    When you view the summary page of a virtual machine that is powered on or suspended, the virtual machine screen shot loads without the required CSRF token, which causes the ESXi host to require a new session. The new session causes the pop up of a login dialog box and requires you to enter your username and password.
    Workaround: When you are prompted to enter your username and password, click Cancel.

  • New After upgrading to a newer version of ESXi, you might encounter a Service Unavailable error when you attempt to access your ESXi host
    After you upgrade an ESXi host from 5.5 to 6.0 or later, attempting to navigate to http://host-name/ui or http://host-IP-address/ui might result in the following error:

    503 Service Unavailable (Failed to connect to endpoint: [N7Vmacore4Http16LocalServiceSpecE:0xffa014e8] _serverNamespace = /ui _isRedirect = false _port = 8308)

    A change to /etc/vmware/rhttpproxy/endpoints.conf remains after an upgrade and causes the /ui endpoint to override the VMware Host Client.
    1) Log in to your ESXi host either by using SSH or ESXi Shell. If you use SSH, you might need to enable SSH first. You can enable SSH by using DCUI.

    2) Back up endpoints.conf. file

    cp /etc/vmware/rhttpproxy/endpoints.conf /tmp
    3) Open the /etc/vmware/rhttpproxy/endpoints.conf file in an editor and remove the following line:
    /ui local 8308 redirect allow
    4) Restart the reverse Web proxy.
    /etc/init.d/rhttpproxy restart
    5) Try to access the VMware Host Client at http://host-name/ui or http://host-IP-address/ui

  • New The VMware Host Client might freeze during high rate of task activity
    The Host Client might appear to freeze when the rate of task activity is high. If you experience a similar issue, minimize the recent tasks panel until the rate of activity subsides. Depending on host load, actions in the client might also have variable latency. For example, when the host is under high load, latency increases when you right-click an object.
    Workaround: Minimize the recent tasks panel.

check-circle-line exclamation-circle-line close-line
Scroll to top icon