| VMware Remote Console 11.1.0 | 02 APR 2020 Build 15913118 | Mac App Store Build 15913119 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:
- Users with network privileges for a virtual machine can now change a virtual machine’s network adapter through VMware Remote Console without having host privileges for the virtual machine.
- VMware Remote Console for Windows supports the usage of smart cards connected in shared mode for authentication purposes.
- Deprecated APIs have been removed from the VMware Remote Console installer for macOS.
- The Linux installer for VMware Remote Console has been updated to use Python 3 and PyGObject/Pycairo.
- The Python library has been upgraded to version 3.8.1.
- The libpng library has been upgraded to version 1.6.37.
Compatibility
You can use VMware Remote Console 11.1.0 to connect to virtual machines in vSphere, vRealize Automation, and vCloud Director.
NOTES:
- VMware Remote Console 11.1.0 requires direct access to port 443 on ESXi hosts. For more information, see KB 76672.
- vRealize Automation 8.0 is not compatible with any version of VMware Remote Console.
You can install VMware Remote Console 11.1.0 on the following host operating systems:
Windows (64-bit)
- Windows Server 2019
- Windows Server 2016
- Windows Server 2012 R2
- Windows Server 2012
- Windows 10
- Windows 8
- Windows 7
Windows (32-bit)
- Windows 10
- Windows 7
macOS
- macOS 10.15
- macOS 10.14
- macOS 10.13
Linux
- CentOS 8.1
- CentOS 8.0
- Debian 10.3
- Fedora 31
- Fedora 30
- Linux Mint 19
- Red Hat Enterprise Linux 8.1
- SUSE Linux Enterprise Server 15 SP1
- Ubuntu 19.10
- Ubuntu 19.04
- Ubuntu 18.04
- Ubuntu 16.04
Known Issues
The known issues are grouped as follows.
macOS- The VMware Remote Console macOS App Store client may react slowly when performing passthrough on a mass storage device.
When a mounted mass storage device is passed through to a remote virtual machine, the VMware Remote Console macOS client may freeze for several seconds.
Workaround: Manually unmount the mass storage device from the host operating system before initiating passthrough in VMware Remote Console.
- 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.
- Some device operations are not supported on macOS.
When you access virtual machines using the VMware Remote Console macOS client, you cannot perform certain device operations. For example, you cannot add new devices or display sound card settings. The specific operations are noted in the documentation.
Workaround: None.
- 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.
- VMware Remote Console automatically closes when the virtual machine is powered off.
When you power off a virtual machine that is being accessed by the VMware Remote Console Linux client, the client automatically closes. You cannot perform operations on the powered-off virtual machine through VMware Remote Console.
Workaround: None.
- Virtual machines automatically power on.
When you access a powered-off virtual machine with VMware Remote Console, the virtual machine is automatically powered on.
Workaround: None. If you need to perform operations on a powered-off virtual machine through VMware Remote Console, power off the virtual machine after accessing it.
