Vmware View 5 Client Mac Download
Horizon Client for Mac 5.v.iv | 10 March 2022
These release notes cover the following topics:
- What'due south New in This Release
- Internationalization
- Earlier You Begin
- Resolved Problems
- Known Problems
Top of Page
What's New in This Release
Horizon Client for Mac five.5.4 includes bug fixes.
Internationalization
The user interface and documentation for Horizon Customer are available in English, Japanese, French, German, Simplified Chinese, Traditional Chinese, Korean, and Spanish.
Before Yous Brainstorm
- Horizon Client requires a macOS High Sierra (10.thirteen), macOS Mojave (10.fourteen), macOS Catalina (ten.fifteen), or macOS Big Sur (11) operating arrangement running on a 64-bit Intel-based Mac.
- Horizon Client is supported with the latest maintenance release of Horizon 6 version vi.2.x and later releases.
- To install Horizon Client for Mac, download the disk prototype file from the VMware Horizon Client download page. For system requirements and installation instructions, run across the VMware Horizon Client for Mac Installation and Setup Guide document.
Resolved Issues
- Fixes to the lawmaking signing for 2 libraries. VMware would like to thank Arnor Kristjansson of Move AS for reporting this issue.
Known Issues
The known issues are grouped as follows.
-
If yous employ the PCoIP display protocol, connecting some password-protected storage devices (such equally IronKey USB wink drives) might non work correctly. For case, after y'all redirect the device to the remote desktop, the password prompt does not appear. The remote desktop shows that a new drive was added and then displays a new drive letter of the alphabet only no corresponding characterization to place the device.
Workaround: Configure Horizon Customer to automatically connect the device when you insert it. From the Horizon Client menu bar, select Desktop > USB > Autoconnect USB Devices on Insert.
-
When y'all insert an SD card into a Transcend USB three.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 non appear in the Connection > USB carte in Horizon Client and you cannot employ the USB redirection characteristic to connect the device to the remote desktop.
Workaround: Reinsert the SD bill of fare into the Transcend card reader. After the device is connected to the remote desktop, reinsert the SD card over again to make the disk volume announced in the remote desktop.
-
If y'all use the USB redirection feature to connect a Transcend USB 3.0 external hard drive to a remote desktop from your Mac customer system, files that yous re-create or movement to the drive do not appear on the drive after y'all disconnect the bulldoze from the remote desktop.
Workaround: Redirect the external difficult drive to the remote desktop again. The files announced on the bulldoze.
-
When you connect to a Windows remote desktop, start USB services, redirect a USB storage device to the remote desktop, disconnect from the remote desktop, and and so endeavor to reconnect to the remote desktop, either USB services are not available in the remote desktop or you cannot reconnect to the remote desktop. In Horizon Administrator, the state of the automobile is Amanuensis unreachable.
Workaround: If you are an end user, restart Horizon Client and endeavour again. If y'all are a Horizon administrator, restart Horizon Agent in the machine.
-
After yous connect to a remote desktop with the USB Automatically connect at startup setting enabled, the desktop connection is sometimes disconnected.
Workaround: None.
-
If you connect and and so reconnect to a remote desktop with the USB Automatically connect at startup setting enabled, not all USB devices appear in the USB carte afterwards you reconnect to the desktop.
Workaround: Eject and and then reinsert the USB device. For internal Mac devices, you might need to restart the calculator.
-
When yous start the USB service on a macOS High Sierra (x.thirteen) system, the System Extension Blocked dialog box appears.
Workaround: Click OK in the System Extension Block dialog box, navigate to Organization Preferences > Security & Privacy, and allow the extension to load.
-
On macOS ten.thirteen or later, if you are using a TokenD driver, the Keychain Admission app does not refresh when you unplug and re-plug in a smart card/smart card reader, and the Mac customer cannot obtain the update status for the smart card. Because of this event, the following problems might occur in Horizon Client on macOS 10.13 or later on:
- Smart card authentication does not piece of work after you unplug and re-plug in a smart carte/smart card reader.
- Smart card redirection might not work afterward you unplug and re-plug in a smart card/smart carte du jour reader several times.
- The Disconnect user sessions on smart card removal choice in Horizon Ambassador does not work.
- The smart carte du jour removal policy on the amanuensis car might non piece of work.
Workaround: Switch to the CryptoTokenKit driver on macOS 10.13 or later. If yous want to continue using the TokenD driver, for the smart card hallmark issue, quit both Keychain Admission and the Horizon Client app, relaunch Horizon Client, and perform smart card authentication once again, making sure that Keychain Access is not launched. For the smart card redirection issue, reboot the Mac client machine, launch Horizon Customer, and perform smart card authentication again, making sure that Keychain Access isn't launched. In that location is no workaround for the smart menu removal policy issue with a TokenD driver.
-
If you set the Horizon Client security preference (VMware Horizon Client > Preferences > Security) to Practice non 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 and so plug it dorsum in.
-
With the IDPrime .Cyberspace card, when the SafeNet Authentication Customer middleware is installed, you tin can view or change the smart bill of fare's enshroud type. If the cache type for the IDPrime .Internet carte du jour is "Normal Cache," the customer might not verify the smart card's Pivot during server authentication when the smart carte du jour PIN is cached.
Workaround: Change the Cache Blazon to "Always Prompt" for the IDPrime .Net carte du jour. This setting enables the client to verify the smart carte's PIN each fourth dimension the user connects to the server.
-
If multiple Horizon clients connect to the aforementioned RDS desktop or remote application simultaneously and map to a location-based printer with the aforementioned name, the printer appears in the first client session, simply not in after 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 awarding print dialog box. The location-based printer appears in the printer list.
-
Sometimes the virtual printing feature and location-based press feature are not able to display the right 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, yet.
Workaround: Log off the desktop running on the Windows Server 2012 RDS host and reconnect to information technology.
-
Keyboard shortcut mappings exercise non work if y'all are continued to a remote desktop or awarding and the Mac Input Source is Traditional Chinese or Korean.
Workaround: Earlier you connect to the remote desktop or application, switch to the English Input Source on the Mac client arrangement. If you 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 you connect to the remote desktop or awarding.
-
If you launch a remote desktop with the PCoIP brandish 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 than 4K (4096 x 2160), auto fit does not work for the remote desktop if yous change the display to full resolution.
Workaround. None. This problem is caused past a PCoIP limitation.
-
When you connect to a remote desktop that is running Windows 10 Creators Update with the VMware Nail 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 brandish 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.
-
With the Session Collaboration feature, the primary session cannot see the cursor movement of the collaborative session if the master session puts the cursor on an extended monitor.
Workaround: Motility the cursor back to the primary monitor.
-
If you start a remote desktop with the VMware Blast brandish protocol in total-screen or window mode on an iMac that has a Retina display or a monitor that supports a 5K display with Total Resolution style, then disconnect and reconnect with the PCoIP display protocol, the connexion fails and the remote desktop does non start.
Workaround: This trouble is caused by a PCoIP limitation. Change to Normal way and use the PCoIP or VMware Boom display protocol.
-
When yous are using a remote desktop in full-screen mode on multiple displays, if you click Customize Touch Bar on the external display and click Done, the Open selection window and Launch Detail List Impact Bar items do not piece of work.
Workaround: This problem is a third-party issue. Apple fixed this issue in macOS 10.14 Mojave.
-
You might lose focus for the front window when you utilise the Touch on Bar to switch between published applications that are hosted on Windows Server 2016. This trouble can likewise occur when yous press Command+~, or click the dock icon, to switch windows. This problem typically only occurs after switching windows several times.
Workaround: Use the mouse to click the window and regain focus.
-
Changes to webcam and sound devices that are continued to, or disconnected from, the Mac client system during a remote desktop session are not detected by the Real-Fourth dimension Audio-Video characteristic.
Workaround: Disconnect and reconnect to your remote desktop session to discover webcam and sound device changes. For example, if you lot connect a USB headset to the Mac client organisation during a remote desktop session and y'all 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 an administrator edits an application pool in Horizon Ambassador and changes the path to point to a different awarding that already has an awarding pool associated with it, unexpected results can occur. For example, the original awarding might exist launched from the Mac Dock instead of the new awarding.
Workaround: Make certain that each application in a subcontract is associated with only i application pool.
-
Users cannot launch an application from the Mac Dock if multiple awarding pools betoken to the same application in one subcontract, and if the awarding pool the users selected was created with associated parameters in Horizon Administrator. If a user saves the application in the Mac Dock and tries to open up the saved particular, 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 you utilize 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.
Workaround: None.
-
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 dissimilar user if the credential caching timeout menses ( clientCredentialCacheTimeout ) on the server has not yet expired. Horizon Client will automatically utilize 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 carte item), click the Add Server button to add the server again, and 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 after you launch a Windows Server 2016 awarding or switch the top window between Horizon Client and the Windows Server 2016 application window.
Workaround: None. This trouble is a third-party issue.
-
If you connect to a remote application for which the pre-launch characteristic is enabled on the Horizon server, and the Horizon Client reconnect behavior is gear up to "Ask to reconnect to open applications" or "Practise not enquire to reconnect and practise non automatically reconnect," resumed application sessions are disconnected after the pre-launch timeout expires (default ten minutes).
Workaround: Ready the Horizon Client reconnect behavior to "Reconnect automatically to open up applications."
-
With Moom 3.2.12 (3240), the Moom UI appears when you 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 end window when you use 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, use 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.
-
Yous cannot start a VMware App Volumes application from the Dock on the customer organisation.
Workaround: Start the application from Horizon Customer, or use a shortcut.
-
The Moom user interface does not piece of work for UWP published applications.
Workaround: None.
-
On client systems running macOS 11.v.1 and preview releases of macOS 12, client-to-amanuensis URL Content Redirection does non work for not-browser applications.
Workaround: Open the URL using the VMware Horizon URL Filter, equally described inVMware Knowledge Base (KB) article 85733.
Vmware View 5 Client Mac Download
Posted by: kevinrove1954.blogspot.com