Horizon Client for Mac 4.6 | 21 September 2017
Last Updated: 21 September 2017
These release notes cover the following topics:
Horizon Client for Mac makes it easy to access your remote desktops and published applications from your Mac with the best possible user experience on the Local Area Network (LAN) or across a Wide Area Network (WAN).
- Support for Mac OS X Yosemite (10.10), Mac OS X El Capitan (10.11), macOS Sierra (10.12), and macOS High Sierra (10.13) - Use a 64-bit Intel-based Mac to work on your remote desktop or published application.
- Unmatched performance - The adaptive capabilities of the PCoIP display protocol and the VMware Blast display protocol are optimized to deliver the best user experience, even over low-bandwidth and high-latency connections. Your remote desktop or published application is fast and responsive, regardless of where you are.
- Simple connectivity - Horizon Client for Mac is tightly integrated with VMware Horizon 6 and VMware Horizon 7 for simple setup and connectivity. Quickly reconnect to your remote desktop or published application by selecting shortcuts in Horizon Client.
- Secure from any location - At your desk or away from the office, your data is delivered securely to you wherever you are. Enhanced certificate checking is performed on the client. Horizon Client for Mac also supports optional RADIUS and RSA SecurID authentication.
- Change the VMware Blast network condition after you connect to a server
After you connect to a server, you can switch the network condition between Typical and Excellent, if Typical or Excellent was selected before you connected to the server.
- Application pre-launch works without enablement in Horizon Client
You can now use the application pre-launch feature without having to set the Horizon Client reconnection behavior to "Reconnect automatically to open applications."
- Select specific monitors in a multi-monitor setup
You can use the selective multiple-monitor feature to select the monitors on which to display a remote desktop window. For example, if you have three monitors, you can specify that the remote desktop window appears on only two of those monitors. By default, a remote desktop window appears on all monitors in a multiple-monitor setup.
- macOS High Sierra (10.13) support
You can install Horizon Client on a macOS High Sierra (10.13) system.
- Norwegian keyboard support
You can use a Norwegian keyboard with Horizon Client.
- SHA-256 support
Horizon Client has been updated to support the SHA-256 cryptographic hash algorithm.
- OpenSSL 1.0.2l support
The OpenSSL library is updated to version openssl-1.0.2l.
The user interface and documentation for Horizon Client are available in English, Japanese, French, German, Simplified Chinese, Traditional Chinese, Korean, and Spanish.
- Horizon Client requires a Mac OS X Yosemite (10.10), Mac OS X El Capitan (10.11), macOS Sierra (10.12), or macOS High Sierra (10.13) operating system running on a 64-bit Intel-based Mac.
- Horizon Client is supported with the latest maintenance release of Horizon 6 version 6.x and later releases.
- To install Horizon Client for Mac, download the disk image file from the VMware Horizon Client download page. For system requirements and installation instructions, see the VMware Horizon Client for Mac Installation and Setup Guide document.
If you use the PCoIP display protocol, connecting some password-protected storage devices (such as IronKey USB flash drives) might not work correctly. For example, after you redirect the device to the remote desktop, the password prompt does not appear. The remote desktop shows that a new drive was added and so displays a new drive letter but no corresponding label to identify the device.
Workaround: Configure Horizon Client to automatically connect the device when you insert it. From the Horizon Client menu bar, select Desktop > USB > Autoconnect USB Devices on Insert.
If Microsoft Remote Desktop Connection for Mac version 2.1.1 is installed on the Mac client system and you use the RDP display protocol to connect to a desktop on a Windows Server 2008 R2 RDSH server for which RDS licensing is specified, the following error message occurs: You were disconnected from the Windows-based computer because of problems during the licensing protocol. This is a third-party issue.
Changes to webcam and audio devices that are connected to, or disconnected from, the Mac client system during a remote desktop session are not detected by the Real-Time Audio-Video feature.
Workaround: Disconnect and reconnect to your remote desktop session to detect webcam and audio device changes. For example, if you connect a USB headset to the Mac client system during a remote desktop session and you want to use that headset on the remote desktop, you must disconnect and reconnect to the remote desktop session to make the headset available.
If Microsoft Remote Desktop Connection for Mac version 2.1.1 is installed on the Mac client system and you use the RDP display protocol to connect to an RDS desktop hosted on Windows Server 2012, the following error message appears: Remote Desktop Connection cannot verify the identity of the computer that you want to connect to.
Workaround: Use Horizon Client for Mac 3.0 and select the PCoIP display protocol when you connect to the remote desktop. Note: If you are using a pre-3.0 version of Horizon Client for Mac, you cannot select the PCoIP display protocol.
The keyboard language is not synchronized with the language in desktop and application sessions.
When you insert an SD card into a Transcend USB 3.0 card reader attached to your Mac client system, the SD card is not mounted automatically. Because the SD card is not mounted on your Mac client system, the device does not appear in the Connection > USB menu in Horizon Client and you cannot use the USB redirection feature to connect the device to the remote desktop.
Workaround: Reinsert the SD card into the Transcend card reader. After the device is connected to the remote desktop, reinsert the SD card again to make the disk volume appear in the remote desktop.
If you use the USB redirection feature to connect a Transcend USB 3.0 external hard drive to a remote desktop from your Mac client system, files that you copy or move to the drive do not appear on the drive after you disconnect the drive from the remote desktop.
Workaround: Redirect the external hard drive to the remote desktop again. The files appear on the drive.
If an administrator edits an application pool in View Administrator and changes the path to point to a different application that already has an application pool associated with it, unexpected results can occur. For example, the original application might be launched from the Mac Dock instead of the new application.
Workaround: Make sure that each application in a farm is associated with only one application pool.
Users cannot launch an application from the Mac Dock if multiple application pools point to the same application in one farm, and if the application pool the users selected was created with associated parameters in View Administrator. If a user saves the application in the Mac Dock and tries to open the saved item, the application fails to launch with the associated parameters.
Workaround: Make sure that each application in a farm is associated with only one application pool.
If multiple Horizon clients connect to the same RDS desktop or remote application simultaneously and map to a location-based printer with the same name, the printer appears in the first client session, but not in later client sessions.
Workaround: For the client sessions in which the printer does not appear, perform a manual refresh. For a remote desktop, press F5 or refresh the Devices and Printers window. For a remote application, close and reopen the application print dialog box. The location-based printer appears in the printer list.
Sometimes the virtual printing feature and location-based printing feature are not able to display the correct list of printers in the Devices and Printers window of a remote, session-based desktop. This issue can occur with desktops provided by Windows Server 2012 RDS hosts. The printers shown within applications are correct, however.
Workaround: Log off the desktop running on the Windows Server 2012 RDS host and reconnect to it.
If you use a PIV smart card to authenticate to a Windows 7, XP, or Vista remote desktop on which ActivClient is installed, Horizon Client might stop responding when you log off from the desktop.
Workaround: On the Windows 7 remote desktop, uninstall ActivClient and use Windows Update to install the PIV smart card driver. There is no workaround for Windows XP and Vista desktops.
If you set the Horizon Client security preference (VMware Horizon Client > Preferences > Security) to Do not verify server identity certificates and connect to a View server that has a valid root-signed certificate, Horizon Client might stop responding.
Workaround: Unplug the smart card reader and then plug it back in.
You cannot use a PIV smart card to authenticate to a Windows 8 or later remote desktop from an Mac OS X Mavericks (10.9) or later client system, or to a Windows Vista remote desktop from an Mac OS X Yosemite (10.10) or later client system.
Workaround: For Mac OS X 10.10 and later client systems, use Charismathics software for PIV smart cards.
Keyboard shortcut mappings do not work if you are connected to a remote desktop or application and the Mac Input Source is Traditional Chinese or Korean.
Workaround: Before you connect to the remote desktop or application, switch to the English Input Source on the Mac client system. If you are already connected to the remote desktop or application, reconnect to the View Connection Server instance and switch to the English Input Source on the Mac client system before you connect to the remote desktop or application.
If you launch a remote desktop with the PCoIP display protocol or the VMware Blast display protocol in full screen or window mode on an iMac with Retina 5K display and the screen size is more than 4K (4096 x 2160), auto fit does not work for the remote desktop if you change the display to full resolution (Connection > Resolution > Full Resolution).
Workaround. None. This problem is caused by a PCoIP or VMware Blast limitation.
If you use the client drive redirection feature to share a folder or drive with remote desktops and applications, but you connect to a remote desktop or application that does not support client drive redirection, an error message is not displayed to notify you that the folder or drive was not shared.
Workaround: Install View Agent 6.1.1 or later in the remote desktop or RDS host. View Agent 6.1.1 or later is required to use the client drive redirection feature.
When you connect to a Windows desktop, start USB services, redirect a USB storage device to the desktop, disconnect from the desktop, and then try to reconnect to the desktop, either USB services are not available in the desktop or you cannot reconnect to the desktop. In View Administrator, the state of the machine is Agent unreachable.
Workaround: If you are an end user, restart Horizon Client and try again. If you are a View administrator, restart View Agent in the machine.
If you use the client drive redirection feature to share a USB drive with a remote desktop, and you unplug the device and then plug it back in during the desktop session, you can no longer access the device in the remote desktop. Unplugging a USB drive during a session also removes the drive and folder entries from the Folder list on the Sharing panel in the Preferences dialog box and you must reshare the drive the next time you connect to the remote desktop.
Workaround: Do not unplug a shared USB drive during a remote desktop session unless you intend to stop using the device.
If you use Horizon Client on a new MacBook, and you use the USB-C port to connect to the network, you might notice poor performance when copying and pasting between a remote desktop to a shared folder.
After you install Horizon Agent 7.0 in a Windows 7 remote desktop, you can no longer use Microsoft Remote Desktop Connection Client for Mac 2.1.1 to connect to the remote desktop. This problem occurs because TLSv1.0 is disabled by default in Horizon 7 version 7.0 and later.
Workaround: Install Microsoft update 3080079: Update to add RDS support for TLS 1.1 and TLS 1.2 in Windows 7 or Windows Server 2008 R2 in the Windows 7 virtual machine and perform the steps in VMware KB 2059786: Establishing a RDP connection with a Windows 8.1 desktop from Horizon View Client for Mac.
If you select the Remember this password check box when you log in to a server, you cannot log in to the same server as a different user if the credential caching timeout period (clientCredentialCacheTimeout) on the server has not yet expired. Horizon Client will automatically use the saved credentials to log you in to the server.
Workaround: Remove the server from the Selector window (right-click the server icon and select the Delete menu item), click the Add Server button to add the server again, and then log in to the server as the different user.
When you connect to a remote desktop with the VMware Blast display protocol from a Mac client system that has an NVIDIA GeForce GT 755M graphics card, the desktop stops responding.
Workaround: None. This is a third-party issue.
If you use a local certificate for server authentication, authentication sometimes fails and an SSL error occurs.
Workaround: Disable TLS 1.2 in Horizon Client. For information, see "Configure Advanced TLS/SSL Options" in VMware Horizon Client for Mac Installation and Setup Guide.
When you use Horizon Client on macOS Sierra (10.12), the remote desktop window exits from Tab mode when you enter full-screen mode or Split mode.
Workaround: None. This behavior is by design for Horizon Client.
When you use Horizon Client on macOS Sierra (10.12), Horizon Client stops responding when it reads a smart card with Apple CryptoTokenKit PIVToken.
Workaround: Disable PIVToken by using one of the following methods: 1) Install PKard for Mac v1.7, which automatically disables the com.apple.CryptoTokenKit.pivtoken token; or 2) Enter the following command at the command line:
sudo defaults write /Library/Preferences/com.apple.security.smartcard DisabledTokens -array com.apple.CryptoTokenKit.pivtoken
If you connect to a Windows 2016 RDS desktop, use the client drive redirection to share a local folder with the remote desktop, edit a Microsoft Office file in the shared folder, and then navigate to a different folder on the remote desktop, the remote desktop might stop responding.
Workaround: None. This problem is a Microsoft issue.
When you use Horizon Client on macOS Sierra (10.12), Apple builtin USB devices are not automatically redirected to remote desktops when you configure Horizon Client to connect USB devices automatically when Horizon Client starts (Connection > USB > Automatically connect at startup).
When you use Horizon Client on macOS Sierra (10.12), the remote desktop window turns black if you connect and reconnect to a Windows Server 2012 RDS desktop and then select Window > Show Tab Bar.
Workaround: Reset the remote desktop virtual machine.
If you use Horizon Client on macOS Sierra (10.12), and you connect to a server that is configured for URL Content Redirection, depending on the configuration, the popup dialog box Do you want to change your default browser to browsername or keep using "VMware Horizon URL Filter" appears behind the app windows. Also, if you try to set or change the default browser from the browser settings, you can see the popup dialog box behind the app windows on the server login.
Workaround: Navigate behind the app windows to view the popup dialog and click the Keep using "VMware Horizon URL Filter" button.
- In certain circumstances, opening a local file with File > Open in a remote desktop or remote application causes the guest operating system on the Horizon Agent machine to encounter a STOP error (blue screen) or to stop responding (hang) when client drive redirection (CDR) is used. For more information, see VMware Knowledge Base (KB) article 2149417: Agent machine gets STOP error or stops responding when you open a local file shared with CDR.
When you connect to a remote desktop that is running Windows 10 Creators Update with the VMware Blast display protocol, autofit fails when the desktop enters full screen with two displays.
Workaround: Resize the window and autofit recovers.
After you connect to a remote desktop with the USB Automatically connect at startup setting enabled, the desktop connection is sometimes disconnected.
If you connect and then reconnect to a remote desktop with the USB Automatically connect at startup setting enabled, not all USB devices appear in the USB menu after you reconnect to the desktop.
Workaround: Eject and then reinsert the USB device. For internal Mac devices, you might need to restart the computer.
On late 2016 MacBook Pro client systems, the response time of Windows Server 2016 hosted remote applications is slow in the first few seconds after you launch a Windows Server 2016 application or switch the top window between Horizon Client and the Windows Server 2016 application window.
Workaround: None. This problem is a third-party issue.
When you start the USB service on a macOS High Sierra (10.13) system, the System Extension Blocked dialog box appears.
Workaround: Click OK in the System Extension Block dialog box, navigate to System Preferences > Security & Privacy, and allow the extension to load.
If you connect to a remote application for which the pre-launch feature is enabled on a Horizon 7 version 7.2 server, and the Horizon Client reconnect behavior is set to "Ask to reconnect to open applications" or "Do not ask to reconnect and do not automatically reconnect," resumed application sessions are disconnected after the pre-launch timeout expires (default 10 minutes).
Workaround: Set the Horizon Client reconnect behavior to "Reconnect automatically to open applications."
When you enter full-screen mode in a remote desktop with three displays on a pre-macOS 10.13 system, or with four displays on a macOS 10.13 system, the toolbar does not pop up after you move the mouse to the top of the window on some displays.
Workaround: None. This problem is a third-party issue.