This site will be decommissioned on December 31st 2024. After that date content will be available at techdocs.broadcom.com.

 

VMware Remote Console | 24 JAN 2018 | Build 11818843

Check for additions and updates to these release notes.

What's in the Release Notes

The release notes cover the following topics:

What's New

This release of VMware Remote Console includes the following changes:

  • Updated versions of OpenSSL (1.0.2q), libxml2 (2.9.8), and cURL (7.6.1)
  • Additional fixes as described in Resolved Issues

Compatibility and Installation

You can install this release on the following host operating systems:

64-bit and 32-bit Windows

  • Windows Server 2016
  • Windows Server 2012 R2
  • Windows Server 2012
  • Windows Server 2008 R2 SP1
  • Windows Server 2008 R2
  • Windows 10
  • Windows 8.1
  • Windows 8
  • Windows 7

Mac

  • macOS 10.14
  • macOS 10.13
  • macOS 10.12
  • OS X 10.11

Linux

  • VMware Remote Console generally runs on the same Linux offerings as VMware Workstation versions that are released around the same time. For more information, see the VMware Compatibility Guide.

Documentation

See the following guides for information about installing and using VMware Remote Console.

Resolved Issues

The resolved issues are grouped as follows.

General

This release fixes the following general issues.

  • You cannot modify the vCPU count of a virtual machine without having host-level view privileges.

    If you had virtual machine-level privileges but did not have host-level view privileges, you could not change the number of vCPUs on a virtual machine.

    This issue has been resolved in this release. 

  • When you connect to a virtual machine, the VMware Remote Console window might not change to the correct size.

    The VMware Remote Console window would sporadically retain the default resolution instead of matching that of the guest machine.

    This issue has been resolved in this release.

  • If you connect directly to an ESXi host and attach a network adapter to a distributed port group, a misleading error message is displayed.

    The message Invalid device Network Adapter: Invalid configuration for device '0'. was displayed if you attempted to add or reconfigure a network adapter attached to a distributed port group. This configuration is only available when you connect through vCenter Server.

    If you have connected directly to an ESXi host, the interface no longer allows you to attempt to add or reconfigure a network adapter attached to a distributed port group.

Windows

This release fixes the following Windows issues.

  • VMware Remote Console cannot connect to a vCloud Director or vRealize Automation virtual machine through a proxy server configured by a proxy auto-configuration (PAC) file.

    Previously, VMware Remote Console was unable to obtain proxy server information from a WebSocket (ws or wss) URI scheme.

    This issue has been fixed in this release.

  • VMware Remote Console fails to connect to virtual machines when IPv6 is blocked.

    If a firewall is blocking all IPv6 connections, including those to a loopback address, VMware Remote Console would successfully create a socket but fail to connect to it. Because the socket was created, VMware Remote Console would not fall back to IPv4.

    This issue has been resolved in this release. IPv4 is used if IPv6 is unavailable or blocked.

Mac

This release fixes the following Mac issues.

  • Toggling the Connect Network Adapter check box may cause a network adapter to lose its backing information.

    If you toggled a network adapter backed by a vSphere Distributed Switch, the information about that distributed switch could be lost. You would then be unable to connect the network adapter again.

    This issue has been resolved in this release.

  • If you connect to vCloud Director or vRealize Automation, the Send Ctrl+Alt+Del option is unavailable.

    If you launched a session to vCloud Director or vRealize Automation, you would be unable to send the Ctrl+Alt+Delete keystroke combination to the virtual machine.

    This issue has been resolved in this release.

  • If you choose a client-side floppy disk or CD/DVD image file to mount, the file may be displayed as "Untitled" and fail to mount.

    If you selected a client-side image before selecting the remote VM device, the image would be displayed as "Untitled". Additionally, if you first selected a remote VM device, then a client-side image, and then a second client-side image, the second image would be displayed as the name of the first image.

    This issue has been resolved in this release.

Linux

This release fixes the following Linux issues.

  • File browsing is not supported on remote servers.

    In previous versions, the contents of the local host were displayed even when you attempted to browse files on a remote server.

    This issue has been resolved in this release.

Known Issues

The known issues are grouped as follows.

Mac

The following Mac issues are known to affect this release.

  • VMware Remote Console does not launch on macOS 10.13 or later.

    The Mac displays a System Extension Blocked message when you attempt to launch VMware Remote Console on macOS 10.13 or later versions.

    Workaround: As a user with administrator privileges, go to System Preferences > Security > Privacy. Under the General tab, near the bottom, you see a message about VMware software being blocked. Click Allow. For more information, see Knowledge Base Article 2151770.

  • Device options

    There are device-related options that are not available when running VMware Remote Console on a Mac. For example, you cannot add new devices, or display sound card settings. Unavailable Mac options are noted where applicable in the documentation.

Linux

The following Linux issues are known to affect this release.

  • On newer Linux distributions, terminal-based installation or online upgrade may fail.

    Version 5 of the ncurses library is required to install VMware Remote Console. However, newer versions of some Linux distributions, such as Fedora 28 and SUSE Linux Enterprise Server 15, include only version 6 by default. This may cause the online upgrade process and terminal-based installation process to fail.

    Workaround: Manually install ncurses 5 on your machine.

    • For Fedora 28 or 29, run the dnf install ncurses-compat-libs.x86_64 command.
    • For SUSE Linux Enterprise Server 15, use YaST to install the ncurses 5 package.
  • VMware Remote Console and VMware Workstation cannot be installed on the same computer.

    Because certain components are shared between VMware Remote Console and VMware Workstation, these products cannot both be installed on the same Linux machine.

    Workaround: None.

  • Wayland protocol is not supported

    VMware Remote Console requires Xorg and does not install or run under Wayland sessions. Installation errors occur on newer operating systems that use Wayland, such as Fedora 25.

    Workaround: None

  • Help link does not resolve

    You click the Help option from within VMware Remote Console and receive a file not found error.

    Workaround: Open a browser directly to https://docs.vmware.com/en/VMware-Remote-Console/index.html

  • Virtual machines automatically power on

    VMware Remote Console automatically powers on virtual machines when connecting to virtual machines that are powered off.

    Workaround: None

  • VMware Remote Console automatically closes

    VMware Remote Console automatically closes when the remote virtual machine shuts down.

    Workaround: None

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