Vsphere-5.5-client-download on Mac

Horizon Client for Mac 5.5.iii | 20 September 2021

These release notes embrace the post-obit topics:

Cardinal Features

Horizon Client for Mac makes it piece of cake to access your remote desktops and published applications from your Mac with the best possible user experience on the Local Expanse Network (LAN) or across a Wide Area Network (WAN).

  • Support for macOS High Sierra (x.13), macOS Mojave (10.xiv), macOS Catalina (ten.15), and macOS Large Sur (xi) - Utilise a 64-flake Intel-based Mac to work on your remote desktop or published awarding.
  • Unmatched functioning - The adaptive capabilities of the PCoIP display protocol and the VMware Boom display protocol are optimized to evangelize 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 yous are.
  • Simple connectivity - Horizon Client for Mac is tightly integrated with VMware Horizon 6 and VMware Horizon 7 for unproblematic setup and connectivity. Apace reconnect to your remote desktop or published awarding by selecting shortcuts in Horizon Customer.
  • Secure from any location - At your desk-bound or abroad from the office, your information is delivered securely to you wherever y'all are. Enhanced certificate checking is performed on the client. Horizon Client for Mac too supports optional RADIUS and RSA SecurID hallmark.

Peak of Page

What's New in This Release

Horizon Client for Mac 5.5.3 fixes an effect previously encountered when starting published applications from customer systems running macOS 11.half-dozen.

Horizon Client for Mac 5.5.2 includes problems fixes.

Horizon Client for Mac 5.five.1 includes the following new features:

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

Horizon Client for Mac v.5 includes the following new features:

  • Configure cursor issue treatment
    You can optimize cursor effect handling by configuring settings in the ~/Library/Preferences/VMware Horizon View/config file on the Mac client arrangement. Run across Configuring Cursor Outcome Handling.
  • Customer version restriction
    A warning bulletin appears in Horizon Client if you attempt to connect to a server that does not support your Horizon Customer version. For information nigh setting up customer version restrictions, run into Global Client Brake Settings for Client Sessions.
  • Support for macOS Big Sur (11)
    Yous tin install Horizon Client for Mac on a macOS Large Sur (11) system.

Top of Folio

Internationalization

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

Top of Folio

Before You Begin

  • Horizon Customer requires a macOS High Sierra (10.13), macOS Mojave (x.fourteen), macOS Catalina (ten.15), or macOS Large Sur (11) operating system running on a 64-bit Intel-based Mac.
  • Horizon Client is supported with the latest maintenance release of Horizon 6 version six.2.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 Customer for Mac Installation and Setup Guide document.

Resolved Issues

The number provided earlier each resolved effect refers to the VMware internal issues tracking system.

Known Problems

The known issues are grouped as follows.

USB Redirection

  • If you lot use the PCoIP brandish protocol, connecting some countersign-protected storage devices (such equally IronKey USB flash drives) might not work correctly. For example, later on you redirect the device to the remote desktop, the password prompt does not appear. The remote desktop shows that a new bulldoze was added and so displays a new bulldoze 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 Customer carte du jour bar, select Desktop > USB > Autoconnect USB Devices on Insert.

  • When yous insert an SD bill of fare into a Transcend USB 3.0 card reader attached to your Mac customer organization, the SD card is not mounted automatically. Considering the SD card is not mounted on your Mac client system, the device does non announced in the Connection > USB menu in Horizon Client and yous cannot utilise 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 iii.0 external difficult bulldoze to a remote desktop from your Mac customer organization, files that you copy or move to the drive do not appear on the bulldoze afterward you disconnect the bulldoze from the remote desktop.

    Workaround: Redirect the external hard drive to the remote desktop over again. The files appear on the drive.

  • When y'all connect to a Windows remote desktop, outset USB services, redirect a USB storage device to the remote desktop, disconnect from the remote desktop, and so try to reconnect to the remote desktop, either USB services are not available in the remote desktop or you lot cannot reconnect to the remote desktop. In Horizon Administrator, the state of the machine is Amanuensis unreachable.

    Workaround: If you are an finish user, restart Horizon Client and try again. If you are a Horizon ambassador, restart Horizon Agent in the car.

  • Subsequently you connect to a remote desktop with the USB Automatically connect at startup setting enabled, the desktop connection is sometimes asunder.

    Workaround: None.

  • If you connect and and then reconnect to a remote desktop with the USB Automatically connect at startup setting enabled, not all USB devices appear in the USB carte du jour afterward you lot reconnect to the desktop.

    Workaround: Eject and then reinsert the USB device. For internal Mac devices, you lot might demand to restart the computer.

  • When you commencement the USB service on a macOS Loftier Sierra (x.13) system, the System Extension Blocked dialog box appears.

    Workaround: Click OK in the System Extension Block dialog box, navigate to Organisation Preferences > Security & Privacy, and allow the extension to load.

Smart Card Authentication

  • On macOS 10.13 or later, if you lot are using a TokenD driver, the Keychain Access app does not refresh when you lot unplug and re-plug in a smart card/smart menu reader, and the Mac client cannot obtain the update status for the smart card. Because of this issue, the following problems might occur in Horizon Client on macOS x.thirteen or later:

    • Smart carte du jour authentication does not work after y'all unplug and re-plug in a smart card/smart carte du jour reader.
    • Smart card redirection might non work afterwards you unplug and re-plug in a smart carte du jour/smart card reader several times.
    • The Disconnect user sessions on smart card removal option in Horizon Administrator does not work.
    • The smart carte removal policy on the agent car might not 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 menu authentication issue, quit both Keychain Access and the Horizon Client app, relaunch Horizon Client, and perform smart carte du jour authentication again, making sure that Keychain Access is not launched. For the smart menu redirection result, reboot the Mac client motorcar, launch Horizon Client, and perform smart card authentication once again, making certain that Keychain Access isn't launched. There is no workaround for the smart card removal policy issue with a TokenD commuter.

  • If you set the Horizon Client 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 terminate responding.

    Workaround: Unplug the smart card reader and so plug it back in.

  • With the IDPrime .Net bill of fare, when the SafeNet Hallmark Client middleware is installed, you tin view or change the smart card'south cache type. If the cache type for the IDPrime .Net carte is "Normal Cache," the client might not verify the smart menu's PIN during server authentication when the smart menu PIN is cached.

    Workaround: Change the Enshroud Blazon to "Always Prompt" for the IDPrime .Net card. This setting enables the client to verify the smart card's PIN each time the user connects to the server.

