Vmware Vsphere Client 5.5 Mac Os X Download Updated

Vmware Vsphere Client 5.5 Mac Os X Download

Horizon Client for Mac 5.5.3 | 20 September 2021

These release notes embrace the post-obit topics:

Central Features
What's New in This Release
Internationalization
Before You Begin
Resolved Issues
Known Issues

Key Features

Horizon Customer for Mac makes it piece of cake to access your remote desktops and published applications from your Mac with the all-time possible user feel on the Local Surface area Network (LAN) or beyond a Wide Area Network (WAN).

Back up for macOS High Sierra (x.xiii), macOS Mojave (10.14), macOS Catalina (x.15), and macOS Big Sur (11) - Apply a 64-bit Intel-based Mac to work on your remote desktop or published awarding.
Unmatched performance - The adaptive capabilities of the PCoIP display protocol and the VMware Blast display protocol are optimized to deliver the all-time user experience, fifty-fifty over depression-bandwidth and high-latency connections. Your remote desktop or published awarding is fast and responsive, regardless of where yous are.
Simple connectivity - Horizon Client for Mac is tightly integrated with VMware Horizon 6 and VMware Horizon 7 for simple setup and connectivity. Rapidly 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 role, your data is delivered securely to yous wherever you are. Enhanced certificate checking is performed on the client. Horizon Customer for Mac also supports optional RADIUS and RSA SecurID authentication.

Top of Page

What'due south New in This Release

Horizon Customer for Mac 5.v.iii fixes an consequence previously encountered when starting published applications from client systems running macOS 11.6.

Horizon Customer for Mac 5.5.ii includes bug fixes.

Horizon Client for Mac 5.5.ane includes the post-obit new features:

Fixes an incompatibility with USB redirection and the Chrome browser. The upshot is as well present in the Chromium-based Edge browser.

Horizon Client for Mac 5.5 includes the following new features:

Configure cursor event treatment
You can optimize cursor effect handling by configuring settings in the ~/Library/Preferences/VMware Horizon View/config file on the Mac customer organisation. See Configuring Cursor Event Handling.
Client version restriction
A warning message appears in Horizon Customer if you effort to connect to a server that does not support your Horizon Customer version. For information about setting upwardly client version restrictions, come across Global Client Brake Settings for Customer Sessions.
Back up for macOS Big Sur (11)
You lot can install Horizon Client for Mac on a macOS Big Sur (11) arrangement.

Top of Page

Internationalization

The user interface and documentation for Horizon Client are bachelor in English, Japanese, French, German, Simplified Chinese, Traditional Chinese, Korean, and Spanish.

Top of Page

Before You Begin

Horizon Customer requires a macOS Loftier Sierra (10.13), macOS Mojave (10.xiv), macOS Catalina (10.15), or macOS Big Sur (11) operating organisation running on a 64-bit Intel-based Mac.
Horizon Client is supported with the latest maintenance release of Horizon 6 version 6.2.x and later releases.
To install Horizon Client for Mac, download the disk image file from the VMware Horizon Client download folio. For system requirements and installation instructions, see the VMware Horizon Client for Mac Installation and Setup Guide document.

Resolved Issues

The number provided before each resolved issue refers to the VMware internal bug tracking system.

Known Issues

The known bug are grouped as follows.

USB Redirection
Smart Carte Hallmark
Printing
Displays and Keyboards
Bear upon Bar
Miscellaneous

USB Redirection

If you use the PCoIP display protocol, connecting some password-protected storage devices (such as IronKey USB flash drives) might non work correctly. For example, after you redirect the device to the remote desktop, the countersign prompt does not appear. The remote desktop shows that a new drive was added and and so displays a new drive letter of the alphabet merely 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.
When you insert an SD menu into a Transcend USB iii.0 carte du jour reader fastened to your Mac client organisation, the SD menu is non mounted automatically. Because the SD carte is not mounted on your Mac customer system, the device does not appear in the Connexion > USB menu in Horizon Customer and y'all cannot use the USB redirection characteristic to connect the device to the remote desktop.

Workaround: Reinsert the SD card into the Transcend carte du jour reader. After the device is connected to the remote desktop, reinsert the SD card once more to brand the disk volume announced in the remote desktop.
If y'all utilize the USB redirection feature to connect a Transcend USB 3.0 external difficult drive to a remote desktop from your Mac customer arrangement, files that you copy or move to the bulldoze practice 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 bulldoze.
When you lot connect to a Windows remote desktop, starting time USB services, redirect a USB storage device to the remote desktop, disconnect from the remote desktop, and then try to reconnect to the remote desktop, either USB services are non available in the remote desktop or you cannot reconnect to the remote desktop. In Horizon Ambassador, the land of the machine is Agent unreachable.

