Horizon Client for Mac OS X 4.0.1 | 31 March 2016
Last Updated: 31 March 2016
These release notes cover the following topics:
- Key Features
- What's New in This Release
- Before You Begin
- Resolved Issues
- Known Issues
Horizon Client for Mac OS X makes it easy to access your Windows-based remote desktop or application 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 Mavericks (10.9), Mac OS X Yosemite (10.10), and Mac OS X El Capitan (10.11) - Use a 64-bit Intel-based Mac to work on your Windows-based remote desktop or 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 application is fast and responsive regardless of where you are.
- Simple connectivity - Horizon Client for Mac OS X is tightly integrated with VMware Horizon 6 and VMware Horizon 7 for simple setup and connectivity. Quickly reconnect to your remote desktop or 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 OS X also supports optional RADIUS and RSA SecurID authentication.
Features Supported on Windows Desktops for Mac OS X Clients
|Horizon Client Feature||Supported in Horizon Client for Mac OS X|
|PCoIP display protocol||X|
|VMware Blast display protocol||X|
|RDP display protocol||X|
|Client drive redirection||X|
|Real-Time Audio-Video (RTAV)||X|
|Wyse Multimedia Redirection|
|Windows 7 Multimedia Redirection|
- You can use Horizon Client for Mac OS X to securely access remote Windows-based applications, in addition to remote desktops.
- You can use remote Windows-based applications only if you are connected to a VMware Horizon 6.0 with View or later server.
New Features in Horizon Client 4.0.1
- TLSv1.0 is enabled by default
Enabling TLSv1.0 ensures that by default Horizon Client can connect to VMware Horizon Air servers. You do not need to upgrade to Horizon Client 4.0.1 unless you use Horizon Client to connect to Horizon Air cloud-hosted desktops and applications.
New Features in Horizon Client 4.0
- VMware Blast Extreme
End-users can select the VMware Blast display protocol when they connect to a remote desktop or application in Horizon Client, and they can configure decoding and network protocol options for VMware Blast sessions. Administrators can create vmware-view URIs to launch a remote desktop or application with the VMware Blast display protocol. This feature also requires Horizon Agent 7.0.
- Client drive redirection feature enhancements
You can now open local files with remote applications directly from your local file system and you can run remote applications directly from your Applications folder.
- TLSv1.0 disabled by default
TLSv1.0 is disabled by default for communications between Horizon Client and View Connection Server and View Agent or Horizon Agent. SSLv3 is removed.
- Multiple monitors in different modes
When you have multiple monitors, you can use the Window > Use Single Display in Full Screen option to make a remote desktop fill only one monitor. With this option, the monitors do not have to be in the same mode. For example, if you are using a laptop connected to an external monitor, the external monitor can be in portrait mode or landscape mode.
- OS X El Capitan (10.11) Split View support
With Split View in OS X El Capitan, you can fill your Mac screen with two applications without having to manually move and resize windows. You can use Split View with remote desktops in full-screen mode (Full Screen or Use Single Display in Full Screen option).
- Configure Horizon Client to forget server user name and domain information
By default, Horizon Client stores the user name and domain that you enter when you log in to a server to connect to a remote desktop or application. For increased security, you can configure Horizon Client to never remember the server user name and domain.
- OpenSSL 1.0.2f support
The OpenSSL library is updated to version openssl-1.0.2f.
- Support discontinued for Mac OS X 10.8 as a client operating system
Horizon Client for Mac OS X 4.0 must be installed on Mac OS X 10.9, 10.10, or 10.11.
New Features in Horizon Client 3.5
- Client drive redirection feature general availability
The client drive redirection feature is now fully supported in Horizon Client for Mac OS X. Previously, client drive redirection was a Tech Preview feature.
- Automatic sharing of USB storage devices and FireWire and Thunderbolt-connected drives
You can configure the client drive redirection feature to automatically share all USB storage devices and FireWire and Thunderbolt-connected external drives with remote desktops and applications. You do not have to select the devices or drives to share.
- Default display protocol configurable in Horizon Client Settings
When multiple display protocols are configured for a remote desktop, you can select the display protocol to use from a menu on the Horizon Client Settings dialog box.
- Windows 10 remote desktop support
You can use Horizon Client to connect to Windows 10 remote desktops.
- Smart card reauthentication after idle session
If you use a smart card to authenticate, you can now use your smart card to reauthenticate if your remote session becomes idle.
- TLSv1.2 enabled by default
TLSv1.2 is enabled by default for communication between Horizon Client and View Connection Server and View Agent. In addition, the default cipher control string is changed to "!aNULL:kECDH+AES:ECDH+AES:RSA+AES:@STRENGTH".
- OpenSSL 1.0.2d support
The OpenSSL library is updated to version openssl-1.0.2d.
- 4K resolution support for remote desktops and applications
You can use a 4K display when accessing a remote desktop or application with the PCoIP display protocol. This feature also requires Horizon 6 version 6.2.
- Virtual printing changes
Virtual printers appear as <printer_name> in single-user virtual machine desktops and as <printer_name>(s<session_ID>) in session-based desktops on RDS hosts if View Agent 6.2 or later is installed.
- Access Point integration
Horizon Client can use the new Access Point appliance instead of a security server to connect to a View Connection Server instance. This feature also requires Horizon 6 version 6.2.
New Features in Horizon Client 3.4
- Smart cards for logging in to RDS desktops and hosted applications
Users can now authenticate to RDS-based desktops and RDS-based applications using smart cards. Requires View Agent 6.1 or later.
- USB redirection of mass storage devices on RDS desktops and hosted applications
Users can plug their USB flash drives and hard disks into their client systems and have these devices redirected to RDS-hosted desktops and applications. USB redirection of other types of USB devices, and other types of USB storage devices, such as security storage drives and USB CD-ROM, is not supported. This feature is supported on Windows Server 2012 RDS hosts. Requires View Agent 6.1 or later.
- Support discontinued for Mac OS X 10.6 and 10.7 as client operating systems
Horizon Client for Mac OS X 3.4 must be installed on Mac OS X 10.8, 10.9, or 10.10. For more information, see Retiring Old OSes: XP, Vista, Mac OS X 10.6 & 10.7.
- Client drive redirection (Tech Preview)
Users can now share folders and drives on their Mac client systems with remote desktops and applications. This feature is called client drive redirection. Requires View Agent 6.1.1 or later.
- Using a local IME with remote applications
Users can now use an IME (input method editor) installed on their Mac client systems to send non-English characters to remote applications.
- Linux remote desktops
Administrators can set up a Linux virtual machine as a remote desktop. End users can log in to a Linux remote desktop from Horizon Client for Mac OS X. Requires View Agent 6.1.1 or later and Horizon Client for Mac OS X 3.4. Not all features are supported in this release. For more information, see Setting Up Horizon 6 for Linux Desktops.
- OpenSSL 1.0.1m support
The OpenSSL library is updated to version openssl-1.0.1m.
New Features in Horizon Client 3.2
- Authenticate with a smart card - You can use a smart card to authenticate to remote desktops that have Windows XP, Windows Vista, Windows 7, and Windows Server 2008 R2 guest operating systems. You can also configure Horizon Client to automatically select a local certificate or the certificate on a smart card when you connect to a View server.
- Mac OS X Yosemite (10.10) support - You can install Horizon Client on Mac OS X Yosemite (10.10).
- Configurable keyboard mappings - You can customize how remote desktops and applications interpret Apple keyboard shortcuts by configuring keyboard shortcut mappings. You can create different keyboard shortcut mappings for remote desktops and remote applications.
- Connect to a View server at Horizon Client launch - You can set the Always connect at launch setting for a View server to automatically connects to that View server when you launch Horizon Client. This setting is enabled by default for the first View server that you connect to with Horizon Client.
- Autoconnect to a remote desktop - You can configure a View server to automatically launch a remote desktop when you connect to the server. If you are entitled to only one remote desktop on a View server, Horizon Client automatically launches that desktop when you connect to the server.
- Dock alerts - Flashing Windows taskbar items are forwarded to Horizon Client. A flashing red dot appears on the remote application's Dock icon when the application requires attention.
- OpenSSL 1.0.1i support - The OpenSSL library is updated to version openssl-1.0.1i.
New Features in Horizon Client 3.1
- Application name changed
The name of the Horizon Client application for Mac OS X has changed from VMware Horizon View Client to VMware Horizon Client. The name of the installer file has also changed.
- Expanded virtual printing and location-based printing support
The virtual printing and location-based printing features are now supported for single-session Windows Server 2008 R2 desktops, RDS desktops (that are hosted on virtual machine RDS hosts), and remote applications. You must be connected to an Horizon 6.0.1 with View server to use these features.
- USB 3.0 support
Horizon Client 3.1, together with Horizon 6.0.1 with View, supports USB 3.0 devices plugged into USB 3.0 ports. USB 3.0 devices are supported only with a single stream. Because multiple stream support is not implemented in this release, USB device performance is not enhanced.
- Reconnect to Horizon Client after sleep
Horizon Client now reconnects automatically after your Mac goes into sleep mode. If reconnection is not possible because of a session timeout, the authentication screen appears and you can reauthenticate to the View server. The secure tunnel must be enabled in View Administrator to use this feature.
- Windows system tray items appear in the Mac client notification area
If a remote application creates a Windows System Tray item, that item now appears in the notification area on the menu bar of your Mac client system. You can interact with the item from the notification area on your Mac in the same way that you would interact with it from the System Tray on a Windows system.
- URI and Horizon Workspace shortcut optimizations
When you launch a remote desktop or application from a uniform resource identifier (URI) or Horizon Workspace shortcut, a small status window now appears while the server prepares the remote desktop or application.
- Launch a remote application from the Dock
Clicking the icon for a remote application in the Dock now launches the remote application. Previously, Horizon Client launched when you clicked a remote application icon in the Dock.
- Hide the Horizon Client window after remote desktop or application launch
After you launch a remote desktop or application from Horizon Client, you can now hide the Horizon Client window by clicking the X icon in the upper left corner of the window. Clicking the X icon does not disconnect your sessions. You can also set a preference to always hide the Horizon Client window after a remote desktop or application has launched. You can reopen the Horizon Client window from the Dock item or from the Window menu.
- USB channel encryption configuration
You can now use the advanced SSL options that you use to encrypt communications between Horizon Client and the View server and View Agent to select security protocols and specify a cipher control string for the USB channel.
- Log file collection configuration
Administrators can now configure parameters in the /Library/Preferences/com.vmware.horizon.plist file on a Mac client system to set the maximum number of Horizon Client log files and the maximum number of days to keep log files.
New Features in Horizon Client 3.0
- Support for hosted applications - With this release of Horizon Client for Mac OS X, you can securely access remote Windows-based applications and remote desktops running in a Horizon 6.0 environment. After launching Horizon Client for Mac OS X and logging in to a Horizon 6.0 View server, you see all the remote applications that you are entitled to use, in addition to remote desktops. Selecting an application opens a window for that application on your Mac OS X system. A remote application looks and behaves as if it were locally installed. A new -appName option has been added so that you can create URIs for connecting to remote applications by clicking a link in a Web page.
- Favorite remote desktops and applications - You can select remote desktops and applications as favorites. Favorites are identified by a star. The star helps you quickly find your favorite desktops and applications. Your favorite selections are saved, even after you log off from the Horizon 6.0 View server.
- Configurable security protocols and cipher control string - End users can now select the security protocols that Horizon Client uses to connect to a Horizon 6.0 View server and configure the cipher control string.
The user interface and documentation for Horizon Client are available in English, Japanese, French, German, Simplified Chinese, Traditional Chinese, and Korean.
- Horizon Client requires a Mac OS X Mountain Lion (10.8), Mac OS X Mavericks (10.9), Mac OS X Yosemite (10.10), or Mac OS X El Capitan (10.11) operating system running on a 64-bit Intel-based Mac.
- You must install Horizon Client on Mac OS X Mountain Lion (10.8) or later to use remote applications. Remote applications do no not appear in Horizon Client if the client system is running an earlier verion of OS X. Remote applications are available only on VMware Horizon 6.0 with View and later servers.
- Horizon Client is supported with the latest maintenance release of VMware View 5.3.x and later releases.
- To install Horizon Client for Mac OS X, download the disk image file from the VMware Horizon Client download page. For system requirements and installation instructions, see Using VMware Horizon Client for Mac OS X.
Resolved in Horizon Client 4.0
- Horizon Client for Mac OS X now supports Split View on OS X El Capitan (10.11).
Resolved in Horizon Client 3.5.2
- The Horizon Client 3.5.2 release contains bug fixes for Mac OS X El Capitan (10.11).
Resolved in Horizon Client 3.5
- On Windows 7 and Windows Server 2008 R2 desktops, if you removed a drive from being shared on the desktop, Windows Explorer continued to display the removed drive in the guest operating system. This issue has been resolved.
- If you used the client drive redirection feature to share a video file on a USB device with a remote desktop, and you used VLC media player to play the video in the remote desktop, either the video did not play or you received the following error message: 'File reading failed: VLC could not read the file (Bad file descriptor)'. This issue has been resolved.
- With the client drive redirection feature, if you single-clicked a folder alias to add a folder to the Folder list, the folder alias itself was added to the Folder list, not the folder to which the alias referred. This issue has been resolved.
- When you used Horizon Client on a new MacBook to connect to a remote desktop, USB devices were not redirected to the remote desktop and did not appear in the USB menu. The USB menu displayed "No suitable USB device available." This issue has been resolved.
When TLSv1.2 was enabled, an SSL error occurred when you used a smart card to authenticate to the View server. This issue has been resolved.
Resolved in Horizon Client 3.4.1
- When you connected to a remote desktop from a Mac OS X El Capitan (10.11) client system, the entire desktop window was black. This issue has been resolved.
- You could not use the USB redirection feature to redirect a USB storage device from an OS X El Capitan (10.11) client system to a remote desktop. This issue has been resolved.
Resolved in Horizon Client 3.4
No issues were resolved in this version of Horizon Client for Mac OS X.
Resolved in Horizon Client 3.2
When you used the virtual printing feature and changed any printer settings or printing preferences, such as, for example, DPI or double-sided printing, the printer settings did not persist after you disconnected or logged off from a remote desktop. This issue has been resolved.
Resolved in Horizon Client 3.1
- Virtual printing was not supported for RDS (Remote Desktop Sessions) desktops or single-session Windows Server 2008 R2 desktops. This issue has been resolved.
- If you were connected to a remote application and you pressed Fn+control+option+del on your Mac keyboard, the Ctrl+Alt+Del screen of the Windows server that hosts the remote application appeared. You could click the Cancel button on the Window server screen to return to the remote application. However, if you pressed Fn+control+option+del in the remote application a second time, you could not click into the Windows server screen and return to the remote application. This issue has been resolved.
- Remote applications that depend on user interaction with the System Tray could not be shut down. For example, if you opened Skype as a remote application, the only way to close the window was to quit Horizon Client. This issue has been resolved.
Resolved in Horizon Client 3.0
- Previously, for a Mac with OS X Mavericks (10.9), you had to open System Preferences, click Mission Control, and deselect Displays have separate Spaces to use full screen with more than one monitor. This issue has been resolved.
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.
Because the key combination Command+Tab on an Apple keyboard is used for switching applications on Mac OS X, using this key combination has no effect in a remote desktop. For remote desktops that run Windows 7, this means that there is no equivalent of the key combination Windows+Tab for using Windows Flip 3D.
Workaround: You can use the key combination Command+Control+Tab for Windows Flip 3D, but you must also press Enter choose the application you want to switch to.
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 OS X 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 OS X, 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 OS X 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 OS X 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 OS X 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 8.x remote desktop from a OS X Mavericks (10.9) or OS X Yosemite (10.10) client system, or to a Windows Vista remote desktop from an OS X Yosemite (10.10) client system.
Workaround: For 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 use a PIV smart card to authenticate to a Windows XP remote desktop on which ActivClient is installed from an OS X Yosemite (10.10) client system and the smart card removal policy is set to disconnect user sessions on smart card removal, the desktop might not unlock automatically when you reconnect to the desktop. The smart card removal policy is a View Connection Server setting.
If you use a PIV smart card to authenticate to a Windows XP remote desktop on which ActivClient is installed from an OS X Yosemite (10.10) or OS X Mavericks (10.9) client system and the smart card removal policy is set to disconnect user sessions on smart card removal, the PIN dialog box in the Windows XP desktop stops responding when you reconnect to the desktop. The smart card removal policy is a View Connection Server setting.
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.
If you enable the Allow access to removable storage setting for the client drive redirection feature, and you also select the Automatically connect at startup or Automatically connect when inserted setting for the USB redirection feature, USB redirection does not work as expected. For example, non-storage devices, such as USB card readers, are not redirected automatically with the USB redirection feature.
Workaround: Manually redirect the USB devices.
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 OS X.