Printing

  • If multiple Horizon clients connect to the same RDS desktop or remote application simultaneously and map to a location-based printer with the same proper noun, the printer appears in the first customer session, but not in after client sessions.

    Workaround: For the client sessions in which the printer does not appear, perform a transmission refresh. For a remote desktop, printing F5 or refresh the Devices and Printers window. For a remote application, shut 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 characteristic are not able to display the correct listing of printers in the Devices and Printers window of a remote, session-based desktop. This effect 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 information technology.

Displays and Keyboards

  • Keyboard shortcut mappings practice not piece of 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 awarding, 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 Connectedness Server instance and switch to the English language 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 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), auto fit does not work for the remote desktop if you change the display to full resolution.

    Workaround. None. This problem is caused by a PCoIP limitation.

  • 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 ii displays.

    Workaround: Resize the window and autofit recovers.

  • When y'all connect to a remote desktop with the VMware Blast display protocol from a Mac client arrangement that has an NVIDIA GeForce GT 755M graphics bill of fare, the desktop stops responding.

    Workaround: None. This is a third-political party issue.

  • With the Session Collaboration feature, the primary session cannot see the cursor motion of the collaborative session if the principal session puts the cursor on an extended monitor.

    Workaround: Move the cursor back to the primary monitor.

  • If you kickoff a remote desktop with the VMware Blast display protocol in full-screen or window mode on an iMac that has a Retina display or a monitor that supports a 5K display with Full Resolution mode, and so disconnect and reconnect with the PCoIP display protocol, the connectedness fails and the remote desktop does not beginning.

    Workaround: This problem is acquired by a PCoIP limitation. Modify to Normal fashion and use the PCoIP or VMware Blast display protocol.

Touch Bar

  • When yous are using a remote desktop in full-screen fashion on multiple displays, if you lot click Customize Touch Bar on the external brandish and click Done, the Open selection window and Launch Item List Touch on Bar items exercise non work.

    Workaround: This problem is a tertiary-party issue. Apple stock-still this effect in macOS 10.14 Mojave.

  • You might lose focus for the front window when y'all apply the Touch on Bar to switch between published applications that are hosted on Windows Server 2016. This problem can as well occur when you press Control+~, or click the dock icon, to switch windows. This trouble typically simply occurs after switching windows several times.

    Workaround: Apply 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 customer 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 arrangement during a remote desktop session and you lot desire to use that headset on the remote desktop, you must disconnect and reconnect to the remote desktop session to brand the headset available.

  • If an administrator edits an application pool in Horizon Ambassador and changes the path to betoken to a different application that already has an application pool associated with it, unexpected results can occur. For example, the original awarding might exist launched from the Mac Dock instead of the new application.

    Workaround: Brand sure that each application in a farm is associated with merely 1 application puddle.

  • Users cannot launch an application from the Mac Dock if multiple application pools point to the same awarding in one farm, and if the awarding puddle 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 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 yous use Horizon Client on a new MacBook, and you use the USB-C port to connect to the network, you might detect poor performance when copying and pasting between a remote desktop to a shared folder.

    Workaround: None.

  • If you select the Remember this password check box when you log in to a server, yous cannot log in to the aforementioned server as a dissimilar 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 together Server button to add the server again, and then log in to the server as the unlike user.

  • On late 2016 MacBook Pro client systems, the response time of Windows Server 2016 hosted remote applications is ho-hum in the starting time few seconds afterwards 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 3rd-political party issue.

  • If you connect to a remote awarding for which the pre-launch characteristic is enabled on the Horizon server, and the Horizon Customer reconnect behavior is set to "Ask to reconnect to open up applications" or "Do not ask to reconnect and practice non automatically reconnect," resumed application sessions are disconnected after the pre-launch timeout expires (default x minutes).

    Workaround: Set the Horizon Client reconnect behavior to "Reconnect automatically to open up applications."

  • With Moom iii.ii.12 (3240), the Moom UI appears when y'all hover your mouse over the Close icon, not the maximize icon, in Office 2016 and 2019 apps.

    Workaround: None.

  • You might lose focus for the front window when you utilise custom controls in the Moom app to motility or resize published applications that are hosted on Windows Server 2016 or Windows Server 2019.

    Workaround: To regain focus, apply your mouse to click on the title bar of the application window.

  • Horizon Client for Mac stops responding if you unplug an external graphics processing unit (GPU).

    Workaround: None.

  • You cannot start a VMware App Volumes application from the Dock on the client arrangement.

    Workaround: Start the application from Horizon Client, or apply a shortcut.

  • The Moom user interface does not work for UWP published applications.

    Workaround: None.

  • On customer systems running macOS eleven.5.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 of operations (KB) commodity 85733.

check-circle-line assertion-circumvolve-line close-line

Scroll to top icon

Vsphere-5.5-client-download on Mac

Posted by: marymainst.blogspot.com