Workaround: If y'all are an terminate user, restart Horizon Client and try over again. If yous are a Horizon administrator, restart Horizon Agent in the machine.
Afterward you connect to a remote desktop with the USB Automatically connect at startup setting enabled, the desktop connectedness is sometimes disconnected.

Workaround: None.
If yous connect then reconnect to a remote desktop with the USB Automatically connect at startup setting enabled, not all USB devices appear in the USB bill of fare later on you reconnect to the desktop.

Workaround: Eject and then reinsert the USB device. For internal Mac devices, yous might need to restart the computer.
When yous start the USB service on a macOS High Sierra (ten.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.

Smart Menu Authentication

On macOS ten.13 or after, if you are using a TokenD commuter, the Keychain Access app does not refresh when you unplug and re-plug in a smart carte/smart card reader, and the Mac client cannot obtain the update status for the smart card. Because of this issue, the following bug might occur in Horizon Customer on macOS x.xiii or afterwards:
- Smart card authentication does not work subsequently you unplug and re-plug in a smart carte/smart card reader.
- Smart carte redirection might not work later y'all unplug and re-plug in a smart card/smart card reader several times.
- The Disconnect user sessions on smart card removal option in Horizon Administrator does not work.
- The smart carte du jour removal policy on the agent machine might not piece of work.
Workaround: Switch to the CryptoTokenKit driver on macOS 10.13 or later. If you want to continue using the TokenD driver, for the smart card hallmark effect, quit both Keychain Access and the Horizon Customer app, relaunch Horizon Customer, and perform smart card authentication again, making sure that Keychain Admission is not launched. For the smart bill of fare redirection issue, reboot the Mac client machine, launch Horizon Client, and perform smart card authentication again, making certain that Keychain Access isn't launched. There is no workaround for the smart card removal policy issue with a TokenD driver.
If you set the Horizon Customer security preference (VMware Horizon Client > Preferences > Security) to Do not verify server identity certificates and connect to a server that has a valid root-signed certificate, Horizon Client might stop responding.

Workaround: Unplug the smart bill of fare reader and then plug information technology back in.
With the IDPrime .Cyberspace card, when the SafeNet Hallmark Customer middleware is installed, you can view or change the smart carte du jour's cache type. If the cache type for the IDPrime .Net card is "Normal Cache," the client might not verify the smart card's Pivot during server authentication when the smart carte du jour PIN is cached.

Workaround: Change the Cache Type to "Always Prompt" for the IDPrime .Net card. This setting enables the client to verify the smart card'due south PIN each time the user connects to the server.

Press

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 customer session, but not in later client sessions.

Workaround: For the client sessions in which the printer does non appear, perform a manual refresh. For a remote desktop, press F5 or refresh the Devices and Printers window. For a remote application, shut and reopen the awarding 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 tin can occur with desktops provided by Windows Server 2012 RDS hosts. The printers shown inside applications are correct, still.

Workaround: Log off the desktop running on the Windows Server 2012 RDS host and reconnect to it.

Displays and Keyboards

Keyboard shortcut mappings do not piece of work if yous are continued to a remote desktop or application and the Mac Input Source is Traditional Chinese or Korean.

Workaround: Before you lot connect to the remote desktop or application, switch to the English Input Source on the Mac client system. If you lot are already connected to the remote desktop or application, reconnect to the Connection Server instance and switch to the English Input Source on the Mac client system before y'all connect to the remote desktop or application.
If you launch a remote desktop with the PCoIP display protocol in full screen or window mode on an iMac with a Retina or monitor that supports a 5K display, and the screen size is more than 4K (4096 x 2160), automobile fit does not work for the remote desktop if you modify the display to full resolution.

Workaround. None. This trouble is caused by a PCoIP limitation.
When you connect to a remote desktop that is running Windows ten Creators Update with the VMware Boom display protocol, autofit fails when the desktop enters full screen with two displays.

Workaround: Resize the window and autofit recovers.
When you connect to a remote desktop with the VMware Boom display protocol from a Mac client organisation that has an NVIDIA GeForce GT 755M graphics menu, the desktop stops responding.

Workaround: None. This is a 3rd-party result.
With the Session Collaboration feature, the primary session cannot see the cursor movement of the collaborative session if the chief session puts the cursor on an extended monitor.

Workaround: Move the cursor back to the primary monitor.
If yous start a remote desktop with the VMware Blast display protocol in full-screen or window manner on an iMac that has a Retina brandish or a monitor that supports a 5K display with Full Resolution way, so disconnect and reconnect with the PCoIP display protocol, the connection fails and the remote desktop does non start.

Workaround: This trouble is caused past a PCoIP limitation. Change to Normal mode and use the PCoIP or VMware Blast display protocol.

Touch Bar

When you are using a remote desktop in full-screen mode on multiple displays, if yous click Customize Touch Bar on the external display and click Done, the Open selection window and Launch Detail Listing Touch Bar items practise not work.

Workaround: This problem is a third-party issue. Apple stock-still this issue in macOS ten.xiv Mojave.
Yous might lose focus for the forepart window when you use the Touch Bar to switch between published applications that are hosted on Windows Server 2016. This problem can besides occur when yous printing Command+~, or click the dock icon, to switch windows. This trouble typically only occurs after switching windows several times.

Workaround: Use the mouse to click the window and regain focus.

Miscellaneous

Changes to webcam and audio devices that are connected to, or disconnected from, the Mac client organization during a remote desktop session are non detected by the Real-Fourth dimension Audio-Video feature.

Workaround: Disconnect and reconnect to your remote desktop session to detect webcam and audio device changes. For example, if y'all connect a USB headset to the Mac client system during a remote desktop session and you desire to employ that headset on the remote desktop, you must disconnect and reconnect to the remote desktop session to make the headset available.
If an ambassador edits an application pool in Horizon Administrator and changes the path to indicate to a dissimilar 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 just ane application pool.
Users cannot launch an application from the Mac Dock if multiple awarding pools point to the same application in one farm, and if the application pool the users selected was created with associated parameters in Horizon Ambassador. If a user saves the application in the Mac Dock and tries to open the saved item, the awarding fails to launch with the associated parameters.

Workaround: Brand sure that each application in a farm is associated with only one application puddle.
If yous use Horizon Client on a new MacBook, and you employ 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.

Workaround: None.
If you lot select the Remember this countersign cheque box when yous log in to a server, you lot cannot log in to the same server every bit a unlike user if the credential caching timeout period ( clientCredentialCacheTimeout ) on the server has not yet expired. Horizon Customer will automatically use the saved credentials to log y'all in to the server.

Workaround: Remove the server from the Selector window (right-click the server icon and select the Delete menu detail), click the Add Server push to add the server once more, then log in to the server as the different user.
On late 2016 MacBook Pro client systems, the response time of Windows Server 2016 hosted remote applications is slow in the first few seconds afterward you launch a Windows Server 2016 awarding or switch the peak window between Horizon Customer and the Windows Server 2016 awarding window.

Workaround: None. This problem is a third-party consequence.
If yous connect to a remote awarding for which the pre-launch characteristic is enabled on the Horizon server, and the Horizon Client reconnect behavior is set to "Inquire to reconnect to open applications" or "Do not ask to reconnect and do not automatically reconnect," resumed awarding sessions are disconnected later on the pre-launch timeout expires (default 10 minutes).

Workaround: Set the Horizon Customer reconnect beliefs to "Reconnect automatically to open up applications."
With Moom three.2.12 (3240), the Moom UI appears when yous hover your mouse over the Close icon, not the maximize icon, in Role 2016 and 2019 apps.

Workaround: None.
You might lose focus for the front window when yous use custom controls in the Moom app to move or resize published applications that are hosted on Windows Server 2016 or Windows Server 2019.

Workaround: To regain focus, utilize your mouse to click on the championship bar of the application window.
Horizon Client for Mac stops responding if you unplug an external graphics processing unit (GPU).

Workaround: None.
You lot cannot start a VMware App Volumes awarding from the Dock on the client system.

Workaround: Starting time the awarding from Horizon Client, or use a shortcut.
The Moom user interface does not piece of work for UWP published applications.

Workaround: None.
On customer systems running macOS 11.v.1 and preview releases of macOS 12, client-to-agent URL Content Redirection does not work for not-browser applications.

Workaround: Open the URL using the VMware Horizon URL Filter, as described inVMware Knowledge Base (KB) article 85733.